Mars-Express/High Resolution Stereo Camera nadir (panchromatic) images
projected to Equidistant Cylindrical projection ortho-rectified using
the MOLA DTM (HRSC level 3). The images are accessible via an OGC Map
Web Service (WMS) directly from our WMS Server. For an interactive
web-GIS of the data, visit: http://maps.planet.fu-berlin.deEPN-TAPEPN-TAPMars-Express/High Resolution Stereo Camera nadir (panchromatic) images
projected to Equidistant Cylindrical projection ortho-rectified using
the MOLA DTM (HRSC level 3). The images are accessible via an OGC Map
Web Service (WMS) directly from our WMS Server. For an interactive
web-GIS of the data, visit: http://maps.planet.fu-berlin.deEPN-TAP access to HRSC level 3 panchromatic image dataQuery successfulThis resource contains data associated with the publication source.For advice on how to cite the resource(s) that contributed to this result, see http://dachs.planet.fu-berlin.de/tableinfo/hrsc3nd.epn_core
EPN-TAP access to HRSC level 3 panchromatic image data
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…
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… Spatial vectors
(e.g., vector information from a GIS, spatial footprints…) belong
here. This is relevant, e. g., for collections of vectorial elements
(e.g., crater lists or ROI definitions) which can be handled directly
in a specialized environment such as a GIS. This includes maps of
vectors, e.g., wind maps.
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.
CODMAC levels are:
1 -- raw
2 -- edited
3 -- calibrated
4 -- resampled
5 -- derived
6 -- ancillaryInternal table row index Unique ID in data service, also in v2. 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 enumerated list (e.g., 'im' for image, sp for spectrum)Standard IAU name of target (from a list related to target class), case sensitiveType of target, from enumerated listAcquisition start time (in JD)Acquisition stop time (in JD)Sampling 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 limitSectral resolution, lower limit.Sectral resolution, upper limitLongitude on body, lower limit.Longitude on body, upper limitLatitude on body, lower limit.Latitude on body, upper limitHeight over defined null, lower limit.Height over defined null, upper limitObsCore-like footprint, valid for celestial, spherical, or body-fixed frames.Resolution 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 enumerated listIncidence 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 spacecraft.Standard name of instrumentUCD(s) defining the data, with multiple entries separated by hash (#) characters.CODMAC calibration level; see the et_cal note http://dc.g-vo.org/tableinfo/titan.epn_core#note-et_cal for what values are defined here.Date 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, next 2 paramenters must be present.File format typeEstimate file size in kbyte (with this spelling)Bibcode preferred if available (does that include link?), doi, or other biblio id, URLURL of a thumbnail image with predefined size (png ~200 pix, for use in a client only)URL of the preview linkSolar longitude (minimum)Solar longitude (maximum)Filter nameReflectance scaling factorReflectance offsetRadiance scaling factorRadiance offset (unit: W*m**-2*sr**-1)Map projection parameters in libproj notationMeters per pixelMeters per pixel