![]() ![]() table_name: the actual name of the user-defined data table (this is also the primary key for this table).The gpkg_contents table is the table of contents for a GeoPackage. The name of the user-defined data table is the primary key for gpkg_contents and generally is a foreign key for content-specific metadata tables. The presence of other metadata tables is dictated by the content being stored (see Content Types). GeoPackages contain two mandatory metadata tables, gpkg_contents and gpkg_spatial_ref_sys. These tables fall into two categories, user-defined data tables and metadata tables. Like other relational databases, GeoPackages contain a number of tables. For versions 1.2 and later, this returns an integer representing the version number in the form MMmmPP (MM = major version, mm = minor version, PP = patch).1196444487 (the 32-bit integer value of 0x47504B47 or GPKG in ASCII) for GPKG 1.2 and greater.These statements can be executed just like any other SQL statement and where relevant, they return a result set. SQLite uses pragma statements to implement non-standard SQL functions. Using a direct SQL interface such as DB Browser is the easiest way to check a GeoPackage version. Note: For maximum interoperability, start your database identifiers (table names, column names, etc.) with a lowercase character and only use lowercase characters, numbers 0-9, and underscores ( _). The post also provides information on how to add the SpatiaLite extension to enable further spatial analysis in SQLite. ![]() This blog post (The section titled “Creating a GeoPackage with Reference Data”) provides an example that describes steps for creating a GeoPackage using ogr2ogr.
0 Comments
Leave a Reply. |