Railworks convert tile coordinates to latitude longitude

[rscarter]

Does anybody know how to convert tile coordinates to latitude and longitude.

For example, a siding is on tile -110 87 (in track tile -000100+000087)

On this tile, it occupies x and y coordinates 286.422 and 481.438

This data is from the tracks.bin file.

Thanks for any help.

[buzz456]

I know if you go there in the world editor it tells you the lat long up there in the box at the top. That's how I did all the route markers for the MRL.

[Bananarama]

Does anybody know how to convert tile coordinates to latitude and longitude.

For example, a siding is on tile -110 87 (in track tile -000100+000087)

On this tile, it occupies x and y coordinates 286.422 and 481.438

This data is from the tracks.bin file.

Thanks for any help.

Use the tile number, in this case it begins with a "-" indicating it's in the northern portion of the route, and the "+" for the second value means it's in the western section (100km and 87km). The second set of numbers you wrote (x, y) are in meters.

Open the RouteProperties.xml file for the route, and the lat/lon is given. Add the above tile numbers: 100km west, and 87km (you can add the other values as decimals) using the following calculator: http://www.nhc.noaa.gov/gccalc.shtml

There are plenty of other browser calculators on the 'net - Google is your friend.

[rscarter]

Thanks Marc. I have created a FoxPro program to read the tracks.bin file and create a list of all sidings in a route. It creates a .pdf file that shows the siding name and the internal Display Name used internally by TS201+ in scenarios. But the data in the tracks.bin file shows the tile and offset of the siding that I need to convert to latitude and longitude in order to use the utility at the top of the screen to go to a particular latitude and longitude. What is interesting is that some of the display names are so different from the siding name. For example in the P&LE, Siding "Inspection/departure lead east track 3" has a display name of "Passing track 3 cont." Sometimes the numbers are even different. Although it is not an issue in TS201+, when there are duplicates it causes problems when running scenarios.

I think this is a good utility for route builders to check sidings.

I know that these are all offsets from the base latitude and longitude of a route. I'll give your suggestion for converting these offsets to Lat and Lon a try. Thanks.

Dick