WFS: GetFeature requests adhere to the set coordinate system in later QGIS Server versions.

[eri-blan]

Describe the bug
I haven´t studied this problem thoroughly but it seems that with the QGIS Server version we´ve been using (3.40.2) now, WFS responses seem to respect the coordinate system set in Hajk "more".

This results in a response feature set in the used coordinate system and not in EPSG:4326 like i think it was in previous version, which in turn is projected to coordinate values that become far away from where ever the correct values should be, i.e. the map window is moved to a far away place.

Any one else having a later QGIS Server version that has experienced this issue? It sort of worked in QGIS Server 3.34.

[eri-blan]

Noticed that the searchModel.js needs a crs-object in the response to handle this which does not seem to exist when requesting with QGIS Server 3.40. So I think it is only a problem in the searchModel.js, or rather in QGIS Server 3.40 since the problem seems to be taken care of in the vectorLayer.js. I´ll investigate further if there is a setting for this or if it is something that should be fixed.

[Hallbergs]

LMK if you want to have a quick meeting where we can investigate this issue! @eri-blan

[eri-blan]

We will circumvent this by using GML3 instead of JSON. I also want to add that as it is now, QGIS Server 3.40 sends the crs-object with the requested coordinate system in the response when using GET instead of POST.