id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
12313	"Core enhancement or plugin to query editor-imagery-index and notify user if ""better"" imagery might be available"	bgirardot	team	"Hi all,

It would be very useful, and actually important to OSM data quality, if JOSM could in some way support querying the https://github.com/osmlab/editor-imagery-index project to see if ""better"" imagery is available for the area in the view port.

The two main reasons are:

1. There might actually be ""better"" imagery available for an area and it would be good use it if it actually is ""better"" (better/best in quotes because it is obviously dependent on context what ""better"" or ""best"" means, I still slightly skeptical of the concept)

2. iD now defaults to the imagery listed as ""best"" in that imagery index so it is important that josm users have easy, obvious insight into what imagery might have been or will be used to map an area. We can find out about existing mapped objects by doing a history on object of course, but that can be misleading depending on how the object was mapped and doesn't address what imagery will likely be used in the future by iD users. What is important is to know what iD editors are using currently when I am reviewing mapping in an area or about to start mapping in an area.

If the code finds the imagery-index suggests a ""best"" imagery set for the area in the view port, it could offer the option to load that imagery layer with a click.

This is really an effort to make sure mapping and imagery use is harmonized as much as possible for consistency.

It is not that much different in concept than how JOSM queries the off-set database now to suggest imagery might need alignment. Except in this case, it will query the editor-imagery-index and suggest there might be better imagery in general to use instead.


"	enhancement	closed	normal	17.02	Core imagery		fixed