Open jeremyh opened 3 years ago
Follow-up query to look into: do our range searches handle inclusive/exclusive bounds the same way as expected by Stac?
Do we interpret "ranges" like /stac/search?datetime=2018-02-12/2018-02-12
correctly? (I don't know what "correct" is without research)
See also comment by @alexgleith on limitation of current open-range searches: https://github.com/opendatacube/datacube-explorer/pull/243#discussion_r534572906
We allow stac searches with a datetime property:
/stac/search?datetime=
Currently
datetime
can be a timestamp:or a range:
... and time is optional:
But RFC 3339 looks much larger and has many other options. Most notably, newer version of stac-api mention that open ranges are allowed with two dots:
Short-term, we should at least support these open-ranges, since the Stac docs mention them, and they're easy to implement.
...longer-term, ideally look for a library to parse these ranges rather than implementing them ourselves.