Files
opencloud/services
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
..
2026-08-28 23:17:11 +00:00
2026-08-18 17:17:30 +02:00
2026-06-03 16:28:44 +02:00
2026-08-03 13:20:03 +02:00
2026-09-02 23:18:41 +00:00
2026-07-14 18:12:24 +02:00
2026-06-18 15:05:49 +02:00
2026-08-25 09:55:39 +02:00