MCD is a database of atmospheric statistics compiled from Global Climate Model (GCM) numerical simulation of Martian atmosphere (<a href=http://www-mars.lmd.jussieu.fr>http://www-mars.lmd.jussieu.fr</a>). The GCM computes in 3D the atmospheric circulation and climate taking into account radiative transfer through the gaseous atmospheres and the dust and ice aerosols, includes a representation of the CO2 ice condensation and sublimation on the ground and in the atmosphere, simulates the water cycle (with modelling of cloud microphysics), the dust multisize particle transport, the atmospheric composition controlled by the photochemistry and the local non-condensible gas enrichment and depletion induced by CO2 condensation and sublimation, and has been extended into the thermosphere and to model ionospheric processes (due to chemistry). The database extends up to exobase (the top of the thermosphere, roughly at 300km in altitude); in addition to statistics on temperature, wind, pressure, radiative fluxes, it provides data such as atmospheric composition (including dust water vapor and ice content) and make use of 'dust and Extreme Ultra Violet (EUV) scenarios' to represent the variation of dust in the atmosphere and solar EUV conditions. User Manual of the service : <a href=http://vo.lmd.jussieu.fr:8080/MCD_VESPA_service_user_manual.pdf>User Manual of the service </a> .EPN-TAP MCD is a database of atmospheric statistics compiled from Global
Climate Model (GCM) numerical simulation of Martian atmosphere (<a
href=http://www-mars.lmd.jussieu.fr>http://www-mars.lmd.jussieu.fr</a>).
The GCM computes in 3D the atmospheric circulation and climate taking
into account radiative transfer through the gaseous atmospheres and
the dust and ice aerosols, includes a representation of the CO2 ice
condensation and sublimation on the ground and in the atmosphere,
simulates the water cycle (with modelling of cloud microphysics), the
dust multisize particle transport, the atmospheric composition
controlled by the photochemistry and the local non-condensible gas
enrichment and depletion induced by CO2 condensation and sublimation,
and has been extended into the thermosphere and to model ionospheric
processes (due to chemistry). The database extends up to exobase (the
top of the thermosphere, roughly at 300km in altitude); in addition to
statistics on temperature, wind, pressure, radiative fluxes, it
provides data such as atmospheric composition (including dust water
vapor and ice content) and make use of 'dust and Extreme Ultra Violet
(EUV) scenarios' to represent the variation of dust in the atmosphere
and solar EUV conditions. User Manual of the service : <a
href=http://vo.lmd.jussieu.fr:8080/MCD_VESPA_service_user_manual.pdf>User
Manual of the service </a> .LMD/IPSL The database contains some outputs of the MCD for all the scenarios
available, at different positions of latitude and longitude. These MCD
outputs are provided as Votables containing profiles of temperatures,
pressures, density and abundances of O2 and O3 for altitudes between 0
and 249.5 km from the surface.Query successfulFor advice on how to cite the resource(s) that contributed to this result, see http://vo.lmd.jussieu.fr/tableinfo/mcd.epn_core
The database contains some outputs of the MCD for all the scenarios
available, at different positions of latitude and longitude. These MCD
outputs are provided as Votables containing profiles of temperatures,
pressures, density and abundances of O2 and O3 for altitudes between 0
and 249.5 km from the surface.
The following values are defined for this field:
im -- image
associated scalar fields with two spatial axes, e.g., images with
multiple color planes like from multichannel or filter cameras.
Preview images (e.g. map with axis and caption) also belong here.
Conversely, all vectorial 2D fields are described as catalogue
(see below).
ma -- map
scalar field/rasters with two spatial axes covering a large
area and projected either on the sky or on a planetary body,
associated to a Projection parameter (with a short enumerated
list of possible values). This is mostly intended to identify
complete coverages that can be used as reference basemaps.
sp-- spectrum
measurements organized primarily along a spectral axis, e.g.,
radiance spectra. This includes spectral aggregates (series
of related spectra with non-connected spectral ranges, e.g.,
from several channels of the same instrument
ds -- dynamic spectrum
consecutive spectral measurements through time, organized
as a time series. This typically implies successive spectra of
the same target or field of view.
sc -- spectral cube
sets of spectral measurements with 1 or 2 D spatial coverage, e.g.,
imaging spectroscopy. The choice between Image and spectral_cube is
related to the characteristics of the instrument (which dimension
is most resolved and which dimensions are acquired simultaneously).
The choice between dynamic_spectrum and spectral_cube is related
to the uniformity of the field of view.
pr -- profile
scalar or vectorial measurements along 1 spatial dimension, e.g.,
atmospheric profiles, atmospheric paths, sub-surface profiles,
traverses…
pf -- photometric profile
scalar or vectorial measurements along 1 angular dimension, e.g.,
phase or polarization curves, phase functions, emission-phase
function sequences… typically associated to variations in
illumination angle parameters.
vo -- volume
other measurements with 3 spatial dimensions, e.g., internal or
atmospheric structures, including shells/shape models (3D surfaces).
mo -- movie
sets of chronological 2 D spatial measurements.
cu -- cube
multidimensional data with 3 or more axes, e.g., all that is not
described by other 3 D data types such as spectral cubes or volume.
This is mostly intended to accommodate unusual data with multiple
dimensions.
ts -- time series
measurements organized primarily as a function of time (with
exception of dynamical spectra and movies, i.e. usually a scalar
quantity). Typical examples of time series include space-borne
dust detector measurements, daily or seasonal curves measured at
a given location (e.g., a lander), and light curves.
ca -- catalog
applies to a single granule providing a list of events, a catalog
of object parameters, a list of features… It is good practice to
describe the type of data included in the catalogue using a
hash-separated-list (e.g., a table of spectra should be described
by ca#sp, so that it will respond to a query for spectra).
ci -- catalogue item
applies when the service itself provides a catalogue, with entries
described as individual granules. The service can be, e.g., a list
of asteroid properties or spectral lines. Catalogue_item can be
limited to scalar quantities (including strings), and possibly to
a single element. This organization allows the user to search inside
the catalogue from the TAP query interface.
sv -- spatial vector
vector information associated to localization, such as spatial
footprints or a GIS-related element. This could contain a kml
or geojson file (STC-S strings are provided though the s_region
parameter, though). This includes maps of vectors, e.g., wind maps.
ev -- event
individual events, typically formatted in VOEvent. Characteristics
are provided via the event_* parameters.
CODMAC levels are:
1 -- raw
2 -- edited
3 -- calibrated
4 -- resampled
5 -- derived
6 -- ancillaryInternal table row index, which must be unique within the table. Can be alphanumeric.Common to granules of same type (e.g. same map projection, or geometry data products). Can be alphanumeric.Associates granules derived from the same data (e.g. various representations/processing levels). Can be alphanumeric, may be the ID of original observation.The high-level organization of the data product, from a controlled vocabulary (e.g., 'im' for image, sp for spectrum). Multiple terms may be used, separated by # characters.Standard IAU name of target (from a list related to target class), case sensitiveType of target, from a controlled vocabulary.Acquisition start time (in JD), as UTC at time_refpositionAcquisition stop time (in JD), as UTC at time_refpositionSampling time for measurements of dynamical phenomena, lower limit.Sampling time for measurements of dynamical phenomena, upper limitIntegration time of the measurement, lower limit.Integration time of the measurement, upper limitSpectral range (frequency), lower limit.Spectral range (frequency), upper limitSpectral sampling step, lower limit.Spectral sampling step, upper limitSpectral resolution, lower limit.Spectral resolution, upper limitLongitude on body, lower limit.Longitude on body, upper limitLatitude on body, lower limit.Latitude on body, upper limitAltitude from reference surface, lower limit.Altitude from reference surface, upper limitObsCore-like footprint, valid for celestial, spherical, or body-fixed framesResolution in the first coordinate, lower limit.Resolution in the first coordinate, upper limitResolution in the second coordinate, lower limit.Resolution in the second coordinate, upper limitResolution in the third coordinate, lower limit.Resolution in the third coordinate, upper limitFlavor of coordinate system, defines the nature of coordinates. From a controlled vocabulary, where 'none' means undefined.Incidence angle (solar zenithal angle) during data acquisition, lower limit.Incidence angle (solar zenithal angle) during data acquisition, upper limitEmergence angle during data acquisition, lower limit.Emergence angle during data acquisition, upper limitPhase angle during data acquisition, lower limit.Phase angle during data acquisition, upper limitStandard name of the observatory or spacecraftStandard name of instrumentUCD(s) defining the data, with multiple entries separated by hash (#) characters.Dataset-related encoding, or simplified CODMAC calibration levelDate of first entry of this granuleDate of last modification (used to handle mirroring)Start of public access periodTitle of resource (an acronym really, will be used to handle multiservice results)URL of the data file, case sensitive. If present, then access_format and access_estsize are mandatory.File format type (RFC 6838 Media Type a.k.a. MIME type)Estimated file size in kbyte.Defaults to UTC in data services; takes values from http://www.ivoa.net/rdf/time_scale otherwiseIdentifies a chemical species, case sensitiveMin local time at observed regionMax local time at observed regionID of specific coordinate system and version or properties.Type of region or feature of interestMin Solar longitude Ls (location on orbit / season)Max Solar longitude Ls (location on orbit / season)Solar conditions for the model inputDust conditions for the model inputIdentifier of the MCD scenarioURL of a datalink service for this dataset
A Datalink service to retrieve the data set as well as additional related files, plus possibly services for server-side processing.