Closed Robinlovelace closed 5 years ago
Merging #50 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #50 +/- ##
=======================================
Coverage 65.53% 65.53%
=======================================
Files 13 13
Lines 383 383
=======================================
Hits 251 251
Misses 132 132
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 7be13e8...9ca704c. Read the comment docs.
Why are you not pushing @Robinlovelace? :)
I'm not sure what this means - are these point counts of traffic data? And do you mean that we then need a corresponding road network? And does that in turn mean that dodgr
could be used to generate flow estimates for the whole network using the point counts as sources? That would be cool!
The points were previously just points where data was collected. Now I've added actual travel data by mode, e.g.
#> YEAR MONITORING TYPE TOTAL FLOW ARX PEDAL-MOTORCYCLE ARX CAR
#> 1 2015 LBS 20MPH monitoring 9203.857 639.2857 7702.7143
#> 2 2015 LBS 20MPH monitoring 10787.143 960.5714 8463.0000
#> 3 2015 LBS 20MPH monitoring 1148.571 290.8571 745.4286
#> 4 2015 LBS 20MPH monitoring 2296.429 270.5714 1635.8571
#> 5 2015 LBS 20MPH monitoring 7030.857 146.8571 6152.1429
#> 6 2015 LBS 20MPH monitoring 7771.000 122.5714 6868.7143
Yes I think it's a cool dataset. Many possibilities with it. 1st thought is that it could be useful for testing geoplumbers
's ability to visualise multiple layers. Route network data should be added to the list in #45, if the network had flow estimates that would increase it's value I think as will be the kind of thing we'll want to visualise repeatedly in the (active transport) future.
I've only joined the pedal cycle flow data to the sf
object traffic
though to avoid 'data overload':
#> total cycle_or_motorcycle av_speed year geometry
#> 1 19991.0000 1599.85714 19.950 2015 -0.11124, 51.49595
#> 2 3445.0000 561.42857 15.100 2015 -0.10723, 51.49412
#> 3 14801.8571 269.42857 25.400 2015 -0.07460, 51.42772
#> 4 34337.1429 655.71429 18.950 2015 -0.07426, 51.42598
#> 5 676.2857 55.85714 14.300 2015 -0.07075, 51.48484
#> 6 16431.4286 515.00000 26.525 2014 -0.07082, 51.45261
Belated answer to your question @layik :
Because it's quite a lot of data: 500kb+
I think it's worth it though. Your package, your choice. + I like branches :deciduous_tree: !
I am happy.
Great. Lots more pretty visualisations can result from this interesting dataset. Very interested to see the relationship between the traffic and crash datasets.
I also updated the traffic dataset so it actually contains traffic data. Just a simple road network to add. @mpadge as the creator of the awesome osmdata are you up for giving that a shot? Suggest the name
traffic_network
for consistency (all these Southwark datasets now start withtraffic
).Reprex illustrating the new datasets:
Created on 2018-10-10 by the reprex package (v0.2.1)