![formato iso to xbe converter formato iso to xbe converter](https://img.youtube.com/vi/veWawhsvuS0/mqdefault.jpg)
įor spatial reference content including but not limited to tiles and features, each row in contents must reference a coordinate reference system stored in the gpkg_spatial_ref_sys table. min_x, min_y, max_x, and max_y: the spatial extents of the content.last_change: the informational date of last change, in ISO 8601 format.identifier and description: human-readable text.table_name: the actual name of the user-defined data table.GeoPackages consist of two mandatory metadata tables: gpkg_contentsĪ table of contents for a GeoPackage. These tables can be either user-defined or metadata tables. The GeoPackages contain a number of tables, like other relational databases. This makes it ideal for mobile applications in off-line mode and fast sharing on cloud storage or USB storage devices, etc. The purpose of designing a GeoPackage was to make a lightweight database as much possible and include it in a ready-to-use single file. You can extend a GeoPackage by using the extension rules as defined in clause 2.3 of the standard. GPKG file formatĪ GeoPackage is made up as an extended SQLite 3 database file a standard defines a set of rules (required conventions) for: Various governments, commercial, and open source organizations widely support the GeoPackage. It was published in 2014 defined by the OGC (Open Geospatial Consortium) on the behalf of the US military. gpkg extension consists of a geographic information system implemented as a SQLite database container containing data and metadata tables with typical definitions, format limitations, integrity assertions and content constraints.