Changeset hashtags feedback

[mikelmaron]

Ticket to capture actionable ideas from https://lists.openstreetmap.org/pipermail/talk/2015-November/074992.html

[mikelmaron]

• Document (or link to documentation) on how the OSMTM works in the wiki, including structure of changeset comments.
• Update guidance to encourage mappers to add their own insights in changeset comments
• Share more the downstream analysis of changeset comments, like http://osmgeoweek.org/metrics
• Make the point person for an OSMTM visible and contactable for feedback.
• Investigate potential use of other tags in the changeset

[xivk]

I just checked and not even JOSM remote control supports changeset-tags other than source:

http://josm.openstreetmap.de/wiki/Help/Preferences/RemoteControl

Other tags in changesets is at least going to require changes to both JOSM and iD.

[ethan-nelson]

@xivk the TM currently passes a changeset comment and source already to JOSM (https://github.com/hotosm/osm-tasking-manager2/blob/master/osmtm/static/js/project.js#L382-L394). The issue from the email is that mappers are only using the hashtags added default by the TM project creator and no other customization, so we need to work on either having project creators add additional non-hashtag descriptive changeset comments or training mappers using the TM to add more information. The former is obviously easier to implement in the TM framework.

[xivk]

I was checking this for @mikelmaron 's last item. "Investigate potential use of other tags in the changeset". I'm assuming he means changeset-tags.

Currently only source and the comment tag are supported via JOSM remote control. Changeset-tags are also described as 'labels' here:

http://www.openstreetmap.org/changeset/35413969

More info: http://wiki.openstreetmap.org/wiki/Changeset#Tags_on_changesets

[bgirardot]

I was thinking we might even include what the TM project has in the "entities to map" field in the changeset comments.

It would not directly address what the person actually mapped, but it would indicate what they were supposed to map.

We have kicked the idea around of creating our own custom iD editor, I could see a simple interface that takes the entities to map field, and makes a list of check boxes the mapper could check or uncheck to indicate what they actually did map.

e.g.,
X buildings
X roads
0 waterways
0 dams
(those 0's are empty checkboxes, not zeros)

[pbb72]

One (easy?) change could be to include the title of the task in the change set comment. Currently, only the ID of the task is included, but there is no guarantee that the task manager or it's ID system will exist forever. Including the task title as plain text would make the description more understandable, and lessen the dependency between the two systems.

[bhousel]

Just wanted to followup on this - I added a hashtags field to iD.

The field is a separate changeset tag called hashtags=*, which can contain a semicolon-delimited list of event hashtags (e.g. #thing1;#thing2;#thing3). The field is settable via the API, just like the comment field.

Any hashtags detected in the comment will be automatically extracted into this new field - so there is no rush to switch over the task manager code to use it. But it can eventually allow apps more flexibility to perform changeset analysis, and it frees up the comment field for users to add more meaningful comments.

related issues:
#703
openstreetmap/iD#2834
openstreetmap/iD#4223 (comment)
AmericanRedCross/osm-stats#48