Skip to content

Commit 428ff35

Browse files
lvdbrinklvdbrink
committed
Addresses review @BillSwirrl
fix typo config + rewrite / shorten text about transforming coordinates. Adopted the suggested rewrite as Bill gave it.
1 parent a4ad296 commit 428ff35

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎bp/bpconfig.js‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ var respecConfig = {
252252
"date": "1 November 2016"
253253
},
254254
"OAF2": {
255-
"authors": ["Clements Portele", "Panagiotis (Peter) A. Vretanos"],
255+
"authors": ["Clemens Portele", "Panagiotis (Peter) A. Vretanos"],
256256
"href": "https://docs.ogc.org/is/18-058/18-058.html",
257257
"title": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference",
258258
"date": "2 November 2020",

‎bp/index.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3784,7 +3784,7 @@ <h4 class="subhead">Possible Approach to Implementation</h4>
37843784

37853785
<p>It is generally recommended to limit the number of supported <a>CRS</a>s in a data dissemination endpoint for clarity. Only support <a>CRS</a>s that make sense for the data. If a <a>CRS</a> doesn't cover the data, do not support it.</p>
37863786

3787-
<p>Offering geospatial data in different <a>CRS</a> in practice means the data needs to be transformed from the storage <a>CRS</a> to other supported <a>CRS</a>s. Depending on the storage format, it may or may not be possible to let a fast implementation like a database handle the reprojection. When supporting multiple <a>CRS</a>s through the API, it is recommended to have a mechanism in place to do the conversion. Many programming languages support libraries that can handle this. Since geographic data can be large and complex, it is recommended to cache the converted data for reuse by another client, or the same client at a later time. This eliminates the need of reprojecting the same data more than once. </p>
3787+
<p>Offering geospatial data in different <a>CRS</a> in practice means the data needs to be transformed from the orinigal CRS to other supported CRSs. Database software and libraries for most programming languages are available which can do this. Reprojection can be done in advance and stored, or calculated at the time of a request. If reprojecting on request, since geographic data can be large and complex, it is recommended to cache the converted data to eliminate the need of reprojecting the same data more than once.</p>
37883788

37893789
<p>For Web APIs, CRS support should be offered in conformance to the OGC API building blocks related to CRS [[OAF2]]. These building blocks can be supported in any Web API: </p>
37903790

0 commit comments

Comments
 (0)