ivoa interoperability meeting – victoria, bc – 18 may 2006 data discovery and metadata query...

IVOA Interoperability Meeting – Victoria, BC – 18 May 2006

Data Discovery and Metadata Query Using Data Discovery and Metadata Query Using Characterisation DMCharacterisation DM

Igor ChilingarianIgor Chilingarian (CRAL Observatoire de Lyon, France/SAI MSU, Russia) (CRAL Observatoire de Lyon, France/SAI MSU, Russia)

on behalf ofon behalf of

Characterisaton subgroup of DM WGCharacterisaton subgroup of DM WG


Commonalities of DAL protocols Commonalities of DAL protocols Query interfaces of:Query interfaces of:

SIAPSIAP

SSAPSSAP

SLAPSLAP

STAP (Astrogrid)STAP (Astrogrid)

In all the cases query is constructed using In all the cases query is constructed using “mnemonic” parameter names, for example“mnemonic” parameter names, for example

POS=180,10&SIZE=1.0&BAND=4e-7/5e-7POS=180,10&SIZE=1.0&BAND=4e-7/5e-7

In all cases “mandatory” query parameters In all cases “mandatory” query parameters correspond to the characterisation DM elementscorrespond to the characterisation DM elements


Using Characterisation DMUsing Characterisation DMQuery interface we propose:Query interface we propose:

Usage of the “axis” concept to “universalize” the queries on different Usage of the “axis” concept to “universalize” the queries on different physical parameters. Usage of at least first and at most second level physical parameters. Usage of at least first and at most second level of the characterisation metadataof the characterisation metadata

Axes are identified by their UCDsAxes are identified by their UCDs

list of available axes should be given by the getCapabilities query list of available axes should be given by the getCapabilities query (or its analogue)(or its analogue)

Usage of complete characterisation UTYPEs as http-get (post) Usage of complete characterisation UTYPEs as http-get (post) parameter namesparameter names

Additional parameters (not covered by characterisation DM) should Additional parameters (not covered by characterisation DM) should be given by the getCapabilities querybe given by the getCapabilities query


Example 1. Accessing SpectraExample 1. Accessing Spectraspectral: give me all the flux calibrated data fromspectral: give me all the flux calibrated data from the archive with the central the archive with the central wavelength between 4500A and 4900A, with a starting wavelength not wavelength between 4500A and 4900A, with a starting wavelength not longer than 4200A, with a finishing wavelength not shorter than 6000Alonger than 4200A, with a finishing wavelength not shorter than 6000A,, having FWHM spectral resolution between 1A and 2A,having FWHM spectral resolution between 1A and 2A,

http://my-vo.org/finddata?http://my-vo.org/finddata?

axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&

aaxis1.coverage.location.Coord.xis1.coverage.location.Coord.CoordinateCoordinate.value=0.45.value=0.45//0.49&0.49&

axis1.coverage.bounds.limits.LoLimit=axis1.coverage.bounds.limits.LoLimit=//0.42&0.42&

axis1.coverage.bounds.limits.HiLimit=0.6axis1.coverage.bounds.limits.HiLimit=0.6//&&

axis1.resolution.refval=0.0001axis1.resolution.refval=0.0001//0.0002&0.0002&

axis2.ucd=phot&axis2.calibrationStatus=1axis2.ucd=phot&axis2.calibrationStatus=1


Example 2: ImagesExample 2: Imagesimages: give me all the flux calibrated data from the archive with the central images: give me all the flux calibrated data from the archive with the central wavelength between 4000A and 10000A, with the right ascension of the wavelength between 4000A and 10000A, with the right ascension of the centre between 12h and 18h, and declination of the centre >+88 deg, centre between 12h and 18h, and declination of the centre >+88 deg, having FWHM spatial resolution not less than 3.6 arcsec. having FWHM spatial resolution not less than 3.6 arcsec. Interesting: this Interesting: this query should also return 3D spectroscopic data if they exist in the archivequery should also return 3D spectroscopic data if they exist in the archive..


axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&

axis1.coverage.location.Coord.Coordinate.value=0.4/1.0&axis1.coverage.location.Coord.Coordinate.value=0.4/1.0&

axis2.ucd=pos&axis1.calibrationStatus=1&axis1.unit=deg&axis2.ucd=pos&axis1.calibrationStatus=1&axis1.unit=deg&

axis2.coverage.location.Coord.Position2D.Value2.c1=180/270&axis2.coverage.location.Coord.Position2D.Value2.c1=180/270&

axis2.coverage.location.Coord.Position2D.Value2.c2=88/90&axis2.coverage.location.Coord.Position2D.Value2.c2=88/90&

axis2.resolution.refval=0.001/&axis2.resolution.refval=0.001/&



Example 3: 3D data (IFU, Fabry-Perot,…)Example 3: 3D data (IFU, Fabry-Perot,…)3D spectra: give me all the flux calibrated data from the archive with the 3D spectra: give me all the flux calibrated data from the archive with the central wavelength between 4500A and 4900A, having FWHM spectral central wavelength between 4500A and 4900A, having FWHM spectral resolution between 1A and 2A, located at the area with the right ascension resolution between 1A and 2A, located at the area with the right ascension of the centre between 12h and 18h, and declination of the centre >+88 deg, of the centre between 12h and 18h, and declination of the centre >+88 deg, having FWHM spatial resolution not less than 1.8 arcsechaving FWHM spatial resolution not less than 1.8 arcsec


?axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&?axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&

axis1.coverage.location.Coord.Spectral.value=0.45axis1.coverage.location.Coord.Spectral.value=0.45//0.49&0.49&

axis1.coverage.bounds.limits.LoLimit=axis1.coverage.bounds.limits.LoLimit=//0.42&0.42&

axis1.coverage.bounds.limits.HiLimit=0.6axis1.coverage.bounds.limits.HiLimit=0.6//&&

axis1.resolution.refval=0.0001axis1.resolution.refval=0.0001//0.0002&0.0002&

axis2.ucd=pos&axis1.calibrationStatus=1&axis1.unit=deg&axis2.ucd=pos&axis1.calibrationStatus=1&axis1.unit=deg&

axis2.coverage.location.Position2D.Value2axis2.coverage.location.Position2D.Value2.c1.c1=180=180//270&270&

axis2.coverage.location.Position2D.Value2axis2.coverage.location.Position2D.Value2.c2.c2=88=88/90/90&&

axis2.resolution.refval=0.001axis2.resolution.refval=0.001//&&



Example 4: Atomic LinesExample 4: Atomic Linesspectral lines: give me all spectral lines of Hydrogen (ssp.atomicNumber), spectral lines: give me all spectral lines of Hydrogen (ssp.atomicNumber), between 900A and 1500A with the final energy level between 13.5 and 13.7 between 900A and 1500A with the final energy level between 13.5 and 13.7 eV (get Lyman series)eV (get Lyman series). “ssp” means Service-Specific Parameter. “ssp” means Service-Specific Parameter


?axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&?axis1.ucd=em&axis1.calibrationStatus=1&axis1.unit=um&

axis1.coverage.location.Coord.value=0.09axis1.coverage.location.Coord.value=0.09//0.10.133&&

axis2.ucd=phys.energy%3Bphys.atom.final%3Bphys.atom.level&axis2.ucd=phys.energy%3Bphys.atom.final%3Bphys.atom.level&

axis2.unit=eV&axis2.calibrationStatus=1&axis2.unit=eV&axis2.calibrationStatus=1&

axis2.coverage.location.Coord.value=13.5axis2.coverage.location.Coord.value=13.5//13.7&13.7&

ssp.atomicNumber=1ssp.atomicNumber=1


CaveatsCaveats

UCD 1+ may contain “;” that is equivalent to “&” UCD 1+ may contain “;” that is equivalent to “&” in the HTTP_GETin the HTTP_GET

Query length may exceed 4096 bytes allowed Query length may exceed 4096 bytes allowed for HTTP_GETfor HTTP_GET

Upper/lower case issue: parameters are case-Upper/lower case issue: parameters are case-sensitive for HTTP_GET, but UTYPEs are case- sensitive for HTTP_GET, but UTYPEs are case- insensitiveinsensitive


Useful FeaturesUseful FeaturesEasy conversion into XQueryEasy conversion into XQuery

Logical extension: use ADQL/x instead of http-get queryLogical extension: use ADQL/x instead of http-get query

No more discussions on the names of the parameters!No more discussions on the names of the parameters!

ivoa interoperability meeting – victoria, bc – 18 may 2006 data discovery and metadata query...

Documents