-
Notifications
You must be signed in to change notification settings - Fork 54
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
ConsolidateMetadata2 #678
ConsolidateMetadata2 #678
Conversation
Thanks for looking at this @norlandrhagen ! I was just reading about the parquet implementation and noticed it says:
Since consolidate_metadata also seems to assume JSON/dict input I would not expect to be able to pass geoparquet to consolidate_metadata either. Did you consolidate metadata before converting to geoparquet for the CMIP6 dataset you worked on? |
Update: Thanks @abarciauskas-bgse & @ranchodeluxe for talking through this! According to discussion in this PR: #675. It seems like there isn't really a point to consolidate the metadata for a Kerchunk reference.
|
(just adding these bullets also)
|
|
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 doing this @norlandrhagen 🥳 Can't wait to get this merged so I can double check if my assumption about fsspec auth args is correct or not
@cisaacstern would you mind taking a look at this when you get a chance? |
ConsolidateMetadata
doesn't seem to be creating a.zmetadata
in the reference recipe tests.Based on Martin Durants comments here: fsspec/kerchunk#240 (comment), this PR updates how the
.zmetadata
is being created.Some open questions:
zarr.open_consolidated
were working...without a .zmetadata file?path.fs.save_json(ref_path)
calls save_json`. How do we modify the parquet stores?cc @abarciauskas-bgse @ranchodeluxe