Open StijnCaerts opened 10 months ago
I am facing the exact same problem. Is anybody trying to find a solution?
Thank you.
The implementation of the Filter extension here does not yet include temporal filters.
You can use the datetime
field alongside filter
for temporal search.
{
"datetime": ["2020-11-11T00:00:00Z", "2020-11-12T00:00:00Z"],
"filter": {}
}
Would this work?
I noticed the NoneType: None
, which is something I'm also getting. Seems to me that it has to do with the chosen logging level (logging.exception vs .error). I'd like it to go away -- has this been resolved elsewhere?
@sotosoul Does my solution above work for you?
The issue here is that the T_INTERSECTS
search operator is not supported in the implementation here. Happy to review any PRs if you are willing to contribute that feature.
Describe the bug The temporal intersection queries listed in the documentation of the filter API extension do not work. For the cql2-text query, you get a parsing error as pygeofilter seems to expect a different syntax:
T_INTERSECTS(datetime, INTERVAL('2020-11-11T00:00:00Z', '2020-11-12T00:00:00Z'))
datetime T_INTERSECTS INTERVAL('2020-11-11T00:00:00Z', '2020-11-12T00:00:00Z')
This results in the following error:
But also the cql2-json query does not work:
To Reproduce Run the temporal intersection query examples listed in the filter API extension documentation: https://github.com/stac-api-extensions/filter/?tab=readme-ov-file#example-6-temporal-intersection
Expected behavior These queries should work for full support of the filter extension.