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

allow for optional import of intersection data (eg official data, or externally processed) #302

Closed
carlhiggs opened this issue Jun 16, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@carlhiggs
Copy link
Collaborator

Currently intersections are represented using the consolidate intersections function of OSMnx, however as per #138 this doesn't necessarily work well in all settings. In brief, a tolerance parameter (metres) is used for simplifying the network, however this is designed more for use in localised areas without variation in network structure. In contrast, for whole city analysis with broad variation in network topology as well as in complex features like round abouts, it may be desirable to use an alternative data source or externally processed (cleaned) data to represent intersections more accurately.

This is simple to implement, by allowing users to specify a custom intersection dataset, and if this is configured it will be imported; otherwise, the default will be to derive a dataset of intersections using OpenStreetMap.

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

No branches or pull requests

1 participant