I've made progress and I may have encountered a bug (or I'm just naive).
Turns out my issue with layers displaying was because of a difference in the
layers 'Layer Name' and the 'Displayed Name' (in QGIS 2.4 layer
properties/general). If I changed the layer display name by right clicking
on the l
Glad to know Im not the only one.
I didn't consider checking whether the polygons were valid...maybe there is
an error in one of them.
I can confirm that none of the layers I'm dealing with have between 5 & 4000
features in them that show up fine in QGIS Desktop and QGIS Server (getmap).
The rea
Hi Carlos,
I recently had the situation that one of my layers contained polygons
with errors (PostGIS). It was drawn in QGIS desktop but did not show up
in QWC. I did not investigate further but fixed the errors.
Furthermore I used to have a layer which eventually contained no
features, thus Q
Played with this a lot today, and the only thing that fixed the issue was to
change the WMS service in the gs files to WMS 1.0 from WMS 1.3
So now a map with load, correctly zoomed to the projectsettings extents, but
some layers are loading unchecked as if they have no data (which is not the
case)
Hi Carlos,
a lot has changed in QWC since december, however I would compare your
old GlobalOptions.js with the new one, especially in the MapOptions and
LayerOptions sections.
Hm, when looking at your GetProjectSettings response the bbox for the
layer is different from where the layer is locat
Thanks for the guidance Bernhard! I totally missed that setting when I was
going through the setup. I'll be sure to review the openlayers api docs.
Unfortunately, changing it did not solve my issue, and I would have figured
that the coordinate issue (with Lat changing when panning left - right)
w
Hi,
I rechecked your GlobalOptions.js and realized in l. 198 you set map
units to metres, I think, this should be "degrees" for EPSG:4326.
Please be sure to know what each parameter you set in MapOptions and
LayerOptions means and why you set it the way you do. Check the
OpenLayers api doc for
I did find the QWC bounding box being issued. It only issues a call for the
project when you zoom all the way out and when it does I get this (before
changing the yx arg)
http://gis.idn12.com/qgis/qgis_mapserv.fcgi?map=C:/projects/elements/testshp2.qgs&LAYERS=VIEWS_2%2CCLAB_INRES_4326&OPACITIES=2
Hi Bernhard,
I tried the fix you suggested without any luck. In the GlobalOption.js I
downloaded yesterday the yx: argument was on l.252 (not sure if that
matters)
I don't know how to check what BBOX QWC issues (reviewed the client with
firebug but nothing stuck out)
I noticed that the lat-long
Hi Carlos,
change l. 215 of GlobalOptions.js to
yx: {"EPSG:4326": true},
and see if that helps
Background: WMS1.3 has reverse axis order for EPSG:4326 compared to
WMS1.1. Compare the BBOX in the GetMap request you posted to the one QWC
issues (before changing GlobalOptions)
Bernhard
Am 09.0
Hi everyone,
I've hit a brick wall. I was doing a new install of QGIS server, apache,
and QWC. The server loads the test qgis project as expected
http://gis.idn12.com/qgis/qgis_mapserv.fcgi?map=C:/projects/elements/testshp.qgs&LAYERS=CLAB_INRES_4326&OPACITIES=255,255,255&FORMAT=image/png&DPI=96&
11 matches
Mail list logo
