Bug report #13037
WFS GetCapabilities respons misses <keywords> key
| Status: | Closed | ||
|---|---|---|---|
| Priority: | High | ||
| Assignee: |  René-Luc ReLuc | ||
| Category: | QGIS Server | ||
| Affected QGIS version: | 2.12.0 | 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 #: | 21112 |
Description
When you request getCapabilities to QGIS-server es. http://x.x.x.x/cgi-bin/qgis_mapserv.fcgi?map=myproject.qgs&service=WFS&request=GetCapabilities&version=1.0.0 the reply is missing <Keywords> key in the <Service>. This is a tag described in OGC WFS 1.0 recommendation in http://portal.opengeospatial.org/files/?artifact_id=7176. It's not possible to use owslib.wfs to parse resources.
Associated revisions
[BUGFIX] WFS GetCapabilities respons misses <keywords> key
Fixes #13037 WFS GetCapabilities respons misses <keywords> key
Replace KeywordList by Keywords in WFS Getcapabilities and keywords in WCS GetCapabilities.
[BUGFIX] WFS GetCapabilities respons misses <keywords> key
Fixes #13037 WFS GetCapabilities respons misses <keywords> key
Replace KeywordList by Keywords in WFS Getcapabilities and keywords in WCS GetCapabilities.
[BUGFIX] WFS GetCapabilities respons misses <keywords> key
Fixes #13037 WFS GetCapabilities respons misses <keywords> key
Replace KeywordList by Keywords in WFS Getcapabilities and keywords in WCS GetCapabilities.
[BUGFIX] WFS GetCapabilities respons misses <keywords> key
Fixes #13037 WFS GetCapabilities respons misses <keywords> key
Replace KeywordList by Keywords in WFS Getcapabilities and keywords in WCS GetCapabilities.
History
#1
Updated by Giovanni Manghi over 9 years ago
- Operating System deleted (
All) - Status changed from Open to Feedback
I cannot confirm on qgis server master
<WFS_Capabilities version="1.0.0" updateSequence="0" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.0.0/WFS-capabilities.xsd"><Service><Name>WFS</Name><Title>map_none</Title><Abstract>-</Abstract><KeywordList><Keyword>blah blah blah</Keyword></KeywordList>...
#2
Updated by Giovanni Manghi over 9 years ago
- Status changed from Feedback to Closed
- Resolution set to not reproducable
closing for lack of feedback.
#3
Updated by jachym - almost 9 years ago
- Status changed from Closed to Reopened
- Affected QGIS version changed from 2.8.2 to 2.12.0
- Priority changed from Normal to High
Reopening:
The bug is actually about WFS Capapabilities response invalidity - the XML response is simply wrong (according to OGC Schema).
How to reproduce (linux):
# download the schema file - it's url is in the head of Capabilities response wget "http://schemas.opengis.net/wfs/1.0.0/WFS-capabilities.xsd" # download the capabilities response wget "http://localhost/cgi-bin/qgis_mapserv.fcgi?REQUEST=GetCapabilities&SERVICE=WFS" -O capabilities.xml # validate xmllint --schema WFS-capabilities.xsd capabilities.xml --noout
And the result is:
capabilities.xml:6: element KeywordList: Schemas validity error : Element '{http://www.opengis.net/wfs}KeywordList': This element is not expected. Expected is one of ( {http://www.opengis.net/wfs}Keywords, {http://www.opengis.net/wfs}OnlineResource ).
capabilities.xml:45: element GML3: Schemas validity error : Element '{http://www.opengis.net/wfs}GML3': This element is not expected. Expected is ( {http://www.opengis.net/wfs}GML2 ).
capabilities.xml fails to validate
Therefore I would say, QGIS WFS server is not usable at the moment. But maybe I did something wrong, correct me please, if so.
#4
Updated by Ivan Mincik almost 9 years ago
- Assignee set to Marco Hugentobler
When fixed, please backport it also to 2.8 LTS. Thanks.
#5
Updated by Ivan Mincik almost 9 years ago
- Assignee changed from Marco Hugentobler to René-Luc ReLuc
#6
Updated by René-Luc ReLuc almost 9 years ago
- Status changed from Reopened to Closed
Fixed in changeset e2d1320295fa16fc40f2787531bd5d2cbda2bd29.