Opened 9 years ago

Closed 9 years ago

#2938 closed defect (fixed)

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

Reported by: tourcyc Owned by: Andy Allan
Priority: minor Milestone:
Component: opencyclemap Version:
Keywords: Cc:



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.

I experienced as well a timeout browsing the relation (although not right now anymore, might depend on the load):

Change History (1)

comment:1 Changed 9 years ago by Andy Allan

Resolution: fixed
Status: newclosed

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.

Note: See TracTickets for help on using tickets.