[mapserver-dev] WFS 1.1.0 Server and lat/long axis order

Kralidis,Tom [Ontario] Tom.Kralidis at ec.gc.ca
Wed Feb 25 14:20:59 EST 2009


It doesn't pass the SRS.  Here's what the WFS connector does:

"GET /cgi-bin/mapserv/mapserv?SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&MAP=/tmp/pa/config_en.map&TYPENAME=pa HTTP/1.1"

..Tom


> -----Original Message-----
> From: pramsey at cleverelephant.ca 
> [mailto:pramsey at cleverelephant.ca] On Behalf Of Paul Ramsey
> Sent: Wednesday, 25 February 2009 11:55
> To: Kralidis,Tom [Ontario]
> Cc: mapserver-dev
> Subject: Re: [mapserver-dev] WFS 1.1.0 Server and lat/long axis order
> 
> When the interop extension makes the data request, what form 
> does it use for the SRS?  "EPSG:XXXX" or "urn://blahblah"?
> 
> P
> 
> On Fri, Feb 20, 2009 at 1:00 PM, Kralidis,Tom [Ontario] 
> <Tom.Kralidis at ec.gc.ca> wrote:
> >
> > Well, apparently (I don't have ArcMap) the interoperability 
> extension 
> > ArcMap is using does _not_ allow you specify the version 
> for WFS, so 
> > it grabs 1.1.0 (latest).  For WMS it allows you to specify version.
> >
> > We found a workaround by tacking on "version=1.0.0" to the 
> base URL, 
> > but there's a greater issue at hand :)
> >
> > ..Tom
> >
> >
> >> -----Original Message-----
> >> From: mapserver-dev-bounces at lists.osgeo.org
> >> [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Paul 
> >> Ramsey
> >> Sent: Friday, 20 February 2009 15:58
> >> To: Kralidis,Tom [Ontario]
> >> Cc: mapserver-dev
> >> Subject: Re: [mapserver-dev] WFS 1.1.0 Server and lat/long 
> axis order
> >>
> >> If you do the request via WFS 1.0 does it come out correct?
> >> This is exactly the tower-of-babel I predicted when I starting 
> >> hammering on axis ordering in WFS back in 2005.
> >>
> >> P.
> >>
> >> On Fri, Feb 20, 2009 at 12:36 PM, Kralidis,Tom [Ontario] 
> >> <Tom.Kralidis at ec.gc.ca> wrote:
> >> >
> >> > We recently stood up 5.2.1 to offer up corporate WMS, WFS,
> >> WCS and SOS
> >> > interfaces.
> >> >
> >> > We have MAP.PROJECTION set to init=epsg:4326.
> >> >
> >> > We don't have MAP.WEB.METADATA.wfs_srs set.
> >> >
> >> > We have MAP.LAYER.METADATA.PROJECTION set (to each layer's native
> >> > projection)
> >> >
> >> > WFS 1.1.0 shows EPSG:4326 as the DefaultSRS for the 
> FeatureType in 
> >> > question (probably fetching from MAP.PROJECTION?).
> >> >
> >> > A colleague has noticed that connecting to our endpoint 
> using WFS 
> >> > 1.1.0, through ESRI ArcMap.  ArcMap renders the features flipped.
> >> >
> >> > Searching a bit more, we found:
> >> >
> >> >
> >> 
> http://n2.nabble.com/WFS-lat-lon-coordinates-switched-in-ArcGIS-td205
> >> 5
> >> > 07
> >> > 9.html
> >> >
> >> > When I try in QGIS, the WFS renders fine.
> >> >
> >> > Anyone have suggestions?  Can WFS offer up > 1 SRS?  
> This would be 
> >> > _non-trivial_ change to the codebase.
> >> >
> >> > ..Tom
> >> > _______________________________________________
> >> > mapserver-dev mailing list
> >> > mapserver-dev at lists.osgeo.org
> >> > http://lists.osgeo.org/mailman/listinfo/mapserver-dev
> >> >
> >> _______________________________________________
> >> mapserver-dev mailing list
> >> mapserver-dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
> >>
> > _______________________________________________
> > mapserver-dev mailing list
> > mapserver-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/mapserver-dev
> >
> 


More information about the mapserver-dev mailing list