User Story
As a data analyst querying geographic items, I want to define a Geospatial column that stores geometry footprints as WKT text and query them with Trino's ST_ functions, so that I can filter and analyze products spatially.
Acceptance Criteria
- Geospatial can be selected as a data type in the Attributes menu.
- Geospatial is shown on the column details page.
- A Geospatial column reliably stores geometries as WKT (POLYGON, POINT, …)
- Spatial filtering combines correctly with non-spatial filters (instrument, cloud_cover) and with ORDER BY / LIMIT.
- Invalid / empty / non-WKT values are handled gracefully so queries don't fail; the footprint LIKE 'POLYGON%' guard (or an equivalent validity check) is documented as the pattern to use.
- NULL handling is explicit, so rows with missing values behave as intended.
- Documentation of the guard pattern and the reference query.
Follow Us
You can follow this task with the notification on the right tab.
Ask us anything here in the comments below, and vote with emojis for most requested items !
👍 to vote for this issue
Discuss on Discord
Feel free to discuss with us on https://discord.gg/ovhcloud
User Story
As a data analyst querying geographic items, I want to define a Geospatial column that stores geometry footprints as WKT text and query them with Trino's ST_ functions, so that I can filter and analyze products spatially.
Acceptance Criteria
Follow Us
You can follow this task with the notification on the right tab.
Ask us anything here in the comments below, and vote with emojis for most requested items !
👍 to vote for this issue
Discuss on Discord
Feel free to discuss with us on https://discord.gg/ovhcloud