-
Notifications
You must be signed in to change notification settings - Fork 0
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
support tileId filter with wildcard on CDSE #25
Comments
Some environment variables that need to be set in order to test this locally (required by our own code or by GDAL):
* S3 endpoint data.cloudferro.com (see AWS_S3_ENDPOINT envar for driver pods on CDSE) is only accessible from Cloudferro itself; use endpoint https://eodata.cloudferro.com instead. |
Available on CDSE-staging. Example process graph: {
"process_graph": {
"load1": {
"process_id": "load_collection",
"arguments": {
"id": "SENTINEL2_L2A",
"spatial_extent": {
"west": 4.912844218500582,
"east": 4.918160603369832,
"south": 51.02816932187383,
"north": 51.029815337603594
},
"temporal_extent": [
"2023-09-24T00:00:00Z",
"2023-09-25T00:00:00Z"
],
"bands": [
"B04",
"B03",
"B02"
],
"properties": {
"tileId": {
"process_graph": {
"eq1": {
"process_id": "eq",
"arguments": {
"x": {
"from_parameter": "value"
},
"y": "31*"
},
"result": true
}
}
}
}
}
},
"save2": {
"process_id": "save_result",
"arguments": {
"data": {
"from_node": "load1"
},
"format": "GTIFF"
},
"result": true
}
},
"parameters": []
} There are some debug logs re: what's filtered out client side e.g.:
or
|
I tried with the following jobs but they error when trying to start. |
What's the error? I can't tell from the logs. |
There were some issues wrt/ starting batch jobs so please try again. |
,finished,j-f5c4b9fa566d4df4a060f52b2166f8aa filter : 30SU* |
Specifically for Sentinel-2 layers on CDSE:
we want to filter on the tile id of a feature.
This currently works in load_collection:
properties=dict(tileId=lambda x:x=="31UFS")
But now we need to filter on multiple id's. Cloudferro does not support that.
My proposal is to allow a wildcard match like 31*
We would need to implement that with filtering on our side instead of sending the property filter to the catalog.
The text was updated successfully, but these errors were encountered: