[Geoserver-users] Geoserver ArcSDE WFS-T

Has anybody been able to get GeoServer to work with ArcSDE 9.2 using WFS-T.

I am running ArcSDE 9.2 sp5, and I need to use WFS-T for update, insert & delete.

I have tried basically all version of GeoServer. I’ve managed to get version 1.5.4 to update & delete, but not insert.

And for all the other version, I’ve either have porblem connecting to SDE, or having porblem with loading a new featureType, problems other people seem to have experienced as well.

I really would like to know how to get GeoServer to work with ArcSDE with WFS-T.

Thanks.

________________________________________________

Yi Lik Tsang
GIS Developer

SPATIAL VISION
Level 2, 170 Queen Street, Melbourne, VIC, 3000
Phone: +61 3 9691 3013
Fax: +61 3 9691 3001
E-mail: yilik.tsang@anonymised.com

For our latest news visit http://www.spatialvision.com.au This e-mail is privileged and confidential and intended only for the addressee(s). If received in error advise Spatial Vision by return e-mail and then please delete.
Please consider the environment before printing this email.

Hi Yi,

On Wednesday 03 September 2008 05:38:29 am Yi Lik Tsang wrote:

Has anybody been able to get GeoServer to work with ArcSDE 9.2 using
WFS-T.

yes? at least I know of a couple corporate users that are happy with it or
when they wasn't they invested some resources into improving the GeoServer
ArcSDE extension.

I am running ArcSDE 9.2 sp5, and I need to use WFS-T for update, insert
& delete.

I have tried basically all version of GeoServer. I've managed to get
version 1.5.4 to update & delete, but not insert.

And for all the other version, I've either have porblem connecting to
SDE, or having porblem with loading a new featureType, problems other
people seem to have experienced as well.

well, this is an open source project, so you either:
- provide a patch with proper unit tests and the module maintainers will be
glad to review it and apply it for you if the patch it good enough
- get a contract with one of the many organizations that support geoserver to
fix it for you
- or kindly ask the community to look over the problems you're experiencing
and hope them fix it for you for free. But for that to happen you need to
provide more information that the developers can use to assess your problem.
A simple statement of frustration gives us anything to work on. You can
usually send a stack trace report, describe better your problem and the steps
to reproduce, describe the structure of the tables you're trying to access
and are failing, or even provide a sample dataset that happens to fail.
Also, if the instructions at
http://docs.codehaus.org/display/GEOTDOC/ArcSDE+DataStore are not good or out
of date, once you solve your problem you could contribute some documentation
clean up in order to avoid others the pain you're suffering.

best regards,

Gabriel

I really would like to know how to get GeoServer to work with ArcSDE
with WFS-T.

And I really would like to help you. If the instructions on

Thanks.

________________________________________________

Yi Lik Tsang
GIS Developer

SPATIAL VISION
Level 2, 170 Queen Street, Melbourne, VIC, 3000
Phone: +61 3 9691 3013
Fax: +61 3 9691 3001
E-mail: yilik.tsang@anonymised.com

For our latest news visit http://www.spatialvision.com.au
This e-mail is privileged and confidential and intended only for the
addressee(s). If received in error advise Spatial Vision by return e-mail
and then please delete. Please consider the environment before printing
this email.

Yi,
Just to chime in, here in Massachusetts we are currently running WFS-T with
SDE 9.2 SP5 and GeoServer 1.6.5. Before that we were using SDE 9.1 SP 1 and
GeoServer 1.3. So it can be done!
--
View this message in context: http://www.nabble.com/Geoserver-ArcSDE-WFS-T-tp19297795p19309002.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Hi Gabriel + all,

Thanks for the relpy.

I have done a bit more testing in the last few days, and using GeoServer
1.6.5 beta, I have managed to get either update and delete, or just
insert to work, but not both.

In GeoServer, I created a namespace with URI:
http://au.spatialvision.com, and prefix: sv. Using
xmlns:sv="http://au.spatialvision.com/", I would get an error doing
update or delete, but works fine with insert.

WFS-T Insert (Success):
<?xml version="1.0" encoding="UTF-8"?>
<wfs:Transaction
  service="WFS"
  version="1.0.0"
  handle="IMFinsert"
  xmlns:sv="http://au.spatialvision.com/&quot;
  xmlns:wfs="http://www.opengis.net/wfs&quot;
  xmlns:ogc="http://www.opengis.net/ogc&quot;
  xmlns:gml="http://www.opengis.net/gml&quot;&gt;
  <wfs:Insert>
    <sv:NCCMA.GISADMIN.SVPOINTTEST>
      <SHAPE>
        <gml:Point srsName="EPSG:4283">
          
<gml:coordinates>143.88987121309273,-36.10663900954768</gml:coordinates>
        </gml:Point>
      </SHAPE>
    </sv:NCCMA.GISADMIN.SVPOINTTEST>
  </wfs:Insert>
</wfs:Transaction>

WFS-T Delete (fail):
<?xml version="1.0" encoding="UTF-8"?>
<wfs:Transaction
  service="WFS"
  version="1.0.0"
  handle="IMFdelete"
  xmlns:sv="http://au.spatialvision.com/&quot;
  xmlns:wfs="http://www.opengis.net/wfs&quot;
  xmlns:ogc="http://www.opengis.net/ogc&quot;
  xmlns:gml="http://www.opengis.net/gml&quot;&gt;
  <wfs:Delete typeName="sv:NCCMA.GISADMIN.SVPOINTTEST">
    <ogc:Filter>
      <FeatureId fid="NCCMA.GISADMIN.SVPOINTTEST.41"/>
    </ogc:Filter>
  </wfs:Delete>
</wfs:Transaction>
<?xml version="1.0" ?>
<ServiceExceptionReport
  version="1.2.0"
  xmlns="http://www.opengis.net/ogc&quot;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation="http://www.opengis.net/ogc
http://schemas.opengis.net/wfs/1.0.0/OGC-exception.xsd&quot;&gt;
  <ServiceException>
    org.geoserver.wfs.WFSException: Could not locate FeatureStore
for "{http://au.spatialvision.com/\}NCCMA.GISADMIN.SVPOINTTEST"
  </ServiceException>
</ServiceExceptionReport>
at
org.geoserver.wfs.UpdateElementHandler.execute(UpdateElementHandler.java
:130)

WFS-T Update (fail)
<?xml version="1.0" encoding="UTF-8"?>
<wfs:Transaction
  service="WFS"
  version="1.0.0"
  handle="IMFupdate"
  xmlns:sv="http://au.spatialvision.com/&quot;
  xmlns:wfs="http://www.opengis.net/wfs&quot;
  xmlns:ogc="http://www.opengis.net/ogc&quot;
  xmlns:gml="http://www.opengis.net/gml&quot;&gt;
  <wfs:Update typeName="sv:NCCMA.GISADMIN.SVPOINTTEST">
    <wfs:Property>
      <wfs:Name>SHAPE</wfs:Name>
      <wfs:Value>
        <gml:Point srsName="EPSG:4283">
          
<gml:coordinates>144.48483089829804,-36.12842743111402</gml:coordinates>
        </gml:Point>
      </wfs:Value>
    </wfs:Property>
    <ogc:Filter>
      <ogc:FeatureId fid="NCCMA.GISADMIN.SVPOINTTEST.1688"/>
    </ogc:Filter>
  </wfs:Update>
</wfs:Transaction>
<?xml version="1.0" ?>
<ServiceExceptionReport
  version="1.2.0"
  xmlns="http://www.opengis.net/ogc&quot;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation="http://www.opengis.net/ogc
http://schemas.opengis.net/wfs/1.0.0/OGC-exception.xsd&quot;&gt;
  <ServiceException>
    org.geoserver.wfs.WFSException: Could not locate FeatureStore
for "{http://au.spatialvision.com/\}NCCMA.GISADMIN.SVPOINTTEST"
  </ServiceException>
</ServiceExceptionReport>
at
org.geoserver.wfs.UpdateElementHandler.execute(UpdateElementHandler.java
:130)

However, if the xmlns in the WFS-T Transcational XML is changed from
xmlns:sv="http://au.spatialvision.com/&quot; to
xmlns:sde="http://au.spatialvision.com/&quot;\. That is, absolutely nothing
is changed in GeoServer, and the FeatureType in GeoServer is still
sv:NCCMA.GISADMIN.SVPOINTTEST. I would be able to do update or delete,
but not insert.

WFS-T Delete (Success):
<?xml version="1.0" encoding="UTF-8"?>
<wfs:Transaction
  service="WFS"
  version="1.0.0"
  handle="IMFdelete"
  xmlns:sde="http://au.spatialvision.com/&quot;
  xmlns:wfs="http://www.opengis.net/wfs&quot;
  xmlns:ogc="http://www.opengis.net/ogc&quot;
  xmlns:gml="http://www.opengis.net/gml&quot;&gt;
  <wfs:Delete typeName="sv:NCCMA.GISADMIN.SVPOINTTEST">
    <ogc:Filter>
      <FeatureId fid="NCCMA.GISADMIN.SVPOINTTEST.57"/>
    </ogc:Filter>
  </wfs:Delete>
</wfs:Transaction>

WFS-T Update (Success):
<?xml version="1.0" encoding="UTF-8"?>
<wfs:Transaction
  service="WFS"
  version="1.0.0"
  handle="IMFupdate"
  xmlns:sde="http://au.spatialvision.com/&quot;
  xmlns:wfs="http://www.opengis.net/wfs&quot;
  xmlns:ogc="http://www.opengis.net/ogc&quot;
  xmlns:gml="http://www.opengis.net/gml&quot;&gt;
  <wfs:Update typeName="sv:NCCMA.GISADMIN.SVPOINTTEST">
    <wfs:Property>
      <wfs:Name>SHAPE</wfs:Name>
      <wfs:Value>
        <gml:Point srsName="EPSG:4283">
          
<gml:coordinates>143.70662636644562,-35.78084618396142</gml:coordinates>
        </gml:Point>
      </wfs:Value>
    </wfs:Property>
    <ogc:Filter>
      <ogc:FeatureId fid="NCCMA.GISADMIN.SVPOINTTEST.41"/>
    </ogc:Filter>
  </wfs:Update>
</wfs:Transaction>

WFS-T Insert (Fail):
<?xml version="1.0" encoding="UTF-8"?>
<wfs:Transaction
  service="WFS"
  version="1.0.0"
  handle="IMFinsert"
  xmlns:sde="http://au.spatialvision.com/&quot;
  xmlns:wfs="http://www.opengis.net/wfs&quot;
  xmlns:ogc="http://www.opengis.net/ogc&quot;
  xmlns:gml="http://www.opengis.net/gml&quot;&gt;
  <wfs:Insert>
    <sv:NCCMA.GISADMIN.SVPOINTTEST>
      <SHAPE>
        <gml:Point srsName="EPSG:4283">
          
<gml:coordinates>143.83011628903543,-36.3630334994521</gml:coordinates>
        </gml:Point>
      </SHAPE>
    </sv:NCCMA.GISADMIN.SVPOINTTEST>
  </wfs:Insert>
</wfs:Transaction>
<?xml version="1.0" ?>
<ServiceExceptionReport
  version="1.2.0"
  xmlns="http://www.opengis.net/ogc&quot;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation="http://www.opengis.net/ogc
http://schemas.opengis.net/wfs/1.0.0/OGC-exception.xsd&quot;&gt;
  <ServiceException>
    org.xml.sax.SAXParseException: The prefix "sv" for element
"sv:NCCMA.GISADMIN.SVPOINTTEST" is not bound.
  </ServiceException>
</ServiceExceptionReport>

Has anybody experience simlier problem?? And sicne some user has been
able to get WFS-T to work, I really would like to know the setup they
are using.

Any kind of help is appericated.

Thanks.

Yi Lik

________________________________________________

Yi Lik Tsang
GIS Developer

SPATIAL VISION
Level 2, 170 Queen Street, Melbourne, VIC, 3000
Phone: +61 3 9691 3013
Fax: +61 3 9691 3001
E-mail: yilik.tsang@anonymised.com

-----Original Message-----
From: Gabriel Roldán [mailto:groldan@anonymised.com]
Sent: Thursday, 4 September 2008 10:23 AM
To: geoserver-users@lists.sourceforge.net
Cc: Yi Lik Tsang
Subject: Re: [Geoserver-users] Geoserver ArcSDE WFS-T

Hi Yi,

On Wednesday 03 September 2008 05:38:29 am Yi Lik Tsang wrote:

Has anybody been able to get GeoServer to work with ArcSDE 9.2 using
WFS-T.

yes? at least I know of a couple corporate users that are happy with it
or
when they wasn't they invested some resources into improving the
GeoServer
ArcSDE extension.

I am running ArcSDE 9.2 sp5, and I need to use WFS-T for update,
insert & delete.

I have tried basically all version of GeoServer. I've managed to get
version 1.5.4 to update & delete, but not insert.

And for all the other version, I've either have porblem connecting to
SDE, or having porblem with loading a new featureType, problems other
people seem to have experienced as well.

well, this is an open source project, so you either:
- provide a patch with proper unit tests and the module maintainers will
be
glad to review it and apply it for you if the patch it good enough
- get a contract with one of the many organizations that support
geoserver to
fix it for you
- or kindly ask the community to look over the problems you're
experiencing
and hope them fix it for you for free. But for that to happen you need
to
provide more information that the developers can use to assess your
problem.
A simple statement of frustration gives us anything to work on. You can
usually send a stack trace report, describe better your problem and the
steps
to reproduce, describe the structure of the tables you're trying to
access
and are failing, or even provide a sample dataset that happens to fail.
Also, if the instructions at
http://docs.codehaus.org/display/GEOTDOC/ArcSDE+DataStore are not good
or out
of date, once you solve your problem you could contribute some
documentation
clean up in order to avoid others the pain you're suffering.

best regards,

Gabriel

I really would like to know how to get GeoServer to work with ArcSDE
with WFS-T.

And I really would like to help you. If the instructions on

Thanks.

________________________________________________

Yi Lik Tsang
GIS Developer

SPATIAL VISION
Level 2, 170 Queen Street, Melbourne, VIC, 3000
Phone: +61 3 9691 3013
Fax: +61 3 9691 3001
E-mail: yilik.tsang@anonymised.com

For our latest news visit http://www.spatialvision.com.au This e-mail
is privileged and confidential and intended only for the addressee(s).

If received in error advise Spatial Vision by return e-mail and then
please delete. Please consider the environment before printing this
email.

For our latest news visit http://www.spatialvision.com.au
This e-mail is privileged and confidential and intended only for the addressee(s). If received in error advise Spatial Vision by return e-mail and then please delete.
Please consider the environment before printing this email.

Hi,

I tried to do my first WFS-T version 1.1.0 insert but the result was not promising. Here is my situation:

- I read the "States" polygon layer through WFS 1.1.0 with a GIS client. Client is flipping the axis but I don't care about that.
- I digitised a new polygon (triangle) on a states layer
- I let the GIS client to send WFS insert request.

The result is in the end of the message. When I compared the request with Geoserver demo requests I can see some differences, for example single vs. double quotas. Anybody having an idea if quotas are the the reason for failure, or the flipped axis, or something else?

-Jukka Rahkonen-

Listing from Geoserver console:

Result:
12 syys 14:43:23 INFO [org.geoserver.filters] - Compressing output for mimetype: text/xml
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - First 4 bytes of XML doc are : 3C ('<') 3F ('?') 78 ('x') 6D ('m')
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - Charset detection phase 1. Inferred encoding: UTF-8
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - Charset detection phase 2. Charset in XML declaration is `null`.
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - Trying to create reader basing on existing charset information: `UTF-8`.
12 syys 14:59:56 DEBUG [org.geoserver.ows] - Raw XML request starts with: <?xml version='1.0' encoding='ISO-8859-1'?><wfs:Transaction version='1.1.0'
service='WFS' xmlns:gml='http://www.opengis.net/gml’ xmlns:ogc='http://www.opengis.net/ogc’ xmlns:wfs='http://www.opengis.net/wfs’ xmlns:xsi='http://w
ww.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://www.opengis.net/wfs/1.1.0/WFS-transaction.xsd’ xmlns:topp='http://www.openplans.org/topp
' ><wfs:Insert handle='insert1' idgen='GenerateNew' ><topp:states><topp:the_geom><gml:Surface srsName='urn:x-ogc:def:crs:EPSG:6.11.2:4326'>
<gml:patches>
<gml:PolygonPatch>
<gml:exterior><gml:LinearRing><gml:posList srsDimension='2' count='4'>29.422823762810733 -71.86195768805085 36.22812243286723 -70.16063302053672 31.12
414843032486 -76.6256667570904 29.422823762810733 -71.86195768805085</gml:posList></gml:LinearRing></gml:exterior></gml:PolygonPatch>
</gml:patches>
</gml:Surface></topp:the_geom></topp:states></wfs:Insert></wfs:Transaction>

12 syys 14:59:56 WARN [org.geoserver.ows] -
java.lang.ArrayIndexOutOfBoundsException: 1
        at org.geotools.xml.impl.ParserHandler.startElement(ParserHandler.java:261)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(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.XML11Configuration.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.geoserver.wfs.xml.v1_1_0.WfsXmlReader.read(WfsXmlReader.java:78)
        at org.geoserver.ows.Dispatcher.parseRequestXML(Dispatcher.java:1072)
        at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:389)
        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)
        at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:684)
        at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625)
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392)
        at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:357)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1054)
        at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.geoserver.filters.ReverseProxyFilter.doFilter(ReverseProxyFilter.java:170)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:73)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:47)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:264)
        at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107)
        at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:110)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:178)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:229)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148)
        at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:358)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:453)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
        at org.mortbay.jetty.Server.handle(Server.java:303)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:320)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

Hi Jukka,

There is a minor issue with your request. The schemaLocation attribute on the root element is invalid. It needs to be a space separated set of tuples of the form "<namespace> <location>...". So if you change the schemaLocation attribute to:

"http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd&quot;

It should work. You can also just omit the attribute all together. Try that and let us know how it works.

-Justin

Rahkonen Jukka wrote:

Hi,

I tried to do my first WFS-T version 1.1.0 insert but the result was not promising. Here is my situation:

- I read the "States" polygon layer through WFS 1.1.0 with a GIS client. Client is flipping the axis but I don't care about that.
- I digitised a new polygon (triangle) on a states layer
- I let the GIS client to send WFS insert request.

The result is in the end of the message. When I compared the request with Geoserver demo requests I can see some differences, for example single vs. double quotas. Anybody having an idea if quotas are the the reason for failure, or the flipped axis, or something else?

-Jukka Rahkonen-

Listing from Geoserver console:

Result:
12 syys 14:43:23 INFO [org.geoserver.filters] - Compressing output for mimetype: text/xml
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - First 4 bytes of XML doc are : 3C ('<') 3F ('?') 78 ('x') 6D ('m')
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - Charset detection phase 1. Inferred encoding: UTF-8
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - Charset detection phase 2. Charset in XML declaration is `null`.
12 syys 14:59:56 DEBUG [org.vfny.geoserver.requests] - Trying to create reader basing on existing charset information: `UTF-8`.
12 syys 14:59:56 DEBUG [org.geoserver.ows] - Raw XML request starts with: <?xml version='1.0' encoding='ISO-8859-1'?><wfs:Transaction version='1.1.0'
service='WFS' xmlns:gml='http://www.opengis.net/gml’ xmlns:ogc='http://www.opengis.net/ogc’ xmlns:wfs='http://www.opengis.net/wfs’ xmlns:xsi='http://w
ww.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://www.opengis.net/wfs/1.1.0/WFS-transaction.xsd’ xmlns:topp='http://www.openplans.org/topp
' ><wfs:Insert handle='insert1' idgen='GenerateNew' ><topp:states><topp:the_geom><gml:Surface srsName='urn:x-ogc:def:crs:EPSG:6.11.2:4326'>
<gml:patches>
<gml:PolygonPatch>
<gml:exterior><gml:LinearRing><gml:posList srsDimension='2' count='4'>29.422823762810733 -71.86195768805085 36.22812243286723 -70.16063302053672 31.12
414843032486 -76.6256667570904 29.422823762810733 -71.86195768805085</gml:posList></gml:LinearRing></gml:exterior></gml:PolygonPatch>
</gml:patches>
</gml:Surface></topp:the_geom></topp:states></wfs:Insert></wfs:Transaction>

12 syys 14:59:56 WARN [org.geoserver.ows] -
java.lang.ArrayIndexOutOfBoundsException: 1
        at org.geotools.xml.impl.ParserHandler.startElement(ParserHandler.java:261)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(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.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.geotools.xml.Parser.parse(Parser.java:185)
        at org.geoserver.wfs.xml.v1_1_0.WfsXmlReader.read(WfsXmlReader.java:78)
        at org.geoserver.ows.Dispatcher.parseRequestXML(Dispatcher.java:1072)
        at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:389)
        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)
        at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:684)
        at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:625)
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392)
        at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:357)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1054)
        at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.geoserver.filters.ReverseProxyFilter.doFilter(ReverseProxyFilter.java:170)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:73)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:47)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:264)
        at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107)
        at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:110)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:178)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:229)
        at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
        at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148)
        at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:358)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:453)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
        at org.mortbay.jetty.Server.handle(Server.java:303)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:320)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Justin Deoliveira
Software Engineer, OpenGeo
http://opengeo.org

Hi Justin,

I made first just a visual check, but when I had a closer look at the States shapefile it really did contain a new row - an empty geometry of type multipolygon. I will repeat my test on Monday.

-Jukka-

Justin Deoliveira wrote:

Hi Jukka,

That response does indeed indicate a successful insert, congrats. But

you say you can't see the new polygon in the shapefile? Curious.. how
did you verify this. Did you do a count on the number of rows? Or just a
visual inspection?

Rahkonen Jukka wrote:

Hi,

I edited the insert request as you suggested and it lead to this response:

<wfs:TransactionResponse version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
?
<wfs:TransactionSummary>
<wfs:totalInserted>1</wfs:totalInserted>
<wfs:totalUpdated>0</wfs:totalUpdated>
<wfs:totalDeleted>0</wfs:totalDeleted>
</wfs:TransactionSummary>
<wfs:TransactionResults/>
?
<wfs:InsertResults>
?
<wfs:Feature handle="insert1">
<ogc:FeatureId fid="new0"/>
</wfs:Feature>
</wfs:InsertResults>
</wfs:TransactionResponse>

Does this mean I have done my first successful WFS 1.1.0 insert transaction? The new polygon for sure is not now in the states shapefile, but that may be another story.

-Jukka Rahkonen-

Hi Jukka,

Looks like you are making progress! If you include the modified transaction request I will gladly look it over to see if i spot any issues. And if it works against the states layer i will gladly run it over here to see what i get.

-Justin

Rahkonen Jukka wrote:

Hi Justin,

I made first just a visual check, but when I had a closer look at the States shapefile it really did contain a new row - an empty geometry of type multipolygon. I will repeat my test on Monday.

-Jukka-

Justin Deoliveira wrote:

Hi Jukka,

That response does indeed indicate a successful insert, congrats. But

you say you can't see the new polygon in the shapefile? Curious.. how did you verify this. Did you do a count on the number of rows? Or just a visual inspection?

Rahkonen Jukka wrote:

Hi,

I edited the insert request as you suggested and it lead to this response:

<wfs:TransactionResponse version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
?
<wfs:TransactionSummary>
<wfs:totalInserted>1</wfs:totalInserted>
<wfs:totalUpdated>0</wfs:totalUpdated>
<wfs:totalDeleted>0</wfs:totalDeleted>
</wfs:TransactionSummary>
<wfs:TransactionResults/>
?
<wfs:InsertResults>
?
<wfs:Feature handle="insert1">
<ogc:FeatureId fid="new0"/>
</wfs:Feature>
</wfs:InsertResults>
</wfs:TransactionResponse>
Does this mean I have done my first successful WFS 1.1.0 insert transaction? The new polygon for sure is not now in the states shapefile, but that may be another story.
-Jukka Rahkonen-

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

Hi,

My progress is not very amazing. I have now upgraded GeoServer to 1.7.0 RC3 and received a new version of WFS-T 1.1.0 client. I am trying to insert a new feature into States layer. Somehow the request seems to be accepted by Geoserver but it does never go to the end but stops to phase where Geoserver shows message:
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use featureValidation to check contents of insert

The request and messages captured from console follows.

-Jukka Rahkonen-

06 loka 14:52:37 DEBUG [org.geoserver.ows] - Raw XML request starts with: <?xml version='1.0' encoding='ISO-8859-1'?><wfs:Transaction version='1.1.0' service='WFS' xmlns:gml='http://www.opengis.net/gml’ xmlns:ogc='http://www.opengis.net/ogc’ xmlns:wfs='http://www.opengis.net/wfs
xmlns:topp='http://www.openplans.org/topp’ ><wfs:Insert handle='insert1' idgen='GenerateNew' ><topp:states><topp:the_geom><gml:Surface srsName='urn:x-ogc:def:crs:EPSG:4326'>
<gml:patches>
<gml:PolygonPatch>
<gml:exterior><gml:LinearRing><gml:posList srsDimension='2' count='4'>45.41527563744351 -80.36858102562147 48.81792497247176 -81.21924335937854 47.45686523846045 -84.45176022765537 45.41527563744351 -80.36858102562147</gml:posList></gml:LinearRing></gml:exterior></gml:PolygonPatch>
</gml:patches>
</gml:Surface></topp:the_geom></topp:states></wfs:Insert></wfs:Transaction>
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Locating FeatureSource uri:'http://www.openplans.org/topp’ name:'states'
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - located FeatureType w/ typeRef 'states_shapefile:states' and elementName '{http://www.openplans.org/topp\}states'
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Transasction Insert:net.opengis.wfs.impl.InsertElementTypeImpl@anonymised.com (feature: [org.geotools.feature.simple.SimpleFeatureImpl@anonymised.com], handle: insert1, idgen: GenerateNew, inputFormat: <unset>, srsName: null)
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use featureValidation to check contents of insert

________________________________

Lähettäjä: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Lähetetty: ma 22.9.2008 18:32
Vastaanottaja: Rahkonen Jukka
Kopio: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] WFS-T insert failure

Hi Jukka,

Looks like you are making progress! If you include the modified
transaction request I will gladly look it over to see if i spot any
issues. And if it works against the states layer i will gladly run it
over here to see what i get.

-Justin

Rahkonen Jukka wrote:

Hi Justin,

I made first just a visual check, but when I had a closer look at the States shapefile it really did contain a new row - an empty geometry of type multipolygon. I will repeat my test on Monday.

-Jukka-

Justin Deoliveira wrote:

Hi Jukka,

That response does indeed indicate a successful insert, congrats. But

you say you can't see the new polygon in the shapefile? Curious.. how
did you verify this. Did you do a count on the number of rows? Or just a
visual inspection?

Rahkonen Jukka wrote:

Hi,

I edited the insert request as you suggested and it lead to this response:

<wfs:TransactionResponse version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
?
<wfs:TransactionSummary>
<wfs:totalInserted>1</wfs:totalInserted>
<wfs:totalUpdated>0</wfs:totalUpdated>
<wfs:totalDeleted>0</wfs:totalDeleted>
</wfs:TransactionSummary>
<wfs:TransactionResults/>
?
<wfs:InsertResults>
?
<wfs:Feature handle="insert1">
<ogc:FeatureId fid="new0"/>
</wfs:Feature>
</wfs:InsertResults>
</wfs:TransactionResponse>

Does this mean I have done my first successful WFS 1.1.0 insert transaction? The new polygon for sure is not now in the states shapefile, but that may be another story.

-Jukka Rahkonen-

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

Hi developers,

I am beginning to think that there must be something seriously rotten in the OGC Web Feature Service standard. So far I haven't found two pieces of software which have understood the standard in a similar way at least when it comes to transactions. Perhaps FOSS GIS folks could leave OGC to flip their axis and start making own feature service that works? Or are there already some commonly used open alternatives for WFS-T?

-Jukka Rahkonen-

I’m successfully using openlayers, geoserver 1.7.0 RC-something and ArcSDE 9.2 as backend for insert, update and delete transactions :wink:

Actually I have written some of the WFS-communication myself, since the WFS stuff in openlayers is only just almost done yet. But the point is - it works.

I won’t be the first to say WFS isn’t the greatest standard ever - but implying that no combination of software understands it in a similar way would’t be doing it justice.

/Björn

On Mon, Oct 6, 2008 at 4:07 PM, Rahkonen Jukka <Jukka.Rahkonen@…486…> wrote:

Hi developers,

I am beginning to think that there must be something seriously rotten in the OGC Web Feature Service standard. So far I haven’t found two pieces of software which have understood the standard in a similar way at least when it comes to transactions. Perhaps FOSS GIS folks could leave OGC to flip their axis and start making own feature service that works? Or are there already some commonly used open alternatives for WFS-T?

-Jukka Rahkonen-


This SF.Net email is sponsored by the Moblin Your Move Developer’s challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi,

Sorry, temporary frustration hit me. How about if I say that it is hard to find well featured GIS clients which can do WFS-T version 1.1.0 transactions against both Geoserver and deegree out-of-the-box?

-Jukka-

Björn Harrtell wrote:

I'm successfully using openlayers, geoserver 1.7.0 RC-something and ArcSDE

9.2 as backend for insert, update and delete transactions :wink:

Actually I have written some of the WFS-communication myself, since the WFS

stuff in openlayers is only just almost done yet. But the point is - it
works.

I won't be the first to say WFS isn't the greatest standard ever - but

implying that no combination of software understands it in a similar way
would't be doing it justice.

/Björn

On Mon, Oct 6, 2008 at 4:07 PM, Rahkonen Jukka <Jukka.Rahkonen@anonymised.com>wrote:

Hi developers,

I am beginning to think that there must be something seriously rotten in
the OGC Web Feature Service standard. So far I haven't found two pieces of
software which have understood the standard in a similar way at least when
it comes to transactions. Perhaps FOSS GIS folks could leave OGC to flip
their axis and start making own feature service that works? Or are there
already some commonly used open alternatives for WFS-T?

-Jukka Rahkonen-

Without even knowing I would say yes.

Regarding alternatives to WFS, look here http://www.featureserver.org for an interesting concept using REST for the transactional interface supporting several data formats.

/Björn

On Mon, Oct 6, 2008 at 6:52 PM, Rahkonen Jukka <Jukka.Rahkonen@…486…> wrote:

Hi,

Sorry, temporary frustration hit me. How about if I say that it is hard to find well featured GIS clients which can do WFS-T version 1.1.0 transactions against both Geoserver and deegree out-of-the-box?

-Jukka-

Björn Harrtell wrote:

I’m successfully using openlayers, geoserver 1.7.0 RC-something and ArcSDE
9.2 as backend for insert, update and delete transactions :wink:

Actually I have written some of the WFS-communication myself, since the WFS
stuff in openlayers is only just almost done yet. But the point is - it
works.

I won’t be the first to say WFS isn’t the greatest standard ever - but
implying that no combination of software understands it in a similar way
would’t be doing it justice.

/Björn

On Mon, Oct 6, 2008 at 4:07 PM, Rahkonen Jukka <Jukka.Rahkonen@…486…>wrote:

Hi developers,

I am beginning to think that there must be something seriously rotten in
the OGC Web Feature Service standard. So far I haven’t found two pieces of
software which have understood the standard in a similar way at least when
it comes to transactions. Perhaps FOSS GIS folks could leave OGC to flip
their axis and start making own feature service that works? Or are there
already some commonly used open alternatives for WFS-T?

-Jukka Rahkonen-

Thanks a lot for the interesting link. Unfortunately, because of http://www.ec-gis.org/inspire/ I fear we need to go on with WFS.

-Jukka-

Lähettäjä: Björn Harrtell wrote:

Without even knowing I would say yes.

Regarding alternatives to WFS, look here http://www.featureserver.org for an
interesting concept using REST for the transactional interface supporting
several data formats.

/Björn

On Mon, Oct 6, 2008 at 6:52 PM, Rahkonen Jukka <Jukka.Rahkonen@anonymised.com>wrote:

Hi,

Sorry, temporary frustration hit me. How about if I say that it is hard to
find well featured GIS clients which can do WFS-T version 1.1.0 transactions
against both Geoserver and deegree out-of-the-box?

-Jukka-

Björn Harrtell wrote:

> I'm successfully using openlayers, geoserver 1.7.0 RC-something and
ArcSDE
9.2 as backend for insert, update and delete transactions :wink:

> Actually I have written some of the WFS-communication myself, since the
WFS
stuff in openlayers is only just almost done yet. But the point is - it
works.

> I won't be the first to say WFS isn't the greatest standard ever - but
implying that no combination of software understands it in a similar way
would't be doing it justice.

/Björn

On Mon, Oct 6, 2008 at 4:07 PM, Rahkonen Jukka <Jukka.Rahkonen@anonymised.com
>wrote:

>> Hi developers,
>
>> I am beginning to think that there must be something seriously rotten in
>> the OGC Web Feature Service standard. So far I haven't found two pieces
of
>> software which have understood the standard in a similar way at least
when
>> it comes to transactions. Perhaps FOSS GIS folks could leave OGC to
flip
>> their axis and start making own feature service that works? Or are
there
>> already some commonly used open alternatives for WFS-T?
>
> -Jukka Rahkonen-
>

Hi Jukka,

I am sorry your experience with wfs has been sub optimal. From someone who has implemented wfs i feel your pain. However, moving forward. I ran your transaction request and I think i found the issue. It is the fact the request uses gml:Surface, as opposed to gml:MultiPolygon. Even though GeoServer is the reference implementation of wfs 1.1, it does not do curves and surfaces, only very very simple cases in which a regular Polygon or LineString can be encoded with Surface and Curve respectively. And this actually only means that GeoServer parses MultiSurface and MultiCurve.

Regardless, if you convert the transaction below to MultiPolygon, you will hopefully see the correct result. I apologize for the confusion, GeoServer instead of just ignoring the Surface, should really throw an exception stating that it is not supported.

-Justin

Rahkonen Jukka wrote:

Hi,
My progress is not very amazing. I have now upgraded GeoServer to 1.7.0 RC3 and received a new version of WFS-T 1.1.0 client. I am trying to insert a new feature into States layer. Somehow the request seems to be accepted by Geoserver but it does never go to the end but stops to phase where Geoserver shows message:
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use featureValidation to check contents of insert
The request and messages captured from console follows.
-Jukka Rahkonen-
06 loka 14:52:37 DEBUG [org.geoserver.ows] - Raw XML request starts with: <?xml version='1.0' encoding='ISO-8859-1'?><wfs:Transaction version='1.1.0' service='WFS' xmlns:gml='http://www.opengis.net/gml’ xmlns:ogc='http://www.opengis.net/ogc’ xmlns:wfs='http://www.opengis.net/wfs
xmlns:topp='http://www.openplans.org/topp’ ><wfs:Insert handle='insert1' idgen='GenerateNew' ><topp:states><topp:the_geom><gml:Surface srsName='urn:x-ogc:def:crs:EPSG:4326'>
<gml:patches>
<gml:PolygonPatch>
<gml:exterior><gml:LinearRing><gml:posList srsDimension='2' count='4'>45.41527563744351 -80.36858102562147 48.81792497247176 -81.21924335937854 47.45686523846045 -84.45176022765537 45.41527563744351 -80.36858102562147</gml:posList></gml:LinearRing></gml:exterior></gml:PolygonPatch>
</gml:patches>
</gml:Surface></topp:the_geom></topp:states></wfs:Insert></wfs:Transaction>
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Locating FeatureSource uri:'http://www.openplans.org/topp’ name:'states'
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - located FeatureType w/ typeRef 'states_shapefile:states' and elementName '{http://www.openplans.org/topp\}states'
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Transasction Insert:net.opengis.wfs.impl.InsertElementTypeImpl@anonymised.com (feature: [org.geotools.feature.simple.SimpleFeatureImpl@anonymised.com], handle: insert1, idgen: GenerateNew, inputFormat: <unset>, srsName: null)
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use featureValidation to check contents of insert

________________________________

Lähettäjä: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Lähetetty: ma 22.9.2008 18:32
Vastaanottaja: Rahkonen Jukka
Kopio: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] WFS-T insert failure

Hi Jukka,

Looks like you are making progress! If you include the modified
transaction request I will gladly look it over to see if i spot any
issues. And if it works against the states layer i will gladly run it
over here to see what i get.

-Justin

Rahkonen Jukka wrote:

Hi Justin,

I made first just a visual check, but when I had a closer look at the States shapefile it really did contain a new row - an empty geometry of type multipolygon. I will repeat my test on Monday.

-Jukka-

Justin Deoliveira wrote:

Hi Jukka,
That response does indeed indicate a successful insert, congrats. But

you say you can't see the new polygon in the shapefile? Curious.. how
did you verify this. Did you do a count on the number of rows? Or just a
visual inspection?

Rahkonen Jukka wrote:

Hi,
I edited the insert request as you suggested and it lead to this response:
<wfs:TransactionResponse version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
?
<wfs:TransactionSummary>
<wfs:totalInserted>1</wfs:totalInserted>
<wfs:totalUpdated>0</wfs:totalUpdated>
<wfs:totalDeleted>0</wfs:totalDeleted>
</wfs:TransactionSummary>
<wfs:TransactionResults/>
?
<wfs:InsertResults>
?
<wfs:Feature handle="insert1">
<ogc:FeatureId fid="new0"/>
</wfs:Feature>
</wfs:InsertResults>
</wfs:TransactionResponse>

Does this mean I have done my first successful WFS 1.1.0 insert transaction? The new polygon for sure is not now in the states shapefile, but that may be another story.

-Jukka Rahkonen-

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

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

Justin Deoliveira wrote:

Fine, now I understand the situation a bit but not much better. It was the first time I met those MultiSufaces and surfaceMembers. But I do not still understand which one is blame to that the transaction is not successful, GeoServer or the the newest OpenJUMP WFS-plugin that I use as a test client. GetCapabilities is telling about states feature type that it is of MultiSurfacePropertyType and I put here below what GeoServer gives if I send it getFeature for Colorado. I can see that it is of type gml:MultiSurface that has gml:Polygon as a gml:surfaceMember. Should a well behaving, standard compliant WFS client now understand from the fraction "gml:Polygon" or something else that it should be sending back to the server just MultiPolygons and absolutely not Surfaces?

-Jukka Rahkonen-

Here is Colorado in GeoServer WFS 1.1.0 language but without all the coordinates.

<?xml version="1.0" encoding="UTF-8"?>
<wfs:FeatureCollection numberOfFeatures="1" timeStamp="2008-10-07T08:57:43.625+03:00" xsi:schemaLocation="http://www.openplans.org/topp http://localhost:8080/geoserver/wfs?service=WFS&amp;version=1.1.0&amp;request=DescribeFeatureType&amp;typeName=topp:states http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot; xmlns:ogc="http://www.opengis.net/ogc&quot; xmlns:tiger="http://www.census.gov" xmlns:wfs="http://www.opengis.net/wfs&quot; xmlns:topp="http://www.openplans.org/topp&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:sf="http://www.openplans.org/spearfish&quot; xmlns:ows="http://www.opengis.net/ows&quot; xmlns:gml="http://www.opengis.net/gml&quot; xmlns:xlink="http://www.w3.org/1999/xlink&quot;&gt;&lt;gml:featureMembers&gt;&lt;topp:states gml:id="states.6"><gml:boundedBy><gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:4326"><gml:lowerCorner>36.988972000000004 -109.055199</gml:lowerCorner><gml:upperCorner>41.00341 -102.036758</gml:upperCorner></gml:Envelope></gml:boundedBy><topp:the_geom><gml:MultiSurface srsName="urn:x-ogc:def:crs:EPSG:4326"><gml:surfaceMember><gml:Polygon><gml:exterior><gml:LinearRing><gml:posList>37.641459999999995 -102.043999 ...37.641459999999995 -102.043999</gml:posList>

</gml:LinearRing></gml:exterior></gml:Polygon></gml:surfaceMember></gml:MultiSurface></topp:the_geom><topp:STATE_NAME>Colorado</topp:STATE_NAME><topp:STATE_FIPS>08</topp:STATE_FIPS><topp:SUB_REGION>Mtn</topp:SUB_REGION><topp:STATE_ABBR>CO</topp:STATE_ABBR><topp:LAND_KM>268659.501</topp:LAND_KM><topp:WATER_KM>960.364</topp:WATER_KM><topp:PERSONS>3294394.0</topp:PERSONS><topp:FAMILIES>854214.0</topp:FAMILIES><topp:HOUSHOLD>1282489.0</topp:HOUSHOLD><topp:MALE>1631295.0</topp:MALE><topp:FEMALE>1663099.0</topp:FEMALE><topp:WORKERS>1233023.0</topp:WORKERS><topp:DRVALONE>1216639.0</topp:DRVALONE><topp:CARPOOL>210274.0</topp:CARPOOL><topp:PUBTRANS>46983.0</topp:PUBTRANS><topp:EMPLOYED>1633281.0</topp:EMPLOYED><topp:UNEMPLOY>99438.0</topp:UNEMPLOY><topp:SERVICE>421079.0</topp:SERVICE><topp:MANUAL>181760.0</topp:MANUAL><topp:P_MALE>0.495</topp:P_MALE><topp:P_FEMALE>0.505</topp:P_FEMALE><topp:SAMP_POP>512677.0</topp:SAMP_POP></topp:states></gml:featureMembers></wfs:FeatureCollection>

Hi Jukka,

I am sorry your experience with wfs has been sub optimal.
From someone who has implemented wfs i feel your pain.
However, moving forward. I ran your transaction request and I
think i found the issue. It is the fact the request uses
gml:Surface, as opposed to gml:MultiPolygon. Even though
GeoServer is the reference implementation of wfs 1.1, it does
not do curves and surfaces, only very very simple cases in
which a regular Polygon or LineString can be encoded with
Surface and Curve respectively. And this actually only means
that GeoServer parses MultiSurface and MultiCurve.

Regardless, if you convert the transaction below to
MultiPolygon, you will hopefully see the correct result. I
apologize for the confusion, GeoServer instead of just
ignoring the Surface, should really throw an exception
stating that it is not supported.

-Justin

Rahkonen Jukka wrote:
> Hi,
>
> My progress is not very amazing. I have now upgraded
GeoServer to 1.7.0 RC3 and received a new version of WFS-T
1.1.0 client. I am trying to insert a new feature into
States layer. Somehow the request seems to be accepted by
Geoserver but it does never go to the end but stops to phase
where Geoserver shows message:
> 06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use
featureValidation to
> check contents of insert
>
> The request and messages captured from console follows.
>
> -Jukka Rahkonen-
>
> 06 loka 14:52:37 DEBUG [org.geoserver.ows] - Raw XML
request starts with: <?xml version='1.0'
encoding='ISO-8859-1'?><wfs:Transaction version='1.1.0'
service='WFS' xmlns:gml='http://www.opengis.net/gml
xmlns:ogc='http://www.opengis.net/ogc
xmlns:wfs='http://www.opengis.net/wfs
> xmlns:topp='http://www.openplans.org/topp’ ><wfs:Insert
> handle='insert1' idgen='GenerateNew'
> ><topp:states><topp:the_geom><gml:Surface
> srsName='urn:x-ogc:def:crs:EPSG:4326'>
> <gml:patches>
> <gml:PolygonPatch>
> <gml:exterior><gml:LinearRing><gml:posList srsDimension='2'
> count='4'>45.41527563744351 -80.36858102562147 48.81792497247176
> -81.21924335937854 47.45686523846045 -84.45176022765537
> 45.41527563744351
>
-80.36858102562147</gml:posList></gml:LinearRing></gml:exterior></gml:
> PolygonPatch>
> </gml:patches>
>
</gml:Surface></topp:the_geom></topp:states></wfs:Insert></wfs:Transac
> tion>
> 06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Locating
FeatureSource uri:'http://www.openplans.org/topp’ name:'states'
> 06 loka 14:52:37 DEBUG [org.geoserver.wfs] - located
FeatureType w/ typeRef 'states_shapefile:states' and
elementName '{http://www.openplans.org/topp\}states'
> 06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Transasction
> Insert:net.opengis.wfs.impl.InsertElementTypeImpl@anonymised.com (feature:
> [org.geotools.feature.simple.SimpleFeatureImpl@anonymised.com], handle:
> insert1, idgen: GenerateNew, inputFormat: <unset>, srsName: null)
> 06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use
featureValidation to
> check contents of insert
>
>
>
> ________________________________
>
> Lähettäjä: Justin Deoliveira [mailto:jdeolive@anonymised.com]
> Lähetetty: ma 22.9.2008 18:32
> Vastaanottaja: Rahkonen Jukka
> Kopio: geoserver-users@lists.sourceforge.net
> Aihe: Re: [Geoserver-users] WFS-T insert failure
>
>
>
> Hi Jukka,
>
> Looks like you are making progress! If you include the modified
> transaction request I will gladly look it over to see if i spot any
> issues. And if it works against the states layer i will
gladly run it
> over here to see what i get.
>
> -Justin
>
> Rahkonen Jukka wrote:
>> Hi Justin,
>>
>> I made first just a visual check, but when I had a closer
look at the States shapefile it really did contain a new row
- an empty geometry of type multipolygon. I will repeat my
test on Monday.
>>
>> -Jukka-
>>
>>
>> Justin Deoliveira wrote:
>>
>>> Hi Jukka,
>>> That response does indeed indicate a successful insert, congrats.
>>> But
>> you say you can't see the new polygon in the shapefile?
Curious.. how
>> did you verify this. Did you do a count on the number of rows? Or
>> just a visual inspection?
>>
>>> Rahkonen Jukka wrote:
>>>> Hi,
>>>> I edited the insert request as you suggested and it lead
to this response:
>>>> <wfs:TransactionResponse version="1.1.0"
>>>> xsi:schemaLocation="http://www.opengis.net/wfs
>>>> http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
>>>> ?
>>>> <wfs:TransactionSummary>
>>>> <wfs:totalInserted>1</wfs:totalInserted>
>>>> <wfs:totalUpdated>0</wfs:totalUpdated>
>>>> <wfs:totalDeleted>0</wfs:totalDeleted>
>>>> </wfs:TransactionSummary>
>>>> <wfs:TransactionResults/>
>>>> ?
>>>> <wfs:InsertResults>
>>>> ?
>>>> <wfs:Feature handle="insert1">
>>>> <ogc:FeatureId fid="new0"/>
>>>> </wfs:Feature>
>>>> </wfs:InsertResults>
>>>> </wfs:TransactionResponse>
>>>>
>>>> Does this mean I have done my first successful WFS 1.1.0
insert transaction? The new polygon for sure is not now in
the states shapefile, but that may be another story.
>>>>
>>>> -Jukka Rahkonen-
>>
>>
---------------------------------------------------------------------
>> ---- This SF.Net email is sponsored by the Moblin Your Move
>> Developer's challenge Build the coolest Linux based
applications with
>> Moblin SDK & win great prizes Grand prize is a trip for two to an
>> Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Geoserver-users mailing list
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org/&gt;
Enterprise support
> for open source geospatial.
>
>

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

Hi Jukka,

It is probably the combination of a couple of things. First what I think is happening is that the transaction itself is a success... it is just occurring with no geometry which is why you never see the feature.

During the wfs 1.1 test bed in ows4 we definitely argued against making use of surfaces and curves as defaults for the server. But... there was push back to that because in GML3 multi polygon and multi line string are deprecated.

So we had to fake it... we only parse those objects if we can actually represent them as multi polygons and multi line strings. Which means they cannot have a regular surface or curve within them. Which in GML3 is legal because Polygon and Surface are in the same subsitution group, same story for LineString and curve.

So to answer your question, sending MultiSurface and MultiCurve to GeoServer is ok, however they have to contain only Polygons and LineString's. Sending anything with a Surface or Curve in it will fail. And indeed any compliant WFS 1.1 server should allow this as well. even if they do indeed support full blown Surface and Curve, since it is perfectly legal in terms of GML.

Hope that sheds some light.

-Justin

Rahkonen Jukka wrote:

Justin Deoliveira wrote:

Fine, now I understand the situation a bit but not much better. It was the first time I met those MultiSufaces and surfaceMembers. But I do not still understand which one is blame to that the transaction is not successful, GeoServer or the the newest OpenJUMP WFS-plugin that I use as a test client. GetCapabilities is telling about states feature type that it is of MultiSurfacePropertyType and I put here below what GeoServer gives if I send it getFeature for Colorado. I can see that it is of type gml:MultiSurface that has gml:Polygon as a gml:surfaceMember. Should a well behaving, standard compliant WFS client now understand from the fraction "gml:Polygon" or something else that it should be sending back to the server just MultiPolygons and absolutely not Surfaces?

-Jukka Rahkonen-

Here is Colorado in GeoServer WFS 1.1.0 language but without all the coordinates.

<?xml version="1.0" encoding="UTF-8"?>
<wfs:FeatureCollection numberOfFeatures="1" timeStamp="2008-10-07T08:57:43.625+03:00" xsi:schemaLocation="http://www.openplans.org/topp http://localhost:8080/geoserver/wfs?service=WFS&amp;version=1.1.0&amp;request=DescribeFeatureType&amp;typeName=topp:states http://www.opengis.net/wfs http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot; xmlns:ogc="http://www.opengis.net/ogc&quot; xmlns:tiger="http://www.census.gov" xmlns:wfs="http://www.opengis.net/wfs&quot; xmlns:topp="http://www.openplans.org/topp&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:sf="http://www.openplans.org/spearfish&quot; xmlns:ows="http://www.opengis.net/ows&quot; xmlns:gml="http://www.opengis.net/gml&quot; xmlns:xlink="http://www.w3.org/1999/xlink&quot;&gt;&lt;gml:featureMembers&gt;&lt;topp:states gml:id="states.6"><gml:boundedBy><gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:4326"><gml:lowerCorner>36.988972000000004 -109.055199</gml:lowerCorner><gml:upperCorner>41.00341 -102.036758</gml:upperCorner></gml:Envelope></gml:bounde

dBy><topp:the_geom><gml:MultiSurface srsName="urn:x-ogc:def:crs:EPSG:4326"><gml:surfaceMember><gml:Polygon><gml:exterior><gml:LinearRing><gml:posList>37.641459999999995 -102.043999 ...37.641459999999995 -102.043999</gml:posList>

</gml:LinearRing></gml:exterior></gml:Polygon></gml:surfaceMember></gml:MultiSurface></topp:the_geom><topp:STATE_NAME>Colorado</topp:STATE_NAME><topp:STATE_FIPS>08</topp:STATE_FIPS><topp:SUB_REGION>Mtn</topp:SUB_REGION><topp:STATE_ABBR>CO</topp:STATE_ABBR><topp:LAND_KM>268659.501</topp:LAND_KM><topp:WATER_KM>960.364</topp:WATER_KM><topp:PERSONS>3294394.0</topp:PERSONS><topp:FAMILIES>854214.0</topp:FAMILIES><topp:HOUSHOLD>1282489.0</topp:HOUSHOLD><topp:MALE>1631295.0</topp:MALE><topp:FEMALE>1663099.0</topp:FEMALE><topp:WORKERS>1233023.0</topp:WORKERS><topp:DRVALONE>1216639.0</topp:DRVALONE><topp:CARPOOL>210274.0</topp:CARPOOL><topp:PUBTRANS>46983.0</topp:PUBTRANS><topp:EMPLOYED>1633281.0</topp:EMPLOYED><topp:UNEMPLOY>99438.0</topp:UNEMPLOY><topp:SERVICE>421079.0</topp:SERVICE><topp:MANUAL>181760.0</topp:MANUAL><topp:P_MALE>0.495</topp:P_MALE><topp:P_FEMALE>0.505</topp:P_FEMALE><topp:SAMP_POP>512677.0</topp:SAMP_POP></topp:states></gml:featureMembers></wfs:FeatureCollection>

Hi Jukka,

I am sorry your experience with wfs has been sub optimal.
From someone who has implemented wfs i feel your pain.
However, moving forward. I ran your transaction request and I
think i found the issue. It is the fact the request uses
gml:Surface, as opposed to gml:MultiPolygon. Even though
GeoServer is the reference implementation of wfs 1.1, it does
not do curves and surfaces, only very very simple cases in
which a regular Polygon or LineString can be encoded with
Surface and Curve respectively. And this actually only means
that GeoServer parses MultiSurface and MultiCurve.

Regardless, if you convert the transaction below to
MultiPolygon, you will hopefully see the correct result. I
apologize for the confusion, GeoServer instead of just
ignoring the Surface, should really throw an exception
stating that it is not supported.

-Justin

Rahkonen Jukka wrote:

Hi,

My progress is not very amazing. I have now upgraded

GeoServer to 1.7.0 RC3 and received a new version of WFS-T
1.1.0 client. I am trying to insert a new feature into
States layer. Somehow the request seems to be accepted by
Geoserver but it does never go to the end but stops to phase
where Geoserver shows message:

06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use

featureValidation to

check contents of insert

The request and messages captured from console follows.

-Jukka Rahkonen-

06 loka 14:52:37 DEBUG [org.geoserver.ows] - Raw XML

request starts with: <?xml version='1.0'
encoding='ISO-8859-1'?><wfs:Transaction version='1.1.0'
service='WFS' xmlns:gml='http://www.opengis.net/gml
xmlns:ogc='http://www.opengis.net/ogc
xmlns:wfs='http://www.opengis.net/wfs

xmlns:topp='http://www.openplans.org/topp’ ><wfs:Insert
handle='insert1' idgen='GenerateNew'

<topp:states><topp:the_geom><gml:Surface

srsName='urn:x-ogc:def:crs:EPSG:4326'>
<gml:patches>
<gml:PolygonPatch>
<gml:exterior><gml:LinearRing><gml:posList srsDimension='2'
count='4'>45.41527563744351 -80.36858102562147 48.81792497247176
-81.21924335937854 47.45686523846045 -84.45176022765537
45.41527563744351

-80.36858102562147</gml:posList></gml:LinearRing></gml:exterior></gml:

PolygonPatch>
</gml:patches>

</gml:Surface></topp:the_geom></topp:states></wfs:Insert></wfs:Transac

tion>
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Locating

FeatureSource uri:'http://www.openplans.org/topp’ name:'states'

06 loka 14:52:37 DEBUG [org.geoserver.wfs] - located

FeatureType w/ typeRef 'states_shapefile:states' and
elementName '{http://www.openplans.org/topp\}states'

06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Transasction
Insert:net.opengis.wfs.impl.InsertElementTypeImpl@anonymised.com (feature:
[org.geotools.feature.simple.SimpleFeatureImpl@anonymised.com], handle:
insert1, idgen: GenerateNew, inputFormat: <unset>, srsName: null)
06 loka 14:52:37 DEBUG [org.geoserver.wfs] - Use

featureValidation to

check contents of insert

________________________________

Lähettäjä: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Lähetetty: ma 22.9.2008 18:32
Vastaanottaja: Rahkonen Jukka
Kopio: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] WFS-T insert failure

Hi Jukka,

Looks like you are making progress! If you include the modified
transaction request I will gladly look it over to see if i spot any
issues. And if it works against the states layer i will

gladly run it

over here to see what i get.

-Justin

Rahkonen Jukka wrote:

Hi Justin,

I made first just a visual check, but when I had a closer

look at the States shapefile it really did contain a new row
- an empty geometry of type multipolygon. I will repeat my
test on Monday.

-Jukka-

Justin Deoliveira wrote:

Hi Jukka,
That response does indeed indicate a successful insert, congrats.
But

you say you can't see the new polygon in the shapefile?

Curious.. how

did you verify this. Did you do a count on the number of rows? Or
just a visual inspection?

Rahkonen Jukka wrote:

Hi,
I edited the insert request as you suggested and it lead

to this response:

<wfs:TransactionResponse version="1.1.0"
xsi:schemaLocation="http://www.opengis.net/wfs
http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd&quot;&gt;
?
<wfs:TransactionSummary>
<wfs:totalInserted>1</wfs:totalInserted>
<wfs:totalUpdated>0</wfs:totalUpdated>
<wfs:totalDeleted>0</wfs:totalDeleted>
</wfs:TransactionSummary>
<wfs:TransactionResults/>
?
<wfs:InsertResults>
?
<wfs:Feature handle="insert1">
<ogc:FeatureId fid="new0"/>
</wfs:Feature>
</wfs:InsertResults>
</wfs:TransactionResponse>

Does this mean I have done my first successful WFS 1.1.0

insert transaction? The new polygon for sure is not now in
the states shapefile, but that may be another story.

-Jukka Rahkonen-

---------------------------------------------------------------------

---- This SF.Net email is sponsored by the Moblin Your Move
Developer's challenge Build the coolest Linux based

applications with

Moblin SDK & win great prizes Grand prize is a trip for two to an
Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Justin Deoliveira
OpenGeo - http://opengeo.org/&gt;

Enterprise support

for open source geospatial.

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

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