The setting 'Use layer ids as name' does not work for WFS-call

[qgib]

Author Name: Mie Winstrup (Mie Winstrup)
Original Redmine Issue: 15085
Affected QGIS version: 2.14.0
Redmine category:qgis_server
Assignee: René-Luc ReLuc

---

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:
!Use_layer_ids_as_names.png!

The problem
When calling a WMS GetCapability-request to this Qgis-project layerids are used as names:
!WMS_use_layernames_as_ids_001.png!

However, when calling a WFS GetCapability-request to this Qgis-project, the layerids are NOT used as names (it is the layername instead):
!WFS_use_layernames_as_ids_001.png!

---

• Use_layer_ids_as_names.png (Mie Winstrup)
• WMS_use_layernames_as_ids_001.png (Mie Winstrup)
• WFS_use_layernames_as_ids_001.png (Mie Winstrup)

---

Related issue(s): #23028 (relates)
Redmine related issue(s): 15086

---

[qgib]

Author Name: Mie Winstrup (Mie Winstrup)

---

• 10050 was configured as WFS_use_layernames_as_ids_001.png
• 10048 was configured as Use_layer_ids_as_names.png
• 10049 was configured as WMS_use_layernames_as_ids_001.png

---

• WFS_use_layernames_as_ids_001.png (Mie Winstrup)
• Use_layer_ids_as_names.png (Mie Winstrup)
• WMS_use_layernames_as_ids_001.png (Mie Winstrup)

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

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

[qgib]

Author Name: René-Luc ReLuc (@rldhont)

---

• assigned_to_id was configured as René-Luc ReLuc
• description was changed from 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:
!Use_layer_ids_as_names.png!

The problem
When calling a WMS GetCapability-request to this Qgis-project layerids are used as names:
!WMS_use_layernames_as_ids_001.png!

However, when calling a WFS GetCapability-request to this Qgis-project, the layerids are NOT used as names (it is the layername instead):
!WFS_use_layernames_as_ids_001.png!
to 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:
!Use_layer_ids_as_names.png!

The problem
When calling a WMS GetCapability-request to this Qgis-project layerids are used as names:
!WMS_use_layernames_as_ids_001.png!

However, when calling a WFS GetCapability-request to this Qgis-project, the layerids are NOT used as names (it is the layername instead):
!WFS_use_layernames_as_ids_001.png!

[qgib]

Author Name: René-Luc ReLuc (@rldhont)

---

has it been fixed in 2.18 ?

---

• status_id was changed from Open to Feedback

[qgib]

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

---

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.

---

• resolution was changed from to no timely feedback
• status_id was changed from Feedback to Closed