Clarus Metadata Task Force Background Information

1
Clarus Metadata Task ForceBackground Information
National Center for Atmospheric Research Boulder,
CO September 28-29, 2006

• Andy Stern, Meteorologist
• FHWA/Road Weather Management Team
• Mitretek Systems
• Falls Church, VA

2
Tier Structure

• A tier structure has been proposed to assist in
  discussion organization
• Basic Metadata (Tier 1) set of common metadata
  elements essential for Clarus to operate allow
  for a broader usage of ESS
• Supplemental Metadata (Tier 2) enhances the
  Tier 1 metadata by adding more diverse
  descriptions for ESS platforms its surroundings
• Specialized Metadata (Tier 3) descriptors for
  specialized programs

3
Tier Structure
Essential Clarus Metadata
Specialized Metadata Fields
Optional Clarus Metadata Additional
General Metadata Fields
Tier 1 Task Force Goal
Tier 2 Secondary Goal
Tier 3 Just for Discussion
4
Tier 1 Goals

• Develop a common set of ESS metadata elements
  (can be shared nationally)
• Identify understand the essential owner
  provided metadata fields for Clarus
• Consider optional owner provided metadata fields
  for Clarus
• Add additional fields that would support the
  broader usage of ESS data metadata on a
  national scale

5
Tier 1 Elements
Maintenance -Installation -Calibration -Repairs/re
placements
Physical Station Description -Location -Elevation
Sensor Types -Weather -Pavement -Subsurface -Speci
alized (CCTV)
ESS Data Access -Phone Number -IP Address -DOT POC
Tier 1 Metadata

• Representativeness
• Obstructions
• Heat sources/sinks
• Terrain

6
Initial Look _at_ Metadata Comparisons

• Eight examples of established metadata were used
  to compare fields associated with ESS surface
  observations. These included
• Utah DOT
• Meridian
• Washington State DOT
• ESS Siting Guidelines

• Alaska DOT PF
• CMML 2.0
• Clarus
• World Meteorological Organization (WMO)

7
Utah DOT Metadata Example
801-555-5555
Credit Ralph Patterson
8
Utah DOT Metadata ESS Map
9
Utah Dot Metadata
10
Utah DOT Metadata Panoramic Photos
11
Meridian Environmental Technology Site Evaluation
Report
Credit Leon Osborne
12
Meridian Environmental Technology Four
Quadrant Site Layout
13
Washington State DOT Site Metadata Sheet
Credit Larry Senn
14
FHWA ESS Siting Guidelines
15
Alaska DOT PF
Credit FSU Alum Jack Stickel
16
Alaska DOT PF
17
Canadian CMML v2.0
18
Clarus Metadata Dictionary
Credit Mixon/Hill
19
WMO World Meteorological Organization
20
Metadata Characteristics

• From the eight metadata sets
• there were at least 105 distinct fields
  describing eight general categories of elements
  including
• ESS platform identification and location
• Site ownership
• Instrumentation
• Video/Camera information
• Communications
• Site layout
• Maintenance

FHWA Road Weather Management
21
Ranking Metadata

• After all metadata fields were compared, only
  four fields were common among all eight data
  sets
• Platform ID/Site Number
• Plain Text Location Description
• Latitude/Longitude Position (of tower base)
• Site Elevation (of tower base)

22
Metadata Ranking 2nd Level

• Metadata fields that were common among 6 of the 8
  data sets include
• Highway Milepost Marker
• Thermometer Model
• Anemometer Model
• Site Representativeness
• Description of Obstructions
• Landscape Features (terrain)

Hardware Location Attributes
Physical Features Describing the Surroundings
23
Metadata Study Results
24
Spreadsheet Overview

• The MTF Data Dictionary spreadsheet contains 5
  worksheets (which are in your handouts)
• All Fields Contains a listing of all metadata
  elements in the Clarus system
• Critical Owner Provided Fields All metadata
  elements considered critical for Clarus and are
  supplied by the network owner
• Data Types Short explanations of data types used
  in the MTF data dictionary spreadsheet
• Optional Owner Provided Fields Metadata elements
  included in the Clarus cache that are not
  considered critical
• NTCIP 1204 Obs Types A listing of observation
  types from the 1204 data dictionary

25
All Fields Worksheet
Our initial focus will be on owner provided
essential Clarus fields
Clarus Library Name
Plain Language Description
26
Critical Owner Provided Fields
27
Critical Owner Provided Fields
Clarus Metadata Library Name
Plain text description
Ranking (from the Study)
Precision
Fields associated with quality checking
Clarus Data types
Data Bounds
Example or format
28
Data Type Definitions
29
Optional Owner Provided Fields
Phone numbers contain only digits (no or ())
30
NTCIP 1204 Observation Types
31
Things to Remember (1 of 2)

• To the Clarus database, observations are broken
  down into atomic elements (e.g., temperature vs.
  dew point vs. pressure)
• NTCIP 1204 data types are used when practical
  (e.g., weather elements)
• Because the same database field can hold
  different observed values, specific precision and
  data bounds cannot be assigned in the generic
  sense

32
Things to Remember (2 of 2)

• Telephone numbers (including faxes, etc) only
  contain digits (no dashes)
• The essential Clarus metadata fields are only a
  subset of what will be needed to accurately
  describe an ESS
• The final metadata list should be inclusive of
  essential elements but not so labor intensive or
  costly as to prevent its use

33
CCTV Advice (courtesy of Bob H)

• Position Latitude/Longitude height of the
  camera above the ground
• Type Manufacturer model
• Shielding type (if any)
• Sensing Visible versus Infrared
• Mobility
• Fixed Nominal pan/tilt/zoom values
• Pan/Tilt/Zoom predefined settings or streaming
  values?
• All directions in degrees relative to true North

34
Go Forth!

• We are now ready to begin discussing metadata
  fields
• We will begin with Essential Owner Provided
  Fields for Clarus
• We are under a time constraint because of the
  pending release of the Clarus RFA
• Focus on our goal
• Be prepared to compromise
• Everyones opinion is valuable