You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Technically there is no geometry fix needed here, the entire feature is just being deleted.
It might be worth investigating if there are use cases where simply deleting the feature is not the best solution (e.g. a missing member should be added, or some tags should be moved to the member relation), but this seems like a good fix suggestion candidate.
There are cases such as this island where certain tags should be added to the member Way before removing the redundant relation. I am not sure if this can be generalized enough to be turned into an autofix suggestion. Would it be safe to e.g. include two autofixes here, one to delete the relation and another to add any missing tags to the member way?
As many suggestions as needed can be included to resolve a problem, as long as we are confident that they are the correct solution. For the island in question I think it would be correct to include a fix suggestion to add tags to the way and another to remove the relation.
Which Atlas check is the fix suggestion related to?
One-Member Relation Check
Description: https://github.com/osmlab/atlas-checks/blob/dev/docs/checks/oneMemberRelationCheck.md
Script: https://github.com/osmlab/atlas-checks/blob/dev/src/main/java/org/openstreetmap/atlas/checks/validation/relations/OneMemberRelationCheck.java
Describe more details of suggested fix(es)
Suggested Fix 1:
Type of fixing: Geometry fix
Operation: Delete
Suggested Action: Remove the flagged relation
Is there any code enhancement needed if adding the fix suggestion component?
No
The text was updated successfully, but these errors were encountered: