On Jul 27, 2:45 pm, "Mr. Scott" <[email protected]> wrote: > > But alas, if they can't even get their data structures aligned, seems > their's little hope for that.
Geocoder output is supposed to align with xAL. In that DTD (see http://www.oasis-open.org/committees/ciq/download.html) a PostalCode element can be a child of - AdministrativeArea - SubAdministrativeArea - Locality - DependentLocality - Thoroughfare - PostOffice - PostBox - Premise - Firm - Department - LargeMailUser Not all of those elements are included in the geocoder output, but there is definitely scope for some apparent inconsistency while remaining within the specification. Issue 606 would definitely make life easier. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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 -~----------~----~----~----~------~----~------~--~---
