[OSM-talk] Something wrong with OSM server?

[Nick Hill]

Hi All


It seems to me the 'problem' is that in areas like Central London, we have a 
very high aerial density of nodes and segments.

The servers are protected by having a bounding box limitation, which has up 
until now, sanitised huge queries and only returned those the hardware can 
reasonably handle.

Given there is no inherent limit on aerial density of OSM data, and given we 
have areas of extremely high density, It is no longer the case that establishing 
a maximum bounding box is adequate to preserve system integrity. We'll need to 
consider other mechanisms to maintain system integrity.

We can, of course, upgrade systems, but that alone gives no guarantee. We will 
therefore need to abort queries where the number of nodes exceeds a pre-set 
threshold.

This means the client will not know apriori if a query will be accepted by the 
API. However, the API could perhaps respond with a series of bounding boxen 
which the client may like to try instead.

Perhaps the API can be accessed by a queued, asynchronous system where a server 
is set aside to handle large queries one by one. Perhaps queries mailed to the 
server then returned by mail as and when they are processed.



Adrian Frith wrote:
> Hi folks,
> 
> Is anyone else having trouble getting through to the server? I can't
> open the Slippy map or the Java editing applet; I just get connection
> timeouts. I can get to the wiki without any trouble
> 
> It's very possible that my ISP is screwing something up, so I thought
> I'd check and see if anyone else is having trouble.
> 
> Thanks,
> Adrian
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk