Before creating a task, segments should be merged if they have a node in common and have the same name about road-completion-old

[joostschouppe]

Copied over from issue 19

Current output is for every single segment. In the current REF data, a new segment begins at every junction (and only at junctions). In the case of a new development, that means the area is split into many tasks. A mapper will be tempted to do the entire area, so the other tasks need manual or automatic closing. In the case of a Maproulette Challenge, there would be no problem if it is updated very often.

In the case of false positives, the current single segment approach is a bit problematic. One mapper could mark the segment as false positive (or problematic in a different way). But it is a lot of work to map all the segmentes in the area as false positive. Then the next mapper might be less critical and still copy the data.
This might be solved by grouping segments together.

The disadvantage of any grouping, is that mapper feedback (false positive, too difficult, a comment) is then forced on the entire group. This makes the feedback harder to give (I could map some of this area, but a little part was wrong) and harder to process at the data source (I can't now simply match the feedback to my original data object, but just get some info about a wider area).

Suggested solution:

group output that is adjecent and has the same name under one object
join the main unique identifiers (several WS_GIDN or one streetname ID) to the task