#5812 closed enhancement (duplicate)
lower imagery resolution than possible
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | |
Keywords: | Bing, WMS | Cc: |
Description
in version 3751 when WMS support was added to the core, the displayed imagery has a lower resolution than with the slippymap plugin in previous versions. This makes it more difficult to map and therefore reduces the quality of the work output.
Though the WMS now seems to be implemented quite well :)
Attachments (1)
Change History (5)
by , 14 years ago
Attachment: | josmcompare.png added |
---|
comment:1 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
What is your value of imagery.tms.max_zoom_lvl
? Which area were you looking at?
To get this value, look at "Max zoom lvl." the settings tab of the tms/wms tab or search for this setting in the advanced settings tab.
Try increasing the value until josm loads the white "no image" tiles from bing; then decrease by one.
comment:2 by , 14 years ago
Type: | defect → enhancement |
---|
okay, the default value is 18. I can increase it up to 20 without getting empty tiles. If I'm right this depends on the available maximum resolution in your area.
When there's no way for JOSM to distinguish between empty and filled tiles there should be a button or menu allowing the user to edit imagery.tms.max_zoom_lvl
easily.
For example an addition to the context menu of the background (Auto Zoom, Auto load tiles, Load tile, Show tile info...) like a dropdown context menu allowing to choose the value in a list. Alternatively the same dropdown menu inside 'Imagery' in the menu bar.
comment:3 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | needinfo → closed |
All that remains is already mentioned in #5741.
two screenshots of different JOSM versions mixed together to show the difference in imagery quality