osm2streets terminology and structure about osm2streets HOT 5 CLOSED

* `Road`: a collection of Lanes (and Buffers), travelling in the same direction; A "half street" if you will, or a slip road or slip lane.
* `Street`: a collection of Roads (and cycletracks/footpaths) that all run (mostly) parallel to one "centerline", representing the whole corridor, "building to building".

* `Intersection`: the area where multiple lanes of travel overlap and the road endpoints that join it.
* `Junction`: A collection of Intersections (and some Roads) that make up one "junction". E.g., a roundabout is one Road and one Intersection per (single carriageway) arm.

This is one thing that is a bit weird, mostly "road" and "street" being so different.

I would like to work with the network as a directed graph, and so each direction is it's own edge which can be treated independently. What should the term for that edge be? Why not "road"?

The two distinct levels will be very useful I think. E.g. a route would be calculated in the RoadNetwork but directions would be described in the StreetNetwork: "left at A street, right at B street, 4th house on the right."

from osm2streets.

This is one thing that is a bit weird, mostly "road" and "street" being so different.

Agreed. There are all these more nuanced terms for street, road, avenue, etc, but in my rough understanding (probably from the stroad video by Not Just Bikes), a road is a larger, more car-oriented form of a street, with less driveways and POIs along it. That's totally unrelated to the definitions here, but it may be confusing.

If a Road is meant to be one direction only, I wonder if "Edge" or "HalfRoad" or "DirectedRoad" could be more clear. I am still not entirely sure I understand how bidirectional cycletracks on one side of a road (common term) or a contraflow bus lane would fit into this.

I like the idea of having two "layers" of abstraction, with Streets and Junctions possibly just being containers of lower-level Roads and Intersections.

I would like to work with the network as a directed graph, and so each direction is it's own edge which can be treated independently. What should the term for that edge be? Why not "road"?

Why not "edge" or "half-road", just to clearly divorce from common terms?

from osm2streets.

I wonder if "Edge" or "HalfRoad" or "DirectedRoad"
"edge" loses context too quickly, so HalfRoad and DirectectRoad are sounding good. OnewayRoad? OneRoad?

Do we use Corridor instead of Street to keep both sides of "stroads" out of the namespace. A Corridor is a list of OneRoads and Buffers or something? Corridors and Junctions are what you would use to draw a metro map, for example.

from osm2streets.

I have come around to preferring "RoadWay" for the "half street" concept for most of the reasons that they are called "ways" in OSM. A "two way road" is made up of two RoadWays? Yep, sounds about right to me.

from osm2streets.

"Corridor" and "Curb" used to talk about this in a great talk at SotM US: OSM can help Inventory and Manage the Curb - Daniela Waltersdorfer

from osm2streets.