Dataset Interoperability Recommendations by Category

Recommendations

Dataset Interoperability Recommendations for Earth Science (RFC-028)

• Page:
  Consider “balanced” chunking for 3-D datasets in grid structures
• Page:
  Distinguish clearly between HDF and netCDF packing conventions
• Page:
  Include Basic CF Attributes
• Page:
  Include Datum Attributes for Data in Grid Structures
• Page:
  Include Time Dimension in Grid Structured Data
• Page:
  Make HDF5 files netCDF4-Compatible and CF-compliant within Groups
• Page:
  Mapping between ACDD and ISO
• Page:
  Maximize HDF5/netCDF4 interoperability via API accessibility
• Page:
  Order Dimensions to Facilitate Readability of Grid Structure Datasets
• Page:
  Use CF Bounds Attributes
• Page:
  Verify CF compliance
• Page:
  When to Employ Packing Attributes

Dataset Interoperability Recommendations for Earth Science: Part 2 (RFC-036)

• Page:
  Adopt Semantically Rich Dataset Release Identifiers
• Page:
  Character Set for User-Defined Group, Variable, and Attribute Names
• Page:
  Consistent Units Attribute Value for Variables Across One Data Collection
• Page:
  Date-Time Information in Granule Filenames
• Page:
  Ensure Granule's Filename Uniqueness Across Different Dataset Releases
• Page:
  Include Georeference Information with Geospatial Coordinates
• Page:
  Include Time Coordinate in Swath Structured Data
• Page:
  Keep Coordinate Values in Coordinate Variables
• Page:
  Not-a-Number (NaN) Value
• Page:
  Standardize File Extensions for HDF5/netCDF Files
• Page:
  Use the Units Attribute Only for Variables with Physical Units

Combined RFC-028 and RFC-036 Dataset Interoperability Recommendations for Earth Science

• Page:
  Adopt Semantically Rich Dataset Release Identifiers
• Page:
  Attach the CF flag_values or flag_masks Attributes Along With the CF flag_meanings Attribute to Each Flag Variable
• Page:
  Avoid Use of the missing_value Attribute
• Page:
  Character Set for User-Defined Group, Variable, and Attribute Names
• Page:
  Consider “balanced” chunking for 3-D datasets in grid structures
• Page:
  Consistent Units Attribute Value for Variables Across One Data Collection
• Page:
  Date-Time Information in Granule Filenames
• Page:
  Define the Projection Ellipsoid to Match the Reference Datum
• Page:
  Distinguish clearly between HDF and netCDF packing conventions
• Page:
  Document Missing Granules for Instruments That Acquire Data on a Regular Basis
• Page:
  Ensure Granule's Filename Uniqueness Across Different Dataset Releases
• Page:
  Include Basic CF Attributes
• Page:
  Include Datum Attributes for Data in Grid Structures
• Page:
  Include Georeference Information with Geospatial Coordinates
• Page:
  Include Only One Variable per GeoTIFF File

Testing

Compliance and Metadata Recommendations

• Page:
  Adopt Semantically Rich Dataset Release Identifiers
• Page:
  Attach the CF flag_values or flag_masks Attributes Along With the CF flag_meanings Attribute to Each Flag Variable
• Page:
  Avoid Use of the missing_value Attribute
• Page:
  Character Set for User-Defined Group, Variable, and Attribute Names
• Page:
  Consider “balanced” chunking for 3-D datasets in grid structures
• Page:
  Consistent Units Attribute Value for Variables Across One Data Collection
• Page:
  Date-Time Information in Granule Filenames
• Page:
  Define the Projection Ellipsoid to Match the Reference Datum
• Page:
  Distinguish clearly between HDF and netCDF packing conventions
• Page:
  Document Missing Granules for Instruments That Acquire Data on a Regular Basis
• Page:
  Ensure Granule's Filename Uniqueness Across Different Dataset Releases
• Page:
  Include Basic CF Attributes
• Page:
  Include Datum Attributes for Data in Grid Structures
• Page:
  Include Georeference Information with Geospatial Coordinates
• Page:
  Include Only One Variable per GeoTIFF File

Grid Data Recommendations

• Page:
  Order Dimensions to Facilitate Readability of Grid Structure Datasets
• Page:
  Include Time Dimension in Grid Structured Data
• Page:
  Include Datum Attributes for Data in Grid Structures
• Page:
  Include Georeference Information with Geospatial Coordinates
• Page:
  Consider “balanced” chunking for 3-D datasets in grid structures
• Page:
  Keep Coordinate Values in Coordinate Variables
• Page:
  When to Employ Packing Attributes
• Page:
  Include Time Coordinate in Swath Structured Data
• Page:
  Not-a-Number (NaN) Value
• Page:
  Standardize File Extensions for HDF5/netCDF Files
• Page:
  Maximize HDF5/netCDF4 interoperability via API accessibility
• Page:
  Consistent Units Attribute Value for Variables Across One Data Collection
• Page:
  Distinguish clearly between HDF and netCDF packing conventions
• Page:
  Ensure Granule's Filename Uniqueness Across Different Dataset Releases
• Page:
  Use the Units Attribute Only for Variables with Physical Units

Swath Data Recommendations

• Page:
  Adopt Semantically Rich Dataset Release Identifiers
• Page:
  Attach the CF flag_values or flag_masks Attributes Along With the CF flag_meanings Attribute to Each Flag Variable
• Page:
  Avoid Use of the missing_value Attribute
• Page:
  Character Set for User-Defined Group, Variable, and Attribute Names
• Page:
  Consider “balanced” chunking for 3-D datasets in grid structures
• Page:
  Consistent Units Attribute Value for Variables Across One Data Collection
• Page:
  Date-Time Information in Granule Filenames
• Page:
  Define the Projection Ellipsoid to Match the Reference Datum
• Page:
  Distinguish clearly between HDF and netCDF packing conventions
• Page:
  Document Missing Granules for Instruments That Acquire Data on a Regular Basis
• Page:
  Ensure Granule's Filename Uniqueness Across Different Dataset Releases
• Page:
  Include Basic CF Attributes
• Page:
  Include Datum Attributes for Data in Grid Structures
• Page:
  Include Georeference Information with Geospatial Coordinates
• Page:
  Include Only One Variable per GeoTIFF File