[Feature request] Support non-spatial tables in Geopackages according to the specification #515
Description
Describe the feature
Add non-spatial tables to gpkg_contents according to the Geopackage specification (2.4 Attributes and 1.1.2.1.2. Table Data Values).
Differences compared to spatial tables:
data_type="attributes"srs_id=0
Example Use
This feature request is important for end users handling Geopackage data in GUI applications.
Here is a quick sketch for the additional code needed.
geopackage.after_create adds an entry to gpkg_contents for every non-spatial table:
def after_create(table, bind, **kw):
# ... previous code
is_spatial = any(
_check_spatial_type(col.type, Geometry, dialect) for col in table.columns
)
if not is_spatial:
bind.execute(
text(
"""INSERT INTO gpkg_contents
VALUES (
:table_name,
'attributes',
:table_name,
"",
strftime('%Y-%m-%dT%H:%M:%fZ', CURRENT_TIMESTAMP),
NULL,
NULL,
NULL,
NULL,
0
);"""
).bindparams(
table_name=table.name,
)
)
# ... remaining codegeopackage.before_drop removes the entry from gpkg_contents for every non-spatial table:
def after_create(table, bind, **kw):
# ... previous code
if len(gis_cols) == 0:
bind.execute(
text(
"""DELETE FROM gpkg_contents
WHERE LOWER(table_name) = LOWER(:table_name);"""
).bindparams(table_name=table.name)
)
# ... remaining codeUse cases
All tables in a Geopackage should be listed in the table gpkg_contents to make sure they are discoverable by all applications.
QGIS does not properly recognize non-spatial tables that are not listed in gpkg_contents. By adding them to gpkg_contents they work as expected in QGIS.