Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Geometry Encoding Clarification for Non-Linear Geometry Types #402
It is validated to always be 0 in ets-gpkg12. Was this bit only meant to be 1 for the deprecated user defined geometry types? It's a little confusing that the non-linear geometry types require an extension but are encoded with an extended bit of 0 (StandardGeoPackageBinary) instead of 1 (ExtendedGeoPackageBinary).
I'm not sure what the intention was for this either anymore. The idea of the extension bit was that it provided an indication that the geometry body was not encoded in standard WKB. Instead it started with a vendor tag followed by vendor specific content.