[OSM-dev] [Marble-devel] NOTICE: gazetteer.osm.org being retired

Chris Browet cbro at semperpax.com
Wed Sep 1 15:14:55 BST 2010


On Wed, Sep 1, 2010 at 15:49, Patrick Kilian <osm at petschge.de> wrote:

> Hi,
>
> >> If you want to use an OSM service in one of your applications, then I
> >> would suggest firstly, and most importantly, that the application
> >> doesn't have a *.openstreetmap.org <http://openstreetmap.org> URL
> >> embedded anywhere in the code.
> > Come on. Does that mean that we cannot use "www.openstreetmap.org/api
> > <http://www.openstreetmap.org/api>" to update the database?
> This one might be ok. Iff you make your users sign up for OSM and have
> them read and understand the limits e.g. on acceptable sources.
>
>
> > That "tile.openstreetmap.org <http://tile.openstreetmap.org>" can
> > disappear in 2 weeks time?
> Very unlikely. But it might if the hardware catches on fire. And you
> should definitely NOT hardcode that URL into your application. The
> application should talk to your server(s) only. In the start you could
> redirect or proxy the request on your server. If later you app is used
> by 1 million users you can run your own tileserver under that URL. And
> once you reach 2 billion users you can run a load balance there.
>
> All without changing a single rolled-out copy of your app, just by
> reconfiguring a single point - your server.
>
> And if the OSM hardware ever burns down you can still feed you
> application from your proxy or even start to render from the last saved
> planet dump.
>
> While I'd completely agree in a business world, don't forget we are FLOSS
developers working on software in our free time.

We don't (at least I don't, and I doubt Marble has) have "a server". OSMF
do.
Just put a big red sticker on the wiki saying "ABSOLUTELY DO NOT USE OUR WEB
SERVICES, SETUP YOUR OWN!", then...

- Chris -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20100901/433883e1/attachment.html>


More information about the dev mailing list