![]() GeoPackages that comply with the requirements in the standard and do not implement vendor-specific extensions are interoperable across all enterprise and personal computing environments. ![]() This means that the data in a GeoPackage can be accessed and updated in a "native" storage format without intermediate format translations. Since a GeoPackage is a database container, it supports direct use. These capabilities are built on a common base and the extension mechanism provides implementors a way to include additional functionality in their GeoPackages. The required and supported content of a GeoPackage is entirely defined in the standard. The GeoPackage standard defines the schema for a GeoPackage, including table definitions, integrity assertions, format limitations, and content constraints. To be clear, a GeoPackage is the SQLite container and the GeoPackage Encoding Standard governs the rules and requirements of content stored in a GeoPackage container. tile matrix sets of imagery and raster maps at various scales. ![]() The GeoPackage Encoding Standard describes a set of conventions for storing the following within an SQLite database: GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. An Open Format for Geospatial Information
0 Comments
Leave a Reply. |