Coordinate discrepancies between ORTS and MSTS

[commec61]

Good one Andre.

[baldwin]

Earth is not round, it is more like a ring donut. Nobody has yet discovered the hole.

[Coonskin]

Nobody has yet discovered the hole.

Note: "Holes" (plural). Said "holes" are plentiful, which, by the way, is simply a shortened version of the term "a**holes". Such holes are easily found: The highest concentration of them (by a far stretch) can be found mainly in Washington D.C. (Both sides.)

You're welcome.

[Rick-MONON]

I would love to add to these comments, but I already fell off my chair laughing to much.....................lololol

[conductorchris]

Anyone who wants to laugh even more, just google FEMA cars (people think that autoracks are actually human cattle cars to round us all up when "they" come to put us in concentration camps.) Having stumbled on that, I got even more of a laugh when one person went apoplectic having discovered chains and tie-downs inside an empty one. Certain proof! There can be no doubt of their plans, now! We are doomed!

Oh and then I stumbled on "documentation" that Amtrak's Beach Grove shop complex is actually a FEMA camp.

Christopher

[charland]

It all depends on how you treat your customers!

Paul :-)

[baldwin]

To bring this thread back on course we know that MSTS uses the Goode-Homosoline projection. What we don't know it what ORTS is using or TSRE. From what Paul stated in post #14, I suspect it too is using G-H.

[charland]

I think OR's compass is just off and they have never thought it was important enough to fix. Remember, it was only six or eight months age that mile markers were introduced in their track monitor after years of people asking for that feature.

Paul :-)

[charland]

I think OR's compass is just off and they have never thought it was important enough to fix. Remember, it was only six or eight months age that mile markers were introduced in their track monitor after years of people asking for that feature.

I'm trying to post this reply and the first time it asked me if I wanted to leave the page without posting the reply, the second time I tried it sent me to the advanced reply page.

Paul :-)

[geepster775]

If the MSTS RE lands you at the correct spot per the MSTS compass, and TSRE lands you at the correct spot per the OR compass, then it appears both tools are in sync with their respective platform's compass algorithm (whatever that is) and the discrepancy problem only surfaces when you use one platform's compass to find some exact spot in the other platform's RE.

Clearly both platforms handle the issue differently, but who is to say definitively which one really is off. You would pretty much need a sufficient pool of TSRE-built routes (which we don't have) to statistically analyze for mileage shortages/overages.

[charland]

From the beginning of this thread, the problem is with Open Rails compass, TSRE really wasn't part of the question. The issue is with Open Rails giving incorrect latitude and longitude since it's first beta. Checking this morning with TSRE proves that you do get the correct results by entering the MSTS coordinates and going to the same spot.

If you want to see for yourself just do a little test. Go to a station or somewhere that's obviously recognizable and write down the coordinates. Go into MSTS RE and then TSRE and enter the coordinates and see if you go to the same spot.

Paul

[geepster775]

What was asked of you this morning was

"Now if Paul had input those same OR compass coordinates in TSRE, where would the jump have landed the camera?"

[charland]

And my reply to that question this morning was that I did and they brought me to the exact same location that my engine was, just as MSTS did, and not a mile away like OR does... post #14.

Paul :-)

[geepster775]

Just to be clear -

When you plugged the so-called 'wrong' OR compass values into TSRE, it took you right to where the engine sat when you screen grabbed the so-called 'wrong' OR compass coordinates.

And when you plugged in the MSTS compass coordinates, different values from the OR compass numbers, into the MSTS RE, it did the same, landed you right where the MSTS compass said the engine was when you took the MSTS screen grab.

But when you plugged the OR compass values into MSTS RE, you landed a mile away.

[R. Steele]

This thread from Jan 2017 at ET may help to clarify
http://www.elvastower.com/forums/ind...13-james-ross/

I've seen this same topic discussed in many threads, I understand it from a mapmaking viewpoint, but that's all.

...and here's James Ross observation regarding I statement I made in a thread about moving forests and trees in 2015 and why the coordinates in the MSTS RE were no where near the same place in OR
I said

The discussed difference between OR's lat and long readings and the RE is noticeable, quite a lot of real estate between the two sets of coordinates. Has anyone looked into any way of determining a relationship so perhaps a simple program could be made...plug in the lat and long readings from OR and out come the correct numbers to plug into the RE.

James's answer

(quote name='James Ross' timestamp='1430248596' post='179165')
For what it's worth, I think OR is simply wrong and MSTS is right. I wrote my own code for doing lat/long inside MSTS's world before I worked on OR and it matches up much better.

It may simply be a matter that the person who wrote that section of code for OR is no longer involved in the project and didn't leave enough breadcrumbs for anyone to figure out what they did and how they did it.
Obviously, this is a known fact...question is...Has a bug been reported, if not...why don't one of you with knowledge report it and if a bug was reported, what is the status?
Dispatcher originally wondered why the difference in lat and long between MSTS and OR.