-
Notifications
You must be signed in to change notification settings - Fork 0
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
traffic variable #12
Comments
This is only classifying for one timestamp! It is considering that if at least 10% of total segment length is with Recalling the paper definition
|
I think it does make sense, but this can be discussed. The idea here is to analyze if there is any conflict during the day. @temospena |
But how to define "any"? (Imagining that this is the max result of congestion of all segments during all day). |
Is there a possibility to use the road hierarchy levels (primary, secondary, tertiary - excluding residential, off road and links), as a proxy of this variable? Something to think and discuss. |
Considering that
googetraffic
package only allows to retrieve live information, and in raster, it would require to "wait" for some hours for the results of transit dynamics.On the other hand, the
mapboxapi
allows for requests of "typical" day and time (intervals of 15min), but with the cost of the max API requests per month. The results are retrieved in vector.I would suggest to explore the
mapboxapi
package, and make the requests at the final stage, for the cell candidates, and not for the whole city limit. This would lower the request amounts, and maybe provide a faster process.More info:
The text was updated successfully, but these errors were encountered: