Another step in my debugging is always, for problem database layers, is
to add an EXTENT parameter inside that same layer (which you get from an
ogrinfo command).
Also, if everything works (commandline, manual requests in browser),
then I always use a tool like Fiddler to get the exact (problem) request
that is being generated by QGIS.
Anyway, thanks again for using MS4W for sharing your spatial
information. Be sure to contact me and help support MS4W, as I see that
it is very important for your needs.
Thanks again,
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/
On 2016-11-23 11:48 AM, mathias cunault wrote:
I did what you said : I copy and paste layer by layer from the old
mapfile to a new one, and test each time. I did not make any
modification (as far as i know). Now I can get the capabilities in FF !
Thanks.
Now I have the list of layers in QGIS. But I can't load them : it seems
to have a problem of connection with PostGIS. Log error says :
Error executing SQL: (connection pointer is NULL
) in msPostGISLayerGetExtent()[Wed Nov 23 16:33:27 2016].216000
msPostGISLayerGetExtent(): General error message. Error executing SQL.
Check server logs.
I guess that the logs in the message are PostGIS ones ?
2016-11-23 15:10 GMT+01:00 Jeff McKenna <[email protected]
<mailto:[email protected]>>:
In that tiny mapfile (one layer), I would also remove any special
characters and numbers from any of your strings in that small
mapfile (so no accents, numbers, spaces in any NAME parameters, and
remove any special characters from the wms_title metadata or
elsewhere). Working with that copied mapfile and removing all those
things helps me debug always - then later I can go back to the full
mapfile, get that working at the commandline, then test with a
manual request in the browser, and finally test in a client such as
QGIS or OpenLayers.
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/ <http://www.gatewaygeomatics.com/>
On 2016-11-23 9:48 AM, Jeff McKenna wrote:
Hi,
Regarding your issue, here is my advice for how I always debug
such a
situation:
- I narrow down the mapfile until I am able to have the
smallest/shortest mapfile that still generates the error (one layer,
simple classification)
- once I have that tiny mapfile, then examine that one problem layer
(most times I also change the data in that layer, from something
like a
PostGIS connection to a local shapefile, and see if that changes
anything)
- for OGC/WMS requests, I will run the request directly from the
MS4W
commandline, such as:
setenv.bat
mapserv -nh
QUERY_STRING="map=D:\ms4w\blah.map&SERVICE=wms&REQUEST=GetCapabilities"
getcap.xml
And open that generated xml file to check for any errors or
"WARNING"s
in the response.
Thank you for the positive feedback from you that MS4W is
working great
for you and your clients.
-jeff
_______________________________________________
mapserver-users mailing list
[email protected] <mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/mapserver-users
<http://lists.osgeo.org/mailman/listinfo/mapserver-users>
--
/----------/
/Mathias Cunault/
/chargé d’opération et de recherche
///Inrap Tours - /148 av. Maginot
37000 TOURS
06 32 05 98 96
[email protected] <mailto:[email protected]>_/
www.inrap.fr <http://www.inrap.fr>
abonnez-vous à la lettre d'information de l'Inrap :
http://www.inrap.fr/newsletter.php
Darth Mathias : "Topology is a pathway to many abilities some consider
to be unnatural"
Padwan : "Is it possible to learn this power ?"
Darth Mathias : "Not from an archaeologist !"
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
