Bug report #8870
"Metadata" for WMS/WFS/etc? layer issues
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Web Services clients/WMS | ||
| Affected QGIS version: | 2.0.1 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | not reproducable |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 17550 |
Description
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 
(246 KB)
History
#1
Updated by Jonathan Moules about 11 years ago
Similar issue for WCS it seems too.
#2
Updated by Jonathan Moules almost 11 years ago
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.
#3
Updated by Jonathan Moules almost 11 years ago
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.
#4
Updated by Jürgen Fischer about 10 years ago
- Category set to Web Services clients/WMS
#5
Updated by Giovanni Manghi over 7 years ago
- Regression? set to No
- Easy fix? set to No
#6
Updated by Giovanni Manghi over 6 years ago
- Status changed from Open to Feedback
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!
#7
Updated by Giovanni Manghi over 6 years ago
- Resolution set to not reproducable
- Description updated (diff)
- Status changed from Feedback to Closed
Closing for lack of feedback.