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/
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]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
