[Qgis-user] InvalidCRS with WMS request on QGIS-server 2.18.18

galebellego.ext at orange.com galebellego.ext at orange.com
Tue Apr 3 09:51:37 PDT 2018


Hello,

I encounter a problem with a (docker-hosted) version of QGIS-server 2.18.18 (built from Source).

When I perform a WMS request on server, I always get a InvalidCRS error :
<ServiceExceptionReport version="1.3.0"><ServiceException code="InvalidCRS">Could not create output CRS</ServiceException></ServiceExceptionReport>

The same request sent on a 3.1 version of qgis-server performs well!


http://myContainer/qgis?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=layer1&MAP=%2Fdata%2Ftest_2.18.qgs&CRS=EPSG%3A3857&STYLES=&WIDTH=2471&HEIGHT=1237&BBOX=-408661.0170981592%2C6217550.309401342%2C-361442.04287499154%2C6241188.460398533

(I also tried with version 1.1.1 and 'SRS').


When I perform getCapabilities, I saw thoses lines including an empty <CRS/> in the 2.18.18 response.
Since they are CRS-related, this might be a clue :

3.1
<Layer><Name>layer1</Name><Title>layer1</Title><CRS>CRS:84</CRS><CRS>EPSG:3857</CRS><CRS>EPSG:4326</CRS>

2.18.18
<Layer queryable="1"><Name>layer1</Name><Title>layer1</Title><CRS>CRS:84</CRS><CRS/><CRS>EPSG:4326</CRS><CRS>EPSG:3857</CRS>


The only other remarkable difference I noticed : it appeared that the QGIS_PROJECT_FILE in server 2.18.18 is not used (that's why I had to set it in the URL), when it is used in the 3.1 version.
There are other differences, but none that looked concerned with my problem ... according to me! I may be wrong indeed... thus you'll find both the response to getCapabilities enclosed!.


I have created a project from scratch, from a shapefile with a few dots, and still I have the problem..
The WMS capabilities are set, and the layer name as well as the BBOX and the file name are ok.

So if anyone has a tip here...

Thanks by Advance.


Gaƫl

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20180403/46b30060/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qgis2.18.xml
Type: application/xml
Size: 10256 bytes
Desc: qgis2.18.xml
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20180403/46b30060/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qgis3.0.xml
Type: application/xml
Size: 10537 bytes
Desc: qgis3.0.xml
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20180403/46b30060/attachment-0001.xml>


More information about the Qgis-user mailing list