Hi,
To answer my own question:
1) changing SurfacePropertyType into GeometryPropertyType in the
schema and creating an empty Geometry does the trick!
2) looking at the code I discovered that the check on existing id's is
done based on the id of the feature NOT on the id of the geometry! I am
I propose a change to WFS behaviour that will have widespread impact on
GeoServer and GeoTools users. In particular, XML consumers that have
grown accustomed to consuming featureMembers may break. However, this
change is necessary to support gml:id uniqueness in complex features.
GeoServer cann
Andrea,
is XSIdRegistry turned off for simple features, for performance and
memory reasons? I recall a discussion ...
Kind regards,
Ben.
On 20/04/10 20:46, Rob van Swol wrote:
> Hi,
> I have a simple GML3 Application schema which I use to encode a
> featurecollection to a gml document. Howeve
Hi,
I have a simple GML3 Application schema which I use to encode a
featurecollection to a gml document. However I do not succeed in
getting duplicate gml:id's in geometry elements to be replaced by
xlink:href attributes. Even worse: duplicate id's are accepted while I
thought that the XSDIdReg
Encoder can actually perfom a single encode, a second will fail
---
Key: GEOT-3047
URL: http://jira.codehaus.org/browse/GEOT-3047
Project: GeoTools
Issue Type: Bug
Compone
FeatureCollection should be encoded with multiple featureMember elements not
one featureMembers element to support xlink:href
-
Key: GEOT-3046
