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
Custom imagery layer is not recorded proper in changeset tags #663
Comments
Did you make an edit after setting that custom url? |
@ansis Uncertain about this. Will reproduce. |
retested. After doing an actual edit it printed it like expected. multiple imagery sources are recorded as a semicolon separated list. Closing this as it's no bug but was wrong testing on my side.
|
I suspect you have misunderstood the issue. This is not about incorrectly crediting Google Maps, it is about NOT allowing Google Imagery as a background layer. We do not have permission or a licence to use Google's imagery. Some people, especially newbies, do not understand this so would use Google Imagery (or indeed Google maps layers) if we let them. We must put in place a method to prevent this - preferably with an explanation as to why this is not permitted. The integrity of OSM data will be compromised if data is copied or traced from sources we have no licence to use. |
My mistake |
In this changeset I had Google Maps as a custom imagery background.
http://api06.dev.openstreetmap.org/browse/changeset/17660
It prints "imagery_used = Bing".
I suggest in case of custom imagery to include the actual URL being used. Mention this to the user when setting up the layer to prevent from surprises.
The text was updated successfully, but these errors were encountered: