The "Extension Table Record" states that gpkg_2D_gridded_coverage_ancillary and gpkg_2D_gridded_tile_ancillary rows need to be added to the gpkg_extensions table.
For tables that are compliant with the gpkg_elevation_tiles_tiff extension, those tables need to be identified in the gpkg_extensions table. However for elevations using PNG, there is currently no requirement to add those to the gpkg_extension table. That is inconsistent - assuming it is PNG because the author of the GeoPackage didn't list it in gpkg_extension is risky.
Suggest adding a row to the Extension Table Record that looks like:
table_name: 'name of actual tile pyramid user data table containing unsigned integer data'
column_name: tile_data
extension_name: gpkg_elevation_tiles
definition: TBD
scope: read_write
The "Extension Table Record" states that
gpkg_2D_gridded_coverage_ancillary
andgpkg_2D_gridded_tile_ancillary
rows need to be added to thegpkg_extensions
table.For tables that are compliant with the
gpkg_elevation_tiles_tiff
extension, those tables need to be identified in thegpkg_extensions
table. However for elevations using PNG, there is currently no requirement to add those to thegpkg_extension
table. That is inconsistent - assuming it is PNG because the author of the GeoPackage didn't list it ingpkg_extension
is risky.Suggest adding a row to the Extension Table Record that looks like: table_name: 'name of actual tile pyramid user data table containing unsigned integer data' column_name: tile_data extension_name: gpkg_elevation_tiles definition: TBD scope: read_write