[ Re: Vocabularising dataproduct_type] an attempt for definitions for catalog and source list

[Mireille LOUYS]

hi all,

here is my suggestion for the term */catalog/* as it has been used so 
far in the VO

/catalog/:

a set of physical quantities recorded from an observing/simulation 
process and measured/computed for a set of individual astronomical 
objects (sources).
Each catalog entry corresponds to one individual source object.
The usual representation is a table with columns figuring the quantities 
and rows representing an entry.

/source list:/

a catalog where entries are derived from one or a restricted set or data 
products : single image, multiband image, radio or hyperspectral cube, 
eventlist for instance.

Typically, ObsTAP can handle source list as dataproducts, with coverage 
inherited from the progenitor dataset.

On the contrary very large catalogs like survey, hips catalogs with 
coverage='allsky' are managed within archives/datacenters and searched 
on with keywords from the astronomical semantics, like type of objects, 
regime, instrument types, survey name, etc.

Here is an interface example: http://cdsarc.unistra.fr/viz-bin/cat

Are there server applications distributing such all sky catalogs with 
Obscore as one single dataproduct?

best , Mireille

-- 
--
Mireille Louys,  MCF (Associate Professor)
CDS				IPSEO, Images, Laboratoire Icube
Observatoire de Strasbourg	Telecom Physique Strasbourg
11 rue de l'Université		300, Bd Sebastien Brandt CS 10413
F- 67000-STRASBOURG		F-67412 ILLKIRCH Cedex
Tel: +33 3 68 85 24 34

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dal/attachments/20200324/94f76561/attachment-0001.html>