Skip to content

Make non-spatial tables discoverable #221

Closed
@jyutzler

Description

@jyutzler

Reference: http://ogc.standardstracker.org/show_request.cgi?id=380

The request calls for supporting non-spatial tables in a GeoPackage . An Extended GeoPackage includes elements that are outside the GeoPackage Core Specification. This is perfectly appropriate, and in many cases encouraged. There is nothing keeping the GeoPackage producer from adding additional tables (whatever the reason) and calling the output file an Extended GeoPackage.

The real issue is discoverability. Some applications do not know how to find these tables inside a GeoPackage. It may be possible for the user to open them manually, but that is unreasonable if there are a large number of tables. A better solution would be to make those tables discoverable.

A simple extension such as the following would support this.

gpkg_extensions column value
table_name (actual table name)
column_name NULL
extension_name gpkg_non_spatial
definition TBD
scope read-write

If desired, this extension could also work with the Schema Extension.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions