Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note: from 5 July 2021, these pages are no longer the primary source of the EPN-TAP doc - see instead the IVOA latex source: https://github.com/ivoa-std/EPNTAP


List of EPN-TAP parameters
(refreshed/completed April 2019, Oct 2020, June 2021, Oct 2021) (SE) 

You can use this file to keep track of your service parameters: EPN-TAP_parameters_List_template.xlsx

EPN-TAP

  • EPN-TAP is a VO access protocol dedicated to Planetary Science data. It is based on the TAP mechanism from IVOA, completed with sets of parameters and associated lists of values. In this regard, it is similar to ObsTAP but with a different scope.
  • EPN-TAP version 2 is a major update of the protocol to accommodate larger services and simplify setup and use of data services. All parameters are described here.

...

  • Lab spectroscopy: parameters to describe mineralogical samples (and possibly other samples)
  • Solar System objects: covers orbital/rotational parameters, physical properties, and taxonomy
  • APIS: contains for consistency with APIS service. Contains parameters for observing programs Contributive (most parameters are actually included in other extensions)
  • Contributive works / observing programs: enlargement of APIS extension to other data
  • Exoplanets / planetary systems properties
  • Map extension (to be enlarged)
  • Events: covers the VOevent standard and other types of events
  • Particle spectroscopy (to be finalized)
  • Results of planetary 3D modelling run (in progress)
  • Bibliographic entries? May be manageable otherwise, through bibcode / doi interpretation

Support file

You can use this file to keep track of your service parameters: EPN-TAP_parameters_List_template.xlsx


YYYdistance;stat.min (bof)
or pos.radius;stat.min (does not exist)
  for spherical & cylindrical

pos.eq.ra;stat.min for celestial 

pos.bodyrc.lon;stat.min for body

pos.cartesian.x;stat.min for Cartesian

pos.healpix for healpix (with 2 parameters?  - weird) - TBC

empty ("") for none (and no unit)

pos.eq.decpos;stat.max, etc

phys.outline;obs.field

 pos.incidenceAng;stat.min
meta.ref.url;meta.preview meta.ref;time.scale
Min

pos.ecliptic.lon;pos.heliocentric;stat.max

Name , v2

Value required (not NULL)?


SQL type

Unit / Format / Range

Description

UCDPlease comment! 

UCD in Obscore 1.1

(309/35/2016 2017 REC version)

Utype

(tentative) 

Comments

EPNCore mandatory parameters
 (Must be present, possibly empty)
 (bold face: a value is required)




Current value
current but dubious or undefined
check this (dubious)

— ? : closest sense

_ : N/A in ObsCore

from epntap v2 mixin (aug 2017)
equivalent/close in ObsCore doc 1.1

 

granule_uid

Text


Internal table row index.
Unique ID in data service. meta.id

  meta.id;meta.dataset

meta.id
 Can be alphanum.

granule_gid

Y

Text


Common to granules of same type

meta.id

meta.id
E.g. same map projection, or geometry data products. Can be alphanum.

obs_id

Y

Text


Associates granules derived from the same data

meta.id;obs

meta.idobscore:DataID.observationID E.g. various representations / processing levels. Can be alphanum., may be the ID of original observation.
Keep it simple in intricate situations.

dataproduct_type

Text


Organization of the data product, from enumerated list

meta.code.class

meta.id

Epn.dataProductType

obscore:ObsDataset.dataProductType


target_name

Text


Standard IAU name of target (from a list related to target must match target_class), case sensitive.

meta.id;src

meta.id;srcEpn.TargetNameCase sensitive
Services with no target_name do exist

target_class

Text


Type of target, from enumerated list

src.class

src.classEpn.TargetClass

time_min

Double

d (date as JD)

Start time (in JD). UTC measured at time_origin location (default is observer's frame)

time.start;obs

time.start;obs.exposure

Char.TimeAxis.Coverage.Bounds.Limits.Interval.StartTime

TBD (from ObsCore)



time_max

Double

d (date as JD)

Stop time (in JD). UTC measured at time_origin location (default is observer's frame)

time.end;obs

time.end;obs.exposure

Char.TimeAxis.Coverage.Bounds.Limits.Interval.StopTime

TBD (from ObsCore)



time_sampling_step_min

DoubleFloat

s

Min time sampling step

time.resolution;stat.min

time.resolution — ?resolution Epn.Time.Time_sampling_step_min

time_sampling_step_max

DoubleFloat

s

Max time sampling step

time.resolution;stat.max


Epn.Time.Time_sampling_step_max

time_exp_min

DoubleFloat

s

Min integration time

time.duration;obs.exposure;stat.min

time.duration;obs.exposureEpn.Time.Time_exp_min

time_exp_max

DoubleFloat

s

Max integration time

time.duration;obs.exposure;stat.max


Epn.Time.Time_exp_max

spectral_range_min

DoubleFloat

Hz

Min spectral range (as frequency)

em.freq;stat.min

em.wl;stat.minmin (always as wl)

Epn.Spectral.Spectral_range_minAlways as freqfrequency

spectral_range_max

DoubleFloat

Hz

Max spectral range (as frequency)

em.freq;stat.max

em.wl;stat.maxEpn.Spectral.Spectral_range_max

spectral_sampling_step_min

DoubleFloat

Hz

Min spectral sampling step

em.freq;spect.stepbinSize;stat.min

meta.numberEpn.Spectral.Spectral_sampling_step_min

spectral_sampling_step_max

DoubleFloat

Hz

Max spectral sampling step

em.freq;spect.stepbinSize;stat.max

meta.numberEpn.Spectral.Spectral_sampling_step_max

spectral_resolution_min

DoubleFloat


Min spectral resolution (resolving power)

spect.resolution;stat.min

spect.resolution
resolution (relates to resolving power)

Epn.Spectral.Spectral_resolution_min

Now (2019) provides resolving power |(lambda / delta(lambda)| = |f /Df|
How do we accommodate FWHM for filters?

spectral_resolution_max

DoubleFloat


Max spectral resolution (resolving power)

spect.resolution;stat.max


Epn.Spectral.Spectral_resolution_max

Now (2019) provides resolving power |(lambda / delta(lambda)| = |f /Df|
How do we accommodate FWHM for filters?

c1min

DoubleFloat

(1)Longitude from 0. to 359.9999

RA from 0. to 23.9999


Min of first coordinatepos;stat.mindepends on the frame

see table below

pos.pos.eq.raeq.raEpn.Spatial.Spatial_range.c1min

Typo in current mixin (.lonG => .lon

UCDs for cyl and sph coord are from PEN-UCDlist-20210430

c1max

Float

(1)

Max of first coordinate, depends on the frame



Epn.Spatial.Spatial_range.c1minTypo in current mixin (.lonG => .lon

c1max

Double

c1max

c2min

Float

(1)


Max Min of first coordinatepos;stat.max, etcsecond coordinate, depends on the frame. 


pos.eq.decEpn.Spatial.Spatial_range.c1maxc2min

c2minc2max

DoubleFloat

(1)

Latitude from -89.9999 to +89.9999

Min Max of second coordinate

pos;stat.min

pos.angDistance;stat.min
or pos.az.zd;stat.min (for zenithal distance) for spherical 

or pos.az.azi;stat.min (for azimuth)
  for cylindrical

pos.eq.dec;stat.min for celestial 

pos.bodyrc.lat;stat.min for body

pos.cartesian.y;stat.min for Cartesian

empty ("") for none (and no unit)

depends on the frame



Epn.Spatial.Spatial_range.c2max

c3min

Float

(1)

Min of third coordinate



Epn.Spatial.Spatial_range.c3min

c3max

Float

(1)

Max of third coordinate



Epn.Spatial.Spatial_range.c2minc3max

c2maxs_region

DoubleText

(1)

Max of second coordinate

pos;stat.max, etc

Epn.Spatial.Spatial_range.c2max

c3min

Double

(1)

Min of third coordinate

pos;stat.min

pos.AngDistance;stat.min
or pos.az.azi;stat.min (for azimuth)
  for spherical

pos.distance;stat.min  for cylindrical

pos.distance;stat.min for celestial 

pos.bodyrc.alt;stat.min for body? (from surface only, implicitly from reference level)
or
pos.distance;pos.bodyrc;stat.min for body (from center)?

pos.cartesian.z;stat.min for Cartesian

empty ("") for none (and no unit3)

ObsCore-like footprint in 2D (if spatial_frame_type = celestial or body)

pos.outline;obs.field

pos.outline;obs.fieldobscore:Char.SpatialAxis.Coverage.Support.Area

(was initially instr.fov, to be corrected)
ObsCore value updated (was phys.angArea;obs) to phys.outline, 
then corrected to pos.outline

Must have xtype= adql:REGION to work with TAP
Frame may be identified in q.rd (UNKNOWNFrame).
Use value given in spatial_frame_type - very unclear…
Do we need another param for GIS interface?

c1_resol_min

Float

(2)

Min resolution in first coordinate

(2)

pos.angResolution;stat.minEpn.Spatial.Spatial_resolution.c1_resol_minpos.resolution restored in 2018
In body fixed frame, use pixelscale_min/max for resolution at the surface 

c1_resol_max

Float

(2)

Max resolution in first coordinate

(2)

pos.angResolution;stat.maxEpn.Spatial.Spatial_resolution.c1_resol_max_

c2_resol_min

Float

(2)

Min resolution in second coordinate

(2)


Epn.Spatial.Spatial_range.c3min

c3max

Double

(1)

Max of third coordinate

resolution.c2_resol_min_

c2_resol_max

Float

(2)

Max resolution in second coordinate

(2)


Epn.Spatial.Spatial_range.c3max

s_region

spoly

PgSphere spoly

ObsCore-like footprint for celestial, spherical, or body-fixed frames.

phys.outline;obs.fieldobscore:Char.SpatialAxis.Coverage.Support.Area

(was initially instr.fov, to be corrected)
ObsCore value updated (was phys.angArea;obs)
Frame may be identified in q.rd (UNKNOWNFrame).
Use value given in spatial_frame_type - very unclear…
Do we need another param for GIS interface?

c1_resol_min

Double

(1)

Min resolution in first coordinate

pos.resolution;stat.min
if linear 

pos.angResolution;stat.min
if angular

pos.angResolution;stat.minEpn.Spatial.Spatial_resolution.c1_resol_minpos.resolution restored in 2018
In body fixed frame, use pixelscale_min/max for resolution at the surface 

c1_resol_max

Double

(1)

Max resolution in first coordinate

pos.resolution;stat.max
if linear 

pos.angResolution;stat.max
if angular

pos.angResolution;stat.maxEpn.Spatial.Spatial_resolution.c1_resol_max_

c2_resol_min

Double

(1)

Min resolution in second coordinate

pos.resolution;stat.min
if linear 

pos.angResolution;stat.min
if angular

Epn.Spatial.Spatial_resolution.c2_resol_min_

c2_resol_max

Double

(1)

Max resolution in second coordinate

pos.resolution;stat.max
if linear 

pos.angResolution;stat.max
if angular

Epn.Spatial.Spatial_resolution.c2_resol_max_

c3_resol_min

Double

(1)

Min resolution in third coordinate

pos.resolution;stat.min
if linear 

pos.angResolution;stat.min
if angular (spherical only)

Epn.Spatial.Spatial_resolution.c3_resol_minpos.resolution restored in 2018

c3_resol_max

Double

(1)

Max resolution in third coordinate

pos.resolution;stat.max
if linear 

 pos.angResolution;stat.min
if angular (spherical only) 

Epn.Spatial.Spatial_resolution.c3_resol_maxpos.resolution restored in 2018

spatial_frame_type

 Y

Text

(1)

Use "none" if undefined

Flavor of coordinate system, defines the nature of coordinates. From enumerated list

meta.code.class;pos.frame

_

A value is required by DaCHS (query will return errors if empty)
Default value = none

incidence_min

Double

deg

Min incidence angle (solar zenithal angle)

_Epn.View_angle.Incidence_angle_minUCD for angles included in 2018 

incidence_max

Double

deg

Max incidence angle (solar zenithal angle)

 pos.incidenceAng;stat.max

_Epn.View_angle.Incidence_angle_maxUCD for angles included in 2018

emergence_min

Double

deg

Min emergence angle

 pos.emergenceAng;stat.min

_Epn.View_angle.Emergence_angle_minUCD for angles included in 2018

emergence_max

Double

deg

Max emergence angle

 pos.emergenceAng;stat.max

_Epn.View_angle.Emergence_angle_maxUCD for angles included in 2018

phase_min

Double

deg

Min phase angle

pos.phaseAng;stat.min

Epn.View_angle.Phase_angle_min

phase_max

Double

deg

Max phase angle

pos.phaseAng;stat.max

Epn.View_angle.Phase_angle_max

instrument_host_name

Text

Standard name of the observatory or spacecraft

meta.id;instr.obsty

meta.id;instr.telProvenance.ObsConfig.Facility.name

instrument_name

Text

Standard name of instrument

meta.id;instr

meta.id;instrProvenance.ObsConfig.Instrument.name

measurement_type

Text

UCD(s) defining the data

meta.ucd

meta.ucdEpn.Measurement_type Add ;meta.modelled if simulation or model
Add ;stat.uncalib if uncalibrated data 

processing_level

Integer

Use dataset-related value. If none defined, use simplified CODMAC calibration level

meta.calibLevel

meta.code;obs.calib

~ obscore:ObsDataset.calibLevelTo be replaced by PDS4 values in v2.1?

creation_date

YTimestamp

(ISO-8601 String)

Date of first entry of this granule

time.creation

time;meta.dataset

modification_date

YTimestamp(ISO-8601 String)

Date of last modification

time.processing

Used to handle mirroring
UCD value being discussed in 2018

release_date

YTimestamp

(ISO-8601 String)

Start of public access period (set to creation_date if no proprietary period)

time.release

time.releaseobscore:Curation.releaseDate

service_title

Y

Text

Title of resource = schema name

meta.title

May be used to handle multiservice results

Common optional parameters

access_url

Text

URL of the data file, case sensitive (additional files may be linked through datalink_url). Can point to a script. If present, next 2 parameters must also be present.

meta.ref.url;meta.file

meta.ref.urlObs.Access.Reference

Use this to link data!
Could accommodate a datalink with access_format = 'application/x-votable+xml;content=datalink'
(from ObsCore)
- but this is a funny idea…

access_format

Text

(mime type in lowercase)

File format type  

meta.code.mime

meta.code.mimeObs.Access.Format

access_estsize

Integer

kbyte

Estimate file size in kbyte (with this spelling)

phys.size;meta.file

phys.size;meta.fileObs.Access.Sizeaccess_md5TextMD5 Hash for the file when available (real file, not script) meta.checksum;meta.file

thumbnail_url

Text

URL of a thumbnail image with predefined size (png ~200 pix, for use in a client only)

file_name

Text

Name of the data file only, case sensitive

meta.id;meta.file

meta.title;obs — ?ObsCore obs_title is for a short free text string describing the granule. Do we want this?datalink_urlText(url)Provides links to files or services on the servermeta.ref.url;meta.datalinkAssociated mime-type is 'application/x-votable+xml;content=datalink'
(from ObsCore)

species

Text

Identifies a chemical species, case sensitive

meta.id;phys.atmol

This is the only case sensitive parameter (with target_name)wavebandText

Electro-magnetic band, from enumerated list

instr.bandpassalt_target_nameTextcan be a hash listProvides alternative target name if more commonmeta.id;src

target_region

Text

Type of region or feature of interest

obs.field

feature_name

Text

Secondary name
(e.g. standard name of a region of interest)

obs.field 

Anchor
featurenamefeaturename

publisher

Text

Resource publisher

meta.curation

meta.ref.url;meta.curation~ obscore:Curation.publisherID

bib_reference

Text

Bibcode preferred if available, doi, or other biblio id, URL...

meta.bib

meta.bib.bibcode (if bibcode)

meta.bib.bibcode

(always as bibcode)

obscore:Curation.referenceinternal_referenceTextList of granule_uid(s) in the current servicemeta.id.crossUse to link one granule to a set of other granules. To be used only if required - e.g. to solve situations that would otherwise require several tablesexternal_linkText(url)Link to a web page providing more details on the granule.meta.ref.url

Link to an individual page in a web site associated to the database, e.g., a planet page in Exoplanets service. This is a way to provide extra granule information which cannot be accommodated in the table.

spatial_coordinate_description

Text

ID of specific coordinate system and version / properties

meta.code.class;pos.frame

~COOSYS, but includes planetary ones
Still TBD. Discussion in progress here: EPN-TAP v2: Current discussion topic

spatial_origin

Text

Defines the frame origin

meta.ref;pos.frame

time_origin

Text

Defines where the time is measured (e. g., ground vs spacecraft)

target_time is of course always on target.

time_scale

Text

Always UTC in data services - from enumerated list

time.scale

subsolar_longitudeDoubledegSub-solar point longitudepos.bodyrc.lonProvided in the most natural body-related coordinate frame, E-handed - seems to require 'body'
No min/max here 
subsolar_latitudeDoubledegSub-solar point latitudepos.bodyrc.lat_subobserver_longitudeDoubledegSub-observer point longitude (sub-Earth for ground based observations)pos.bodyrc.lon_subobserver_latitudeDoubledegSub-observer point latitude (sub-Earth for ground based observations) pos.bodyrc.lat_

ra

Double

deg only (like ObsCore)

Right ascension (not hour angle!)

pos.eq.ra;meta.main

dec

Double

deg

Declination

pos.eq.dec;meta.main

radial_distance_minDoublekmMin distance from center (in body-fixed frame)pos.distance;pos.bodyrc;stat.minradial_distance_maxDoublekmMax distance from center (in body-fixed frame)pos.distance;pos.bodyrc;stat.maxaltitude_fromshape_minDoublekmMin altitude above shape model / DTM (in body-fixed frame)pos.bodyrc.alt;stat.minaltitude_fromshape_maxDoublekmMax altitude above shape model / DTM (in body-fixed frame)pos.bodyrc.alt;stat.max

solar_longitude_min

Double

deg

resolution.c2_resol_max_

c3_resol_min

Float

(2)

Min resolution in third coordinate

(2)


Epn.Spatial.Spatial_resolution.c3_resol_minpos.resolution restored in 2018

c3_resol_max

Float

(2)

Max resolution in third coordinate

(2)


Epn.Spatial.Spatial_resolution.c3_resol_maxpos.resolution restored in 2018

spatial_frame_type

Text

(1)


Flavor of coordinate system, defines the nature of coordinates. From enumerated list. Use "none" if undefined

meta.code.class;pos.frame

_

A value is required by DaCHS (query will return errors if empty)
Default value = none

incidence_min

Float

deg

Min incidence angle (solar zenithal angle)

 pos.incidenceAng;stat.min

_Epn.View_angle.Incidence_angle_minUCD for angles included in 2018 

incidence_max

Float

deg

Max incidence angle (solar zenithal angle)

 pos.incidenceAng;stat.max

_Epn.View_angle.Incidence_angle_maxUCD for angles included in 2018

emergence_min

Float

deg

Min emergence angle

 pos.emergenceAng;stat.min

_Epn.View_angle.Emergence_angle_minUCD for angles included in 2018

emergence_max

Float

deg

Max emergence angle

 pos.emergenceAng;stat.max

_Epn.View_angle.Emergence_angle_maxUCD for angles included in 2018

phase_min

Float

deg

Min phase angle

pos.phaseAng;stat.min


Epn.View_angle.Phase_angle_min

phase_max

Float

deg

Max phase angle

pos.phaseAng;stat.max


Epn.View_angle.Phase_angle_max

instrument_host_name

Text


Standard name of the observatory or spacecraft

meta.id;instr.obsty

meta.id;instr.telProvenance.ObsConfig.Facility.name

instrument_name

Text


Standard name of instrument

meta.id;instr

meta.id;instrProvenance.ObsConfig.Instrument.name

measurement_type

Text


UCD(s) defining the data

meta.ucd

meta.ucdEpn.Measurement_typeAdd ;meta.modelled if simulation or model
Add ;stat.uncalib if uncalibrated data - in which case processing_level must be 0 or 1

processing_level

Integer


Dataset-related encoding, or simplified CODMAC calibration level

meta.calibLevel

meta.code;obs.calib

~ obscore:ObsDataset.calibLevel To be replaced by PDS4 values in v2.1?

creation_date

Timestamp

(4)

Date of first entry of this granule

time.creation

time;meta.dataset

modification_date

Timestamp(4)

Date of last modification

time.processing



Used to handle mirroring
UCD value being discussed in 2018

release_date

Timestamp

(4)

Start of public access period (set to creation_date if no proprietary period)

time.release

time.releaseobscore:Curation.releaseDate

The value is in ISO 8601 format reusing this pattern: (“YYYY-MM-DDThh:mm:ss”) If release_date is in the future, the data is proprietary.

service_title

Text


Title of resource = schema name

meta.title



May be used to handle multiservice results

Common optional parameters








access_url

Text


URL of the data file, case sensitive (additional files may be linked through datalink_url). Can point to a script. If present, next 2 parameters must also be present

meta.ref.url;meta.file

meta.ref.urlObs.Access.Reference

Use this to link data!
Could accommodate a datalink with access_format = 'application/x-votable+xml;content=datalink'
(from ObsCore)
- but this is a funny idea…

access_format

Text


RFC 2045 media type (mime), required to be all-lower case 

meta.code.mime

meta.code.mimeObs.Access.Format

access_estsize

Integer

kbyte

Estimate file size in kbyte (with this spelling)

phys.size;meta.file

phys.size;meta.fileObs.Access.Size
access_md5Text
MD5 Hash for the file when available (real file, not script) meta.checksum;meta.file


thumbnail_url

Text


URL of a thumbnail image with predefined size (png ~200 pix, for use in a client only)

meta.ref.url;meta.preview




file_name

Text


Name of the data file only, case sensitive

meta.id;meta.file

meta.title;obs — ?
ObsCore obs_title is for a short free text string describing the granule. Do we want this?
datalink_urlText
Provides links to files or services on the servermeta.ref.url

Associated mime-type is 'application/x-votable+xml;content=datalink'
(from ObsCore)

species

Text


Identifies a chemical species, case sensitive

meta.id;phys.atmol



This is the only case sensitive parameter (with target_name)
messengerText

Vector of measured signal, including electromagnetic 
band, from enumerated list

instr.bandpass


alt_target_nameText
Provides alternative target name(s). Can be a hash listmeta.id;src


target_region

Text


Type of region or feature of interest

meta.id;src;obs.field




feature_name

Text


Secondary name (e.g. standard name of a region of interest)

meta.id;src;obs.field 



Anchor
featurename
featurename

publisher

Text


Resource publisher

meta.curation

meta.ref.uri;meta.curation~ obscore:Curation.publisherID

processing_level_desc

Text
Describes specificities of the processing levelmeta.note


bib_reference

Text


Bibcode or doi preferred; can be a URL or anything else. Refers to the granule

meta.bib

meta.bib

obscore:Curation.referenceBibcode & doi can be completed in TOPCAT
internal_referenceText
Related granule_uid(s) in the current servicemeta.id.cross

Use to link one granule to a set of other granules. To be used only if required - e.g. to solve situations that would otherwise require several tables
external_linkText
Web page providing more details on the granulemeta.ref.url

Link to an individual page in a web site associated to the database, e.g., a planet page in Exoplanets service. This is a way to provide extra granule information which cannot be accommodated in the table.

shapeText

introduces an ascii (ST)MOC, v2 (2D footprint on celestial, spherical, or body-related frames, possibly including time)

pos.outline;obs.field

Must have xtype="MOC" (follow DALI recommendation)

outline doesn't fit definition (refers to a contour)

spatial_coordinate_description

Text


ID of specific coordinate system and version / properties

meta.code.class;pos.frame



~COOSYS, but includes planetary ones
Still TBD, needs to be OGC compliant. Discussion in progress here: EPN-TAP v2: Current discussion topic

spatial_origin

Text


Defines the frame origin

meta.ref;pos.frame




time_refposition

Text


Defines where the time is measured (e. g., ground vs spacecraft). Default is observer's frame

meta.ref;time.scale



target_time is of course always on target.

time_scale

Text


Defaults to UTC in data services - from enumerated list

time.scale




subsolar_longitude_minFloatdegMinimum sub-solar point longitudepos.bodyrc.lon;stat.min

Provided in the most natural body-related coordinate frame, E-handed - seems to require 'body'
subsolar_longitude_maxFloatdegMaximum sub-solar point longitudepos.bodyrc.lon;stat.max

Provided in the most natural body-related coordinate frame, E-handed - seems to require 'body'
subsolar_latitude_minFloatdegMinimum sub-solar point latitudepos.bodyrc.lat;stat.min

_
subsolar_latitude_maxFloatdegMaximum sub-solar point latitudepos.bodyrc.lat;stat.max

_
subobserver_longitude_minFloatdegMinimum sub-observer point longitude (sub-Earth for ground based observations)pos.bodyrc.lon;stat.min

_
subobserver_longitude_maxFloatdegMaximum sub-observer point longitude (sub-Earth for ground based observations)pos.bodyrc.lon;stat.max

_
subobserver_latitude_minFloatdegMinimum sub-observer point latitude (sub-Earth for ground based observations) pos.bodyrc.lat;stat.min

_
subobserver_latitude_maxFloatdegMaximum sub-observer point latitude (sub-Earth for ground based observations) pos.bodyrc.lat;stat.max

_

ra

Float

deg

Right ascension

pos.eq.ra;meta.main



deg only (like ObsCore)

dec

Float

deg

Declination

pos.eq.dec;meta.main




radial_distance_minFloatkmMin distance from observed area to body center pos.distance;pos.bodyrc;stat.min


radial_distance_maxFloatkmMax distance from observed area to body center pos.distance;pos.bodyrc;stat.max


altitude_fromshape_minFloatkmMin altitude of observed area above shape model / DTMpos.bodyrc.alt;stat.min


altitude_fromshape_maxFloatkmMax altitude of observed area above shape model / DTMpos.bodyrc.alt;stat.max


solar_longitude_min

Float

deg

Min Solar longitude Ls (location on orbit / season)

pos.ecliptic.lon;pos.heliocentric;stat.min 




solar_longitude_max

Float

deg

Max Solar longitude Ls (location on orbit / season)

pos.ecliptic.lon;pos.heliocentric;stat.min  max




solarlocal_longitudetime_maxmin

DoubleFloat

deg

Max Solar longitude Ls (location on orbit / season)

local_time_min

Double

h

Min local time h

Min local time at observed region

time.phase;time.period.rotation;time.phase;stat.min




local_time_max

DoubleFloat

h

Max local time at observed region

time.phase;time.period.rotation;time.phase;stat.max 




target_distance_min

DoubleFloat

km

Min observer-target distance

pos.distance;stat.min




target_distance_max

DoubleFloat

kmMax observer-target distancepos.distance;stat.max


target_time_minDouble

Timestamp

d(4)

Min observing time in target frame

time.start;src



(simplest way to look for coordinated observations)

target_time_maxDouble

Timestamp

d(4)

Max observing time in target frame

time.end;src




earth_distance_minDoubleFloatauAUMin Earth-target distancepos.distance;stat.min


earth_distance_maxDoubleFloatauAUMax Earth-target distance

pos.distance;stat.max




sun_distance_minDoubleFloatauAUMin Sun-target distancepos.distance;stat.min


sun_distance_maxDoubleFloatauAUMax Sun-target distancepos.distance;stat.max


Parameters from extensions








obs_modeText
Observing modemeta.code;instr.setup

From APIS + observation extensions (with adapted UCDs)
detector_nameText
Detector namemeta.id;instr.detFrom APIS + observation extensions (UCDs adapted later)


opt_elemText
Optical element namemeta.id;instr.param


filterText Identifies filter in use, typically for images.meta.id;instr.filter

Informative only, free format (no list, but see http://svo2.cab.inta-csic.es/svo/theory/fps3/). Search can only rely on spectral range, as ObsCore does.
instrument_typeText
type of instrumentmeta.id;instr

To be used with cautionInformative only (not a reliable search parameter): free format, no reference list intended.
acquisition_idText
ID of the data file/acquisition in the original archivemeta.id


proposal_idIntegerText
Proposal identifiermeta.id;obs.proposal


proposal_pitextText
Proposal principal investigator

meta.id.PI;obs.proposal




proposal_titleText
Proposal titlemeta.title;obs.proposal


campaignText
Name of the observational campaignmeta.id;metaobs.codeproposal


target_descriptionText
Original target keywordsmeta.note;src


proposal_target_nameText
target name as in proposal titlemeta.note;obs.proposal


target_apparent_radiusDoubleFloatarcsecApparent radius of the target

phys.angSize;src




north_pole_positionDoubleFloatdegNorth pole position angle with respect to celestial north pole

pos.posAng



Group of 5 parameters very specific to APIS.
Name is ~ OK, but actually provides the position angle of the planet axis. Use "orientation" for the image.Group of 5 parameters very specific to APIS.
target_primary_hemisphereText
Primary observed hemispheremeta.id;obs.field


target_secondary_hemisphereText
Secondary observed hemispheremeta.id;obs.field


platescDoubleFloatarcsec/pixel?pixspatial resolution per pixel or angular size or platescale (on sky only)posinstr.angResolutionscale


orientationDoubleFloatdegPosition angle of image y axis (on sky only)pos.posAng

Provides the direction of the polar axis in the image, counted clockwise from north.
observer_nameText
Observer name

obs.observer;meta.main




observer_instituteText
Observer institutemeta.note;meta.main


observer_idInteger
Image observer's PVOL numeric identifier

meta.id.PI




Group of 5 from PVOL, OK for general use but UCDs are wrong have to be changed in PVOL.
This was meta.pubid in PVOL

observer_codeText
Image observer's PVOL service usernamemeta.id.PI

meta.pubcode in PVOL
observer_countryText
Image observer's country of residencemeta.note;obs.observer

meta.pubcountry in PVOL
observer_lonFloatDoubledegObserver's approximate longitudeobs.observer;pos.earth.lon


meta.publon in PVOL
observer_latFloatDoubledegObserver's approximate latitudeobs.observer;pos.earth.lat

meta.publat in PVOL
massDoubleFloatkg Mass Mass of objectphys.mass

Solar System Objects extension (generic values in catalogues, not observations)
sideralsidereal_rotation_periodDoubleFloath Object Object rotation ratetime.period.rotation


mean_radiusDoubleFloatkm
phys.size.radius


equatorial_radiusDoubleFloatkm
phys.size.radius


polar_radiusDoubleFloatkm
phys.size.radius


diameterdoubleFloatkmTarget diameter, or equivalent diameter for binary objectsphys.size.diameter

Used in tnosarecool, not very consistent (use radius?)

semi_major_axis

DoubleFloatauAU

phys.size.smajAxis




inclinationFloatDoubledegOrbit inclination

src.orbital.inclination




eccentricityDoubleFloat
Orbit eccentricity

src.orbital.eccentricity




long_ascDoubleFloatdegLongitude of ascending node, J2000.0src.orbital.node


arg_perihelDoubleFloatdegArgument of Perihelionperihelion, J2000.0src.orbital.periastron


mean_anomalyDoubleFloatdegMean anomaly at the epochsrc.orbital.meanAnomaly


epochDoubled

Epoch of interest in JD

time.epoch


dynamical_class

Text
Class of small body, from enumerated listmeta.code.class;src


dynamical_typeText
Subdivision of the class, from enumerated listmeta.code.class;src


taxonomy_codeText
Code for target taxonomysrc.class.color

Values Possible values depend on target type and possibly on service
magnitudeDoubleFloatmagAbsolute magnitude. For small bodies, from HG magnitude systemphys.magAbs

Actually depends on service (eg, spectro_planets vs DynAstVO vs tnosarecool).
UCD may include mention of the photometric band.
fluxDoubleFloatmJyTarget fluxphot.flux.density


albedoDoubleFloat
Target albedophys.albedo


map_projection

Text
ID from enumerated list, or string with parameters (referring to a standard)pos.projection

Map extension

map_height

DoubleFloatpixelpixMap size in px

phys.size




map_widthDoubleFloatpixelpixMap size in px

phys.size




map_scaleTextFormat TBD
Preferably a ratio (e. g., "1:50000")

pos.wcs.scale?




pixelscale_minDoubleFloatkm/pixelpixMin pixel size on a surface

instr.scale;stat.min




pixelscale_maxDoubleFloatkm/pixelpixMax pixel size on a surface

instr.scale;stat.max




particle_spectral_type

Text


From enumerated list

meta.id;phys.particle

Particle spectroscopy extension, UCD TBD


particle_spectral_range_min

DoubleFloat



phys.energy;phys.particle;stat.min

phys.mass;phys.particle;stat.min




particle_spectral_range_max

DoubleFloat



phys.energy;phys.particle;stat.max

phys.mass;phys.particle;stat.max




particle_spectral_sampling_step_min

DoubleFloat



spect.resolution;phys.particle;stat.min




particle_spectral_sampling_step_max

DoubleFloat



spect.resolution;phys.particle;stat.max




particle_spectral_resolution_min

DoubleFloat



spect.resolution;phys.particle;stat.min




particle_spectral_resolution_max

DoubleFloat



spect.resolution;phys.particle;stat.max




original_publisher


Text
Refers to the source of the data, especially in e. g.,  in compilations of experimental datameta.note;meta.main

Experiment Experimental spectroscopy + contributive work extensions

producer_name

Text
Data producer name, especially in compilations of experimental datameta.note;meta.main


producer_institute

Text
Data producer institute, especially e. g., in compilations of experimental datameta.note;meta.main


sample_idText
Provides a local ID in an existing catalogue meta.id;src

In addition to target_name

sample_classification

Text
Information related to class, sub-class, species… as hash listInformation related to class, sub-class, species… (using standard names)meta.note;phys.compositionsample_descTextcan be a hash listDescribes the sample, its origin, and possible preparationmeta.note

data_calibration_desc

Textcan be a hash listProvides information on post-processing meta.note(preferably to a "comment" parameter)setup_descTextcan be a hash listDescribes the experimental setup if needed - may include Aperture (size of sample measured), etcmeta.note

geometry_type

TextType of observation (such as bidirectional, biconical, directional-hemispherical, etc)meta.note

grain_size_min

DoubleµmMin particle size in µm

phys.size;stat.min

grain_size_maxDoubleMax particle size in µm

phys.size;stat.max

azimuth_minDoubledegMin azimuth angle for illuminationpos.azimuth;stat.min

Check meaning/requirements for <0 values?
UCD added in 2018 (instead of pos.azimuthAng requested - OK)

azimuth_maxDoubledegMax azimuth angle for illuminationpos.azimuth;stat.maxUCD added in 2018

pressure

DoublebarAmbient pressure

phys.pressure

VOunits says: Pascal.
But this is in files 

measurement_atmosphere

textDescribes experimental conditions. "vacuum" for measurements under vacuum.

meta.note;phys.pressure

temperatureDoubleKAmbient temperature

phys.temperature

event_type

Text

Type of event from enumerated list (e. g., meteor_shower, fireball, lunar_flash, comet_tail_crossing…)

TBD

Events extension
If dataproduct_type = ev
UCDs should be provided with the standard

event_statusText

From enumerated list

TBDevent_citeText

From enumerated list

TBD

(1): depending on context (as given by spatial_frame_type). Please comment here: EPN-TAP v2: Current discussion topic

...

meta.note;phys.composition

This uses standard names for classes… 
sample_descText
Describes the sample, its origin, and possible preparation. Can be a hash listmeta.note


species_inchikeyText

Fixed length string identifying the species. Can be a hash list

meta.id;phys.atmol



Follows IUPAC standard (Heller et al 2015)

data_calibration_desc

Text
Provides information on post-processing. Can be a hash listmeta.note

(preferably to a "comment" parameter)
setup_descText
Describes the experimental setup. Can be a hash listmeta.note

May include Aperture (size of sample measured), etc

geometry_type

Text
Type of observation, from enumerated list. Can be a hash listmeta.note;instr.setup


spectrum_type

Text
Type of spectral observation, from enumerated list TBD. Can be a hash listmeta.note;instr.setup

Alternative to UCD, very detailed

grain_size_min

FloatumMin sample particle size 

phys.size;stat.min




grain_size_maxFloatumMax sample particle size 

phys.size;stat.max




azimuth_minFloatdegMin azimuth angle for illuminationpos.azimuth;stat.min

Check meaning/requirements for <0 values?
UCD added in 2018 (instead of pos.azimuthAng requested - OK)

azimuth_maxFloatdegMax azimuth angle for illuminationpos.azimuth;stat.max

UCD added in 2018

pressure

FloatbarAmbient pressure

phys.pressure



VOunits says: Pascal.

measurement_atmosphere

Text
Describes experimental conditions. "vacuum" for measurements under vacuum

meta.note;phys.pressure




temperatureFloatKAmbient temperature

phys.temperature




event_type

Text

Type of event from enumerated list

meta.code.class



Events extension
If dataproduct_type = ev
UCDs should be provided with the standard

event_statusText

From enumerated list

meta.code.status




event_citeText

From enumerated list

meta.code.status





(1): depending on context (as given by spatial_frame_type), see table below

Longitude and RA range from 0. to 360; Latitude and Dec range from -90. to +90.

For spatial_frame_type = "none": no value is provided, UCD are empty strings (""), and no unit is provided

(2) Spatial resolution parameters have the same unit as spatial coordinate parameters. The associated UCD combine either pos.resolution (if linear) or pos.angResolution (if angular) with secondary stat.min or stat.max

c1: only body and celestial are angular; c2: only cartesian is linear; c3: only spherical is angular

(3): Any contour type that works with ADQL's geometry operators (CONTAINS, INTERSECTS...) is legal here

(4): Timestamps are provided as ISO-8601 String as specified by DALI. On VOtable output, xtype="timestamp" attribute is required.


Frame coordinates UCD/unitscelestialbodycartesiansphericalcylindrical

c1min

pos.eq.ra;stat.min 

pos.bodyrc.lon;stat.min

pos.cartesian.x;stat.min

(in km)

pos.spherical.r;stat.min 

(in m)

pos.cylindrical.r;stat.min 

(in km)

c1maxpos.eq.ra;stat.maxpos.bodyrc.lon;stat.max

pos.cartesian.x;stat.max

(in km)

pos.spherical.r;stat.max 

(in m)

pos.cylindrical.r;stat.max 

(in km)

c2minpos.eq.dec;stat.minpos.bodyrc.lat;stat.min

pos.cartesian.y;stat.min

(in km)

pos.spherical.colat;stat.min

pos.cylindrical.azi;stat.min

c2maxpos.eq.dec;stat.maxpos.bodyrc.lat;stat.max

pos.cartesian.y;stat.max

(in km)

pos.spherical.colat;stat.max

pos.cylindrical.azi;stat.max

c3min

pos.distance;stat.min

(in AU)

pos.bodyrc.alt;stat.min (from surface only, implicitly from reference level)
or
pos.distance;pos.bodyrc;stat.min (from center)?

(in km)

pos.cartesian.z;stat.min

(in km)

pos.spherical.azi;stat.min

pos.cylindrical.z;stat.min

(height, in km)

c3max

pos.distance;stat.max

(in AU)

pos.bodyrc.alt;stat.max (from surface only, implicitly from reference level)
or
pos.distance;pos.bodyrc;stat.max (from center)?

(in km)

pos.cartesian.z;stat.max

(in km)

pos.spherical.azi;stat.max

pos.cylindrical.z;stat.max

(height, in km)

Example table for IDs:

File name-type

granule_uid

granule_gid

obs_id

A-Raw

1

native

A

A-Calib

2

calibrated

A

A-geom

3

geometry

A

A-proj

4

projected

A

B-Raw

5

native

B

B-Calib

6

calibrated

B

B-geom

7

geometry

B

B-proj

8

projected

B 

...

• Granule_gid: any general indication to providers? I.e.: preview, native, calibrated, geometry… 
A client should be able to display the values present in a service, TBC service (feasible in TOPCAT)

• Reshuffle previous "service parameters":

  • Mandatory :
    publisher - make it mandatory???
    add publisher_did as in Obscore? (for DaCHS/registry; provides unique ID of service for this publisher/server)Optional - TBC, with UCD = meta.ref.uri;meta.curation 
  • Optional 
    spatial_coordinate_description  (default = none)
    spatial_origin  (default = body center or SS barycenter? Or observer location)
    time_origin  (default = observer)
    time_scale (default = UTC – no other values allowed in data services? [only in computational services, e.g. ephemeris])
    Same values to be used in registry declaration 

...

Accref is introduced by the EPN-TAP localfile mixin, but not used - in principle not included in TAP response, be may be present anyway. It may be better to hide it entirely also in the portal (TBC).


Parameters introducing error bars/uncertainties

...

The associated UCDs start with stat.error; or possibly statstat.error;stat.min; & stat.error;stat.min; (those 2 are undefined, though)max;


Support for PDS3 detached labels (proposal)

Solution with datalink seems OK: data files under access_url and detached labels provided under datalink_url in a link table - although no attempt made to read them from the portal yet (use VIR unpublished service to test this).


Utypes (TBC)

Need to clean up current doc (2.0). Utypes are = DM fields. They are supposedly used to identify the meaning of parameters and help e.g. tools to grab required quantities - This will not work in some areas though, e. g. with spectral tools as they currently use UCD instead of Utype for this purpose (not many tools appear to actually rely on Utype in fact). See discussion here for usage (a bit old?): http://www.ivoa.net/documents/Notes/UTypesUsage/20130213/NOTE-utypes-usage-1.0-20130213.html

...