Closed PeterDSteinberg closed 8 years ago
This was partially addressed in PR #53 which added a bands_as_columns
decorator. Further consideration may be required for data_sources which have more than 3 dimensions, e.g. (band
, y
, x
, z
) or (band
, y
, x
, z
, time
) instead of (band
, y
, x
).
The comment above relates also to #54 as NetCDF often have higher dimensionality.
Just discussed this with @brendancol . We are going to provide in the data_sources
section of config a place to specify the dimensions and canvas of the input data to be derived from files, allowing for dimensions of band
, y
, x
, z
, time
and various common patterns of flattening or reducing that data.
Currently all samples go from a shape of ( band, y, x) to (space, band). We should make
{flatten: True}
be a step in asample_pipeline
explicitly rather than calling it automatically. Some methods may actually want to flatten it to(lat points, lon points * bands)
and breakingflatten
out as an explicit step will allow more control