On Sep 4, 3:33 pm, "warden [Andrew Leach - Maps API Guru]"
<[EMAIL PROTECTED]> wrote:
> On Sep 4, 4:18 pm, Lewis <[EMAIL PROTECTED]> wrote:
>
> > Using the geocode service, we've been getting some odd results. For
> > Norwich, UK, most postcodes provide invalid results when using a key.
>
> I think you've found a hole, so I wouldn't shout about it too loudly.
> On the other hand, because it's a hole, you need to be prepared for it
> to be plugged.
>
> The API doesn't geocode postcodes (it only goes as far as sector
> centroids). The HTTP geocoder, which should be used with a key,
> provides the same results (as you've found). It's an abuse of the
> system not to use a key. Using no key is the way which it's used on
> Google's own domains, which at the moment do geocode the entire
> postcode. Pamela has indicated that this behaviour is planned to
> change because of Royal Mail licensing issues -- and probably the fact
> that it's not only Google who can use their full-code data.
>
> I get a 610 error with your second (non-key) link, which would
> indicate that you are using that link within a script hosted by Google
> (in googlepages, perhaps?) for it to work.
>
> Andrew
I found the same to be true with Google's other services:
gx
geo
nav
if running locally on hard drive. The key cannot be validated without
a valid domain name. Once I moved it to the web, it failed without a
vaild key.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
