[Geowanking] Geowanking Digest, Vol 9, Issue 14
scitronpousty at gmail.com
Fri Jul 17 12:35:30 PDT 2009
I no longer work for deCarta but I just thought I would point out that this
restriction does not apply to using the deCarta API. To boot, they have a
better freeform geocoder for some EU countries.
---------- Forwarded message ----------
> From: Sean Gorman <Sean.Gorman at fortiusone.com>
> To: Christopher Schmidt <crschmidt at metacarta.com>
> Date: Thu, 16 Jul 2009 20:56:22 -0400
> Subject: Re: [Geowanking] address parsing
> Yeah this causes all sorts of weirdness although my understanding is the
> legal terms flow from the street providers i.e. Teleatlas and Navteq. For
> instance when talking to Navteq about POI data we could not show it on
> Google maps because they use Teleatlas. Hence Yahoo using OSM and Google's
> MapMaker ????
> Sent from my iPhone
> On Jul 16, 2009, at 8:41 PM, Christopher Schmidt <crschmidt at metacarta.com>
> On Fri, Jul 17, 2009 at 10:16:50AM +1000, pamela fox wrote:
>>> FYI - there is still a cap. It's not currently enforced the same way it
>>> would on a normal server, but it will be in the future. So you should
>>> code with it in mind.
>>> Keep in mind also that Google geocodes can only be used in conjunction
>> The same is true of Yahoo! Geocodes and Yahoo! maps, afaik. (I guess
>> other than compare them visually, since looking at the numbers wouldn't
>> be 'using them with a google map'...)
>> -- Chris
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Geowanking