Projection issues on WFS-Server

[Stephan Holl]

Hello Assefa,

On Wed, 08 Mar 2006 09:30:03 -0500 Yewondwossen Assefa
<assefa at dmsolutions.ca> wrote:

> Stephan,
> 
>   From what I have seen, this happens when the layer does not have a 
> projection object (with possibly an espg code) that reflects the 
> projection of your layer.
>   This can easily be reproduced  if I set a projection object at the
> map level (or metadata wfs_srs = "EPSG:4326") and I use a layer which
> is not in lat/long and does not have a projection object.
> In that case the default fallback is to assume that the layer is the 
> same projection as the map. If the layer has a valid projection,
> there will be a reprojection of the extents.
> 
>   Stephan, is this the case for you ?

No, it is not the case. I have a projection-block set on maplevel
(EPSG:4326), and the layer in question has the same projection set.

AS I pointed out to Frank, the beahviour is correct exporting the layer
into a shapefile. So I assume it is a PostGIS-WFS-issue. That said, I
do not know what you need to reproduce this. Does it make sense to
bundle up a small dataset with the stripped-down-wfs-mapfile, a
PostGIS-dump and the shapefile?

Thank you for your help.

Best
	Stephan

> 
> Frank Warmerdam wrote:
> > Stephan Holl wrote:
> > 
> >> Hello Frank,
> >>
> >> On Tue, 7 Mar 2006 15:12:20 -0500 Frank Warmerdam
> >> <warmerdam at POBOX.COM> wrote:
> >>
> >>> Stephan Holl wrote:
> >>>
> >>>> GetCapabilities
> >>>> ...
> >>>> <SRS>EPSG:4326</SRS>
> >>>> <LatLongBoundingBox minx="-2.5e+07" miny="-2.5e+07"
> >>>> maxx="2.5e+07" maxy="2.5e+07"/>
> >>>> ...
> >>>>
> >>>> This should be from my understanding
> >>>> <LatLongBoundingBox minx="-180" miny="-90" maxx="180" maxy="90"/>
> > 
> > 
> > Stephan,
> > 
> > Looking more closely at your bounding box, it doesn't really look
> > like it hasn't been reprojected.  It looks more like it was
> > unitialized or defaulted somehow since all the values are the same.
> > 
> > I am also starting to wonder if this is an issue specific to
> > PostGIS.
> > 
> > I'm no WFS nor PostGIS-in-MapServer guru.  My suggestion is you try
> > and reproduce the problem from shapefiles.  If you can reproduce it
> > from shapefiles, then you should submit a bug report with a dataset,
> > map and the exact WFS query to reproduce the problem.  You should
> > test the WFS query against mapserv at the commandline to maximally
> > ensure it will be easy for the bug fixer to reproduce.
> > 
> > If you can't reproduce the problem with a shapefile, then I suspect
> > the issue is somehow related to WFS interacting with the PostGIS
> > driver. You likely still ought to file a bug, but it will likely be
> > hard to bundle things up to make it easy for a bug fixer to
> > reproduce.
> > 
> > Best regards,
> 
> 



-- 
GDF Hannover - Solutions for spatial data analysis and remote sensing
Hannover Office      -     Mengendamm 16d      -     D-30177 Hannover
Internet: www.gdf-hannover.de      -      Email: holl at gdf-hannover.de
Phone : ++49-(0)511.39088507       -        Fax: ++49-(0)511.39088508