[Geopackage] gpkg_contents when type is not 'feature' or 'tiles'
Pepijn Van Eeckhoudt
pepijn.vaneeckhoudt at luciad.com
Fri Nov 7 10:45:37 EST 2014
There was a very similar question on the mailing list some time ago
(look for thread 'Aspatial Tables with Metadata').
Two strategies were proposed then:
- Register the table as 'features' and apply a 'no geometry' extension to it
- Register the table as 'aspatial'
I'm not sure which approach the person asking the question end up taking.
On 06/11/14 12:14, Patrick van Dijk wrote:
> I'd like to register my alpha only table (e.g. no geometry field)
> table in gpkg_contents as I can then store an identifier
> and description for the table and I can also add additional field
> information in gpkg_data_columns.
> So my suggestion is to create a gpkg_contents record with its
> data_type set to 'alpha' (instead of feature).
> Req 13 explains the gpkg_contents table for field data_type.
> Type of data stored in the table:.
> “features” per clause 220.127.116.11.1,
> “tiles” per clause 18.104.22.168.1, or
> an implementer-defined value
> for other data tables in an
> Extended GeoPackage.
> So I guess, what I want to do is fine.
> Am I right?
Luciad Email Signature *Pepijn Van Eeckhoudt*
Senior Software Architect
*LUCIAD* <http://www.luciad.com/> CONNECT • VISUALIZE • ANALYZE • ACT
pepijn.vaneeckhoudt at luciad.com <mailto:firstname.lastname at luciad.com> •
T +32 16 23 95 91
Follow us on LinkedIn <https://www.linkedin.com/company/luciad>or
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Geopackage