- OGC® Standards
- OGC Standards List
- Specification Profiles
- Abstract Specification
- OGC Reference Model
- OGC Schema Updates
- Public Engineering Reports
- TC Policy Directives
- GeoDRM Reference Model
- Best Practices
- Discussion Papers
- Deprecated Documents
- Retired Documents
- Requests (RFP's, RFQ's...)
- White Papers
- Change Requests
- Submit Change Request or Requirement
The OGC Seeks Comments on Candidate GeoPackage Standard
The Open Geospatial Consortium (OGC®) seeks public comments on the current draft of the candidate OGC GeoPackage (GPKG) Standard. The GPKG Standards Working Group (SWG) will consider all submitted comments when they prepare a final draft of the GeoPackage Standard.
The candidate OGC GeoPackage Standard provides an open, non-proprietary, platform-independent SQLite container for distribution and direct use of all kinds of geospatial data, including vector features and tile matrix sets. GeoPackage can be used by mobile device users who require geospatial application services and associated data in disconnected or limited network connectivity environments where open, sharable geospatial data to support their applications is frequently unavailable. GeoPackage supports applications that involve creation of geospatial data products in enterprise computing environments, data product distribution to other computing environments, mobile workforce data capture and updates, and volunteered geographic information.
The GeoPackage container and related GPKG SQLite Extension configuration and API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world. Standard configuration and APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services.
All OGC standards are free and publicly available. Download the candidate GeoPackage Standard below, or check it out on GitHub. Comments are due by 5 September 2013.
Comments can be submitted for a thirty day period ending on the "Close request date" listed above. Comments received will be consolidated and reviewed by OGC members for incorporation into the document. There are three ways to provide input into the candidate standard:
- Edit the document on GitHub: if you are familiar with GitHub, please make your proposed changes directly. Instructions are in the README.md file in that repository.
- Submit an "issue" on GitHub: GitHub offers a simple interface for posting an issue/comment. Just click the green "New Issue" button.
- Submit an issue via email: Comments can be submitted to a dedicated email reflector The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template