[Geoserver-users] WFS-T request @ Geoserver 1.7.2

D.Nunes · February 18, 2009, 7:28pm

Hi all,

In a wfs-t request, where can i add an optional parameter like maxFeatures
or outputFormat in the request.

Request: (At Geoserver Sample Requests, the WFS_transactionUpdate.xml)

<wfs:Transaction service="WFS" version="1.0.0"
  xmlns:topp="http://www.openplans.org/topp"
  xmlns:ogc="http://www.opengis.net/ogc"
  xmlns:wfs="http://www.opengis.net/wfs">
  <wfs:Update typeName="topp:tasmania_roads">
    <wfs:Property>
      <wfs:Name>TYPE</wfs:Name>
      <wfs:Value>street</wfs:Value>
    </wfs:Property>
    <ogc:Filter>
      <ogc:FeatureId fid="tasmania_roads.1"/>
    </ogc:Filter>
  </wfs:Update>
</wfs:Transaction>

Cumps,

D.Nunes
--
View this message in context: http://www.nabble.com/WFS-T-request-%40-Geoserver-1.7.2-tp22086352p22086352.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Justin_Deoliveira · February 19, 2009, 4:00am

Hi,

Those parameters only appy to a GetFeature request, and will be ignored by transaction. They are attributes of the root GetFeature element.

-Justin

D.Nunes wrote:

Hi all,

In a wfs-t request, where can i add an optional parameter like maxFeatures
or outputFormat in the request.

Request: (At Geoserver Sample Requests, the WFS_transactionUpdate.xml)

<wfs:Transaction service="WFS" version="1.0.0"
  xmlns:topp="http://www.openplans.org/topp"
  xmlns:ogc="http://www.opengis.net/ogc"
  xmlns:wfs="http://www.opengis.net/wfs">
  <wfs:Update typeName="topp:tasmania_roads">
    <wfs:Property>
      <wfs:Name>TYPE</wfs:Name>
      <wfs:Value>street</wfs:Value>
    </wfs:Property>
    <ogc:Filter>
      <ogc:FeatureId fid="tasmania_roads.1"/>
    </ogc:Filter>
  </wfs:Update>
</wfs:Transaction>

Cumps,

D.Nunes

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

D.Nunes · February 19, 2009, 11:01am

There are any other parameters?

Or which parameters can i put in a wfs-t request?

Cumps.

D.Nunes

Justin Deoliveira-6 wrote:

Hi,

Those parameters only appy to a GetFeature request, and will be ignored
by transaction. They are attributes of the root GetFeature element.

-Justin

D.Nunes wrote:

Hi all,

In a wfs-t request, where can i add an optional parameter like
maxFeatures
or outputFormat in the request.

Request: (At Geoserver Sample Requests, the WFS_transactionUpdate.xml)

<wfs:Transaction service="WFS" version="1.0.0"
  xmlns:topp="http://www.openplans.org/topp"
  xmlns:ogc="http://www.opengis.net/ogc"
  xmlns:wfs="http://www.opengis.net/wfs">
  <wfs:Update typeName="topp:tasmania_roads">
    <wfs:Property>
      <wfs:Name>TYPE</wfs:Name>
      <wfs:Value>street</wfs:Value>
    </wfs:Property>
    <ogc:Filter>
      <ogc:FeatureId fid="tasmania_roads.1"/>
    </ogc:Filter>
  </wfs:Update>
</wfs:Transaction>

Cumps,

D.Nunes

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
CA
-OSBC tackles the biggest issue in open source: Open Sourcing the
Enterprise
-Strategies to boost innovation and cut costs with open source
participation
-Receive a $600 discount off the registration fee with the source code:
SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/WFS-T-request-%40-Geoserver-1.7.2-tp22086352p22098105.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Andrea_Aime3 · February 19, 2009, 11:17am

D.Nunes ha scritto:

There are any other parameters?

Or which parameters can i put in a wfs-t request?

Have a look at the official specifications for WFS 1.0
and WFS 1.1:
http://www.opengeospatial.org/standards/wfs

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Toan_Nguyen · February 20, 2009, 7:32am

Hi all,
I download Geoserver 172 to test before using. I have installed pds_durbuy, and then I can see it on map. But I can do a simple wfs request:

<wfs:GetFeature service=“WFS” version=“1.0.0”
outputFormat=“GML2”
xmlns:topp=“http://www.openplans.org/topp”
xmlns:durbuy=“http://www.d2d3.com/durbuy”
xmlns:wfs=“http://www.opengis.net/wfs”
xmlns:ogc=“http://www.opengis.net/ogc”
xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”
xsi:schemaLocation=“http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd”>
<wfs:Query typeName=“durbuy:pds_durbuy”>
ogc:Filter
<ogc:FeatureId fid=“pds_durbuy.3”/>
</ogc:Filter>
</wfs:Query>
</wfs:GetFeature>

Result:

error:Translator error
Translator error
Error reading Features
Could not aquire feature:org.geotools.data.DataSourceException: Error Performing SQL query: SELECT “gid”, “dolgis_gra”, “objectid”, “affect”, “sect_78”, “descriptio”, “art_cwatup”, “lien_walle”, “metadata”, “shape_leng”, “shape_area”, encode(asBinary(force_2d(“the_geom”),‘XDR’),‘base64’) FROM “public”.“pds_durbuy” WHERE () LIMIT 1000000

WHERE statement is empty.

Nguyễn Đình Toán

Neu khong doc duoc tieng Viet, vui long chon Encoding là Unicode (UTF-8). Cam on.

Andrea_Aime3 · February 20, 2009, 7:38am

Toan Nguyen ha scritto:

Hi all,
I download Geoserver 172 to test before using. I have installed pds_durbuy, and then I can see it on map. But I can do a simple wfs request:

<wfs:GetFeature service="WFS" version="1.0.0"
  outputFormat="GML2"
  xmlns:topp="http://www.openplans.org/topp"
  xmlns:durbuy="http://www.d2d3.com/durbuy"
  xmlns:wfs="http://www.opengis.net/wfs"
  xmlns:ogc="http://www.opengis.net/ogc"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.opengis.net/wfs
                      http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd">
  <wfs:Query typeName="durbuy:pds_durbuy">
    <ogc:Filter>
       <ogc:FeatureId fid="pds_durbuy.3"/>
    </ogc:Filter>
    </wfs:Query>
</wfs:GetFeature>

Result:
error:Translator error
Translator error
Error reading Features
Could not aquire feature:org.geotools.data.DataSourceException: Error Performing SQL query: SELECT "gid", "dolgis_gra", "objectid", "affect", "sect_78", "descriptio", "art_cwatup", "lien_walle", "metadata", "shape_leng", "shape_area", encode(asBinary(force_2d("the_geom"),'XDR'),'base64') FROM "public"."pds_durbuy" WHERE () LIMIT 1000000

WHERE statement is empty.

Hum, this is not looking good, the where clause should not have been
there, or be "where false" (if the only fid you provided is not
structurally valid for that table).

Most likely the issue is that your table does not have
a primary key, so the fid you specified cannot be matched back to
a filter on the (missing) primary key. Any fid that does not conform
to what GeoServer would generate gets removed before encoding (so
in this case the where clause should have been "where false", since
no record can satisfy your request).

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Toan_Nguyen · February 21, 2009, 1:56pm

Yeah, this table have no primary key. I have fixed, and it run well.
Thank you very much.

On Fri, Feb 20, 2009 at 2:38 PM, Andrea Aime <aaime@anonymised.com> wrote:

Most likely the issue is that your table does not have

a primary key, so the fid you specified cannot be matched back to
a filter on the (missing) primary key. Any fid that does not conform
to what GeoServer would generate gets removed before encoding (so
in this case the where clause should have been “where false”, since
no record can satisfy your request).

Cheers
Andrea

–
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

–
Nguyễn Đình Toán

Neu khong doc duoc tieng Viet, vui long chon Encoding là Unicode (UTF-8). Cam on.