|This article or section may contain out-of-date information: An experimental conflation plugin is now available in JOSM, and some of the content here has been moved there. See JOSM/Plugins/Conflation for more information
If you know about the current state of affairs, please help keep everyone informed by updating this information. (Discuss)
This page will outline possible designs for a conflation tool that works with nodes. This page will not discuss the value of or challenges associated with imports, other than to say that any contributor is expected to be aware of issues surrounding mass imports, and will exercise caution in using this tool.
This will present a user-centric workflow of syncing OSM data with external data.
- Convert Shapefile/Geodatabase/etc to an OSM XML file, using an appropriate field mapping.
- Load XML into JOSM and download OSM data for the same region in a separate layer.
- Start conflation plugin.
- Conflation dialog will ask user to specify:
- After analysis, user is presented with a dialog showing:
- Possible matches
- Nodes in Mine not found in Theirs
- Nodes in Theirs not found in Mine
- For matches, the user will be presented with another dialog that shows a table with:
- Each pair of nodes along with their respective attributes (presented in a table format with columns for A and B, and rows for each key)
- The distance between the nodes
- The cost associated with the match, perhaps color coded (green or 0 being a perfect match)
- A dialog to merge tags and location/geometry, perhaps reutilizing some of the conflict dialogs
- The user can then run the plugin again, perhaps with an increased distance threshhold, and repeat the above steps
- For the remaining nodes manual analysis is required (list of nodes ONLY in A and ONLY in B can be stored, and selected by clicking a button on the docked dialog)