Versions Compared

Key

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

...

3) The notion of table/service parameters is deprecated

This was not supported Such parameters were not directly accessible by TAP. ThereforeIn v2, even constant parameters must be replicated in every line of the epn_core view.

The corresponding Such parameters may be duplicated in the registry declaration though, so as to provide a fast description of services.

...

We have to study a possible extension of its use from regions of the sky to body-related coordinates (either on ellipsoids or 3D shape models) .

...

creation_date and modification_date are now mandatory parameters for every granule. The latter is intended to optimize mirroring of services, by identifying the part granules to be updated/copied.

These parameters must be provided as ISO 8601 strings with format "2013-11-17T10:41:00.00+01:00" (with no space) where the indication of time zone is mandatory. The associated data type must be "date". ADQL supports this format and filtering using time zone is possible.

...

All floating point parameters are now in double precision ( to prevents stupid prevent errors).

 

8) Thematic extensions

Some science fields will require optional parameters, which need to be used consistently between services addressing the same field. Such extensions have to be designed by sub-groups involved in the corresponding data services, either as providers or users. This includes:

  • Lab spectroscopy: parameters to describe mineralogical samples (and possibly other samples)
  • Orbital/rotational parameters and physical properties of Solar System bodies (TBC, but requested by some)
  • Planetary Results of planetary 3D modelling run results
  • Exoplanets / planetary systems properties
  • Bibliographic entries? May be manageable otherwise, through bibcode / doi interpretation

...

Name, v2

Must be filled?

Name, v1

Type

Unit / Format

Description

UCD

EPNCore mandatory parameters

(must be present, possibly empty)

 

 

 

 

 

 

granule_uid

Y

index

Text

 

Internal table row index
Unique ID in data service, also in v2. Can be alphanum.

meta.id

granule_gid

Y

_

Text

 

Common to granules of same type (e.g. same map projection, or geometry data products). Can be alphanum.

meta.id

obs_id

Y

_

Text

 

Associates granules derived from the same data (e.g. various representations / processing levels). Can be alphanum., may be the ID of original observation.

meta.id

 

resource_type

Text

 

Can be dataset or granule

meta.code.class

_ (TBC)

 

dataset_id

Text

 

Dataset identification & granule reference

meta.id

dataproduct_type

Y

dataproduct_type

Text

 

Organization of the data product, from enumerated list

meta.code.class

target_name

Y

target_name

Text

 

Standard IAU name of target (from a list related to target class), case sensitive

meta.id;src

target_class

Y

target_class

Text

 

Type of target, from enumerated list

meta.code.class;src

time_min

 

time_min

Double

d

Acquisition start time (in JD). UTC at time_origin (default is observer's frame)

time.start

time_max

 

time_max

Double

d

Acquisition stop time (in JD). UTC at time_origin (default is observer's frame)

time.end

time_sampling_step_min

 

time_sampling_step_min

Double

s

Min time sampling step

time.interval;stat.min

time_sampling_step_max

 

time_sampling_step_max

Double

s

Max time sampling step

time.interval;stat.max

time_exp_min

 

time_exp_min

Double

s

Min integration time

time.duration;stat.min

time_exp_max

 

time_exp_max

Double

s

Max integration time

time.duration;stat.max

spectral_range_min

 

spectral_range_min

Double

Hz

Min spectral range (frequency)

em.freq;stat.min

spectral_range_max

 

spectral_range_max

Double

Hz

Max spectral range (frequency)

em.freq;stat.max

spectral_sampling_step_min

 

spectral_sampling_step_min

Double

Hz

min spectral sampling step

em.freq.step;stat.min
(not in list)

spectral_sampling_step_max

 

spectral_sampling_step_max

Double

Hz

Max spectral sampling step

em.freq.step;stat.max
(not in list)

spectral_resolution_min

 

spectral_resolution_min

Double

Hz

Min spectral resolution

spect.resolution;stat.min

spectral_resolution_max

 

spectral_resolution_max

Double

Hz

Max spectral resolution

spect.resolution;stat.max

c1min

 

c1min

Double

(1)

Min of first coordinate

pos;stat.min

c1max

 

c1max

Double

(1)

Max of first coordinate

pos;stat.max

c2min

 

c2min

Double

(1)

Min of second coordinate

pos;stat.min

c2max

 

c2max

Double

(1)

Max of second coordinate

pos;stat.max

c3min

 

c3min

Double

(1)

Min of third coordinate

pos;stat.min

c3max

 

c3max

Double

(1)

Max of third coordinate

pos;stat.max

s_region

 

 

Text

(STC-S String)

ObsCore-like footprint, assume spatial_coordinate_description – this one TBC (needs another param for GIS interface?)

instr.fov ?? - doubtful…
phys.angArea;obs (from obsCore)

c1_resol_min

 

c1_resol_min

Double

(1)

Min resolution in first coordinate

pos.resolution;stat.min
(deprecated)

c1_resol_max

 

c1_resol_max

Double

(1)

Max resolution in first coordinate

pos.resolution;stat.max
(deprecated)

c2_resol_min

 

c2_resol_min

Double

(1)

Min resolution in second coordinate

pos.resolution;stat.min
(deprecated)

c2_resol_max

 

c2_resol_max

Double

(1)

Max resolution in second coordinate

pos.resolution;stat.max
(deprecated)

c3_resol_min

 

c3_resol_min

Double

(1)

Min resolution in third coordinate

pos.resolution;stat.min
(deprecated)

c3_resol_max

 

c3_resol_max

Double

(1)

Max resolution in third coordinate

pos.resolution;stat.max
(deprecated)

spatial_frame_type

 

spatial_frame_type

Text

 

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

meta.code.class;pos.frame

incidence_min

 

incidence_min

Double

deg

Min incidence angle (solar zenithal angle)

pos.posAng;stat.min 

incidence_max

 

incidence_max

Double

deg

Max incidence angle (solar zenithal angle)

pos.posAng;stat.max 

emergence_min

 

emergence_min

Double

deg

Min emergence angle

pos.posAng;stat.min 

emergence_max

 

emergence_max

Double

deg

Max emergence angle

pos.posAng;stat.max

phase_min

 

phase_min

Double

deg

Min phase angle

pos.phaseAng;stat.min

phase_max

 

phase_max

Double

deg

Max phase angle

pos.phaseAng;stat.max

instrument_host_name

 

instrument_host_name

Text

 

Standard name of the observatory or spacecraft

meta.id;instr.obsty

instrument_name

 

instrument_name

Text

 

Standard name of instrument

meta.id;instr

measurement_type

 

measurement_type

Text

 

UCD(s) defining the data

meta.ucd

processing_level

 

processing_level

Integer

 

CODMAC calibration level in v1
To be replaced by PDS4 values in v2?

meta.code;obs.calib

creation_date

Y

 

Date

(ISO-8601 String)

Date of first entry of this granule

time.creation

modification_date

Y

 

Date

(ISO-8601 String)

Date of last modification (used to handle mirroring)

time.update

release_date

Y

 

Date

(ISO-8601 String)

Start of public access period

time.release

service_title

Y

service_title
(still "title" in many v1 services)

Text

 

Title of resource (will be used to handle multiservice results)

meta.title

Optional parameters

 

 

 

 

 

 

access_url

 

access_url

Text

 

URL of the data file, case sensitive. If present, next 2 parameters must be present.

meta.ref.url;meta.file

access_format

 

access_format

Text

 (mime type in lowercaseslowercase)

File format type  

meta.code.mime

access_estsize

 

access_estsize

Integer

kB

Estimate file size in kB

phys.size;meta.file
(TBC)

data_access_url _Text If access_format indicates a detached label, this parameter is mandatory and points to the corresponding data file - both will be handled by the client before samping it to tools or downloading meta.ref.url;meta.file
access_md5 Text MD5 Hash for the file when available (real file) 

_
replaced by another granule group

 

preview_url

Integer

 

URL of a preview image (std format with adequate resolution for user's purpose)

meta.ref.url;meta.file

_
replaced by another granule group

 

native_access_url

Text

 

URL of the data file in native form, case sensitive

meta.ref.url;meta.file

_
replaced by another granule group

 

native_access_format

Text

 

File format type in native form

meta.id;class
or meta.code.mime (if we use MIME type)

thumbnail_url

 

_

Text

 

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

meta.ref.url;meta.file

file_name

 

file_name

Text

 

Name of the data file only, case sensitive

meta.id;meta.file

species

 

species

Text

 

Identifies a chemical species, case sensitive

meta.id;phys.atmol

alt_target_name _Text Provides alternative target name if more common (e.g. comets)meta.id;src

target_region

 

target_region

Text

 

Type of region of interest

meta.id;class

feature_name

 

element_name

Text

 

Secondary name
(can be standard name of region of interest)

meta.id;pos

bib_reference

 

reference

Text

 

Bibcode, doi, or other biblio id, URL…

meta.bib

ra

 

ra

Double

deg or h:m:s?

Right ascension

pos.eq.ra;meta.main

dec

 

dec

Double

deg

Declination

pos.eq.dec;meta.main

solar_longitude_min

 

solar_longitude

Double

deg

Min Solar longitude Ls (location on orbit / season)

pos.posangle (TBC)

solar_longitude_max

 

solar_longitude

Double

deg

Max Solar longitude Ls (location on orbit / season)

pos.posangle (TBC)

local_time_min

 

local_time_min

Double

h

Local time at observed region

time.phase;stat.min?

local_time_max

 

local_time_max

Double

h

Local time at observed region

time.phase;stat.max?

target_distance_min

 

target_distance (no min/max)

Double

km

Observer-target distance

pos.distance;stat.min

target_distance_max  

Double

kmObserver-target distancepos.distance;stat.max

target_time_min

 

_

Double

d

Observing time in target frame (simplest way to look for coordinated observations)

time.start ??

target_time_max

 

_

Double

d


time.end ??

particle_spectral_type

 

particle_spectral_type

Text

 

 

 

particle_spectral_range_min

 

particle_spectral_range_min

Double

 

 

 

particle_spectral_range_max

 

particle_spectral_range_max

Double

 

 

 

particle_spectral_sampling_step_min

 

particle_spectral_sampling_step_min

Double

 

 

 

particle_spectral_sampling_step_max

 

particle_spectral_sampling_step_max

Double

 

 

 

particle_spectral_resolution_min

 

particle_spectral_resolution_min

Double

 

 

spect.resolution;stat.min

particle_spectral_resolution_max

 

particle_spectral_resolution_max

Double

 

 

spect.resolution;stat.max

were "Relative to service" (Table header) (now optional?)

 

 

 

 

 

 

publisher

 

publisher

Text

 

Resource publisher

meta.name

spatial_coordinate_description

 

spatial_coordinate_description

Text

 

ID of specific coordinate system and version, still TBD

Discussion in progress here: VESPA / Coordinate systems

meta.code.class;pos.frame ?

spatial_origin

 

spatial_origin

Text

 

Defines the frame origin

meta.ref;pos.frame

time_origin

 

time_origin

Text

 

Defines where the time is measured

?

time_scale

 

?

Text

 

Always UTC in data services (may be relaxed in computational services such as ephemeris) - from enumerated list

time.scale

...


• string delimiter for enumerated lists = #first entry#second entry#…#last entry#
TBC with PDS, exoplanets, NSSDC…  (requires a character which never appears in target names, etc) but seems to be the best solution


• Defaut values :
NULL/void: will never return an answer to a query using this parameter (TBC, seems ADQL-related. To be corrected if it is a limitation of the client)
For float / double : -inf for *_min +inf for *_max – still TBC (NaN won't do). To be tested on a real case.
For strings: not needed? (i.e. NULL/void is OK?)

...