s 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';
tober 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 resu
-
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
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.
@lists.sourceforge.net
Subject: Re: [Geoserver-users] WXXM and app-schema plug-in
On Thu, Oct 2, 2014 at 3:10 PM, Weiss, Kevin
mailto:kweis...@harris.com>> wrote:
Ben,
Attached is a tarball with my mapping files as well as the updated schema
(icaoSurfaceForecastReport.xsd). Note that forecast_
On Thu, Oct 2, 2014 at 3:10 PM, Weiss, Kevin 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
nt: 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 pro
doc-dav...@csiro.au]
> 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
n.caradoc-dav...@csiro.au]
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."
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
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 defi
11 matches
Mail list logo
