The DHuS addon is a Java package that contains the definitions and extraction rules and operations for the CryoSat-2 products. The central element of this package is the ontology definition file (cryosat-2.owl) located in the META-INF folder inside the resources directory.
The addon works in conjunction with the DRBX cortex definition (separate package), currently designed to support the following product types from the CryoSat-2 satellite mission:
- SIR_FDM_2_
- SIR_GOPM_2
- SIR_SAR_2_
- SIR_GOPR_2
- SIR_LRM_2_
- SIR_GOP_2_
- SIR_SIN_2_
- SIR_GDR_2_
- SIR_GOPN_2
All metadata that will be extracted and made available via DHuS is defined within the OWL file mentioned above. The following is a complete list of metadata attributes implemented with this addon. Sample outputs to demonstrate which values these attributes can take can be found in the samples folder inside the resources directory.
OData Name | OpenSearch Name | Description | SIR_FDM_2_ | SIR_GOPM_2 | SIR_SAR_2_ | SIR_GOPR_2 | SIR_LRM_2_ | SIR_GOP_2_ | SIR_SIN_2_ | SIR_GDR_2_ | SIR_GOPN_2 |
---|---|---|---|---|---|---|---|---|---|---|---|
Satellite | - | Name of the satellite | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Instrument | - | Name of the instrument | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Date | - | Same as sensing start date | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Sensing start | beginposition | Sensing start date | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Sensing stop | endposition | Sensing stop date | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Footprint | gmlfootprint | GML footprint | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
JTS footprint | footprint | JTS footprint | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Platform name | platformname | Name of the platform | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Platform short name | platformshortname | Short name of the platform | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Platform serial identifier | platformserialidentifier | Identification number of the platform among the mission | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Platform NSSDC identifier | platformnssdcidentifier | The National Space Science Data Center (NSSDC) identification number of the platform | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Instrument name | instrumentname | Name of the instrument | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Instrument short name | instrumentshortname | Short name of the instrument | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Orbit number | orbitnumber | Absolute orbit number | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Relative orbit number | relativeorbitnumber | Relative orbit number | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Cycle | cycle | Number of cycles | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Phase | phase | Mission phase | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Orbit direction | orbitdirection | Direction of the orbit (ascending or descending) | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Processing level | processinglevel | The value of the last processing | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Processor version | processorversion | Version number of processing software | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Generation time | - | Product generation date | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Processing mode | processingmode | Full name of processing mode or file class | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Processing mode abbreviation | processingmodeabbreviation | Abbreviated name of processing mode or file class | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Product type | producttype | Product type designation | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Product description | productdescription | One line description of the file | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Size | size | File size | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Format | format | Product format description | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
Filename | filename | File name | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ | ☑ |
More information on the source of the respective attributes can be found directly by looking at the OWL file itself.
In contrast to all other attributes, the footprint coordinates are extracted from the binary data file (DBL) in case of the SIR_FDM_2_ product and from the netCDF file for all other products. For the SIR_FDM_2_ product, the cortex topic (separate package) uses an XML schema definition file to create a tree of nodes which is then navigable within the addon OWL. This functionality is already provided for netCDF files by using the DRB netCDF extension in the topic class definition.
The generation of the footprints is based on the following sources:
- SIR_FDM_2_: Latitude and Longitude of measurement (Section 8.27 in CryoSat Product Handbook)
- Others: 1 Hz Latitude (lat_01) and Longitude (lon_01) (Section 3.1 in CryoSat Ice netCDF L2 Product Format Specification)
The values are provided in the unit of 1e-1 microdegrees and need to be scaled accordingly. Furthermore, longitudes need to be converted from the (0-360) range to the (-180 to 180) range.
The coordinates provided are the orbit coordinates. A continuous polygon having a fictional width of 1 millidegree was chosen to represent the footprint (defined by the offset variable in the OWL).
The number of points per polygon needs to be small enough for the DHuS to be able to handle it. A total number of approximately 400 points was chosen.