WFS not working at all

[qgib]

Author Name: Willem Buitendyk (@swaxolez)
Original Redmine Issue: 19801
Affected QGIS version: 3.2.2
Redmine category:web_services_clients/wfs

---

Upgraded to 3.2.2 on Mac. WFS is completely non-responsive using WFS 1.1 or WFS 2.0. Error coming back is:

Server generated an exception in GetFeature response: org.opengis.referencing.NoSuchAuthorityCodeException: No authority was defined for code "". Did you forget "AUTHORITY:NUMBER"?

In addition I'm also seeing that upon initially loading the canvas is truncated. Opening python console or messages console, resizing and then closing allows the canvas to snap to entire screen.

---

Related issue(s): #29258 (relates)
Redmine related issue(s): 21441

---

[qgib]

Author Name: Willem Buitendyk (@swaxolez)

---

WFS Error: "Did you forget "AUTHORITY:NUMBER"?" was related to a bad EPSG on geoserver.

However, WFS still loads incredibly slowly or not at all compared to 2.14. The geoserver connection I am using is drawing from a postgis backend which may be part of the problem, yet I did not have this problem on 2.14

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Can you share the service URL? Thanks.

---

• status_id was changed from Open to Feedback
• regression was changed from 0 to 1

[qgib]

Author Name: Willem Buitendyk (@swaxolez)

---

Unfortunately I can't as our WFS server is private data. I will try to find some other large public WFS datasets to see if there is any difference.

[qgib]

Author Name: Willem Buitendyk (@swaxolez)

---

I've made some progress. An old EPSG code was causing some issues so I changed it from 4030 to 4326. WFS 1.1 works somewhat. WFS 2.0 does not work at all. It all works on Windows but WFS 2.0 is very slow compared to WFS 1.1.

Here is my wild guess - it has something to do with the pop-up progress bar and large datasets.

No doubt though on either Windows or Mac, WFS is much much slower.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

The canvas size issue on macOS is known and was already filed in a different ticket.

---

• subject was changed from WFS not working at all. Canvas not fully sized on new instance of QGIS to WFS not working at all

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Willem Buitendyk wrote:

I've made some progress. An old EPSG code was causing some issues so I changed it from 4030 to 4326. WFS 1.1 works somewhat. WFS 2.0 does not work at all. It all works on Windows but WFS 2.0 is very slow compared to WFS 1.1.

Here is my wild guess - it has something to do with the pop-up progress bar and large datasets.

No doubt though on either Windows or Mac, WFS is much much slower.

I'm testing a Mapserver (sorry no Geoserver here) that publishes layers with millions of features, and can't see any particular slowdown compared to 2.18 (Linux here).

A test service URL that shows the issue for you is really necessary in order to be able to diagnose/troubleshoot the problem.

[qgib]

Author Name: Willem Buitendyk (@swaxolez)

---

Giovanni Manghi wrote:

Willem Buitendyk wrote:

I've made some progress. An old EPSG code was causing some issues so I changed it from 4030 to 4326. WFS 1.1 works somewhat. WFS 2.0 does not work at all. It all works on Windows but WFS 2.0 is very slow compared to WFS 1.1.

Here is my wild guess - it has something to do with the pop-up progress bar and large datasets.

No doubt though on either Windows or Mac, WFS is much much slower.

I'm testing a Mapserver (sorry no Geoserver here) that publishes layers with millions of features, and can't see any particular slowdown compared to 2.18 (Linux here).

A test service URL that shows the issue for you is really necessary in order to be able to diagnose/troubleshoot the problem.

Yes fair enough. I will have to try map server with the postgis backend. In the meantime I've started moving all of my datasets to postgis directly as it seems to be faster and have given up on WFS. For whatever reason that alludes me my geoserver, serving postgis data doesn't work with QGIS 3. It still works fine with QGIS 2. Strange.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Yes fair enough. I will have to try map server with the postgis backend. In the meantime I've started moving all of my datasets to postgis directly as it seems to be faster and have given up on WFS. For whatever reason that alludes me my geoserver, serving postgis data doesn't work with QGIS 3. It still works fine with QGIS 2. Strange.

that could be very well a QGIS 3 issue and means that must be fixed, yet is difficult to find the issue without having the necessary environment/scenario to test.

[qgib]

Author Name: Paolo Cavallini (@pcav)

---

Any test case available?

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• relates was configured as Multiple issues and deadlocks with WFS #29258

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

This is likely a duplicate of #29258

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• status_id was changed from Feedback to Open