- From: Jon Ferraiolo <jferrai@us.ibm.com>
- Date: Wed, 25 Jun 2008 08:14:04 -0700
- To: "Alan McNamara" <alan.mcnamara@badja.com>
- Cc: public-geolocation@w3.org
- Message-ID: <OFE886F93C.6D61E6CA-ON88257473.00535E74-88257473.0053AFBA@us.ibm.com>
For lay people (such as me) who until now have never heard the term
"geodetic system" before, perhaps the API can have the ability to return a
simple lat/long value but somewhere inside the spec there can be an
explanation of which geodetic system (or whatever the proper term is) is
used by default.
Jon
"Alan McNamara"
<alan.mcnamara@ba
dja.com> To
Sent by: public-geolocation@w3.org
public-geolocatio cc
n-request@w3.org
Subject
The Geolocation API must provide
06/25/08 06:09 AM location data in terms of a pair
of latitude and longitude
coordinates.
I am not a GIS expert, but my GIS friends constantly remind me that there
is no such thing as latitude and longitude. Such numbers are dependent on
the geodetic system used.
Futher, the draft arbitarily uses wgs84 for altitude, so it may be that
this is also intended to be used for latitude and longitude. This would
not be acceptable in Australia, for example. In New South Wales, and
Australian state, all candastre (land) data is supplied in a couple of
Australian standard. So wgs84 locations would not correctly show which
street you were standing.
I suggest the standard needs to require the inclusion of the geodetic
system. The standard may need to propose a list of supported geodetic
systems.
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: pic24157.gif
- image/gif attachment: ecblank.gif
Received on Wednesday, 25 June 2008 15:17:21 UTC