WMS GetCapabilities truncated for a CONNECTIONTYPE POSTGIS

[jmckenna]

• Problem data statement:

    DATA "geom from (SELECT id,dgsid,easting,northing,ST_SetSRID(ST_MakePoint(easting,northing),26957) as geom FROM geophys_logs) as subquery using unique id using srid=26957"

• GetCapabilities is truncated at that layer:

    ...
    <Layer queryable="1" opaque="0" cascaded="0">
        <Name>geophys-logs</Name>
        <Title>DGS - wells with Geophysical Logs</Title>
        <KeywordList>
          <Keyword>MetadataUrl=http://geodev.dgs.udel.edu/dgir/temp_metadata.htm
l</Keyword>
        </KeywordList>
        <SRS>EPSG:26957</SRS>
        <SRS>EPSG:4326</SRS>
        <SRS>EPSG:4269</SRS>
        <SRS>EPSG:4152</SRS>
        <SRS>EPSG:2776</SRS>
        <SRS>EPSG:3785</SRS>
        <SRS>EPSG:900913</SRS>

• but specifying "wms_extent" solves it:

    METADATA
       ...
       #'wms_extent' '348360.900000 4015701.800000 582411.600000 4462986.400000'
    END

[jmckenna]

Could be related to ticket:3585

[jmckenna]

More info on test env:

• Windows
• MapServer 6.0.1 (packaged in MS4W)

(good news is that this has been reported with non-MS4W binaries as well: see ticket:3977 comment:4)

[dmorissette]

Adding Paul to CC. The issue manifests itself in the WMS GetCapabilities, but I suspect the problem would really take its roots in the PostGIS code. A simple testcase (if possible) might help someone reproduce and fix the issue.

[jmckenna]

ah yes, this morning i mentioned the simple test case in a related ticket (3977). and yes creating the simple test case could be an issue...especially if my guesses are right that this is only a Windows issue. :)

[sholl]

We had this issue only on ArcSDE-Layers with self-compiled MS from (somewhat older) trunk.

I did not test the mentioned trick with adding WMS_EXTENT to the metadata to solve the problem though.

Too bad I cannot add a testcase since the data is not freely available; but I am highly interested in having a solution for this issue.

Stephan