Recently, the iD editor added validation layers / Q/A-layers.
They allow mapper to see validation issues inside the mapping UI and fix them right away.
The github-tickets list for "validation" provides an overview of validation layers / Q&A-layers (but also inline validation).
This data set looks like a great addition to this validation list.
However, as far as i can see this app needs an API first, that would allow the iD editor to show and finish the issues. Things like
list all issues for a given bounding box
per issue, a list all features that area involved (iD can then over+highlight the roads/houses that are "involved" with the issue)
provide an issue type id that can be used for translations inside of iD
allow Id to mark issues as "ignored" or "solved" (similar to the KeepRight solution)
a unique issue id and permalink that can be used by iD to link to the issue and also reference it inside the changeset-tags.
On the other hand – since the dataset is limited to a few countries –, iD probably needs to extend the feature that lists all available validation layer to be map-location-sensitive. Like with the "Deutsche Bahn" data layer that iD only shows in Germany.
Recently, the iD editor added validation layers / Q/A-layers. They allow mapper to see validation issues inside the mapping UI and fix them right away. The github-tickets list for "validation" provides an overview of validation layers / Q&A-layers (but also inline validation).
This data set looks like a great addition to this validation list.
However, as far as i can see this app needs an API first, that would allow the iD editor to show and finish the issues. Things like
On the other hand – since the dataset is limited to a few countries –, iD probably needs to extend the feature that lists all available validation layer to be map-location-sensitive. Like with the "Deutsche Bahn" data layer that iD only shows in Germany.
PS, thanks for the tool and the update at https://www.youtube.com/watch?v=AIBi2aD-4n0