On Thu, Mar 30, 2017 at 1:11 PM, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> Because I know your pain I warn you about another oddity that could make
> you mad: You won't get any warning about only partly successful
> transactions, like attributes are inserted but geometry
Hi,
We are also validating geometries on the client side.
-Jukka-
Deen wrote:
Re: [Geoserver-users] Inserting features not in order with WFS-T
Hi Andrea and Jukka,
Big thanks for your quick responses.
@Andrea: tried your solution with no luck, I might probably design another id
column
Hi Andrea and Jukka,
Big thanks for your quick responses.
@Andrea: tried your solution with no luck, I might probably design another
id column in my table to keep tracking the features as Jukka mentioned
@Jukka: Yes, I agree with you and I've seen the oddity before (can't
remember what ca
you
mad: You won't get any warning about only partly successful transactions, like
attributes are inserted but geometry not and you believe that everything is OK.
-Jukka Rahkonen-
Deen wrote:
Re: [Geoserver-users] Inserting features not in order with WFS-T
Hello all,
Recently I am play
Hi Deen,
yes, it is normal behavior. There is a WFS 1.1 only option (not available
in WFS 1.0, and then removed in WFS 2.0)
that allows to force the server to use the specified ids.
You should be able to add idgen='UseExisting' as an attribute in your
insert element, and if the backend
is a databa
Hello all,
Recently I am playing a lot with GeoServer WFS-T and try to understand it.
What I want to achieve is simple, namely inserting multiple features to a
PostGIS table. However, today I found out that the insertion of features is
not in order, Here is a sample XML request I sent:
http://ww
