Hi all,

First of all, I want to say that WMS sucks. The 100-page spec sucks, the 
efficiency sucks.

That said, I just committed to SVN a set of hacks I've come to call "OSM WMS". 

Why? Long story short, this will allow me to promote OSM to GIS people. Or, as 
FakeSteveC would say, Arctards.

However, the current implementation has the potential of pounding the API down 
to its knees (no caching of any kind). In fact, I think it has more bugs than 

So, I'd like to know if you think it would be a good idea to do load balancing 
between several OSMXAPI servers.

(Yes, I know the best solution is to set up a local mirror of the database 
given a planet dump, and get the data from there. I just wanted to make 
something very simple to set up.)

Also, would it be a good idea to call OSMXAPI with the whole earth as a BBOX 
and try to render the whole coastline? Any ideas on how an OSM WMS would 
behave on such large requests?

Iván Sánchez Ortega <[EMAIL PROTECTED]>

Don't tell any big lies today.  Small ones can be just as effective.

Attachment: signature.asc
Description: This is a digitally signed message part.

dev mailing list

Reply via email to