fix: use WFS POST for historical land use

2026-07-14 15:31:54 +02:00
parent 8c694fa9ce
commit d062edbbe1
4 changed files with 67 additions and 31 deletions
@@ -7801,3 +7801,4 @@ Live deployment correction:
 - Both Tower deploy entry points now wait for the `geointel` container healthcheck, which includes completed startup migrations and backend readiness, before launching the independent migration smoke.
 - The first Statbel upload exposed 3D sector coordinates (`Z=0`) against the canonical 2D PostGIS vector column. The source is valid; GeoIntel now preserves the original artifact, records the Z-feature count and explicitly drops Z only for the 2D query index.
 - Vector upload persistence is now atomic across Dataset, DatasetVersion and VectorFeature rows, with storage cleanup on rollback. This prevents the failed-indexing orphan state observed during the live import.
+- Tower could read the historical WFS capabilities but its gateway rejected XML `FILTER` content embedded in a GET query. The operator now sends the same read-only WFS 2.0 GetFeature request as XML POST; a live two-feature forest page returned successfully before redeployment.
@@ -55,6 +55,10 @@ These historical map editions support exploratory area evolution, not
 cadastral object lineage. Their feature identities are declared unstable and
 GeoIntel does not fabricate added/removed object counts.

+The operator uses standards-compliant WFS 2.0 XML POST requests. This keeps
+the spatial/class filters server-side without exposing a long XML filter in a
+GET query, which the public gateway rejects.
+
 ## OSM

 - Naam: OpenStreetMap