The DHuS addon is a Java package that contains the definitions and extraction rules and operations for the Envisat products. The central element of this package is the ontology definition file (aeolus.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 Envisat satellite mission:
- ASPS products (AMI sensor)
- ASPS20.H
- ASPS20.N
- ATSR sensor
- AT1_AR__2P
- AT1_NR__2P
- AT1_TOA_1P
- AT2_AR__2P
- AT2_TOA_1P
- AT2_NR__2P
- RA sensor
- ERS_ALT_2_
- ERS_ALT_2M
- ERS_ALT_2S
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 | ASPS | ATSR | RA |
---|---|---|---|---|---|
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 | ☐ | ☑ | ☐ |
Processing level | processinglevel | The value of the last processing | ☑ | ☑ | ☑ |
Processing center | processingcenter | Processing center ID | ☑ | ☐ | ☑ |
Generation time | - | Product generation date | ☑ | ☐ | ☑ |
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.
The footprint coordinates are extracted from the mixed ASCII/binary data file (E1/E2) or the netCDF (nc) fil, depending on the product. For the E1/E2 files, 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:
- ASPS: Latitude (lat) and Longitude (lon) variables in netCDF (Table 9 in ASPS Product Format)
- ATSR AR: Latitude and Longitude of the SST Record 30 arc minute cell MDS (Section 7.5.3.8.4 in ENVISAT-1 PRODUCTS SPECIFICATIONS, VOLUME 7: AATSR PRODUCTS SPECIFICATIONS)
- ATSR NR and TOA: Tie point latitudes and longitudes (Table 7.4.1.7.2-1 in ENVISAT-1 PRODUCTS SPECIFICATIONS, VOLUME 7: AATSR PRODUCTS SPECIFICATIONS)
- RA: Latitude (lat) and Longitude (lon) variables in netCDF (Section 5.3.4 and 5.3.5 in REAPER Product Handbook for ERS Altimetry Reprocessed Products)
For the following products, the values are provided in the unit of microdegrees and need to be scaled accordingly:
- ATSR
- RA
The coordinates within the ASPS products are given in the unit of millidegrees.
Furthermore, longitudes need to be converted from the (0-360) range to the (-180 to 180) range for all products.
The ASPS footprint covers one full orbit. The width of the swath is based on the coordinates given by the netCDF variables.
The ATSR AR product contains the pixel coordinates of all pixels along one orbit. The pixel width is 0.5 degrees and there are on average 10 pixels per row. The footprint is calculated by taking the average of the coordinates of every 200 pixels. The width of the swath is 500 km.
For the ATSR NR and TOA products, the width of the swath is based on the coordinates given in the data set records.
For the RA products, 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.