Sam,
your definition of FacilitiesType has the problem I described in my
previous email: it does not respect the property/object encoding rule.
Instead of having a property of type AdministrativeAreasType, to respect
the property/object rule, you should have a property of
Hello again Ben,
I have created my own xsds from ones I found online. I have included type
names in my xsds and I believe that my mapping files are correctly formatted
so I can't see what's wrong.
I have uploaded the two mapping files and two XSDs to this location:
Sam,
what are the XSD types of Shape and AdministrativeAreas in the schema?
What is the XSD type of Facility? Complex properties must follow the GML
encoding rule, in which each object is contained in a property type so
that both its name and type information can be encoded. Not following
Hi Ben,
Thanks for the response. As you can probably gather, I'm a bit new at this.
OK, so I've changed the namespace in the XSDs and referred to them in the
mapping files and created an extra workspace for the GML 3.2 requirements.
The files load into Geoserver OK.
However, when I try and
Sam,
you can't mix and match GML 3.1.1 and GML 3.2.1 as they have different
namespaces and the types for a feature and all the geometries are
different. If your application schema is GML 3.1.1, it will only work
with GML 3.1.1 requests (WFS 1.1.0). Likewise for GML 3.2.1 (WFS 2.0.0
or WFS
Hi
I have created an app schema for two different feature types, type 1
contains a field of type 2 that is then populated via a mapping file.
However when I do a WFS request with GML 3.1.1, I get:
Edinburgh Castle
Open
Stone
Stone
1
1
3.1987
55.9486
