May I suggest the following work flow: 1) Agree upon 2 dates sufficiently spaced i.e. 2 weeks apart 2) First date, add the new tag, leave the old tag in the system. This will not break anything, and from that date data consumers know they can start migrating their renderers, harvesters, or whatever into the new scheme without loss of data integrity 3) Run sanity checks on the data, maybe manually correct slips such as type=sewer -> substance=sewage if needed 4) On Second date remove the unwanted key, objects where the key should remain should have been flagged by now, and data consumers should all be on the new scheme also. 5) Define an interval to re-run the scripts if it is probable that anybody still might use the old scheme.
This should be the general rule for mechanical edits when migrating tagging schemes. Also make sure that editors such as Potlatch2, iD, JOSM and Merkaartor, all have corrected their presets by the second date. If old scheme is stuck in the preset than it is likely that old scheme will continue to be used. Also data consumers must be aware when new tagging scheme is in the editor presets as that WILL affect their data. Aun Johnsen > On Jan 4, 2015, at 09:06, [email protected] wrote: > > Rainer, others and myself should be focused on consistency, versatility of > tags, doing things (like tag migration) once.
_______________________________________________ talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk
