On Fri, Oct 23, 2009 at 1:08 PM, Tom Hughes <[email protected]> wrote: > On 23/10/09 17:47, Anthony wrote: >> If you have a better suggestion, feel free to suggest it. Or if you >> can point me to a policy which forbids what I'm doing, I'll be happy >> to stop contributing to OSM. > > The policy is, broadly speaking, that if you put sufficient load on the api > that is causes a problem and comes to my attention then you're likely to > find yourself blocked. That is especially so if it looks you are crawling > the data in some way.
I figured as much. That's why I'm implementing the cache, rather than downloading the same data over and over again. > The point basically is that the API is designed to provide small chunks of > data and people that want larger chunks of data are encouraged to use planet > instead. Planet does not include history, correct? That was one of the questions in my original post. What's the nicest/friendliest way to download all the history for a particular US state? On Fri, Oct 23, 2009 at 1:11 PM, Tom Hughes <[email protected]> wrote: > In the real world we don't all have infinite CPU time and I/O bandwidth Hence my point about using a modern database, where you can create things like materialized views to make accessing the database efficient without making the core schema itself a mess. _______________________________________________ Geocoding mailing list [email protected] http://lists.openstreetmap.org/listinfo/geocoding
