On Nov 10, 5:14 am, Chad Killingsworth <[email protected]> wrote: [snip] > > - is my hunch correct that Google developers can make any changes they > > want to the JSON data structure, as long as the published accessors > > function as advertised? > > Technically, the documentation says that the location property is a > LatLng object. LatLng does not have public properties called lat and > lng and Google can make changes to undocumented properties at any > time. [snip] > You should read this thread - you aren't the first to have difficulty > with > this:https://groups.google.com/group/google-maps-js-api-v3/browse_thread/t... > > Chad Killingsworth
Chad: Thanks for the pointer to the discussion. Moral: rely on the published JavaScript accessors, not the raw JSON object. That said, future astonishment and confusion could be averted by changing the text in: http://code.google.com/apis/maps/documentation/javascript/reference.html#GeocoderResult from "GeocoderResult object specification A single geocoder result in JSON format retrieved from the geocode server. Note that a geocode may return multiple result objects." to something like: "GeocoderResult object specification A single call to geocode will return an array of GeocoderResult objects in JSON format. Although the structure of the GeocoderResult is clearly visible in the JSON string, we strongly recommend that you use the published JavaScript accessors, described below, as the structure may change without notice." I'm sure the technical writers at Google can say this more succinctly than I can. (BTW, is there a formal channel for requesting a documentation change like this?) Thanks for your help. - ff -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
