The Open Geospatial Consortium (OGC) on the GeoPackage Well Known Text (WKT) for Coordinate Reference Systems (CRS) Extension candidate standard.
The candidate standard revises and replaces the GeoPackage WKT for Coordinate Reference Systems Extension that is currently published as Annex F.10 of GeoPackage Encoding Standard 1.3.0. The candidate extension defines how to encode Coordinate Reference Systems (CRS) in GeoPackage using the OGC CRS WKT2 standard. This new revision adds coordinate epochs to the encoding of coordinate reference systems in a GeoPackage to support dynamic CRSs.
In a dynamic CRS, coordinates of a point on the surface of the Earth may change with time. To be unambiguous, the coordinates must always be qualified with the epoch at which they are valid. In 2021, the GeoPackage SWG approved a change adding coordinate epochs to gpkg_spatial_ref_sys. Because this was the only substantive change to the GeoPackage Encoding Standard being considered at the time, the decision was made to split this extension into a separate document so that it could be considered separately.
GeoPackage is an open, platform-independent, portable, self-describing, compact format for transferring geospatial information. The core (unextended) GeoPackage Encoding Standard supports the older OGC CRS WKT standard. Through this extension, both encodings may be used. However, use of the newer encoding is strongly encouraged. GeoPackage clients are expected to use the newer encoding if both encodings are present.
Comments can be submitted to a dedicated email reflector 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. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) 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