As per a recent discussion (https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Geopackages-Can-Alteryx-Open-GeoPackage-Files-gpkg/td-p/734558), please add the GeoPackage datatype to the Input tool.
For reference, the open-source project ogr2ogr has this functionality. (https://gdal.org/programs/ogr2ogr.html)
Thanks!
I would just add that Geopackages needs to be an input AND output options.
Shapefiles should be avoided for years now (file size limit, 8 caracters column names, etc...).
Most of opendata will are or will be in this format in the near future.
Thanks
hi @Hollingsworth, thanks for this idea - we all love open source. As soon as this meets the necessary criteria, our product team will review.
As a spatial ETL tool, I would say this functionality is essential for Alteryx
I agree with @PSolomonCote that it should be part of the Output tool as well. The faster Alteryx supports new and better file formats, the faster we move away from legacy formats that are inefficient or ineffective.
This would be a hugely useful feature. Shapefiles are less than ideal for a number of reasons and there's also been an increase in open, and Government data being supplied as .gpkg. Being able to input and output in that format would be great!
Seems odd that this isn't already a thing. Please make it a thing. Input & Output for the win
Would love to have Geopackage support! (Currently looking at 100s of files that I can't read)
@grossal @Hollingsworth , improving our spatial file I/O is definitely something that is on our radar. In addition to Geopackage are there any other emerging formats you would like to see?
We all need to come together and do our part to end the dominance of the shapefile. 😁
http://switchfromshapefile.org/
@JeffVR it would be amazing if we could also support WKT files!
@JeffVR,
While not a file format, I think that a robust ESRI REST connector is a significant need for the Spatial toolkit. I have written a very simple endpoint downloader for my purposes. But it was written out of need, not out of scope, meaning that I only coded the bits that I needed and not a full replication of the parameters. There are also many different ways that the ArcGIS server can be organized/authenticated and sometimes I have to stop in the middle of my work and debug for an edge caseFurthermore, considering the huge ArcGIS Online community, I also think there is a need for an ESRI REST publisher/writer connector macro. This is certainly in line with the Alteryx "we crunch and then give to others for display" model that has been successful with Tableau, et.al.Thanks for engaging us on this question!
Ordnance Survey are making more and more spatial data available in geopackage format only, especially output from the National Geographic Database (NGD). Being able to handle the geopackage native format both as input and output would make life much easier and tasks less time consuming as it removes the need to convert to another format first before being able use and manipulate the data in Alteryx.
