"Metadata" for WMS/WFS/etc? layer issues

[qgib]

Author Name: Jonathan Moules (Jonathan Moules)
Original Redmine Issue: 8870
Affected QGIS version: 2.0.1
Redmine category:web_services_clients/wms

---

Few issues with the "metadata" tab on layer properties for a WMS and WFS.
For WMS I have a large GetCapabilities file - attached (GeoServer 2.3.5 is running the backend).

• Every time I click on "Metadata", QGIS hangs for about 2 seconds while it parses this file. The logs show it's not making a request to the server so it's using the local version and the delay is entirely within QGIS. This seems quite slow given I have a 3.4GHz 8 core Xeon CPU.

• More obviously a bug - the only part of the WMS layer Metadata screen that's populated is the "properties". This contains ALL WMS GetCapabilities information.
  None of the other information (title, abstract, etc) is filled, despite being in the GetCapabilities for this layer.

#############
WFS

• Behaviour is different but similar - the title, abstract etc aren't filled in, but the "properties" box only contains information on the specified layer rather than all of them (as it did for WMS).

---

• getcapabilities_1.3.0.xml (Jonathan Moules)

[qgib]

Author Name: Jonathan Moules (Jonathan Moules)

---

Similar issue for WCS it seems too.

[qgib]

Author Name: Jonathan Moules (Jonathan Moules)

---

Note: Apparently these fields are for user metadata. My question then is - why? They can be easily automatically populated from the OGC service. Any user-entered data will be lost as soon as they remove the layer. It'd only be useful if they saved it as a QGS file which seems like a very limited use-case.

[qgib]

Author Name: Jonathan Moules (Jonathan Moules)

---

More obviously a bug - the only part of the WMS layer Metadata screen that's populated is the "properties". This contains ALL WMS GetCapabilities information.

That issue also carries over to the Browser layer properties, again only for WMS as best I can tell.

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

• category_id was configured as Web Services clients/WMS

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• regression was configured as 0
• easy_fix was configured as 0

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Please test with a recent QGIS release (2.18 or 3), if the issue/request is still valid change the affected version accordingly, if is fixed/implemented then close the ticket. Thanks!

---

• status_id was changed from Open to Feedback

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Closing for lack of feedback.

---

• resolution was changed from to not reproducable

• description was changed from Few issues with the "metadata" tab on layer properties for a WMS and WFS.
  For WMS I have a large GetCapabilities file - attached (GeoServer 2.3.5 is running the backend).

• Every time I click on "Metadata", QGIS hangs for about 2 seconds while it parses this file. The logs show it's not making a request to the server so it's using the local version and the delay is entirely within QGIS. This seems quite slow given I have a 3.4GHz 8 core Xeon CPU.

• More obviously a bug - the only part of the WMS layer Metadata screen that's populated is the "properties". This contains ALL WMS GetCapabilities information.
  None of the other information (title, abstract, etc) is filled, despite being in the GetCapabilities for this layer.

#############
WFS

• Behaviour is different but similar - the title, abstract etc aren't filled in, but the "properties" box only contains information on the specified layer rather than all of them (as it did for WMS). to Few issues with the "metadata" tab on layer properties for a WMS and WFS.
  For WMS I have a large GetCapabilities file - attached (GeoServer 2.3.5 is running the backend).

• Every time I click on "Metadata", QGIS hangs for about 2 seconds while it parses this file. The logs show it's not making a request to the server so it's using the local version and the delay is entirely within QGIS. This seems quite slow given I have a 3.4GHz 8 core Xeon CPU.

• More obviously a bug - the only part of the WMS layer Metadata screen that's populated is the "properties". This contains ALL WMS GetCapabilities information.
  None of the other information (title, abstract, etc) is filled, despite being in the GetCapabilities for this layer.

#############
WFS

• Behaviour is different but similar - the title, abstract etc aren't filled in, but the "properties" box only contains information on the specified layer rather than all of them (as it did for WMS).
• status_id was changed from Feedback to Closed