Skip to content

DOC-772 | GEO_POINT() accepts elevation but z coordinate is ignored in geo functions #741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

DOC-772 | GEO_POINT() accepts elevation but z coordinate is ignored in geo functions #741

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
213 changes: 116 additions & 97 deletions site/content/3.11/aql/functions/geo.md
View file
Open in desktop

Large diffs are not rendered by default.

15 changes: 15 additions & 0 deletions site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
18 changes: 18 additions & 0 deletions site/content/3.11/release-notes/version-3.11/whats-new-in-3-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
15 changes: 15 additions & 0 deletions site/content/3.12/release-notes/version-3.11/incompatible-changes-in-3-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
18 changes: 18 additions & 0 deletions site/content/3.12/release-notes/version-3.11/whats-new-in-3-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
15 changes: 15 additions & 0 deletions site/content/3.13/release-notes/version-3.11/incompatible-changes-in-3-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
18 changes: 18 additions & 0 deletions site/content/3.13/release-notes/version-3.11/whats-new-in-3-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down