From a914ebe5e83ed5d76e0a7568cdc6fba0af44448f Mon Sep 17 00:00:00 2001 From: shimoncohen Date: Sun, 21 Jun 2026 13:53:03 +0300 Subject: [PATCH] docs(dem): add elevation obligations --- .../DEM/Services/{elevation/README.md => elevation.md} | 2 +- docs/MapColonies/obligations.md | 10 ++++++++++ 2 files changed, 11 insertions(+), 1 deletion(-) rename docs/MapColonies/DEM/Services/{elevation/README.md => elevation.md} (99%) diff --git a/docs/MapColonies/DEM/Services/elevation/README.md b/docs/MapColonies/DEM/Services/elevation.md similarity index 99% rename from docs/MapColonies/DEM/Services/elevation/README.md rename to docs/MapColonies/DEM/Services/elevation.md index 054d85ee44..e30b830c7c 100644 --- a/docs/MapColonies/DEM/Services/elevation/README.md +++ b/docs/MapColonies/DEM/Services/elevation.md @@ -1,6 +1,6 @@ --- id: dem-elevation-service -slug: info +slug: elevation title: Elevation ⛰️ description: Service to return geographic coordinate [lat, lon] elevation tags: diff --git a/docs/MapColonies/obligations.md b/docs/MapColonies/obligations.md index 5f8867bf45..e194fe4482 100644 --- a/docs/MapColonies/obligations.md +++ b/docs/MapColonies/obligations.md @@ -58,3 +58,13 @@ We also recommend that the layers are loaded in the same order as described in t ### Using Feedback API with Geocoding While interacting with Geocoding API, for BI purposes and to better understand our users's needs and interests, for each response sent from Geocoding API, we require the users to provide 'feedback' on our response by using Geocoding's [`Feedback API`](/docs/MapColonies/vector/Services/geocoding/feedback). + +## DEM + +### Displaying Elevation results + +If you choose to display [`Elevation`](/docs/MapColonies/DEM/Services/elevation) results in your application UI, you must clearly present the following fields: +- `productType` +- `resolutionMeter` +- `absoluteAccuracyLEP90` +Displaying these fields is critical to ensuring end-users can make informed decisions based on the returned data.