Skip to content
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

Closed
stephankn opened this issue Feb 6, 2013 · 6 comments
Closed

Custom imagery layer is not recorded proper in changeset tags #663

stephankn opened this issue Feb 6, 2013 · 6 comments

Comments

@stephankn
Copy link

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.

@ansis
Copy link
Collaborator

ansis commented Feb 6, 2013

Did you make an edit after setting that custom url? imagery_used is only set for layers displayed while an edit is made.

@stephankn
Copy link
Author

@ansis Uncertain about this. Will reproduce.

@stephankn
Copy link
Author

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.

imagery_used = Custom (configured);Bing

http://api06.dev.openstreetmap.org/browse/changeset/17677

@chillly
Copy link

chillly commented Feb 6, 2013

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.

@ansis
Copy link
Collaborator

ansis commented Feb 6, 2013

@chillly nope, not misunderstood. The issue discussing that is #662

@chillly
Copy link

chillly commented Feb 6, 2013

My mistake

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants