From f65f2ffd8f2e57003be2447c0da0348462ca71ee Mon Sep 17 00:00:00 2001 From: marqh Date: Thu, 27 Dec 2018 15:47:23 +0000 Subject: [PATCH 1/2] prefer epsg-registry for epsg --- spec.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/spec.md b/spec.md index 8f10fc6..dc370c5 100644 --- a/spec.md +++ b/spec.md @@ -371,7 +371,7 @@ Example of a three-dimensional geographic CRS (latitude-longitude-height): ```json { "type": "GeographicCRS", - "id": "http://www.opengis.net/def/crs/EPSG/0/4979" + "id": "https://www.epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::4979" } ``` @@ -383,12 +383,12 @@ Projected CRSs use two coordinates to denote positions on a Cartesian plane, whi If a Coverage conforms to one of the defined [domain types][domain-types] then the coordinate identifier `"x"` is used to denote easting and `"y"` is used for northing. -Example of a projected CRS (here [British National Grid](http://spatialreference.org/ref/epsg/osgb-1936-british-national-grid/)): +Example of a projected CRS (here [British National Grid](https://www.epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::27700)): ```json { "type": "ProjectedCRS", - "id": "http://www.opengis.net/def/crs/EPSG/0/27700" + "id": "https://www.epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::27700" } ``` @@ -403,7 +403,7 @@ Example of a vertical CRS, here representing height above the NAV88 datum: ```json { "type": "VerticalCRS", - "id": "http://www.opengis.net/def/crs/EPSG/0/5703" + "id": "https://www.epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::5703" } ``` @@ -461,7 +461,7 @@ In this specification, only a string-based notation for time values is defined. a client SHOULD interpret those dates in that reduced precision. Example: - +ep ```json { "type": "TemporalRS", @@ -608,7 +608,7 @@ Example of a reference system connection object: "coordinates": ["y","x","z"], "system": { "type": "GeographicCRS", - "id": "http://www.opengis.net/def/crs/EPSG/0/4979" + "id": "https://www.epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::4979" } } ``` @@ -637,7 +637,7 @@ Example of a domain object with [`"Grid"`][domain-types] domain type: "coordinates": ["y","x","z"], "system": { "type": "GeographicCRS", - "id": "http://www.opengis.net/def/crs/EPSG/0/4979" + "id": "https://www.epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::4979" } }] } From 01202c63733102098113f4985b5eb23207bac0a9 Mon Sep 17 00:00:00 2001 From: marqh Date: Thu, 27 Dec 2018 15:48:39 +0000 Subject: [PATCH 2/2] -ep --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index dc370c5..3a041e2 100644 --- a/spec.md +++ b/spec.md @@ -461,7 +461,7 @@ In this specification, only a string-based notation for time values is defined. a client SHOULD interpret those dates in that reduced precision. Example: -ep + ```json { "type": "TemporalRS",