Data Access Layer standards: current status...TAP 1.1 and ADQL 2.1 are discussed Drafts DataLink 1.0...

Data Access Layer standards: current status

F.Bonnarel (DAL WG chair: CDS / CNRS)

M.Molinaro (DAL WG vice-chair: OAT/ INAF)

DALI [VOTABLE]

TAP ADQL

ObsTAP ([Obscore])

ConeSearch SIAV1 SSA1.1 SIAV2.0

AccessData DataLink

??????

TAP = generic and interoperable relational DBMS interface. ADQL - extended SQL forn Astronomy. IVOA Recommendations since 2008 and 2010

« Simple » access protocols (ConeSerach, SIA, SSA …) : mainly Parameter query interface for catalogues, images, cubes, spectra

ObsTAp is dataset discovery based on a TAP service (2011)

Newcomers : DataLink (2015) AccessData (Working Draft)

After a few years of implementations and feedback TAP and ADQL are currently under revision

SIA very old (2002) - need a major upgrade + data extraction (= AccessData)

* Data Discovery (Query) * A service shall be able to receive queries regarding its data collection(s) from a client, with the client placing one or more of the following constraints: * RA,Dec * Frequency/wavelength * Polarization states * Spatial size * Angular resolution * Integration time * Time of observation

* A service shall return to the client a list of observations, and the corresponding metadata for each observation, meeting the user-imposed constraints. In the event that the user places no constraints, the entire list of observations, and the corresponding metadata for each data set, shall be returned. In the event that no data meet the user's constraints, the service shall indicate the absence of any matches.

Multi-dimensional Data Acces

minimal requirements from CSP:

* Data Access * Once a user has the list of observations that satisfy the constraints, they select all or a subset of the observations and: * Download the complete science data for each of the selected observations (the service shall return the complete multi-dimensional science data and metadata for each selected observation) or; * Download simple cutouts of the science data for each of the selected observations (the service shall be able to extract and return a user-specified subset of the complete multi-dimensional science data and metadata for each selected observation). * Simple Cutout * For a simple cutout, the user-specified subset is restricted to be a contiguous interval within each dimension of the multi-dimensional science data. The user should *not* be allowed to specify subsets with "gaps" or resampling or anything like that. * Spatial: a circle (a coordinate and a radius) * Energy: one interval (from energy1 to energy2) * Time: one interval (from time1 to time2) * Polarization: a list

Multi-dimensional Data Acces

minimal requirements from CSP:

Radio data cube

Green and red Axes

- Spatial dimensions

Blue Axis :

- Wavelength dimension

STEP 1 : Discovery

STEP 2:

Description :

- Axes type

- Extension

- Typical value

- Date

- Data producer,

- Data curator

i

« Integral Field Unit » optical

Domain datacube

STEP 3

AccessData

Subsets (trasnformed or not)

Remotly transparently

accesssible

Sous - cube

Multidimensional data

protocol Caravane

Final view

Multidimensional data

protocol Caravane

SIA 2.1 AccessDat

a

1.1

Current view

Cube Access scenario: basic

(first version of protocols, october 2015)

• I ) Scenario : find out cube services from registry. Obstap (generic, ADQL)

or SIAV2 (cube-oriented, parameterQuery)

• II ) Query from an ObsCore service « select * from Obscore where dataproduct_type = cube »

• II bis ) Query from a SIAV2 service « http://.......?request=query&pos=circle 3.0 2.0 1.0 &band=0.001 0.003 »

Cube Access scenario: basic

(first version of protocols, october 2015)

• III ) query response :

votable, ObsCore/consistent

• IV ) DataLink : fixed links, metadata services, access data

• IV bis ) direct AccessData

ObsCore Heuristic Map

Discovery

Discovery

AMIGA response for NGC 613

DataLink

Two mechanisms to bound resources (others datasets, descriptions, services) to « discovered » datasets = resource descriptor and links services Cube average (fixed links), accessdata, (custom services)

AccesData

• Cutout driven by parameters identical to Query • POS=CIRCLE 12 34 0.5 • POS=RANGE 12.014.0 34.0 36.0 • BAND=500 550 • TIME= 55000.0 56000.0 • POL=Q,POL=.....

Client implementation : TapHandle :

TAP 1.1 and ADQL 2.1 are discussed Drafts

DataLink 1.0 is a recommendation since June 2015

SIAV2.0 is a proposed recommendation with a very long stay in TCG review phase.

Hopefully all main issues have been solved and it becomes a

recommendation before Sydney

AccesData 1.0 : new version of WD before Sydney. Should be fast because it’s very dependant on SIAV2. - recommendation well before May 2016 interop

SimDAL (Theoretical data), VOTP (Voevent), Time Series , upgrade of DataLink/SIAV2/AccessData

Cube Access scenario

(open discussion )

• I ) Scenario : find out cube services from registry. Obstap / SIAV2

• II bis ) Query from an ObsCore service « select * from Obscore where dataproduct_type = cube »

• II ) Query from a SIAV2 service « http://.......?request=query&pos=...&band=.... »

• Stored datasets • Virtual datasets

Cube Access scenario

(second version of protocols, may 2015)

• IV ) direct acces to Metadata (get WCS or other details) .

Additional metadata, ImageDM consistent metadata (= ImageDM serialization)

• IV bis ) datalink

• V ) Accessdata : cutout, resampling, regridding

ImageDataModel heuristic map