Bug report #15085
The setting 'Use layer ids as name' does not work for WFS-call
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: |  René-Luc ReLuc | ||
| Category: | QGIS Server | ||
| Affected QGIS version: | 2.14.0 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | no timely feedback |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 23027 |
Description
The setting 'Use layer ids as name' works for WMS-call but does not work for WFS-call. This makes it difficult programmatically to use a combination of WMS and WFS.
Case:
I have a qgis-project. The qgis-project is published as a WMS and WFS with QGIS Server (ubuntu). Since there is inconsistency in the naming of files with WMS and WFS if a layer contains a space (reported as bug), I want to use the setting 'Use layer ids as name' to be able to use a combination of WMS and WFS call to the same qgis-project. In Project Properties I specify that I want to use layer ids as names:
The problem
When calling a WMS GetCapability-request to this Qgis-project layerids are used as names:
However, when calling a WFS GetCapability-request to this Qgis-project, the layerids are NOT used as names (it is the layername instead):
Related issues
History
#1
Updated by Mie Winstrup over 8 years ago
- File WFS_use_layernames_as_ids_001.png added
- File Use_layer_ids_as_names.png added
- File WMS_use_layernames_as_ids_001.png added
#2
Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
- Regression? set to No
#3
Updated by René-Luc ReLuc about 7 years ago
- Assignee set to René-Luc ReLuc
- Description updated (diff)
#4
Updated by René-Luc ReLuc about 7 years ago
- Status changed from Open to Feedback
has it been fixed in 2.18 ?
#5
Updated by Jürgen Fischer almost 6 years ago
- Resolution set to no timely feedback
- Status changed from Feedback to Closed
Bulk closing 82 tickets in feedback state for more than 90 days affecting an old version. Feel free to reopen if it still applies to a current version and you have more information that clarify the issue.