Search

Start Over Subject astronomy-databases Publisher The GAVO DC team
1. A Short Course on ADQL
ID:
ivo://org.gavo.dc/misc/adqlcourse
Title:
A Short Course on ADQL
Short Name:
GAVO ADQL course
Date:
27 Dec 2024 08:31:03
Publisher:
The GAVO DC team
Description:
This is a course on the Virtual Observatory's main query language ADQL (short for Astronomical Data Query Language), which is a SQL dialect standardised so users do not have to learn new languages each time they want to use a new resource. We also introduce the basic aspects of the Table Access Protocol TAP, which transports ADQL queries, their results as well as the metadata necessary to write meaningful queries. The course comes with many exercises, most of which also have solutions. We hope it is suitable for both self-study and as lecture notes in teacher-led situations.
2. Global TAP Schema Simple Search
ID:
ivo://org.gavo.dc/glots/q/plain
Title:
Global TAP Schema Simple Search
Short Name:
GloTS plain
Date:
27 Dec 2024 08:31:01
Publisher:
The GAVO DC team
Description:
The global TAP schema collects information on tables and columns from known TAP servers. This facilitates locating queriable data by physics (via UCD) or keywords (via description). Note that this shouldn't really be necessary as all information present here should be exposed through Registry records. However, in reality data providers currently are much more liable to give column metadata in their tap_schema than in their Registry records. Hence, for the time being, we maintain this service by harvesting tap_schemas about monthly.
3. GloTS, the Global TAP Schema
ID:
ivo://org.gavo.dc/glots/q/createTables
Title:
GloTS, the Global TAP Schema
Date:
06 Feb 2024 08:59:18
Publisher:
The GAVO DC team
Description:
The global TAP schema collects information on tables and columns from known TAP servers. This facilitates locating queriable data by physics (via UCD) or keywords (via description). Note that this shouldn't really be necessary as all information present here should be exposed through Registry records. However, in reality data providers currently are much more liable to give column metadata in their tap_schema than in their Registry records. Hence, for the time being, we maintain this service by harvesting tap_schemas about monthly.