[mapserver-users] Problems with time-enabled WMS (WMS-T) in a cascaded layer
Hello, I am trying to make time-enabled WMS-T requests to a cascaded layer that originates from the NASA MODIS services. I can successfully make calls to directly to the NASA service as below: http://neowms.sci.gsfc.nasa.gov/wms/wms?version=1.1.1&service=WMS&request=GetMap&SRS=EPSG:4326&FORMAT=image/jpeg&STYLES=&BBox=-120.000,26.000,-97.000,44.000&Width=600&Height=470&Layers=MOD13A2_E_NDVI&TIME=2000-02-18 ...other applicable dates include 2000-05-09, 2000-03-22, and 2011-02-02... The NASA getCapabilities URL for this layer is: http://neo.sci.gsfc.nasa.gov/FGDCMetadata?datasetId=MOD13A2_E_NDVI and the NASA getCapabilites URL for the entire WMS service is: http://neowms.sci.gsfc.nasa.gov/wms/wms?version=1.3.0&service=WMS&request=GetCapabilities When I try to pass a &TIME argument to the cascaded layer, I only get the image for the default time as specified in the NASA getCapabilities call to the WMS service My cascaded URL looks like this: http://edacwms.unm.edu/cgi-bin/mapfiles/epht_environment/epht_enviro_wms?version=1.1.1&SERVICE=WMS&REQUEST=GetMap&FORMAT=image/jpeg&STYLES=&SRS=EPSG:26913&BBOX=-1011825.41,2963772.82,1141463.33,4903085.27&Width=600&Height=470&Layers=MOD13A2_E_NDVI&TIME=2000-05-09 and the LAYER definition looks like this: LAYER NAME "MOD13A2_E_NDVI" TYPE RASTER CONNECTION "http://neowms.sci.gsfc.nasa.gov/wms/wms?"; CONNECTIONTYPE WMS STATUS ON METADATA "wms_name" "MOD13A2_E_NDVI" "wms_server_version""1.1.1" "wms_srs" "EPSG:4326" "wms_abstract" "Vegetation Index NDVI 16 day - Terra/MODIS" "wms_title" "Vegetation Index NDVI 16 day - Terra/MODIS" #"wms_time" "2011-02-02" "wms_format""image/jpeg" "wms_connectiontimeout" "60" "wms_latlonboundingbox" "-180 -90 180 90" "wms_transparent" "FALSE" "wms_timeextent" "2000-02-18,2000-03-06,2000-03-22,2000-04-07,2000-04-23,2000-05-09,2000-05-25,2000-06-10,2000-06-26,2000-07-12,2000-07-28,2000-08-13,2000-08-29,2000-09-14,2000-09-30,2000-10-16,2000-11-01,2000-11-17,2000-12-03,2000-12-19,2001-01-01,2001-01-17,2001-02-02,2001-02-18,2001-03-06,2001-03-22,2001-04-07,2001-04-23,2001-05-09,2001-05-25,2001-06-10,2001-06-26,2001-07-12,2001-07-28,2001-08-13,2001-08-29,2001-09-14,2001-09-30,2001-10-16,2001-11-01,2001-11-17,2001-12-03,2001-12-19,2002-01-01,2002-01-17,2002-02-02,2002-02-18,2002-03-06,2002-03-22,2002-04-07,2002-04-23,2002-05-09,2002-05-25,2002-06-10,2002-06-26,2002-07-12,2002-07-28,2002-08-13,2002-08-29,2002-09-14,2002-09-30,2002-10-16,2002-11-01,2002-11-17,2002-12-03,2002-12-19,2003-01-01,2003-01-17,2003-02-02,2003-02-18,2003-03-06,2003-03-22,2003-04-07,2003-04-23,2003-05-09,2003-05-25,2003-06-10,2003-06-26,2003-07-12,2003-07-28,2003-08-13,2003-08-29,2003-09-14,2003-09-30,2003-10-16,2003-11-01,2003-11-17,2003-12-03,2003-12-19,2004-01-01,2004-01-17,2004-02-02,2004-02-18,2004-03-06,2004-03-22,2004-04-07,2004-04-23,2004-05-09,2004-05-25,2004-06-10,2004-06-26,2004-07-12,2004-07-28,2004-08-13,2004-08-29,2004-09-14,2004-09-30,2004-10-16,2004-11-01,2004-11-17,2004-12-03,2004-12-19,2005-01-01,2005-01-17,2005-02-02,2005-02-18,2005-03-06,2005-03-22,2005-04-07,2005-04-23,2005-05-09,2005-05-25,2005-06-10,2005-06-26,2005-07-12,2005-07-28,2005-08-13,2005-08-29,2005-09-14,2005-09-30,2005-10-16,2005-11-01,2005-11-17,2005-12-03,2005-12-19,2006-01-01,2006-01-17,2006-02-02,2006-02-18,2006-03-06,2006-03-22,2006-04-07,2006-04-23,2006-05-09,2006-05-25,2006-06-10,2006-06-26,2006-07-12,2006-07-28,2006-08-13,2006-08-29,2006-09-14,2006-09-30,2006-10-16,2006-11-01,2006-11-17,2006-12-03,2006-12-19,2007-01-01,2007-01-17,2007-02-02,2007-02-18,2007-03-06,2007-03-22,2007-04-07,2007-04-23,2007-05-09,2007-05-25,2007-06-10,2007-06-26,2007-07-12,2007-07-28,2007-08-13,2007-08-29,2007-09-14,2007-09-30,2007-10-16,2007-11-01,2007-11-17,2007-12-03,2007-12-19,2008-01-01,2008-01-17,2008-02-02,2008-02-18,2008-03-06,2008-03-22,2008-04-07,2008-04-23,2008-05-09,2008-05-25,2008-06-10,2008-06-26,2008-07-12,2008-07-28,2008-08-13,2008-08-29,2008-09-14,2008-09-30,2008-10-16,2008-11-01,2008-11-17,2008-12-03,2008-12-19,2009-01-01,2009-01-17,2009-02-02,2009-02-18,2009-03-06,2009-03-22,2009-04-07,2009-04-23,2009-05-09,2009-05-25,2009-06-10,2009-06-26,2009-07-12,2009-07-28,2009-08-13,2009-08-29,2009-09-14,2009-09-30,2009-10-16,2009-11-01,2009-11-17,2009-12-03,2009-12-19,2010-01-01,2010-01-17,2010-02-02,2010-02-18,2010-03-06,2010-03-22,2010-04-07,2010-04-23,2010-05-09,2010-05-25,2010-06-10,2010-06-26,2010-07-12,2010-07-28,2010-08-13,2010-08-29,2010-09-14,2010-09-30,2010-10-16,2010-11-01,2010-11-17,2010-12-03,2010-12-19,2011-01-01,2011-01-17,2011-02-02" #"wms_timeextent" "2000-02-18,2000-03-06/2000-12-19/P16D,2001-01-01/2001-12-19/P16D,2002-01-01/2002-12-19/P16D,2003-01-01/2003-12-19/P16D,2004-01-01/2004-02-18/P16D,2004-03-06/2004-12-19/P16D,2005-01-01/2005-12-19/P16D,2006-01-01/2006-12-19/P16D,2007-01-01/2007-12-19/P16D,2008-01-01/2008-02-18/P16D,2008-03-06/2008-12-19/P16D,2009-01-01/2009-12-19/P16D,20
VS: [mapserver-users] Problem with cascading WMS reprojection
Thank you Jukka, Your solution worked! ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
RE: [mapserver-users] Problem with cascading WMS reprojection
Should the MAP PROJECTION block be in the MAP object? -Original Message- From: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of William Hudspeth Sent: Thursday, March 24, 2011 12:50 PM To: mapserver-users@lists.osgeo.org Cc: w...@unm.edu Subject: [mapserver-users] Problem with cascading WMS reprojection Hello, I am trying to reproject a cascaded NASA MODIS NDVI raster. The original raster is served as epsg:4326 from the NASA servers. It is using version=1.3.0 and CRS-CRS:84. I am cascading it through my own mapserver client/server and trying to reproject as epsg:26913 (utm zone13), where the MAP projection and extents are in 26913. My MAP projection looks like this: MAP . EXTENT 93549 3464749 694099 4065299 UNITS METERS . END #END MAP OBJECT PROJECTION "init=epsg:26913" #UTM-Zone 13N END #END MAP PROJECTION OBJECT and, my LAYER definition looks like this: LAYER NAME "MOD13A2_E_NDVI" TYPE RASTER CONNECTION "http://neowms.sci.gsfc.nasa.gov/wms/wms?"; CONNECTIONTYPE WMS STATUS ON METADATA "wms_name""MOD13A2_E_NDVI" "wms_server_version" "1.1.1" "wms_srs" "EPSG:4326" "wms_format" "image/jpeg" "wms_latlonboundingbox" "-180 -90 180 90" "wms_transparent" "FALSE" END #METADATA PROJECTION "init=epsg:4326" #WGS84 Decimal Degrees END #PROJECTION END #LAYER Interestingly, even though the MAP projection is NOT set to EPSG:4326, I can make a successful request using epsg:4326. In all cases, the LAYER metadata uses EPSG:4326. So, while this request is successful: http://edacwms.unm.edu/cgi-bin/mapfiles/epht_environment/epht_enviro_wms?version=1.1.1&SERVICE=WMS&REQUEST=GetMap&FORMAT=image/jpeg&STYLES=&SRS=EPSG:4326&BBOX=-120.000,26.000,-97.000,44.000&Width=600&Height=470&Layers=MOD13A2_E_NDVI This one is NOT successful: http://edacwms.unm.edu/cgi-bin/mapfiles/epht_environment/epht_enviro_wms?version=1.1.1&SERVICE=WMS&REQUEST=GetMap&FORMAT=image/jpeg&STYLES=&SRS=EPSG:26913&BBOX=93549,3464749,694099,4065299&Width=600&Height=470&Layers=MOD13A2_E_NDVI where I get an error: msWMSLoadGetMapParams(): WMS server error. Invalid SRS given : SRS must be valid for all requested layers. Any insight would be greatly appreciated... Bill ___ 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
VS: [mapserver-users] Problem with cascading WMS reprojection
Hi, I would try what happens if the whole PROJECTION block is removed from the LAYER. And I believe it would be good to add "wms_srs" with a list of projections you would like to support into MAP level METADATA object. -Jukka Rahkonen- -Alkuperäinen viesti- Lähettäjä: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] Puolesta William Hudspeth Lähetetty: 24. maaliskuuta 2011 19:50 Vastaanottaja: mapserver-users@lists.osgeo.org Kopio: w...@unm.edu Aihe: [mapserver-users] Problem with cascading WMS reprojection Hello, I am trying to reproject a cascaded NASA MODIS NDVI raster. The original raster is served as epsg:4326 from the NASA servers. It is using version=1.3.0 and CRS-CRS:84. I am cascading it through my own mapserver client/server and trying to reproject as epsg:26913 (utm zone13), where the MAP projection and extents are in 26913. My MAP projection looks like this: MAP . EXTENT 93549 3464749 694099 4065299 UNITS METERS . END #END MAP OBJECT PROJECTION "init=epsg:26913" #UTM-Zone 13N END #END MAP PROJECTION OBJECT and, my LAYER definition looks like this: LAYER NAME "MOD13A2_E_NDVI" TYPE RASTER CONNECTION "http://neowms.sci.gsfc.nasa.gov/wms/wms?"; CONNECTIONTYPE WMS STATUS ON METADATA "wms_name""MOD13A2_E_NDVI" "wms_server_version" "1.1.1" "wms_srs" "EPSG:4326" "wms_format" "image/jpeg" "wms_latlonboundingbox" "-180 -90 180 90" "wms_transparent" "FALSE" END #METADATA PROJECTION "init=epsg:4326" #WGS84 Decimal Degrees END #PROJECTION END #LAYER Interestingly, even though the MAP projection is NOT set to EPSG:4326, I can make a successful request using epsg:4326. In all cases, the LAYER metadata uses EPSG:4326. So, while this request is successful: http://edacwms.unm.edu/cgi-bin/mapfiles/epht_environment/epht_enviro_wms?version=1.1.1&SERVICE=WMS&REQUEST=GetMap&FORMAT=image/jpeg&STYLES=&SRS=EPSG:4326&BBOX=-120.000,26.000,-97.000,44.000&Width=600&Height=470&Layers=MOD13A2_E_NDVI This one is NOT successful: http://edacwms.unm.edu/cgi-bin/mapfiles/epht_environment/epht_enviro_wms?version=1.1.1&SERVICE=WMS&REQUEST=GetMap&FORMAT=image/jpeg&STYLES=&SRS=EPSG:26913&BBOX=93549,3464749,694099,4065299&Width=600&Height=470&Layers=MOD13A2_E_NDVI where I get an error: msWMSLoadGetMapParams(): WMS server error. Invalid SRS given : SRS must be valid for all requested layers. Any insight would be greatly appreciated... Bill ___ 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] Problem with cascading WMS reprojection
Hello, I am trying to reproject a cascaded NASA MODIS NDVI raster. The original raster is served as epsg:4326 from the NASA servers. It is using version=1.3.0 and CRS-CRS:84. I am cascading it through my own mapserver client/server and trying to reproject as epsg:26913 (utm zone13), where the MAP projection and extents are in 26913. My MAP projection looks like this: MAP . EXTENT 93549 3464749 694099 4065299 UNITS METERS . END #END MAP OBJECT PROJECTION "init=epsg:26913" #UTM-Zone 13N END #END MAP PROJECTION OBJECT and, my LAYER definition looks like this: LAYER NAME "MOD13A2_E_NDVI" TYPE RASTER CONNECTION "http://neowms.sci.gsfc.nasa.gov/wms/wms?"; CONNECTIONTYPE WMS STATUS ON METADATA "wms_name""MOD13A2_E_NDVI" "wms_server_version" "1.1.1" "wms_srs" "EPSG:4326" "wms_format" "image/jpeg" "wms_latlonboundingbox" "-180 -90 180 90" "wms_transparent" "FALSE" END #METADATA PROJECTION "init=epsg:4326" #WGS84 Decimal Degrees END #PROJECTION END #LAYER Interestingly, even though the MAP projection is NOT set to EPSG:4326, I can make a successful request using epsg:4326. In all cases, the LAYER metadata uses EPSG:4326. So, while this request is successful: http://edacwms.unm.edu/cgi-bin/mapfiles/epht_environment/epht_enviro_wms?version=1.1.1&SERVICE=WMS&REQUEST=GetMap&FORMAT=image/jpeg&STYLES=&SRS=EPSG:4326&BBOX=-120.000,26.000,-97.000,44.000&Width=600&Height=470&Layers=MOD13A2_E_NDVI This one is NOT successful: http://edacwms.unm.edu/cgi-bin/mapfiles/epht_environment/epht_enviro_wms?version=1.1.1&SERVICE=WMS&REQUEST=GetMap&FORMAT=image/jpeg&STYLES=&SRS=EPSG:26913&BBOX=93549,3464749,694099,4065299&Width=600&Height=470&Layers=MOD13A2_E_NDVI where I get an error: msWMSLoadGetMapParams(): WMS server error. Invalid SRS given : SRS must be valid for all requested layers. Any insight would be greatly appreciated... Bill ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] MapServer 6.0.0-beta3 release
UbuntuGIS MapServer packages have been updated for the beta3 release: https://launchpad.net/~ubuntugis/+archive/ubuntugis-testing/ Alan On March 23, 2011 05:45:22 pm Daniel Morissette wrote: > The MapServer Team is pleased to announce the release of MapServer > 6.0.0-beta3. This is the latest beta on our way to a final 6.0 release. > We realize that it comes only 5 days after beta2, but it also contains > several important fixes and we encourage you to test it and continue to > provide feedback. > > The 6.0 release introduces important changes in key components of the > MapServer core (rendering, query and expressions), and for this reason > we count on you, MapServer power users, to help test the release in your > respective environments and provide feedback (through the users list or > Trac tickets). > > This is the third of four planned beta releases and if all goes well a > final release should occur around the end of April. The full release > plan which also includes the list of new features and changes in this > release is available at: >http://mapserver.org/trunk/development/release/release-plan-6.0.html > > The list of fixes since beta1 is attached at the end of this message. > For a complete list see the HISTORY.TXT file at: > > > http://trac.osgeo.org/mapserver/browser/tags/rel-6-0-0-beta3/mapserver/HIST > ORY.TXT > > We have started working on a 5.6 -> 6.0 migration guide. This document > contains important notes on backwards incompatibilities or other changes > required when upgrading to 6.0. It is not complete yet but we strongly > recommend that you review the latest version online at: > > http://mapserver.org/trunk/MIGRATION_GUIDE.html > > The source for this release can be downloaded at: > > http://mapserver.org/download.html > or > http://download.osgeo.org/mapserver/mapserver-6.0.0-beta3.tar.gz > > The binary distributions listed in the download page should be updated > with binaries for the new beta release in the next day or so. > > Once again we need your help to ensure a high quality product, so please > help out by testing your applications with this new code base. > > Thanks! - The MapServer Team > > > Version 6.0.0-beta3 (2011-03-23) > > > - apply min/max size/width style values to polygon spacing (vaguely related >to #3132) > > - assure that a created tile has a non-zero width and height (#3370) > > - use png_sig_cmp instead of png_check_sig (#3762) > > - Rendering: scale style OFFSET and GAP the same way we scale other style >attributes. Beforehand, we scaled them proportionaly to the computed > width. > > - KML: fix rounding problem for point feautres (#3767) > > - KML: update code to reflect output changes. Fix true type symbols. > (#3766) > > - SLD: Text Symbolizer now uses the new expression syntax (#3757) > > - WFS: correct bbox values for GetFeature with featureid request (#3761) > > - Mapscript Seg Fault on mapObj->getMetaData (#3738) > > - Correct double free in msCleanup(). > > - Initialize default formats in WCS. > > - Fix csharp Makefile.in (#3758) > > - Allow run-time subs in class->text (makes sense if you allow it in >class->expression). > > - Fix build problem when --enable-cgi-cl-debug-args is enabled (#2853) > > ___ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapserver-users -- Alan Boudreault Mapgears http://www.mapgears.com ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] showing line direction (without font)
clement, GEOMTRANSFORM END SYMBOL "arrowhead" ANGLE AUTO does what you want, with the arrowhead symbol being a truetype symbol with character '>'. you can also define arrowhead as a vector symbol with the points forming an arrowhead. -- thomas On Thu, Mar 17, 2011 at 15:28, Clément MONIER wrote: > Hi, > > > > Is it possible to display a layer of lines with direction’s marks using > MapServer ? > > With no “font trick” (i.e a char symbol like ‘>’,…) > > > > See picture attached showing a nice sample > > > > Thanks & Regards > > > > Clement > > ___ > 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] showing line direction (without font)
Hi, Is it possible to display a layer of lines with direction's marks using MapServer ? With no "font trick" (i.e a char symbol like '>',...) See picture attached showing a nice sample Thanks & Regards Clement <>___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
RE: [mapserver-users] MapServer 6.0.0-beta3 release
Packages for RHEL/CentOS/Scientific Linux 5 and as src.rpm: http://www.r3-gis.com/upload/mapserver-6.0.0beta3-1.0.el5.src.rpm http://www.r3-gis.com/upload/mapserver-6.0.0beta3-1.0.el5.x86_64.rpm http://www.r3-gis.com/upload/php-mapserver-6.0.0beta3-1.0.el5.x86_64.rpm http://www.r3-gis.com/upload/php-mapserver-proj-6.0.0beta3-1.0.el5.x86_64.rpm http://www.r3-gis.com/upload/mapserver-perl-6.0.0beta3-1.0.el5.x86_64.rpm http://www.r3-gis.com/upload/mapserver-python-6.0.0beta3-1.0.el5.x86_64.rpm http://www.r3-gis.com/upload/mapserver-java-6.0.0beta3-1.0.el5.x86_64.rpm http://www.r3-gis.com/upload/mapserver-debuginfo-6.0.0beta3-1.0.el5.x86_64.rpm These packages depend on http://wiki.osgeo.org/wiki/Enterprise_Linux_GIS and on the php53* packages, which might be found in http://dev.centos.org/centos/5/testing/x86_64/RPMS/php53/ , until CentOS 5.6 is out. Peter R3 GIS Srl - GmbH http://www.r3-gis.com Daniel Morissette wrote Subject: [mapserver-users] MapServer 6.0.0-beta3 release Date: 23.03.2011 22:45 >The MapServer Team is pleased to announce the release of MapServer >6.0.0-beta3. This is the latest beta on our way to a final 6.0 release. >We realize that it comes only 5 days after beta2, but it also contains >several important fixes and we encourage you to test it and continue to >provide feedback. > >The 6.0 release introduces important changes in key components of the >MapServer core (rendering, query and expressions), and for this reason >we count on you, MapServer power users, to help test the release in your >respective environments and provide feedback (through the users list or >Trac tickets). > >This is the third of four planned beta releases and if all goes well a >final release should occur around the end of April. The full release >plan which also includes the list of new features and changes in this >release is available at: > http://mapserver.org/trunk/development/release/release-plan-6.0.html > >The list of fixes since beta1 is attached at the end of this message. >For a complete list see the HISTORY.TXT file at: > > >http://trac.osgeo.org/mapserver/browser/tags/rel-6-0-0-beta3/mapserver/HISTORY.TXT > >We have started working on a 5.6 -> 6.0 migration guide. This document >contains important notes on backwards incompatibilities or other changes >required when upgrading to 6.0. It is not complete yet but we strongly >recommend that you review the latest version online at: > > http://mapserver.org/trunk/MIGRATION_GUIDE.html > >The source for this release can be downloaded at: > > http://mapserver.org/download.html >or > http://download.osgeo.org/mapserver/mapserver-6.0.0-beta3.tar.gz > >The binary distributions listed in the download page should be updated >with binaries for the new beta release in the next day or so. > >Once again we need your help to ensure a high quality product, so please >help out by testing your applications with this new code base. > >Thanks! - The MapServer Team > > >Version 6.0.0-beta3 (2011-03-23) > > >- apply min/max size/width style values to polygon spacing (vaguely >related > to #3132) > >- assure that a created tile has a non-zero width and height (#3370) > >- use png_sig_cmp instead of png_check_sig (#3762) > >- Rendering: scale style OFFSET and GAP the same way we scale other style > attributes. Beforehand, we scaled them proportionaly to the computed >width. > >- KML: fix rounding problem for point feautres (#3767) > >- KML: update code to reflect output changes. Fix true type symbols. >(#3766) > >- SLD: Text Symbolizer now uses the new expression syntax (#3757) > >- WFS: correct bbox values for GetFeature with featureid request (#3761) > >- Mapscript Seg Fault on mapObj->getMetaData (#3738) > >- Correct double free in msCleanup(). > >- Initialize default formats in WCS. > >- Fix csharp Makefile.in (#3758) > >- Allow run-time subs in class->text (makes sense if you allow it in > class->expression). > >- Fix build problem when --enable-cgi-cl-debug-args is enabled (#2853) > >___ >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
