Ok, I finally figured it out. To add some resolution to this thread here is what I discovered.
I needed to modify the icaoSurfaceForecastReport.xsd to specify the type of aerodromeWxForecast to be a wx:ForecastPropertyType and remove the inner definition as it was merely a duplicate of the wx:ForecastPropertyType. Once that was done, I modified my feature chaining to define the wx:Forecast object as the top level object of the secondary table (as opposed to avwx:aerodromeWxForecast). So, each avwx:TAF contains an avwx:aerodromeWxForecast attribute that is feature linked to the wx:Forecast object. I'm not sure if this will help anyone else in the future, but I hate stumbling across threads like this with no resolution. Thanks again for all the help. Kevin M. Weiss Software Engineer HARRIS IT Services -----Original Message----- From: Weiss, Kevin Sent: Monday, October 06, 2014 11:33 AM To: 'Ben Caradoc-Davies'; geoserver-users@lists.sourceforge.net Subject: RE: [Geoserver-users] WXXM and app-schema plug-in Ben, Sorry for the delay. I tried removing the complexType definition relying solely on the type attribute as you suggested, but the result is still the same. When I change GeoServer to VERBOSE logging I can see that the object appears to be populated correctly, but the WFS response still contains the empty aerodromeWxForecast objects. Is there a validation process that occurs after the document is built up that could be causing this somehow? Attached is the trace log showing the fully populated document. Kevin M. Weiss Software Engineer HARRIS IT Services -----Original Message----- From: Ben Caradoc-Davies [mailto:ben.caradoc-dav...@csiro.au] Sent: Thursday, October 02, 2014 9:31 PM To: Weiss, Kevin; geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] WXXM and app-schema plug-in Kevin, in your schema the aerodromeWxForecast element has both a type attribute and a complexType definition; these are two distinct ways of defining the type of the element and I do not think you can use both. Please try using the type attribute only. Have a look at the TAF element as a guide. Kind regards, Ben. On 02/10/14 21:10, Weiss, Kevin wrote: > I tried adding type="wx:ForecastPropertyType" to the > avwx:aerodromeWxForecast, but the change had no effect. -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre ------------------------------------------------------------------------------ Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
