Commit 8859d230 authored by Carlos H. Brandt's avatar Carlos H. Brandt
Browse files

Add CRISM to DMP doc

parent 11d68724
# NEANIAS Planetary Data Management Plan
**_What is the purpose of the data collection/generation and its relation to the objectives of the project?_**
The Planetary group of NEANIAS, under NEANIAS-Space working group, will provide imagery analysis
tools of highly demanded planetary bodies -- Mars and the Moon. For simplicity, hereafter called _bodies_. The goal is to scale up services we have developed during recent years to a larger audience,
......@@ -17,44 +15,40 @@ _Geolocation_ is the primary feature of our data. Database systems capable of ma
In the following sections, we provide the list of data sets to be handled, followed by their description,
and the interface to users and internal system components. As the project evolves, the content of this document will evolve accordingly as to accommodate the details of our data software system.
## Datasets
Sources of our data are mostly PDS ( [ref_pds] ) data archives. See section [PDS][#PDS] for a general description of a PDS archive.
### Datasets
Sources of our data are mostly PDS ( [ref_pds] ) data archives:
* dataset: [MEX HRSC DTM and Nadir imagery](/datasets/MEX/HRSC/
* dataset: [MEX HRSC](#mex-hrsc)
* archive: PDS3
* format: PDS IMAGE (array)
* source: ESA, NASA
* volume: 5 TB 
* dataset: [MRO CRISM](/datasets/MRO/CRISM/
* dataset: [MRO CRISM](#mro-crism)
* archive: PDS3
* format: PDS IMAGE (cube)
* source: NASA
* volume: 20 TB
* dataset: [MRO HiRISE](/datasets/MRO/HiRISE/
* dataset: [MRO HiRISE](#mro-hirise)
* archive: PDS3
* format: PDS IMAGE (array)
* source: NASA
* volume: 20 TB
* dataset: [MRO CTX](/datasets/MRO/CTX/
* dataset: [MRO CTX](#mro-ctx)
* archive: PDS3
* format: PDS IMAGE (array)
* source: NASA
* volume: 10 TB 
* dataset: [LRO LROC](/datasets/LRO/LROC/
* dataset: [MGS MOLA + KAGUYA](#mgs-mola-+-kaguya)
* archive: PDS3
* format: PDS IMAGE (array)
* source: NASA
* volume: 10 TB
* dataset: [MRO MOLA + KAGUYA](/datasets/MRO/MOLA/
* volume: 2 TB
* dataset: [LRO LROC](#lro-lroc)
* archive: PDS3
* format: PDS IMAGE (array)
* source: NASA
* volume: 2 TB
* volume: 10 TB 
#### TBD:
......@@ -86,7 +80,143 @@ Total amount of source data is around 80TB.
### FAIR Data
The High Resolution Stereo Camera (HRSC), on board of Mars Express (, provide high resolution images over almost the entire surface of Mars in different wavelengths.
HRSC level-4 data are going to be used: DTM models and Nadir images. The data is available through a PDS archive. Data is provided as monochromatic 2D PDS IMAGE arrays, with metadata in PDS LABEL format as the image's header.
* Dataset ID: `MEX-M-HRSC-5-REFDR-DTM-V1.0`
* Dataset URL:
* ``
* ``
* Data format: `PDS IMAGE`. `PDS LABEL` content are attached to `IMAGE` as `HEADER`
* Products of interest: DTM-Sphere (`DT`), DTM-Areoid (`DA`), Nadir observations (`ND`)
* Data products volume: 10TB
#### Data archive summary
The data -- _i.e._, images -- are organized in sub-directories under the archive's `data/` directory. Each sub-directory represents the mission's orbit they were taken. PNG images are provided for quick view of data content under the archive's `browse/` directory.
##### File naming
The image files in the DATA directories follow this convention:
> * `OOOO` 4 digit orbit number
> * `MMMM` number of the image in this orbit
> * `DD` sensor name (can be `ND,BL,GR,IR,RE,DT,DA`)
> * The `4` indicates the level of processing which is archived in PSA/PDS
The image data of our interest are those which `DD` values:
* `ND` (Nadir sensor)
* `DT` (MOLA Sphere DTM)
* `DA` (MOLA Areoid DTM)
##### Coordinates reference system
All latitudes and longitudes are given in degrees, latitudes are planetocentric. The level 4 products will be projected onto a SPHERE in authalic/conformal projection (sphere formulae with planetocentric latitude) using radius of the MOLA sphere (3396.0 km):
> * If the latitude center of the image is between -85° and +85°: **Sinusoidal** projection center latitude = 0, center longitude will be determined automatically using an integer value
> * If the latitude center of the image is < -85° or > +85°: **Stereographic** projection, center latitude = +/- 90°, center longitude=0°
### MGS MOLA + Kaguya
Mars Orbiter Laser Altimeter (MOLA) was an experiment on board of the Mars Global Surveyor dedicated to collect altimetry data, eventually used to create topographic maps of Mars.
We are going to use the Mission Experiment Gridded Data Record (MEGDR), which are topographic maps based on altimetry data accumulated over the whole (MOLA) mission. Data is provided as monochromatic 2D PDS IMAGE arrays accompanied by the respective PDS LABEL metadata file.
* Dataset ID: `mgs-m-mola-5-megdr-l3-v1`
* Dataset URL: ``
* Data format: `PDS IMAGE` + `PDS LABEL`
* Data volume: 20TB
#### Data archive summary
MEGDR products are images gridded at several resolutions: 4, 16, 32, 64, and 128 pixels per degree. These images provide maps of the global topography of Mars. In addition, maps with resolutions of 128, 256 and 512 pixels per degree are included for the north and south polar regions of Mars. For each map resolution, the data set contains images of planetary radius, topography, and the number of MOLA shots within a grid cell (referred to as counts). Topography is computed as the planetary radius minus the areiod raduis. Images of the Mars areoid are provided at resolutions of 4, 16, and 32 pixels per degree.
Products are grouped according to their resolution, at the top of the archive structure the directories `meg004/`, `meg016/`, `meg032`, `meg064/`, and `meg128/` for the global maps, and `polar/` for the polar maps.
##### File naming
> File names for the global image maps use the format of `MEGpxxnyyyrv.IMG` with the following definitions:
> - `p` indicates the product type (A for areoid, C for counts, R for radius, and T for topogray)
> - `xx` is the latitude of the upper left corner of the image
> - `n` indicates whether the latitude is north (N) or south (S)
> - `yyy` is the east longitude of the upper left corner of the image
> - `r` is the map resolution using the pattern
> - `c` = 4 pixel per degree
> - `e` = 16 pixel per degree
> - `f` = 32 pixel per degree
> - `g` = 64 pixel per degree
> - `h` = 128 pixel per degree
> - `i` = 256 pixel per degree
> - `j` = 512 pixel per degree
> - `v` is a letter indicating the product version
> The file naming scheme used for the polar maps is `MEGT_p_rrr_v.IMG`:
> * `p` is replaced by `N` for north pole or `S` for south pole
> * `rrr` is replaced by 128, 256 or 512
> * `v` is the product version
##### Coordinates reference system
The global maps are in **simple cylindrical** map projections using the IAU2000 planetocentric coordinate system with east positive longitude.
The polar maps are stored in polar **stereographic** projections.
The Mars Reconnaissance Orbiter hosted a number of instruments we will make use of their data, the Compact Reconnaissance Imaging Spectrometer for Mars (CRISM) is one of them. CRISM is capable of observing Mars in many different wavelength, it generated _multi-_ and _hyper-spectral_ data depending on its operation mode (_untargeted_ and _targeted_).
CRISM Targeted Reduced Data Record (TRDR) is the primary dataset in use. The data is available through a PDS3 archive, it is composed by 3D PDS IMAGE-CUBES and metadata in PDS LABEL files.
* Dataset ID: `mro-m-crism-3-rdr-targeted-v1`
* Archive URL: ``
* Data format: `PDS CUBE` + `PDS LABEL`
* Data volume: 30TB
#### Data archive summary
In the `Archive URL` we will have access to different release datasets, directories are named as `mrocr_21xx/` where `xx` is the number of the release (13, currently). Data products are stored at `./<dataset>/YYYY/YYYY_DDD/<products>/`:
* `<dataset>` is the dataset acronym, `trdr`, `ddr` ;
* `YYYY` and `DDD` are _year_ and the _day_ of the year the observation started;
* `<products>` named after class type and observation ID unique to a single observation.
##### File Naming
Under `<products>`, directories separate sets of products according to the observation resolution, an unique ID, and affixes identifying data source, type of measurement reported and other attributes coded to fit in a filename. The details of TRDR products filenaming convention are rather long and I understand does not fit here in this document; the reader is invited to read the section `3.2.5` of document [crism_avsis]( for the details.
##### Coordinates reference system
TRDR images are in sensor space, projection to a Mars coordinates is done on our systems with the use of DDR data.
## FAIR Data
Key components, and observations, towards a better use of the services and data provided:
* Findable: Publish data on indexes like Virtual Obervatories (IVOA) and OGC Catalogue service, as well as a clear _Data Access_ HTML interface under NEANIAS web portal (well indexed by search engines, _e.g._, Google);
......@@ -159,6 +289,9 @@ Compositional data from multi- and hyperspectral imagers (mostly for Mars, the M
* Jupyter Notebook, for interactive lower-level data analysis.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment