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

CRS best practices: Google Geocoding API

From: Jeremy Tandy <jeremy.tandy@gmail.com>
Date: Fri, 03 Mar 2017 15:14:10 +0000
Message-ID: <CADtUq_118GbqQbE+PDYkqTjWdk-iz3MWnoNH4CsTYd9yUkkO9g@mail.gmail.com>
To: SDW WG Public List <public-sdw-wg@w3.org>, Ed Parsons <eparsons@google.com>
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:14:54 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 March 2017 15:14:54 UTC