Error Loading Height

[ruifonseca]

Lately I have detected this problem



It happens on longitude -8.00000

I ahve long had a set of 3m hgst files for the territory at hand already loaded and with terrtex from Mapbox images. Recently I started laying track on these tiles and because i as layign in trial and error i wantd to load the height again... from the same old files and this started to happen. A few days ago I doanload a set of 1m resolution hgst files and the same thing keeps happening... therefore I do not thing it has anything to do with the terrain files, but rather with the TSRE5...

[eric]

It may be an error. I occasionally see 2-5m differences from what I expect as well, although this looks much more.

That functionality hasn't been touched in v8.x as far as I know. Perhaps GokuMK can comment or offer a suggestion.

You can try the offset adjustments in the upper right corner to a negative or positive value. That may line it up as expected.

[oper190]

Not familiar with TRSE , but seen this often in OR: ( in some routes more than others )
Open Rails 2024-02-03 09-08-44.jpg
Open Rails 2024-03-09 04-36-47.jpg
Open Rails 2024-04-03 05-43-38.jpg
and the infinity needle, couldn't find the top
Open Rails 2024-03-08 09-23-21.jpg

[ruifonseca]

This is nothing of the sorts... this happens ain all tiles with the -8 longitude, I've already tried in several other regions of my country were I'm going to lay track... it happens at the 42th parallet, 40th and also at the 38th... so I'm assuming here is happens north to south. I've been using he test version since f, but i cannot tell if this would happen on that one or not...

[rdayt]

See that black line along the right hand side of hgsd file shown above? That's the problem.
TSRE sees that line and raises the terrain to the maximum height along the black line.
Pure black is max height pure white is sea level.
Lay a long piece of track adjacent to the line and then move it into the raised terrain then use the height function under f2 in TSRE to set the correct height, right click and set terrain to object.

Randy

[ruifonseca]

I see it, and I know it is the problem. the bigger problme is... why is it there? because it was not on the first time i loaded the height... and all of the suddent it is there... and when i changed from the 3m res files to the 1m res files... it's alos there... i belive it's a problem with tsre5 importing the hgst files, because it runs all along the 8th parallel. and actually, this goes down to sea level, or 0m on the black line.

[ruifonseca]

It may be an error. I occasionally see 2-5m differences from what I expect as well, although this looks much more.

That functionality hasn't been touched in v8.x as far as I know. Perhaps GokuMK can comment or offer a suggestion.

You can try the offset adjustments in the upper right corner to a negative or positive value. That may line it up as expected.

Is he still around? havent heard of him for quite some time. Maybe I'll post this on his forum...

[rdayt]

Sprocket holes from the film handling machine will do the same thing.
sprocket holes.jpg
Randy

[eric]

It's likely anomalies in the raw data and they do frequently occur at the seam.

Maybe it would make sense to ignore or zero out the values that are more than 100m different from the preceeding value or not. I'd rather have a sinkhole than a pin sticking up.