< Back to ODE Help Main Page

ODE - Frequently Asked Questions

What is ODE?
What are the System Requirements to use ODE?
What is PDS?
What are PDS Archives? / What is a Data Set?
What are Data Products?
What is a Product Id?
What is a Product Type?
Are products the same as files?
What is in the ODE Database?
Are products and files free?
Coordinate System?
What are derived files?
What are Footprints?
What are KML files?
What are shape files?
What are Footprint Product Coverage Maps and How Do I Use Them?
How do I add products to my cart?
How do I download products and/or files?
Tell me more about the missions, instruments and products
Why are there differences between HiRISE, CTX, MCS, MOC and the other ODE products? (ODE Mars)
What are Coordinated Observations? (ODE Mars)
 
What is ODE?
Planetary Data System (PDS) Geosciences Node's Orbital Data Explorer (ODE) provides map and forms-based search, retrieve, and order function for PDS for PDS-compliant archives from a variety of spacecraft instrument observations. Mars ODE includes observations from Mars Reconnaissance Orbiter (MRO), the European Space Agency's Mars Express (MEX), and the Mars Global Surveyor (MGS). The MRO mission is characterized by very high data volumes and complex observation plans relative to previous planetary missions. Mercury ODE includes observations from the MESSENGER spacecraft. Lunar ODE includes observations from the Clementine, Lunar Prospector, and, when released, the Lunar Reconnaissance Orbiter (LRO). ODE is designed to augment the existing PDS search and retrieval interface by providing advanced search, retrieve, and order tools, integrated analysis tools, and visualization tools. br>

ODE consists of a web site, a metadata database, and a background processor. The background processor extracts PDS product metadata from the PDS archives and organizes it into a searchable database. The ODE web site provides a tool for searching and exploring these metadata as well as accessing and downloading the PDS archives themselves. The primary audience of the website is the science community, but anyone is welcome to use the website.
The ODE website complements the PDS Imaging Node 's Atlas website by providing cross mission and instrument searches for imaging and non-imaging data products. The Atlas website includes the MRO-specific image search capability.

What are the System Requirements to use ODE?
Windows
  • Google Chrome Beta
  • Firefox 2.0 and above
  • Internet Explorer 6.0 and above
  • Netscape 9.0 and above
  • Safari 3.2 and above
Mac OS X
  • Camino 1.0 and above
  • Firefox 2.0 and above
  • Netcape 9.0 and above
  • Safari 3.2 and above
Linux
  • Firefox 2.0 and above
Browser Settings
  • Browser must have Flash enabled
  • Browser must have Java and JavaScript enabled
  • Browser must have Cookies enabled
  • Screen Resolution: 1024x768 or higher recommended
  • Be sure that pop-up blocker software is disabled
Browser Troubleshooting

What is PDS?
NASA's Planetary Data System (PDS) archives and distributes scientific data from NASA planetary missions, astronomical observations, and laboratory measurements. The PDS is sponsored by NASA's Science Mission Directorate. Its purpose is to ensure the long-term usability of NASA data and to stimulate advanced research. PDS is continually upgrading and updating its archives, to better serve the needs of its user communities. Learn more about PDS.

PDS Nodes - The Best of Planetary Data!

The PDS includes seven university/research center science teams, called discipline nodes. These nodes specialize in specific areas of planetary data. The contributions from these nodes provide a data-rich source for scientists, researchers and developers. You can visit them through the links on the PDS Home Page. You will learn more about the archives of each node, and about the education and public outreach services that these nodes provide.

What are PDS Archives? / What is a Data Set?
Planetary science data stored in PDS are organized by data sets. A data set is a collection of related data products, usually data products acquired by a particular instrument and processed in a certain way. Each data product within a data set is of a given product type and has a unique product id. The data set also includes all documentation and supporting materials needed to understand and use the data products. Data sets are stored in volumes.
What are Data Products?
A data product is a set of measurements resulting from a science observation, usually stored in one file. For example, an image, a spectrum, and a time series table of measurements are data products. A data product has a PDS label that contains metadata about a product such as when and where the data were collected, what the data contain, and as how the data are organized. These labels are either detached files or attached to at the beginning of a data product file. More information about data products can be found in the PDS documentation here.

What is a Product Id?
Each PDS data product has a Product Identifier (Product Id). The product id is a permanent, unique identifier assigned to a data product by its producer. The product id is unique within a data set. The product id is a character string up to 40 characters in length. Many producers embed information about the product in the product id. For example, the product ids of HiRISE data products include both the mission phase and the orbit number in which the data product was generated.

What is a Product Type?
Each data product is of a single Product Type. A product type identifies the type or category of a data product within a data set. For example, raw observation data products usually have a product type of "Experimental Data Record" or EDR for short. Other examples include "Reduced Data Record" (RDR for short), DOCUMENT, CALIBRATION, ANCILLARY, or VALIDATION_REPORT.

Are products the same as files?
A data product is usually stored in one file, but some data products are stored in multiple files with a single PDS label.


What is in the ODE Database?
At the heart of ODE is a database. The ODE backend loads this database with information from the PDS archives. The ODE web site allows users to search, explore, and access this data. The database consists of several components:
  • Metadata Database - A SQL Database storing product and archive metadata
  • File set including:
  • Expanded Product Labels
  • Browse and Thumbnail Images
  • Zoom and Pan Versions of Selected Browse Images
  • Derived Files
  • Geographical Maps
The metadatabase stores information about the PDS archives and products. Fundamentally, the database is organized into four major components:
  • Dataset and Volume Information - Information about the PDS datasets and archive volumes that is accessible via ODE.
  • Product Information - Information about each PDS data product including product metadata extracted from the products label along with information about what files in the archive store the product information, what PDS node the product is stored at, how to access the actual product files, etc.
  • Directory/File Information - Information about each data set's volume directories and files. This is distinct from the product information's product file data. Rather, the directory/file information is used to provide a user with a directory or FTP like view of the archives including archive files that are not part of the product.
  • Coordinated Observation Information - Information about coordinated observations and which products are correlated to each observation.
Are products and files free?
Yes. PDS data is freely available to the public.

Coordinate system?
All product coordinates in ODE are stored in planetocentric, positive longitude east, 0 to 360 degrees. ODE uses a variety of methods to obtain a location for a product. Different products require different methods. The method used for a particular product can be found under the product results page, metadata tab, at the bottom under ODE notes. NOTE: coordinates are for searching and display only and may vary in precision. Users should explore and understand the data set to determine how to precisely map the product.

A range of disparate coordinate systems were used for planetary data from different missions stored in PDS, which makes it difficult to search and correlate data from various instruments. Currently, all products in ODE are stored in planetocentric, positive longitude east, 0 to 360 degrees coordinates (Tables 1-3). ODE uses a variety of methods to obtain a location for different products. Most of the data coordinates stored in ODE are acquired from the attached or detached PDS labels. ODE also has data coordinates acquired from the Unified Planetary Coordinates (UPC) database. The method used for a particular product can be found under the product results page, metadata tab, at the bottom under ODE notes. NOTE: coordinates are for searching and display only and may vary in precision. Users should explore and understand the data set to determine how to precisely map the product.
The UPC project was carried out at the U. S. Geological Survey (USGS) and Jet Propulsion Laboratory (JPL). It provides easy access to planetary data in a set of unified, consistent coordinate systems (Becker et al., 2007), which is also consistent with the MRO and MOLA data.
The Planetocentric system has an origin at the center of mass of the body. The planetocentric latitude is the angle between the equatorial plane and a vector connecting the point of interest and the origin of the coordinate system. Latitudes are defined to be positive in the northern hemisphere of the body, where north is in the direction of Earth's angular momentum vector, i.e., pointing toward the hemisphere north of the solar system invariant plane. Planetocentric longitude is measured around the equator of the body from a prime meridian defined and adopted by international agreement. Longitudes increase toward the east making the Planetocentric system right-handed. Radius is the distance from the planetary body's center of mass to the point of interest.
A spheroid usually approximates well to the shape of planets, because the shape of a rotating body in hydrostatic equilibrium is approximately a spheroid. Mapping parameters for different planetary bodies (Mars, Moon, Mercury, and Venus) are listed in Table 1 (Seidelmann et al., 2002; 2005). The first column gives the mean radius of the body. The standard errors of the mean radii indicate the accuracy of determination of these parameters due to inaccuracies of the observational data. The second and third columns give equatorial and polar radii for 'best-fit' spheroids. An ellipsoid has been adopted for Mars by the IAU with a polar radius of 3376.2 km and an equatorial radius of 3396.19 km. For Moon, Mercury, and Venus, a sphere is used as the reference surface.
Table 1. Mapping Parameters (unit: km)
Planet Mean Radius Equatorial Radius Polar Radius
Mars 3389.5±0.2 3396.19±0.1 AVG 3376.2±0.1
N 3373.19±0.1
S 3379.21±0.1
Moon 1737.4±1 1737.4±1 1737.4±1
Mercury 2439.7±1.0 2439.7±1.0 2439.7±1.0
Venus 6051.8±1.0 6051.8±1.0 6051.8±1.0
Most of the basemaps stored in ODE are provided by USGS. Map projection is based on spheres rather than ellipsoids for these basemaps because of the computational cost and the capabilities of commercial software applications. The adopted projection convention for these basemaps includes Equirectangular (also named Simple Cylindrical) and Polar Stereographic map projections. The global maps are in Equirectangular map projections using the IAU2000 planetocentric coordinate system with east positive longitude. The polar maps are stored in polar stereographic projections.
The Equirectangular projection (Snyder, 1987) is typically used at middle and lower latitudes. With this projection, all lines of latitude are parallel to one another, as is also the case with longitude lines. Parallels of latitude and meridians of longitude are straight lines that are perpendicular to one another. This map projection is centered on the equator. The map resolution is constant throughout the image. The Polar Stereographic projection (Snyder, 1987), ideal for maps covering the polar regions, minimizes scale and shape distortion at high latitudes. This projection is centered on the north or south pole. Lines of longitude extend radially from the pole, and parallels of latitude are concentric circles around the center. For Mars, the Polar Stereographic projection is approximated by adopting a spherical geometry with a polar radius of 3376.2 km.
More information on how to predefine ArcGIS projection files can be found in the USGS's web of Planetary Interactive GIS on-the-Web Analyzable Database (PIGWARD). Projection files can be downloaded from the PIGWARD and ODE web.
Table 2. Reference System Used for Mars Data in Different Missions

Mission

Instrument

Data_Set_ID

Product_Type

Reference System Used in Archive

MRO

CRISM

MRO-M-CRISM-2-EDR-V1.0

EDR

IAU2000 planetocentric reference system with east longitude (0-360?) being positive (r = 3396.19 km)

MRO-M-CRISM-4/6-CDR-V1.0

CDR (contains calibration files used to process EDRs to units of radiance or I/F)

N/A

MRO-M-CRISM-6-DDR-V1.0

DDR

IAU2000 planetocentric

MRO-M-CRISM-3-RDR-TARGETED-V1.0

TARGETED_RDR

IAU2000 planetocentric

MRO-M-CRISM-5-RDR-MULTISPECTRAL-V1.0

MAP_PROJECTED_MULTISPECTRAL_RDR

IAU planetocentric system with east longitude being positive    (r = 3396.0 km)

MRO-M-CRISM-5-RDR-MPTARGETED-V1.0

MTRDR (not available yet)

IAU2000 planetocentric

CTX

MRO-M-CTX-2-EDR-L0-V1.0

EDR

Image coordinates (Lat, Lon) were computed using NAIF SPICE kernel by MSSS personnel or NAIF

MARCI

MRO-M-MARCI-2-EDR-L0-V1.0

EDR

Using NAIF SPICE kernel

HIRISE

MRO-M-HIRISE-2-EDR-V1.0

EDR

N/A

MRO-M-HIRISE-3-RDR-V1.0

RDR (without the embedded map projection information)

IAU2000 planetocentric

MRO-M-HIRISE-3-RDR-V1.1

RDRV11 (with the embedded map projection information)

IAU2000 planetocentric

MCS

MRO-M-MCS-2-EDR-V1.0

EDR

IAU2000 planetocentric

MRO-M-MCS-4-RDR-V1.0

RDR

Planetocentric spherical coordinates

MRO-M-MCS-5-DDR-V1.0

DDR (not ready, not being peer reviewed)

Planetocentric spherical coordinates

RSS

MRO-M-RSS-1-MAGR-V1.0

EDR

SPK and CKF files can be converted to a wide range of coordinate frames by the NAIF reader routines. Other data types are not dependent on definition of a coordinate system.

SHARAD

MRO-M-SHARAD-3-EDR-V1.0

EDR

IAU2000 planetocentric reference ellipsoid

MRO-M-SHARAD-4-RDR-V1.0

RDR

Mars Express (MEX)

HRSC

MEX-M-HRSC-3-RDR-V2.0

RDR

N/A

MEX-M-HRSC-5-REFDR-MAPPROJECTED-V2.0

REFDR (map projected image data)

Planetographic spherical coordinates with east longitude being positive (r = 3396.19 km)

MEX-M-HRSC-5-REFDR-DTM-V1.0

REFDR_DTM

Planetocentric spherical coordinates with east longitude being positive (r = 3396.0 km)

SPICAM

MEX-Y/M-SPI-2-IREDR-RAWXCRUISE/MARS-V1.0

EDR

IAU1988 reference ellipsoid     (re = 3397.0 km; rp = 3375.0 km)

MEX-Y/M-SPI-2-UVEDR-RAWXCRUISE/MARS-V1.0

EDR

MRS

MEX-M-MRS-1/2/3-NEV-0001-V1.0

N/A

N/A

MARSIS

MEX-M-MARSIS-2-EDR-V1.0

EDR

Planetocentric coordinates

MEX-M-MARSIS-3-RDR-SS-V1.0

RDR (MEX MARS MARSIS REDUCED DATA RECORD SUBSURFACE V1.0)

Planetocentric coordinates

MEX-M-MARSIS-3-RDR-AIS-V1.0

RDR (MEX MARS MARSIS RDR ACTIVE IONOSPHERE SOUNDING V1.0

Measurements of wave electric fields, which are presented as detected by the sensors and are not rotated into any other coordinate system.

OMEGA

MEX-M-OMEGA-2-EDR-FLIGHT-V1.0

EDR

IAU2000 planetocentric

MEX-M-OMEGA-2-EDR-FLIGHT-EXT1-V1.0

EDR

IAU2000 planetocentric

PFS

MEX-M-PFS-2-EDR-NOMINAL-V1.0

EDR

N/A

MEX-M-PFS-2-EDR-EXT1-V1.0

EDR

N/A

Mars Odyssey

GRS

ODY-M-GRS-2-EDR-V1.0

EDR

IAU2000 planetocentric

ODY-M-GRS-5-AHD-V1.0

AVERAGED_HEND_DATA (AHD)

ODY-M-GRS-5-AND-V1.0

AVERAGED_NEUTRON_DATA (AND)

ODY-M-GRS-5-SGS-V1.0

SUMMED_GAMMA_SPECTRA (SGS)

ODY-M-GRS-4-DHD-V1.0

DERIVED_HEND_DATA (DHD)

ODY-M-GRS-4-DND-V1.0

DERIVED_NEUTRON_DATA (DND)

ODY-M-GRS-4-CGS-V1.0

CORRECTED_GAMMA_SPECTRA (CGS)

ODY-M-GRS-5-ELEMENTS-V1.0

ELEMTS - Element Concentrations

N/A

THEMIS

 

VIS-EDR; IR-EDR; VIS-RDR; IR-RDR; VIS-ABR; IR-BTR

IAU2000 planetocentric

MARIE

ODY-M-MAR-2-REDR-RAW-DATA-V1.0

REDRs

MARIE's internal coordinate system is defined by the geometry of the detector. The PSDs have their own coordinate system in the sense that each strip (corresponding to a row or a column) is assigned a sequential number from 1 to 24. These values are not referenced to any other coordinate system, as the primary purpose of the PSDs is to calculate the angle at which incident particles traverse the silicon detectors.

ODY-M-MAR-3-RDR-CALIBRATED-DATA-V1.0

RDRs

Radio Science

ODY-M-RSS-1-RAW-V1.0

AGK/ion/ODF/opt/sak/sff/soe/spk/tck/tnf/tro/wea

SPK, TCK, and SAK files can be converted to a wide range of coordinate frames by the NAIF reader routines. Other data types are not dependent on definition of a coordinate system.

Accelerometer

(not available yet)

 

 

Mars Global Surveyor (MGS)

MOC-NA / MOC-WA

MGS-M-MOC-NA/WA-2-DSDP-L0-V1.0

NADSDP / WADSDP

IAU1994 planetographic reference system                        (re = 3397.0 km; rp = 3375.0 km)

MGS-M-MOC-NA/WA-2-SDP-L0-V1.0

NASDP / WASDP

MOLA

MGS-M-MOLA-3-PEDR-L1A-V1.0

PEDR

IAU2000 planetocentric             (r = 3396.0 km)

MGS-M-MOLA-5-MEGDR-L3-V1.0

MEGDR - Mission Experiment Gridded Data Record

IAU2000 planetocentric (Davies et al., 1994; Duxbury et al., 2001; Seidelmann et al., 2002)

MGS-M-MOLA-5-SHADR-V1.0

SHADR

IAU 1991 (Davies et al., 1992), planetocentric, with longitudes measured positive east.

MGS-M-MOLA-3-PRDR-L1A-V1.0

PRDR

IAU2000 planetocentric
Note:
Table 3. Reference System Used for Moon Data in Different Missions

Mission

Instrument

Data_Set_ID

Product_Type

Reference System Used in Archive

 

Clementine

 

HIRES

CLEM1-L-H-5-DIM-HIRES-V1.0

MDIM

Planetographic spherical coordinates with r = 1737.4 km       

HIRES/LWIR/NIR/UVVIS/A-STAR/B-STAR

CLEM1-L/E/Y-A/B/U/H/L/N-2-EDR-V1.0

EDR

Planetocentric

UVVIS

CLEM1-L-U-5-DIM-BASEMAP-V1.0

MDIM 5-Band Mosaic

Planetographic spherical coordinates with r = 1737.4 km

CLEM1-L-U-5-DIM-UVVIS-V1.0

MDIM Global Basemap Mosaic

LIDAR

CLEM1-L-LIDAR-3-TOPO-V1.0

TOPO Raw Data

N/A

CLEM1-L-LIDAR-5-TOPO-V1.0

TOPO

Planetocentric (Williams et al., 1993; Dickey et al., 1994)

RSS

CLEM1-L-RSS-1-BSR-V1.0

Raw Data Record

SPK ephemeris files and CK attitude files are produced for the J2000 inertial reference frame. SPICE reader routines may be used to convert these to other coordinate systems. Other data types are not dependent on definition of a coordinate system.

CLEM1-L-RSS-5-BSR-V1.0

RDR

Planetocentric system with positive east longitude (r = 1737.4 km)

CLEM1-L-RSS-5-GRAVITY-V1.0

GRAVITY

Planetocentric (Davies et al., 1992)

LWIR

CLEM1-L-LWIR-3-RDR-V1.0

RDR

Planetocentric

Lunar Prospector (LP)

{GRS, NS, APS, MAG, ER}

LP-L-ENG/GRS/NS/APS/MAG/ER-1-MDR-V1.0

MDR

Selenocentric/selenographic

GRS

LP-L-GRS-3-RDR-V1.0

RDR

N/A

NS

LP-L-NS-3-RDR-V1.0

RDR

N/A

RSS

LP-L-RSS-5-GRAVITY-V1.0

GRAVITY

Planetocentric system with positive east longitude (r = 1738.0 km) (Newhall and Williams, 1997)

LP-L-RSS-5-LOS-V1.0

LOS

Planetocentric system (Newhall and Williams, 1997)

MAG

LP-L-MAG-4-SUMM-LUNARCRDS-5SEC-V1.0

Magnetic field data from LP MAG

in two different coordinate systems: selenocentric solar ecliptic (SSE) and body-fixed selenographic (SEL)

LP-L-MAG-4-LUNAR-FIELD-TS-V1.0

LP MAG Level 2 Data (CODMAC Level 4): Lunar Magnetic Field Time Series V1.0   

in two coordinate systems: selenographic (SG) coordinates; and east, north, and radial (ENR) coordinates

LP-L-MAG-5-LUNAR-FIELD-BINS-V1.0

LP MAG Level 3 Data (CODMAC Level 5): Lunar Magnetic Field Bins V1.0

Measurements in east, north, and radial (ENR) coordinates

LP-L-MAG-5-SURFACE-FIELD-MAP-V1.0

LP MAG Level 4 Data (CODMAC Level 5): Surface Magnetic Field Maps V1.0

Selenographic with mean lunar radius (1738 km)

ER

LP-L-ER-4-SUMM-OMNIDIRELEFLUX-V1.0

low resolution data from LP ER

N/A

LP-L-ER-3-RDR-HIGHRESFLUX-V1.0

high resolution data from LP ER

N/A

LP-L-ER-3-RDR-3DELEFLUX-80SEC-V1.0

3-D spectrum data from LP ER 

in ''despun spacecraft'' (SCD) coordinates, closely related to GSE coordinates.

LP-L-ER-4-ELECTRON-DATA-V1.0

LP ER Level 2 Data (CODMAC Level 4)

N/A
Note:
Table 4. Reference System Used for Mercury Data in Different Missions

Mission

Instrument

Data_Set_ID

Product_Type

Reference System Used in Archive

MESSENGER

EPPS (EPS/FIPS)

MESS-E/V/H/SW-EPPS-2-EPS-RAWDATA-V1.0

DATA

Planetocentric

MESS-E/V/H/SW-EPPS-2-FIPS-RAWDATA-V1.0

DATA

Planetocentric

MAG

MESS-E/V/H/SW-MAG-2-EDR-RAWDATA-V1.0

DATA/ ENGINEERING_DATA (EDR)

N/A (just some uncalibrated sensor measurements)

MESS-E/V/H/SW-MAG-3-CDR-CALIBRATED-V1.0

CDR

Spacecraft (SC) CDR: in sensor and spacecraft coordinates.        

J2000 (J2K) CDR: in J2000 coordinates.

Mercury Solar Orbital (MSO) CDR: in Mercury solar orbital coordinates.

Mercury Body Fixed (MBF) CDR: in Mercury body fixed coordinates.            

Radial-Tangential-Normal (RTN) CDR: in RTN coordinates.    

GRS

MESS-E/V/H-GRNS-2-GRS-RAWDATA-V1.0

DATA/ANCILLARY

N/A, SPICE kernels will be archived at the PDS NAIF node. Coordinate systems will be included in the appropriate RDR SIS documents.

NS

MESS-E/V/H-GRNS-2-NS-RAWDATA-V1.0

EDR/DATA/ ANCILLARY

N/A, SPICE kernels will be archived at the PDS NAIF node. Coordinate systems will be included in the appropriate RDR SIS documents.

MLA

MESS-E/V/H-MLA-2-EDR-RAWDATA-V1.0

DATA/ANCILLARY

N/A

MASCS

MESS-E/V/H-MASCS-2-UVVS-EDR-V1.0

EDR

Planetocentric

MESS-E/V/H-MASCS-2-VIRS-EDR-V1.0

EDR

Planetocentric

XRS

MESS-E/V/H-XRS-2-EDR-RAWDATA-V1.0

DATA

Planetocentric

RSS

MESS-V/H-RSS-1-EDR-RAWDATA-V1.0

ODF/TNF

SPK and CKF files can be converted to a wide range of coordinate frames by the NAIF reader routines. Other data types are not dependent on definition of a coordinate system.

MDIS-NAC / MDIS-WAC

MESS-E/V/H-MDIS-2-EDR-RAWDATA-V1.0

EDR

IAU2000 planetocentric system with east longitude being positive

MDIS-NAC / MDIS-WAC

MESS-E/V/H-MDIS-4-CDR-CALDATA-V1.0

CDR

IAU2000 planetocentric
Note:
Related documents:
  1. Becker, K.J., L.R. Gaddis1, L.A. Soderblom, J.A. Anderson, J.M. Barrett, T.L. Becker, T.M. Hare, S.C. Sides, D.L. Soltesz, A. Stanboli, R.M. Sucharski, T.L. Sucharski, and K.N. Winfree (2007), The Unified Planetary Coordinates Database, 38th Lunar and Planetary Sciences Conference, March 12 - 16, 2007. League City, Texas. (abstract) [Url: http://www.lpi.usra.edu/meetings/lpsc2007/pdf/2022.pdf].
  2. Davies, M.E., V.K. Abalakin, A. Brahic, M. Bursa, B.H. Chovitz, J.H. Lieske, P.K. Seidelmann, A.T. Sinclair, and Y.S. Tjuflin (1992), Report of the IAU/IAG/COSPAR working group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 1991, Celestial Mechanics and Dynamical Astronomy, 53, pp. 377-397.
  3. Davies, M.E., V.K. Abalakin, M. Bursa, J.H. Lieske, B. Morando, D. Morrison, P.K. Seidelman, A.T. Sinclair, B. Yallop, and Y.S. Tjuflin (1994), Report of the IAU/IAG/COSPAR Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites, Celestial Mechanics and Dynamical Astronomy 63, pp. 127-148.
  4. Dickey, J., J.E. Faller, X.X. Newhall, R.L. Ricklefs, J.G. Ries, P.J. Shellus, C. Veillet, A.L. Whipple, J.R. Wiant, J.G. Williams, and C.F. Yoder (1994), Lunar Laser Ranging: A Continuing Legacy of the Apollo Program, Science, 265, pp. 482-490.
  5. Duxbury, T.C., R. Kirk, and B.A. Archinal (2001), Mars Geodesy/Cartography Working Group recommendations on Mars cartographic constants and coordinate systems, International Society for Photogrammetry and Remote Sensing, WG IV/9: Extraterrestrial Mapping Workshop "Planetary Mapping 2001", USGS, Flagstaff, Arizona.
  6. Hare, T.M. (2008), ArcMap 8.x and 9.x Planetary Projection Tutorial 14 [Url: http://webgis.wr.usgs.gov/pigwad/tutorials/planetarygis/arcmap_projections.htm].
  7. LRO Project (2008), A Standardized Lunar Coordinate System for the Lunar Reconnaissance Orbiter, LRO Project White Paper, version 4 of May 14 [Url: http://lunar.gsfc.nasa.gov/library/451-SCI-000958.pdf].
  8. Newhall, X.X., and J.G. Williams (1997), Estimation of the Lunar Physical Librations, Celestial Mechanics and Dynamical Astronomy, 66, pp. 21-30.
  9. Planetary Science Data Dictionary Document, JPL D-7116, Rev. E, August 28, 2002.
  10. Seidelmann, P. K. (Chair), V.K. Abalakin, M. Bursa, M.E. Davies, C. De Bergh, J.H. Lieske, J. Oberst, J.L. Simon, E.M Standish, P. Stooke, and P.C. Thomas (2002), Report of the IAU/IAG Working Group on Cartographic Coordinates and Rotation Elements of the Planets and Satellites: 2000, Celestial Mechanics and Dynamical Astronomy, 82, pp. 83-110.
  11. Seidelmann, P.K. (Chair), B.A. Archinal (Vice-Chair), M.F. A'Hearn, D.P. Cruikshank, J.L. Hilton, H.U. Keller, J. Oberst, J.L. Simon, P. Stooke, D.J. Tholen, and P.C. Thomas (2005), Report Of The IAU/IAG Working Group On Cartographic Coordinates And Rotational Elements: 2003, Celestial Mechanics and Dynamical Astronomy, 91, pp. 203-215.
  12. Snyder, J.P. (1987), Map Projections, U.S. Geological Survey Professional Paper 1395.
  13. Williams, J. G., X.X. Newhall, and E.M. Standish (1993), Users of Ephemerides of the Earth-Moon System, JPL Internal Memorandum, December 18.
What are derived files? The term derived files (or in some cases, derived products) refer to products or files derived from other PDS science products. In some cases, these are generated by the instrument teams and included in the PDS Archives. An example is the Derived Data Records (DDRs) of the CRISM instrument.
ODE itself also generates derived files to improve PDS usability. There are four classes of ODE derived files:
  1. Static one PDS product to one or more derived files - These files are derived from a single PDS product. They are static, i.e. they are pre-derived from the PDS product, usually when the product is loaded into ODE. These are listed under the Product Results (see section 4.64) page's Derived Files tab.
  2. Dynamic one PDS to one or more derived files - These derived files are similar to static except they are generated when a user requests them.
  3. Static many PDS to one derived files - These files are derived from many PDS products. They are static, i.e. they are pre-derived from the PDS products, usually when the products are loaded into ODE. The best example is the product coverage KML and Shapefiles found under the tools tab.
  4. Dynamic many PDS to one derived files - Finally, these products are dynamically generated products based on multiple PDS products. The most obvious example is the MOLA PEDR query tool results (see section 4.68). These are generated from multiple PEDR products and only generated when a user asks for them.
How do I add products to my cart? First, your web browser needs to have cookies enabled. You will receive notification at the top of the pages of ODE if your browser does not have cookies enabled. Cookies can be enabled in most web browsers by navigating to the browser's tools and internet options.

The product search results list, product detail, and MRO coordinated observation search results page contain the functionality for adding products to your cart.

On the product search results list, the user simply selects the checkboxes next to the desired products, and then clicks the "Update Cart" button. After the products have been added to the cart, the text "In Cart" will be visible in the far right column of the product list. Deselect the check boxes and click "Update Cart" to remove selected products from the cart.

The product detail page contains "Add Product to Cart" and "Remove Product from Cart" buttons on its default browse tab. These buttons are used to immediately add or remove the current product from the cart. If the product is in the cart or has just been added to the cart, text will indicate, "This product is in your cart." above the add and remove buttons. The product detail page may also contain a “Related Products” tab if the current product is associated with other data products in ODE. The “Related Products” tab contains the same functionality as the search results list for adding and removing related products from the cart.

The coordinated observation search results page displays groups of products by default. Clicking on the "expand products" image will display the individual products of the group. Once the individual products are displayed they can be added to the cart with the check boxes and "Update Cart" button in the same fashion as the product search results list page.

How do I download products and/or files? ODE provides four options for acquiring data products and data sets:
1. Search for products and directly download files from the product detail pages
(more on using the product detail page)

2. Locate and directly download files from the Data Set Browser file listings
(more on using the Data Set Explorer)

The next two options require that you first add the desired data products to the download cart from the search results list, product detail, or coordinated observation search results page.
3. Download HTML version of the product list from the download cart page, which allows download of individual files.
From the download cart page, expand the list of products selected for download. Check the "Display Individual Files of the Products" check box to see the individual files associated with each product. Then click the "Download HTML version of the product list" hyper link. This link will allow the user to save a local HTML copy of the product/file list displayed on the page. Then this results list web page can be used to view ODE product detail pages and directly download product files at any time. (more on using the download cart page)

4. Complete the checkout process. The Geosciences Node will acquire, organize, and then place the files in an FTP folder for your download.
After adding the desired data products to the download cart, the user will proceed through the "checkout process" by navigating to the Download page. Additional download options are available via check boxes on this page. The user may have the option to include "Selected Products' Derived Files" with the cart selections. This will include map projected shape files and KML files for the products in the user cart. This option is only available if these files exist for the selected products. Also, the user can choose to add all the data set documentation and supporting materials for the products in the cart to the order by selecting the "Mini-Archive Files" checkbox, which creates a "Mini-Archive".
The next page of the checkout process requires the user to select the desired compression format (zip, tar, tar.gz) and enter his or her email address. The address is used to notify the user when the download request is available. The request will be submitted to a processing queue after the user submits the request on this page.
ODE will then create a set of compressed files that will contain all the requested products, derived files (if selected), and mini-archive files (if selected).. The compressed files will be placed in a user specific folder on a FTP site at the Geosciences Node. The user will be emailed a notification when the files are available for download. The email will contain the direct FTP address in addition to the login username and password. The time between submitting the request and receiving notification that the files are ready for download varies based on the size of the request, and the number of other user requests in the queue. Small requests can be available within an hour or two, but large requests can take up to 24 hours. An estimate of the time required to fulfill the order is displayed on the Download cart page

In addition to the options listed above, the user can navigate to the Geosciences Node site to download individual files directly from that location http://pds-geosciences.wustl.edu.

The MRO High-Resolution Imaging Science Experiment (HiRISE), Context Imager (CTX), Mars Climate Sounder, and MGS Mars Orbital Camera products are not stored at the PDS Geosciences node, but direct links to product files are available through ODE and these products can be added to ODE's download cart. Users can also acquire these data products directly from their host node websites: HiRISE data is stored at the PDS HiRISE Data Node, CTX and MOC are stored at the PDS Imaging Node, and MCS is stored at the PDS Atmospheres Node.

Why are there differences between HiRISE, CTX, MCS, MOC and the other ODE products? (ODE Mars) ODE provides a method for searching, browsing, and accessing various archives in PDS. Some of the archives cataloged in ODE are stored at other PDS nodes. Specifically, HiRISE data is stored at the PDS HiRISE Data Node, CTX, MOC, and Clementine EDR, UVVIS Basemap Mosaic, UVVIS DIM Mosaic, and HiRes Mosaic data stored at the PDS Imaging Node, and MCS is stored at the PDS Atmospheres Node, and Lunar Prospector MDR (Level 0, GRS/NS/APS/MAG/ER), MAG Processed Time Series (NASA Level 1B), MAG Filtered Time Series (NASA Level 2), MAG Magnetization Maps (NASA Level 3 and 4), ER Processed Time Series (NASA Level 1B), and ER Filtered Time Series (NASA Level 2) data are stored at the PDS PPI Node. With ODE Version 2.2, users can add these products to their download cart and the display of direct links to product files at their host PDS node. ODE's product detail page also provides links to the PDS node that stores the data for product access and download. This allows users to use the best tools for access and downloading the products from the host PDS node. For example, the HiRISE images are often very large and the HiRISE data node provides special web tools for viewing the products on line.

What are Coordinated Observations? (ODE Mars) ODE supports the MRO concept called a "Coordinated Observation", a planned observation involving multiple instruments at a given location and time. The source of these planned observations is the MRO science operations group. ODE tracks these planned coordinated observations and then correlates them to PDS products that resulted from the planned coordinated observation. This allows users to find and view related products from HiRISE, CRISM, and CTX, MCS, and even the Mars Phoenix Lander. Users can access the coordinated observations and their products via the Coordinated Observation page and via the related products tab of the product details page. In the case of Mars Phoenix Lander data, the user is connected to the PDS Geosciences node Phoenix Analyst Notebook.

A warning about coordinated observations: Sometime these planned observations do not take place, or a re delayed, or some instruments do not participate as planned. ODE uses the available information as best it can to locate data products from coordinated observations but the results may be incomplete. The user should also be aware that MRO data products are not archived in PDS until at least six months after they are acquired.