Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add street class and car speed information to output of street_network_to_sf() #290

Closed
mvpsaraiva opened this issue Aug 22, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@mvpsaraiva
Copy link
Collaborator

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:

image

image


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.

@mvpsaraiva mvpsaraiva added the enhancement New feature or request label Aug 22, 2022
@rafapereirabr
Copy link
Member

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.

@rafapereirabr
Copy link
Member

Closing this issue in favor of @289

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants