Brian Osborn

I wrote a [Coordinate Reference Systems library](https://github.com/ngageoint/coordinate-reference-systems-java) to parse CRS WKT 1 and 2. [Recently added](https://github.com/ngageoint/coordinate-reference-systems-java/releases/tag/1.1.0) a CRS to PROJ / PROJ.4 parser as well. Example to use with this...

The shadow view w/ triggers approach as the new "standard" specification could result in a fair amount of headaches. The above proposal, however, is to update the base specification gpkg_contents...

Understood, however this is a very special case due to the rowid alias already existing as explained above.

> The Related Tables Extension requires integer ids for relationships. The NGA Contents Id Extension is a work around to this issue. The only way to foreign key to a...

Any extension that wants to relate data on a Contents wide level in addition to a Contents data row level nature. The Metadata Extension suffers the same issue as the...

> The Metadata Extension suffers the same issue As in the foreign key is still to a String table_name value and not an integer. This seems true and confirmed by...

We can move past the Metadata Extension as that went off topic. There is nothing wrong with it. You had mentioned it, and I was simply pointing out that it...

Sounds good. For number 2, take a look at our Contents Id extension in case OGC would like to adopt it as a solution. It does nothing more than associate...

Yes, that would be an acceptable solution as well. I think the SWG's goal is to try and avoid all new columns (from [comment above](https://github.com/opengeospatial/geopackage/issues/516#issuecomment-624798602) and #230), so I'm not...

Just an alternate option to consider... Update the specification with new columns and provide an upgrade script between each GeoPackage version (as needed). Optionally used by implementations to upgrade GeoPackages....