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
Add a field to notes to indicate what software is creating them #385
Comments
We did discuss this at EWG a few weeks back, but I can't remember what the plan was beyond the fact that @zerebubuth wasn't impressed with my plan to leverage the oauth clients ;-) There should be something in the minutes though. |
relevant meeting was http://www.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2013-06-17
|
If this is simply about identifying with which user agent the user created or commented the note, why not simply use the UserAgent from the HTTP header? |
That wouldn't differentiate between Craigslist and the OSM website and the OSM website on a browser in the field though would it, unless you also included the referrer or something? |
This would help with streetcomplete/StreetComplete#2692 (comment) but in general it's very useful for mappers to know if the note came from a survey app, or website. Right now some apps embed this content within the description |
As more apps and external entities like Craigslist start using our "Notes" feature, it would be helpful to see where notes are coming from.
For example if they come from Craigslist, I know that the user was looking at a custom rendering that may be several weeks out of date. If it is from a smartphone app it means the user was probably in the field and had eyes on the situation when the note was created. If it was created in JOSM then it is likely an armchair mapper making a note of something he didn't have time to fix up while doing some other mapping.
Basically I want a "created_by" tag for notes just like changesets have now. Obviously notes don't have tags and I don't see much use in allowing arbitrary tagging on notes so it should just be its own field.
The text was updated successfully, but these errors were encountered: