This is my first-ever contribution to an open-source project, so please bear with me if anything seems off—I’m eager to learn!
I came across your project last week and found it super interesting and relevant to something I was working on: extracting sidewalk polygons in cities around the world using OSM. I really appreciate all the thought and effort you’ve already put into it—thank you for sharing!
Since I’m not familiar with JS or Wasm, setting up the JavaScript version was a bit too challenging for me. So, I decided to create Python bindings instead (I noticed this was already on the roadmap—hopefully, this aligns with your plans!).
Here’s what I’ve done:
Replicated the structure of osm2streets-js to create osm2streets-py.
Updated the overall Cargo.toml slightly to accommodate the new bindings.
Added documentation explaining installation, usage, and the functions currently implemented (everything that already had Wasm bindings) - in osm2streets-py.
Included a test.py to run a basic test case and a test.ipynb notebook showcasing more of the capabilities.
A sample output:
You can install the package before the merge using this command, which points to my fork. The documentation already links to your main repository for post-merge clarity:
I hope you find this valuable! I’m excited to hear your thoughts and feedback on what I’ve built so far. Please feel free to share any tips or pointers on structuring contributions (for this or future projects)—I’m here to learn!
Hi there,
I hope you’re doing well!
This is my first-ever contribution to an open-source project, so please bear with me if anything seems off—I’m eager to learn!
I came across your project last week and found it super interesting and relevant to something I was working on: extracting sidewalk polygons in cities around the world using OSM. I really appreciate all the thought and effort you’ve already put into it—thank you for sharing!
Since I’m not familiar with JS or Wasm, setting up the JavaScript version was a bit too challenging for me. So, I decided to create Python bindings instead (I noticed this was already on the roadmap—hopefully, this aligns with your plans!).
Here’s what I’ve done:
A sample output:
You can install the package before the merge using this command, which points to my fork. The documentation already links to your main repository for post-merge clarity:
I hope you find this valuable! I’m excited to hear your thoughts and feedback on what I’ve built so far. Please feel free to share any tips or pointers on structuring contributions (for this or future projects)—I’m here to learn!
Looking forward to your comments, Lukas