You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've added a few columns to the edges table from street_network_to_sf():
edge_index: unique index of each vertex in R5's network.
osm_id: id from OpenStreetMap. It can be repeated because a single OSM feature can be broken down into multiple street segments with different characteristics.
street_class: "MOTORWAY", "PRIMARY", "SECONDARY", "TERTIARY", or "OTHER"
car_speed: maximum car speed in km/h
Now, we can map street classes and car speeds:
Next steps
But the real usefulness of this feature will be to allow users to change driving speeds in order to account for traffic congestion, simulate traffic calming strategies, etc (as in issue #289). For example, real driving speeds for select cities can be downloaded from Uber Movement, and those speeds can be linked to the output of street_network_to_sf() through the osm_id column.
So, to complete this feature, we need to:
allow users to modify the edges data.frame in any way they want, such as changing driving speeds, street classes, LTS, or if streets allow walking, driving and cycling (they can already do that, we just need to document it so it's done safely)
create a new function to read the modified edges data.frame and apply the changes back to R5's network (we need to decide if those changes will only be stored in memory during the R session or if we'll allow them to be 'permanently baked' into the network.dat)
Perhaps we can work on this feature after we release version 1.0.
The text was updated successfully, but these errors were encountered:
This looks really great! I agree the next steps could be included in a future version, perhaps v1.1.0. In any case, this would be a super nice feature indeed.
I've added a few columns to the
edges
table fromstreet_network_to_sf()
:Now, we can map street classes and car speeds:
Next steps
But the real usefulness of this feature will be to allow users to change driving speeds in order to account for traffic congestion, simulate traffic calming strategies, etc (as in issue #289). For example, real driving speeds for select cities can be downloaded from Uber Movement, and those speeds can be linked to the output of
street_network_to_sf()
through theosm_id
column.So, to complete this feature, we need to:
edges
data.frame in any way they want, such as changing driving speeds, street classes, LTS, or if streets allow walking, driving and cycling (they can already do that, we just need to document it so it's done safely)edges
data.frame and apply the changes back to R5's network (we need to decide if those changes will only be stored in memory during the R session or if we'll allow them to be 'permanently baked' into the network.dat)Perhaps we can work on this feature after we release version 1.0.
The text was updated successfully, but these errors were encountered: