topic Re: Having issue with setting Base Elevations in contours. in 3D Questions

Having issue with setting Base Elevations in contours.

JonathanHarris — Fri, 09 Mar 2012 18:28:43 GMT

I am trying to create a TIN from NED data. Here is the process I have used so far. I downloaded a segment of the NED from the USGS seamless server and pulled it into ArcMap. Using spatial analyst, I was able to create a contour file utilizing 1m intervals and a z factor of 1. The contour is created without issues. When I bring the contour into ArcScene 10, It shows up as 2D. When I go into the Base Heights Tab, I'm choosing "USE a constant value or expression" and selecting "[Contour]" in the expression builder. When I press OK, the contour disappears from the scene. If I click zoom to layer all I see is a thin string of vertical dots in the center of my screen. What am I missing.

I also tried setting the base heights from the original NED surface.

The file is in GCS_North_American_1983, which is the same as the source NED.
I am using the evaluation version of 3D and Spatial analyst. Version 10

Re: Having issue with setting Base Elevations in contours.

TimothyHales — Fri, 09 Mar 2012 19:06:06 GMT

Try projecting your data using a projected coordinate system. With the data in a Geographic Coordinate System, it is not being read very well. You may also be able to calculate a vertical exageration from the scene properties (View > Scene Properties) to get the data to view.

Re: Having issue with setting Base Elevations in contours.

TarunJaiswal — Fri, 09 Mar 2012 19:36:15 GMT

Here is a link to a Knowledge Base Technical Article addressing this issue.

ArcScene layers display as vertical lines

Hope it helps.

Tarun

Re: Having issue with setting Base Elevations in contours.

Anonymous User — Fri, 09 Mar 2012 20:45:26 GMT

Original User: jonharis

Thank you guys. That fixed it. I used the Vertical Exaggeration workaround.

Re: Having issue with setting Base Elevations in contours.

PatrickQuintard — Fri, 09 Mar 2012 23:18:53 GMT

I used the Vertical Exaggeration workaround.