-
Notifications
You must be signed in to change notification settings - Fork 46
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
editoast: add a osm-to-railjson command #4048
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #4048 +/- ##
============================================
+ Coverage 20.23% 20.24% +0.01%
+ Complexity 2076 2073 -3
============================================
Files 795 795
Lines 78377 78394 +17
Branches 2058 2057 -1
============================================
+ Hits 15858 15872 +14
- Misses 61359 61363 +4
+ Partials 1160 1159 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your PR! 🎉
It looks good to me, can you just rewrite your git history to follow up the git commit style describe here.
6169782
to
f75fd1a
Compare
f75fd1a
to
e8b058e
Compare
This command will extract data from OpenStreetMap (.pbf file format) and generate the track_sections from Ways that represent rails It uses the osm4routing crate to cut the ways into edges suitable for routing So far it only handles track sections
a830b71
to
33f8a8e
Compare
This command will extract data from OpenStreetMap (.pbf file format) and generate the track_sections from Ways that represent rails
It uses the osm4routing crate to cut the ways into edges suitable for routing
ref #4035