[geos-commits] [SCM] GEOS branch main updated. c0d97ffcdfd2f5f175053ff1aa9b44df6baf49be

[git at osgeo.org]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GEOS".

The branch, main has been updated
       via  c0d97ffcdfd2f5f175053ff1aa9b44df6baf49be (commit)
      from  47435e4f5d4163d01e77116b289de5b5c57778c6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c0d97ffcdfd2f5f175053ff1aa9b44df6baf49be
Author: Daniel Baston <dbaston at gmail.com>
Date:   Thu Oct 23 13:26:44 2025 -0400

    FAQ: Remove outdated content about M ordinates (#1318)

diff --git a/web/content/usage/faq/index.md b/web/content/usage/faq/index.md
index 5481744af..5ecc2fcd4 100644
--- a/web/content/usage/faq/index.md
+++ b/web/content/usage/faq/index.md
@@ -37,11 +37,6 @@ One way to perform geodetic computations is to project data to an appropriate pl
 using a transformation library such as [PROJ](https://proj.org/).
 The desired geometric operations can be computed in planar space, and reprojected back to geodetic.
 
-### Does GEOS support coordinates with measures (M)?
-
-No, the GEOS coordinate model only supports X,Y and Z ordinates.
-We hope to add support for M, and also a more efficient XY coordinate storage representation.
-
 ## Robustness
 
 ### Why does `GEOSIntersects(GEOSIntersection(A, B), A) == false`?
@@ -50,7 +45,7 @@ GEOS represents geometry coordinates using IEEE-754 double-precision floating po
 This is a finite representation, whereas the implicit lines between vertices have infinite precision.  In general it is highly unlikely that a coordinate computed via an arithmetic operation
 (such as a line intersection) is reported by an `intersects` test as lying exactly on the (theoretical) lines.
 
-For example, the diagram below shows how the computed intersection point of two lines in general does not lie exactly on either line (scale exaggerrated for clarity):
+For example, the diagram below shows how the computed intersection point of two lines in general does not lie exactly on either line (scale exaggerated for clarity):
 
 ![GEOS computed intersection point for two lines](geos-line-intersect-precision.png)
 
@@ -61,6 +56,6 @@ As explained in the previous question, GEOS uses finite-precision floating point
 because in the general case it is not possible to represent points along a line exactly using finite-precision numbers.
 
 The diagram below shows how points interpolated along a line rarely lie exactly on the line
-(scale exaggerrated for clarity):
+(scale exaggerated for clarity):
 
 ![GEOS computed points interpolated along line](geos-line-interpolated-precision.png)

-----------------------------------------------------------------------

Summary of changes:
 web/content/usage/faq/index.md | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)


hooks/post-receive
-- 
GEOS