Open jdries opened 9 months ago
Update for myself: example of metadata that users are asking for.
{
"geometry" : "τ1{tend=946684800000,tstart=0,ttype=logical}S2(43199,21599){bbox=[-180.0 180.0 -90.0 90.0],proj=EPSG:4326}",
"metadata" : {
"im:keywords" : "global, climate, weather, Average temperature",
"dc:comment" : "This is WorldClim version 2.1 climate data for 1970-2000. This version was released in January 2020.\r\nThere are monthly climate data for average temperature (°C).\r\nThe data is available at 30 seconds (~1 km2).\r\nFor \"time\", the month scope is inside the semantics data annotation",
"im:notes" : "",
"dc:title" : "WorldClim Historical climate data version 2.1 data 30s for 1970-2000 average temperature January",
"dc:url" : "https://worldclim.org/data/worldclim21.html",
"dc:creator" : "",
"im:thematic-area" : "Earth",
"dc:originator" : "Worldclim",
"im:geographic-area" : "Global",
"dc:source" : "Fick, S.E. and R.J. Hijmans, 2017. Worldclim 2: New 1-km spatial resolution climate surfaces for global land areas. International Journal of Climatology 37(12):4302-4315."
},
}
2 new use cases came up, with a similar solution:
Note that this collection metadata also acts as a definition of constraints: if the output aoi is europe, than it will probably not accept an input aoi in north america. So UDP tools can use this for input field validation, which is very useful for generic wizards like the openEO editor has.
My proposed solution is to simply add a property with the target STAC collection metadata to the UDP and batch job schema:
https://api.openeo.org/#tag/User-Defined-Processes/operation/store-custom-process
I'll probably experiment with this myself, but also wanted to share the idea. These cases are triggered by user projects.