Can someone point me to a "clear, precise" description of the fields
in the AddressDetails returned by the "getLocations()" method of
GClientGeocoder? I've searched and read numerous posts about the
inconsistencies around this API and nowhere have I seen anything that
gives me the confidence that this API works consistently enough to
stand on its own.
I just want to be able to know that the results coming back will be
consistent. When a valid address including a town is passed in I
still get times when the LocalityName does not come back. I want to
be able to do a lookup passing in "street and zip code" or "street,
city/town, state" or "street, city/town, state, and zip code" and get
consistent results back.
The odd thing is that regardless of whether I pass in "street and zip
code", "street, town, state", "street, town, state, zip code" to
maps.google.com the correct, conistent address is shown when the
results are returned.
> Can someone point me to a "clear, precise" description of the fields
> in the AddressDetails returned by the "getLocations()" method of
> GClientGeocoder? I've searched and read numerous posts about the
> inconsistencies around this API and nowhere have I seen anything that
> gives me the confidence that this API works consistently enough to
> stand on its own.
> I just want to be able to know that the results coming back will be
> consistent. When a valid address including a town is passed in I
> still get times when the LocalityName does not come back. I want to
> be able to do a lookup passing in "street and zip code" or "street,
> city/town, state" or "street, city/town, state, and zip code" and get
> consistent results back.
> The odd thing is that regardless of whether I pass in "street and zip
> code", "street, town, state", "street, town, state, zip code" to
> maps.google.com the correct, conistent address is shown when the
> results are returned.
No it is not. I'm looking up a simple address in the US.
The fact that the getLocations() method returns different structures
when returning results to represent a street name for example makes
this an API that could use a little more detail. For example:
> On Jul 6, 3:35 am, snappa <bill.snap...@gmail.com> wrote:
> > Can someone point me to a "clear, precise" description of the fields
> > in the AddressDetails returned by the "getLocations()" method of
> > GClientGeocoder? I've searched and read numerous posts about the
> > inconsistencies around this API and nowhere have I seen anything that
> > gives me the confidence that this API works consistently enough to
> > stand on its own.
> > I just want to be able to know that the results coming back will be
> > consistent. When a valid address including a town is passed in I
> > still get times when the LocalityName does not come back. I want to
> > be able to do a lookup passing in "street and zip code" or "street,
> > city/town, state" or "street, city/town, state, and zip code" and get
> > consistent results back.
> > The odd thing is that regardless of whether I pass in "street and zip
> > code", "street, town, state", "street, town, state, zip code" to
> > maps.google.com the correct, conistent address is shown when the
> > results are returned.
Can anyone shed some light on the expected structure of the
getLocations results?
I could understand all the variants IF there were a type denoting
which format to expect so that parsing were predictable but have not
seen this documented anywhere.
Any help / pointers would be appreciated.
Thanks in advance.
On Jul 5, 11:00 pm, snappa <bill.snap...@gmail.com> wrote:
> No it is not. I'm looking up a simple address in the US.
> The fact that the getLocations() method returns different structures
> when returning results to represent a street name for example makes
> this an API that could use a little more detail. For example:
> > On Jul 6, 3:35 am, snappa <bill.snap...@gmail.com> wrote:
> > > Can someone point me to a "clear, precise" description of the fields
> > > in the AddressDetails returned by the "getLocations()" method of
> > > GClientGeocoder? I've searched and read numerous posts about the
> > > inconsistencies around this API and nowhere have I seen anything that
> > > gives me the confidence that this API works consistently enough to
> > > stand on its own.
> > > I just want to be able to know that the results coming back will be
> > > consistent. When a valid address including a town is passed in I
> > > still get times when the LocalityName does not come back. I want to
> > > be able to do a lookup passing in "street and zip code" or "street,
> > > city/town, state" or "street, city/town, state, and zip code" and get
> > > consistent results back.
> > > The odd thing is that regardless of whether I pass in "street and zip
> > > code", "street, town, state", "street, town, state, zip code" to
> > > maps.google.com the correct, conistent address is shown when the
> > > results are returned.
A bit belated, but I'm going to respond with a possible solution in case it is still of use, or in hopes that someone else will have a better solution.
As best as I can tell, the two uncertainties for a full address in the US are the presence of a SubAdministrativeArea and the presence of a Locality.
In other words, ThoroughfareName can be at:
place.AddressDetails.Country.AdministrativeArea.* SubAdministrativeArea.Locality*.Thoroughfare.ThoroughfareName place.AddressDetails.Country.AdministrativeArea.*SubAdministrativeArea* .Thoroughfare.ThoroughfareName place.AddressDetails.Country.AdministrativeArea.*Locality* .Thoroughfare.ThoroughfareName place.AddressDetails.Country.AdministrativeArea.Thoroughfare.ThoroughfareNa me
For which the most efficient way I've found to deal with this are
On Mon, Jul 7, 2008 at 12:32 PM, snappa <bill.snap...@gmail.com> wrote:
> Can anyone shed some light on the expected structure of the > getLocations results?
> I could understand all the variants IF there were a type denoting > which format to expect so that parsing were predictable but have not > seen this documented anywhere.
> Any help / pointers would be appreciated.
> Thanks in advance.
> On Jul 5, 11:00 pm, snappa <bill.snap...@gmail.com> wrote: > > No it is not. I'm looking up a simple address in the US.
> > The fact that the getLocations() method returns different structures > > when returning results to represent a street name for example makes > > this an API that could use a little more detail. For example:
> > > > Can someone point me to a "clear, precise" description of the fields > > > > in the AddressDetails returned by the "getLocations()" method of > > > > GClientGeocoder? I've searched and read numerous posts about the > > > > inconsistencies around this API and nowhere have I seen anything that > > > > gives me the confidence that this API works consistently enough to > > > > stand on its own.
> > > > I just want to be able to know that the results coming back will be > > > > consistent. When a valid address including a town is passed in I > > > > still get times when the LocalityName does not come back. I want to > > > > be able to do a lookup passing in "street and zip code" or "street, > > > > city/town, state" or "street, city/town, state, and zip code" and get > > > > consistent results back.
> > > > The odd thing is that regardless of whether I pass in "street and zip > > > > code", "street, town, state", "street, town, state, zip code" to > > > > maps.google.com the correct, conistent address is shown when the > > > > results are returned.
