You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Then apparently it works out the size of the relation, and zooms to an appropriate level. (Takes approx 8 seconds for me)
I actually came here to report that it was a bug and didn't work at all. Only on trying to reproduce did I realise that it eventually zooms in and shows the relation correctly. Hopefully there's a way of making this behave a lot more nicely, by guessing an approximate zoom level first or something.
(Not sure if this is mapnik or something else. Guessing mapnik.)
The text was updated successfully, but these errors were encountered:
Author: Ldp [Added to the original trac issue at 9.54am, Saturday, 10th July 2010]
Not mapnik.
It's not really a bug either. Fetching a relation from the API can take some time, and the extent of the relation is not known to the website until the API delivers that relation.
As a relation can be anywhere in the world, there's no other thing to do than to show the entire world at first.
Author: TomH [Added to the original trac issue at 8.13am, Monday, 12th July 2010]
As Ldp says, the problem is that we don't know the bounding box for the relation until the API has returned the data and that is what causes the delay - there isn't a lot we can easily do about that.
Reporter: stevage
[Submitted to the original trac issue database at 2.45pm, Thursday, 8th July 2010]
I actually came here to report that it was a bug and didn't work at all. Only on trying to reproduce did I realise that it eventually zooms in and shows the relation correctly. Hopefully there's a way of making this behave a lot more nicely, by guessing an approximate zoom level first or something.
(Not sure if this is mapnik or something else. Guessing mapnik.)
The text was updated successfully, but these errors were encountered: