Open soxofaan opened 1 year ago
Side note regarding empty cubes: with raster cubes in load_collection
we have NoDataAvailable
and TemporalExtentEmpty
errors, so "empty cube" seems like an error condition there
A PR based on your findings would be great so that we can discuss specific improvements.
There's room for improvement of 1+2 for sure, making more clear that it's probably no-data values/null that you want to set if no data is available. 3 also makes sense to me. Mixing data types is allowed in openEO, it's up to the implementations to decide whether they can support this or not. I would need to look into details for 4, I don't have a direct answer here.
Regarding the errors: They usually apply if there are no labels for the requested dimensions available, i.e. no data to load from. A datacube with all no-data values is not necessarily captured by that.
We're trying to support/implement a use case that depends heavily on vector cube manipulation and some questions related to
load_geojson
came up (based on 2.0.0-rc.1 spec, other refs: #427 #322):properties
parameter, which is empty by default, so no properties are preserved by default actuallyproperties
has default value empty array[]
but it is unclear what should happen in this case: there is only a geometries dimension with labels, but no "cube data".(N, 0)
(N labels along "geometries" dimension and zero labels along "properties" dimension)?(N,1)
?properties
and typeother
is created if at least one property is provided.". I wonder if it wouldn't be cleaner to just always add this "properties" dimension, regardless of the number of provided properties. Then e.g.:properties
array[]
=> "properties" dimension with single dummy label and no-data valuesproperties
array, e.g.["population"]
=> "properties" dimension with single label "population". Advantage compared to not adding the dimension is that the property name ("population" in example) is preserved["id", "area", "population"]
=> as currently specified