Let library users handle output however they like, and add flatgeobuf output #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3 functional changes here:
I used the input data from #5:
time cargo run --release -- disaggregate --od-csv-path ~/Downloads/od_sp_center.csv --zones-path ~/Downloads/zones_sp_center.geojson --output-path result.fgb --output-fgb
Before this PR, output to geojson took 58s. After this PR, down to 22s!
FGB output takes much longer, 50s. Not sure why yet, though I have a few ideas. The resulting file is much smaller -- 735MB FGB, 1.4GB GeoJSON. I haven't checked downstream yet to see which is faster to read, or if reading is even the bottleneck in a larger pipeline.
This is a step towards #49 (comment) improving the API for language bindings, but the input is still a bunch of files.