Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

too many tracks in local cycleway relation? Database timeout triggered? #2938

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

Reporter: tourcyc
[Submitted to the original trac issue database at 9.26pm, Thursday, 6th May 2010]

Hi,

there is a local cycling route (or better a route network "water castle route") which
contains lots of tracks which add to a few 100 km. The last rendering update this week didn't
draw it anymore - the route (WBR) meanwhile vanishes on large scales as well: is there any
method to find out the reason except "complaining" here?

Updating this (large?) relation meanwhile takes about 30 seconds (via merkaartor)- so I
assume the database might have caused a timeout for the rendering engine.
http://www.openstreetmap.org/?relation=13239

I experienced as well a timeout browsing the relation (although not right now anymore,
might depend on the load):
http://www.openstreetmap.org/browse/relation/13239

@openstreetmap-trac
Copy link
Author

Author: Andy Allan
[Added to the original trac issue at 9.57am, Friday, 7th May 2010]

It's not a problem with the relation, it was a problem this week with the cyclemap not processing all relations. This has now been fixed and the tiles are regenerating.

In general, if a relation is so large that it causes timeouts or other difficulties in editing it should be broken into multiple parts. This is purely to make editing faster and easier for other contributors.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant