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

[feature] Assist in merging in walk networks #112

Open
kuanb opened this issue Oct 9, 2018 · 3 comments
Open

[feature] Assist in merging in walk networks #112

kuanb opened this issue Oct 9, 2018 · 3 comments

Comments

@kuanb
Copy link
Owner

kuanb commented Oct 9, 2018

This step is often performed by users, but can be confusing. Create a "most common" path for importing in walk networks (perhaps from OSMnx) and support its conversion to peartree.

@kuanb kuanb changed the title [feature [feature] Assist in merging in walk networks Oct 9, 2018
@e-lo
Copy link

e-lo commented Oct 25, 2018

Is there an example somewhere of this being done? (even if it isn't 'standard' yet)

@kuanb
Copy link
Owner Author

kuanb commented Oct 25, 2018

@e-lo thanks for your question. Here is a Gist with a quick sketch of integrating some walk network data from OSM via the Overpass API (queried with OSMnx's helper method) with New Orleans' published GTFS data: https://gist.github.com/kuanb/f826dd2df30c1d4e9974b0bc073b72e7

@kuanb
Copy link
Owner Author

kuanb commented Oct 29, 2018

@e-lo just wanted to check back in to make sure that Gist was helpful. If you need any additional assistance, please let me know - I would be happy to help you if you are trying to use peartree in a project!

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

No branches or pull requests

2 participants