On Oct 14, 1:53 pm, LSSMN <[email protected]> wrote: > > Does anybody know why? And is there a workaround?
(a) Geocoders change. The default position regarding display of SubAdministrativeArea may have changed because zipcodes may cover more than one. (b) You could reverse-geocode the point returned, which is presumably the centroid of the zipcode area. A point will always be in a single county, although it *may* not be the county which most of the zipcode area covers. It's likely that a SubAdministrativeArea will be returned for a single point, at least most of the time. http://maps.google.com/maps/geo?q=44.9605503,-93.2616717&output=xml&key=ABQIAAAAKS0eaO74jIASu1UolJlxPRT2yXp_ZAY8_ufC3CFXhHIE1NvwkxT43gCOvmoj2ysfZZF7BgURU_Z-Bg It doesn't work for the UK particularly well. http://maps.google.com/maps/geo?q=51.9605503,-1.2616717&output=xml&key=ABQIAAAAKS0eaO74jIASu1UolJlxPRT2yXp_ZAY8_ufC3CFXhHIE1NvwkxT43gCOvmoj2ysfZZF7BgURU_Z-Bg -- in this case, geocoding the address gives SubAdministrativeArea. Perhaps it's necessary to do some defensive coding and try reverse- geocoding if the data is not returned first time. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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-api?hl=en.
