Dear Nuno Oliveira,
thank you for the answer. It's quite interesting that complex features have
this behaviour. Never thought about the fact, that the needed name-spaces
are uncertain at the point of the encoding time.
To summarize, it affects all encodings of complex features and it's not
Dear list,
I've noticed a strange thing in my GetFeature request regarding namespaces
and I don't know exactly why. When I do a GetFeature request on the default
data (e.g. Tasmania state boundaries) of the GeoServer the
header looks pretty normal. All necessary
namespaces are listed. However,
Dear list,
I've installed GeoServer 2.12.1 last winter and running successfully since
that day when working with complex features. I've noticed a lot of progress
this year in the community and seen the latest releases.
I am little bit afraid to upgrade because there are some important
Dear list,
in the past, I've worked with the app schema tutorial data. Simple features
stored in a java properties file which has been converted into complex
features for delivery via WFS.
Now, my data source has changed. I'm working with complex GML features
stored in a GML file which I want to
Hi Sorin,
thank you for your response.
GeoServer - User mailing list wrote
> I could provide more info if you could provide a clearer picture of what
> you are trying to achieve.
Well, my data is in its complexity comparable with the INSPIRE data. It
based on an on object oriented model. All
