WOML-Core contains the basic types and elements for the Weather Objects Modelling Language (WOML). In most cases you want to use it through the derived, concrete schemas, like WOML-SWO, WOML-Quantity or WOML-Textfct.
WOML-Core is currently based on GML 3.1.1.
WOML Core Types
The type hierarchy in WOML-Core single object feature types is based on the main geometry: objects are divided into point, line and (surface)area objects. They all inherit the basic metadata properties, like creation time, textual descriptions and geometric bounds from their super types. The corresponding abstract elements act as substitution heads for the semantically meaningful meteorological feature elements defined outside the WOML-Core.
All single feature WOML feature types are inherited from gml:DynamicFeature, which gives them ability to reflect their properties' development in time, like the movement and shape changes of a front during observation or forecast period. The values for these time-depending properties are expressed as "Event" objects for a given points in time contained in the gml:history property. WOML-Core defines these events for each of the basic objects types: PointObjectEventType for points, LineObjectEventType for lines and SurfaceObjectEventType for area objects. They all extend the gml:AbstractTimeSliceType by adding the corresponding geomentry-related properties as the ones that might change in time. The gml:validTime property defines the limits for the entire lifetime of a meteorological feature, so the event objects' valid times should be limited to the valid time of the containing feature.
To gather more than one meteorological objects into a forecast or analysis for a given area and time frame, the WOML-Core defines two basic feature collection types: the WeatherForecastType and the MeteorologicalAnalysisType. These collection types may also contain other WOML features as they descend from the gml:AbstractFeatureCollectionType. Both the analysis and the forecast features provide one or more geographical target regions as well as zero or more references to the background data the forecaster has used for creating the objects in the collection.
For a semantically more loosely defined collection of feature objects, you can use MeteorologicalObjectCollectionType higher in the feature type hierarchy, which only adds the concept of contained features' shared connection points and the basic metadata properties to the gml:FeatureCollectionType.
The instances of MeteorologicalAnalysis and WeatherForecast may carry an official approval given by a forecasting authority and the digital signature of the collection content using the W3C Digital Signature standard to verify the issuing authority and protect the data against intermediate modifications. More this kind of "approved" collections may be created by extending the womlcore:AbstractApprovedObjectCollectionType in the domain specific schemas.
Issues scheduled for the next versions