Transcript Work on a WMS 1.3 profile

®
Hosted and Sponsored by
Met Ocean Best Practices Progress report
78th OGC Technical Committee
Boulder, Colorado (USA)
Marie-Françoise Voidrot
September 19, 2011
Copyright © 2011Open Geospatial Consortium
References
• OGC Procedures and templates
– Technical Committee Policies and Procedures draft revision OGC 05-020r17
– Draft OGC Standard document template OGC 10-176r2
– Guidance to Editors and Authors of OGC Documents that use the OGC Standards
document template. OGC 10-177r1
– RFC_Checklist_for_non-fast_track_candidate_standard OGC10-204r1
• Technical references
– OpenGIS® Web Map Server Implementation Specification Version: 1.3.0 OGC 06-042
– Web Map Services - Application Profile for EO Products Version: 0.3.3 OGC 07-063r1
– DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a
military environment Version: 0.9.0 OGC 09-102
– WMS 2.0.0v15 OGC Web Map Services Standard Candidate.doc
– Emails, Teleconf minutes ….
OGC
®
Choices
• Work on a WMS 1.3 profile
– Cons :
•
•
WMS 1.1 is more implemented
WMS 2.0 should solve part of our issues
– Pros :
•
•
•
the spec is there,
It is the last one
It is the one recommended by INSPIRE
– The bet : the challenge is to do one, making a WMS2.0 update should be easier
• The form : The document should follow the spec structure as far as possible
– Cons :
•
Different from the OGC template and other existing profiles
– Pros :
•
•
will easy a simultaneous reading and understanding,
should allow an easy share of the load : anyone can take an issue an suggest a phrasing for the corresponding
paragraphs
– The bet : the synthesis should be easier as it will be first paragraph by paragraph and then on the
global document
OGC
®
Let’s go….to….questions
• General scope
– The server advertises the version of the spec it implements but how does it advertise the
profile it implements?
– How to define a timestamp for the getcapabilities in order to handle the permanent update
of the met ocean data?
OGC
®
Let’s try
• Time handling,
– The most specific
– Compulsory for our domain
– The most difficult but the most discussed (for observation and forecast)
• First proposal via the twiki end June
2011http://external.opengis.org/twiki_public/MetOceanDWG/MetOceanWMSBP20110627
• Reactions from people involved into Climatology and climate change
• Changes and new discussions :
• how to express a monthly mean anomaly compared to a monthly mean temperature defined
on a reference period of 20 years
– Overloading the TIME parameter semantics -> excluded
– Putting the temporal reference infos into the name of the layer -> if it doesn’t lead to a huge amount of
layers
– Defining new specific DIMENSIONS -> loosing interoperability
OGC
®
Controlled vocabulary
1.
4.
World Meteorological Organization:. International Meteorological Vocabulary WMO/OMM/BMO N°182
Publisher: Secretariat to World Meteorological Organization ; 2nd edition (January 1992), ISBN-10: 92-6302182-1 Content is 697 pages of controlled vocabulary with the definitions in English, French, Russian and
Spanish.Organised by alphabetical order in English but provides an Index for the other languages.
World Meteorological Organization keywords for metadata :
http://www.wmo.int/pages/prog/www/WDM/Metadata/WMO_%20metadata_standard_keywords.xls
World Meteorological Organization’s terminology database :. METEOTERM contains specialized
terminology in six languages: English, Arabic, Chinese, French, Russian and Spanish. METEOTERM
includes the International Meteorological Vocabulary, the International Glossary of Hydrology, and terms
from related sciences that appear in WMO documents. METEOTERM
WMO Common Codes table C13 COMMON CODE TABLES TO BINARY AND ALPHANUMERIC CODES
5.
ECMWF : a major work of mapping on behalf of WMO. Parameters tables of ECMWF GRIB API
6.
7.
8.
9.
10.
CF-Conventions : Comparable work has been done by the CF-Conventions actors : CF-Conventions
American Meteorological Society Glossary including definitions AMS Glossary.
NNew Program : See attached files of a weather ontology produced by the NNEW program
*ionet gemet thesaurus
Nasa's Global Change Master Directory : (GCMD) and http://gcmd.gsfc.nasa.gov/Resources/valids/
2.
3.
OGC
®
Some disappointing points
• We have opened again the Pandora’s box of time handling
• People have been worn out by this issue
OGC
®
But also some positive outcomes
• Writing the first draft for time has been quite
easy
• The climate people get involved : new
communities catch the train
OGC
®
Conclusion
• A slow process
• Too many issues
• Need to find a way to share the load
– Volunteers to take the lead for specific issues : vertical coordinates
or compoundCRS
– Relays for general questions to OGC experts without having the
responsability to define a solution compatible with all standards,
existing works ….
OGC
®
Having some servers and
clients available
A growing dynamic
Volunteers always welcome
OGC
®
Discussions
• Validation of the choices
– To make Best Practices for version 1.3
– To built a BP document sticking to the specification doc
• Any volunteer for pending issues?
–
–
–
–
–
–
Time (observations, forecasts, climatologie, climate change)
Layers naming
Projections/CRS
Vertical coordinates or compound CRSs
Styling
GetFeature Info standardisation or definition of new operations
• To benefit from support from the other groups or OGC experts
–
–
–
–
Asynchronous and dynamic delivery
How to serve extra metadata about WMS layers ans maps
How to advertise compliancy with a best practices or profile
How to define a timestamp for the getcapabilities in order to handle the permanent
update of the met ocean data?
OGC
®