Hi all,
In ArcGIS Online Experience Builder, I’m seeing the Elevation Profile widget flatten out when a drawn or selected trail exceeds a certain length, even though the trail has noticeable elevation changes. Shorter segments look fine, but once the profile hits a certain distance, the detail drops off.
I’ve tested this using both the Esri World Elevation Service and my own 10m DEM published for use in the Web Scene Viewer — same result in AGOL.
What’s odd is that I built this exact same application in Portal (ArcGIS Enterprise 11.1), which uses Experience Builder 1.10, and the issue doesn’t occur there — the profile remains detailed across the entire trail length.
Has anyone else run into this? Is this a known regression in the newer ArcGIS Online Elevation Profile widget (Experience Builder 1.18), or is there a setting to control sampling resolution?
Screenshots attached for comparison between AGOL and Portal outputs.
Screenshots attached:
AGOL – Short segment (works fine)
AGOL – Longer segment (flattening occurs)
Portal – Older EB version (no issue)
Thanks!
AGOL (Short-Distance Trail)
AGOL (Flattening Occurs)
Portal - Older EB Version, no issue
To any devs reading this:
It looks like this flattening started after the jump from Experience Builder 1.10 (Portal, works fine) to 1.18 (AGOL, flattening occurs). I suspect the newer AGOL Elevation Profile widget caps the number of elevation samples on longer lines, so detail drops off past a certain distance. This happens with both Esri World Elevation and my own 10 m DEM.
Would love to see either a higher sample limit or a setting to control sampling density so AGOL matches the detail from older Portal versions.
Hi @JCOSGIS , I can look into this issue. Please, would you be able to share your web map with the trails layer you are using?
Hi @AlixVezina, thanks for looking into this!
Here’s the Jeffco Trails Explorer (Web Scene) map along with the Open Space Trails layer it uses. I’ve also added the Experience Builder app in case you’d like to test it yourself to see the issue in action.
Please let me know if you need anything else or have any follow-up questions.
Hi @AlixVezina,
Any luck looking into this? Thanks again for your help.
@JCOSGIS Apologies for the delay, our devs are still looking into this. We aren't sure yet what caused this change.
Hi @JCOSGIS
The issue no longer appears to occur. Do you know if any changes were made to the elevation service from your end? Are you still able to reproduce the issue?
Hi @Ali,
Nothing was changed on our end. We had been holding off on publishing our application until this issue was resolved. At this point, we’re also unable to reproduce the issue, so it does appear to be fixed.
Thanks for checking in!
Well, that is strange. But I'm glad it is now working for your app and you will be able to publish it! 😊 If the issue ever comes back, please let me know.