tom at tom-carden.co.uk
Tue Apr 25 23:56:23 BST 2006
Brief reply, because people have already clarified that it's only
putting OSM alongside Google Maps we don't like - manipulating and
presenting the data in new ways is *what it's all about* :)
Public apology much appreciated - like I said earlier today the
feedback is useful, but apart from the documentation problem (which
you already fixed) the other things weren't news to anyone who has
read the list much in the last couple of months.
I hope you stick around and find a way to contribute, and to consume
the data as you see fit. If you can set up, run and maintain a WMS
server based off planet.osm then fantastic - that will take the strain
off OSM's own machines until they can cope.
As for picking a bounding box, that should be possible using OSM's
tile code. It's a little flaky right now and could use some love, but
it basically works. I've got some stuff in the works that should help
a lot with this in the coming months.
On 4/25/06, Christopher Schmidt <crschmidt at crschmidt.net> wrote:
> I'd like to apologize for my earlier emails regarding OSM performance,
> and my problems with it. They were out of line, and I shouldn't have
> made them.
> I also want to apologize for creating a WMS server for the data - I
> didn't realize that I was possibly endangering the OSM project, and I'll
> make sure that I don't expose such things publicly in the future -- my
> goal is not to hurt hte project, I was just hoping to put up something
> cool that would let other people build cool things, but that also lets
> people put it on top of copyright data and compare.
> Is there any way to expose WMS in a way that's not dangerous to the
> project? I'd be willing to expose a WMS server on my server for others
> to use, if someone tells me the best way to prevent it from being
> Christopher Schmidt
> Web Developer
> talk mailing list
> talk at openstreetmap.org
More information about the talk