[Geoserver-users] WXXM and app-schema plug-in

GeoServer GeoServer User
1

Hello all,

I’m running into an issue attempting to map our DB contents to an avwx:TAF object as defined in the WXXM 1.1.1 schema. I believe the issue is that the WXXM schema defines a 0…n mapping of avwx:TAF to avwx:aerodromeWxForecast objects, but the avwx:aerodromeWxForecast element is defined within the SurfaceForecastReportType rather than as a top-level complexType. When I attempt to use feature chaining to create these sub-elements the result is:

“NoSuchElementException: No top level element found in schemas: {http://www.eurocontrol.int/avwx/1.1}aerodromeWxForecast”.

The WXXM schema in question can be found here.

http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurfaceForecastReport.xsd

Seeing that these schemas are outside of my control is there any workaround I could try that doesn’t require modification of the schema itself?

Thanks,

Kevin M. Weiss

Software Engineer

HARRIS IT Services

2

Kevin,

I checked with feature chaining expert Rini Angreani who confirmed "No element, no mapping."

There is an easy workaround: modify the schema in your app-schema-cache. (The same trick will work with an OASIS Catalog but cache is easiest; I recommend being lazy.) GeoServer app-schema will use the version in the cache and never update it so your changes are safe. Caches are also portable and can be deployed to other instances. If you change the definition in your cache to be compatible with GeoServer app-schema, you can still refer to the canonical schema location in your mapping files and it will be encoded as such in responses. As long as your changes do not change the information model, this is a complete, interoperable solution. The behaviour of schema caching is designed to allow this workaround.

For details on schema resolution, see:
http://docs.geoserver.org/latest/en/user/data/app-schema/app-schema-resolution.html

Kind regards,
Ben.

On 01/10/14 02:24, Weiss, Kevin wrote:

Hello all,

I’m running into an issue attempting to map our DB contents to an
avwx:TAF object as defined in the WXXM 1.1.1 schema. I believe the
issue is that the WXXM schema defines a 0..n mapping of avwx:TAF to
avwx:aerodromeWxForecast objects, but the avwx:aerodromeWxForecast
element is defined within the SurfaceForecastReportType rather than as a
top-level complexType. When I attempt to use feature chaining to create
these sub-elements the result is:

“NoSuchElementException: No top level element found in schemas:
{http://www.eurocontrol.int/avwx/1.1\}aerodromeWxForecast”.

The WXXM schema in question can be found here
<http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurfaceForecastReport.xsd&gt;\.

http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurfaceForecastReport.xsd

Seeing that these schemas are outside of my control is there any
workaround I could try that doesn’t require modification of the schema
itself?

Thanks,

*Kevin M. Weiss*

Software Engineer

*H**/A/**RRIS IT Services*

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Mineral Resources Flagship
Australian Resources Research Centre

3

Ben,
Thanks for the reply. I modified the locally cached copy of the schema and was able to bypass the "No top level element" error. I'm now getting WFS responses that contain multiple avwx:aerodromeWxForecast elements...however no matter what I try the aerodromeWxForecast elements are empty. (See attached for an example snippet) The number of elements is correct (3 in the attached example), but the sub-elements are not getting populated and no error is generated.
The feature chain mapping appears to be correct and is included by the parent mapping file. I can force it to generate an error by intentionally misspelling one of the column names which results in an error listing the db contents. In that error I can see it is correctly retrieving data from the table, but it never results in a populated element.
I'm using feature chaining on a few other data types without issue and this case doesn't appear to be any different configuration-wise.

Any ideas on what I might try to resolve this would be greatly appreciated.
Thanks,

Kevin M. Weiss
Software Engineer
HARRIS IT Services

-----Original Message-----
From: Ben Caradoc-Davies [mailto:Ben.Caradoc-Davies@…367…]
Sent: Wednesday, October 01, 2014 2:06 AM
To: Weiss, Kevin; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] WXXM and app-schema plug-in

Kevin,

I checked with feature chaining expert Rini Angreani who confirmed "No element, no mapping."

There is an easy workaround: modify the schema in your app-schema-cache.
(The same trick will work with an OASIS Catalog but cache is easiest; I recommend being lazy.) GeoServer app-schema will use the version in the cache and never update it so your changes are safe. Caches are also portable and can be deployed to other instances. If you change the definition in your cache to be compatible with GeoServer app-schema, you can still refer to the canonical schema location in your mapping files and it will be encoded as such in responses. As long as your changes do not change the information model, this is a complete, interoperable solution. The behaviour of schema caching is designed to allow this workaround.

For details on schema resolution, see:
http://docs.geoserver.org/latest/en/user/data/app-schema/app-schema-resolution.html

Kind regards,
Ben.

On 01/10/14 02:24, Weiss, Kevin wrote:

Hello all,

I’m running into an issue attempting to map our DB contents to an
avwx:TAF object as defined in the WXXM 1.1.1 schema. I believe the
issue is that the WXXM schema defines a 0..n mapping of avwx:TAF to
avwx:aerodromeWxForecast objects, but the avwx:aerodromeWxForecast
element is defined within the SurfaceForecastReportType rather than as
a top-level complexType. When I attempt to use feature chaining to
create these sub-elements the result is:

“NoSuchElementException: No top level element found in schemas:
{http://www.eurocontrol.int/avwx/1.1\}aerodromeWxForecast”.

The WXXM schema in question can be found here
<http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurfaceForecastReport.xsd&gt;\.

http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurf
aceForecastReport.xsd

Seeing that these schemas are outside of my control is there any
workaround I could try that doesn’t require modification of the schema
itself?

Thanks,

*Kevin M. Weiss*

Software Engineer

*H**/A/**RRIS IT Services*

----------------------------------------------------------------------
-------- Meet PCI DSS 3.0 Compliance Requirements with EventLog
Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI
DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download
White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.
clktrk

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@...367...> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre

WXXM_TAF.xml (625 Bytes)

4

Kevin,

please show us the mappings for this element and how you defined the new element.

Be sure to have the correct nesting of type and property type so that the GML encoding rule object/property/object/property... is observed otherwise the GeoTools Encoder will silently ignore your complex content. I suspect that avwx:aerodromeWxForecast should be defined as a wx:ForecastPropertyType.

Kind regards,
Ben.

On 02/10/14 04:54, Weiss, Kevin wrote:

Ben,
Thanks for the reply. I modified the locally cached copy of the schema and was able to bypass the "No top level element" error. I'm now getting WFS responses that contain multiple avwx:aerodromeWxForecast elements...however no matter what I try the aerodromeWxForecast elements are empty. (See attached for an example snippet) The number of elements is correct (3 in the attached example), but the sub-elements are not getting populated and no error is generated.
The feature chain mapping appears to be correct and is included by the parent mapping file. I can force it to generate an error by intentionally misspelling one of the column names which results in an error listing the db contents. In that error I can see it is correctly retrieving data from the table, but it never results in a populated element.
I'm using feature chaining on a few other data types without issue and this case doesn't appear to be any different configuration-wise.

Any ideas on what I might try to resolve this would be greatly appreciated.
Thanks,

Kevin M. Weiss
Software Engineer
HARRIS IT Services

-----Original Message-----
From: Ben Caradoc-Davies [mailto:Ben.Caradoc-Davies@anonymised.com]
Sent: Wednesday, October 01, 2014 2:06 AM
To: Weiss, Kevin; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] WXXM and app-schema plug-in

Kevin,

I checked with feature chaining expert Rini Angreani who confirmed "No element, no mapping."

There is an easy workaround: modify the schema in your app-schema-cache.
(The same trick will work with an OASIS Catalog but cache is easiest; I recommend being lazy.) GeoServer app-schema will use the version in the cache and never update it so your changes are safe. Caches are also portable and can be deployed to other instances. If you change the definition in your cache to be compatible with GeoServer app-schema, you can still refer to the canonical schema location in your mapping files and it will be encoded as such in responses. As long as your changes do not change the information model, this is a complete, interoperable solution. The behaviour of schema caching is designed to allow this workaround.

For details on schema resolution, see:
http://docs.geoserver.org/latest/en/user/data/app-schema/app-schema-resolution.html

Kind regards,
Ben.

On 01/10/14 02:24, Weiss, Kevin wrote:

Hello all,

I’m running into an issue attempting to map our DB contents to an
avwx:TAF object as defined in the WXXM 1.1.1 schema. I believe the
issue is that the WXXM schema defines a 0..n mapping of avwx:TAF to
avwx:aerodromeWxForecast objects, but the avwx:aerodromeWxForecast
element is defined within the SurfaceForecastReportType rather than as
a top-level complexType. When I attempt to use feature chaining to
create these sub-elements the result is:

“NoSuchElementException: No top level element found in schemas:
{http://www.eurocontrol.int/avwx/1.1\}aerodromeWxForecast”.

The WXXM schema in question can be found here
<http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurfaceForecastReport.xsd&gt;\.

http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurf
aceForecastReport.xsd

Seeing that these schemas are outside of my control is there any
workaround I could try that doesn’t require modification of the schema
itself?

Thanks,

*Kevin M. Weiss*

Software Engineer

*H**/A/**RRIS IT Services*

----------------------------------------------------------------------
-------- Meet PCI DSS 3.0 Compliance Requirements with EventLog
Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI
DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download
White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.
clktrk

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Mineral Resources Flagship
Australian Resources Research Centre

5

Ben,
Attached is a tarball with my mapping files as well as the updated schema (icaoSurfaceForecastReport.xsd). Note that forecast_wx.xml and forecast_cloud.xml are currently unused. I wanted to get the TAF->Forecast mapping working first before introducing more feature chain sub-elements.

I tried adding type="wx:ForecastPropertyType" to the avwx:aerodromeWxForecast, but the change had no effect.

Thanks for helping with this.

Kevin M. Weiss
Software Engineer
HARRIS IT Services

-----Original Message-----
From: Ben Caradoc-Davies [mailto:Ben.Caradoc-Davies@…367…]
Sent: Wednesday, October 01, 2014 8:16 PM
To: Weiss, Kevin; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] WXXM and app-schema plug-in

Kevin,

please show us the mappings for this element and how you defined the new element.

Be sure to have the correct nesting of type and property type so that the GML encoding rule object/property/object/property... is observed otherwise the GeoTools Encoder will silently ignore your complex content. I suspect that avwx:aerodromeWxForecast should be defined as a wx:ForecastPropertyType.

Kind regards,
Ben.

On 02/10/14 04:54, Weiss, Kevin wrote:

Ben,
Thanks for the reply. I modified the locally cached copy of the schema and was able to bypass the "No top level element" error. I'm now getting WFS responses that contain multiple avwx:aerodromeWxForecast elements...however no matter what I try the aerodromeWxForecast elements are empty. (See attached for an example snippet) The number of elements is correct (3 in the attached example), but the sub-elements are not getting populated and no error is generated.
The feature chain mapping appears to be correct and is included by the parent mapping file. I can force it to generate an error by intentionally misspelling one of the column names which results in an error listing the db contents. In that error I can see it is correctly retrieving data from the table, but it never results in a populated element.
I'm using feature chaining on a few other data types without issue and this case doesn't appear to be any different configuration-wise.

Any ideas on what I might try to resolve this would be greatly appreciated.
Thanks,

Kevin M. Weiss
Software Engineer
HARRIS IT Services

-----Original Message-----
From: Ben Caradoc-Davies [mailto:Ben.Caradoc-Davies@…367…]
Sent: Wednesday, October 01, 2014 2:06 AM
To: Weiss, Kevin; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] WXXM and app-schema plug-in

Kevin,

I checked with feature chaining expert Rini Angreani who confirmed "No element, no mapping."

There is an easy workaround: modify the schema in your app-schema-cache.
(The same trick will work with an OASIS Catalog but cache is easiest; I recommend being lazy.) GeoServer app-schema will use the version in the cache and never update it so your changes are safe. Caches are also portable and can be deployed to other instances. If you change the definition in your cache to be compatible with GeoServer app-schema, you can still refer to the canonical schema location in your mapping files and it will be encoded as such in responses. As long as your changes do not change the information model, this is a complete, interoperable solution. The behaviour of schema caching is designed to allow this workaround.

For details on schema resolution, see:
http://docs.geoserver.org/latest/en/user/data/app-schema/app-schema-re
solution.html

Kind regards,
Ben.

On 01/10/14 02:24, Weiss, Kevin wrote:

Hello all,

I’m running into an issue attempting to map our DB contents to an
avwx:TAF object as defined in the WXXM 1.1.1 schema. I believe the
issue is that the WXXM schema defines a 0..n mapping of avwx:TAF to
avwx:aerodromeWxForecast objects, but the avwx:aerodromeWxForecast
element is defined within the SurfaceForecastReportType rather than
as a top-level complexType. When I attempt to use feature chaining
to create these sub-elements the result is:

“NoSuchElementException: No top level element found in schemas:
{http://www.eurocontrol.int/avwx/1.1\}aerodromeWxForecast”.

The WXXM schema in question can be found here
<http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurfaceForecastReport.xsd&gt;\.

http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSur
f
aceForecastReport.xsd

Seeing that these schemas are outside of my control is there any
workaround I could try that doesn’t require modification of the
schema itself?

Thanks,

*Kevin M. Weiss*

Software Engineer

*H**/A/**RRIS IT Services*

---------------------------------------------------------------------
-
-------- Meet PCI DSS 3.0 Compliance Requirements with EventLog
Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI
DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download
White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.
clktrk

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@...367...> Software Engineer
CSIRO Mineral Resources Flagship Australian Resources Research Centre

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@...367...> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre

6

On Thu, Oct 2, 2014 at 3:10 PM, Weiss, Kevin <kweiss01@anonymised.com> wrote:

Ben,
Attached is a tarball with my mapping files as well as the updated schema
(icaoSurfaceForecastReport.xsd). Note that forecast_wx.xml and
forecast_cloud.xml are currently unused. I wanted to get the TAF->Forecast
mapping working first before introducing more feature chain sub-elements.

I don't see the attachment?

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

7

Sigh…

Too early here and not enough coffee yet.

Thanks,

Kevin M. Weiss

Software Engineer

HARRIS IT Services

taf_mapping.tgz (7.5 KB)

···

From: andrea.aime@…84… [mailto:andrea.aime@…84…] On Behalf Of Andrea Aime
Sent: Thursday, October 02, 2014 8:39 AM
To: Weiss, Kevin
Cc: Ben Caradoc-Davies; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] WXXM and app-schema plug-in

On Thu, Oct 2, 2014 at 3:10 PM, Weiss, Kevin <kweiss01@…5740…> wrote:

Ben,
Attached is a tarball with my mapping files as well as the updated schema (icaoSurfaceForecastReport.xsd). Note that forecast_wx.xml and forecast_cloud.xml are currently unused. I wanted to get the TAF->Forecast mapping working first before introducing more feature chain sub-elements.

I don’t see the attachment?

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit

http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

8

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-Davies@anonymised.com>
Software Engineer
CSIRO Mineral Resources Flagship
Australian Resources Research Centre

9

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-Davies@…367…]
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-Davies@...367...> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre

GS_Trace.txt (4.18 KB)

10

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-Davies@…367…]
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-Davies@...367...> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre

11

That's great, Kevin. thanks for letting us know.

Kind regards,
Ben.

On 07/10/14 05:35, Weiss, Kevin wrote:

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-Davies@anonymised.com]
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-Davies@anonymised.com> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Mineral Resources Flagship
Australian Resources Research Centre