WMS error after upgrade to 4.4
Yewondwossen Assefa
assefa at DMSOLUTIONS.CA
Thu Jan 20 15:45:50 EST 2005
Tracy,
- Start by doing a getcapabilities on the wms server. You will see all
the layers that are available.
- inside your wms client map, use the same name for the "wms_name"
paramater as one of the layers defined on the server and that should be it.
I just tried this wms cleint layer pointing to your server and it did
display the layer properly :
LAYER
NAME "Municipal Park"
TYPE RASTER
STATUS ON
#CONNECTION
"http://www.chirpwhistler.info/scripts/mapserv.exe?map=c:\chameleon-2.0\chirp\map\chirp.map&"
CONNECTION
"http://www.chirpwhistler.info/scripts/mapserv.exe?map=chirp_wms.map&"
CONNECTIONTYPE WMS
METADATA
"wms_title" "Park"
"wms_srs" "EPSG:42304 EPSG:42101 EPSG:4269 EPSG:4326
EPSG:42304 EPSG:26910"
"wms_name" "Municipal Park"
"wms_server_version" "1.1.1"
"wms_formatlist" "image/gif,image/png,image/jpeg,image/wbmp"
"wms_format" "image/gif"
END
END
I do not thing there is any thing wrong but just only layer names
issues. BTW avoid using spaces in layer names (eg Municipal Park, you
should use Municipal_Park). You can use a more descriptive name for the
title.
Hope this helps. If you still have issues with it, I suggest you open a
bug in mapserver and enter your problem with appropriate data set for
testing.
Best Regards,
Tracy Howlett wrote:
> Hmmm - thanks a lot for your help but I'm still getting the layer error.
>
> Can you tell me what I need to do to make my layers OGC compliant?
>
> Tracy Howlett
> Community Habitat Resources Project
> GIS Web Development Coordinator
> PO Box 1122, Whistler, BC, V0N 1B8
> Phone: 604 932 2019
> Fax: 604 932 2077
> Web: www.CHiRPwhistler.info
> Forum: www.CHiRPwhistler.info/forums/index.php
>
>
> -----Original Message-----
> From: Yewondwossen Assefa [mailto:assefa at dmsolutions.ca]
> Sent: Thursday, January 20, 2005 7:27 AM
> To: Tracy at CHiRPwhistler.info
> Cc: MAPSERVER-USERS at LISTS.UMN.EDU
> Subject: Re: [UMN_MAPSERVER-USERS] WMS error after upgrade to 4.4
>
> Not sure what might be the problem, but I have tested your wms client
> map file and spotted a couple of issues in the first layer (RMOW
> bounadary) :
>
> - "wms_name" "RMOW " : from your server file definition,
> this should be "RMOW" with no white space. Maybe mapserver should
> automatically strip white spaces but in any case you should chnage it.
>
> "wms_server_version" "1.11" : should be 1.1.1
>
> After these 2 corrections, I was able to dsiplay the map.
>
> Hope it helps.
>
> Later,
>
>
> Tracy Howlett wrote:
>
>
>>Here is my getmap request:
>>
>>
>
> http://www.chirpwhistler.info/scripts/mapserv.exe?map=chirp_wms.map&VERSION=
>
>>1.1.1&SERVICE=wms&REQUEST=GetMap
>>
>>And here is the sample of my cascading mapfile and the base mapfile
>>
>>I really appreciate your help!
>>
>>Cascade (c:\inetpub\scripts\chirp_wms.map):
>>
>>#
>># Start of map file
>>#
>># Sample map file for a chameleon app.
>>#
>>NAME CHIRP_WMS
>>STATUS ON
>>SIZE 570 360
>>SYMBOLSET "c:\chameleon-2.0\CHiRP\etc\symbols.sym"
>>EXTENT 486515 5541282 512169 5559285
>>UNITS METERS
>>SHAPEPATH "c:\chameleon-2.0\CHiRP\data\"
>>IMAGECOLOR 255 255 255
>>FONTSET "c:\chameleon-2.0\CHiRP\etc\fonts.txt"
>>
>>#
>># Start of web interface definition
>>#
>>WEB
>>#
>># On Windows systems, /tmp and /tmp/ms_tmp/ should be created at the root
>># of the drive where the .MAP file resides.
>>#
>> IMAGEPATH "/tmp/ms_tmp/"
>> IMAGEURL "/tmp/"
>> METADATA
>> "wms_title" "CHIRP_WMS"
>> "wms_onlineresource"
>>
>
> "http://www.chirpwhistler.info/scripts/mapserv.exe?map=c:\chameleon-2.0\CHiR
>
>>P\map\chirp.map&"
>> END
>>END
>>
>>PROJECTION
>> "init=epsg:26910"
>>END
>>
>>#
>># Start of layer definitions
>>#
>>
>>LAYER
>> NAME "RMOW Boundary"
>> TYPE RASTER
>> STATUS ON
>> CONNECTION
>>
>
> "http://localhost/scripts/mapserv.exe?map=c:\c:\chameleon-2.0\chirp\map\chir
>
>>p.map&"
>> CONNECTIONTYPE WMS
>> METADATA
>> "wms_title" "RMOW"
>> "wms_srs" "EPSG:42304 EPSG:42101 EPSG:4269 EPSG:4326
>>EPSG:42304 EPSG:26910"
>> "wms_name" "RMOW "
>> "wms_server_version" "1.11"
>> "wms_formatlist" "image/gif,image/png,image/jpeg,image/wbmp"
>> "wms_format" "image/gif"
>> END
>>END
>>
>>LAYER
>> NAME "Municipal Park"
>> TYPE RASTER
>> STATUS ON
>> CONNECTION
>>
>
> "http://www.chirpwhistler.info/scripts/mapserv.exe?map=c:\chameleon-2.0\chir
>
>>p\map\chirp.map&"
>> CONNECTIONTYPE WMS
>> METADATA
>> "wms_title" "Park"
>> "wms_srs" "EPSG:42304 EPSG:42101 EPSG:4269 EPSG:4326
>>EPSG:42304 EPSG:26910"
>> "wms_name" "Park"
>> "wms_server_version" "1.1.1"
>> "wms_formatlist" "image/gif,image/png,image/jpeg,image/wbmp"
>> "wms_format" "image/gif"
>> END
>>
>>LAYER
>> NAME "Buildings"
>> TYPE RASTER
>> STATUS ON
>> CONNECTION
>>
>
> "http://www.chirpwhistler.info/scripts/mapserv.exe?map=c:\chameleon-2.0\CHiR
>
>>P\map\chirp.map&"
>> CONNECTIONTYPE WMS
>> METADATA
>> "wms_title" "Buildings"
>> "wms_srs" "EPSG:26910"
>> "wms_name" "Buildings"
>> "wms_server_version" "1.1.1"
>> "wms_formatlist" "image/gif,image/png,image/jpeg,image/wbmp"
>> "wms_format" "image/gif"
>> END
>>END
>>
>>Base MapFile (c:\chameleon-2.0\chirp\map\chirp.map):
>>
>>#
>># Start of map file
>>#
>># Sample map file for a chameleon app.
>>#
>>NAME CHiRP
>>STATUS ON
>>SIZE 570 360
>>SYMBOLSET "../etc/symbols.sym"
>>EXTENT 486515 5541282 512169 5559285
>>UNITS METERS
>>SHAPEPATH "../data/"
>>IMAGECOLOR 255 255 255
>>FONTSET "../etc/fonts.txt"
>>
>>
>>#
>># Start of web interface definition
>>#
>>WEB
>> MINSCALE 1300
>> MAXSCALE 13000000000
>>#
>># On Windows systems, /tmp and /tmp/ms_tmp/ should be created at the root
>># of the drive where the .MAP file resides.
>>#
>> IMAGEPATH "/tmp/ms_tmp/"
>> IMAGEURL "/tmp/"
>># LOG "/tmp/gmap.log"
>> METADATA
>> "wms_title" "CHiRP"
>> "wms_onlineresource"
>>
>
> "http://www.CHiRPwhistler.info/scripts/mapserv.exe?map=c:\chameleon-2.0\CHiR
>
>>P\map\chirp.map&"
>> END
>>END
>>
>>#
>># Start of reference map
>>#
>>REFERENCE
>> IMAGE images/whistler_sm.png
>> EXTENT 486515 5541282 512169 5559285
>> STATUS ON
>> COLOR -1 -1 -1
>> OUTLINECOLOR 255 0 0
>> SIZE 75 50
>>END
>>
>>#
>># Start of legend
>>#
>>LEGEND
>> STATUS ON
>> KEYSIZE 18 12
>> # LABEL object
>> LABEL
>> TYPE BITMAP
>> SIZE MEDIUM
>> COLOR 0 0 89
>> END
>> TEMPLATE "legend3.html"
>>END
>>
>>
>>#
>># Start of scalebar
>>#
>>SCALEBAR
>> IMAGECOLOR 255 255 255
>> LABEL
>> COLOR 0 0 0
>> SIZE SMALL
>> END
>> SIZE 150 5
>> COLOR 255 255 255
>> BACKGROUNDCOLOR 0 0 0
>> OUTLINECOLOR 0 0 0
>> UNITS Kilometers
>> INTERVALS 5
>> STATUS ON
>>END
>>
>>
>>QUERYMAP
>> STATUS ON
>> STYLE HILITE
>> COLOR 255 0 0
>>END
>>
>>PROJECTION
>> "init=epsg:26910"
>>END
>>
>>#
>># Start of layer definitions
>>#
>>
>># MUNICIPAL PARK
>>
>>LAYER
>> NAME "Municipal Park"
>> GROUP "Recreation"
>> TYPE POLYGON
>> DUMP TRUE
>> TEMPLATE "blank.html"
>> TOLERANCE 10
>> TOLERANCEUNITS PIXELS
>> STATUS ON
>> DATA "Park"
>> PROJECTION
>> "init=epsg:26910"
>> END
>> CLASS
>> COLOR 150 231 138
>> END
>> METADATA
>> WMS_GROUP_TITLE "Recreation"
>> WMS_TITLE "Park"
>> WMS_ABSTRACT "Park"
>> WMS_SRS "EPSG:26910"
>> END
>>END
>>
>># RMOW BOUNDARY
>>
>>LAYER
>> NAME "Resort Municipality of Whistler"
>> TYPE LINE
>> STATUS ON
>> GROUP "Boundaries"
>> DATA "RMOW"
>> PROJECTION
>> "init=epsg:26910"
>> END
>> CLASS
>> COLOR 168 0 0
>> SYMBOL "Line"
>> SIZE 2
>> END
>> METADATA
>> WMS_GROUP_TITLE "Boundaries"
>> WMS_TITLE "RMOW"
>> WMS_ABSTRACT "Resort Municipality of Whistler Boundary"
>> WMS_SRS "EPSG:26910"
>> END
>>END
>>
>># BUILDINGS
>>
>>LAYER
>> NAME "Buildings"
>> GROUP "Civic Information"
>> TYPE POLYGON
>> DATA "Building"
>> MAXSCALE 15000
>> STATUS ON
>> TOLERANCE 10
>> TOLERANCEUNITS PIXELS
>> TEMPLATE "blank.html"
>> CLASSITEM "Class"
>> PROJECTION
>> "init=epsg:26910"
>> END
>> CLASS
>> NAME "Accomodation"
>> EXPRESSION "Accomodation"
>> OUTLINECOLOR 0 0 0
>> COLOR 230 0 0
>> END
>> CLASS
>> NAME "Commercial"
>> EXPRESSION "Commercial"
>> OUTLINECOLOR 0 0 0
>> COLOR 0 77 168
>> END
>> CLASS
>> NAME "Residential"
>> EXPRESSION "Residential"
>> OUTLINECOLOR 0 0 0
>> COLOR 200 133 68
>> END
>> CLASS
>> NAME "Lift Base"
>> EXPRESSION "Lift Base"
>> OUTLINECOLOR 0 0 0
>> COLOR 0 0 0
>> END
>> CLASS
>> NAME "Municipal"
>> EXPRESSION "Municipal"
>> OUTLINECOLOR 0 0 0
>> COLOR 130 155 90
>> END
>> CLASS
>> NAME "Other"
>> OUTLINECOLOR 0 0 0
>> EXPRESSION ""
>> COLOR 130 130 130
>> END
>> CLASS
>> NAME "Commercial"
>> EXPRESSION "Commercial"
>> COLOR 0 77 168
>> END
>> METADATA
>> WMS_GROUP_TITLE "CivicInformation"
>> WMS_TITLE "Buildings"
>> WMS_ABSTRACT "Buildings"
>> WMS_SRS "EPSG:26910"
>> END
>>END
>>
>>
>>
>>
>>
>>
>>
>>Tracy Howlett
>>Community Habitat Resources Project
>>GIS Web Development Coordinator
>>PO Box 1122, Whistler, BC, V0N 1B8
>>Phone: 604 932 2019
>>Fax: 604 932 2077
>>Web: www.CHiRPwhistler.info
>>Forum: www.CHiRPwhistler.info/forums/index.php
>>
>>
>>-----Original Message-----
>>From: Yewondwossen Assefa [mailto:assefa at dmsolutions.ca]
>>Sent: Wednesday, January 19, 2005 5:18 PM
>>To: Tracy Howlett
>>Cc: MAPSERVER-USERS at LISTS.UMN.EDU
>>Subject: Re: [UMN_MAPSERVER-USERS] WMS error after upgrade to 4.4
>>
>>Do you have an example of a getmap URL returing the exception and maybe
>>your map definition ?
>>
>>There has been some work done in the wms code before the 4.4 release so
>>that mapserver would be OGC compliant (so more parameter tesing and
>>exception generating has been added) and this may explain the problems
>>your are having.
>>
>>Later,
>>
>>
>>Tracy Howlett wrote:
>>
>>
>>
>>>Hello,
>>>
>>>
>>>
>>>I've recently upgraded to MapServer 4.4 after running 4.0.1 successfully
>>>for over a year. I have been using a Cascading WMS service to share
>>>some of my layers out to another MapServer user who has been accessing
>>>my data without problem.
>>>
>>>
>>>
>>>For some reason, now that MapServer 4.4 is running, the WMS layers are
>>>no longer being shared. We have run the getCapabilities for both my
>>>base mapfile and my cascaded map file service and they both come back
>>>error free but when we run a getMap we receive the following error:
>>>
>>>
>>>
>>><?xml version='1.0' encoding="ISO-8859-1" standalone="no" ?> <!DOCTYPE
>>>ServiceExceptionReport SYSTEM
>>>"http://schemas.opengeospatial.net/wms/1.1.1/exception_1_1_1.dtd">
>>>
>>><ServiceExceptionReport version="1.1.1"> <ServiceException
>>>code="LayerNotDefined">
>>>
>>>msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the
>>>LAYERS parameter.
>>>
>>></ServiceException>
>>>
>>></ServiceExceptionReport>
>>>
>>>
>>>
>>>I've read about this error in the archives but cannot find a solution
>>>for my particular file. When my colleague calls the mapfile only one of
>>>the 10 layers listed is returned.
>>>
>>>The data has not changed since I upgraded and it is all in the same
>>>projection (UTM Zone 10). Are there some naming conventions or WMS
>>>requirements that are new in 4.4 that I have not found in the
>>
>>documentation?
>>
>>
>>>
>>>Any help would be greatly appreciated as we are trying to get this thing
>>>up and running again for a presentation on Saturday.
>>>
>>>
>>>
>>>Thanks,
>>>
>>>
>>>
>>>**Tracy Howlett**
>>>
>>>Community Habitat Resources Project
>>>
>>>GIS Web Development Coordinator
>>>
>>>PO Box 1122, Whistler, BC, V0N 1B8
>>>
>>>Phone: 604 932 2019
>>>
>>>Fax: 604 932 2077
>>>
>>>Web: www.CHiRPwhistler.info <http://www.CHiRPwhistler.info>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
--
----------------------------------------------------------------
Assefa Yewondwossen
Software Analyst
Email: assefa at dmsolutions.ca
http://www.dmsolutions.ca/
Phone: (613) 565-5056 (ext 14)
Fax: (613) 565-0925
----------------------------------------------------------------
More information about the mapserver-users
mailing list