systemed/conflation

OpenStreetMap Live Conflation

conflation's Issues

Initial enhancement list

Improvements to editing/conflation

These improvements will make it easier for mappers to work with the data and integrate it into OSM.

• Provide a ‘done’ button so that an item can be marked as such and not presented to future users (this will require some authentication work, either against the OSM API or separately, so that people can’t just anonymously mark everything as done)
• Optionally save changes to an .osc file for further editing, rather than direct upload
• Display (externally-hosted) photos if referenced in the source data
• Douglas-Peucker ways when creating new features
• Support creating/modifying multipolygons
• Provide an option to add an OSM note rather than making an edit
• Provide a freeform tag editor
• Consider a background tint on the Leaflet map for edits that have already been made
• Tilemaker option to not include objects with null tags

Improvements to conflation logic

• Improve tag-matching when selecting candidates (incorporate OSM data rules so that clashing features aren’t suggested)
• Improve geometry-based selection of way candidates
• When creating waynodes, suggest creating a new node within the way, closest to the source point. (Typical use-case: an island crossing next to a junction. Currently the suggestion is usually the junction node, whereas actually the crossing is a few metres further along the road)
• Offer multiple OSM objects as a potential edit (typically a 'chain' of ways along a road)
• Support splitting ways
• Support connectivity for new ways (auto-join to existing ways at start/end/crossing)

Moving towards a hosted service

These potential improvements will make it easier for data owners to upload their data so that OSM mappers can integrate it.

• Provide a WYSIWYG UI for tag remapping
• Auto-generate config.json for tilemaker
• Provide an improved, generic vector tile style file
• Offer a hosted service where data owners can simply upload shapefiles without having to spin up a server
• Consider any changes required to deal with massive files (e.g. nationwide)

Other enhancements

• Serve GeoJSON-like webservices so that data can be directly integrated into iD (see openstreetmap/iD#4164, openstreetmap/iD#4633)
• Convert source data into well-known file formats (.osm, .kml, .geojson) for use in JOSM, Potlatch and other OSM editors