-
Notifications
You must be signed in to change notification settings - Fork 10
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
operations / transformations #79
Comments
Other ideas:
I've also been thinking about a 'merge' command for awhile - had been planning to make an issue for that, where collection-level metadata would shift to the row level. I was thinking that would be a full featured command, where you could do things like reprojection, and clean up boundaries. But it might make sense to push more to 'operations' and keep the merge pretty simple - it would just reject things that don't merge well, but the source data could be transformed more to get ready for the merge. |
PR for most of the functionality: #114 |
ToDo list (added by @m-mohr):
List of ideas:
fiboa improve example.parquet -s
shapely.make_valid
):fiboa improve example.parquet ... -g
fiboa merge
, a single input dataset and the --include/--exclude flags (note: use -x and --crs if needed)fiboa improve example.parquet --crs EPSG:1234
fiboa improve example.parquet
) and vice versa (fiboa improve example.parquet -gp1
)fiboa improve example.parquet --compression brotli
There's been a good bit of desire to do 'extra' things in the converters, and we had a good discussion with some ideas on how to approach that in the last call, so wanted to open an issue.
The original one was #21 - add area and perimeter. But then also things like adding statistics as new columns, or filtering columns out.
Was thinking it could be ideal to keep the 'converters' very 'clean' - like they just translate from the source data to fiboa. But then there's maybe
fiboa transform
or something like that with a bunch of sub-commands. And ideally you could also use those sub-commands as part of the conversion process. Some of the initial ideas:converter
: Add option to calculate area and perimeter if missing #21)I'm sure there's lots more, but basically have a set of utilities that help clean up and format data better, and harmonize it for various use cases. But every transformation is an 'opinion' to use the Varda way of thinking about it. So keep those as their own utilities, for people to choose to transform as they want.
The text was updated successfully, but these errors were encountered: