| 2014-11-16 01:14:47 |
Herb Kelsey |
bug |
|
|
added bug |
| 2016-08-17 17:01:06 |
CeeJay |
bug |
|
|
added subscriber Simon Etxebarria |
| 2016-12-30 17:03:45 |
James Ross |
summary |
Lat Long doesn't match MSTS |
Latitude and longitude don't match MSTS (and are wrong generally) |
|
| 2016-12-30 17:03:49 |
James Ross |
or: status |
New |
Triaged |
|
| 2016-12-30 17:03:55 |
James Ross |
or: importance |
Undecided |
High |
|
| 2016-12-30 17:04:25 |
James Ross |
or: assignee |
|
James Ross (twpol) |
|
| 2022-12-30 09:40:17 |
om sonar |
description |
Since we are stuck with using the MSTS Route Editor for fixing errors like trees in the middle of the roadway on account of overlapping forests and stuff of that ilk, it would be handy if the Latitude and Longitude of the problem location in Open Rails would be close enough to the Latitude and Longitude in MSTS so you could find the problem in the other software and fix it. The difference is a good half mile of distance from the problem and where Lat Long says it is. Checking coordinates for both MSTS and OR against latitude/longitude lookup sites it would appear that MSTS is spot on, so the problem exists in OR. |
Since we are stuck with using the MSTS Route Editor for fixing errors like trees in the middle of the roadway on account of overlapping forests and stuff of that ilk, it would be handy if the Latitude and Longitude of the problem location in Open Rails would be close enough to the Latitude and Longitude in MSTS so you could find the problem in the other software and fix it. The difference is a good half mile of distance from the problem and where Lat Long says it is. Checking coordinates for both MSTS and OR against latitude/longitude lookup sites it would appear that MSTS is spot on, so the problem exists in OR.ttttgffddfddfffff dont do this |
|
| 2022-12-30 09:40:31 |
om sonar |
or: assignee |
James Ross (twpol) |
|
|
| 2022-12-30 09:40:42 |
om sonar |
or: status |
Triaged |
New |
|
| 2023-03-25 13:08:10 |
James Ross |
description |
Since we are stuck with using the MSTS Route Editor for fixing errors like trees in the middle of the roadway on account of overlapping forests and stuff of that ilk, it would be handy if the Latitude and Longitude of the problem location in Open Rails would be close enough to the Latitude and Longitude in MSTS so you could find the problem in the other software and fix it. The difference is a good half mile of distance from the problem and where Lat Long says it is. Checking coordinates for both MSTS and OR against latitude/longitude lookup sites it would appear that MSTS is spot on, so the problem exists in OR.ttttgffddfddfffff dont do this |
Since we are stuck with using the MSTS Route Editor for fixing errors like trees in the middle of the roadway on account of overlapping forests and stuff of that ilk, it would be handy if the Latitude and Longitude of the problem location in Open Rails would be close enough to the Latitude and Longitude in MSTS so you could find the problem in the other software and fix it. The difference is a good half mile of distance from the problem and where Lat Long says it is. Checking coordinates for both MSTS and OR against latitude/longitude lookup sites it would appear that MSTS is spot on, so the problem exists in OR. |
|
