Iteration on coherent network results

[Robinlovelace]

In conversation with Angus and Malcolm, we're talking about improving this result from a policy perspective.

• [x] Overall it should mostly be arterial
• [ ] Would be nice if it could grow

[Robinlovelace]

We should adjust the settings so that we don't include lots of residential / off road routes:

[Robinlovelace]

Ideas on how to do this can be found in this paper by @mszell (any input welcome Michael!): http://arxiv.org/abs/2107.02185

[mszell]

Very nice tool! Thx for asking. In our project we had the same issue with such residential zig-zag paths. I don't have the solution but there could be different methods to resolve this. We are experimenting with COIN right now, for example: https://journals.sagepub.com/doi/10.1177/2399808320967680 (implemented in momepy). Or, a heuristic could be to penalize turns or to improve certain metrics. All work in progress, happy to let you know our preliminary results once we have some..

[Robinlovelace]

Awesome, thanks for the suggestion and quickfire response Michael, can keep you posted as things progress! @wangzhao0217 literally working on this with me right now, hope to be able to share ideas back with the community at some point..

[Robinlovelace]

Reviving this in conversation with @wangzhao0217. We're in a good place, with an MVP UI deployed on the test website thanks to great work by @mvl22 shown below.

However, the groups do not make sense from a transport planning perspective. Group 1 should be what you build first but currently the group orders are random. And groups are more like areas, rather than the 'skeleton' of the network for the first groups and the 'leaves' for the latter groups in the cohesive network, as described in the GrowBike method and paper by @mszell.

The first group should represente the bit that transport planners should build first. Which is usually from the centre, or from the largest residential area to the economic centre, along the route/corridor with the highest demand.

This is what we have currently:

Source: https://nptscot.github.io/#/cohesivenetwork/#11.67/55.9385/-3.184

Thoughts on best next steps on this very welcome.

[Robinlovelace]

BTW @mvl22 good example of the dynamic URLs that change when layers are changed. Should the Cohesive network UI element not be expanded though? Reproducible example: click on the link above and you see this:

However you should see something more like this I think:

Right? We should track this in the UI codebase if so.

[mvl22]

Yes.

I haven't yet reworked the accordion to have a proper hierarchical relationship between the titles, the layer-enabling buttons and the controls within layers. Once that is done, auto-opening a section, and indeed getting the parameter-level URLs in place will be possible.

[Robinlovelace]

Latest comments from @anguscalder:

We should get more continuity, e.g. making the path continue.