Preparing for GeoPackage 1.2
The GeoPackage SWG continues to make changes to the GeoPackage Encoding Standard. Our goal is to make the standard clear, concise, and self-consistent. Following on 1.0.1 (which focused on features) and 1.1.0
(which focused on tiles), we have made a number of changes focusing on
extensions. As always, we insist on maintaining reverse compatibility. In fact there are no substantive changes to existing parts of the core this time around.
We plan to release this version as GeoPackage 1.2. For detailed information on this release, please review the release notes. The changes
range from typographical fixes to substantive changes that alter
requirements. Following is a summary of the substantive changes:
- Adding an "Attributes" section to describe the use of non-spatial data
- Deprecating Requirement 69 (a mandate for extension F.1 that was nearly impossible to achieve or verify)
- Deprecating Annexes F.2, F.4, and F.5, three extensions that were determined to be non-interoperable and non-usable
- Updating the column name for WKT for Coordinate Reference Systems (Annex F.10)
- Adding the Elevation Extension as Annex F.11
- Changing the way GeoPackage versions are declared based on community feedback
We initiated a 30-day comment period on Friday. After the comment period concludes, we will address all of the feedback. After that we will request a vote by the OGC Technical Committee to adopt 1.2 as an official encoding standard. We hope that you will take this opportunity to check out the draft and let us know if there is anything that can be improved.
Excited to see support for "non-spatial" tables in 1.2. No objections to other proposed changes for 1.2
ReplyDeleteHope for a release soon.
Thanks
Michael