Mechanical Edits/Mateusz Konieczny - bot account/moving FIXME to fixme
Page content created as advised on Automated_Edits_code_of_conduct#Document_and_discuss_your_plans.
Who
I, Mateusz Konieczny using my bot account
contact
message via OSM I will respond also to PMs to the bot account. In both cases I will be notified about incoming PMs via email and notifications in OSM editors.
What
Why
fixme=* is a standard way to mark fixmes.
FIXME=* is an unexpected and duplicate way to mark fixme and therefore retagging this duplicate to fixme=* would improve tagging without any information loss.
As result authors of QA tools would not need to discover that there is not only fixme but also its duplicate FIXME tag.
Direct reason
I encountered fixme note not listed in my tool - as it was using FIXME=*.
Numbers
Between 170 000 and 180 000 objects are expected to be edited. See https://taginfo.openstreetmap.org/keys/FIXME#map for a geographic distribution. Note that migrating FIXME to fixme in Poland is already approved (see Mechanical Edits/Mateusz Konieczny - bot account/moving FIXME to fixme in Poland)
How
FIXME=* tag would be replaced by fixme=* with the same value. Objects where fixme=* is present and not equal to fixme=* would skipped. Objects with other tags with FIXME in name would be skipped (for example source:FIXME=*).
An example ( https://www.openstreetmap.org/node/4725543372 ):
state before a mechanical edit:
state after a mechanical edit:
Changeset would be described and tagged with tags that mark it as automatic, provide link to discussion approving edit, link repository with source code etc. It would include at least
- automatic=yes
- bot=yes
- created_by=osmapi/1.0.2
- discussion_before_edits=https://lists.openstreetmap.org/pipermail/talk/2018-July/080916.html
- source_code=link to a github repository
Changeset would be split into small areas to avoid continent-sized bounding boxes. As this tag may be on extremely large objects (for example relations representing long routes) it may be unavoidable to make some edits with very large bounding boxes.
Edits would be generated by an osmapi based program.
Discussion
https://lists.openstreetmap.org/pipermail/talk/2018-July/080916.html
Mailing list - initial post
title
proposed mechanical edit - moving FIXME=* to fixme=*
text
fixme tag is a standard way to mark fixmes. Editors wishing to finish mapping in their area would (directly or indirectly, for example using JOSM) look through objects tagged with fixme tags.
FIXME tag is an unexpected way to mark fixmes, retagging this duplicate to fixme key would improve tagging without any information loss.
It would make development of QA tools easier as authors would not need to discover and implement support for this duplicated key.
Between X and Y objects are expected to be edited. See https://taginfo.openstreetmap.org/keys/FIXME#map for a geographic distribution.
Changeset would be split into small areas to avoid continent-sized bounding boxes. As this tag may be on extremely large objects (for example relations representing long routes) it may be unavoidable to make some edits with very large bounding boxes.
For documentation page see https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/moving_FIXME_to_fixme For documentation of my previous proposals (including both proposals that failed to be approved and approved ones) see https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account
Please comment - especially if there are any problems with this idea. Please also comment if you support this edit, in case of no response at all edit will not be made as there would be no evidence that this idea is supported.
Repetition
Redoing this edit in the future would be treated as a new mechanical edit with a new approval process.
Opt-out
Please comment in the discussion thread (see #Discussion).