Opened 13 months ago

Last modified 13 months ago

#18637 reopened enhancement

Option of keyboard shortcut for "switch (background-)imagery view to next available (background-)imagery in list"

Reported by: anonymous Owned by: team
Priority: normal Milestone:
Component: Core imagery Version: latest
Keywords: keyboard shortcut background imagery Cc:


See title, is something already possible/available? If not, is this an idea which would be worth for implementing?

Thanks for reading in advance.

Attachments (0)

Change History (9)

comment:1 Changed 13 months ago by anonymous

(same question for iD-editor, see:

comment:2 Changed 13 months ago by skyper

Resolution: worksforme
Status: newclosed

Already implemented see Layer List Dialog.

comment:3 Changed 13 months ago by anonymous

@skyper thanks for pointing to the "LayerList". I think this is not the list i meant here. I talking about the imagery list, for which you have access in top main menu "Imagery", which means 10th menu item from left side.

(file | edit | view | mode | tools | more tools | data | selection | presets | IMAGERY | windows | public transport | audio | help).

comment:4 Changed 13 months ago by skyper

Resolution: worksforme
Status: closedreopened

comment:5 Changed 13 months ago by simon04

Similar to [Alt]+[Tab], but using ⯀ (to be defined) and for (not-yet-added) background imagery?

Say, the imagery menu lists A, B, C, D as available imagery sources fur the current location. When having only a data layer, pressing ⯀ should add A? When A is present, pressing ⯀ should remove A and add B? When D is present, pressing ⯀ should remove D and add A?

comment:6 Changed 13 months ago by anonymous

@simon04 exactly. Thank you for the way much better explanation of what i had in my mind.

comment:7 Changed 13 months ago by anonymous

Imaging use-case, there is a removed building and the mapper changed the existing osm-object from building=yes to demolished:building=yes (or to removed:building=yes or to razed:building=yes) maybe because he want to reduce the risk, that the building outline will be mapped again from the next mapper which uses the outdated aerial imagery (background data) as source.

I would think, the lifecycle object relics (demolished:*=yes or removed:*=yes or razed:*=yes) could be latest removed from the osm-database at all, when all different available (for the relevant area) aerial imagery doesn't show the old buildings any more. So it would be convenient to scroll/browse fast (via keyboard shortcut) through all the potential available aerial imageries for that area.

comment:8 Changed 13 months ago by mdk

Wouldn't it make more sense to select the imagery sources you need and cycle though them?

In my area (Zürich) JOSM lists 11 imageries, but 6 are not useful for me:

  • 2 are outdated: "Kanton Zürich Orthophotos 2014/2015" and "Kanton Zürich Orthophotos 2015/2016" are deprecated by "Kanton Zürich Orthophoto 2018"
  • 2 are based on OSM: "OpenStreetMap (Standard Black & White)" and "OpenStreetMap Carto (Standard)"
  • 2 has bad resolution (a pixel is about 10 square meter): " Central Alps in late September 2016" and " Western Alps autumn colors 2017"

Does it make sense always to cycle threw all of them?

comment:9 Changed 13 months ago by anonymous

@mdk Interesting,

My first idea was to have an option to go through all potential available imagery sources, just to check if there is one which could help me for a specific mapping (use) case.

Later on, it could be of course a good idea to select some of these imagery sources, which are not more of interest (so which have low priority, maybe because of far outdated data), and move these imagery sources to a kind of a black list. The black list items could be removed for the new keyboard shortcut scrolling function cycle.

Modify Ticket

Change Properties
Set your email in Preferences
as reopened The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to anonymous
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.