Geopackage Standards
Geopackage Standards
The OGC GeoPackage Standards Working Group charter is being amended. The OGC members listed
below have proposed this amendment per the purpose clause of the SWG charter amendment below.
The SWG charter amendment provided in this document meets the requirements of the OGC TC Policies
and Procedures. The SWG name, statement of purpose, scope, list of deliverables, audience, and language
specified in the proposal will constitute the SWG's official charter. Technical discussions may occur no
sooner than the SWG's first meeting.
This SWG will operate under the OGC 2007 IPR Policy. The eligibility requirements for becoming a
participant in the SWG at the first meeting (see details below) are that:
Of course, participants also may join the SWG at any time. The OGC and the SWG welcomes all interested
parties.
Non-OGC members who wish to participate may contact us about joining the OGC. In addition, the public
may access some of the resources maintained for each SWG: the SWG public description, the SWG
Charter, Change Requests, and public comments, which will be linked from the SWG’s page.
Please feel free to forward this announcement to any other appropriate lists. The OGC is an open standards
organization; we encourage your feedback.
1. GeoPackage
This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for
direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various
scales. Direct use means the ability to access and update data in a “native” storage format without
intermediate format translations in an environment (e.g. through an API) that guarantees data model and
data set integrity and identical access and update results in response to identical requests from different
client applications. GeoPackages are interoperable across all enterprise and personal computing
environments, and are particularly useful on mobile devices like cell phones and tablets in communications
environments with limited connectivity and bandwidth.
4. Scope of Work
The SWG has received and will continue to accept notices of errors in and omissions from the GeoPackage
Encoding Standard. The SWG will evaluate these notices, draft corrections and additions to correct the
notice items, and make edits to the standard based on decisions of the SWG membership. This task will
begin as soon as the amended charter is approved. A corrigendum revision is scheduled to be completed by
the end of September 2014.
The SWG will collect all outstanding Change Request Proposals , evaluate each of the proposals, and make
edits to the standard based on CRPs and related decisions of the SWG membership. This task will begin as
soon as CRPs are approved by the TC Chair and received by the SWG.
The SWG, at their discretion, may ask the membership for any additional change requests that have not
been previously submitted, including potential future work items identified in the version 1.0.0 Standard.
The SWG will address potential future work items identified in the version 1.0.0 Standard as requested in a
CRP. (Informal requests have been received for an extension to encode elevation data in TIFF format.)
The SWG will develop a GeoPackage Implementation Guide Best Practices Document.
The SWG will collaborate with the Simple Features SWG on additional geometry types and changes to
Well Known Text (WKT) / Well Known Binary (WKB) geometry encodings.
The SWG will develop an OWS Context Document Guide for GeoPackage Best Practices Document in
collaboration with the OWS Context SWG. Both SWGs voted to perform this task and have started
working on it together.
The SWG will collaborate with other SWGS to extend their standards to use GeoPackage as a supported
exchange format, and to make any changes to the GeoPackage Encoding Standard that may be required to
enable these new uses.
The SWG will produce a CITE TEAM Engine TestNG ETS for the GeoPackage Encoding Standard and its
SQLite Configuration and SQLite Extension. A beta version of the ETS is scheduled to be completed by
the end of September 2014.
The SWG will produce one or more revisions of the GeoPackage Encoding Standard for consideration by
the OGC membership for adoption. The first such revision is scheduled to be completed by the end of
March 2015.
OGC Simple Features Standards may be extended to include and provide WKT/WKB encoding for several
GeoPackage optional geometry types .
The GeoPackage Encoding Standard relationship to the OWS Context Document Abstract and
Implementation Encoding Standards will be described in a Best Practices Document developed jointly by
both SWGs. Change Request Proposals for the GeoPackage and OWC Standards may be created to enable
the practices described in that document.
Other OGC Standards including but not limited to WFS, WMTS, WCS, WPS, and CSW, may be extended
to use GeoPackage as a supported exchange format. Changes to the GeoPackage Encoding Standard may
be required to enable these new uses.
5. Description of Deliverables
7. Anticipated Participants
The primary anticipated participants in this SWG include developers, vendors, and users of Geospatial
Applications, Geospatial Web Services, and Geospatial Data Stores. Other anticipated participants
include participants in current and past SWGs for OWS specifications that may be subject of future Change
Requests to harmonize them with the GeoPackage specification (e.g. OWS Common and OWS Context) or
to use GeoPackages as an exchange and storage format.
The work of the SWG will be carried out primarily by email and conference calls, possibly every 1-2
weeks, probably continuing the existing schedule of Tuesdays at 11:00 AM Eastern, with face-to-face
meetings perhaps at each of the OGC TC meetings.
e. Convener(s)
Kevin Backe (U.S. Army Geospatial Center)