Page 1 of 1

Terrain importing not working in Kansas City area.

Unread postPosted: Sun Jul 01, 2018 2:23 pm
by Brickrail782
It seems to think that the entire area is perfectly flat, and it refuses to correct any manual changes (i.e, making a small hill in the area.) What's wrong?

Re: Terrain importing not working in Kansas City area.

Unread postPosted: Sun Jul 01, 2018 2:45 pm
by wacampbell
Here's a few things to check.

1. Is the Lat. Lon. for your route set properly.
2. Did you download DEM data for the KC area?
3. Is the data in the right format? - ie 1 arcsecond or 3 arcsecond SRTM topo in .HGT format
4. Are the filenames in the right format - ie N24W116.hgt
5. Did you put the data in the right folder? eg Railworks\DEM\SRTM
6. When you import the dem, be sure you are not selecting too large a region ie 1x1, 2x2, etc - drop down to 1x1 to be sure

Re: Terrain importing not working in Kansas City area.

Unread postPosted: Sun Jul 01, 2018 4:59 pm
by Brickrail782
Turns out I had downloaded data that was too far north of KC. Seems to be in working condition now. *!!thnx!!*

Re: Terrain importing not working in Kansas City area.

Unread postPosted: Thu Jul 05, 2018 10:22 am
by SAR704
I think the only time I've had an issue like this is when I've mistakenly entered the wrong coordinates, eg entering the longitude as latitude and vice versa.

Easy error to make, but can be a PITA. Gotta pay full attention when setting up a route template.