Hi,
Just to add to the comments on logging, there is a new pull request at
https://github.com/mapserver/mapserver/pull/5707It makes sense to me that it
should be possible to turn off logging for
queries not returning features.The tests, and client applications however
benefit from a message
The debug levels are 0 to 5, 0 being none, and 5 being the most verbose.
I believe the problem in msDrawRasterLayerLow() is that it uses a "=="
test instead of a ">=".
i.e. it uses:
if(layer->debug == MS_TRUE)
but it should use
if(layer->debug >= 1)
or even better use the
I have an interest in this as well, more from the perspecitive of different
data source call though. Connecting up to other data sources has historically
been a pain to debug. I could help with this at the sprint too and most likely
not break anything too bad.
:c)
bobb
On Nov 16, 2018,
This isn't surprising. We haven't been real good about consistently using
levels across the code base - cleaning that up would be a good project (or
sprint activity) and wouldn't require deep technical knowledge.
I'll create a ticket for the case you've pointed about below...
--Steve
From:
Hi,
I have always used just "DEBUG 5" for debugging raster layers but now I finally
made a test with Mapserver 7.0.1 for seeing what is the real difference between
the debugging levels. I was a bit surprised to see that there is not so much
difference at all, and that the DEBUG 1 level gives
