Files
opencloud/pkg
Dominik Schmidt e43fe13066 fix(kql): normalise geo.bbox latitude order for backend-consistent behaviour
Sorts the two latitudes in the KQL layer so MinLat <= MaxLat. Only bleve
strictly requires it (it errors on an inverted box; OpenSearch tolerates it),
but doing it centrally keeps behaviour consistent across backends and the AST
easy to reason about. Longitude order is preserved so an antimeridian-crossing
box (minLon > maxLon) still works, which both backends handle identically.
2026-09-03 01:58:11 +02:00
..
2025-01-13 16:42:19 +01:00
2025-01-13 16:42:19 +01:00
2025-01-13 16:42:19 +01:00
2026-04-23 09:31:11 +02:00
2025-01-13 16:42:19 +01:00
2026-04-23 09:31:11 +02:00
2025-01-20 10:59:08 +01:00
2025-09-11 09:49:24 +02:00
2025-01-13 16:42:19 +01:00
2025-01-13 16:42:19 +01:00
2026-04-23 09:31:11 +02:00
2026-04-23 09:31:11 +02:00
2025-09-12 12:18:47 +02:00
2025-01-13 16:42:19 +01:00
2026-04-23 09:31:11 +02:00
2025-01-13 16:42:19 +01:00
2026-08-25 10:01:26 +02:00
2025-01-13 16:42:19 +01:00