Select to view content in your preferred language

Exposing elevation slope aspect values when publishing Terrain Data

627
2
Jump to solution
10-03-2012 11:03 AM
WesleyMarcell
Occasional Contributor
I have been wrestling with a problem and am turning to the forums for help.

We have a terrain dataset that was generated from x,y point data.  When I add this layer to a map and publish I cannot turn on WCS as the layer does not support it.

I would like the client to be able to click on the terrain map service with the identify tool and see the corresponding elevation, Slope, and Aspect values that you can see when identifying on the terrain dataset in ArcMap.

So first, is this even possible?  I have tested in version 10.0 and 10.1 and cannot figure anything out.  Second, If it is possible can someone provide guidance or a link to the solution?  I really think that this functionality should be possible using ArcGIS Server, especially with the prevailance of LiDAR/Elevation data and ESRI's push to support it.  If this is not a supported function, will it be added in a future release?

The only partial solution I have found is converting the terrain dataset to a raster.  I placed the raster below the terrain dataset and published which allowed the client to identify the elevation values within the raster.  This does not expose the slope and aspect information though.

Thanks for any assistance!
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
TanuHoque
Esri Regular Contributor
Identifying a Terrain/TIN layer via a map service is planned to be supported in 10.1 SP1.

View solution in original post

0 Kudos
2 Replies
TanuHoque
Esri Regular Contributor
Identifying a Terrain/TIN layer via a map service is planned to be supported in 10.1 SP1.
0 Kudos
WesleyMarcell
Occasional Contributor
Thanks Tanu.  I looked for the expected updates with SP1 and that was the first item listed for ArcGIS Server.  I appreciate your quick response and look forward to this added functionality.

�?� NIM043298 - The Terrain and TIN layers are not identified using the Identify Tool, if they are accessed through a map service.
0 Kudos