Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by

Table of Contents

Group by:

No namespace

Elements
Attributes

http://www.ivoa.net/xml/STC/stc-v1.30.xsd

Elements
Complex Types
Attribute Groups

Resource hierarchy:

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
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Imported schema stc-v1.30.xsd
Namespace http://www.ivoa.net/xml/STC/stc-v1.30.xsd
Properties
attribute form default: unqualified
element form default: qualified
Schema location http://www.ivoa.net/xml/STC/stc-v1.30.xsd
[ top ]
Imported schema xlink.xsd
Namespace http://www.w3.org/1999/xlink
Properties
attribute form default: qualified
element form default: qualified
Schema location http://www.ivoa.net/xml/Xlink/xlink.xsd
[ top ]
Imported schema VOResource-v1.0.xsd
Namespace http://www.ivoa.net/xml/VOResource/v1.0
Annotations
Implementation of an XML Schema describing a resource to 
be used in the Virtual Observatory Project.  Based on "Resource 
Metadata for the Virtual Observatory", Version 0.8, 
February 2002 by Bob Hanisch et al.
Properties
attribute form default: unqualified
element form default: unqualified
version: 1.02
Schema location http://www.ivoa.net/xml/VOResource/VOResource-v1.0.xsd
[ top ]
Element EPNcore
Namespace http://voparis-europlanet.obspm.fr/xml/TAPCore/EPNCore.xsd
Diagram
Diagram EPNCore.tmp#EPNCoreType_resource_type EPNCore.tmp#EPNCoreType_dataproduct_type EPNCore.tmp#EPNCoreType_target_name EPNCore.tmp#EPNCoreType_target_class EPNCore.tmp#EPNCoreType_time EPNCore.tmp#EPNCoreType_spectral EPNCore.tmp#EPNCoreType_spatial EPNCore.tmp#EPNCoreType_view_angle EPNCore.tmp#EPNCoreType_instrument_host_name EPNCore.tmp#EPNCoreType_instrument_name EPNCore.tmp#EPNCoreType_measurement_type EPNCore.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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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.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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Element EPNCoreType / target_class
Namespace No namespace
Diagram
Diagram EPNCore.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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Element EPNCoreType / time
Namespace No namespace
Diagram
Diagram EPNCore.tmp#Time_Type_time_min EPNCore.tmp#Time_Type_time_max EPNCore.tmp#Time_Type_time_sampling_step_min EPNCore.tmp#Time_Type_time_sampling_step_max EPNCore.tmp#Time_Type_time_exp_min EPNCore.tmp#Time_Type_time_exp_max EPNCore.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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Element EPNCoreType / spectral
Namespace No namespace
Diagram
Diagram EPNCore.tmp#SpectralType_spectral_range_min EPNCore.tmp#SpectralType_spectral_range_max EPNCore.tmp#SpectralType_spectral_sampling_step_min EPNCore.tmp#SpectralType_spectral_sampling_step_max EPNCore.tmp#SpectralType_spectral_resolution_min EPNCore.tmp#SpectralType_spectral_resolution_max EPNCore.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"/>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Element EPNCoreType / spatial
Namespace No namespace
Diagram
Diagram EPNCore.tmp#SpatialType_spatial_range EPNCore.tmp#SpatialType_Spatial_frame_type EPNCore.tmp#SpatialType_spatial_resolution EPNCore.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"/>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Element SpatialType / spatial_range
Namespace No namespace
Diagram
Diagram EPNCore.tmp#Spatial_RangeType_c1min EPNCore.tmp#Spatial_RangeType_c2min EPNCore.tmp#Spatial_RangeType_c3min EPNCore.tmp#Spatial_RangeType_c1max EPNCore.tmp#Spatial_RangeType_c2max EPNCore.tmp#Spatial_RangeType_c3max EPNCore.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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Element SpatialType / Spatial_frame_type
Namespace No namespace
Diagram
Diagram EPNCore.tmp#SpatialFrameTypeType_celestial EPNCore.tmp#SpatialFrameTypeType_body EPNCore.tmp#SpatialFrameTypeType_cartesian EPNCore.tmp#SpatialFrameTypeType_cylindrical EPNCore.tmp#SpatialFrameTypeType_spherical EPNCore.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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
Element SpatialType / spatial_resolution
Namespace No namespace
Diagram
Diagram EPNCore.tmp#SpatialResolutionType_c1_resol_min EPNCore.tmp#SpatialResolutionType_c2_resol_min EPNCore.tmp#SpatialResolutionType_c3_resol_min EPNCore.tmp#SpatialResolutionType_c1_resol_max EPNCore.tmp#SpatialResolutionType_c2_resol_max EPNCore.tmp#SpatialResolutionType_c3_resol_max EPNCore.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"/>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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>
Schema location file:/home/lesidaner/Mes_documents/avo/Europlanet/site-web/europlanet/xml/TAPCore/EPNCore.xsd
[ top ]
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