1 / 13

HDF-EOS 3.0: Functional and Structural Design Overview

This document details the functional and structural design of HDF-EOS 3.0, based on HDF5 with input from NCSA. It discusses collaboration with EOS AURA teams to refine the design, aiming to maintain minimal impact on heritage code while enhancing functionality. Key features outlined include file I/O, compression, swath and grid interfaces, FORTRAN wrappers, and user guides. Additionally, it describes attributes, subsetting, and various inquiry functions. The document also highlights issues with data types and proposed user input solutions.

huong
Télécharger la présentation

HDF-EOS 3.0: Functional and Structural Design Overview

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HDF-EOS 3.0 Functional and Structural Design David Wynne/Alex Muslimov Emergent Information Technologies, Inc. September 19, 2000 davidw@eos.hitc.com/amuslimo@eos.hitc.com

  2. HDF-EOS 3.0 • Based on HDF5, with input from NCSA with respect to Design, Implementation and Method • Working with EOS AURA teams to Refine Design • Primary Goal of Design -- minimal impact to Heritage Code

  3. Current HDF-EOS 3.0 Functionality • Basic File I/O • FillValues • Compression • Chunking/Tiling • Swath Interface • Grid Interface • FORTRAN Wrappers • Profile Interface • Global, Group & Local Attributes • Extendable DataSets • Test Drivers • User’s Guide • Subsetting • SUN, SGI & DEC

  4. Functional Specification • Swath File Access • SWopen, SWcreate, SWattach, SWdetach and SWclose • Dimension/ Mapping Definition • SWdefdim, SWdefdimmap and SWdefidxmap • Field Definition/Compression/Chunking • SWdefgeofield*, SWdefdatafield*, SWdefcomp and • SWdefcomchunk • Field I/O, Inquiry and Info • SWwritefield, SWreadfield, SWinqdatafields, SWinqgeofield • and SWfieldinfo* • *Function interface has changed between HDF-EOS 2.x and 3.0 • Function names italicized represent new functionality

  5. Functional Specification, cont. • Attribute I/O, Inquiry and Info • SWwriteattr, SWreadattr, SWinqattrs, SWattrinfo • SWwritegrpattr, SWreadgrpattr, SWinqgrpattrs, SWgrpattrinfo • SWwritelocattr, SWreadlocattr, SWinqlocattrs and SWlocattrinfo • General Inquiry and Info • SWinqswath, SWnentries, SWinqdims, SWdiminfo, • SWinqmaps, SWmapinfo, SWinqidxmaps and SWidxmapinfo • Subsetting • SWdefboxregion, SWdeftimeperiod, SWregioninfo, • SWperiodinfo, SWextractregion and SWextractperiod • Profile • PRdefine, PRread, PRwrite, PRinquire and PRinfo • Function names italicized represent new functionality

  6. Functional Specification, cont. • HDF-EOS 2.6 • SWdefdatafield(swathID, fieldname, dimlist, numtype, merge) • HDF-EOS 3.0 • SWdefdatafield(swathID, fieldname, dimlist, maxdimlist, numtype, merge) • Maxdimlist • New HDF5 functionality passed through. This allows the user to set an upper limit to the size of the dataset.

  7. Top Level of HDF-EOS 3.0 File Root -- / HDFEOS POINTS HDFEOS INFORMATION SWATHS GRIDS Miscellaneous Proposed Group, User Input Group

  8. Top Level of HDF-EOS 3.0 File HDFEOS HDFEOS INFORMATION HDFEOSVersion StructMetadata.0 Data Set Attribute Group

  9. Swath Structure SwathName Global Attribute <SwathName>:<AttrName> Group Attribute <DataFields>:<AttrName> Data Fields Profile Fields Geolocation Fields Local Attribute <FieldName>:<AttrName> Profile Field1 Profile Fieldn Longitude Latitude Data Field1 Data Fieldn Each Data Field can have Attributes and/or Dimension Scales Time CoLatitude Dimension Scale Shaded Objects are implemented in a fixed way so the user doesn’t have direct access via the interface DataField1:DIMENSIONLIST Proposed Attribute, User Input Message Attribute <SwathName>:<AttrName> Data Set Attribute Group

  10. Profile Structure SwathName Global Attribute <SwathName>:<AttrName> Group Attribute <DataFields>:<AttrName> Profile Fields Geolocation Fields Local Attribute <FieldName>:<AttrName> Profile Field1 Profile Fieldn Longitude Latitude Each Data Field can have Attributes and/or Dimension Scales Dimension Scale Time CoLatitude DataField1:DIMENSIONLIST Message Attribute <SwathName>:<AttrName> Proposed Attribute, User Input Data Set Attribute Group

  11. Grid Structure Global Attribute <GridName>:<AttrName> GridName _BLKSOM: Group Attribute <DataFields>:<AttrName> Data Fields Local Attribute <FieldName>:<AttrName> Data Field1 Data Fieldn Message Attribute <GridName>:<AttrName> Each Data Field can have Attributes and/or Dimension Scales Dimension Scale Proposed Attribute, User Input Shaded Objects are implemented in a fixed way so the user doesn’t have direct access DataField1:DIMENSIONLIST Data Set Attribute Group

  12. Point Structure Global Attribute <PointName>:<AttrName> PointName _LevelWritten Group Attribute <DataFields>:<AttrName> Linkage Data Object Reference FWD POINT Level1 Name Local Attribute <LevelName>:<AttrName> BCK POINT Leveln Name Object Reference Message Attribute <PointName>:<AttrName> Proposed Attribute, User Input Shaded Objects are implemented in a fixed way so the user doesn’t have direct access Data Set Group Attribute

  13. Issues • Maximum size of variable length and compound data types • Chunking with variable length and compound data types • Only deflation compression method implemented. • File size limit in ECS - Is two Gbytes enough?

More Related