The following GitHub document has been translated from the Microsoft Word version of the Candidate GeoPackage Standard released for public comment on August 6, 2013. This is an open document, and the OGC invites collaboration and comments directed at the development and enhancement of this candidate standard. Please see the RFC release page for more information, including instructions on how to provide traditional comments on the draft specification to OGC.
The contributor understands that any contributions, if accepted by the OGC Membership, shall be incorporated into the formal OGC GeoPackage standards document and that all copyright and intellectual property shall be vested to the OGC.
This specification describes an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. It specifies a set of conventions for SQLite to store interoperable Features and/or Tiles on a common base. The core document additionally describes optional Metadata, and Schema information to build richer applications. An Extension Mechanism is specified to provide implementors a way to include additional functionality in their GeoPackages, with a number of optional extensions included.
Editor: Paul Daisey
The main specification is in the spec/ folder.
The GeoPackage SWG is accepting public comments and suggested revisions to the specification via GitHub. This is the first time OGC has supported this mechanism for public comment and review. It is preferred that suggested changes to the specification are done by modifying the actual document, using pull requests against this repository. However, you may also make more general comments by submitting an issue on the repository. Click the "exclamation point within a circle" icon on the right side of the window to go to the issue view. For more detailed guidance, see process.md.
If you are new to GitHub then just hit 'edit' on any of the specification pages. This will automatically 'fork' the repository in to your own copy. After editing there you can create a 'pull request' from your fork to submit the work for review and merging. Read Forking a Repo help or email [email protected] if you have questions about this process.
If you are making a more substantial set of changes please create a branch to work on the set. Pull requests stay with the branches they are made on, so if you make more changes based on feedback that can all get pulled in when ready. Note you can create new branches as well as new files completely through the web.
For more on markdown there is a great cheat sheet. And note you can hit 'preview' at any time in edit mode to see if you got things right.