On 30/05/16 00:04, Andre Joost wrote:
Thank you André
It's good to know there's an explanation. I'm not
sure how to apply it practically.
I found approximate Eastings can be obtained by
applying to formula /Google/ E/10 + 143500, but
the error can be +/-100m. Not really very useful.
Cheers
*John*
Am 14.05.2016 um 03:29 schrieb John Groombridge:
>
>If I create a waypoint at S 41° 11.003 E 174° 52.440, the equivalent
>Topo50 Grid reference is N5439192 E1757172.
>
>If I save and drag the waypoint onto Google Earth, Google Earth displays
>the same Latitude/Longitude, but the UTM coordinates are S5438707 E32169.38
>
>Ignoring the N/S 485m error, what is the explanation for the E32169
>display.
>
The Topo50 Grid of New Zealand EPSG:2193 is a transverse mercator
projection bases on the 173°E meridian, with a false easting of 1600000m
and a false northing of 10000000m to the equator.
The UTM zone of Wellington NZ (UTM 60S, EPSG:32760) is based on the
177°E meridian, with a false Easting of 500000m to it. Y values for UTM
South are measured from the South Pole.
So your point is 500000-32169 meters away from the 177°E meridian.
HTH,
André Joost
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
