Data Dictionaries - Missions

The following page links to all released Mission Data Dictionaries, including XML Schema and Schematrons for the applicable PDS4 namespace.

All versions of the data dictionaries can be found here.

Need help with creating a dictionary or where to start, please contact the PDS Operator at pds_operator@jpl.nasa.gov.


What are you looking for?


Data Dictionaries

Compatible Versions

For each version of the PDS Common Data Dictionary, there are specific discipline and mission dictionary that are compatible. You can find this information in our Dictionary Stacks database.

Back to top

PDS Common

All versions of the PDS Common data dictionaries can be found here.

Back to top

Discipline Dictionaries

All versions of the Discipline data dictionaries can be found here.

Back to top

Mission Dictionaries

Cassini (cassini)

The Cassini Mission Dictionary (cassini) contains classes, attributes and rules specific to the Cassini Mission and its instruments (Note: Huygens classes will be in a separate dictionary).

Back to top

Chandrayaan-1 (chan1)

The Chandrayaan-1 Mission Dictionary (chan1) contains classes, attributes and rules specific to the Chandrayaan-1 Mission and its instruments.

Back to top

Clementine (clementine)

The Clementine Mission Dictionary (clementine) contains classes, attributes and rules specific to the Clementine Mission and its instruments.

Back to top

DAWN (dawn)

The DAWN Mission Dictionary (dawn) contains classes, attributes and rules specific to the DAWN Mission and its instruments.

Back to top

Hayabusa2 (hyb2)

The Hayabusa2 Dictionary (hyb2) contains classes, attributes and rules specific to the Hayabusa2 Mission and its instruments.

Back to top

Juno (juno)

The JUNO Mission Dictionary (juno) contains classes, attributes and rules specific to the JUNO Mission and its instruments.

Back to top

LADEE (ladee)

The LADEE Mission Dictionary (ladee) contains classes, attributes and rules specific to the LADEE Mission and its instruments.

Back to top

Mars 2020 (mars2020)

The Mars 2020 Mission Dictionary contains classes and attributes that describe data products from the Mars 2020 Perseverance Rover Mission.

Back to top

MAVEN (mvn)

The MAVEN Mission Dictionary (mvn) contains classes, attributes and rules specific to the MAVEN mission and its instruments.

Back to top

MER (mer)

The Mars Exploration Rover Mission Dictionary (mer) contains classes, attributes and rules specific to the MER Mission and its instruments.

Back to top

MESSENGER (mess)

The MESSENGER Mission Dictionary (mess) contains classes, attributes and rules specific to the MESSENGER Mission and its instruments.

Back to top

OSIRIS-REx (orex)

The OSIRIS-REx Mission Dictionary (orex) contains classes, attributes and rules specific to the OSIRIS-REx Mission and its instruments.

Back to top

VOYAGER 1 (vg1)

The VOYAGER-1 Mission Dictionary (vg1) contains classes, attributes and rules specific to the Voyager-1 Mission and its instruments.

Back to top

VOYAGER 2 (vg2)

The VOYAGER-2 Mission Dictionary (vg2) contains classes, attributes and rules specific to the Voyager-2 Mission and its instruments.

Back to top

Namespaces

The PDS4 XML Schema and Schematron files are organized by namespace. For a list of existing namespaces, refer to the PDS Namespace Registry.

Back to top

How To Create A Dictionary

Please contact your applicable discipline node to ensure a new dictionary is necessary prior to beginning development. Once agreed upon, there are several places to go when trying to learn how to create a dictionary.

Once all information is gathered, create a ticket here to initialize a new PDS LDD and register it with the PDS Namespace Registry.

Back to top

Submitting A New Version

When a Local Data Dictionary (LDD) Steward is ready to submit a new version of an LDD for release:

Submit LDD Release Request

Note: Assume validation has been completed by steward.

Dictionary Validation

The LDD steward is encouraged to perform test/validation via one/both of the testing mechanisms:

Note: Currently, there is no explicit way to run validate to check out the schemas, but by reading the schemas into the tool, it will raise an error if they are invalid.

  • Open in Oxygen and click the red checkbox at the top.
  • Execute latest validate (version 1.16.0+) and specify the schemas via the command-line, for example:
    $ validate -x PDS4_CART_1C00_1932.xsd -S PDS4_CART_1C00_1932.xsd -t PDS4_CART_1C00_1932.xml
    				

The PDS Engineering Node will also perform some basic testing and validation when a release is requested to ensure nothing makes it out as "released" that is invalid.

If there is an error, an email will be sent to the steward with error message(s).

If no error is found, the LDD will be posted to both latest and all schemas pages. An email will be sent to the steward indicating posting is completed.

Back to top