You are here: OGC Public Wiki>MetOceanDWG Web>MetOceanWMSBestPracticesHotTopics>MetOceanModellingTimeUpdate_2011March (05 Apr 2011, MarieFrancoiseVoidrotMartinez)Edit Attach

Proposal of mapping between TIME concepts of numerical weather simulations and ISO/DIS 19156 Observations and Measurements (O&M 2.0)

This page just make a summary of the Proposal made in the Bonn TC by Jeremy Tandy

Following comments from members of the DWG, the specification of the 'assimilationWindow' concept has been updated. A new version (2.3) of Jeremy's presentation can be found here:

OGC_Met-Ocean_DWGIts-about-time2011-03-22_TANDY_v2.3.pdf

This proposal is base on ISO/DIS 19156 Observations and Measurements ... also known as O&M 2.0

Met Ocean Time Concept O&M Modelling Comments or examples

1-phenomenonTime: period covered by the forecast; the time domain of the forecast result

6.2.2.2 phenomenonTime

The attribute phenomenonTime:TM_Object shall describe the time that the result (6.2.2.9) applies to the property of the feature-of-interest (6.2.2.7). This is often the time of interaction by a sampling procedure (8.1.3) or observation procedure (6.2.2.10) with a real-world feature.

NOTE 1 The phenomenonTime is the temporal parameter normally used in geospatial analysis of the result.

NOTE 2 If the observedProperty of an observation is ‘occurrence time’ then the result should be the same as the phenomenonTime

For instance if a numerical weather simulation starts at 2010-05-06T00:00Z and the simulation describes the future weather conditions over the subsequent 84 hour period until 2010-05-09T12:00Z,

phenomenonTime.begin=2010-05-06T00:00Z

phenomenonTime.end=2010-05-09T12:00Z
________ ________ ________
2-resultTime: time at which the last part of the numerical forecast run is made available = When the complete result are published

6.2.2.3 resultTime

The attribute resultTime:TM_Instant shall describe the time when the result became available, typically when the procedure (6.2.2.10) associated with the observation was completed For some observations this is identical to the phenomenonTime. However, there are important cases where they differ.

In the example above if the simulation completes at 04:30Z,

resultTime=2010-05-06T04:30Z
________ ________ ________
  6.2.2.4 validTime

If present, the attributevalidTime:TM_Period shall describe the time period during which the result is intended to be used.

NOTE This attribute is commonly required in forecasting applications.

Although the terminology is similar, O&M validTime describes legal or practical usage constraints that are applied to the observation result. For example, validTime would be used with entities such as Terminal Aerodrome Forecasts (TAFs) which are (legally) only valid for 12-hrs (or 18-hrs) after publication. validTime is different to the validity time which is used to describe an instant of interest within the result of the simulation.

For forecast modelling it can be optional. It is not specified here.

________ ________ ________

3-analysisTime: Analysis Time describes the time instant for the initial conditions of a numerical weather simulation.

The analysis Time is chosen from a time-instant toward the middle of the assimilation window where the model state is considered to be more realistic.

6.2.2.5 parameter

If present, the attributes parameter:NamedValue shall describe an arbitrary event-specific parameter. This might be an environmental parameter, an instrument setting or input, or an event-specific sampling parameter that is not tightly bound to either the feature-of-interest (6.2.2.7) or to the observation procedure (6.2.2.10). To avoid ambiguity, there shall be no more than one parameter with the same name.

parameter.name shall be "analysisTime" for this concept

parameter.value shall be of TYPE time instant

parameter.name="analysisTime" parameter.value=2010-05-06T00:00Z
________ ________ ________
4 assimilationWindow: time period from which observations are selected to be assimilated into the analysis

6.2.2.5 parameter (see above)

parameter.name shall be "assimilationWindow" for this concept

parameter.value shall be of TYPE time period

(note that 'value' can be of any type - for implementation choose TM_Period)

For a simulation with an assimilation window from 21:00 to 02:30 ...

name=“assimilationWindow”

value.begin=“2010-05-05T21:00Z”

value.end=“2010-05-06T02:30Z”
-- MarieFrancoiseVoidrotMartinez - 04 Apr 2011

-- JeremyTandy - 05 Apr 2011
I Attachment Action Size Date Who Comment
OGC_Met-Ocean_DWGIts-about-time2011-03-22_TANDY_v2.3.pdfpdf OGC_Met-Ocean_DWGIts-about-time2011-03-22_TANDY_v2.3.pdf manage 4 MB 05 Apr 2011 - 07:45 JeremyTandy Update of the proposal from Jeremy Tandy discussing how TIME concepts of numerical weather simulations (i.e. forecasts) can be mapped to ISO/DIS 19156 Observations and Measurements
Edit  | Attach | Print version | History: r3 < r2 < r1 | Backlinks | View wiki text | Edit wiki text | More topic actions
Topic revision: r3 - 05 Apr 2011, MarieFrancoiseVoidrotMartinez
This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback