-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Document input data format specification #49
Comments
@katamartin / @freeman-lab - here's a short sample {
"history": "Created: Wed Dec 22 04:14:40 2021",
"hostname": "prefect-job-9f003c8e-85nkn",
"institution": "CarbonPlan",
"multiscales": [
{
"datasets": [
{
"path": "0",
"pixels_per_tile": 128
},
{
"path": "1",
"pixels_per_tile": 128
}
],
"metadata": {
"args": [],
"kwargs": {
"levels": 2,
"method": "bilinear",
"regridder_kws": {
"periodic": true
},
"weights_template": null
},
"method": "pyramid_regrid",
"version": "0.0.post60"
},
"type": "reduce"
}
],
"source": "/srv/conda/envs/notebook/bin/prefect",
"username": "jovyan",
"version": "0.4.0"
} Can you confirm that the maps-relevant spec can be entirely confined to the |
@jhamman yeah I think that's right! This is all we look at from the metadata (starting in soon-to-be-released v2 of Lines 251 to 278 in a3cab7c
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should write down the multiscale-schema we depend on here. There are various conversations happening about the use of the multiscales spec for mapping applications (see zarr-developers/zarr-specs#125, zarr-developers/zarr-specs#124, carbonplan/ndpyramid#18, and #14).
The text was updated successfully, but these errors were encountered: