Dear Sebastian,
please see my answers bellow:
On 08/28/2018 11:22 AM, worldexplorer wrote:
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
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
speci
Hi,
When encoding a complex feature we cannot know at encoding time which
name-spaces will be needed
(a complex feature may chain multiple features from different name-spaces
together), so all the available
name-spaces are added. Is worth noticing that the produced XML document is
valid. This
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, w