Skip to content

Commit 96edf77

Browse files
authored
Update wording in Geospatial spec for CRS (#560)
Document existing CRS usage.
1 parent 96656a5 commit 96edf77

1 file changed

Lines changed: 6 additions & 14 deletions

File tree

Geospatial.md

Lines changed: 6 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,12 @@ locations on Earth.
4444
The default CRS `OGC:CRS84` means that the geospatial features must be stored
4545
in the order of longitude/latitude based on the WGS84 datum.
4646

47-
Custom CRS can be specified by a string value. It is recommended to use an
48-
identifier-based approach like [Spatial reference identifier][srid].
47+
Non-default CRS values are specified by any string that uniquely identifies a coordinate reference system associated with this type.
48+
To maximize interoperability, suggested (but not limited to) formats for CRS are:
49+
* `<projjson>` - A complete CRS definition embedded directly using the [PROJJSON](https://proj.org/en/stable/specifications/projjson.html) specification. Example for `OGC:CRS83`: `{"$schema": "https://proj.org/schemas/v0.7/projjson.schema.json","type": "GeographicCRS","name": "NAD83 (CRS83)","datum": {"type": "GeodeticReferenceFrame"...`
50+
* `<authority>:<code>` - where `<authority>` represents some well known authorities, and `code` is the code used by the authority to identify the CRS. Examples are - `OGC:CRS84`, `OGC:CRS83`, `OGC:CRS27`, `EPSG:4326`, `EPSG:3857`, `IGNF:ATI`. See [https://spatialreference.org/](https://spatialreference.org/) for definitions of coordinate reference systems provided by some well known authorities.
51+
* `srid:<identifier>` - A reference using a [Spatial reference identifier (SRID)](https://en.wikipedia.org/wiki/Spatial_reference_system#Identifier), where <identifier> is the numeric SRID value. For example: `SRID:0`.
52+
* `projjson:<key_name>` - where <key_name> refers to a key within the file key-value metadata, where CRS definition in [PROJJSON](https://proj.org/en/stable/specifications/projjson.html) format is stored.
4953

5054
For geographic CRS, longitudes are bound by [-180, 180] and latitudes are bound
5155
by [-90, 90].
@@ -150,18 +154,6 @@ In addition, the following rules are applied:
150154
[geometry-types]: https://github.com/opengeospatial/geoparquet/blob/v1.1.0/format-specs/geoparquet.md?plain=1#L159
151155
[wkb-integer-code]: https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary
152156

153-
# CRS Customization
154-
155-
CRS is represented as a string value. Writer and reader implementations are
156-
responsible for serializing and deserializing the CRS, respectively.
157-
158-
As a convention to maximize the interoperability, custom CRS values can be
159-
specified by a string of the format `type:identifier`, where `type` is one of
160-
the following values:
161-
162-
* `srid`: [Spatial reference identifier](https://en.wikipedia.org/wiki/Spatial_reference_system#Identifier), `identifier` is the SRID itself.
163-
* `projjson`: [PROJJSON](https://proj.org/en/stable/specifications/projjson.html), `identifier` is the name of a table property or a file property where the projjson string is stored.
164-
165157
# Coordinate axis order
166158

167159
The axis order of the coordinates in WKB and bounding box stored in Parquet

0 commit comments

Comments
 (0)