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 AdministrativeAreasPropertyType which then contains a AdministrativeAreasType. This will allow the correct encoding of your output. See GeometryPropertyType for an example of this pattern.
Note that GeoServer 2.11-beta has a new relaxed encoding support that will permit responses that do not respect the property/object rule: https://osgeo-org.atlassian.net/browse/GEOT-5575 https://osgeo-org.atlassian.net/browse/GEOS-7860 Your mapping for Facility/Shape should work. Your XSD requires this to be a Point. Please check that the database column facilitylocation contains POINT geometries, that they are correct registered in your database, and that the geometries are not NULL. If they are not POINT, you could change the XSD type of Facility/Shape to GeometryPropertyType. Null namespaces are usually caused by missing secondary namespaces. Please see my previous email for a link to the documentation that details how to fix this. Kind regards, Ben. On 27/02/17 21:29, sammeek wrote: > 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: > > http://meekbaa1.miniserver.com/dl/ > > I have included an ID at the appropriate places at the AdministrativeAreas > table seems to work fine when published through Geoserver. > > There is a slight namespace issue when I make a WFS call to Facilities and > the AdministrativeAreas in that it seems to make the namespace null for > whichever I call second. When I call Facilities, the WFS response document > doesn't include both namespaces, but I'm not sure its supposed to. > > Thank you for your continuing assistance. > > Sam > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/Complex-GML-3-1-1-from-App-Schema-tp5309269p5309605.html > Sent from the GeoServer - User mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
