This change creates two new requirements, R146 and R147, that requires SRS IDs to be consistent between gpkg_contents and the two dependent tables, gpkg_geometry_columns and gpkg_tile_matrix_set. In previous versions, this was unspecified. This ambiguity creates a potential interoperability issue because client software could confuse the values if they are different. This change also includes an explanatory note in section 1.1.3.1.2 and new abstract tests in Annex A.
This change adds two new requirements, R150 and R151, to specify the rules for primary keys or primary-key like columns in user-defined features and attributes tables, respectively. While user-defined tables should have primary keys in general, the concept of primary keys does not exist in SQLite for views. These new requirements establish a new option for implementers. User-defined components that lack primary keys (presumably because they are views) must have a primary-key-like column (containing unique integers) as the first column. In previous GeoPackage versions, how to encode a view was unclear. This change also includes an explanatory note with a similar message for tiles views.
This change eliminates the Trigger Definition SQL from the Metadata Extension. As long as those triggers are there, it is not possible to add new scopes to a GeoPackage. Trigger constraints were eliminated from the rest of the encoding standard before reaching v1.0. Why these particular trigger constraints remained is unclear. The rigidity imposed by these constraints is a clear violation of Requirement 25 of the OGC’s Standard for Modular Specifications that governs this SWG. Eliminating these triggers would allow logically-valid extension of the metadata scope list as called for by Requirement 25.
This change also adds a new metadata scope for "style". The list of metadata scopes that is currently in Table 21 is arbitrary and is clearly not limited to the scopes from ISO19115. Since OGC Testbed-15 identified a need for a new scope, it has been added.
The original schema extension stated that schemas are for features layers.
This change loosens the restriction so that a schema may apply to attributes or extensions.
This required a change to R104 which originally specified that the "table_name" from gpkg_data_columns must have a corresponding row in gpkg_contents.
Since some extension tables are described in gpkg_extensions, the requirement was loosened so that the corresponding row must be in either table.