This is an automated email from the ASF dual-hosted git repository.

desruisseaux pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/sis-site.git

commit e38f878b0b425aad5304cd08174e417877b90b33
Author: Martin Desruisseaux <martin.desruisse...@geomatys.com>
AuthorDate: Fri May 10 11:33:19 2024 +0200

    Replace "geodetic datum" by "geodetic reference frame" in text.
---
 content/command-line.md                                      |  2 +-
 content/developer-guide/annexes/geoapi/ReduceDependency.html |  2 +-
 content/developer-guide/referencing/ComponentsOfCRS.html     |  2 +-
 static/examples/coordinates/AmericanCities.csv               | 10 +++++-----
 static/examples/coordinates/CanadianCities.csv               | 10 +++++-----
 5 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/content/command-line.md b/content/command-line.md
index 13e76ce4..6e3da24a 100644
--- a/content/command-line.md
+++ b/content/command-line.md
@@ -100,7 +100,7 @@ The reason is that command output may be targeted to a 
client, while the error m
 
 The following examples first show how to get a Coordinate Reference System 
(CRS) from different kinds of definitions.
 {{% CRS %}} contain necessary information for locating points on Earth.
-Those information include the geodetic datum, the map projection (if any), the 
axes and their units of measurement.
+Those information include the geodetic reference frame, the map projection (if 
any), the axes and their units of measurement.
 When two such {{% CRS %}} are known (the _source_ and the _target_), it is 
possible to convert or transform points between those {{% CRS %}}.
 However the coordinate operation depends not only on the source and target {{% 
CRS %}}, but also on the _area of interest_ as shown
 by the example transforming city coordinates in USA and in Canada.
diff --git a/content/developer-guide/annexes/geoapi/ReduceDependency.html 
b/content/developer-guide/annexes/geoapi/ReduceDependency.html
index ed14fe8d..b72101d3 100644
--- a/content/developer-guide/annexes/geoapi/ReduceDependency.html
+++ b/content/developer-guide/annexes/geoapi/ReduceDependency.html
@@ -148,7 +148,7 @@ public class MyApplication {
         <tr>
           <td><code>GeodeticDatum</code></td>
           <td><code>Ellipsoid</code></td>
-          <td>Description of the geodetic datum.</td>
+          <td>Description of the geodetic reference frame.</td>
         </tr>
         <tr>
           <td><code>CoordinateOperation</code></td>
diff --git a/content/developer-guide/referencing/ComponentsOfCRS.html 
b/content/developer-guide/referencing/ComponentsOfCRS.html
index e9141f01..2cb5cfb3 100644
--- a/content/developer-guide/referencing/ComponentsOfCRS.html
+++ b/content/developer-guide/referencing/ComponentsOfCRS.html
@@ -153,7 +153,7 @@ RangeMeaning  atEnds       = secondAxis.getRangeMeaning();  
// For a longitude a
 
 
 
-      <h3 id="GeodeticDatum">Geodetic datum</h3>
+      <h3 id="GeodeticDatum">Geodetic reference frame</h3>
       <p>
         Since the real topographic surface is difficult to represent 
mathematically, it is not used directly.
         A slightly more convenient surface is the geoid,
diff --git a/static/examples/coordinates/AmericanCities.csv 
b/static/examples/coordinates/AmericanCities.csv
index 9f701676..636753fd 100644
--- a/static/examples/coordinates/AmericanCities.csv
+++ b/static/examples/coordinates/AmericanCities.csv
@@ -1,9 +1,9 @@
 #
-# Coordinates of some cities in USA. The coordinates are given
-# with only 3 significant digits, which implies an uncertainty
-# of more than 100 metres.  With such uncertainty, it does not
-# matter if the geodetic datum is WGS84, NAD83 or NAD27  since
-# the error is greater than the difference between those datums.
+# Coordinates of some cities in USA. The coordinates are given with only 3
+# significant digits, which implies an uncertainty of more than 100 metres.
+# With such uncertainty, it does not matter if the geodetic reference frame
+# is WGS84, NAD83 or NAD27 because the error is greater than the difference
+# between those datums.
 #
 # Axis order is latitude first, then longitude. Units are degrees.
 #
diff --git a/static/examples/coordinates/CanadianCities.csv 
b/static/examples/coordinates/CanadianCities.csv
index a4c255ac..0f5647a3 100644
--- a/static/examples/coordinates/CanadianCities.csv
+++ b/static/examples/coordinates/CanadianCities.csv
@@ -1,9 +1,9 @@
 #
-# Coordinates of some cities in Canada. The coordinates are given
-# with only 3 significant digits, which implies an uncertainty of
-# more than 100 metres. With such uncertainty, it does not matter
-# if the geodetic datum is WGS84, NAD83 or NAD27 since the error
-# is greater than the difference between those datums.
+# Coordinates of some cities in Canada. The coordinates are given with only 3
+# significant digits, which implies an uncertainty of more than 100 metres.
+# With such uncertainty, it does not matter if the geodetic reference frame
+# is WGS84, NAD83 or NAD27 because the error is greater than the difference
+# between those datums.
 #
 # Axis order is latitude first, then longitude. Units are degrees.
 #

Reply via email to