Closed dcooley closed 3 years ago
Thanks Dave, that was actually a stuff up with my latest geodist
update. I'll go back over there and fix, but in the meantime the above commit fixes the problem at this end.
Other topics while we're here: great work with your twin cities analyses - @noamross is doing very similar stuff for NY state, disaggregating census data onto building addresses. I told him about your work, so you may hear from him.
ah cool. Look forward to seeing what he's doing. You may also have been able to recognise {dodgr} being used in the background. As we type I'm now building an interactive version where the user can change road-types on-the-fly, which is what lead me to this bug.
Cool! I was wondering whether there was some dodgr-izing going on behind the scenes there. So was each layer of the animation then a separate dodgr
analysis? You might also be interested in upcoming #144, with which you'll be able to extract proportions of each trip that go along some particular category of way, and so do things like ascribe to each point a value proportional to the relative length of bicycle-borne journeys originating from that point (and maybe going to defined destinations, or wherever) which they have to spend travelling right next to cars. Those proportions will come out as an additional matrix alongside the current distance matrix, yet be calculated with almost the same computational efficiency.
Yes! #144 sounds almost exactly like what I'm putting together. Specifically, this shiny I'm building will show cycling vs driving to schools, and calculates various stats, including 'time spend on same road as a car'. It's very much a prototype and there's definite room for improvement, so I'll keep an eye out for the developments over here.
I've tried this with the CRAN and github versions and get the same error when trying to weight an
sc
streetnetSession Info