Please help me understand why Osmose thinks these boundaries intersect. Yes, they share a couple of nodes where they touch, but the ways don’t cross. Thanks.
Wondering if it’s because of this apparently missing segment: Way: 33199197 | OpenStreetMap ?
They do touch at Node: 5774137260 | OpenStreetMap I’m not familiar enough about Osmose to know if this would trigger a warning.
True, way 33199197 is not closed on its own, but this is not a problem as it’s part of a boundary relation. The other ways in the relation are strung together to form a closed loop. The ‘missing segment’ (way 1319775112) is also part of the relation.
1 Like
Yeah, the ways do touch at two nodes (5774137260 & 5774134850), but Osmose should not flag when two city borders touch. There are so many cases of that in the real world that it would not make sense to treat it as an error. I’ve edited other city boundaries that abut each other and weren’t flagged errors. I don’t think this Osmose issue is due to them simply touching (sharing a couple of nodes), but I can’t figure out what else it could be.
If you look at the code:
it’s using ST_Crosses(b1.linestring, b2.linestring). Which will return true for n5774137260 and false for n5774134850, because n5774137260 is located in the “interior” of the line string and n5774134850 is on the “exterior”.
TLDR; It’s a false positive, mark it so in Osmose.