Why are streets often split into several ways on OSM? examples:
|
Streets are split when one or more properties are different along the street. A non-exhaustive list of such properties would include:
Streets are naturally represented as several ways if they are not linear, or if they are dual carriageways. If a street is split it is best NOT to recombine sections unless using JOSM which forces a check on all mismatched tags. Creating multilinestring topologies representing all parts of a named street should be done outside OSM as a processing step on an extract. For most streets this is trivial, but there are a number of well-understood exceptions which can create problems and for which there are no good widely available solutions. |
Ways are split when the attributes/tags change (and when relation membership changes too). A random example: the speed limit changes, you slplt the way and apply the new speed limit. This does lead to sometimes very small segements (joke for old hands), but is perfectly OK. |
Are they Dual-Carrage ways; with a barrier between the two one way parts? They can be split to help routeing especially when only one half of the road links to a paticular side road. How does splitting a road help the router?
(06 May '14, 07:31)
scai ♦
4
I think they're referring to the separately-mapped oneway parts as opposed to a single way representing the entire dual-carriageway, but that has nothing to do with the original question.
(06 May '14, 18:39)
alester
the router can more easily handle when traffic can't cross between the carrageways at junctions
(01 Mar '16, 19:11)
Govanus
|