Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should relationship mapping tables be present in gpkg_contents? #679

Open
nyalldawson opened this issue Feb 20, 2024 · 1 comment
Open

Comments

@nyalldawson
Copy link

This relates to discussion in OSGeo/gdal#9258 . Currently gdal does not write the mapping tables to gpkg_contents, and this seems to be compliant with the extensions specifications.

But is this intentional? By omitting them from gpkg_contents there's a risk that a client wont know to also check for tables in gpkgext_relations, and consequently refuse to open the mapping table (as current gdal versions fail to do).

Is the intentional that a client should scan for available tables in both gpkg_contents and gpkgext_relations?

@jyutzler
Copy link
Contributor

The expected operation is for the client to scan gpkg_extensions and use that as a guide for what secondary tables to open. When using the Related Tables Extension, a row for gpkgext_relations is added to gpkg_extensions as per https://opengeospatial.github.io/e-learning/geopackage/text/extensions/related_tables.html#id2 or https://docs.ogc.org/is/18-000/18-000.html#gpkg_extensions_records.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants