W3C home > Mailing lists > Public > public-sdw-wg@w3.org > March 2017

Re: CRS best practices: Google Geocoding API

From: Clemens Portele <portele@interactive-instruments.de>
Date: Fri, 3 Mar 2017 15:52:33 +0000
To: Jeremy Tandy <jeremy.tandy@gmail.com>
CC: SDW WG Public List <public-sdw-wg@w3.org>, Ed Parsons <eparsons@google.com>
Message-ID: <50491C88-4881-4DF7-ADC3-AB4A18F12F48@interactive-instruments.de>
Being a human, I'm prepared to guess that these are decimal degrees (because they look like floating point numbers). Easy for machines to figure that out too.

Don’t forget radian or gon which are used in practice as units for angles, too, but are also floating point numbers :)

Clemens


On 3 Mar 2017, at 16:14, Jeremy Tandy <jeremy.tandy@gmail.com<mailto:jeremy.tandy@gmail.com>> wrote:

Hi Ed- in the introductory material you wrote about CRS you make a reference to the Google Geocoding API [1], in that its responses explicitly state Lat and Long rather than a coordinate pair of ambiguous order.

Lat and Long are, by definition, angular measurements. OK - got that.

But parsing through the API documentation, I can't see any reference to the units or datum which is used.

Being a human, I'm prepared to guess that these are decimal degrees (because they look like floating point numbers). Easy for machines to figure that out too.

As a human, I'm also prepared to guess that the API uses the WGS84. But that is a tricky leap for machines to work out.

Does the API documentation say "WGS84" anywhere? If so, can you point me to it so I can refer to this explicitly? And if not, can you either justify why it doesn't matter, or get your colleagues to update the documentation (and then send me a link!).

(I think that we've all agreed that it's dangerous to _assume_ a CRS :-) )

Thanks, Jeremy

[1]: https://developers.google.com/maps/documentation/geocoding/intro


Received on Friday, 3 March 2017 15:53:39 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 March 2017 15:53:39 UTC