How to query feature for elevation data from Imagery Service?

[BlakeMorrison]

I'm attempting to create an app where my end users can click their features and the popup will display the elevation at that point on the map.

I've found this Imagery Service on Living Atlas which seems appropriate: e393da08765940e49e27e30e1df02b58

I'm unable to create a FeatureSet from an Imagery Service. Is there some other type of obvious workflow I'm missing?

[TimF]

@BlakeMorrison - sorry if I'm missing something, but the Living Atlas item (Item ID: e393da08765940e49e27e30e1df02b58) is already configured to return elevation. It does this via a text pop-up. If you add this item to maps, it should respect this.

If you've indexed it to your Portal as a new item - as possibly looks the case - it may have lost the pop-up, so you just need to copy the settings from the original and save your version: 

Hope that helps!

[BlakeMorrison]

Thanks @TimF

I was hoping to reference the elevation layer from another features popup, using the location of that feature.

It's very possible that I'm missing an obvious way of doing this.

I can see now that my link to that imagery service isn't the one I perhaps should have shared, but can confirm I was just meaning to link to the living Atlas service. Not quite sure how I managed that with the link.

[TimF]

Ah gotcha - sorry, I missed the bit about querying other features. I don't think it is possible to query a vector feature and return the service pixel value for a raster Imagery Service... but happy to be corrected on that.

The workaround I'd apply, if the extent is reasonable, would be to convert the raster cells into vector centre-points, so they can then be picked up by Arcade. Whether this is efficient however depends on your circumstances.

[BlakeMorrison]

I've just now asked some form of AI and it pointed me in the direction of making my features z-aware and then adding a specific elevation layer. This makes a lot of sense and I will have to investigate how this all works and the implications to my current workflows. 

Is anyone able to confirm I'm pointed in the right direction?