Does the feature overlap with another feature about osm-compare HOT 4 CLOSED

Found two more cases where overlapping feature were bad edits

1. https://osmcha.mapbox.com/47340745/
2. https://osmcha.mapbox.com/47340745/

from osm-compare.

Working over this issue here: #135. It's based on the workflow described by @bkowshik ^

Tracking down the issues which are coming by:

• For relation type features, we get the bounding box of the relation and not the proper geometry. Therefore, we use individual relation members which are part of that relation to find any overlap with the existing features and also making sure it should not flag overlap members from the same relation

• Another issue which came by was closed ways geometry. So as these are not polygons , therefore it would be impossible to find feature with which it shares same osm area. To deal with that, we polygonized these kind of geometry in changeset-parser based on condition if it has id-area-key. Ref.

• Recently there was another issue of feature finding overlap with itself. And this is caused due to lag with a feature going to mapbox-streets and same feature coming this pipeline for processing. As if the formed happens early than the latter, then a feature would be flagged for overlapping with itself. To curb that from happening , we ignore the cases of feature overlapping with itself.

from osm-compare.

• http://osmcha.mapbox.com/47878397/
• A waterway created very close (almost touching) a highway.

from osm-compare.

Working in this PR : #135
Closing the issue

from osm-compare.