Date | Topic | Presentation |
---|
July 18, 2017 | OGC® GeoPackage Encoding Standard | |
📝 Notes
GeoPackage fits between GeoJSON, which is very lightweight and text based, and a full-blown spatial database system.
GeoPackage is broadly implemented - there are 10-15 vendors listed on the GeoPackage.org site.
GeoPackage uses the WKB (Well Known Binary) representation for vector data. This comes from the OGC Simple Features specification.
The GDAL package can translate both ways for Shapefile <-> GeoPackage.
There is an online GeoPackage to Shapefile converter
File management becomes easier with GeoPackage vs. Shapefiles since everything is contained in a single file
There are many known limitations for Shapefiles. One source is the "Shapefile Challenge" web page.
Shapefiles can only contain one geometry type per file.
There are practical limits to the amount of data that can be put into a GeoPackage file. However, hydrology for the Mississippi river would fit very comfortably
When thinking about limits to GeoPackage, realize that most of those limits (and more) apply to Shapefiles.