feat: Option to export as GeoJSON
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing how the existing GPKG export is produced and review the linked dataexport issue for the expected GeoJSON behavior. Add a native option for GeoJSON export while preserving the current GPKG output, then confirm the resulting files work for the stated export use cases and document the option.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
It has been a recurring issue at the bikenetkit.org development that for sb we only have gpkg exports - for technical reasons, see: https://github.com/BikeNetKit/dataexport/issues/37. Also, geojson is a widely understood format, while gpkg is mostly just understood in the geospatial community, so this might also help the future uptake of sb. For such reasons, in all other bikenetkit packages we have the option for both geojson and gpkg exports.
Proposed Solution
Implement an option for geojson export, see https://github.com/BikeNetKit/dataexport/issues/37
Alternative Solutions
Over at https://github.com/BikeNetKit/dataexport we could write a conversion script to turn the existing gpkg output into geojson. But why not support it natively, given it makes a lot of sense.
Use Cases
See above
Additional Context
We are in the data export phase for bikenetkit.org, so we would need this feature soon, like within 2 weeks. BUT I don't want to create any stress to you @cbueth! You might be the best to develop this feature, but I totally understand if you don't have the time for it. Could you please let me know, so I can plan whether we should write a conversion script. This wouldn't be a problem, just thinking it's better to avoid doing the same work twice, if it's possible.
Willing to Contribute?
- I'm willing to submit a PR for this feature
- I can help test this feature
- I can help document this feature
- Dominant language
- Python
- Stars
- 33
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BikeNetKit/superblockify
-
bug: Calculate rel_increase_comp independently of plottingPossibly taken @cbueth claimed this 21 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
BikeNetKit/superblockify#136 · 2 comments ·
-
bug: gdal requiredOpenbug
Difficulty 1/5 Under an hour Newbie friendliness 78/100
BikeNetKit/superblockify#135 · 3 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
BikeNetKit/superblockify#139 · 3 comments · 1 reaction ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
BikeNetKit/superblockify#138 ·
-
feat: Map coloringOpenenhancement good first issue
Difficulty 5/5 Over a week Newbie friendliness 35/100
BikeNetKit/superblockify#130 · 2 comments ·
All issues in BikeNetKit/superblockify
Similar issues
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ramnes/notion-sdk-py#409 ·
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lindicaphxag-tech/kaggle#28 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
BSData/horus-heresy-3rd-edition#3211 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug tests
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day