Re: [mapserver-users] MapServer v GeoServer

[Yves Moisan]

There have been lots of comparisons done, just Goggle mapserver vs 
geoserver.


IMHO the big differences are:

-Platform: C/C++ vs Java

-GeoServer WFS-T Support (although see TinyOWS for WFS-T and MapServer)

-GeoServer GUI-based configuration (vs mapfiles)

You may also be interested in the 2010 WMS shootout results : 
http://2010.foss4g.org/wms_benchmarking.php  See the link at the bottom 
of that page to the PDF for results.  That's one "neutral" comparison, 
albeit for one aspect of things : WMS performance.


My 2 cents.

Yves
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] PNG Optimization

[Yves Moisan]

Hi Thomas,

Thanx for sharing this benchmark.  I've tried optipng for fun and didn't 
see much difference with a 27 KB Agg/png file (saved about 600 bytes 
even with -o7).  I'm eager to see compression post-processing strategies 
that are worth it.


Cheers,

Yves


Cedric,
Mapserver currently doesn't support png options, although this
souldn't be to difficult to add as a FORMATOPTION (at least for the
non GD renderers).
You should note that the quality of the compression you apply to pngs
has a non trivial effect on the overall rendering time, so we can't
just add maximum compression by default.

ps: you can see the effect of png compression schemes (on throughput
and image size) on this small benchmark I ran for mod-geacache. the
use case is the on the fly merging of two 256x256 png tiles:
http://mod-geocache.googlecode.com/svn-history/r69/trunk/static/benchmark.png

regards,
thomas


2010/12/10 Cédric MOULLET:

Hi,
We are using MapServer to generate tiles and the following ouptut format is
used:

OUTPUTFORMAT
  NAME "pnga"
  MIMETYPE "image/pnga"
  DRIVER "AGG/PNG"
  EXTENSION "png"
  IMAGEMODE "RGBA"
  TRANSPARENT TRUE
  FORMATOPTION "INTERLACE=OFF"
END

We observe that the size of the tiles can be reduced by a at least factor 2
if we use a tool like optipng.
Is it possible to configure MapServer in order to optimize the file output
(and for example use optipng)  ? Or do you see another way to optimize the
image (I'd like to do that on the MapServer side in order to avoid a
postprocessing) ?
Thanks in advance for any hints.
Cédric

--
Welcome to my world: http://www.cedricmoullet.com/
My Linked In profile: http://www.linkedin.com/in/cedricmoullet
Twitter: http://twitter.com/cedricmoullet
Home sweet home:
http://map.geo.admin.ch/?crosshair=bowl&zoom=11&X=185241.24219&Y=561288.90625&bgOpacity=0&selectedNode=node_ch.swisstopo.fixpunkte-lage1

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users



___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users



___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Mapserver crashes with large number of layers

[Yves Moisan]

Dear List,

we're kind of stuck with the following problem:

First of all we are running Mapserver 5.6.5 in CGI Mode on Windows
2003 Server (64bit).

Hi,

I would first try to run it in FastCGI.  We also found running PHP (if 
you are using MS4W for instance) in FastCGI helps.

  Webserver is Apache 2.2.

We have a large Mapfile (seperated into 5 different parts using
INCLUDE) with a total of 571 Layers.
Try to keep separate mapfiles.  The shorter they are the better.  We 
also found putting STATUS OFF helps.

The layers have different
MAXSCALEDENOM values  so not all of them are drawn at all scales. The
layers are referencing the DATA via TILEINDEX (it's S-57 data read
through OGR). Most of the layers cover only a small area, so if I zoom
in to the map more and more layers must be taken into account of
drawing but only a small number must be drawn. All of the layers are
divided into three groups using the GROUP parameter.
What happens if I zoom in to the map at some point mapserver crashes
(actually it's not crashing it just stucks). If I reduce the total
number of layers (by commenting out parts of the mapfile) the map will
be drawn again. So my guess is that there is a problem with the number
of layers (or styles?, or symbols?, or number of layers per group?)
included.

Keep mapfiles small is what we found was most useful.

I turned on debugging on all of my layers but that didn't helped. If I
check the taskmanager mapserver.exe goes to 100% cpu usage and goes
back to zero after a few seconds but it's not being terminated. It's
still running in the process list. Debug output stops right in the
middle of the line. No error message is send to the client or written
to any of the logfiles. Actually no response is send to the client at
all. If I terminate the process using the task manager "Premature end
of script headers: mapserv.exe" is written to the apache error.log and
the client shows "Internal Server Error".
I've had premature end os script headers from time to time.  I have no 
idea what triggers that.


HTH,

Yves

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Connection pooling

[Yves Moisan]

Hi All,

Noticing that postgres.exe processes pop and die quite a bit (Win 2003 
Server), I started looking for tricks to avoid that and came across an 
old post from Paul : 
http://postgis.refractions.net/pipermail/postgis-users/2003-July/002729.html. 



Is this still applicable ?  I suspect yes, but just to be sure.  I don't 
like ProcessExplorer to show all those connections popping up and die ...


Cheers,

Yves
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WMS 1.3.0 questions

[Yves Moisan]

3- That may not be obvious, but MapServer honors the VERSION that you
set in a GetMap request...

Hi Daniel,

I would say it's confusing to see VERSION=1. going through ...


it's just that it works with ranges of
versions for each version-specific difference in the spec instead of
discrete version numbers in an attempt to be forgiving of clients that
support only intermediate versions that MapServer may not be explicitly
built for. More specifically:

(0.0.0<  VERSION<  1.0.7) is treated as 1.0.0

(1.0.7<= VERSION<  1.1.0) is treated as 1.0.7

(1.1.0<= VERSION<  1.1.1) is treated as 1.1.0

(1.1.1<= VERSION<  1.3.0) is treated as 1.1.1

(VERSION>= 1.3.0) is treated as 1.3.0


A word from a coder is worth a thousand [GetMap] images ;-).  That's 
really clear.  But misleading for the client/map integrator IMO.

4- After seeing this thread, I would tend to lean towards producing an
exception if version is not one of the explicitly supported values to
prevent any confusion (i.e. anything not in the following list would
produce an exception: 1.0.0, 1.0.6, 1.0.7, 1.1.0, 1.1.1 and 1.3.0)

I think that's a very sensible solution.  Especially since the VERSION 
parameter is required.  Trying to push a GetMap request without a 
VERSION url parameter already generates an error : "msWMSDispatch(): WMS 
server error. Incomplete WMS request: VERSION parameter missing".  I 
think failing to find an explicit VERSION number in a set of allowed 
values should trigger a similar exception,  something along the lines of 
"msWMSDispatch(): WMS server error. Offending (or misformed or 
something) WMS request: VERSION parameter not in {1.0.0, 1.0.6, 1.0.7, 
1.1.0, 1.1.1, 1.3.0}".


That behaviour would at least comfort me as a user that the VERSION 
number I'm passing in is the one used, short of having a response header 
confirming that (which appears to be an impossible task anyways).


Thanx,

Yves

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WMS 1.3.0 questions

[Yves Moisan]

Le 2010-11-09 21:48, Jeff McKenna a écrit :

Hello Yves,

Hi Jeff,


Some related thoughts:

- related ticket for configuring default WMS version: 
http://trac.osgeo.org/mapserver/ticket/3444 ...please add yourself to 
the CC list of that ticket and join in the discussions and testing and 
feedback, thanks
I added myself in the cc list.  The description of that ticket says "For 
example in WMS if the version parameter is not set, MapServer 
 usually defaults to the 
latest supported version (1.3.0)."  If I read this correctly, if I 
change MapServer from 5.2.x to 5.6 and I happen to be working with EPSG 
codes that have their axes flipped between 1.1.1 and 1.3.0, my WMS 
requests won't work anymore IF i didn't specify a version number.  Ouch.


Also, what happens if I specify a non existent, but valid, number like 
1. ?  I know an image is an image as Jukka mentioned, but how do I 
know how MapServer interpreted my faulty version number ?  Does it 
default to the latest supported version too ?


- doc pointers: 
http://www.mapserver.org/ogc/wms_server.html#wms-1-3-0-support 
...specifically see the 2 working 1.3.0 example requests there


I've seen those.  I can see the request parameters all right, it's just 
that I'm not sure how MapServer reacts.  I know it chokes if I send 
VERSION=abc, but it will send me an image whatever I use for a version 
number as long as it is of the forms x.y or x.y.z.  
VERSION=1234.4567.890 will work !  Because I get only an image back, how 
do I know how MS handled the request ?  Is there a response header I'm 
missing somewhere ?


Thanx.

Yves

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WMS 1.3.0 questions

[Yves Moisan]

Hi All,

I tried to look for an answer to the question "what do I have to do to 
get MapServer to serve a 1.3.0 WMS by default" and I haven't found yet.  
Is there anything to do in the mapfile per se or is it just by the 
virtue of having a version >= 5.4 ?  I thought the latter but then I 
tried things like :


http://toMapserv.cgi?...REQUEST=GetMap&VERSION=1.3.0&CRS=EPSG%3A42304&BBOX=-5175875.27581...&WIDTH=1605&HEIGHT=316

and

http://toMapserv.cgi?...REQUEST=GetMap&VERSION=1.1.1&CRS=EPSG%3A42304&BBOX=-5175875.27581...&WIDTH=1605&HEIGHT=316

and wondered if I'm getting back the response from a 1.3.0 in the first 
case and a 1.1.1 in the second case.  Both images were the same, so I 
thought everything was fine until I tried an unexisting version number 
(e.g. 1.1.122) and still got back an image !


The only error message that made me think MS was indeed looking at the 
version number is when I submitted VERSION=abc.  then MS complained it 
wanted "x.y" or "x.y.z".  So how can I tell I get a real WMS with my 
specified version number instead of what appears to be a default one ?


Doc pointers appreciated.

Yves
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Re: mapserver and i18n

[Yves Moisan]

 Le 2010-10-12 09:36, tellett a écrit :

Hi Stephen, at the moment I'm writing a draft RFC that proposes changes to
make mapserver 'INSPIRE compliant', we're proposing a whole package of
changes (hopefully not too major!!) and I could add this problem to that. Of
course we're creating separate tickets where relevant so I could do this as
well.

Cheers

Tom

Hi All,

I18N is also of significant interest for us north of the US border.  
There are close to 7 Million french speaking folks in Québec.


Cheers,

Yves
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Difference in GD vs AGG PNG output -- seams in my shape files.

[Yves Moisan]

Hi,

I recently upgraded from 5.2.x to 5.6.1, and from GD to AGG.

Here is my output:

AGG: http://i44.tinypic.com/5oh261.png

GD: http://i39.tinypic.com/2h4j409.png

Visual Representation of the shapefile: http://i44.tinypic.com/1zz2u76.png

Look north of Cancun -- the AGG driver is showing seams where the 
polygons connect in my shape file.  It doesn't do it for all of them, 
but I see it a lot, especially when the seams are not straight N/S or 
E/W.  I feel that it has something to do with AGG's antialiasing, but 
I've not been able to pin it down.


Is there any way to resolve this?  I'd really like to use the AGG 
driver, I love the output it produces, minus the white lines!


Mark


Give that url a try : 
http://linfiniti.com/2010/03/comparing-renderers-in-mapserver/


HTH,

Yves
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Truncated msGMLOutput

[Yves Moisan]

> My first guess would be that the mapserv process aborts (seg faults?).
> 
> I'd suggest you enable MS_ERRORFILE/DEBUG at both the map and layer 
> level and look for any hints in the debug output. Also check your Apache 
> error_log for signs of a seg fault (not sure if you'd see anything on 
> Windows though).
> 
> Daniel

Hi Daniel,

Yes, I've just set an error file location (as per Julien's offline
suggestion just before yours) and found out the issue was a boolean to
text cast issue.  I made a view out of my table getting rid of the
faulty column and everything is ok now.  

I wonder why though MS returns a malformed GML output instead of an
error message.

Cheers,

Yves


___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Truncated msGMLOutput

[Yves Moisan]

Hi All,

I have a truncated msGMLOutput document for one of my layers and I fail
to understand where the problem is.  It looks similar to
http://trac.osgeo.org/mapserver/ticket/779 but for GetFeatureInfo.  I'm
running MS 5.2.1 under windows.  I tried to run the query on the
commandline and here's what I get : 

E:\mydir\ms4w\Apache\cgi-bin>mapserv
"QUERY_STRING=map=../mapfiles/mymapfile.map&QUERY_LA
YERS=stations&LAYERS=stations&REQUEST=GetFeatureInfo&EXCEPTIONS=application%2Fvnd.ogc.se_xml&VERSION
=1.0.0&SRS=EPSG%3A32644&BBOX=373865.273287%2C2090503.076491%
2C374934.203341%2C2090907.506727&X=406&Y
=293&INFO_FORMAT=gml%3B%20charset%3Diso-8859-1&FEATURE_COUNT=1000"

Content-type: text/xml



http://www.opengis.net/gml";
 xmlns:xlink="http://www.w3.org/1999/xlink";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>


I guess there's something wrong in my layer definition but I can't see
it so here it is :

LAYER
NAME 'stations'
TYPE POINT
DUMP TRUE
STATUS On
TEMPLATE void
CLASSITEM e_cat_station_type_id
CONNECTION 'user=user password=pwd dbname=mydb host=localhost
port=5433'
CONNECTIONTYPE POSTGIS
DATA '"the_geom_dummy_32644" FROM "e_cat_station" USING UNIQUE
e_cat_station_id USING SRID=32644'

METADATA 
  'DESCRIPTION' 'Stations'
  'LAYER_ENCODING' 'UTF-8'
  "wms_title"  "Monitoring station"
  "wms_srs"  "EPSG:32644"
  "gml_include_items" "all"
END  # Metadata

TRANSPARENCY 100
TOLERANCE 5

CLASS
NAME "Number7"
EXPRESSION "7"
STYLE
  SYMBOL 'circle'
  OUTLINECOLOR 0 0 0
  COLOR 0 255 0
  SIZE 18
END
END
CLASS
NAME "All Stations"
STYLE
  SYMBOL 'circle'
  OUTLINECOLOR 0 0 0
      COLOR 255 0 0
  SIZE 6
END
END


  END  # Layer

The layer shows well (except for the CLASSITEM which I have to sort out,
but that's another issue).  What am I doing wrong and also how can a
truncated XML be generated like this ?

TIA,

Yves Moisan

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users