NSG Geopackage 2.1, NSG Requirement 19

[ayoumans]

NSG requirement 19 states that: Data validity SHALL be assessed against data value constraints specified in Table 26 below using a test suite. Data validity MAY be enforced by SQL triggers.

NSG Req 24: The (min_x, max_x, min_y, max_y) values in the gpkg_contents table SHALL be used to describe an informative bounding rectangle of all tiles in the tile pyramid data table per OGC GeoPackage Clause 1.1.3.1.1

Please note that this has been brought up during the NSG Plugfest and also to the OGC Geopackage working group (Below is the link to this issue in the OGC SWG).

Currently, the OGC compliance test does not check the bounding box requirements for min_X, min_Y, max_X and max_Y in the gpkg_contents table as outlined in the NSG requirement #19. In the OGC specification, the bounding box is informative only and applications have the choice on if this is the default view. However, there is no requirements that this is the exact bounding box or the minimum bounding box of the content for the OGC standard. Later, in NSG Requirement #23 and #24, it says that the min and max values should be the full extent and references 1.1.3.1.1; however, the OGC spec does not say this.

https://github.com/opengeospatial/geopackage/issues/443 This is the link for more information on the OGC GitHub page.