Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cycle crossing inclusion in data packs? #126

Closed
hulsiejames opened this issue Sep 1, 2022 · 3 comments
Closed

cycle crossing inclusion in data packs? #126

hulsiejames opened this issue Sep 1, 2022 · 3 comments

Comments

@hulsiejames
Copy link
Collaborator

The tag cycleway="crosing", described as Tag added to way bicycle crossing mapped as separate way., occurs on a number of linestrings a number of times for Leeds, specifically 230 within the "Leeds" LAD boundary obtained from osmextract.

Screenshot from 2022-09-01 15-36-53

Specific exmaple

From taginfo there are approx. 81,000 of these tags, mostly centred in Europe.

Additionally, only 900 of these tags occur on nodes (in other words, I don't think we need to be too worried about checking the "lines" layer of OSM data to look for cycling crossings)

Is this something that would be useful to contain in the infrastructure data packs? Personally I think so

@Robinlovelace
Copy link
Contributor

Very good idea, hadn't noticed that tag before, big 👍 from me!

@GretaTimaite
Copy link
Collaborator

I think they are essential. Crossings are explicitly mentioned in the inclusive mobility, so I assume they are important in the context of LTN1/20 as well.

The only question is if it can provide any additional information on the type of a crossing. I think in IM function I classified them broadly in two groups. Not sure if it would be of use to you as well.

@hulsiejames
Copy link
Collaborator Author

oi_cycle_crossings has been added to the openinfra package and data packs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants