WFS filtering by QGIS expression supports "$geometry" but not the new "@geometry"

[kannes]

What is the bug or the crash?

QGIS is moving from $ to @ in expressions.

One can use a small subset of QGIS expression functionality in WFS layer filters.

Here only $geometry works. @geometry is not supported yet.

The documentation at https://qgis.org/pyqgis/master/core/QgsVectorLayer.html#ogc-api-features-data-provider-oapif also still uses $geometry.

Steps to reproduce the issue

1. Load dvg:nw_dvg2_krs https://www.wfs.nrw.de/geobasis/wfs_nw_dvg?VERSION=2.0.0 as layer
2. Set the layer's filter/subsetstring to intersects(@geometry, geom_from_wkt('POINT(380000 5650000)'))
3. The layer appears unfiltered (53 features at the time of writing)

Using intersects($geometry, geom_from_wkt('POINT(380000 5650000)')) the layer is correctly filtered to one single feature.

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>

QGIS version	3.40.2-Bratislava
QGIS code branch	Release 3.40
Libraries
Qt version	5.15.15
Python version	3.12.8
GDAL/OGR version	3.10.0
PROJ version	9.5.1
EPSG Registry database version	v11.022 (2024-11-05)
GEOS version	3.13.0-CAPI-1.19.0
SQLite version	3.47.2
PDAL version	2.8.2 (Compiled)2.8.3 (Running)
PostgreSQL client version	unknown
SpatiaLite version	5.1.0
QWT version	6.3.0
QScintilla2 version	2.14.1
OS version	Manjaro Linux
Active Python plugins
MemoryLayerSaver	5.0.2
spatial_filter	1.7
plugin_reloader	0.17
db_manager	0.1.20
MetaSearch	0.3.6
grassprovider	2.12.99
processing	2.12.99

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[agiudiceandrea]

Please have a look at #60105.