image/svg+xml
way37
way56
way522
way156
way37
way56
way522
way156
routerelation#42
way1
way2
way3
way1
way2
way3
routerelation#83
way1
way2
way3
way66
way537
way16
superrouterelation#66
way66
way537
way16
routerelation#44
way1
way2
way3
routerelation#83
way347
way370
mp#148
mp#10
mp#113
mp#10
mp#4
route#90
route#94
route#99
route#92
boundary#43
smp#40
route#81
conditional area,depending on tag
always an area
always an area
nodes
ways
closed ways
routes
multipolygons
superroute
(super?)multipolygon
keepverylongroutesmain-tain-able
keepverylargeMPsmain-tain-able
definearea withinone or moreclosed rings (*)
(*) may be thought as "closed routes", i.e. multiple concatenated osm-ways that fully encircle areas;however, keep in mind that multipolygons in OSM were specified to contain way-primitives /only/,"reusing" way-concatenating-relations as /outer/ or /inner/ in a MP is currently consisdered invalid
allow way-concatenating-relations(such as route, boundary types)to take part in multipolygons,as 'outer', 'inner' members (**)
?
(**) this will also enable lighter landmass relations as they directly reference their encasing boundaries(-relations)
routes concept is held basic; it's about the basicsless the specialities used by specific route types(such as backward and forward membership)
010110010011010110010011
010110010011010110010011
on OpenStreetMap data structures