Data layers can obscure imagery

[mikelmaron]

A neighborhood or city polygon can make it hard to see the imagery and trace other features. You can adjust brightness of background, but not adjust the visibility of the data layer.

[tomhughes]

Those large polygons also have the nasty effect that any click in the background selects the big polygon, which makes it hard to clear the selection (escape will do it) and leaves you with a mysterious command menu floating wherever you clicked.

[jfirebaugh]

Yeah, that problem specifically is #542.

[Tartamillo]

I also find extremely annoying to edit paths and tracks on areas already covered with landuse areas. Not only this stuff gets in the way and risks being destroyed accidentally, but a green cast from landuse overlayed on green Bing imagery makes hard to see things.

I think that a couple of checkboxes to hide and/or lock this kind of data can find its place in the right hand drawer.

[vdeparday]

Maybe it is there but I could not find it. Even just a simple checkbox to turn on and off the data layer would be great because when doing data quality checking it is really hard to tell the quality or to correct without being to see what is underneath a building outline for instance even with 100% brightness on the imagery.

[vdeparday]

I am still regularly hitting this limitation especially in heavily mapped area.
Would someone involved in the code base know roughly how difficult it would be to create a checkbox to turn on/off the data layer to be able to see what is underneath even temporarily? I looked quickly but it seems like would be more complicated than just using js to turn on and off a layer but not entirely sure as I don't know the Id code base.

[samanpwbb]

@vdeparday this is days away from being fixed: #2357

[vdeparday]

awesome, much more than refined than a simple checkbox, looking forward to it, thanks !

[jfirebaugh]

Addressed by feature filtering (#2357).