Open Geospatial Consortium |
Publication Date: 2024-02-06 |
Reference URL for this OGC® document: http://www.opengis.net/doc/NOTES/GeoPackage/1.4 |
Internal reference number of this OGC® document: 23-018r1 |
Category: Release Notes |
Editor: Jeff Yutzler |
Release Notes for OGC GeoPackage 1.4.0 |
Copyright notice |
Copyright © 2024 Open Geospatial Consortium |
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ |
Warning |
This document is not an OGC Standard. This document provides release notes for an OGC Standard. This document is subject to change without notice and may not be referred to as an OGC Standard.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
Document type: Release Notes |
Document subtype: |
Document stage: Approved |
Document language: English |
License Agreement
Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnished agrees to the terms of this Agreement.
If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR.
THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTS THAT MAY BE IN FORCE ANYWHERE IN THE WORLD.
THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE INTELLECTUAL PROPERTY WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE INTELLECTUAL PROPERTY WILL BE UNINTERRUPTED OR ERROR FREE. ANY USE OF THE INTELLECTUAL PROPERTY SHALL BE MADE ENTIRELY AT THE USER’S OWN RISK. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR ANY CONTRIBUTOR OF INTELLECTUAL PROPERTY RIGHTS TO THE INTELLECTUAL PROPERTY BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM ANY ALLEGED INFRINGEMENT OR ANY LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR UNDER ANY OTHER LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH THE IMPLEMENTATION, USE, COMMERCIALIZATION OR PERFORMANCE OF THIS INTELLECTUAL PROPERTY.
This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together with all copies in any form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except as provided in the following sentence, no such termination of this license shall require the termination of any third party end-user sublicense to the Intellectual Property which is in force as of the date of notice of such termination. In addition, should the Intellectual Property, or the operation of the Intellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe, any patent, copyright, trademark or other right of a third party, you agree that LICENSOR, in its sole discretion, may terminate this license without any compensation or liability to you, your licensees or any other party. You agree upon termination of any kind to destroy or cause to be destroyed the Intellectual Property together with all copies in any form, whether held by you or by any third party.
Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual Property shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property without prior written authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole entity that may authorize you or any third party to use certification marks, trademarks or other special designations to indicate compliance with any LICENSOR standards or specifications. This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any provision of this Agreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make it valid and enforceable, and as so modified the entire Agreement shall remain in full force and effect. No decision, action or inaction by LICENSOR shall be construed to be a waiver of any rights or remedies available to it.
This document provides the set of revision notes for OGC® GeoPackage Encoding Standard, version 1.4.0 [OGC 12-128r19] and does not modify that Standard.
This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the Standard set forth in this document, and to provide supporting documentation.
ogcdoc, GeoPackage, release notes
2. References
The following normative documents are new or updated references in the Standard to which these Release Notes apply.
3. Terms and definitions
This document uses the terms defined in Sub-clause 5.3 of [OGC 06-121r8], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this Standard.
For the purposes of this document, the following additional terms and definitions apply.
3.1. administrative change
An administrative change is a change that does not alter the conformance abstract tests for any requirements. It includes typographical errors, changes in wording to improve clarity or consistency, and perfunctory changes such as changes in version numbers.
3.2. critical Change
A critical change is a change that alters requirements in a way that is known to cause reverse compatibility issues.
4. Change Log
4.1. KEY
-
Source:
-
Change Request (CR)
-
GitHub Issue
-
Editor - The GeoPackage document Editor
-
OGC-NA - OGC Naming Authority review
-
Public - Public Comment period
-
SWG decision
-
User - The GeoPackage User Community
-
Other
-
-
Identifier: Change Request number or issue number and pull request/commit in GitHub
-
Type:
-
A=Administrative
-
S=Substantive
-
C=Critical
-
See Description of Critical Changes for more information on critical changes and Description of Substantive Changes for more information on substantive changes.
-
Section: Section number in the updated document
-
Description: Brief text describing the change
-
Purpose: the reason for the change:
-
Clarity
-
Consistency
-
Interoperability
-
Perfunctory
-
Readability
-
Usability
-
Correctness
-
4.2. Change Table
Source | Identifier | Type | Section | Description | Purpose |
---|---|---|---|---|---|
A |
1.1.1.1.1 |
Add note explaining how to retrieve the GeoPackage Version |
Clarity |
||
S |
1.1.1.1.3, 1.1.3.1.2, Annex F.8 |
Make DATETIME format more flexible |
Correctness |
||
A |
1.1.1.1.1 |
Move example indicating GeoPackage Version format to a note |
Clarity |
||
S |
1.1.1.1.3 |
Relax Requirement #4 |
Usability |
||
S |
Annex F.3 |
Replace update1 trigger with update6 and update7 to support upsert operations |
Correctness |
||
A |
1.1.1.1.3, 1.1.3.1.2, Annex F.8 |
Point all references to date-time formats back to Requirement #5 |
Clarity |
||
A |
1.1.2.1.1, Annex I, Annex J |
Update EPSG references |
Correctness |
6. Description of Substantive Changes
6.1. Relax Requirement #4
The GeoPackage designation was originally designed to indicate a schema with maximum interoperability. However, as the standard has evolved, it has become increasingly important for GeoPackages to contain certain extensions. In light of this evolution, the difference between a GeoPackage and an Extended GeoPackage is no longer relevant. If anything, this requirement was just causing confusion. The presence of extensions would cause the Executable Test Suite (ETS) to skip Requirement 4, which has implications in how ETS results are interpreted.
This change has no significant operational impact.
6.2. Update R-tree Index Triggers
Two changes have been made to the R-tree Spatial Index Triggers, which are part of the R-tree Spatial Indexes Extension.
-
In GeoPackage 1.2.1, the update3 trigger was fixed. However, to simplify the process for a client to detect whether the faulty trigger has been repaired, the trigger has now been renamed to _update5.
-
In GeoPackage 1.4.0, the update1 trigger has been fixed to correct a flaw that prevented it from working properly during
UPSERT
statements. The update1 trigger has been deprecated and replaced by the new update6 and update7 triggers. As with the update3 and update5 triggers, this simplifies the process for a client to detect whether the faulty trigger has been repaired.
These changes are designed to prevent interoperability problems and do not introduce any new interoperability risks. Clients are encouraged to apply these fixes to older versions of GeoPackage as well. The Executable Test Suite will be updated to ensure that either set of triggers is treated as compliant.
6.3. Make DATETIME format more flexible
In GeoPackage 1.3.1 and prior, Requirement 5 specified that DATETIME formats must conform to the template YYYY-MM-DDTHH:MM:SS.SSSZ
.
This is unnecessarily restrictive and can cause problems in the following ways:
-
Requiring unnecessary precision may add bloat to the GeoPackage.
-
Requiring a very specific precision may cause problems when converting other data to GeoPackage, including loss of data and the necessity of an additional agent to artificially modify the existing data so that it conforms to the template.
In fact, SQLite documentation offers a number of legal formats and allows fractional seconds to have fewer or more than three digits. In response, the SWG agreed to relax the definition, while retaining compatibility with ISO-8601.
Note
|
After reviewing the potential impact on GeoPackage clients, changes regarding date-time formats have been deferred until further notice. |
7. Future Work
In the future, the GeoPackage SWG will revisit the DATETIME topic, with the goal to mitigate the issues that were brought to the group’s attention during the public comment period.
Appendix A: Revision History
Date | Release | Editor | Primary clauses modified | Descriptions |
---|---|---|---|---|
2023-03-19 |
0.1 |
J. Yutzler |
all |
Initial Revision |
2023-03-29 |
0.2 |
J. Yutzler |
4, 6 |
640/655 |
2023-05-24 |
0.3 |
J. Yutzler |
4, 6 |
660/661 |
2023-05-31 |
0.4 |
J. Yutzler |
4 |
OAB Review |
2023-05-31 |
0.4 |
J. Yutzler |
4, 6 |
Open Comment Period |
2023-09-06 |
0.5 |
J. Yutzler |
4, 6 |
Revert #653 |
2023-10-02 |
0.6 |
J. Yutzler |
7 |
Add future work in response to #666 |
2023-10-19 |
0.7 |
J. Yutzler |
4 |
669/670 |
For the complete revision history, see the GitHub repository.