[mapserver-users] GetFeatureINFO errors in Mapserver notoccurringin Geoserver.

Michelle Douvil mrdouville at shaw.ca
Fri Apr 24 12:34:54 EDT 2009


Thanks again for the reply Steve, 

Where are using Mapserver 5.2.

I have tried playing around with the "PROCESSING  OBJECTID=" parameter to no
avail for the SVW described below. However, for about 30% of other SVWs,  if
I apply the primary key of the input spatial layer to this parameter it does
fix the problem. 

Some Spatial views work fine, (and are complex SVWs with several join
statements and where clauses) and others do not (no join statements or where
clauses as the one below).. We can't seem to narrow down the cause as of
yet.

In one instance of a spatial view, we changed the underlying roles of the
inputs to the spatial views (so the user could see the SVW and the input
spatial layers and attribute tables) And this fixed the problem. 
But for other SVWs this did not correct the problem. Perhaps the primary key
and/or OBJECTID of the input spatial layers need to be in the SVWs for it to
work correctly, but in some instances this has not worked for us either?

Below is the MAP and LAYER definition in the mapfile...

MAP
	EXTENT 79932.9 225000 2020067.1 1875000
	SIZE 100 100
	UNITS meters
	SYMBOLSET "air-climate-symbols.sym"
	FONTSET "fonts.lst"
	DEBUG 5
	 CONFIG  "MS_ERRORFILE" "e:/sw_nt/mapserver/log/air-climate.log"

	NAME "BCGov - Air Climate WMS"
	
	WEB
		METADATA
			wms_title "BCGov - Air Climate WMS"
			wfs_title "BCGov - Air Climate WFS"
			wms_onlineresource "http://server/mapserver/air-climate?service=WMS"
			wfs_onlineresource "http://server/mapserver/air-climate?service=WFS"
			wms_srs "EPSG:3785 EPSG:102190 EPSG:26907 EPSG:26707 EPSG:32607 EPSG:3005
EPSG:42102 EPSG:4269 EPSG:4326 EPSG:26708 EPSG:26709 EPSG:26710 EPSG:26711
EPSG:26712 EPSG:26908 EPSG:26909 EPSG:26910 EPSG:26911 EPSG:26912 EPSG:32608
EPSG:32609 EPSG:32610 EPSG:32611 EPSG:32612 EPSG:54004"
			wfs_srs "EPSG:3785 EPSG:102190 EPSG:26907 EPSG:26707 EPSG:32607 EPSG:3005
EPSG:42102 EPSG:4269 EPSG:4326 EPSG:26708 EPSG:26709 EPSG:26710 EPSG:26711
EPSG:26712 EPSG:26908 EPSG:26909 EPSG:26910 EPSG:26911 EPSG:26912 EPSG:32608
EPSG:32609 EPSG:32610 EPSG:32611 EPSG:32612 EPSG:54004"
			wfs_maxfeatures "0"
			wms_abstract "Data relating to patterns of wind, temperature,
precipitation, etc., over a period of time, for a specified area."
			wms_keywordlist "British
Columbia,BC,Canada,wind,temperature,precipitation,climate,air"
			wms_accessconstraints "This Web Map Service cannot be cascaded through
another Web Map Service without the express written permission of the
Province of British Columbia"
			wms_fees "None"
		END
	END
	PROJECTION
		"init=EPSG:3005"
	END
	LEGEND
		KEYSIZE 15 15
		LABEL
			COLOR 0 0 0
			FONT "arial"
			TYPE truetype
			SIZE 8
		END
	END
LAYER
		NAME "AEI_AIR_QUALITY_AOI_O"
		CONNECTIONTYPE sde
		CONNECTION "server,port:5152,sde,username,password"
		DATA "WHSE_ENVIRONMENTAL_MONITORING.AEI_AIR_QUALITY_AOI_SVW,GEOMETRY"
		TYPE polygon
		MAXSCALEDENOM 12000000
		LABELITEM "AOI_NAME"
		LABELMAXSCALEDENOM 2000000
		STATUS ON
		CLASS
			STYLE
				OUTLINECOLOR 213 13 39
				WIDTH 2
			END
			LABEL
				TYPE truetype
				ANGLE auto
				POSITION auto
				FONT "arial-bold"
				MINDISTANCE 10000
				COLOR 255 255 0
				OUTLINECOLOR 0 0 0
				SIZE 14
			END
		END
		METADATA
			wms_title "Air Quality Areas of Interest - Outlined"
			wms_metadataurl_format "html"
			wms_metadataurl_href
"http://aardvark.gov.bc.ca/apps/metastar/metadataDetail.do?recordUID=42631&recordSet=ISO19115"
			wms_metadataurl_type "TC211"
			wfs_title "Air Quality Areas of Interest - Outlined"
			gml_geometries "geom"
			gml_geom_type "polygon"
      			gml_include_items "all"
      			gml_exclude_items "GEOMETRY,OBJECTID"
			ows_include_items "all"
			ows_exclude_items "GEOMETRY,OBJECTID"
		END #end metadata
		PROCESSING "CLOSE_CONNECTION=DEFER"
		PROCESSING "OBJECTID=OBJECTID"
		DUMP TRUE
		TEMPLATE "foo.html"
	END



Steve Lime wrote:
> 
> Could be a config error in the mapfile. What version of MapServer are you
> using? What does the
> layer def look like?
> 
> Geoserver and MapServer are completely different code bases so they
> definitely approach SDE 
> differently.
> 
> Steve
> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/GetFeatureINFO-errors-in-Mapserver-not-occurring-in-Geoserver.-tp2686390p2693553.html
Sent from the Mapserver - User mailing list archive at Nabble.com.



More information about the mapserver-users mailing list