diff options
| author | Even Rouault <even.rouault@spatialys.com> | 2021-02-10 18:53:27 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-02-10 18:53:27 +0100 |
| commit | 36d8691b20bb0caeb87be262a9b1f0d088ccffd0 (patch) | |
| tree | 30c9e9473616d313e49eb5fc4deea51b6c0e39af | |
| parent | a7f6b407446b35a50b5601650aed993c706fe8ee (diff) | |
| parent | 3ea7abc133148d87a9fe132e7c7a55d3762df6db (diff) | |
| download | PROJ-36d8691b20bb0caeb87be262a9b1f0d088ccffd0.tar.gz PROJ-36d8691b20bb0caeb87be262a9b1f0d088ccffd0.zip | |
Merge pull request #2522 from rouault/update_operations_computation
operations_computation.rst: update 'Filtering and sorting of coordinate operations' section
| -rw-r--r-- | docs/source/operations/operations_computation.rst | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/source/operations/operations_computation.rst b/docs/source/operations/operations_computation.rst index af177f6c..5c003ed2 100644 --- a/docs/source/operations/operations_computation.rst +++ b/docs/source/operations/operations_computation.rst @@ -5,7 +5,7 @@ Computation of coordinate operations between two CRS ================================================================================ :Author: Even Rouault -:Last Updated: 2020-01-02 +:Last Updated: 2021-02-10 Introduction ------------ @@ -50,7 +50,7 @@ geographic CRS: The algorithm involves many cases, so we will progress in the explanation from the most simple case to more complex ones. We document here the working of this -algorithm as implemented in PROJ 6.3.0. +algorithm as implemented in PROJ 8.0.0. The results of some examples might also be quite sensitive to the content of the PROJ database and the PROJ version used. @@ -149,11 +149,12 @@ performed in the order they are listed below: 10. in case of same accuracy, consider as more relevant an operation that does not use grids (operations that use only parameters will be faster) 11. consider as more relevant an operation that involves less transformation steps + (transformation steps considered are the ones listed in the WKT output, not PROJ pipeline steps) 12. and for completeness, if two operations are comparable given all the above criteria, consider as more relevant the one which has the shorter name, and if they - have the same length, consider as more relevant the one whose name comes first in - lexicographic order (obviously completely arbitrary, but a sorting - algorithm must be able to compare all entries) + have the same length, consider as more relevant the one whose name comes last in + lexicographic order (e.g. "FOO to BAR (3)" will have higher precedence than + "FOO to BAR (2)") Geodetic/geographic CRS to Geodetic/geographic CRS, without known identifiers ----------------------------------------------------------------------------- |