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.
Reporter: LonelyPixel [Submitted to the original trac issue database at 1.08am, Monday, 2nd March 2009]
When using "Download", selecting a bookmark and letting Merkaartor do its work, the map view is zoomed to a scale of 20 km when it should really be like 1 km. This makes all the map appear as a tiny pixel cloud in the middle of the window and you first need to zoom in a lot to see anything. This hasn't been so a month ago.
The text was updated successfully, but these errors were encountered:
Author: LonelyPixel [Added to the original trac issue at 5.09pm, Tuesday, 3rd March 2009]
The issue is unpredictable. Once it zooms well enough (one step out of the downloaded bounding rectangle), then it zooms like from mars or so a few times, always with a different scale. I could not infer any relation between the scale on application startup and the resulting scale after downloading the map data. It looks random to me.
Author: RobertJ [Added to the original trac issue at 12.12am, Sunday, 8th March 2009]
i noticed this too, merkaartor zooming out like mad after a download and had the suspicion that it zoomed out to the largest relation (red rectangle).
but this bug seems to have been temporary, only for a day or two.
lonelyPixel, can you check this again in a current build?
Reporter: LonelyPixel
[Submitted to the original trac issue database at 1.08am, Monday, 2nd March 2009]
When using "Download", selecting a bookmark and letting Merkaartor do its work, the map view is zoomed to a scale of 20 km when it should really be like 1 km. This makes all the map appear as a tiny pixel cloud in the middle of the window and you first need to zoom in a lot to see anything. This hasn't been so a month ago.
The text was updated successfully, but these errors were encountered: