Using the Lat/long Reader

It would be nice if coordinates could be entered and then the view shifted to that location. That would require bound checking to make sure the target location is somewhere on an existing baseboard. Sounds like a variation of the Find function that takes you to the location of an object. Perhaps a clever scripter could develop that. I'm not that clever.

As for the number of decimals, that is built-in and not something I added.

Glad you find it useful. I use it constantly to place real world objects in my maps.
 
It would be nice if coordinates could be entered and then the view shifted to that location. That would require bound checking to make sure the target location is somewhere on an existing baseboard. Sounds like a variation of the Find function that takes you to the location of an object. Perhaps a clever scripter could develop that. I'm not that clever.

As for the number of decimals, that is built-in and not something I added.

Glad you find it useful. I use it constantly to place real world objects in my maps.

I see, wish it was available and it would be useful. I made the request for any helpful advice from you since it is relation to any other methods I can adapt to in order to increase workload efficiency on a full scale project I have already embarked on.

Aim: 100% accuracy as much as possible in replication of the entire railway infrastructure across Australia.

At the moment it has started off from the state of Victoria, where the world of origin has initiated from Glen Waverley railway station, the map has continued up to Flinders Street and onwards to Footscray, down to Werribee and at the moment, Geelong where I am building up the interlocking now.

The current process I am using to replicate properly is through Google Earth and plotting placemarks where tracks change direction and other points of interest such as the ends of station platforms and points. Then, the 'my places.kml' file is opened in a word pad and the longitude and latitude co-ordinates are translated to Degrees, decimal minute formats to which trainz uses.

There are at least 10 decimal places where calculating co-ordinates out of Google earth kml files. Which still has a problem as trainz can't show more than 3.

The third decimal place in trainz is also a rounded decimal unit. Most troubling of all, is that these third decimal place numbers of the geographic co-ordinate are at least 1.8 meters within their zone. It's a lot of room for it not to change and is not as precise.

The result is that I have to use a number of Trig stations as well surrounding one co-ordinate to work out precisely where within the 1.8 meter geographic block the position of a track spline should be laid.

Identifying from Google earth a placemark co-ordinate to having it placed correctly in Trainz is taking at least 5 minutes and is easy to make errors as rounded numbers have to be broken down and placing them correctly requires very careful efforts of latitude and longitude positioning.

With your Lat/longitude reader I am able to look down and move accordingly and it is much faster. Using trig stations myself to move over a long distance is quite a difficult task as you have to look into it's side on your way to the co-ordinate

Perhaps if you have something like a way where perhaps the co-ordinates display decimal degrees? I think this format may be more accurate.

Thanks for your help.
 
My work flow is similar but instead of waiting to open the kml file, I transcribe the coordinates directly from the GE screen. I've set the output to show degrees - decimal minutes since that is the way they are shown Trainz. I don't think the display format will change the underlying accuracy. As well, I would not worry too much about an error zone of 1.8 meters. Google Earth objects have been known to be displaced by more than that. If you look at some the junctions between their image files, you'll sometimes see horizontal displacements. Really obvious when a straight road crosses the boundary.
 
Actually that's exactly what I did with the track roads etc on my current project using a microdem hog created terrain just took the co-ordinates directly off Google Earth, one or two bits needed a bit of manipulation due to the inevitable inaccuracies of the DEM I was using, interestingly now you can get them off the UK's Ordnance Survey their DEM's are pretty accurate and would have saved me a lot of Terrain "Carving" Any doubt with Google Earth and I checked on a local map and took the co-ordinates off of that.
To sum up I find your lat long reader extremely useful.
 
Back
Top