Feature request: option to keep summary information about origins and destinations associated with each link

[Robinlovelace]

Use case: you want to know the main areas that will benefit from investment in a particular bridge. Illustration for Waterloo Bridge:

This suggests that many of the users are coming from the south of the river to access destinations just north of the river.

I recall conversations at FOSS4G last year in Florence about ways to do this on-the-fly, that was impressive. In this case it's just returning all the routes that intersect with the view area after zooming in and clicking 'Free lines'. Not the most intuitive interface or efficient implementation, but works to illustrate the concept.

Source: https://www.pct.bike/m/?r=london

[dabreegster]

Would it be more useful to see origins and destinations (with counts) involved with that link? Or the weighted route network, for every route intersecting the link, like shown above?

[Robinlovelace]

I think seeing all origins, and weighted network for every intersecting route, would be most useful. The example above doesn't show a weighted route network: just the top 30 routes that go over the bridge.

[Robinlovelace]

Heads-up @temospena this is the issue that I mentioned. My be better renamed as 'option to keep routes'? Excactly which bits of info per route we need is TBC but distance, list of OSM IDs and optionally geometries would seem a reasonable starting point.

[Robinlovelace]

P.s. greetings from Ireland, looking forward to seeing talk on ATE mentioning digital tools.

[temospena]

the option to keep routes would be super useful if planning to do socio-economic-environmental benefits estimation, when you need to compare distances traveled between ODs with other modes. Geometries are also useful, at least to validate some route profiles, when you need to visualize if the algorithm custom-built is making sense or not.