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. Thanks Steve
---------- Forwarded message ---------- > From: Sean Gorman <[email protected]> > To: Christopher Schmidt <[email protected]> > 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 <[email protected]> > wrote: > > 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 >>> still >>> code with it in mind. >>> Keep in mind also that Google geocodes can only be used in conjunction >>> with >>> a Google map, per the terms of use. >>> >> >> The same is true of Yahoo! Geocodes and Yahoo! maps, afaik. (I guess >> this means that it's a violation of the terms of use to do anything >> other than compare them visually, since looking at the numbers wouldn't >> be 'using them with a google map'...) >> >> -- Chris >> >
_______________________________________________ Geowanking mailing list [email protected] http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
