-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to order imagery layers? #1369
Comments
ELI has a best flag, however it is really only useful for ranking in a category. That said there is no real issue in creating a reasonable order from the available data (category, coverage, age and the best flag), the problems you are seeing are maybe due to the layer not being filtered out pre-build which is what I kind of remember ID doing for 'map' layers. In any case it's an ID issue. |
@AntMadeira As @simonpoole already mentioned this looks like an issue with iD. Please create an issue in the projects issue tracker: https://github.com/openstreetmap/iD/issues I guess it is an issue that there is a growing number of layers in the index, and mappers might judge the importance of layers differently. If there is something that could help in filtering / identifying the usefulness of imagery sources we should definitively think about it. E.g. we could generate for each source an ordering of recentness for each source based on the min/max years, category, and the imagery boundary. E.g. 0 = most recent imagery for the same category. 1 = second most recent imagery, etc. CC @tyrasd |
Thank you, @simonpoole and @rbuffat. I'll open a new issue with iD. |
there already exists issue openstreetmap/iD#8814 (and potential fix/improvement in pull request openstreetmap/iD#8826) for this. |
Recently, some imagery layers were added to iD, but some mappers are complaining that CyclOSM, for example, is the second layer in the list now, which shouldn't have such priority position. Is there a way to organize the layers for a given country by relevance in descending order?
The text was updated successfully, but these errors were encountered: