[Mapserver-users] two questions

[W. Steph]

The mapserver standard engine is a web script. The wms is also a web script. 
The main difference are the arguments passed to the script : in wms, the 
arguments must respect the wms standard. But in term of performances, you'll 
probably wait the same time for the same query with the two scripts (wms and 
standard mapserver).
If you take a deeper look at mapserver arguments (I'm talking about the 
mapserver *script*, not the engine), you'll find that they are the same as 
WMS arguments (height, width, layer...), but with another argument : MAP. 
The idea is to edit your apache config file (usually httpd.conf) and to add 
this line :

SetEnvIf Request_URI "/cgi-bin/wms" 
MS_MAPFILE=path/to/my/map/file/mapfile.map

Where "cgi-bin/wms" is a renamed copy of the mapserver executable script.
Then your "wms" script will be a wms compliant script.
And this script will be as effecient as the standard mapserver script of 
course !
You should read the MapServer WMS Server - Client HOWTO on the mapserver web 
site to get more infos on how to make a wms compliant server with mapserver.

>From: "Giorgio Plazzotta" <giorgio.plazzotta at sarasricerche.it>
>To: "W. Steph" <chewbizz at hotmail.com>
>Subject: Re: [Mapserver-users] two questions
>Date: Fri, 11 Jul 2003 12:41:50 +0200
>
>thank you very much for this useful answer.
>but do u know something about the performances when accessing the data
>through a wms or through the mapserver standard engine?
>
>Giorgio
>
>
>----- Original Message -----
>From: "W. Steph" <chewbizz at hotmail.com>
>To: <giorgio.plazzotta at sarasricerche.it>
>Sent: Friday, July 11, 2003 10:55 AM
>Subject: Re: [Mapserver-users] two questions
>
>
> > Hello !
> >
> > I don't know the answer to your first question, but the second one is 
>easy
>:
> > WMS is a specification comming from the OGC (then open gis consortium),
>take
> > a look at :
> > http://www.opengis.org (you'll find the WMS Spec and other interesting
> > specs)
> > Using this spec and making your server WMS-Compliant is very important 
>to
>be
> > inter-operable with other WMS. Using the WMS spec enables other servers 
>to
> > get geographic data using a simple script. And you can do the same in 
>your
> > application : you can use other's WMS scripts to get external data. And 
>it
> > could be very usefull.
> > I advise you to put a WMS compliant script within your server, (even if
>your
> > application doesn't use this script to get data) to let other map 
>servers
> > access your data.
> > For example, if you have a wms script at url :
>http://my.domain/cgi-bin/wms
> > , it could be used by anyone to get your data ; example :
> >
>http://my.domain/cgi-bin/wms?WMTVER=1.0.0&REQUEST=map&BBOX=10,10,1000,1000&WIDTH=400&HEIGHT=300&LAYERS=BOUNDARIES&FORMAT=PNG
> > This will return a 400x300 PNG image of the layer called "BOUNDARIES"
>within
> > the extent (10,10,1000,1000)
> >
> > >From: "Giorgio Plazzotta" <giorgio.plazzotta at sarasricerche.it>
> > >To: <mapserver-users at lists.gis.umn.edu>
> > >Subject: [Mapserver-users] two questions
> > >Date: Thu, 10 Jul 2003 09:27:32 +0200
> > >
> > >I have two doubts (well probably even more than 2) that maybe somebody
>can
> > >help me to solve.
> > >1) I still use the 3.6 version and therefore I have to optimize the
>raster
> > >laters to 256 colors. When i will be able to use 24 bit color rasters
>what
> > >will happen to the performances in that same raster layer? I mean,
> > >sometimes 256 volors are really unacceptable but maybe in some 
>situations
> > >it's only a matter od graphic perfection (a DTM for example) and 256
>colors
> > >are not so bad. In these situations maybe one could choose to go for 
>the
>8
> > >bit just to preserve performances even id we could serve it 24 bit.
> > >
> > >2) I didn't understand very well all the characteristics of WMS and the
> > >differences of chooseing this platform instead of a normal mapserver
> > >engine. Can anybody suggest a good resource (pref. online) where i can
> > >improve my knowledge? I understood that a wms is the solution when
>mapping
> > >is only a part of the application i am buiding cause i insert the map
> > >service inside it like a component. But if i am developing an 
>application
> > >in which mapping is the main goal probably it's better (performances?) 
>to
> > >choose a more traditional way to serve maps.
> > >
> > >Thanx
> > >Giorgio
> > >
> >
> > _________________________________________________________________
> > Hotmail : un compte GRATUIT qui vous suit partout et tout le temps !
> > http://g.msn.fr/FR1000/9493
> >
> >
>
>

_________________________________________________________________
Trouvez l'âme soeur sur MSN Rencontres ! http://g.msn.fr/FR1000/9551