Hdf eos5 validator tool
This presentation is the property of its rightful owner.
Sponsored Links
1 / 16

HDF-EOS5 Validator Tool PowerPoint PPT Presentation


  • 127 Views
  • Uploaded on
  • Presentation posted in: General

HDF-EOS5 Validator Tool. Bob Bane Jingli Yang Richard Ullman Data Usability Task NASA/GSFC. HDF-EOS5 Validator. Validates HDF-EOS5 files against guidelines Guidelines are encoded in XML Output is a report with specific non-conformance messages. Why HDF-EOS5 Validator?.

Download Presentation

HDF-EOS5 Validator Tool

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Hdf eos5 validator tool

HDF-EOS5 Validator Tool

Bob Bane

Jingli Yang

Richard Ullman

Data Usability Task

NASA/GSFC

HDF-EOS Workshop VII


Hdf eos5 validator

HDF-EOS5 Validator

  • Validates HDF-EOS5 files against guidelines

  • Guidelines are encoded in XML

  • Output is a report with specific non-conformance messages

HDF-EOS Workshop VII


Why hdf eos5 validator

Why HDF-EOS5 Validator?

  • Insures that product files:

    • Have all data and metadata items they are supposed to contain

    • Those items are of correct name, type, and size

  • Validator is a tool mainly for data producers to check format of files before delivering them to users.

HDF-EOS Workshop VII


Hdf eos5 validator1

HDF-EOS5 file

Validator

report

Validator

Guidelines

(in XML)

HDF-EOS5 Validator

HDF-EOS Workshop VII


Xml description of file format guidelines

Like a checklist

List of features that must/should be in file

And their characteristics

Not all-inclusive

Extra things in file will not be reported

XML Description of File Format Guidelines

HDF-EOS Workshop VII


What can be validated

What can be validated?

  • Swaths

    • Every swath

    • Swaths with a specific name

    • Fields

      • Data

        • Every/specific name

      • Geolocation

        • Every/specific name

    • Dimensions

      • Name, size

HDF-EOS Workshop VII


What can be validated cont

What can be validated (cont)?

  • Attributes

    • Global/Swath/Field

    • Type

      • String

        • Value/Set/regular expression

      • Integer/Float

        • Value/Range

HDF-EOS Workshop VII


Examples stringvalue

Examples: StringValue

  • <StringValue/>

    • Any string

  • <StringValue matches=“seconds *”/>

    • “seconds” followed by spaces

  • <StringValue><OneOf><s>foo</s><s>bar</s></OneOf></StringValue>

    • “foo” or “bar”

HDF-EOS Workshop VII


Examples intvalue

Examples: IntValue

  • <IntValue/>

    • Any integer value

  • <IntValue min=“17” max=“42”/>

    • Integer between 17 and 42 inclusive

  • <IntValue> min=“0”/>

    • Non-negative integer

HDF-EOS Workshop VII


Example dimension

Example: Dimension

  • <Dimension name=“Latitude”/>

    • name is required

  • <Dimension name=“Height” size=“100”/>

    • size is fixed

  • <Dimension name=“X” min=“5” max=“10”/>

    • Size can be in range 5-10

HDF-EOS Workshop VII


Examples attributes

Examples: Attributes

<Attributes>

<Mandatory>

<Attribute name=“InstrumentName”>

<StringValue/>

</Attribute>

</Mandatory>

<Optional>

<Attribute name=“FieldCount”>

<IntValue min=“0” max=“10”/>

</Attribute>

</Optional>

</Attributes>

HDF-EOS Workshop VII


Overall file structure

Overall File Structure

<HDF-EOS-Validation-Definition>

<Attributes>…

<Swaths>

<Every-Swath>

<Attributes>…

<Swath-Dimensions>

<Mandatory-Dimensions>

<Dimension … />

<Optional-Dimensions>

<Dimension … />

HDF-EOS Workshop VII


Overall file structure cont

Overall File Structure (cont.)

<GeolocationFields>

<Every-GeolocationField>

<DataType … />

<Dimensions>

<d>Lat</d><d>Lon</d>

<Attributes>…

<GeolocationField-Named name=“LatLon”>

<DataType … />

<Dimensions> …

<Attributes> …

HDF-EOS Workshop VII


Implementation

Implementation

  • Command line

  • C

  • HDF-EOS5 library

  • Open source XML parsing libraries

    • expat

    • SCEW

  • Portable to any HDF-EOS5 platform

HDF-EOS Workshop VII


Sample output report

Sample Output Report

$ validate_hdfeos5 -x HIRDLS-definition.xml -h test.h5

SWATH HIRDLS

Missing mandatory dimension: nWavel

SWATH HIRDLS GEOLOCATION_FIELD Time ATTRIBUTE Units

string "TAI "

doesn't match <StringValue value="seconds"/>

SWATH HIRDLS

Missing mandatory geolocation field: Altitude

SWATH HIRDLS

Missing mandatory data field: TemperatureNormChiSq

Errors: 4

HDF-EOS Workshop VII


Status

Status

  • Supports needs of Aura (our test case)

    • Swaths (no Grids/Points yet)

    • Prototype descriptions

      • For HIRDLS, MLS, OMI, TES

      • Based on Aura Data Format Guidelines document

      • Tested against Aura data samples, and correctly reported variances from guidelines

    • Goal is for product producers to write/maintain their own description files

HDF-EOS Workshop VII


  • Login