You should also consider that the distance from any real-world point
to an infinitely thin geometric line is unlikely ever to be exactly
zero. You'd need to decide what is "close enough", 0.0001mm or 1km.
--
You received this message because you are subscribed to the Google Groups
"Google Maps
Hi Andrew,
We agree that 200 is not the most appropriate HTTP status code for
these responses, but it does appear it is the response that we need to
return in order for developers to be able to easily reach the Geocoder
Response code contained in the body.
As the Geocoder response code is a lot m
On Feb 1, 3:26 am, "Thor (Google Employee)"
wrote:
>
> This change will roll out over the course of the next 24 to 48 hours.
Has Issue 1933 actually been considered? That is, has status 409 been
considered as a possible response or tested with "some client
libraries"? Or are you simply reverting
A while ago as part of some internal updates to our geocoding service,
the HTTP status codes returned for XML responses containing geocoder
error codes were changed to more accurately conform to the HTTP spec
(in our opinion).
We thought this was a "good thing" but it proved to cause more
problems
