Bug report #7536
shapefiles served with qgis wfs server are completely wrong (used to work in 1.8)
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Severe/Regression | ||
| Assignee: |  René-Luc ReLuc | ||
| Category: | Web Services clients/WFS | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | fixed |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 16480 |
Description
pick the attached sample project, and change the project settings ("ows server") so you will able to publish it with qgis server (wfs).
Then use the qgis wfs client to download the vector, you will see (see attached images) that is completely wrong.
This does not happen if the input vector is PostGIS and didn't happened at all on qgis 1.8.
History
#1
Updated by René-Luc ReLuc about 11 years ago
- Category changed from QGIS Server to Web Services clients/WFS
I have testing the project and comparing GML and GeoJSON provided by the QGS Server WFS.
The GeoJSON rendering is exactly the same as ESRI ShapeFile.
The GML data is the same as GeoJSON but the rendering is not the same.
The problem is a GML Parsing error.
#2
Updated by René-Luc ReLuc about 11 years ago
- Resolution set to fixed
- % Done changed from 0 to 100
- Assignee set to René-Luc ReLuc
- Status changed from Open to Closed
The bug was due to an inversion between tuple and coordinates separator in Polygon coordinates elements.
commit 28ade759b32bee140356081607d86814b25a755f 28ade759b32bee140356081607d86814b25a755f