Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema EPNCore.xsd
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Annotations
 
EPNCore schema, designed on the model of the ObsCore
schema (IVOA) but addapted to planetology. To describe the resources content of 
Europlanet/IDIS. This DM will be used in TAP-EPN.
Properties
attribute form default: unqualified
element form default: unqualified
version: 1.0
Element EPNcore
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#EPNCoreType_resource_type EPNCore_xsd.tmp#EPNCoreType_dataproduct_type EPNCore_xsd.tmp#EPNCoreType_target_name EPNCore_xsd.tmp#EPNCoreType_target_class EPNCore_xsd.tmp#EPNCoreType_time EPNCore_xsd.tmp#EPNCoreType_spectral EPNCore_xsd.tmp#EPNCoreType_spatial EPNCore_xsd.tmp#EPNCoreType_view_angle EPNCore_xsd.tmp#EPNCoreType_instrument_host_name EPNCore_xsd.tmp#EPNCoreType_instrument_name EPNCore_xsd.tmp#EPNCoreType_measurement_type EPNCore_xsd.tmp#EPNCoreType
Type EPNCoreType
Properties
content: complex
Model resource_type{0,1} , dataproduct_type* , target_name* , target_class* , time* , spectral* , spatial* , view_angle* , instrument_host_name* , instrument_name* , measurement_type*
Children dataproduct_type, instrument_host_name, instrument_name, measurement_type, resource_type, spatial, spectral, target_class, target_name, time, view_angle
Instance
 
<EPNcore xmlns="http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd">
  <resource_type>{0,1}</resource_type>
  <dataproduct_type>{0,unbounded}</dataproduct_type>
  <target_name>{0,unbounded}</target_name>
  <target_class>{0,unbounded}</target_class>
  <time>{0,unbounded}</time>
  <spectral>{0,unbounded}</spectral>
  <spatial>{0,unbounded}</spatial>
  <view_angle>{0,unbounded}</view_angle>
  <instrument_host_name>{0,unbounded}</instrument_host_name>
  <instrument_name>{0,unbounded}</instrument_name>
  <measurement_type>{0,unbounded}</measurement_type>
</EPNcore>
Source
 
<xs:element name="EPNcore" type="EPNCoreType">
</xs:element>
Element EPNCoreType / resource_type
Namespace No namespace
Annotations
 
A dataset is a consistent set of data and associated metadata. A dataset can be comprised of files, tables, or data computed on the fly.
A granule is the smallest element reachable in a dataset: either a file, a group of associated files, a table entry, or some kind of data computed on the fly.
Diagram
Diagram EPNCore_xsd.tmp#ResourceClassType
Type ResourceClassType
Properties
content: simple
minOccurs: 0
maxOccurs: 1
default: dataset
Facets
enumeration dataset
enumeration granule
Source
 
<xs:element name="resource_type" type="ResourceClassType" minOccurs="0" maxOccurs="1" default="dataset">
  <xs:annotation>
    <xs:documentation>A dataset is a consistent set of data and associated metadata. A dataset can be comprised of files, tables, or data computed on the fly. A granule is the smallest element reachable in a dataset: either a file, a group of associated files, a table entry, or some kind of data computed on the fly.</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / dataproduct_type
Namespace No namespace
Diagram
Diagram
Type restriction of xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Facets
enumeration image 
associated scalar fields with two spatial axes, e.g., images with multiple color planes, from multichannel cameras for example. Maps of planetary surfaces are considered as images.
enumeration spectrum 
data product which spectral coverage is the primary attribute, e.g., a set of spectra.
enumeration dynamic_spectrum 
consecutive spectral measurements through time, organized as a time series.
enumeration spectral_cube 
set of spectral measurements with 1 or 2D spatial coverage, e.g., imaging spectroscopy. The choice between Image and spectral_cube is related to the characteristics of the instrument..
enumeration profile 
scalar or vectorial measurements along 1 spatial dimension, e.g., atmospheric profiles, atmospheric paths, sub-surface profiles…
enumeration volume 
other measurements with 3 spatial dimensions, e.g., internal or atmospheric structures.
enumeration movie 
sets of chronological 2D spatial measurements
enumeration cube 
multidimensional data with 3 or more axes, e.g., all that is not described by other 3D data types such as spectral cubes or volume.
enumeration time_series 
measurements organized primarily as a function of time (with exception of dynamical spectra). A Spacecraft dust detector measurement is a typical example of a time series.
enumeration catalog 
can be a list of events, a catalog of object parameters, a list of features.... E.g., a list of asteroid properties. Can also be a single element.
enumeration spatial_vector 
list of summit coordinates defining a vector, e.g., vector information from a GIS, spatial footprints…
Source
 
<xs:element name="dataproduct_type" maxOccurs="unbounded" minOccurs="0">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="image">
        <xs:annotation>
          <xs:documentation>associated scalar fields with two spatial axes, e.g., images with multiple color planes, from multichannel cameras for example. Maps of planetary surfaces are considered as images.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="spectrum">
        <xs:annotation>
          <xs:documentation>data product which spectral coverage is the primary attribute, e.g., a set of spectra.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="dynamic_spectrum">
        <xs:annotation>
          <xs:documentation>consecutive spectral measurements through time, organized as a time series.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="spectral_cube">
        <xs:annotation>
          <xs:documentation>set of spectral measurements with 1 or 2D spatial coverage, e.g., imaging spectroscopy. The choice between Image and spectral_cube is related to the characteristics of the instrument..</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="profile">
        <xs:annotation>
          <xs:documentation>scalar or vectorial measurements along 1 spatial dimension, e.g., atmospheric profiles, atmospheric paths, sub-surface profiles…</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="volume">
        <xs:annotation>
          <xs:documentation>other measurements with 3 spatial dimensions, e.g., internal or atmospheric structures.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="movie">
        <xs:annotation>
          <xs:documentation>sets of chronological 2D spatial measurements</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="cube">
        <xs:annotation>
          <xs:documentation>multidimensional data with 3 or more axes, e.g., all that is not described by other 3D data types such as spectral cubes or volume.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="time_series">
        <xs:annotation>
          <xs:documentation>measurements organized primarily as a function of time (with exception of dynamical spectra). A Spacecraft dust detector measurement is a typical example of a time series.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="catalog">
        <xs:annotation>
          <xs:documentation>can be a list of events, a catalog of object parameters, a list of features.... E.g., a list of asteroid properties. Can also be a single element.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="spatial_vector">
        <xs:annotation>
          <xs:documentation>list of summit coordinates defining a vector, e.g., vector information from a GIS, spatial footprints…</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element EPNCoreType / target_name
Namespace No namespace
Annotations
 
derive from type=ept:TaregetType.TargetName
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="target_name" maxOccurs="unbounded" minOccurs="0" type="xs:string">
  <xs:annotation>
    <xs:documentation>derive from type=ept:TaregetType.TargetName</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / target_class
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#TargetClass
Type TargetClass
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Facets
enumeration asteroid
enumeration comet
enumeration dwarf_planet
enumeration exoplanet
enumeration interplanetary_medium
enumeration planet
enumeration ring
enumeration sample
enumeration satellite
enumeration sky
enumeration spacecraft
enumeration spacejunk
enumeration star
Source
 
<xs:element maxOccurs="unbounded" minOccurs="0" name="target_class" type="TargetClass">
</xs:element>
Element EPNCoreType / time
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#Time_Type_time_min EPNCore_xsd.tmp#Time_Type_time_max EPNCore_xsd.tmp#Time_Type_time_sampling_step_min EPNCore_xsd.tmp#Time_Type_time_sampling_step_max EPNCore_xsd.tmp#Time_Type_time_exp_min EPNCore_xsd.tmp#Time_Type_time_exp_max EPNCore_xsd.tmp#Time_Type
Type Time_Type
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model time_min{0,1} , time_max{0,1} , time_sampling_step_min{0,1} , time_sampling_step_max{0,1} , time_exp_min{0,1} , time_exp_max{0,1}
Children time_exp_max, time_exp_min, time_max, time_min, time_sampling_step_max, time_sampling_step_min
Instance
 
<time>
  <time_min>{0,1}</time_min>
  <time_max>{0,1}</time_max>
  <time_sampling_step_min>{0,1}</time_sampling_step_min>
  <time_sampling_step_max>{0,1}</time_sampling_step_max>
  <time_exp_min>{0,1}</time_exp_min>
  <time_exp_max>{0,1}</time_exp_max>
</time>
Source
 
<xs:element maxOccurs="unbounded" minOccurs="0" name="time" type="Time_Type">
</xs:element>
Element Time_Type / time_min
Namespace No namespace
Annotations
 
"The time parameter(s) provides the date and time of acquisition. It may be a couple of parameters to handle long periods in some datasets.
This parameter is provided in Julian days, expressed as a double precision float. Although ObsCore uses Modified JD, EPNCore uses JD to avoid ambiguity with time origin. With double precision floats, the accuracy is on the order of 1 ms.
Whenever time is defined by a single parameter, both time_min and time_max contain the same "
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="time_min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>"The time parameter(s) provides the date and time of acquisition. It may be a couple of parameters to handle long periods in some datasets. This parameter is provided in Julian days, expressed as a double precision float. Although ObsCore uses Modified JD, EPNCore uses JD to avoid ambiguity with time origin. With double precision floats, the accuracy is on the order of 1 ms. Whenever time is defined by a single parameter, both time_min and time_max contain the same "</xs:documentation>
  </xs:annotation>
</xs:element>
Element Time_Type / time_max
Namespace No namespace
Annotations
 
"The time parameter(s) provides the date and time of acquisition. It may be a couple of parameters to handle long periods in some datasets.
This parameter is provided in Julian days, expressed as a double precision float. Although ObsCore uses Modified JD, EPNCore uses JD to avoid ambiguity with time origin. With double precision floats, the accuracy is on the order of 1 ms.
Whenever time is defined by a single parameter, both t_min and t_max contain the same "
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="time_max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>"The time parameter(s) provides the date and time of acquisition. It may be a couple of parameters to handle long periods in some datasets. This parameter is provided in Julian days, expressed as a double precision float. Although ObsCore uses Modified JD, EPNCore uses JD to avoid ambiguity with time origin. With double precision floats, the accuracy is on the order of 1 ms. Whenever time is defined by a single parameter, both t_min and t_max contain the same "</xs:documentation>
  </xs:annotation>
</xs:element>
Element Time_Type / time_sampling_step_min
Namespace No namespace
Annotations
 
"This parameter provides the sampling time for measurements of dynamical phenomena, and for computations. This is the time between 2 successive measurements/data. This may be a query parameter e.g. for ephemeris computations. expressed in second "
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element minOccurs="0" maxOccurs="1" name="time_sampling_step_min" type="xs:double">
  <xs:annotation>
    <xs:documentation>"This parameter provides the sampling time for measurements of dynamical phenomena, and for computations. This is the time between 2 successive measurements/data. This may be a query parameter e.g. for ephemeris computations. expressed in second "</xs:documentation>
  </xs:annotation>
</xs:element>
Element Time_Type / time_sampling_step_max
Namespace No namespace
Annotations
 
"This parameter provides the sampling time for measurements of dynamical phenomena, and for computations. This is the time between 2 successive measurements/data. This may be a query parameter e.g. for ephemeris computations. expressed in second "
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element minOccurs="0" maxOccurs="1" name="time_sampling_step_max" type="xs:double">
  <xs:annotation>
    <xs:documentation>"This parameter provides the sampling time for measurements of dynamical phenomena, and for computations. This is the time between 2 successive measurements/data. This may be a query parameter e.g. for ephemeris computations. expressed in second "</xs:documentation>
  </xs:annotation>
</xs:element>
Element Time_Type / time_exp_min
Namespace No namespace
Annotations
 
This parameter corresponds to the minimum integration time of measurements. This time is usually shorter than the time_sampling_step (if both are present).
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="time_exp_min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter corresponds to the minimum integration time of measurements. This time is usually shorter than the time_sampling_step (if both are present).</xs:documentation>
  </xs:annotation>
</xs:element>
Element Time_Type / time_exp_max
Namespace No namespace
Annotations
 
This parameter corresponds to the maximum integration time of measurements. This time is usually shorter than the time_sampling_step (if both are present).
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="time_exp_max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter corresponds to the maximum integration time of measurements. This time is usually shorter than the time_sampling_step (if both are present).</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / spectral
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#SpectralType_spectral_range_min EPNCore_xsd.tmp#SpectralType_spectral_range_max EPNCore_xsd.tmp#SpectralType_spectral_sampling_step_min EPNCore_xsd.tmp#SpectralType_spectral_sampling_step_max EPNCore_xsd.tmp#SpectralType_spectral_resolution_min EPNCore_xsd.tmp#SpectralType_spectral_resolution_max EPNCore_xsd.tmp#SpectralType
Type SpectralType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model spectral_range_min* , spectral_range_max* , spectral_sampling_step_min* , spectral_sampling_step_max* , spectral_resolution_min* , spectral_resolution_max*
Children spectral_range_max, spectral_range_min, spectral_resolution_max, spectral_resolution_min, spectral_sampling_step_max, spectral_sampling_step_min
Instance
 
<spectral>
  <spectral_range_min>{0,unbounded}</spectral_range_min>
  <spectral_range_max>{0,unbounded}</spectral_range_max>
  <spectral_sampling_step_min>{0,unbounded}</spectral_sampling_step_min>
  <spectral_sampling_step_max>{0,unbounded}</spectral_sampling_step_max>
  <spectral_resolution_min>{0,unbounded}</spectral_resolution_min>
  <spectral_resolution_max>{0,unbounded}</spectral_resolution_max>
</spectral>
Source
 
<xs:element name="spectral" minOccurs="0" maxOccurs="unbounded" type="SpectralType"/>
Element SpectralType / spectral_range_min
Namespace No namespace
Annotations
 
The spectral_range is expressed on a frequency in Hertz. It defines the lower bounds of the spectral domain where data have intersection with the requested spectral range.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="spectral_range_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The spectral_range is expressed on a frequency in Hertz. It defines the lower bounds of the spectral domain where data have intersection with the requested spectral range.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpectralType / spectral_range_max
Namespace No namespace
Annotations
 
The spectral_range is expressed on a frequency in Hertz. It defines the upper bounds of the spectral domain where data have intersection with the requested spectral range.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="spectral_range_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The spectral_range is expressed on a frequency in Hertz. It defines the upper bounds of the spectral domain where data have intersection with the requested spectral range.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpectralType / spectral_sampling_step_min
Namespace No namespace
Annotations
 
The spectral_sampling_step is the spectral separation (counted in Hz) between the centers of two adjacent filters or channels). Min is the lower level.
This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and Fourier spectrometers, or observations related to surfaces or atmospheres.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="spectral_sampling_step_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The spectral_sampling_step is the spectral separation (counted in Hz) between the centers of two adjacent filters or channels). Min is the lower level. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and Fourier spectrometers, or observations related to surfaces or atmospheres.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpectralType / spectral_sampling_step_max
Namespace No namespace
Annotations
 
The spectral_sampling_step is the spectral separation (counted in Hz) between the centers of two adjacent filters or channels). Min is the upper level.
This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and Fourier spectrometers, or observations related to surfaces or atmospheres.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="spectral_sampling_step_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The spectral_sampling_step is the spectral separation (counted in Hz) between the centers of two adjacent filters or channels). Min is the upper level. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and Fourier spectrometers, or observations related to surfaces or atmospheres.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpectralType / spectral_resolution_min
Namespace No namespace
Annotations
 
The spectral_resolution corresponds to the spectral bandwidth used for the measurement. In case of filter camera this is the filter bandwidth; in case of spectrometer this is the spectral resolution. 
This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and filter cameras.. Min is the lower level.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="spectral_resolution_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The spectral_resolution corresponds to the spectral bandwidth used for the measurement. In case of filter camera this is the filter bandwidth; in case of spectrometer this is the spectral resolution. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and filter cameras.. Min is the lower level.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpectralType / spectral_resolution_max
Namespace No namespace
Annotations
 
The spectral_resolution corresponds to the spectral bandwidth used for the measurement. In case of filter camera this is the filter bandwidth; in case of spectrometer this is the spectral resolution. 
This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and filter cameras.. Max is the upper level.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="spectral_resolution_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The spectral_resolution corresponds to the spectral bandwidth used for the measurement. In case of filter camera this is the filter bandwidth; in case of spectrometer this is the spectral resolution. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and filter cameras.. Max is the upper level.</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / spatial
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#SpatialType_spatial_range EPNCore_xsd.tmp#SpatialType_Spatial_frame_type EPNCore_xsd.tmp#SpatialType_spatial_resolution EPNCore_xsd.tmp#SpatialType
Type SpatialType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model spatial_range* , Spatial_frame_type , spatial_resolution{0,1}
Children Spatial_frame_type, spatial_range, spatial_resolution
Instance
 
<spatial>
  <spatial_range>{0,unbounded}</spatial_range>
  <Spatial_frame_type>{1,1}</Spatial_frame_type>
  <spatial_resolution>{0,1}</spatial_resolution>
</spatial>
Source
 
<xs:element name="spatial" minOccurs="0" maxOccurs="unbounded" type="SpatialType"/>
Element SpatialType / spatial_range
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#Spatial_RangeType_c1min EPNCore_xsd.tmp#Spatial_RangeType_c2min EPNCore_xsd.tmp#Spatial_RangeType_c3min EPNCore_xsd.tmp#Spatial_RangeType_c1max EPNCore_xsd.tmp#Spatial_RangeType_c2max EPNCore_xsd.tmp#Spatial_RangeType_c3max EPNCore_xsd.tmp#Spatial_RangeType
Type Spatial_RangeType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model c1min{0,1} , c2min{0,1} , c3min{0,1} , c1max{0,1} , c2max{0,1} , c3max{0,1}
Children c1max, c1min, c2max, c2min, c3max, c3min
Instance
 
<spatial_range>
  <c1min>{0,1}</c1min>
  <c2min>{0,1}</c2min>
  <c3min>{0,1}</c3min>
  <c1max>{0,1}</c1max>
  <c2max>{0,1}</c2max>
  <c3max>{0,1}</c3max>
</spatial_range>
Source
 
<xs:element name="spatial_range" minOccurs="0" maxOccurs="unbounded" type="Spatial_RangeType">
</xs:element>
Element Spatial_RangeType / c1min
Namespace No namespace
Annotations
 
This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type.
The service should handle three dimensions, even if the third one is set to NULL.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c1min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
  </xs:annotation>
</xs:element>
Element Spatial_RangeType / c2min
Namespace No namespace
Annotations
 
This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type.
The service should handle three dimensions, even if the third one is set to NULL.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c2min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
  </xs:annotation>
</xs:element>
Element Spatial_RangeType / c3min
Namespace No namespace
Annotations
 
This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type.
The service should handle three dimensions, even if the third one is set to NULL.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c3min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
  </xs:annotation>
</xs:element>
Element Spatial_RangeType / c1max
Namespace No namespace
Annotations
 
This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type.
The service should handle three dimensions, even if the third one is set to NULL.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c1max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
  </xs:annotation>
</xs:element>
Element Spatial_RangeType / c2max
Namespace No namespace
Annotations
 
This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type.
The service should handle three dimensions, even if the third one is set to NULL.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c2max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
  </xs:annotation>
</xs:element>
Element Spatial_RangeType / c3max
Namespace No namespace
Annotations
 
This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type.
The service should handle three dimensions, even if the third one is set to NULL.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c3max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialType / Spatial_frame_type
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#SpatialFrameTypeType_celestial EPNCore_xsd.tmp#SpatialFrameTypeType_body EPNCore_xsd.tmp#SpatialFrameTypeType_cartesian EPNCore_xsd.tmp#SpatialFrameTypeType_cylindrical EPNCore_xsd.tmp#SpatialFrameTypeType_spherical EPNCore_xsd.tmp#SpatialFrameTypeType
Type SpatialFrameTypeType
Properties
content: complex
minOccurs: 1
maxOccurs: 1
Model celestial | body | cartesian | cylindrical | spherical
Children body, cartesian, celestial, cylindrical, spherical
Instance
 
<Spatial_frame_type>
  <celestial>{1,1}</celestial>
  <body>{1,1}</body>
  <cartesian>{1,1}</cartesian>
  <cylindrical>{1,1}</cylindrical>
  <spherical>{1,1}</spherical>
</Spatial_frame_type>
Source
 
<xs:element name="Spatial_frame_type" minOccurs="1" maxOccurs="1" type="SpatialFrameTypeType">
</xs:element>
Element SpatialFrameTypeType / celestial
Namespace No namespace
Annotations
 
(2D angles on the sky, e.g. right ascension c1 and declination c2 + possibly distance from origin c3 – this is a special case of spherical frame),
Diagram
Diagram
Properties
fixed: celestial
Source
 
<xs:element name="celestial" fixed="celestial">
  <xs:annotation>
    <xs:documentation>(2D angles on the sky, e.g. right ascension c1 and declination c2 + possibly distance from origin c3 – this is a special case of spherical frame),</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialFrameTypeType / body
Namespace No namespace
Annotations
 
(2D angles on a rotating body, e.g. longitude c1 (and latitude c2 + possibly a z c3 coordinate)
longitudes always increase eastward, 
the Z coordinate can be the distance counted either from the reference surface or from the body center, TBC (frames are related to body centers, but a surface reference is required for atmospheric structure)
Diagram
Diagram
Properties
fixed: body
Source
 
<xs:element name="body" fixed="body">
  <xs:annotation>
    <xs:documentation>(2D angles on a rotating body, e.g. longitude c1 (and latitude c2 + possibly a z c3 coordinate) longitudes always increase eastward, the Z coordinate can be the distance counted either from the reference surface or from the body center, TBC (frames are related to body centers, but a surface reference is required for atmospheric structure)</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialFrameTypeType / cartesian
Namespace No namespace
Annotations
 
(x,y,z) as (c1, c2, c3)
Diagram
Diagram
Properties
fixed: cartesian
Source
 
<xs:element name="cartesian" fixed="cartesian">
  <xs:annotation>
    <xs:documentation>(x,y,z) as (c1, c2, c3)</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialFrameTypeType / cylindrical
Namespace No namespace
Annotations
 
(r, theta, z) as (c1, c2, c3)angles are defined in degrees
Diagram
Diagram
Properties
fixed: cylindrical
Source
 
<xs:element name="cylindrical" fixed="cylindrical">
  <xs:annotation>
    <xs:documentation>(r, theta, z) as (c1, c2, c3)angles are defined in degrees</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialFrameTypeType / spherical
Namespace No namespace
Annotations
 
(r, theta, phi) as (c1, c2, c3)angles are defined in degrees as in usual spherical systems (E longitude, zenithal angle). If related to the sky, “celestial” coordinates with RA/Dec must be used.
Diagram
Diagram
Properties
fixed: spherical
Source
 
<xs:element name="spherical" fixed="spherical">
  <xs:annotation>
    <xs:documentation>(r, theta, phi) as (c1, c2, c3)angles are defined in degrees as in usual spherical systems (E longitude, zenithal angle). If related to the sky, “celestial” coordinates with RA/Dec must be used.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialType / spatial_resolution
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#SpatialResolutionType_c1_resol_min EPNCore_xsd.tmp#SpatialResolutionType_c2_resol_min EPNCore_xsd.tmp#SpatialResolutionType_c3_resol_min EPNCore_xsd.tmp#SpatialResolutionType_c1_resol_max EPNCore_xsd.tmp#SpatialResolutionType_c2_resol_max EPNCore_xsd.tmp#SpatialResolutionType_c3_resol_max EPNCore_xsd.tmp#SpatialResolutionType
Type SpatialResolutionType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Model c1_resol_min{0,1} , c2_resol_min{0,1} , c3_resol_min{0,1} , c1_resol_max{0,1} , c2_resol_max{0,1} , c3_resol_max{0,1}
Children c1_resol_max, c1_resol_min, c2_resol_max, c2_resol_min, c3_resol_max, c3_resol_min
Instance
 
<spatial_resolution>
  <c1_resol_min>{0,1}</c1_resol_min>
  <c2_resol_min>{0,1}</c2_resol_min>
  <c3_resol_min>{0,1}</c3_resol_min>
  <c1_resol_max>{0,1}</c1_resol_max>
  <c2_resol_max>{0,1}</c2_resol_max>
  <c3_resol_max>{0,1}</c3_resol_max>
</spatial_resolution>
Source
 
<xs:element name="spatial_resolution" minOccurs="0" maxOccurs="1" type="SpatialResolutionType"/>
Element SpatialResolutionType / c1_resol_min
Namespace No namespace
Annotations
 
This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c1_resol_min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialResolutionType / c2_resol_min
Namespace No namespace
Annotations
 
This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c2_resol_min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialResolutionType / c3_resol_min
Namespace No namespace
Annotations
 
This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c3_resol_min" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialResolutionType / c1_resol_max
Namespace No namespace
Annotations
 
This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c1_resol_max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialResolutionType / c2_resol_max
Namespace No namespace
Annotations
 
This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c2_resol_max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element SpatialResolutionType / c3_resol_max
Namespace No namespace
Annotations
 
This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
 
<xs:element name="c3_resol_max" minOccurs="0" maxOccurs="1" type="xs:double">
  <xs:annotation>
    <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / view_angle
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#ViewAngleType_incidence_angle EPNCore_xsd.tmp#ViewAngleType_emergence_angle EPNCore_xsd.tmp#ViewAngleType_phase_angle EPNCore_xsd.tmp#ViewAngleType
Type ViewAngleType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model incidence_angle* , emergence_angle* , phase_angle*
Children emergence_angle, incidence_angle, phase_angle
Instance
 
<view_angle>
  <incidence_angle>{0,unbounded}</incidence_angle>
  <emergence_angle>{0,unbounded}</emergence_angle>
  <phase_angle>{0,unbounded}</phase_angle>
</view_angle>
Source
 
<xs:element name="view_angle" minOccurs="0" maxOccurs="unbounded" type="ViewAngleType"/>
Element ViewAngleType / incidence_angle
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#incidence_angleType_incidence_angle_min EPNCore_xsd.tmp#incidence_angleType_incidence_angle_max EPNCore_xsd.tmp#incidence_angleType
Type incidence_angleType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model incidence_angle_min* , incidence_angle_max*
Children incidence_angle_max, incidence_angle_min
Instance
 
<incidence_angle>
  <incidence_angle_min>{0,unbounded}</incidence_angle_min>
  <incidence_angle_max>{0,unbounded}</incidence_angle_max>
</incidence_angle>
Source
 
<xs:element name="incidence_angle" minOccurs="0" maxOccurs="unbounded" type="incidence_angleType">
</xs:element>
Element incidence_angleType / incidence_angle_min
Namespace No namespace
Annotations
 
. The incidence_angle parameter defines the upper and lower bounds of the incidence angle variation in the data. This is always indicated in decimal degrees.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="incidence_angle_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>. The incidence_angle parameter defines the upper and lower bounds of the incidence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
  </xs:annotation>
</xs:element>
Element incidence_angleType / incidence_angle_max
Namespace No namespace
Annotations
 
. The incidence_angle parameter defines the upper and lower bounds of the incidence angle variation in the data. This is always indicated in decimal degrees.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="incidence_angle_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>. The incidence_angle parameter defines the upper and lower bounds of the incidence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ViewAngleType / emergence_angle
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#emergence_angleType_emergence_angle_min EPNCore_xsd.tmp#emergence_angleType_emergence_angle_max EPNCore_xsd.tmp#emergence_angleType
Type emergence_angleType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model emergence_angle_min* , emergence_angle_max*
Children emergence_angle_max, emergence_angle_min
Instance
 
<emergence_angle>
  <emergence_angle_min>{0,unbounded}</emergence_angle_min>
  <emergence_angle_max>{0,unbounded}</emergence_angle_max>
</emergence_angle>
Source
 
<xs:element name="emergence_angle" minOccurs="0" maxOccurs="unbounded" type="emergence_angleType">
</xs:element>
Element emergence_angleType / emergence_angle_min
Namespace No namespace
Annotations
 
The emergence_angle parameter defines the upper and lower bounds of the emergence angle variation in the data. This is always indicated in decimal degrees.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="emergence_angle_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The emergence_angle parameter defines the upper and lower bounds of the emergence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
  </xs:annotation>
</xs:element>
Element emergence_angleType / emergence_angle_max
Namespace No namespace
Annotations
 
The emergence_angle parameter defines the upper and lower bounds of the emergence angle variation in the data. This is always indicated in decimal degrees.
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="emergence_angle_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The emergence_angle parameter defines the upper and lower bounds of the emergence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ViewAngleType / phase_angle
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#phase_angleType_phase_angle_min EPNCore_xsd.tmp#phase_angleType_phase_angle_max EPNCore_xsd.tmp#phase_angleType
Type phase_angleType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model phase_angle_min* , phase_angle_max*
Children phase_angle_max, phase_angle_min
Instance
 
<phase_angle>
  <phase_angle_min>{0,unbounded}</phase_angle_min>
  <phase_angle_max>{0,unbounded}</phase_angle_max>
</phase_angle>
Source
 
<xs:element name="phase_angle" minOccurs="0" maxOccurs="unbounded" type="phase_angleType">
</xs:element>
Element phase_angleType / phase_angle_min
Namespace No namespace
Annotations
 
The phase_angle parameter defines the upper and lower bounds of the phase angle variation in the data. This is always indicated in decimal degrees (+ define convention for negative values?).
Phase, incidence and emergence are partly related:
abs(i - e) smaler than (phi) smaler than  (i + e)
If the azimuth angle alpha is provided instead of the phase angle, the latter can be derived from knowledge of the three angles:
cos (alpha)=cos (i) cos (e) + cos (alpha) sin (i) sin (e)
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="phase_angle_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The phase_angle parameter defines the upper and lower bounds of the phase angle variation in the data. This is always indicated in decimal degrees (+ define convention for negative values?). Phase, incidence and emergence are partly related: abs(i - e) smaler than (phi) smaler than (i + e) If the azimuth angle alpha is provided instead of the phase angle, the latter can be derived from knowledge of the three angles: cos (alpha)=cos (i) cos (e) + cos (alpha) sin (i) sin (e)</xs:documentation>
  </xs:annotation>
</xs:element>
Element phase_angleType / phase_angle_max
Namespace No namespace
Annotations
 
The phase_angle parameter defines the upper and lower bounds of the phase angle variation in the data. This is always indicated in decimal degrees (+ define convention for negative values?).
Phase, incidence and emergence are partly related:
abs(i - e) smaler than (phi) smaler than  (i + e)
If the azimuth angle alpha is provided instead of the phase angle, the latter can be derived from knowledge of the three angles:
cos (alpha)=cos (i) cos (e) + cos (alpha) sin (i) sin (e)
Diagram
Diagram
Type xs:double
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="phase_angle_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
  <xs:annotation>
    <xs:documentation>The phase_angle parameter defines the upper and lower bounds of the phase angle variation in the data. This is always indicated in decimal degrees (+ define convention for negative values?). Phase, incidence and emergence are partly related: abs(i - e) smaler than (phi) smaler than (i + e) If the azimuth angle alpha is provided instead of the phase angle, the latter can be derived from knowledge of the three angles: cos (alpha)=cos (i) cos (e) + cos (alpha) sin (i) sin (e)</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / instrument_host_name
Namespace No namespace
Annotations
 
This parameter provides the name of the observatory or spacecraft which performed the measurements. 
The best practice is to use IAU observatory codes for ground-based observations: http://www.minorplanetcenter.net/iau/lists/ObsCodesF.html
Concerning space-borne data, SPICE clearly defines ID for space mission names:
http://www-int.stsci.edu/~sontag/spicedocs/req/naif_ids.html
and the PDS dictionary defines values for mission names
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="instrument_host_name" minOccurs="0" maxOccurs="unbounded" type="xs:string">
  <xs:annotation>
    <xs:documentation>This parameter provides the name of the observatory or spacecraft which performed the measurements. The best practice is to use IAU observatory codes for ground-based observations: http://www.minorplanetcenter.net/iau/lists/ObsCodesF.html Concerning space-borne data, SPICE clearly defines ID for space mission names: http://www-int.stsci.edu/~sontag/spicedocs/req/naif_ids.html and the PDS dictionary defines values for mission names</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / instrument_name
Namespace No namespace
Annotations
 
Identifies the instrument(s) that acquired the data.
Service providers are invited to include multiple values for instrument name, e.g., complete name + usual acronym. This will allow queries on either "VISIBLE AND INFRARED THERMAL IMAGING SPECTROMETER" or VIRTIS to produce the same reply.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="instrument_name" minOccurs="0" maxOccurs="unbounded" type="xs:string">
  <xs:annotation>
    <xs:documentation>Identifies the instrument(s) that acquired the data. Service providers are invited to include multiple values for instrument name, e.g., complete name + usual acronym. This will allow queries on either "VISIBLE AND INFRARED THERMAL IMAGING SPECTROMETER" or VIRTIS to produce the same reply.</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNCoreType / measurement_type
Namespace No namespace
Annotations
 
Measurement_type defines the physical quantities contained in the data. This is defined using a UCD.
The list of UCD is related to all quantities included in the service, not only those used for the data in the idis_core table.
The provider should use the UCD list from IVOA and extend it only if necessary.
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xs:element name="measurement_type" minOccurs="0" maxOccurs="unbounded" type="xs:string">
  <xs:annotation>
    <xs:documentation>Measurement_type defines the physical quantities contained in the data. This is defined using a UCD. The list of UCD is related to all quantities included in the service, not only those used for the data in the idis_core table. The provider should use the UCD list from IVOA and extend it only if necessary.</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNResponse
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#EPNResponseType_service_core EPNCore_xsd.tmp#EPNResponseType_service_curation EPNCore_xsd.tmp#EPNResponseType_file_info EPNCore_xsd.tmp#EPNResponseType_complementary_return_info EPNCore_xsd.tmp#EPNResponseType
Type EPNResponseType
Properties
content: complex
Model service_core , service_curation , file_info , complementary_return_info
Children complementary_return_info, file_info, service_core, service_curation
Instance
 
<EPNResponse xmlns="http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd">
  <service_core>{1,1}</service_core>
  <service_curation>{1,1}</service_curation>
  <file_info>{1,1}</file_info>
  <complementary_return_info>{1,1}</complementary_return_info>
</EPNResponse>
Source
 
<xs:element name="EPNResponse" type="EPNResponseType"/>
Element EPNResponseType / service_core
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#EPNCoreType_resource_type EPNCore_xsd.tmp#EPNCoreType_dataproduct_type EPNCore_xsd.tmp#EPNCoreType_target_name EPNCore_xsd.tmp#EPNCoreType_target_class EPNCore_xsd.tmp#EPNCoreType_time EPNCore_xsd.tmp#EPNCoreType_spectral EPNCore_xsd.tmp#EPNCoreType_spatial EPNCore_xsd.tmp#EPNCoreType_view_angle EPNCore_xsd.tmp#EPNCoreType_instrument_host_name EPNCore_xsd.tmp#EPNCoreType_instrument_name EPNCore_xsd.tmp#EPNCoreType_measurement_type EPNCore_xsd.tmp#EPNCoreType
Type EPNCoreType
Properties
content: complex
Model resource_type{0,1} , dataproduct_type* , target_name* , target_class* , time* , spectral* , spatial* , view_angle* , instrument_host_name* , instrument_name* , measurement_type*
Children dataproduct_type, instrument_host_name, instrument_name, measurement_type, resource_type, spatial, spectral, target_class, target_name, time, view_angle
Instance
 
<service_core>
  <resource_type>{0,1}</resource_type>
  <dataproduct_type>{0,unbounded}</dataproduct_type>
  <target_name>{0,unbounded}</target_name>
  <target_class>{0,unbounded}</target_class>
  <time>{0,unbounded}</time>
  <spectral>{0,unbounded}</spectral>
  <spatial>{0,unbounded}</spatial>
  <view_angle>{0,unbounded}</view_angle>
  <instrument_host_name>{0,unbounded}</instrument_host_name>
  <instrument_name>{0,unbounded}</instrument_name>
  <measurement_type>{0,unbounded}</measurement_type>
</service_core>
Source
 
<xs:element name="service_core" type="EPNCoreType"/>
Element EPNResponseType / service_curation
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#CurationMetadataType_publisher EPNCore_xsd.tmp#CurationMetadataType_reference EPNCore_xsd.tmp#CurationMetadataType_collection-id EPNCore_xsd.tmp#CurationMetadataType_title EPNCore_xsd.tmp#CurationMetadataType
Type CurationMetadataType
Properties
content: complex
Model publisher* , reference* , collection-id{0,1} , title{0,1}
Children collection-id, publisher, reference, title
Instance
 
<service_curation>
  <publisher ivo-id="">{0,unbounded}</publisher>
  <reference format="">{0,unbounded}</reference>
  <collection-id>{0,1}</collection-id>
  <title>{0,1}</title>
</service_curation>
Source
 
<xs:element name="service_curation" type="CurationMetadataType"/>
Element CurationMetadataType / publisher
Namespace No namespace
Annotations
 
name of the publisher
Diagram
Diagram VOResource-v1_0_xsd.tmp#ResourceName_ivo-id VOResource-v1_0_xsd.tmp#ResourceName
Type vr:ResourceName
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
ivo-id vr:IdentifierURI optional 
The URI form of the IVOA identifier for the resource refered to
Source
 
<xs:element name="publisher" type="vr:ResourceName" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>name of the publisher</xs:documentation>
  </xs:annotation>
</xs:element>
Element CurationMetadataType / reference
Namespace No namespace
Annotations
 
bibcode for reference URL
Diagram
Diagram VOResource-v1_0_xsd.tmp#Source_format VOResource-v1_0_xsd.tmp#Source
Type vr:Source
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
format xs:string optional 
The reference format.  Recognized values include "bibcode", 
referring to a standard astronomical bibcode 
(http://cdsweb.u-strasbg.fr/simbad/refcode.html).
Source
 
<xs:element name="reference" type="vr:Source" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>bibcode for reference URL</xs:documentation>
  </xs:annotation>
</xs:element>
Element CurationMetadataType / collection-id
Namespace No namespace
Annotations
 
The URI form of the IVOA identifier for the service 
describing the capability refered to by this element.
Diagram
Diagram VOResource-v1_0_xsd.tmp#IdentifierURI
Type vr:IdentifierURI
Properties
content: simple
minOccurs: 0
Facets
pattern ivo://[\w\d][\w\d\-_\.!~\*'\(\)\+=]{2,}(/[\w\d\-_\.!~\*'\(\)\+=]+(/[\w\d\-_\.!~\*'\(\)\+=]+)*)?
Source
 
<xs:element name="collection-id" type="vr:IdentifierURI" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The URI form of the IVOA identifier for the service describing the capability refered to by this element.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CurationMetadataType / title
Namespace No namespace
Annotations
 
This parameter provides the title of the data service.
Diagram
Diagram
Type xs:token
Properties
content: simple
minOccurs: 0
Source
 
<xs:element name="title" type="xs:token" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This parameter provides the title of the data service.</xs:documentation>
  </xs:annotation>
</xs:element>
Element EPNResponseType / file_info
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#FileType_accessURL EPNCore_xsd.tmp#FileType_access_format EPNCore_xsd.tmp#FileType_access_estsize EPNCore_xsd.tmp#FileType
Type FileType
Properties
content: complex
Model accessURL{0,1} , access_format{0,1} , access_estsize{0,1}
Children accessURL, access_estsize, access_format
Instance
 
<file_info>
  <accessURL use="">{0,1}</accessURL>
  <access_format>{0,1}</access_format>
  <access_estsize>{0,1}</access_estsize>
</file_info>
Source
 
<xs:element name="file_info" type="FileType"/>
Element FileType / accessURL
Namespace No namespace
Annotations
 
The URL that can be used to download the data.
Diagram
Diagram VOResource-v1_0_xsd.tmp#AccessURL_use VOResource-v1_0_xsd.tmp#AccessURL
Type vr:AccessURL
Properties
content: complex
minOccurs: 0
Attributes
QName Type Fixed Default Use Annotation
use restriction of xs:NMTOKEN optional 
A flag indicating whether this should be interpreted as a base
URL, a full URL, or a URL to a directory that will produce a 
listing of files.
 
The default value assumed when one is not given depends on the 
context.
Source
 
<xs:element name="accessURL" type="vr:AccessURL" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The URL that can be used to download the data.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / access_format
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
 
<xs:element name="access_format" type="xs:string" minOccurs="0"/>
Element FileType / access_estsize
Namespace No namespace
Diagram
Diagram
Type xs:integer
Properties
content: simple
minOccurs: 0
Source
 
<xs:element name="access_estsize" type="xs:integer" minOccurs="0"/>
Element EPNResponseType / complementary_return_info
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#ComplementaryReturnInfoType_time_scale EPNCore_xsd.tmp#ComplementaryReturnInfoType_time_origin EPNCore_xsd.tmp#ComplementaryReturnInfoType_Spatial_coordinate_description EPNCore_xsd.tmp#ComplementaryReturnInfoType_Spatial_origin EPNCore_xsd.tmp#ComplementaryReturnInfoType_processing_level EPNCore_xsd.tmp#ComplementaryReturnInfoType_target_region EPNCore_xsd.tmp#ComplementaryReturnInfoType
Type ComplementaryReturnInfoType
Properties
content: complex
Model time_scale{0,1} , time_origin{0,1} , Spatial_coordinate_description{0,1} , Spatial_origin{0,1} , processing_level{0,1} , target_region{0,1}
Children Spatial_coordinate_description, Spatial_origin, processing_level, target_region, time_origin, time_scale
Instance
 
<complementary_return_info>
  <time_scale>{0,1}</time_scale>
  <time_origin>{0,1}</time_origin>
  <Spatial_coordinate_description>{0,1}</Spatial_coordinate_description>
  <Spatial_origin>{0,1}</Spatial_origin>
  <processing_level>{0,1}</processing_level>
  <target_region>{0,1}</target_region>
</complementary_return_info>
Source
 
<xs:element name="complementary_return_info" type="ComplementaryReturnInfoType"/>
Element ComplementaryReturnInfoType / time_scale
Namespace No namespace
Diagram
Diagram stc-v1_30_xsd.tmp#timeScaleType
Type timeScaleType
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Facets
enumeration TT 
Terrestrial Time; the basis for ephemerides
enumeration TDT 
Obsolete synonym for TT
enumeration ET 
Ephemeris Time; predecessor of, and continuous with, TT
enumeration TDB 
Barycentric Dynamic Time:the independent variable in planetay ephemerides; time at the solar system barycenter synchronous with TT on an annual basis; sometimes called TEB
enumeration TEB 
Barycentric Ephemeris Time: time at the solar system barycenter synchronous with TT on an annual basis; a deprecated synonym of TDB.
enumeration TCG 
Terrestrial Coordinate Time
enumeration TCB 
Barycentric Coordinate Time; runs slower than TDB but is consistent with physical constants
enumeration TAI 
International Atomic Time; runs 32.184 s behind TT
enumeration IAT 
Synonym for TAI
enumeration UTC 
Coordinated Universal Time; currently (2006) runs 33 leapseconds behind TAI
enumeration GPS 
Global Positioning System's time scale; runs 19 s behind TAI, 51.184 s behind TT.
enumeration LST 
Local Siderial Time; only for ground-based observations; note that the second is shorter
enumeration GMST 
Greenwich Mean Siderial Time; only for ground-based observations; note that the second is shorter
enumeration LOCAL 
Only to be used for simulations in conjunction with a relocatable spatial frame
Source
 
<xs:element minOccurs="0" maxOccurs="1" name="time_scale" type="stc:timeScaleType">
</xs:element>
Element ComplementaryReturnInfoType / time_origin
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
 
<xs:element minOccurs="0" name="time_origin" type="xs:string">
</xs:element>
Element ComplementaryReturnInfoType / Spatial_coordinate_description
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
 
<xs:element minOccurs="0" name="Spatial_coordinate_description" type="xs:string">
</xs:element>
Element ComplementaryReturnInfoType / Spatial_origin
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
 
<xs:element minOccurs="0" name="Spatial_origin" type="xs:string">
</xs:element>
Element ComplementaryReturnInfoType / processing_level
Namespace No namespace
Diagram
Diagram EPNCore_xsd.tmp#ProcessingLevelType
Type ProcessingLevelType
Properties
content: simple
minOccurs: 0
Facets
enumeration 1 
raw data : Unprocessed Data Record 
(low level encoding, e.g. telemetry from a spacecraft instrument. Normally available only to the original team)
enumeration 2 
edited : Experiment Data Record 
(often referred to as “raw data”: decommutated, but still affected by instrumental effects)
enumeration 3 
partially calibrated data : Reduced Data Record (“calibrated” in physical units)
enumeration 4 
resampled : Reformatted Data Record
(mosaics or composite of several observing sessions, involving some level of data fusion)
enumeration 5 
derived : Derived Data Record
(results of data analysis, directly usable by other communities with no further processing)
enumeration 6 
Ancillary Data Record 
(extra data specifically supporting a data set, such as coordinates, geometry…)
Source
 
<xs:element minOccurs="0" name="processing_level" type="ProcessingLevelType">
</xs:element>
Element ComplementaryReturnInfoType / target_region
Namespace No namespace
Annotations
 
This parameter briefly identifies the region of interest for the data set, in complement to target name – it is not mandatory. This parameter only introduces generic regions, not specific local names (see examples below).
The best practice is to take the values from standard sources:
- IAU thesaurus	http://www.mso.anu.edu.au/library/thesaurus/ 
 	+ another version: http://www.vocabularyserver.com/trex/en/ 
The second one seems more recent and more complete (although the interface is not practical)
- Spase dictionary 	“http://www.spase-group.org/”
Diagram
Diagram
Type xs:string
Properties
content: simple
minOccurs: 0
Source
 
<xs:element minOccurs="0" name="target_region" type="xs:string">
  <xs:annotation>
    <xs:documentation>This parameter briefly identifies the region of interest for the data set, in complement to target name – it is not mandatory. This parameter only introduces generic regions, not specific local names (see examples below). The best practice is to take the values from standard sources: - IAU thesaurus http://www.mso.anu.edu.au/library/thesaurus/ + another version: http://www.vocabularyserver.com/trex/en/ The second one seems more recent and more complete (although the interface is not practical) - Spase dictionary “http://www.spase-group.org/”</xs:documentation>
  </xs:annotation>
</xs:element>
Complex Type EPNCoreType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#EPNCoreType_resource_type EPNCore_xsd.tmp#EPNCoreType_dataproduct_type EPNCore_xsd.tmp#EPNCoreType_target_name EPNCore_xsd.tmp#EPNCoreType_target_class EPNCore_xsd.tmp#EPNCoreType_time EPNCore_xsd.tmp#EPNCoreType_spectral EPNCore_xsd.tmp#EPNCoreType_spatial EPNCore_xsd.tmp#EPNCoreType_view_angle EPNCore_xsd.tmp#EPNCoreType_instrument_host_name EPNCore_xsd.tmp#EPNCoreType_instrument_name EPNCore_xsd.tmp#EPNCoreType_measurement_type
Used by
Model resource_type{0,1} , dataproduct_type* , target_name* , target_class* , time* , spectral* , spatial* , view_angle* , instrument_host_name* , instrument_name* , measurement_type*
Children dataproduct_type, instrument_host_name, instrument_name, measurement_type, resource_type, spatial, spectral, target_class, target_name, time, view_angle
Source
 
<xs:complexType name="EPNCoreType">
  <xs:sequence>
    <xs:element name="resource_type" type="ResourceClassType" minOccurs="0" maxOccurs="1" default="dataset">
      <xs:annotation>
        <xs:documentation>A dataset is a consistent set of data and associated metadata. A dataset can be comprised of files, tables, or data computed on the fly. A granule is the smallest element reachable in a dataset: either a file, a group of associated files, a table entry, or some kind of data computed on the fly.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="dataproduct_type" maxOccurs="unbounded" minOccurs="0">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="image">
            <xs:annotation>
              <xs:documentation>associated scalar fields with two spatial axes, e.g., images with multiple color planes, from multichannel cameras for example. Maps of planetary surfaces are considered as images.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="spectrum">
            <xs:annotation>
              <xs:documentation>data product which spectral coverage is the primary attribute, e.g., a set of spectra.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="dynamic_spectrum">
            <xs:annotation>
              <xs:documentation>consecutive spectral measurements through time, organized as a time series.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="spectral_cube">
            <xs:annotation>
              <xs:documentation>set of spectral measurements with 1 or 2D spatial coverage, e.g., imaging spectroscopy. The choice between Image and spectral_cube is related to the characteristics of the instrument..</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="profile">
            <xs:annotation>
              <xs:documentation>scalar or vectorial measurements along 1 spatial dimension, e.g., atmospheric profiles, atmospheric paths, sub-surface profiles…</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="volume">
            <xs:annotation>
              <xs:documentation>other measurements with 3 spatial dimensions, e.g., internal or atmospheric structures.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="movie">
            <xs:annotation>
              <xs:documentation>sets of chronological 2D spatial measurements</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="cube">
            <xs:annotation>
              <xs:documentation>multidimensional data with 3 or more axes, e.g., all that is not described by other 3D data types such as spectral cubes or volume.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="time_series">
            <xs:annotation>
              <xs:documentation>measurements organized primarily as a function of time (with exception of dynamical spectra). A Spacecraft dust detector measurement is a typical example of a time series.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="catalog">
            <xs:annotation>
              <xs:documentation>can be a list of events, a catalog of object parameters, a list of features.... E.g., a list of asteroid properties. Can also be a single element.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="spatial_vector">
            <xs:annotation>
              <xs:documentation>list of summit coordinates defining a vector, e.g., vector information from a GIS, spatial footprints…</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="target_name" maxOccurs="unbounded" minOccurs="0" type="xs:string">
      <xs:annotation>
        <xs:documentation>derive from type=ept:TaregetType.TargetName</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="target_class" type="TargetClass">
    </xs:element>
    <xs:element maxOccurs="unbounded" minOccurs="0" name="time" type="Time_Type">
    </xs:element>
    <xs:element name="spectral" minOccurs="0" maxOccurs="unbounded" type="SpectralType"/>
    <xs:element name="spatial" minOccurs="0" maxOccurs="unbounded" type="SpatialType"/>
    <xs:element name="view_angle" minOccurs="0" maxOccurs="unbounded" type="ViewAngleType"/>
    <xs:element name="instrument_host_name" minOccurs="0" maxOccurs="unbounded" type="xs:string">
      <xs:annotation>
        <xs:documentation>This parameter provides the name of the observatory or spacecraft which performed the measurements. The best practice is to use IAU observatory codes for ground-based observations: http://www.minorplanetcenter.net/iau/lists/ObsCodesF.html Concerning space-borne data, SPICE clearly defines ID for space mission names: http://www-int.stsci.edu/~sontag/spicedocs/req/naif_ids.html and the PDS dictionary defines values for mission names</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="instrument_name" minOccurs="0" maxOccurs="unbounded" type="xs:string">
      <xs:annotation>
        <xs:documentation>Identifies the instrument(s) that acquired the data. Service providers are invited to include multiple values for instrument name, e.g., complete name + usual acronym. This will allow queries on either "VISIBLE AND INFRARED THERMAL IMAGING SPECTROMETER" or VIRTIS to produce the same reply.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="measurement_type" minOccurs="0" maxOccurs="unbounded" type="xs:string">
      <xs:annotation>
        <xs:documentation>Measurement_type defines the physical quantities contained in the data. This is defined using a UCD. The list of UCD is related to all quantities included in the service, not only those used for the data in the idis_core table. The provider should use the UCD list from IVOA and extend it only if necessary.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Simple Type ResourceClassType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Annotations
 
Definition of the classes of resources
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration dataset
enumeration granule
Used by
Source
 
<xs:simpleType name="ResourceClassType">
  <xs:annotation>
    <xs:documentation>Definition of the classes of resources</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="dataset"/>
    <xs:enumeration value="granule"/>
  </xs:restriction>
</xs:simpleType>
Simple Type TargetClass
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Annotations
 
Enumarated list of target types as defined by the Planetary Science data model
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration asteroid
enumeration comet
enumeration dwarf_planet
enumeration exoplanet
enumeration interplanetary_medium
enumeration planet
enumeration ring
enumeration sample
enumeration satellite
enumeration sky
enumeration spacecraft
enumeration spacejunk
enumeration star
Used by
Source
 
<xs:simpleType name="TargetClass">
  <xs:annotation>
    <xs:documentation>Enumarated list of target types as defined by the Planetary Science data model</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration id="ast" value="asteroid"/>
    <xs:enumeration id="com" value="comet"/>
    <xs:enumeration id="dwa" value="dwarf_planet"/>
    <xs:enumeration id="exo" value="exoplanet"/>
    <xs:enumeration id="ipm" value="interplanetary_medium"/>
    <xs:enumeration id="ppl" value="planet"/>
    <xs:enumeration id="rin" value="ring"/>
    <xs:enumeration id="sam" value="sample"/>
    <xs:enumeration id="sat" value="satellite"/>
    <xs:enumeration id="sky" value="sky"/>
    <xs:enumeration id="spc" value="spacecraft"/>
    <xs:enumeration id="spj" value="spacejunk"/>
    <xs:enumeration id="sta" value="star"/>
  </xs:restriction>
</xs:simpleType>
Complex Type Time_Type
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#Time_Type_time_min EPNCore_xsd.tmp#Time_Type_time_max EPNCore_xsd.tmp#Time_Type_time_sampling_step_min EPNCore_xsd.tmp#Time_Type_time_sampling_step_max EPNCore_xsd.tmp#Time_Type_time_exp_min EPNCore_xsd.tmp#Time_Type_time_exp_max
Used by
Model time_min{0,1} , time_max{0,1} , time_sampling_step_min{0,1} , time_sampling_step_max{0,1} , time_exp_min{0,1} , time_exp_max{0,1}
Children time_exp_max, time_exp_min, time_max, time_min, time_sampling_step_max, time_sampling_step_min
Source
 
<xs:complexType name="Time_Type">
  <xs:sequence>
    <xs:element name="time_min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>"The time parameter(s) provides the date and time of acquisition. It may be a couple of parameters to handle long periods in some datasets. This parameter is provided in Julian days, expressed as a double precision float. Although ObsCore uses Modified JD, EPNCore uses JD to avoid ambiguity with time origin. With double precision floats, the accuracy is on the order of 1 ms. Whenever time is defined by a single parameter, both time_min and time_max contain the same "</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="time_max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>"The time parameter(s) provides the date and time of acquisition. It may be a couple of parameters to handle long periods in some datasets. This parameter is provided in Julian days, expressed as a double precision float. Although ObsCore uses Modified JD, EPNCore uses JD to avoid ambiguity with time origin. With double precision floats, the accuracy is on the order of 1 ms. Whenever time is defined by a single parameter, both t_min and t_max contain the same "</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" maxOccurs="1" name="time_sampling_step_min" type="xs:double">
      <xs:annotation>
        <xs:documentation>"This parameter provides the sampling time for measurements of dynamical phenomena, and for computations. This is the time between 2 successive measurements/data. This may be a query parameter e.g. for ephemeris computations. expressed in second "</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element minOccurs="0" maxOccurs="1" name="time_sampling_step_max" type="xs:double">
      <xs:annotation>
        <xs:documentation>"This parameter provides the sampling time for measurements of dynamical phenomena, and for computations. This is the time between 2 successive measurements/data. This may be a query parameter e.g. for ephemeris computations. expressed in second "</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="time_exp_min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter corresponds to the minimum integration time of measurements. This time is usually shorter than the time_sampling_step (if both are present).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="time_exp_max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter corresponds to the maximum integration time of measurements. This time is usually shorter than the time_sampling_step (if both are present).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type SpectralType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#SpectralType_spectral_range_min EPNCore_xsd.tmp#SpectralType_spectral_range_max EPNCore_xsd.tmp#SpectralType_spectral_sampling_step_min EPNCore_xsd.tmp#SpectralType_spectral_sampling_step_max EPNCore_xsd.tmp#SpectralType_spectral_resolution_min EPNCore_xsd.tmp#SpectralType_spectral_resolution_max
Used by
Model spectral_range_min* , spectral_range_max* , spectral_sampling_step_min* , spectral_sampling_step_max* , spectral_resolution_min* , spectral_resolution_max*
Children spectral_range_max, spectral_range_min, spectral_resolution_max, spectral_resolution_min, spectral_sampling_step_max, spectral_sampling_step_min
Source
 
<xs:complexType name="SpectralType">
  <xs:sequence>
    <xs:element name="spectral_range_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The spectral_range is expressed on a frequency in Hertz. It defines the lower bounds of the spectral domain where data have intersection with the requested spectral range.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="spectral_range_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The spectral_range is expressed on a frequency in Hertz. It defines the upper bounds of the spectral domain where data have intersection with the requested spectral range.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="spectral_sampling_step_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The spectral_sampling_step is the spectral separation (counted in Hz) between the centers of two adjacent filters or channels). Min is the lower level. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and Fourier spectrometers, or observations related to surfaces or atmospheres.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="spectral_sampling_step_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The spectral_sampling_step is the spectral separation (counted in Hz) between the centers of two adjacent filters or channels). Min is the upper level. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and Fourier spectrometers, or observations related to surfaces or atmospheres.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="spectral_resolution_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The spectral_resolution corresponds to the spectral bandwidth used for the measurement. In case of filter camera this is the filter bandwidth; in case of spectrometer this is the spectral resolution. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and filter cameras.. Min is the lower level.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="spectral_resolution_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The spectral_resolution corresponds to the spectral bandwidth used for the measurement. In case of filter camera this is the filter bandwidth; in case of spectrometer this is the spectral resolution. This is mostly intended to provide an order of magnitude, e.g. to distinguish between grating spectrometers and filter cameras.. Max is the upper level.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type SpatialType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#SpatialType_spatial_range EPNCore_xsd.tmp#SpatialType_Spatial_frame_type EPNCore_xsd.tmp#SpatialType_spatial_resolution
Used by
Model spatial_range* , Spatial_frame_type , spatial_resolution{0,1}
Children Spatial_frame_type, spatial_range, spatial_resolution
Source
 
<xs:complexType name="SpatialType">
  <xs:sequence>
    <xs:element name="spatial_range" minOccurs="0" maxOccurs="unbounded" type="Spatial_RangeType">
    </xs:element>
    <xs:element name="Spatial_frame_type" minOccurs="1" maxOccurs="1" type="SpatialFrameTypeType">
    </xs:element>
    <xs:element name="spatial_resolution" minOccurs="0" maxOccurs="1" type="SpatialResolutionType"/>
  </xs:sequence>
</xs:complexType>
Complex Type Spatial_RangeType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#Spatial_RangeType_c1min EPNCore_xsd.tmp#Spatial_RangeType_c2min EPNCore_xsd.tmp#Spatial_RangeType_c3min EPNCore_xsd.tmp#Spatial_RangeType_c1max EPNCore_xsd.tmp#Spatial_RangeType_c2max EPNCore_xsd.tmp#Spatial_RangeType_c3max
Used by
Model c1min{0,1} , c2min{0,1} , c3min{0,1} , c1max{0,1} , c2max{0,1} , c3max{0,1}
Children c1max, c1min, c2max, c2min, c3max, c3min
Source
 
<xs:complexType name="Spatial_RangeType">
  <xs:sequence>
    <xs:element name="c1min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c2min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c3min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c1max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c2max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c3max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides up to three spatial coordinates, in a form depending on the spatial frame type. The service should handle three dimensions, even if the third one is set to NULL.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type SpatialFrameTypeType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#SpatialFrameTypeType_celestial EPNCore_xsd.tmp#SpatialFrameTypeType_body EPNCore_xsd.tmp#SpatialFrameTypeType_cartesian EPNCore_xsd.tmp#SpatialFrameTypeType_cylindrical EPNCore_xsd.tmp#SpatialFrameTypeType_spherical
Used by
Model celestial | body | cartesian | cylindrical | spherical
Children body, cartesian, celestial, cylindrical, spherical
Source
 
<xs:complexType name="SpatialFrameTypeType">
  <xs:choice>
    <xs:element name="celestial" fixed="celestial">
      <xs:annotation>
        <xs:documentation>(2D angles on the sky, e.g. right ascension c1 and declination c2 + possibly distance from origin c3 – this is a special case of spherical frame),</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="body" fixed="body">
      <xs:annotation>
        <xs:documentation>(2D angles on a rotating body, e.g. longitude c1 (and latitude c2 + possibly a z c3 coordinate) longitudes always increase eastward, the Z coordinate can be the distance counted either from the reference surface or from the body center, TBC (frames are related to body centers, but a surface reference is required for atmospheric structure)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="cartesian" fixed="cartesian">
      <xs:annotation>
        <xs:documentation>(x,y,z) as (c1, c2, c3)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="cylindrical" fixed="cylindrical">
      <xs:annotation>
        <xs:documentation>(r, theta, z) as (c1, c2, c3)angles are defined in degrees</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="spherical" fixed="spherical">
      <xs:annotation>
        <xs:documentation>(r, theta, phi) as (c1, c2, c3)angles are defined in degrees as in usual spherical systems (E longitude, zenithal angle). If related to the sky, “celestial” coordinates with RA/Dec must be used.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
Complex Type SpatialResolutionType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#SpatialResolutionType_c1_resol_min EPNCore_xsd.tmp#SpatialResolutionType_c2_resol_min EPNCore_xsd.tmp#SpatialResolutionType_c3_resol_min EPNCore_xsd.tmp#SpatialResolutionType_c1_resol_max EPNCore_xsd.tmp#SpatialResolutionType_c2_resol_max EPNCore_xsd.tmp#SpatialResolutionType_c3_resol_max
Used by
Model c1_resol_min{0,1} , c2_resol_min{0,1} , c3_resol_min{0,1} , c1_resol_max{0,1} , c2_resol_max{0,1} , c3_resol_max{0,1}
Children c1_resol_max, c1_resol_min, c2_resol_max, c2_resol_min, c3_resol_max, c3_resol_min
Source
 
<xs:complexType name="SpatialResolutionType">
  <xs:sequence>
    <xs:element name="c1_resol_min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c2_resol_min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c3_resol_min" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c1_resol_max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c2_resol_max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="c3_resol_max" minOccurs="0" maxOccurs="1" type="xs:double">
      <xs:annotation>
        <xs:documentation>This parameter provides a simple estimate of resolution, either the FWHM of the PFS on the sky (in degrees [or mas]), or the pixel size on a surface (in km [or m]), depending on spatial_frame_type.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type ViewAngleType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#ViewAngleType_incidence_angle EPNCore_xsd.tmp#ViewAngleType_emergence_angle EPNCore_xsd.tmp#ViewAngleType_phase_angle
Used by
Model incidence_angle* , emergence_angle* , phase_angle*
Children emergence_angle, incidence_angle, phase_angle
Source
 
<xs:complexType name="ViewAngleType">
  <xs:sequence>
    <xs:element name="incidence_angle" minOccurs="0" maxOccurs="unbounded" type="incidence_angleType">
    </xs:element>
    <xs:element name="emergence_angle" minOccurs="0" maxOccurs="unbounded" type="emergence_angleType">
    </xs:element>
    <xs:element name="phase_angle" minOccurs="0" maxOccurs="unbounded" type="phase_angleType">
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type incidence_angleType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#incidence_angleType_incidence_angle_min EPNCore_xsd.tmp#incidence_angleType_incidence_angle_max
Used by
Model incidence_angle_min* , incidence_angle_max*
Children incidence_angle_max, incidence_angle_min
Source
 
<xs:complexType name="incidence_angleType">
  <xs:sequence>
    <xs:element name="incidence_angle_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>. The incidence_angle parameter defines the upper and lower bounds of the incidence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="incidence_angle_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>. The incidence_angle parameter defines the upper and lower bounds of the incidence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type emergence_angleType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#emergence_angleType_emergence_angle_min EPNCore_xsd.tmp#emergence_angleType_emergence_angle_max
Used by
Model emergence_angle_min* , emergence_angle_max*
Children emergence_angle_max, emergence_angle_min
Source
 
<xs:complexType name="emergence_angleType">
  <xs:sequence>
    <xs:element name="emergence_angle_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The emergence_angle parameter defines the upper and lower bounds of the emergence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="emergence_angle_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The emergence_angle parameter defines the upper and lower bounds of the emergence angle variation in the data. This is always indicated in decimal degrees.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type phase_angleType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#phase_angleType_phase_angle_min EPNCore_xsd.tmp#phase_angleType_phase_angle_max
Used by
Model phase_angle_min* , phase_angle_max*
Children phase_angle_max, phase_angle_min
Source
 
<xs:complexType name="phase_angleType">
  <xs:sequence>
    <xs:element name="phase_angle_min" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The phase_angle parameter defines the upper and lower bounds of the phase angle variation in the data. This is always indicated in decimal degrees (+ define convention for negative values?). Phase, incidence and emergence are partly related: abs(i - e) smaler than (phi) smaler than (i + e) If the azimuth angle alpha is provided instead of the phase angle, the latter can be derived from knowledge of the three angles: cos (alpha)=cos (i) cos (e) + cos (alpha) sin (i) sin (e)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="phase_angle_max" minOccurs="0" maxOccurs="unbounded" type="xs:double">
      <xs:annotation>
        <xs:documentation>The phase_angle parameter defines the upper and lower bounds of the phase angle variation in the data. This is always indicated in decimal degrees (+ define convention for negative values?). Phase, incidence and emergence are partly related: abs(i - e) smaler than (phi) smaler than (i + e) If the azimuth angle alpha is provided instead of the phase angle, the latter can be derived from knowledge of the three angles: cos (alpha)=cos (i) cos (e) + cos (alpha) sin (i) sin (e)</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type EPNResponseType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#EPNResponseType_service_core EPNCore_xsd.tmp#EPNResponseType_service_curation EPNCore_xsd.tmp#EPNResponseType_file_info EPNCore_xsd.tmp#EPNResponseType_complementary_return_info
Used by
Element EPNResponse
Model service_core , service_curation , file_info , complementary_return_info
Children complementary_return_info, file_info, service_core, service_curation
Source
 
<xs:complexType name="EPNResponseType">
  <xs:sequence>
    <xs:element name="service_core" type="EPNCoreType"/>
    <xs:element name="service_curation" type="CurationMetadataType"/>
    <xs:element name="file_info" type="FileType"/>
    <xs:element name="complementary_return_info" type="ComplementaryReturnInfoType"/>
  </xs:sequence>
</xs:complexType>
Complex Type CurationMetadataType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#CurationMetadataType_publisher EPNCore_xsd.tmp#CurationMetadataType_reference EPNCore_xsd.tmp#CurationMetadataType_collection-id EPNCore_xsd.tmp#CurationMetadataType_title
Used by
Model publisher* , reference* , collection-id{0,1} , title{0,1}
Children collection-id, publisher, reference, title
Source
 
<xs:complexType name="CurationMetadataType">
  <xs:sequence>
    <xs:element name="publisher" type="vr:ResourceName" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>name of the publisher</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="reference" type="vr:Source" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>bibcode for reference URL</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="collection-id" type="vr:IdentifierURI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The URI form of the IVOA identifier for the service describing the capability refered to by this element.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="title" type="xs:token" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This parameter provides the title of the data service.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type FileType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#FileType_accessURL EPNCore_xsd.tmp#FileType_access_format EPNCore_xsd.tmp#FileType_access_estsize
Used by
Model accessURL{0,1} , access_format{0,1} , access_estsize{0,1}
Children accessURL, access_estsize, access_format
Source
 
<xs:complexType name="FileType">
  <xs:sequence>
    <xs:element name="accessURL" type="vr:AccessURL" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The URL that can be used to download the data.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="access_format" type="xs:string" minOccurs="0"/>
    <xs:element name="access_estsize" type="xs:integer" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>
Complex Type ComplementaryReturnInfoType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore_xsd.tmp#ComplementaryReturnInfoType_time_scale EPNCore_xsd.tmp#ComplementaryReturnInfoType_time_origin EPNCore_xsd.tmp#ComplementaryReturnInfoType_Spatial_coordinate_description EPNCore_xsd.tmp#ComplementaryReturnInfoType_Spatial_origin EPNCore_xsd.tmp#ComplementaryReturnInfoType_processing_level EPNCore_xsd.tmp#ComplementaryReturnInfoType_target_region
Used by
Model time_scale{0,1} , time_origin{0,1} , Spatial_coordinate_description{0,1} , Spatial_origin{0,1} , processing_level{0,1} , target_region{0,1}
Children Spatial_coordinate_description, Spatial_origin, processing_level, target_region, time_origin, time_scale
Source
 
<xs:complexType name="ComplementaryReturnInfoType">
  <xs:sequence>
    <xs:element minOccurs="0" maxOccurs="1" name="time_scale" type="stc:timeScaleType">
    </xs:element>
    <xs:element minOccurs="0" name="time_origin" type="xs:string">
    </xs:element>
    <xs:element minOccurs="0" name="Spatial_coordinate_description" type="xs:string">
    </xs:element>
    <xs:element minOccurs="0" name="Spatial_origin" type="xs:string">
    </xs:element>
    <xs:element minOccurs="0" name="processing_level" type="ProcessingLevelType">
    </xs:element>
    <xs:element minOccurs="0" name="target_region" type="xs:string">
      <xs:annotation>
        <xs:documentation>This parameter briefly identifies the region of interest for the data set, in complement to target name – it is not mandatory. This parameter only introduces generic regions, not specific local names (see examples below). The best practice is to take the values from standard sources: - IAU thesaurus http://www.mso.anu.edu.au/library/thesaurus/ + another version: http://www.vocabularyserver.com/trex/en/ The second one seems more recent and more complete (although the interface is not practical) - Spase dictionary “http://www.spase-group.org/”</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Simple Type ProcessingLevelType
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration 1 
raw data : Unprocessed Data Record 
(low level encoding, e.g. telemetry from a spacecraft instrument. Normally available only to the original team)
enumeration 2 
edited : Experiment Data Record 
(often referred to as “raw data”: decommutated, but still affected by instrumental effects)
enumeration 3 
partially calibrated data : Reduced Data Record (“calibrated” in physical units)
enumeration 4 
resampled : Reformatted Data Record
(mosaics or composite of several observing sessions, involving some level of data fusion)
enumeration 5 
derived : Derived Data Record
(results of data analysis, directly usable by other communities with no further processing)
enumeration 6 
Ancillary Data Record 
(extra data specifically supporting a data set, such as coordinates, geometry…)
Used by
Source
 
<xs:simpleType name="ProcessingLevelType">
  <xs:restriction base="xs:string">
    <xs:enumeration value="1">
      <xs:annotation>
        <xs:documentation>raw data : Unprocessed Data Record (low level encoding, e.g. telemetry from a spacecraft instrument. Normally available only to the original team)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="2">
      <xs:annotation>
        <xs:documentation>edited : Experiment Data Record (often referred to as “raw data”: decommutated, but still affected by instrumental effects)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="3">
      <xs:annotation>
        <xs:documentation>partially calibrated data : Reduced Data Record (“calibrated” in physical units)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="4">
      <xs:annotation>
        <xs:documentation>resampled : Reformatted Data Record (mosaics or composite of several observing sessions, involving some level of data fusion)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="5">
      <xs:annotation>
        <xs:documentation>derived : Derived Data Record (results of data analysis, directly usable by other communities with no further processing)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="6">
      <xs:annotation>
        <xs:documentation>Ancillary Data Record (extra data specifically supporting a data set, such as coordinates, geometry…)</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
  </xs:restriction>
  <!-- previous definition
        <xs:choice>
            <xs:element name="raw" fixed="0">
                <xs:annotation>
			<xs:documentation>
				raw data
                    </xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="Experiment_Data_Record" fixed="1">
                <xs:annotation>
			<xs:documentation>
				raw data
                    </xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="Reduced_Data_Record" fixed="2">
                <xs:annotation>
			<xs:documentation>
				Reduced Data Record 
                    </xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="Derived_Data_Record" fixed="3">
                <xs:annotation>
			<xs:documentation>
				Derived Data Record 
                    </xs:documentation>
                </xs:annotation>
            </xs:element>
    </xs:choice>
    end of previous definition -->
</xs:simpleType>
XML Schema documentation generated by ® XML Developer.