On Mon, 06 May 2013 20:44:30 +0200, Armin Burger wrote:
> I would suggest you set the debugging level to a higher value like 3
> and
> then check the query logging in the debug log,
It already was set to level 3.
> see
>
>
> http://svn.pmapper.net/trac/wiki/FaqDebugging#a3.Enablep.mapperdebuggi
I've solved Raffaele
you have to change in js_config.php
from
maxExtent: new OpenLayers.Bounds(-400, 300, 800, 1200)
to
maxExtent: new OpenLayers.Bounds(-432531.987809, 4080513.10311,
2779046.192174, 6350387.094751) in PM.mapOptions and PM.overviewMapOptions
it's very useful the d
I would suggest you set the debugging level to a higher value like 3 and
then check the query logging in the debug log, see
http://svn.pmapper.net/trac/wiki/FaqDebugging#a3.Enablep.mapperdebugging
it should contain the queries sent to PG.
armin
On 05/06/2013 05:34 PM, Moritz Lennert wrote:
> H
Hello,
I have two PostGIS layers: one with lines representing hiking paths, one
with polygons representing administrative units, with the mapfile
definitions in [1].
I am trying to elaborate a query in pmapper which would allow to select
an admin unit in an options list and then in a second fi
I' ve same problem.
I've changed Extent in mapfile with minx miny maxx maxy coordinates but
nothing happen.
I've also seen in js_config.php
maxExtent: new OpenLayers.Bounds(-400, 300, 800, 1200)
i've changed these values but still nothing happen.
--
View this message in contex
