GEO_POINT() accepts elevation but z coordinate is ignored in geo functions (#741)

Co-authored-by: Paula Mihu <97217318+nerpaula@users.noreply.github.com>

Author: Simran-B

site/content/arangodb/3.11/aql/functions/geo.md

@@ -615,6 +615,21 @@ support the VelocyPack format. The cluster replication has been changed to use
 VelocyPack instead of JSON to avoid unnecessary conversions and avoiding any
 risk of deviations due to the serialization.
 
+## Optional elevation for GeoJSON Points
+
+<small>Introduced in: v3.11.14-2</small>
+
+GeoJSON Point may now have three coordinates: `[longitude, latitude, elevation]`.
+However, ArangoDB does not take any elevation into account in geo-spatial
+calculations.
+
+Points with an elevation do no longer fail the validation in the `GEO_POLYGON()`
+and `GEO_MULTIPOLYGON()` functions. Moreover, GeoJSON with three coordinates is
+now indexed by geo indexes and thus also matched by geo-spatial queries, which
+means you may find more results than before.
+
+Also see [Geo-spatial functions in AQL](../../aql/functions/geo.md).
+
 ## JavaScript API
 
 ### Database creation

site/content/arangodb/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md

@@ -1402,6 +1402,24 @@ connections. Some memory is pre-allocated at startup for higher efficiency. If t
 `--server.statistics` startup option is set to `false`, then no memory will be
 allocated for connection and request statistics.
 
+### Optional elevation for GeoJSON Points
+
+<small>Introduced in: v3.11.14-2</small>
+
+The `GEO_POINT()` function now accepts an optional third argument to create a
+GeoJSON Point with three coordinates: `[longitude, latitude, elevation]`.
+
+GeoJSON Points may now have three coordinates in general.
+However, ArangoDB does not take any elevation into account in geo-spatial
+calculations.
+
+Points with an elevation do no longer fail the validation in the `GEO_POLYGON()`
+and `GEO_MULTIPOLYGON()` functions. Moreover, GeoJSON with three coordinates is
+now indexed by geo indexes and thus also matched by geo-spatial queries, which
+means you may find more results than before.
+
+Also see [Geo-spatial functions in AQL](../../aql/functions/geo.md).
+
 ## Client tools
 
 ### arangodump

site/content/arangodb/3.11/release-notes/version-3.11/whats-new-in-3-11.md

@@ -615,6 +615,21 @@ support the VelocyPack format. The cluster replication has been changed to use
 VelocyPack instead of JSON to avoid unnecessary conversions and avoiding any
 risk of deviations due to the serialization.
 
+## Optional elevation for GeoJSON Points
+
+<small>Introduced in: v3.11.14-2</small>
+
+GeoJSON Point may now have three coordinates: `[longitude, latitude, elevation]`.
+However, ArangoDB does not take any elevation into account in geo-spatial
+calculations.
+
+Points with an elevation do no longer fail the validation in the `GEO_POLYGON()`
+and `GEO_MULTIPOLYGON()` functions. Moreover, GeoJSON with three coordinates is
+now indexed by geo indexes and thus also matched by geo-spatial queries, which
+means you may find more results than before.
+
+Also see [Geo-spatial functions in AQL](../../aql/functions/geo.md).
+
 ## JavaScript API
 
 ### Database creation

site/content/arangodb/3.12/release-notes/version-3.11/incompatible-changes-in-3-11.md

@@ -1398,6 +1398,24 @@ connections. Some memory is pre-allocated at startup for higher efficiency. If t
 `--server.statistics` startup option is set to `false`, then no memory will be
 allocated for connection and request statistics.
 
+### Optional elevation for GeoJSON Points
+
+<small>Introduced in: v3.11.14-2</small>
+
+The `GEO_POINT()` function now accepts an optional third argument to create a
+GeoJSON Point with three coordinates: `[longitude, latitude, elevation]`.
+
+GeoJSON Points may now have three coordinates in general.
+However, ArangoDB does not take any elevation into account in geo-spatial
+calculations.
+
+Points with an elevation do no longer fail the validation in the `GEO_POLYGON()`
+and `GEO_MULTIPOLYGON()` functions. Moreover, GeoJSON with three coordinates is
+now indexed by geo indexes and thus also matched by geo-spatial queries, which
+means you may find more results than before.
+
+Also see [Geo-spatial functions in AQL](../../aql/functions/geo.md).
+
 ## Client tools
 
 ### arangodump

site/content/arangodb/3.12/release-notes/version-3.11/whats-new-in-3-11.md

@@ -615,6 +615,21 @@ support the VelocyPack format. The cluster replication has been changed to use
 VelocyPack instead of JSON to avoid unnecessary conversions and avoiding any
 risk of deviations due to the serialization.
 
+## Optional elevation for GeoJSON Points
+
+<small>Introduced in: v3.11.14-2</small>
+
+GeoJSON Point may now have three coordinates: `[longitude, latitude, elevation]`.
+However, ArangoDB does not take any elevation into account in geo-spatial
+calculations.
+
+Points with an elevation do no longer fail the validation in the `GEO_POLYGON()`
+and `GEO_MULTIPOLYGON()` functions. Moreover, GeoJSON with three coordinates is
+now indexed by geo indexes and thus also matched by geo-spatial queries, which
+means you may find more results than before.
+
+Also see [Geo-spatial functions in AQL](../../aql/functions/geo.md).
+
 ## JavaScript API
 
 ### Database creation

site/content/arangodb/4.0/release-notes/version-3.11/incompatible-changes-in-3-11.md

@@ -1398,6 +1398,24 @@ connections. Some memory is pre-allocated at startup for higher efficiency. If t
 `--server.statistics` startup option is set to `false`, then no memory will be
 allocated for connection and request statistics.
 
+### Optional elevation for GeoJSON Points
+
+<small>Introduced in: v3.11.14-2</small>
+
+The `GEO_POINT()` function now accepts an optional third argument to create a
+GeoJSON Point with three coordinates: `[longitude, latitude, elevation]`.
+
+GeoJSON Points may now have three coordinates in general.
+However, ArangoDB does not take any elevation into account in geo-spatial
+calculations.
+
+Points with an elevation do no longer fail the validation in the `GEO_POLYGON()`
+and `GEO_MULTIPOLYGON()` functions. Moreover, GeoJSON with three coordinates is
+now indexed by geo indexes and thus also matched by geo-spatial queries, which
+means you may find more results than before.
+
+Also see [Geo-spatial functions in AQL](../../aql/functions/geo.md).
+
 ## Client tools
 
 ### arangodump