Closed samely closed 6 years ago
Date | N° detected error | Total Fixed |
---|---|---|
Wednesday 13th, July | 65652 | 1600 |
Thursday 14th, July | 49930 | 1526 |
Total | -- | 3126 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 18th, July | 44,430 | 1,992 |
Wednesday 20th, July | 39,380 | 2,574 |
Thursday 21th, July | 38,709 | 671 |
Total | -- | 5,237 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 25th, July | 18772 | 189 |
Wednesday 26th, July | 17878 | 0 |
Thursday 27th, July | 17891 | 0 |
Total | -- | 189 |
This changeset claims to be fixing a multipolygon, but it doesn’t look like the edited way was ever part of a multipolygon. Instead, it removed golf
and natural
tags added as part of iD’s Lateral Water Hazard preset. Was this intentional, and if so, should iD’s preset be corrected? According to the wiki, golf=lateral_water_hazard
is legitimate, although natural=water
might be inappropriate for a way.
/cc @bhousel
Thanks for catching this @1ec5.. Indeed iD was adding broken natural=water
polygons via the water hazard presets. I just fixed this! 🏌️
Hi! I think there might be a bug with your workflow/scripts/detection/etc. In changeset 44,381,869 mapper piligab broke a previously valid relation (relation 4,590,559 - Ballybetagh) with the changeset comment of "Fixing broken relation"
@rory Thank you for identifying this. This could have possibly happened due to flagging of the relation under ring not closed
in To-Fix Task. Usually, in the cases similar to the above, the missing way segment is added into the relation but wherein in this changeset 44,381,869, the way segment 326233195 was deleted from the relation. @piligab It would be great if you can check the relation in To-Fix task and clarify why the member was removed from the relation.
cc: @geohacker @Rub21 @poornibadrinath
Hi @rory! I'm not sure how this happened, maybe I could have confused any tags and deleted. I will be careful about my future editions. Thanks for your feedback.
cc. @bsrinivasa, @poornibadrinath, @Rub21, @geohacker
Date | N° detected error | Total Fixed |
---|---|---|
Tuesday 17th, January | 121 | 18 |
Thursday 26th, January | 31 | 1 |
Total | -- | 19 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 23rd January | 58 | 24 |
Wednesday 25th January | 52 | 41 |
Thursday 26th January | 13 | 7 |
Friday 27th January | 36 | 23 |
Total | -- | 95 |
Date | N° detected error | Total Fixed |
---|---|---|
Tuesday 31st January | 73 | 54 |
Thursday 02nd Febrary | 51 | 39 |
Total | -- | 93 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 06th Febrary | 46 | 3 |
Total | -- | 3 |
Date | N° detected error | Total Fixed |
---|---|---|
Thursday 16th February | 229 | 80 |
Friday 17th February | 128 | 84 |
Total | -- | 164 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 20th February | 53 | 17 |
Tuesday 21st February | 25 | 7 |
Wednesday 22nd February | 18 | 5 |
Total | -- | 29 |
Date | N° detected error | Total Fixed |
---|---|---|
Tuesday 28th February | 131 | 49 |
Wednesday 01st March | 74 | 20 |
Thursday 02nd March | 87 | 38 |
Total | -- | 107 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 06th March | 84 | 42 |
Tuesday 07th March | 24 | 12 |
Wednesday 08th March | 12 | 2 |
Friday 10th March | 69 | 43 |
Total | -- | 99 |
Date | N° detected error | Total Fixed |
---|---|---|
Wednesday 15th March | 133 | 17 |
Friday 17th March | 134 | 63 |
Total | -- | 80 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 20th March | 58 | 30 |
Wednesday 22nd March | 22 | 7 |
Thursday 23rd March | 48 | 3 |
Total | -- | 40 |
Date | N° detected error | Total Fixed |
---|---|---|
Wednesday 05th April | 80 | 45 |
Thursday 06th April | 7 | 5 |
Total | -- | 50 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 10th April | 365 | 67 |
Tuesday 11th April | 224 | 42 |
Wednesday 12th April | 182 | 102 |
Total | -- | 211 |
Date | N° detected error | Total Fixed |
---|---|---|
Tuesday 18th April | 21 | 14 |
Wednesday 19th April | 3 | 1 |
Total | -- | 15 |
Date | N° detected error | Total Fixed |
---|---|---|
Thursday 27th April | 247 | 43 |
Total | -- | 43 |
Date | N° detected error | Total Fixed |
---|---|---|
Tuesday 02nd | 247 | 35 |
Wednesday 03rd May | 47 | 27 |
Thursday 04th May | 30 | 9 |
Friday 05th May | 3 | 2 |
Total | -- | 73 |
Date | N° detected error | Total Fixed |
---|---|---|
Monday 08th, May | 26 | 7 |
Tuesday 09th, May | 4 | 4 |
Wednesday 10th, May | 3 | 1 |
Friday 12th, May | 31 | |
Total | -- | 43 |
Objective
Close polygons which are broken.
Tasks
The task below is updating everyday from Monday to Friday with the latest errors in OpenStreetMap
Changeset comment
Coverage
All countries in this list: https://s3.amazonaws.com/mapbox/to-fix/mbtiles.txt
Tools
P
)G
)Instructions
landuse
orbuildings
) delete this tag.not an error
of to-fixCommon issues
Delete the
building=yes
tagDelete the irrelevant node
How are we doing the error detection?
We are using osm-qa-tiles and osmlint selfIntersectingHighways
Who will work on these tasks?
Everybody is available to work on resolving these issues. However, @mapbox/data-team (Peru office) will work on everyday.
Question
Tag @planemad or @rub21 for questions.
cc. @mapbox/team-data