[Geoserver-users] srsName in geometry

hi all,

Geoserver replies to wfs request a gml polygon with no srsName attribute, is it ok ?
How can i force it to do so ?

Thanks.

            <gml:Polygon>
              <gml:exterior>
                <gml:LinearRing>
                  <gml:posList>50.55 0.59 50.54 0.57 50.49 0.57 50.49 0.62 50.55 0.62 50.55 0.6 50.55 0.59</gml:posList>
                </gml:LinearRing>
              </gml:exterior>
            </gml:Polygon>

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Hi Sebastien,

The reason that this is occurring is because the underlying datastore is
not setting the crs information properly. What backend are you using?

-Justin

Sebastien Geindre wrote:

hi all,

Geoserver replies to wfs request a gml polygon with no srsName
attribute, is it ok ?
How can i force it to do so ?

Thanks.

            <gml:Polygon>
              <gml:exterior>
                <gml:LinearRing>
                  <gml:posList>50.55 0.59 50.54 0.57 50.49 0.57 50.49
0.62 50.55 0.62 50.55 0.6 50.55 0.59</gml:posList>
                </gml:LinearRing>
              </gml:exterior>
            </gml:Polygon>

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira a écrit :

Hi Sebastien,

The reason that this is occurring is because the underlying datastore is
not setting the crs information properly. What backend are you using?
  

i use postgis.
srsName is set in gml:boundedBy but not in gml:Polygon...

   <wims:cb gml:id="cb.fid-52dc1f15_116ce12dcef_-6a7a">
      <gml:boundedBy>
        <gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326">
          <gml:lowerCorner>48.124 1.50617</gml:lowerCorner>
          <gml:upperCorner>49.3036 2.38818</gml:upperCorner>
        </gml:Envelope>
      </gml:boundedBy>
      <wims:type>cb-top</wims:type>
      <wims:geometry>
        <gml:Polygon>
          <gml:exterior>
            <gml:LinearRing>
              <gml:posList>48.124 2.1561 48.1742 2.11567 48.1735 1.98735 48.2744 1.90599 48.529 1.9166 48.5799 1.8756 48.5795 2.17525 48.5316 2.34773 48.4808 2.38818 48.2265 2.37499 48.1756 2.3296 48.1753 2.28681 48.1245 2.24157 48.124 2.1561</gml:posList>
            </gml:LinearRing>
          </gml:exterior>
        </gml:Polygon>
      </wims:geometry>
    </wims:cb>

-Justin

Sebastien Geindre wrote:
  

hi all,

Geoserver replies to wfs request a gml polygon with no srsName attribute, is it ok ?
How can i force it to do so ?

Thanks.

            <gml:Polygon>
              <gml:exterior>
                <gml:LinearRing>
                  <gml:posList>50.55 0.59 50.54 0.57 50.49 0.57 50.49 0.62 50.55 0.62 50.55 0.6 50.55 0.59</gml:posList>
                </gml:LinearRing>
              </gml:exterior>
            </gml:Polygon>

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Interesting... postgis is one of the datastores that should be setting
this properly. Which version of geoServer are you using?

Sébastien Geindre wrote:

Justin Deoliveira a écrit :

Hi Sebastien,

The reason that this is occurring is because the underlying datastore is
not setting the crs information properly. What backend are you using?
  

i use postgis.
srsName is set in gml:boundedBy but not in gml:Polygon...

   <wims:cb gml:id="cb.fid-52dc1f15_116ce12dcef_-6a7a">
      <gml:boundedBy>
        <gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326">
          <gml:lowerCorner>48.124 1.50617</gml:lowerCorner>
          <gml:upperCorner>49.3036 2.38818</gml:upperCorner>
        </gml:Envelope>
      </gml:boundedBy>
      <wims:type>cb-top</wims:type>
      <wims:geometry>
        <gml:Polygon>
          <gml:exterior>
            <gml:LinearRing>
              <gml:posList>48.124 2.1561 48.1742 2.11567 48.1735 1.98735
48.2744 1.90599 48.529 1.9166 48.5799 1.8756 48.5795 2.17525 48.5316
2.34773 48.4808 2.38818 48.2265 2.37499 48.1756 2.3296 48.1753 2.28681
48.1245 2.24157 48.124 2.1561</gml:posList>
            </gml:LinearRing>
          </gml:exterior>
        </gml:Polygon>
      </wims:geometry>
    </wims:cb>

-Justin

Sebastien Geindre wrote:
  

hi all,

Geoserver replies to wfs request a gml polygon with no srsName
attribute, is it ok ?
How can i force it to do so ?

Thanks.

            <gml:Polygon>
              <gml:exterior>
                <gml:LinearRing>
                  <gml:posList>50.55 0.59 50.54 0.57 50.49 0.57 50.49
0.62 50.55 0.62 50.55 0.6 50.55 0.59</gml:posList>
                </gml:LinearRing>
              </gml:exterior>
            </gml:Polygon>

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira a écrit :

Interesting... postgis is one of the datastores that should be setting
this properly. Which version of geoServer are you using?
  

The 1.6 branch !!

Sébastien Geindre wrote:
  

Justin Deoliveira a écrit :
    

Hi Sebastien,

The reason that this is occurring is because the underlying datastore is
not setting the crs information properly. What backend are you using?
  

i use postgis.
srsName is set in gml:boundedBy but not in gml:Polygon...

   <wims:cb gml:id="cb.fid-52dc1f15_116ce12dcef_-6a7a">
      <gml:boundedBy>
        <gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326">
          <gml:lowerCorner>48.124 1.50617</gml:lowerCorner>
          <gml:upperCorner>49.3036 2.38818</gml:upperCorner>
        </gml:Envelope>
      </gml:boundedBy>
      <wims:type>cb-top</wims:type>
      <wims:geometry>
        <gml:Polygon>
          <gml:exterior>
            <gml:LinearRing>
              <gml:posList>48.124 2.1561 48.1742 2.11567 48.1735 1.98735 48.2744 1.90599 48.529 1.9166 48.5799 1.8756 48.5795 2.17525 48.5316 2.34773 48.4808 2.38818 48.2265 2.37499 48.1756 2.3296 48.1753 2.28681 48.1245 2.24157 48.124 2.1561</gml:posList>
            </gml:LinearRing>
          </gml:exterior>
        </gml:Polygon>
      </wims:geometry>
    </wims:cb>

-Justin

Sebastien Geindre wrote:
  

hi all,

Geoserver replies to wfs request a gml polygon with no srsName attribute, is it ok ?
How can i force it to do so ?

Thanks.

            <gml:Polygon>
              <gml:exterior>
                <gml:LinearRing>
                  <gml:posList>50.55 0.59 50.54 0.57 50.49 0.57 50.49 0.62 50.55 0.62 50.55 0.6 50.55 0.59</gml:posList>
                </gml:LinearRing>
              </gml:exterior>
            </gml:Polygon>

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Sébastien Geindre ha scritto:

Justin Deoliveira a écrit :

Interesting... postgis is one of the datastores that should be setting
this properly. Which version of geoServer are you using?
  

The 1.6 branch !!

Another small question for you. Is the srs set in the geometry_columns
table (and do you have the record for that table?).
What's the srs handling you chose in the feature type configuration
panel?
Cheers
Andrea

Andrea Aime a écrit :

Sébastien Geindre ha scritto:

Justin Deoliveira a écrit :

Interesting... postgis is one of the datastores that should be setting
this properly. Which version of geoServer are you using?
  

The 1.6 branch !!

Another small question for you. Is the srs set in the geometry_columns
table (and do you have the record for that table?).

how can i check that ??
i added geometry column with following instruction :
select AddGeometryColumn('',nameOfTable, nameOfColumn, 4326, 'POLYGON' 2);
4326 should be srid.

with pgadmin, i could only check that there is a integrity constraint on that geometry column : ADD CONSTRAINT enforce_srid_geometry CHECK (srid(geometry) = 4326);

another question, what differences between running GeoServer as a Java program without a wrapper such as Tomcat and running Geoserver in Tomcat container for example?

What's the srs handling you chose in the feature type configuration
panel?

Système de référence de coordonnées: 4326
      WKT SRS: GEOGCS["WGS 84", DATUM["World Geodetic System 1984", SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]], UNIT["degree", 0.017453292519943295], AXIS["Geodetic longitude", EAST], AXIS["Geodetic latitude", NORTH], AUTHORITY["EPSG","4326"]]
WKT CRS natif: GEOGCS["WGS 84", DATUM["World Geodetic System 1984", SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]], UNIT["degree", 0.017453292519943295], AXIS["Geodetic longitude", EAST], AXIS["Geodetic latitude", NORTH], AUTHORITY["EPSG","4326"]]

Thanks for your help and meilleurs voeux pour la nouvelle année 2008 !!

Cheers
Andrea

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Sébastien Geindre ha scritto:

Andrea Aime a écrit :

Sébastien Geindre ha scritto:

Justin Deoliveira a écrit :

Interesting... postgis is one of the datastores that should be setting
this properly. Which version of geoServer are you using?
  

The 1.6 branch !!

Another small question for you. Is the srs set in the geometry_columns
table (and do you have the record for that table?).

how can i check that ??
i added geometry column with following instruction :
select AddGeometryColumn('',nameOfTable, nameOfColumn, 4326, 'POLYGON' 2);
4326 should be srid.

with pgadmin, i could only check that there is a integrity constraint on that geometry column : ADD CONSTRAINT enforce_srid_geometry CHECK (srid(geometry) = 4326);

another question, what differences between running GeoServer as a Java program without a wrapper such as Tomcat and running Geoserver in Tomcat container for example?

Well, simply put, GeoServer does not run without a "wrapper", it's designed as a web application and it needs a web container to run.
If you start GeoServer form the Start utility in web module, a Jetty
instance is created on the fly and instructed to run GeoServer.

About your data, I think it's possible you found a glitch in our
encoding procedures because of the "odd" geometry type. I see it's
a plain polygon, and it's not something you can get by importing shapefiles into a postgis datastore (that would result in a multipolygon). It's just a guess, but it may be that we never tried
with postgis straight polygons.

I just tried the following:
http://atlas.openplans.org:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=topp:poly_landmarks&maxFeatures=1
the poly_landmarks there is a huge postgis table with multipolygons,
and the sraName appears as expected (but, as I said, the geom
type is a Multipolygon).

Cheers
Andrea

Well, simply put, GeoServer does not run without a "wrapper", it's designed as a web application and it needs a web container to run.
If you start GeoServer form the Start utility in web module, a Jetty
instance is created on the fly and instructed to run GeoServer.

i developp and test in jetty environment and it is ok!!
but for more production test , i think tomcat is a better container than jetty... no ?

About your data, I think it's possible you found a glitch in our
encoding procedures because of the "odd" geometry type. I see it's
a plain polygon, and it's not something you can get by importing shapefiles into a postgis datastore (that would result in a multipolygon). It's just a guess, but it may be that we never tried
with postgis straight polygons.

ok, so it is because it is a 'simple' polygon ?
is it a bug ? do i need to fill a jira issue ?

Cheers
Andrea

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Sébastien Geindre ha scritto:

Well, simply put, GeoServer does not run without a "wrapper", it's designed as a web application and it needs a web container to run.
If you start GeoServer form the Start utility in web module, a Jetty
instance is created on the fly and instructed to run GeoServer.

i developp and test in jetty environment and it is ok!!
but for more production test , i think tomcat is a better container than jetty... no ?

Yes and no... I performance wise they seem to be the same, but Tomcat
has better admin facilities and it's probably more tested. We do deploy
in Tomcat for our demo servers.

About your data, I think it's possible you found a glitch in our
encoding procedures because of the "odd" geometry type. I see it's
a plain polygon, and it's not something you can get by importing shapefiles into a postgis datastore (that would result in a multipolygon). It's just a guess, but it may be that we never tried
with postgis straight polygons.

ok, so it is because it is a 'simple' polygon ?
is it a bug ? do i need to fill a jira issue ?

Hmm... I just tried with a data source having only polygons and
it worked. Any chance you can provide us with a dump or your database?
If so, open a jira issue and attach the dump

Cheers
Andrea

Hmm... I just tried with a data source having only polygons and
it worked. Any chance you can provide us with a dump or your database?
If so, open a jira issue and attach the dump

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?

Cheers
Andrea

!DSPAM:4007,478650cd109972090977483!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira a écrit :

Hmm... I just tried with a data source having only polygons and
it worked. Any chance you can provide us with a dump or your database?
If so, open a jira issue and attach the dump

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
  

i tried to make a wfs 1.0.0 request but it did not work.
I have just updated geotools and geoserver (back from holidays...)

any changes in geotools not compatible with geoserver 1.6 ?
or my wfs request is not 1.0 ? it should be that...

so difficult to say at this time if it works with wfs1.0 request...

10 janv. 17:35:34 WARN [org.geoserver.ows] -
java.lang.RuntimeException: Parsing failed for LinearRing: java.lang.RuntimeException: Could not find coordinates to build linestring

        at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:142)
        at org.geotools.xml.impl.BindingWalker$BindingExecutionChain.execute(BindingWalker.java:197)
        at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:163)
        at org.geotools.xml.impl.ElementHandlerImpl.endElement(ElementHandlerImpl.java:222)
        at org.geotools.xml.impl.ParserHandler.endElement(ParserHandler.java:496)
        at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.geotools.xml.Parser.parse(Parser.java:185)
        at org.geotools.xml.Parser.parse(Parser.java:164)
        at org.geoserver.wfs.xml.v1_0_0.WfsXmlReader.read(WfsXmlReader.java:60)
        at org.geoserver.ows.Dispatcher.parseRequestXML(Dispatcher.java:1058)
        at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:375)
        at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:185)
        at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
        at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Can you include the exact request. There are changes from gml2 to gml3
so i do not suspect geometries supplied in a wfs 1.1 to work with a 1.0
request. That is my guess as to what is happening here.

-Justin

Sébastien Geindre wrote:

Justin Deoliveira a écrit :

Hmm... I just tried with a data source having only polygons and
it worked. Any chance you can provide us with a dump or your database?
If so, open a jira issue and attach the dump

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the
transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
  

i tried to make a wfs 1.0.0 request but it did not work.
I have just updated geotools and geoserver (back from holidays...)

any changes in geotools not compatible with geoserver 1.6 ?
or my wfs request is not 1.0 ? it should be that...

so difficult to say at this time if it works with wfs1.0 request...

10 janv. 17:35:34 WARN [org.geoserver.ows] -
java.lang.RuntimeException: Parsing failed for LinearRing:
java.lang.RuntimeException: Could not find coordinates to build linestring

       at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:142)
       at
org.geotools.xml.impl.BindingWalker$BindingExecutionChain.execute(BindingWalker.java:197)

       at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:163)
       at
org.geotools.xml.impl.ElementHandlerImpl.endElement(ElementHandlerImpl.java:222)

       at
org.geotools.xml.impl.ParserHandler.endElement(ParserHandler.java:496)
       at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
       at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
       at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
       at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
       at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
       at org.geotools.xml.Parser.parse(Parser.java:185)
       at org.geotools.xml.Parser.parse(Parser.java:164)
       at
org.geoserver.wfs.xml.v1_0_0.WfsXmlReader.read(WfsXmlReader.java:60)
       at
org.geoserver.ows.Dispatcher.parseRequestXML(Dispatcher.java:1058)
       at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:375)
       at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:185)
       at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)

       at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira a écrit :

Can you include the exact request. There are changes from gml2 to gml3
so i do not suspect geometries supplied in a wfs 1.1 to work with a 1.0
request. That is my guess as to what is happening here.

-Justin
  

here is the request :
<?xml version="1.0" encoding="UTF-8"?>
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:wims="http://www.flysafe-eu.org/wims&quot; xmlns:gml="http://www.opengis.net/gml&quot; xmlns:ogc="http://www.opengis.net/ogc&quot; xmlns:xlink="http://www.w3.org/1999/xlink&quot; service="WFS" version="1.0.0" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd&quot;&gt;
  <wfs:Query typeName="wims:cat">
    <ogc:Filter>
      <ogc:And>
        <ogc:And>
          <ogc:PropertyIsEqualTo>
            <ogc:PropertyName>real_time</ogc:PropertyName>
            <ogc:Literal>true</ogc:Literal>
          </ogc:PropertyIsEqualTo>
          <ogc:PropertyIsEqualTo>
            <ogc:PropertyName>type</ogc:PropertyName>
            <ogc:Literal>cat</ogc:Literal>
          </ogc:PropertyIsEqualTo>
        </ogc:And>
        <ogc:And>
          <ogc:And>
            <ogc:Or>
              <ogc:And>
                <ogc:PropertyIsLessThanOrEqualTo>
                  <ogc:PropertyName>bottom</ogc:PropertyName>
                  <ogc:Literal>0</ogc:Literal>
                </ogc:PropertyIsLessThanOrEqualTo>
                <ogc:PropertyIsGreaterThanOrEqualTo>
                  <ogc:PropertyName>top</ogc:PropertyName>
                  <ogc:Literal>10000</ogc:Literal>
                </ogc:PropertyIsGreaterThanOrEqualTo>
              </ogc:And>
              <ogc:Or>
                <ogc:PropertyIsBetween>
                  <ogc:PropertyName>bottom</ogc:PropertyName>
                  <ogc:LowerBoundary>
                    <ogc:Literal>0</ogc:Literal>
                  </ogc:LowerBoundary>
                  <ogc:UpperBoundary>
                    <ogc:Literal>10000</ogc:Literal>
                  </ogc:UpperBoundary>
                </ogc:PropertyIsBetween>
                <ogc:PropertyIsBetween>
                  <ogc:PropertyName>top</ogc:PropertyName>
                  <ogc:LowerBoundary>
                    <ogc:Literal>0</ogc:Literal>
                  </ogc:LowerBoundary>
                  <ogc:UpperBoundary>
                    <ogc:Literal>10000</ogc:Literal>
                  </ogc:UpperBoundary>
                </ogc:PropertyIsBetween>
              </ogc:Or>
            </ogc:Or>
            <ogc:Or>
              <ogc:And>
                <ogc:PropertyIsLessThanOrEqualTo>
                  <ogc:PropertyName>validity_start_time</ogc:PropertyName>
                  <ogc:Literal>2007-05-13T10:00:00.000Z</ogc:Literal>
                </ogc:PropertyIsLessThanOrEqualTo>
                <ogc:PropertyIsGreaterThanOrEqualTo>
                  <ogc:PropertyName>validity_end_time</ogc:PropertyName>
                  <ogc:Literal>2007-05-13T11:00:00.000Z</ogc:Literal>
                </ogc:PropertyIsGreaterThanOrEqualTo>
              </ogc:And>
              <ogc:Or>
                <ogc:PropertyIsBetween>
                  <ogc:PropertyName>validity_start_time</ogc:PropertyName>
                  <ogc:LowerBoundary>
                    <ogc:Literal>2007-05-13T10:00:00.000Z</ogc:Literal>
                  </ogc:LowerBoundary>
                  <ogc:UpperBoundary>
                    <ogc:Literal>2007-05-13T11:00:00.000Z</ogc:Literal>
                  </ogc:UpperBoundary>
                </ogc:PropertyIsBetween>
                <ogc:PropertyIsBetween>
                  <ogc:PropertyName>validity_end_time</ogc:PropertyName>
                  <ogc:LowerBoundary>
                    <ogc:Literal>2007-05-13T10:00:00.000Z</ogc:Literal>
                  </ogc:LowerBoundary>
                  <ogc:UpperBoundary>
                    <ogc:Literal>2007-05-13T11:00:00.000Z</ogc:Literal>
                  </ogc:UpperBoundary>
                </ogc:PropertyIsBetween>
              </ogc:Or>
            </ogc:Or>
          </ogc:And>
          <!-- Scale : regional-->
          <ogc:And>
            <ogc:PropertyIsEqualTo>
              <ogc:PropertyName>scale</ogc:PropertyName>
              <ogc:Literal>regional</ogc:Literal>
            </ogc:PropertyIsEqualTo>
            <ogc:Intersects>
              <ogc:PropertyName>geometry</ogc:PropertyName>
              <gml:Polygon>
                <gml:exterior>
                  <gml:LinearRing>
                    <gml:posList>39.1 -10.67 43.71 -6.1 41.08 -3.46 36.24 -7.94 39.1 -10.67</gml:posList>
                  </gml:LinearRing>
                </gml:exterior>
              </gml:Polygon>
            </ogc:Intersects>
          </ogc:And>
        </ogc:And>
      </ogc:And>
    </ogc:Filter>
  </wfs:Query>
</wfs:GetFeature>

Sébastien Geindre wrote:
  

Justin Deoliveira a écrit :
    

Hmm... I just tried with a data source having only polygons and
it worked. Any chance you can provide us with a dump or your database?
If so, open a jira issue and attach the dump

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the
transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
  

i tried to make a wfs 1.0.0 request but it did not work.
I have just updated geotools and geoserver (back from holidays...)

any changes in geotools not compatible with geoserver 1.6 ?
or my wfs request is not 1.0 ? it should be that...

so difficult to say at this time if it works with wfs1.0 request...

10 janv. 17:35:34 WARN [org.geoserver.ows] -
java.lang.RuntimeException: Parsing failed for LinearRing:
java.lang.RuntimeException: Could not find coordinates to build linestring

       at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:142)
       at
org.geotools.xml.impl.BindingWalker$BindingExecutionChain.execute(BindingWalker.java:197)

       at org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:163)
       at
org.geotools.xml.impl.ElementHandlerImpl.endElement(ElementHandlerImpl.java:222)

       at
org.geotools.xml.impl.ParserHandler.endElement(ParserHandler.java:496)
       at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
       at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
       at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
       at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
       at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
       at org.geotools.xml.Parser.parse(Parser.java:185)
       at org.geotools.xml.Parser.parse(Parser.java:164)
       at
org.geoserver.wfs.xml.v1_0_0.WfsXmlReader.read(WfsXmlReader.java:60)
       at
org.geoserver.ows.Dispatcher.parseRequestXML(Dispatcher.java:1058)
       at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:375)
       at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:185)
       at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)

       at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Hi Sébastien,

Can you change:

<gml:Polygon>
<gml:exterior>
  <gml:LinearRing>
   <gml:posList>39.1 -10.67 43.71 -6.1 41.08 -3.46 36.24
-7.94 39.1 -10.67</gml:posList>
  </gml:LinearRing>
</gml:exterior>
</gml:Polygon>

To:

<gml:Polygon>
<gml:outerBoundaryIs>
  <gml:LinearRing>
   <gml:coordinates>39.1 -10.67 43.71 -6.1 41.08 -3.46 36.24
-7.94 39.1 -10.67</gml:coordinates>
  </gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>

And try again. Thanks.

-Justin

Sébastien Geindre wrote:

Justin Deoliveira a écrit :

Can you include the exact request. There are changes from gml2 to gml3
so i do not suspect geometries supplied in a wfs 1.1 to work with a 1.0
request. That is my guess as to what is happening here.

-Justin
  

here is the request :
<?xml version="1.0" encoding="UTF-8"?>
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs&quot;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
xmlns:wims="http://www.flysafe-eu.org/wims&quot;
xmlns:gml="http://www.opengis.net/gml&quot;
xmlns:ogc="http://www.opengis.net/ogc&quot;
xmlns:xlink="http://www.w3.org/1999/xlink&quot; service="WFS" version="1.0.0"
xsi:schemaLocation="http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd&quot;&gt;
<wfs:Query typeName="wims:cat">
   <ogc:Filter>
     <ogc:And>
       <ogc:And>
         <ogc:PropertyIsEqualTo>
           <ogc:PropertyName>real_time</ogc:PropertyName>
           <ogc:Literal>true</ogc:Literal>
         </ogc:PropertyIsEqualTo>
         <ogc:PropertyIsEqualTo>
           <ogc:PropertyName>type</ogc:PropertyName>
           <ogc:Literal>cat</ogc:Literal>
         </ogc:PropertyIsEqualTo>
       </ogc:And>
       <ogc:And>
         <ogc:And>
           <ogc:Or>
             <ogc:And>
               <ogc:PropertyIsLessThanOrEqualTo>
                 <ogc:PropertyName>bottom</ogc:PropertyName>
                 <ogc:Literal>0</ogc:Literal>
               </ogc:PropertyIsLessThanOrEqualTo>
               <ogc:PropertyIsGreaterThanOrEqualTo>
                 <ogc:PropertyName>top</ogc:PropertyName>
                 <ogc:Literal>10000</ogc:Literal>
               </ogc:PropertyIsGreaterThanOrEqualTo>
             </ogc:And>
             <ogc:Or>
               <ogc:PropertyIsBetween>
                 <ogc:PropertyName>bottom</ogc:PropertyName>
                 <ogc:LowerBoundary>
                   <ogc:Literal>0</ogc:Literal>
                 </ogc:LowerBoundary>
                 <ogc:UpperBoundary>
                   <ogc:Literal>10000</ogc:Literal>
                 </ogc:UpperBoundary>
               </ogc:PropertyIsBetween>
               <ogc:PropertyIsBetween>
                 <ogc:PropertyName>top</ogc:PropertyName>
                 <ogc:LowerBoundary>
                   <ogc:Literal>0</ogc:Literal>
                 </ogc:LowerBoundary>
                 <ogc:UpperBoundary>
                   <ogc:Literal>10000</ogc:Literal>
                 </ogc:UpperBoundary>
               </ogc:PropertyIsBetween>
             </ogc:Or>
           </ogc:Or>
           <ogc:Or>
             <ogc:And>
               <ogc:PropertyIsLessThanOrEqualTo>
                 <ogc:PropertyName>validity_start_time</ogc:PropertyName>
                 <ogc:Literal>2007-05-13T10:00:00.000Z</ogc:Literal>
               </ogc:PropertyIsLessThanOrEqualTo>
               <ogc:PropertyIsGreaterThanOrEqualTo>
                 <ogc:PropertyName>validity_end_time</ogc:PropertyName>
                 <ogc:Literal>2007-05-13T11:00:00.000Z</ogc:Literal>
               </ogc:PropertyIsGreaterThanOrEqualTo>
             </ogc:And>
             <ogc:Or>
               <ogc:PropertyIsBetween>
                 <ogc:PropertyName>validity_start_time</ogc:PropertyName>
                 <ogc:LowerBoundary>
                   <ogc:Literal>2007-05-13T10:00:00.000Z</ogc:Literal>
                 </ogc:LowerBoundary>
                 <ogc:UpperBoundary>
                   <ogc:Literal>2007-05-13T11:00:00.000Z</ogc:Literal>
                 </ogc:UpperBoundary>
               </ogc:PropertyIsBetween>
               <ogc:PropertyIsBetween>
                 <ogc:PropertyName>validity_end_time</ogc:PropertyName>
                 <ogc:LowerBoundary>
                   <ogc:Literal>2007-05-13T10:00:00.000Z</ogc:Literal>
                 </ogc:LowerBoundary>
                 <ogc:UpperBoundary>
                   <ogc:Literal>2007-05-13T11:00:00.000Z</ogc:Literal>
                 </ogc:UpperBoundary>
               </ogc:PropertyIsBetween>
             </ogc:Or>
           </ogc:Or>
         </ogc:And>
         <!-- Scale : regional-->
         <ogc:And>
           <ogc:PropertyIsEqualTo>
             <ogc:PropertyName>scale</ogc:PropertyName>
             <ogc:Literal>regional</ogc:Literal>
           </ogc:PropertyIsEqualTo>
           <ogc:Intersects>
             <ogc:PropertyName>geometry</ogc:PropertyName>
             <gml:Polygon>
               <gml:exterior>
                 <gml:LinearRing>
                   <gml:posList>39.1 -10.67 43.71 -6.1 41.08 -3.46 36.24
-7.94 39.1 -10.67</gml:posList>
                 </gml:LinearRing>
               </gml:exterior>
             </gml:Polygon>
           </ogc:Intersects>
         </ogc:And>
       </ogc:And>
     </ogc:And>
   </ogc:Filter>
</wfs:Query>
</wfs:GetFeature>

Sébastien Geindre wrote:

Justin Deoliveira a écrit :
   

Hmm... I just tried with a data source having only polygons and
it worked. Any chance you can provide us with a dump or your database?
If so, open a jira issue and attach the dump

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the
reprojecting
feature collection was not copying over user data when doing the
transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
        

i tried to make a wfs 1.0.0 request but it did not work.
I have just updated geotools and geoserver (back from holidays...)

any changes in geotools not compatible with geoserver 1.6 ?
or my wfs request is not 1.0 ? it should be that...

so difficult to say at this time if it works with wfs1.0 request...

10 janv. 17:35:34 WARN [org.geoserver.ows] -
java.lang.RuntimeException: Parsing failed for LinearRing:
java.lang.RuntimeException: Could not find coordinates to build
linestring

       at
org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:142)
       at
org.geotools.xml.impl.BindingWalker$BindingExecutionChain.execute(BindingWalker.java:197)

       at
org.geotools.xml.impl.BindingWalker.walk(BindingWalker.java:163)
       at
org.geotools.xml.impl.ElementHandlerImpl.endElement(ElementHandlerImpl.java:222)

       at
org.geotools.xml.impl.ParserHandler.endElement(ParserHandler.java:496)
       at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
       at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
       at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown

Source)
       at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown

Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
       at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
       at org.geotools.xml.Parser.parse(Parser.java:185)
       at org.geotools.xml.Parser.parse(Parser.java:164)
       at
org.geoserver.wfs.xml.v1_0_0.WfsXmlReader.read(WfsXmlReader.java:60)
       at
org.geoserver.ows.Dispatcher.parseRequestXML(Dispatcher.java:1058)
       at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:375)
       at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:185)
       at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)

       at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

I tried the following request wfs 1.0.0 and geoserver put srsName in the response !!!!

<wims:geometry>
<gml:Polygon srsName="http://www.opengis.net/gml/srs/epsg.xml#4326&quot;&gt;
<gml:outerBoundaryIs>
<gml:LinearRing>
<gml:coordinates cs="," decimal="." ts=" ">0.38,50.51 0.48,50.47 0.5,50.45 0.53,50.42 0.5,50.4 0.47,50.42 0.44,50.44 0.4,50.48 0.25,50.45 0.22,50.43 0.18,50.41 0.13,50.38 0.15,50.34 0.22,50.3 0.31,50.28 0.35,50.21 0.41,50.21 0.46,50.12 0.49,50.07 0.55,50.05 0.59,50.03 0.61,50 0.65,49.95 0.74,49.95 0.78,49.93 0.84,49.9 0.85,49.87 0.95,49.88 1.06,49.78 1.09,49.73 1.13,49.71 1.17,49.64 1.27,49.62 1.3,49.58 1.33,49.54 1.4,49.52 1.37,49.49 1.41,49.47 1.45,49.44 1.48,49.42 1.49,49.4 1.54,49.39 1.58,49.41 1.62,49.43 1.67,49.41 1.62,49.38 1.53,49.36 1.59,49.31 1.65,49.29 1.69,49.26 1.76,49.21 1.83,49.21 1.88,49.21 1.87,49.17 1.96,49.1 1.97,49.05 2,48.93 2.02,48.91 1.98,48.9 2.01,48.87 2.05,48.85 2.05,48.81 2.07,48.79 2.07,48.76 2.04,48.75 2.04,48.71 2.05,48.67 2.11,48.68 2.18,48.66 2.22,48.66 2.28,48.69 2.25,48.72 2.23,48.8 2.22,48.85 2.21,48.93 2.15,48.99 2.11,49.04 2.1,49.12 2.08,49.15 2.07,49.22 2.06,49.25 2.03,49.28 1.96,49.32 1.93,49.37 1.88,49.37 1.85,49.39 1.81,49.43 1.8,49.45 1.74,49.47 1.71,49.5 1.74,49.56 1.7,49.59 1.6,49.59 1.53,49.58 1.5,49.64 1.43,49.67 1.38,49.69 1.36,49.73 1.29,49.77 1.25,49.78 1.21,49.84 1.17,49.85 1.13,49.95 1.1,49.98 1.04,50.01 0.95,50.02 0.91,49.97 0.88,49.99 0.84,50.03 0.83,50.06 0.78,50.07 0.83,50.13 0.87,50.15 0.87,50.18 0.86,50.22 0.89,50.25 0.9,50.28 0.95,50.31 0.99,50.32 0.96,50.41 0.88,50.45 0.8,50.36 0.83,50.32 0.8,50.28 0.73,50.22 0.7,50.18 0.65,50.18 0.68,50.21 0.61,50.24 0.58,50.29 0.54,50.31 0.54,50.35 0.6,50.38 0.6,50.45 0.59,50.49 0.56,50.54 0.38,50.51</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</wims:geometry>

So you are right...
Is there any solution to have it in gml 3.1, wfs 1.1.0 ???

thanks again and again for helping...

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
  

so, it is confirmed.
srsName is present in wfs1.0 response but not in 1.1 as attribute of polygons.

This issue will it be corrected in 1.6 branch ?
how could i help ?

  

Cheers
Andrea

!DSPAM:4007,478650cd109972090977483!

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Hi Sébastien,

Apologies for the delayed response. The problem is that I cannot
reproduce this one. Can you help me by doing the following.

You are working from sources correct? First can you make sure that both
geotools 2.4.x and geoserver 1.6.x are up to date and rebuild them both.

Then you can you execute the following requests in your browser:

http://localhost:8080/geoserver/wfs?request=GetFeature&service=wfs&version=1.0.0&typename=wims:cat&maxfeatures=1
http://localhost:8080/geoserver/wfs?request=GetFeature&service=wfs&version=1.1.0&typename=wims:cat&maxfeatures=1

Then can you let me if you continue to see the srsName problem.

Thanks,

-Justin

Sébastien Geindre wrote:

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the
transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
  

so, it is confirmed.
srsName is present in wfs1.0 response but not in 1.1 as attribute of
polygons.

This issue will it be corrected in 1.6 branch ?
how could i help ?

Cheers
Andrea

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

You are working from sources correct? First can you make sure that both
geotools 2.4.x and geoserver 1.6.x are up to date and rebuild them both.
  

I 've just update and rebuild, execute requets. srsName pb is still there....

Then you can you execute the following requests in your browser:
http://localhost:8080/geoserver/wfs?request=GetFeature&service=wfs&version=1.0.0&typename=wims:cat&maxfeatures=1
  

<wfs:FeatureCollection xsi:schemaLocation="http://www.flysafe-eu.org/wims http://localhost:8080/geoserver/wfs?service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=wims:cat http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt;
    <gml:boundedBy>
    <gml:Box srsName="http://www.opengis.net/gml/srs/epsg.xml#4326&quot;&gt;
<gml:coordinates decimal="." cs="," ts=" ">-11,35 17,57</gml:coordinates>
</gml:Box>
</gml:boundedBy>
    <gml:featureMember>
    <wims:cat fid="cat.fid-52dc1f15_116ce12dcef_-7155">
<wims:type>cat</wims:type>
<wims:originating_center>FME</wims:originating_center>
<wims:scale>regional</wims:scale>
<wims:area_name>EUR</wims:area_name>
<wims:issue_time>2007-05-13T06:10:00</wims:issue_time>
<wims:refresh_time>2007-05-13T12:00:00</wims:refresh_time>
<wims:analysis_time>2007-05-13T06:00:00</wims:analysis_time>
<wims:forecast_time>0</wims:forecast_time>
<wims:validity_start_time>2007-05-13T04:31:00</wims:validity_start_time>
<wims:validity_end_time>2007-05-13T07:29:00</wims:validity_end_time>
<wims:confidence_level>1</wims:confidence_level>
<wims:intensity>1</wims:intensity>
<wims:altitude>5573.0</wims:altitude>
<wims:top>6342.0</wims:top>
<wims:bottom>5573.0</wims:bottom>
    <wims:geometry>
    <gml:Polygon srsName="http://www.opengis.net/gml/srs/epsg.xml#4326&quot;&gt;
    <gml:outerBoundaryIs>
    <gml:LinearRing>
    <gml:coordinates decimal="." cs="," ts=" ">
-11,38.6 -11,38.6 -10.9,38 -10.6,37.8 -10.3,37.3 -10.5,37.1 -10.4,37 -10.2,37 -10.1,37.1 -10.1,37.3 -9.9,37.3 -9.5,37.3 -9.2,37.2 -9.1,37.2 -8.8,37.1 -8.4,36.9 -7.9,36.8 -7.4,36.7 -7.3,36.7 -7,36.6 -6.6,36.5 -6.3,36.4 -6.2,36.4 -6,36.3 -5.5,36.2 -5.1,36.2 -4.7,36.1 -4.6,36.1 -4.3,36 -3.9,35.9 -3.6,35.8 -3.4,35.8 -2.9,35.7 -2.7,35.7 -2.4,35.6 -2.2,35.6 -1.8,35.6 -1.4,35.6 -1.1,35.6 -0.8,35.5 -0.6,35.5 -0.2,35.4 0,35.4 0.5,35.3 0.7,35.3 1.1,35.3 1.4,35.2 1.6,35.2 2,35.2 2.3,35.3 2.5,35.3 2.8,35.4 3,35.4 3.4,35.4 3.8,35.4 4.2,35.4 4.6,35.4 5,35.4 5.4,35.4 5.8,35.4 6.2,35.4 6.6,35.4 7,35.4 7.4,35.4 7.5,35.5 7.7,35.5 8.1,35.5 8.5,35.5 8.9,35.5 9,35.6 9.2,35.6 9.5,35.7 9.7,35.7 10,35.8 10.2,35.8 10.5,35.9 10.7,35.9 11.1,35.9 11.2,36 11.4,36 11.7,36.1 11.9,36.1 12.3,36.1 12.6,36.2 12.8,36.2 13.2,36.2 13.6,36.2 13.9,36.3 14.1,36.3 14.5,36.3 14.6,36.4 14.8,36.4 15.1,36.5 15.3,36.5 15.6,36.6 15.8,36.6 16.1,36.7 16.3,36.7 16.4,36.8 16.6,36.8 16.9,36.9 17,37.2 17,37.6 17,38 16.7,38.2 16.6,38.1 16.4,38.1 16.3,38 16.1,38 16,37.9 15.8,37.9 15.5,37.8 15.3,37.8 15,37.7 14.8,37.7 14.5,37.6 14.3,37.6 14,37.5 13.8,37.5 13.7,37.4 13.5,37.4 13.4,37.3 13.2,37.3 13.1,37.2 12.9,37.2 12.8,37.1 12.6,37.1 12.3,37 12.1,37 12,36.9 11.8,36.9 11.7,36.8 11.5,36.8 11.2,36.7 10.9,36.6 10.5,36.6 10.2,36.5 10,36.5 9.6,36.5 9.2,36.5 8.8,36.5 8.4,36.5 8,36.5 7.6,36.5 7.2,36.5 6.8,36.5 6.4,36.5 6,36.5 5.6,36.5 5.2,36.5 4.8,36.5 4.4,36.5 4,36.5 3.7,36.4 3.5,36.4 3.1,36.4 2.7,36.4 2.3,36.4 2,36.3 1.8,36.3 1.4,36.3 1,36.3 0.6,36.3 0.2,36.3 -0.2,36.3 -0.3,36.4 -0.6,36.4 -1,36.4 -1.4,36.4 -1.7,36.5 -2,36.5 -2.1,36.4 -2.3,36.4 -2.7,36.5 -3,36.5 -3.1,36.6 -3.4,36.6 -3.8,36.6 -3.8,36.4 -4,36.4 -4.4,36.4 -4.5,36.5 -4.8,36.6 -5.3,36.7 -5.7,36.7 -5.8,36.8 -6,36.9 -6.3,36.9 -6.5,37 -6.9,37 -7.1,37 -7.5,37.1 -7.9,37.3 -8.2,37.3 -8.3,37.4 -8.6,37.6 -8.9,37.7 -9.4,38.2 -9.4,38.4 -9.6,38.3 -9.7,38.2 -9.9,38.2 -10.1,38.3 -11,38.6 -11,38.6
</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</wims:geometry>
<wims:real_time>true</wims:real_time>
<wims:swp_id>swp_catr.200705130006000000_1</wims:swp_id>
</wims:cat>
</gml:featureMember>
</wfs:FeatureCollection

http://localhost:8080/geoserver/wfs?request=GetFeature&service=wfs&version=1.1.0&typename=wims:cat&maxfeatures=1
  
<wfs:FeatureCollection numberOfFeatures="1" timeStamp="2008-01-17T10:57:36.228+00:00" xsi:schemaLocation="http://www.flysafe-eu.org/wims http://localhost:8080/geoserver/wfs?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=wims:cat http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
    <gml:featureMembers>
    <wims:cat gml:id="cat.fid-52dc1f15_116ce12dcef_-7155">
    <gml:boundedBy>
    <gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326">
<gml:lowerCorner>35.2 -11.0</gml:lowerCorner>
<gml:upperCorner>38.6 17.0</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
<wims:type>cat</wims:type>
<wims:originating_center>FME</wims:originating_center>
<wims:scale>regional</wims:scale>
<wims:area_name>EUR</wims:area_name>
<wims:issue_time>2007-05-13T06:10:00+00:00</wims:issue_time>
<wims:refresh_time>2007-05-13T12:00:00+00:00</wims:refresh_time>
<wims:analysis_time>2007-05-13T06:00:00+00:00</wims:analysis_time>
<wims:forecast_time>0</wims:forecast_time>
<wims:validity_start_time>2007-05-13T04:31:00+00:00</wims:validity_start_time>
<wims:validity_end_time>2007-05-13T07:29:00+00:00</wims:validity_end_time>
<wims:confidence_level>1</wims:confidence_level>
<wims:intensity>1</wims:intensity>
<wims:altitude>5573.0</wims:altitude>
<wims:top>6342.0</wims:top>
<wims:bottom>5573.0</wims:bottom>
    <wims:geometry>
    <gml:Polygon>
    <gml:exterior>
    <gml:LinearRing>
    <gml:posList>
38.6 -11.0 38.6 -11.0 38.0 -10.9 37.8 -10.6 37.3 -10.3 37.1 -10.5 37.0 -10.4 37.0 -10.2 37.1 -10.1 37.3 -10.1 37.3 -9.9 37.3 -9.5 37.2 -9.2 37.2 -9.1 37.1 -8.8 36.9 -8.4 36.8 -7.9 36.7 -7.4 36.7 -7.3 36.6 -7.0 36.5 -6.6 36.4 -6.3 36.4 -6.2 36.3 -6.0 36.2 -5.5 36.2 -5.1 36.1 -4.7 36.1 -4.6 36.0 -4.3 35.9 -3.9 35.8 -3.6 35.8 -3.4 35.7 -2.9 35.7 -2.7 35.6 -2.4 35.6 -2.2 35.6 -1.8 35.6 -1.4 35.6 -1.1 35.5 -0.8 35.5 -0.6 35.4 -0.2 35.4 0.0 35.3 0.5 35.3 0.7 35.3 1.1 35.2 1.4 35.2 1.6 35.2 2.0 35.3 2.3 35.3 2.5 35.4 2.8 35.4 3.0 35.4 3.4 35.4 3.8 35.4 4.2 35.4 4.6 35.4 5.0 35.4 5.4 35.4 5.8 35.4 6.2 35.4 6.6 35.4 7.0 35.4 7.4 35.5 7.5 35.5 7.7 35.5 8.1 35.5 8.5 35.5 8.9 35.6 9.0 35.6 9.2 35.7 9.5 35.7 9.7 35.8 10.0 35.8 10.2 35.9 10.5 35.9 10.7 35.9 11.1 36.0 11.2 36.0 11.4 36.1 11.7 36.1 11.9 36.1 12.3 36.2 12.6 36.2 12.8 36.2 13.2 36.2 13.6 36.3 13.9 36.3 14.1 36.3 14.5 36.4 14.6 36.4 14.8 36.5 15.1 36.5 15.3 36.6 15.6 36.6 15.8 36.7 16.1 36.7 16.3 36.8 16.4 36.8 16.6 36.9 16.9 37.2 17.0 37.6 17.0 38.0 17.0 38.2 16.7 38.1 16.6 38.1 16.4 38.0 16.3 38.0 16.1 37.9 16.0 37.9 15.8 37.8 15.5 37.8 15.3 37.7 15.0 37.7 14.8 37.6 14.5 37.6 14.3 37.5 14.0 37.5 13.8 37.4 13.7 37.4 13.5 37.3 13.4 37.3 13.2 37.2 13.1 37.2 12.9 37.1 12.8 37.1 12.6 37.0 12.3 37.0 12.1 36.9 12.0 36.9 11.8 36.8 11.7 36.8 11.5 36.7 11.2 36.6 10.9 36.6 10.5 36.5 10.2 36.5 10.0 36.5 9.6 36.5 9.2 36.5 8.8 36.5 8.4 36.5 8.0 36.5 7.6 36.5 7.2 36.5 6.8 36.5 6.4 36.5 6.0 36.5 5.6 36.5 5.2 36.5 4.8 36.5 4.4 36.5 4.0 36.4 3.7 36.4 3.5 36.4 3.1 36.4 2.7 36.4 2.3 36.3 2.0 36.3 1.8 36.3 1.4 36.3 1.0 36.3 0.6 36.3 0.2 36.3 -0.2 36.4 -0.3 36.4 -0.6 36.4 -1.0 36.4 -1.4 36.5 -1.7 36.5 -2.0 36.4 -2.1 36.4 -2.3 36.5 -2.7 36.5 -3.0 36.6 -3.1 36.6 -3.4 36.6 -3.8 36.4 -3.8 36.4 -4.0 36.4 -4.4 36.5 -4.5 36.6 -4.8 36.7 -5.3 36.7 -5.7 36.8 -5.8 36.9 -6.0 36.9 -6.3 37.0 -6.5 37.0 -6.9 37.0 -7.1 37.1 -7.5 37.3 -7.9 37.3 -8.2 37.4 -8.3 37.6 -8.6 37.7 -8.9 38.2 -9.4 38.4 -9.4 38.3 -9.6 38.2 -9.7 38.2 -9.9 38.3 -10.1 38.6 -11.0 38.6 -11.0
</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</wims:geometry>
<wims:real_time>true</wims:real_time>
<wims:swp_id>swp_catr.200705130006000000_1</wims:swp_id>
</wims:cat>
</gml:featureMembers>
</wfs:FeatureCollection>
Then can you let me if you continue to see the srsName problem.
  

yes i do....

i 'll test again after update the code today.

Thanks,

-Justin

Sébastien Geindre wrote:
  

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the
transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
  

so, it is confirmed.
srsName is present in wfs1.0 response but not in 1.1 as attribute of
polygons.

This issue will it be corrected in 1.6 branch ?
how could i help ?
    

Cheers
Andrea

--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr

Apologies for the length of this thread :)... but i spotted the problem.
Can you please update and rebuild the geotools api module. This problem
should then go away now.

Thanks for the continued patience.

-Justin

Sébastien Geindre wrote:

You are working from sources correct? First can you make sure that both
geotools 2.4.x and geoserver 1.6.x are up to date and rebuild them both.
  

I 've just update and rebuild, execute requets. srsName pb is still
there....

Then you can you execute the following requests in your browser:
http://localhost:8080/geoserver/wfs?request=GetFeature&service=wfs&version=1.0.0&typename=wims:cat&maxfeatures=1
  

<wfs:FeatureCollection
xsi:schemaLocation="http://www.flysafe-eu.org/wims
http://localhost:8080/geoserver/wfs?service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=wims:cat
http://www.opengis.net/wfs
http://localhost:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd&quot;&gt;
    <gml:boundedBy>
    <gml:Box srsName="http://www.opengis.net/gml/srs/epsg.xml#4326&quot;&gt;
<gml:coordinates decimal="." cs="," ts=" ">-11,35 17,57</gml:coordinates>
</gml:Box>
</gml:boundedBy>
    <gml:featureMember>
    <wims:cat fid="cat.fid-52dc1f15_116ce12dcef_-7155">
<wims:type>cat</wims:type>
<wims:originating_center>FME</wims:originating_center>
<wims:scale>regional</wims:scale>
<wims:area_name>EUR</wims:area_name>
<wims:issue_time>2007-05-13T06:10:00</wims:issue_time>
<wims:refresh_time>2007-05-13T12:00:00</wims:refresh_time>
<wims:analysis_time>2007-05-13T06:00:00</wims:analysis_time>
<wims:forecast_time>0</wims:forecast_time>
<wims:validity_start_time>2007-05-13T04:31:00</wims:validity_start_time>
<wims:validity_end_time>2007-05-13T07:29:00</wims:validity_end_time>
<wims:confidence_level>1</wims:confidence_level>
<wims:intensity>1</wims:intensity>
<wims:altitude>5573.0</wims:altitude>
<wims:top>6342.0</wims:top>
<wims:bottom>5573.0</wims:bottom>
    <wims:geometry>
    <gml:Polygon srsName="http://www.opengis.net/gml/srs/epsg.xml#4326&quot;&gt;
    <gml:outerBoundaryIs>
    <gml:LinearRing>
    <gml:coordinates decimal="." cs="," ts=" ">
-11,38.6 -11,38.6 -10.9,38 -10.6,37.8 -10.3,37.3 -10.5,37.1 -10.4,37
-10.2,37 -10.1,37.1 -10.1,37.3 -9.9,37.3 -9.5,37.3 -9.2,37.2 -9.1,37.2
-8.8,37.1 -8.4,36.9 -7.9,36.8 -7.4,36.7 -7.3,36.7 -7,36.6 -6.6,36.5
-6.3,36.4 -6.2,36.4 -6,36.3 -5.5,36.2 -5.1,36.2 -4.7,36.1 -4.6,36.1
-4.3,36 -3.9,35.9 -3.6,35.8 -3.4,35.8 -2.9,35.7 -2.7,35.7 -2.4,35.6
-2.2,35.6 -1.8,35.6 -1.4,35.6 -1.1,35.6 -0.8,35.5 -0.6,35.5 -0.2,35.4
0,35.4 0.5,35.3 0.7,35.3 1.1,35.3 1.4,35.2 1.6,35.2 2,35.2 2.3,35.3
2.5,35.3 2.8,35.4 3,35.4 3.4,35.4 3.8,35.4 4.2,35.4 4.6,35.4 5,35.4
5.4,35.4 5.8,35.4 6.2,35.4 6.6,35.4 7,35.4 7.4,35.4 7.5,35.5 7.7,35.5
8.1,35.5 8.5,35.5 8.9,35.5 9,35.6 9.2,35.6 9.5,35.7 9.7,35.7 10,35.8
10.2,35.8 10.5,35.9 10.7,35.9 11.1,35.9 11.2,36 11.4,36 11.7,36.1
11.9,36.1 12.3,36.1 12.6,36.2 12.8,36.2 13.2,36.2 13.6,36.2 13.9,36.3
14.1,36.3 14.5,36.3 14.6,36.4 14.8,36.4 15.1,36.5 15.3,36.5 15.6,36.6
15.8,36.6 16.1,36.7 16.3,36.7 16.4,36.8 16.6,36.8 16.9,36.9 17,37.2
17,37.6 17,38 16.7,38.2 16.6,38.1 16.4,38.1 16.3,38 16.1,38 16,37.9
15.8,37.9 15.5,37.8 15.3,37.8 15,37.7 14.8,37.7 14.5,37.6 14.3,37.6
14,37.5 13.8,37.5 13.7,37.4 13.5,37.4 13.4,37.3 13.2,37.3 13.1,37.2
12.9,37.2 12.8,37.1 12.6,37.1 12.3,37 12.1,37 12,36.9 11.8,36.9
11.7,36.8 11.5,36.8 11.2,36.7 10.9,36.6 10.5,36.6 10.2,36.5 10,36.5
9.6,36.5 9.2,36.5 8.8,36.5 8.4,36.5 8,36.5 7.6,36.5 7.2,36.5 6.8,36.5
6.4,36.5 6,36.5 5.6,36.5 5.2,36.5 4.8,36.5 4.4,36.5 4,36.5 3.7,36.4
3.5,36.4 3.1,36.4 2.7,36.4 2.3,36.4 2,36.3 1.8,36.3 1.4,36.3 1,36.3
0.6,36.3 0.2,36.3 -0.2,36.3 -0.3,36.4 -0.6,36.4 -1,36.4 -1.4,36.4
-1.7,36.5 -2,36.5 -2.1,36.4 -2.3,36.4 -2.7,36.5 -3,36.5 -3.1,36.6
-3.4,36.6 -3.8,36.6 -3.8,36.4 -4,36.4 -4.4,36.4 -4.5,36.5 -4.8,36.6
-5.3,36.7 -5.7,36.7 -5.8,36.8 -6,36.9 -6.3,36.9 -6.5,37 -6.9,37 -7.1,37
-7.5,37.1 -7.9,37.3 -8.2,37.3 -8.3,37.4 -8.6,37.6 -8.9,37.7 -9.4,38.2
-9.4,38.4 -9.6,38.3 -9.7,38.2 -9.9,38.2 -10.1,38.3 -11,38.6 -11,38.6
</gml:coordinates>
</gml:LinearRing>
</gml:outerBoundaryIs>
</gml:Polygon>
</wims:geometry>
<wims:real_time>true</wims:real_time>
<wims:swp_id>swp_catr.200705130006000000_1</wims:swp_id>
</wims:cat>
</gml:featureMember>
</wfs:FeatureCollection

http://localhost:8080/geoserver/wfs?request=GetFeature&service=wfs&version=1.1.0&typename=wims:cat&maxfeatures=1
  
<wfs:FeatureCollection numberOfFeatures="1"
timeStamp="2008-01-17T10:57:36.228+00:00"
xsi:schemaLocation="http://www.flysafe-eu.org/wims
http://localhost:8080/geoserver/wfs?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=wims:cat
http://www.opengis.net/wfs
http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
    <gml:featureMembers>
    <wims:cat gml:id="cat.fid-52dc1f15_116ce12dcef_-7155">
    <gml:boundedBy>
    <gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326">
<gml:lowerCorner>35.2 -11.0</gml:lowerCorner>
<gml:upperCorner>38.6 17.0</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
<wims:type>cat</wims:type>
<wims:originating_center>FME</wims:originating_center>
<wims:scale>regional</wims:scale>
<wims:area_name>EUR</wims:area_name>
<wims:issue_time>2007-05-13T06:10:00+00:00</wims:issue_time>
<wims:refresh_time>2007-05-13T12:00:00+00:00</wims:refresh_time>
<wims:analysis_time>2007-05-13T06:00:00+00:00</wims:analysis_time>
<wims:forecast_time>0</wims:forecast_time>
<wims:validity_start_time>2007-05-13T04:31:00+00:00</wims:validity_start_time>
<wims:validity_end_time>2007-05-13T07:29:00+00:00</wims:validity_end_time>
<wims:confidence_level>1</wims:confidence_level>
<wims:intensity>1</wims:intensity>
<wims:altitude>5573.0</wims:altitude>
<wims:top>6342.0</wims:top>
<wims:bottom>5573.0</wims:bottom>
    <wims:geometry>
    <gml:Polygon>
    <gml:exterior>
    <gml:LinearRing>
    <gml:posList>
38.6 -11.0 38.6 -11.0 38.0 -10.9 37.8 -10.6 37.3 -10.3 37.1 -10.5 37.0
-10.4 37.0 -10.2 37.1 -10.1 37.3 -10.1 37.3 -9.9 37.3 -9.5 37.2 -9.2
37.2 -9.1 37.1 -8.8 36.9 -8.4 36.8 -7.9 36.7 -7.4 36.7 -7.3 36.6 -7.0
36.5 -6.6 36.4 -6.3 36.4 -6.2 36.3 -6.0 36.2 -5.5 36.2 -5.1 36.1 -4.7
36.1 -4.6 36.0 -4.3 35.9 -3.9 35.8 -3.6 35.8 -3.4 35.7 -2.9 35.7 -2.7
35.6 -2.4 35.6 -2.2 35.6 -1.8 35.6 -1.4 35.6 -1.1 35.5 -0.8 35.5 -0.6
35.4 -0.2 35.4 0.0 35.3 0.5 35.3 0.7 35.3 1.1 35.2 1.4 35.2 1.6 35.2 2.0
35.3 2.3 35.3 2.5 35.4 2.8 35.4 3.0 35.4 3.4 35.4 3.8 35.4 4.2 35.4 4.6
35.4 5.0 35.4 5.4 35.4 5.8 35.4 6.2 35.4 6.6 35.4 7.0 35.4 7.4 35.5 7.5
35.5 7.7 35.5 8.1 35.5 8.5 35.5 8.9 35.6 9.0 35.6 9.2 35.7 9.5 35.7 9.7
35.8 10.0 35.8 10.2 35.9 10.5 35.9 10.7 35.9 11.1 36.0 11.2 36.0 11.4
36.1 11.7 36.1 11.9 36.1 12.3 36.2 12.6 36.2 12.8 36.2 13.2 36.2 13.6
36.3 13.9 36.3 14.1 36.3 14.5 36.4 14.6 36.4 14.8 36.5 15.1 36.5 15.3
36.6 15.6 36.6 15.8 36.7 16.1 36.7 16.3 36.8 16.4 36.8 16.6 36.9 16.9
37.2 17.0 37.6 17.0 38.0 17.0 38.2 16.7 38.1 16.6 38.1 16.4 38.0 16.3
38.0 16.1 37.9 16.0 37.9 15.8 37.8 15.5 37.8 15.3 37.7 15.0 37.7 14.8
37.6 14.5 37.6 14.3 37.5 14.0 37.5 13.8 37.4 13.7 37.4 13.5 37.3 13.4
37.3 13.2 37.2 13.1 37.2 12.9 37.1 12.8 37.1 12.6 37.0 12.3 37.0 12.1
36.9 12.0 36.9 11.8 36.8 11.7 36.8 11.5 36.7 11.2 36.6 10.9 36.6 10.5
36.5 10.2 36.5 10.0 36.5 9.6 36.5 9.2 36.5 8.8 36.5 8.4 36.5 8.0 36.5
7.6 36.5 7.2 36.5 6.8 36.5 6.4 36.5 6.0 36.5 5.6 36.5 5.2 36.5 4.8 36.5
4.4 36.5 4.0 36.4 3.7 36.4 3.5 36.4 3.1 36.4 2.7 36.4 2.3 36.3 2.0 36.3
1.8 36.3 1.4 36.3 1.0 36.3 0.6 36.3 0.2 36.3 -0.2 36.4 -0.3 36.4 -0.6
36.4 -1.0 36.4 -1.4 36.5 -1.7 36.5 -2.0 36.4 -2.1 36.4 -2.3 36.5 -2.7
36.5 -3.0 36.6 -3.1 36.6 -3.4 36.6 -3.8 36.4 -3.8 36.4 -4.0 36.4 -4.4
36.5 -4.5 36.6 -4.8 36.7 -5.3 36.7 -5.7 36.8 -5.8 36.9 -6.0 36.9 -6.3
37.0 -6.5 37.0 -6.9 37.0 -7.1 37.1 -7.5 37.3 -7.9 37.3 -8.2 37.4 -8.3
37.6 -8.6 37.7 -8.9 38.2 -9.4 38.4 -9.4 38.3 -9.6 38.2 -9.7 38.2 -9.9
38.3 -10.1 38.6 -11.0 38.6 -11.0
</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</wims:geometry>
<wims:real_time>true</wims:real_time>
<wims:swp_id>swp_catr.200705130006000000_1</wims:swp_id>
</wims:cat>
</gml:featureMembers>
</wfs:FeatureCollection>
Then can you let me if you continue to see the srsName problem.
  

yes i do....

i 'll test again after update the code today.

Thanks,

-Justin

Sébastien Geindre wrote:
  

I think i may know what is going on here... I just fixed an issue on
trunk that related to a missing srsName due to reprojection occurring
due to being a 1.1 request. The issue was that was then the reprojecting
feature collection was not copying over user data when doing the
transform.

Sebastien, does the srsName show up when you do a wfs 1.0 request?
  

so, it is confirmed.
srsName is present in wfs1.0 response but not in 1.1 as attribute of
polygons.

This issue will it be corrected in 1.6 branch ?
how could i help ?
    

Cheers
Andrea

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org