Regarding DEM data accuracy, it's equivalent to a very low resolution image. And this is combined with the TS/RW terrain system which is not better than the MSTS terrain. It will never be detailed enough in RW to make everyone happy. The data that's available is still fairly accurate though, and good enough for TS projects, which is all that matters.
One can create their own embankment lofts and export anyway. Cuttings are more of a nuisance, but there may be somebody who has found a workaround. There are routes which use rock walls, so I'll assume the same can be done for cuttings.
TheTeenageFoamer wrote:My issue with the DEM data is that my terrain is way higher than where the DEM data would be. This is a factor from making my track according to track chart data.
I have noticed this kind of problem, but when it's a metre or so out, I try to raise the track a couple of dozen metres earlier than what I previously did. I measure lengths using digitalised curve and gradient charts viewed in Irfanview. It shows the pixels of the selection at the top of the screen. You can determine the rough length of the particular gradient by selecting the portion and adjusting according to the number of pixels. I have the digital charts sized in a way so that each mile amounts to roughly 40 pixels.
For example, if you've got a 1 in 120 decline, and then it changes to an incline, you can simply shred portions off the decline, and start the incline say 50 metres earlier. Doing this over a several kilometres makes a difference. It is still rather tedious, but it's much better than having a 30 metre deep cutting in flat countryside.