Goku, on 23 December 2017 - 03:34 PM, said:
James Ross - this projection looks soo difficult. But if you have any example code to work with I can try.
I'd like to give something for users as fast as possible.
That is not a good strategy. You should at least consider some of the options; there have been plenty of discussions here about projections and the options seem to always come back to Transverse Mercator (TM ) although, having looked at it today, Universal Transverse Mercator (UTM) seems like a better option (see below).
Simon E, on 23 December 2017 - 03:38 PM, said:
And to Ross, I think UTM is a MUCH Better Projection. Thats why Trainz, And Train Simulator (Railworks) 2018 uses it.
When making claims of "better" you really ought to include reasoning, even if it's just a link to a respectable source.
UTM and TM are strongly related as their names imply; TM is a projection down a single longitudinal line with good accuracy near to this line (a few degrees to either side), where as UTM is a collection of 60 of these TM "strips" stitched together to create a worldwide version.
Therefore, it seems that the only significant difference between UTM and TM is that UTM provides a global map, where as TM only provides it within a single longitudinal strip. Both provide similar properties (e.g. conformal) and accuracy AFAICT. I would say that UTM is the better choice simply because it is worldwide.
Simon E, on 23 December 2017 - 03:38 PM, said:
and TSRE writes ORTSGeoProjection(MSTS) or ORTSGeoProjection(UTM) in the .trk file. So some innocent novice, doesn't go fiddling with switches in the options dialog in OR.
Nobody has suggested this is a user option in OR AFAICS; this is an option for the route creator only and whatever is selected will be included in the route data somewhere, most likely the track data file (.trk).