I tried to create a terrain model from an ascii file, but my contours look very strange (see slanted lines). Was wondering if anyone can tell me what the issue is/ what I can do to fix it?
I can go more in-depth of exactly what I did, but here is a general overview of my steps: I downloaded the tin data from the website I normally do if I was doing this in MicroStation. I used the Create Terrain Model from Ascii File feature in ORD and uploaded the tin file. I opened the Create Text Import Settings File dialog box and went through the tabs on the left, and I made sure to specify my coordinate system. Then I closed that dialog box and clicked Import. I am not sure if there is something I am overlooking. Has anyone else had any similar issues?
Can you give an example of the data you get from the website (and what website is it)?
Sure, I am located in North Carolina and we use https://fris.nc.gov/fris/
I click on NC and choose a county. Once I choose a quad, I use the Data Export tab on the right hand side and click the Lidar Bare Earth link which downloads a zip file. This was the link we used when doing this same process in MicroStation. The .txt file give me the raw data which has northing, easting, and elevation values. That is what I use in ORD and I made sure in the Create Text Import Settings File dialog box I put my columns as northing, easting, and elevation.
I am unable to reach that site - looking at you image, the data is being read and the terrain created. The only issue would be if the data is correct? Can you post a sample of the text data?
Sure, here is a few lines of the .txt file:
X,Y,Z2258904.2300,750005.1500,259.67002258948.4200,750001.7100,260.44002258935.7000,750009.9400,260.01002258923.0500,750018.1200,259.84002258910.3300,750026.3500,259.49002258982.5400,750007.5200,260.88002258969.5400,750015.9300,260.7800
This goes on for thousands of lines.
The raw data usually has that "X,Y,Z" at the top. When I did this same process in MicroStation, we would delete the first line from the raw data so it was all just numbers. I did the same thing for ORD. In the Create Text Import Settings File dialog box on the Columns tab, I made sure to use a comma delimiter and assign each column as easting, northing, and elevation since the raw data has it as X,Y,Z.
I use a Feature Type of Contour and a Feature Symbology of Terrain\Exist\ET_Contours. I create no filters and I use a projected coordinate system of EPSG:102719 - NAD 1983 StatePlane North Carolina FIPS 3200 Feet. Not sure if any of that information is relevant to what my issue is.
There is nothing wrong with the workflow - it is the data I would now focus on. Are there unwanted overhead cables for example in the data?