a-b-street / a-b-street/speedwalk
Handle access tags(?)
- Dominant language
- Svelte
- Stars
- 24
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Right now, speedwalk does not handle OSM `access` tags.
It does use them for some special foot and bicycle cases, but not in general.
My question is: Is this all we need for our routing use cases?
The access data that is straight from OSM ist included in the export, so we can filter the export or treat them as special cases during routing ("allow private from from/to parts of the route at the start and end").
But I wonder if we are missing something for Speedwalk by not handling access tags explicitly.
---
One case that came up is, that the routable networks UI shows an routable island because there is no direct connection (which in this case is due to the main road being a non-footway-relevant highway=tertiary)
>
>
> https://a-b-street.github.io/speedwalk/#14.64/52.76118/13.16528
> https://www.openstreetmap.org/#map=16/52.76014/13.15905&layers=N
---
So I guess one thing we could do is to add a style that somehow shows private access differently. But the questions the are, `what the conditions are` (which `access`, `foot`, … tags to handle how) and `why we actually do this`, like what is the call to action…
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.