Hi Andrea,
I'm running a recent install of 2.12.0
-Gavin
On Mon, Oct 23, 2017 at 11:45 AM, Andrea Aime
wrote:
> Gavin,
> one question, which version of GeoServer are you using?
> Looked through the posts and could not see it.
>
> Cheers
> Andrea
>
> On Fri, Oct 20, 2017 at 7:38 PM, Gavin Medle
Gavin,
one question, which version of GeoServer are you using?
Looked through the posts and could not see it.
Cheers
Andrea
On Fri, Oct 20, 2017 at 7:38 PM, Gavin Medley wrote:
> Hi,
>
> I understand that App Schema enforces GML striping, i.e. “complex types
> are never the direct property of a
Hi Ben and Gavin,
The XMl encoder was relaxed to support this use cases:
https://github.com/geoserver/geoserver/commit/6d110bbf03db683f8a5c59c566bb75d4d1db
So not sure why it is not working, Galvin can you share with us the XML element
that is including the GnssReceiver element and the rela
Gavin,
I do not think that this is a supported mapping pattern. As you note,
this violates the GML object/property "striping" rule. The only reason
you see anything at all is I think because of recent changes to make the
encoder more permissive. The problem is that the dateInserted property
f
Hi,
I understand that App Schema enforces GML striping, i.e. “complex types are
never the direct property of another complex type; they are always
contained in a property type to ensure that their type is encoded in a
surrounding element.” However, in GeodesyML, there are complex types (
geo:GnssR
