Merge pull request #433 from jyutzler/i432

I432

Author: jyutzler

spec/1_base.adoc

@@ -224,10 +224,10 @@ A GeoPackage file SHALL include a `gpkg_contents` table per table <<gpkg_content
 |`identifier` |TEXT |A human-readable identifier (e.g. short name) for the table_name content |yes | |UNIQUE
 |`description` |TEXT |A human-readable description for the table_name content |yes |'' |
 |`last_change` |DATETIME |timestamp of last change to content, in ISO 8601 format|no |`strftime('%Y-%m-%dT%H:%M:%fZ', 'now')` |
-|`min_x` |DOUBLE |Bounding box minimum easting or longitude for all content in table_name |yes | |
-|`min_y` |DOUBLE |Bounding box minimum northing or latitude for all content in table_name |yes | |
-|`max_x` |DOUBLE |Bounding box maximum easting or longitude for all content in table_name |yes | |
-|`max_y` |DOUBLE |Bounding box maximum northing or latitude for all content in table_name |yes | |
+|`min_x` |DOUBLE |Bounding box minimum easting or longitude for all content in table_name. If tiles, this is informational and the tile matrix set should be used for calculating tile coordinates. |yes | |
+|`min_y` |DOUBLE |Bounding box minimum northing or latitude for all content in table_name. If tiles, this is informational and the tile matrix set should be used for calculating tile coordinates. |yes | |
+|`max_x` |DOUBLE |Bounding box maximum easting or longitude for all content in table_name. If tiles, this is informational and the tile matrix set should be used for calculating tile coordinates.|yes | |
+|`max_y` |DOUBLE |Bounding box maximum northing or latitude for all content in table_name. If tiles, this is informational and the tile matrix set should be used for calculating tile coordinates.|yes | |
 |`srs_id` |INTEGER |Spatial Reference System ID: `gpkg_spatial_ref_sys.srs_id`; when `data_type` is features, SHALL also match `gpkg_geometry_columns.srs_id`; When data_type is tiles, SHALL also match `gpkg_tile_matrix_set.srs_id` |yes | |FK
 |=======================================================================
 

spec/annexes/background.adoc

@@ -147,6 +147,7 @@ All questions regarding this document should be directed to the editor or the co
 |Scott Clark |LNM Solutions |scott.clark<at>lmnsolutions.com
 |David Cray |U.S. Army Geospatial Center GASD |David.Cray<at>usace.army.mil
 |Paul Daisey |Image Matters |pauld<at>imagemattersllc.com
+|Rich Fecher |Radiant Solutions |richard.fecher<at>radiantsolutions.com
 |Nathan P. Frantz |U.S. Army Geospatial Center ERDC |Nathan.P.Frantz<at>usace.army.mil
 |Alessandro Furieri |Spatialite |a.furieri<at>lqt.it
 |Randy Gladish |Image Matters |randyg<at>imagemattersllc.com
@@ -206,7 +207,7 @@ All questions regarding this document should be directed to the editor or the co
 |2018-04-09| R15| Jeff Yutzler| Annex F.3| Removing erroneous part of trigger https://github.com/opengeospatial/geopackage/issues/414
 |2018-04-19| R15| Jeff Yutzler| Annex F.8| Updating Table 19 to fix typos and improve clarity https://github.com/opengeospatial/geopackage/pull/427
 |2018-05-01| R15| Jeff Yutzler| Annexes F.8, F.9, F.10| Updating R140, R141, and R145 to indicate required rows and column values https://github.com/opengeospatial/geopackage/issue/426
-
+|2018-05-16| R15| Rich Fecher| 1.1.3.1.1| Clarifying use of extents in gpkg_contents with tiles content https://github.com/opengeospatial/geopackage/issue/426
 |=======================================================================
 
 === Changes to the OGC® Abstract Specification