Opened 5 years ago
Last modified 12 months ago
#18065 new enhancement
Add fix for "Ways with same position" warning in Validator
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | |
Keywords: | same position fix | Cc: |
Description
As a result of import in Canada there are lots of ways that generate "Ways with same position" warning in JOSM.
Usually these are inner rings of a wood polygon overlapping with identical water/wetland area, or vice-versa. There are probably hundreds of thousands of these in Quebec alone. Here's one example: https://www.openstreetmap.org/way/664902128.
Would be easy to fix such problems by removing duplicated water area and adding water tag to inner ring of the polygon. It would make import and error correction much easier.
Attachments (1)
Change History (9)
by , 4 years ago
Attachment: | closed_ways_with_same_position.osm added |
---|
comment:1 by , 4 years ago
I've attached a simple test case that demonstrates this issue. An auto-fix should allow merging of the duplicated ways provided that there is no tag collision.
comment:2 by , 4 years ago
I fear problems with a autofix outside downloaded area as relations might not be downloaded.
comment:3 by , 4 years ago
Perhaps limit the auto fix to cases where the relation is fully downloaded?
comment:4 by , 4 years ago
I would agree that this could be useful if we were not talking about data from Canvec imports. IMHO it is rather useless to remove the duplicated ways as both are very likely wrong regarding the shape. Whenever I looked at this data I wondered why it was ever imported. Typical examples: way 210659483 or way 210659214.
follow-up: 8 comment:5 by , 3 years ago
Hello - I've written a standalone utility to post-process a .OSM file to fix this exact issue. If someone is looking for a way to solve this issue, feel free to get in touch!
comment:7 by , 3 years ago
Is this problem still present in the latest Canvec data? Wouldn't it be better to fix the tool chain that produces that data?
comment:8 by , 12 months ago
Hey Zelone I am interested! Replying to zelonewolf@…:
Hello - I've written a standalone utility to post-process a .OSM file to fix this exact issue. If someone is looking for a way to solve this issue, feel free to get in touch!
Ways with same position example test case