Projection issues on WFS-Server

[Jaakko Kahkonen]

Similar results here with WMS GetCababilities BoundingBox, using
Mapserver 4.8.0 and PostGIS 1.1.0. GetMap query gives good map images
with postgis layer and other layers, so result as maps are ok.

Part of WMS GetCababilities results:
...

<Title>WMS/WFS pullautin</Title>
    <SRS>EPSG:2393</SRS>
    <LatLonBoundingBox minx="15.5148" miny="59.4772" maxx="33.1781"
maxy="70.0969" />
    <BoundingBox SRS="EPSG:2393"
                minx="3.05784e+06" miny="6.62201e+06" maxx="3.7357e+06"
maxy="7.78e+06" />
    <Layer queryable="0" opaque="0" cascaded="1">
        <Name>mk2m</Name>
        <Title>mk2m aineisto</Title>
        <SRS>EPSG:2393</SRS>
        <ScaleHint min="498.903" max="1995.61" />
    </Layer>
...
    <Layer queryable="0" opaque="0" cascaded="0">
        <Name>elementti</Name>
        <Title> </Title>
        <SRS>EPSG:4258</SRS>
        <LatLonBoundingBox minx="-2.5e+07" miny="-2.5e+07"
maxx="2.5e+07" maxy="2.5e+07" />
        <BoundingBox SRS="EPSG:4258"
                    minx="-2.5e+07" miny="-2.5e+07" maxx="2.5e+07"
maxy="2.5e+07" />
        <ScaleHint min="0.248953" max="4.98903" />
    </Layer>


And part of MapServer mapfile:

MAP
  IMAGETYPE      PNG24
  EXTENT 3057842.59 6622010.94 3735699.26 7780000
  SIZE           600 600
  NAME  NLSDIGIROAD

  PROJECTION
    "init=epsg:2393"
  END

  ...

  WEB
  ...
    METADATA
        "ows_title" "WMS/WFS pullautin"
        "ows_src" "EPSG:2393"
    END
  END
...
  LAYER #
    NAME         mk2m
    TYPE         RASTER
    MINSCALE     1000000
    MAXSCALE     4000000
    STATUS       ON
    CONNECTIONTYPE WMS
    CONNECTION "https://....?"

    METADATA
      "wms_title" "mk2m"
      "wms_srs" "EPSG:2393"
      "wms_name" "mk2m"
      "wms_server_version" "1.1.1"
      "wms_format" "image/png"
      "wms_connectiontimeout" "60"
    END

    PROJECTION
      "init=epsg:2393"
    END
  END

...

  LAYER
    CONNECTIONTYPE postgis
    NAME "elementti"
    CONNECTION "user=xxxx dbname=xxxx host=xxxx port=xxxx"
    DATA "the_geom from elementti"
    STATUS ON
    TYPE LINE
    PROJECTION
      "init=epsg:4258"
    END

    METADATA
      "ows_title" "...."
      "ows_srs" "EPSG:4258"
      "ows_name" "Digiroad elementti"
      "ows_server_version" "1.1.1"
      "ows_format" "image/png"
      "ows_connectiontimeout" "60"
    END
  END



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,