https://vo.astron.nl/tapObscore-1.1ADQL2.12.0The Astronomical Data Query Language is the standard IVOA dialect of SQL; it contains a very general SELECT statement as well as some extensions for spherical geometry and higher mathematics.

gavo_simbadpoint(identifier TEXT) -> POINT

gavo_simbadpoint queries simbad for an identifier and returns the corresponding point. Note that identifier can only be a literal, i.e., as simple string rather than a column name. This is because our database cannot query simbad, and we probably wouldn't want to fire off millions of simbad queries anyway; use simbad's own TAP service for this kind of applications.

ivo_interval_has(val NUMERIC, iv INTERVAL) -> INTEGER

The function returns 1 if the interval iv contains val, 0 otherwise. The lower limit is always included in iv, behaviour on the upper limit is column-specific.

gavo_getauthority(ivoid TEXT) -> TEXT

returns the authority part of an ivoid (or, more generally a URI). So, ivo://org.gavo.dc/foo/bar#baz becomes org.gavo.dc. The behaviour for anything that's not a full URI is undefined.

gavo_match(pattern TEXT, string TEXT) -> INTEGER

gavo_match returns 1 if the POSIX regular expression pattern matches anything in string, 0 otherwise.

ivo_healpix_center(hpxOrder INTEGER, hpxIndex BIGINT) -> POINT

returns a POINT corresponding to the center of the healpix with the given index at the given order.

ivo_string_agg(expression TEXT, delimiter TEXT) -> TEXT

An aggregate function returning all values of expression within a GROUP contcatenated with delimiter

ivo_apply_pm(ra DOUBLE PRECISION, dec DOUBLE PRECISION, pmra DOUBLE PRECISION, pmde DOUBLE PRECISON, epdist DOUBLE PRECISION) -> POINT

Returns a POINT (in the UNDEFINED reference frame) for the position an object at ra/dec with proper motion pmra/pmde has after epdist years. positions must be in degrees, PMs in should be in julian years (i.e., proper motions are expected in degrees/year). pmra is assumed to contain cos(delta). NOTE: This currently is a crappy approximation that does *not* go through the tangential plane. If you use it, let the operators know so we replace it with something real.

gavo_to_jd(d TIMESTAMP) -> DOUBLE PRECISION

The function converts a postgres timestamp to julian date. This is naive; no corrections for timezones, let alone time scales or the like are done; you can thus not expect this to be good to second-precision unless you are careful in the construction of the timestamp.

ivo_interval_overlaps(l1 NUMERIC, h1 NUMERIC, l2 NUMERIC, h2 NUMERIC) -> INTEGER

The function returns 1 if the interval [l1...h1] overlaps with the interval [l2...h2]. For the purposes of this function, the case l1=h2 or l2=h1 is treated as overlap. The function returns 0 for non-overlapping intervals.

gavo_transform(from_sys TEXT, to_sys TEXT, geo GEOMETRY) -> GEOMETRY

The function transforms ADQL geometries between various reference systems. geo can be a POINT, a CIRCLE, or a POLYGON, and the function will return a geometry of the same type. In the current implementation, from_sys and to_sys must be literal strings (i.e., they cannot be computed through expressions or be taken from database columns). All transforms are just simple rotations, which is only a rough approximation to the actual relationships between reference systems (in particular between FK4 and ICRS-based ones). Not that, in particular, the epoch is not changed (i.e., no proper motions are applied). We currently support the following reference frames: ICRS, FK5 (which is trested as ICRS), FK4 (for B1950. without epoch-dependent corrections), GALACTIC. Reference frame names are case-sensitive.

ivo_healpix_index(order INTEGER, ra DOUBLE PRECISION, dec DOUBLE PRECISION) -> BIGINT

Returns the index of the (nest) healpix with order containing the spherical point (ra, dec). An alternative, 2-argument form ivo_healpix_index(order INTEGER, p POINT) -> BIGINT is also available.

ivo_hashlist_has(hashlist TEXT, item TEXT) -> INTEGER

The function takes two strings; the first is a list of words not containing the hash sign (#), concatenated by hash signs, the second is a word not containing the hash sign. It returns 1 if, compared case-insensitively, the second argument is in the list of words coded in the first argument. The behaviour in case the the second argument contains a hash sign is unspecified.

gavo_histogram(val REAL, lower REAL, upper REAL, nbins INTEGER) -> INTEGER[]

The aggregate function returns a histogram of val with nbins+2 elements. Assuming 0-based arrays, result[0] contains the number of underflows (i.e., val<lower), result[nbins+1] the number of overflows. Elements 1..nbins are the counts in nbins bins of width (upper-lower)/nbins. Clients will have to convert back to physical units using some external communication, there currently is no (meta-) data as lower and upper in the TAP response.

gavo_to_mjd(d TIMESTAMP) -> DOUBLE PRECISION

The function converts a postgres timestamp to modified julian date. This is naive; no corrections for timezones, let alone time scales or the like are done; you can thus not expect this to be good to second-precision unless you are careful in the construction of the timestamp.

ivo_nocasematch(value TEXT, pattern TEXT) -> INTEGER

ivo_nocasematch returns 1 if pattern matches value, 0 otherwise. pattern is defined as for the SQL LIKE operator, but the match is performed case-insensitively. This function in effect provides a surrogate for the ILIKE SQL operator that is missing from ADQL. On this site, this is actually implemented using python's and SQL's LOWER, so for everything except ASCII, your milage will vary.

ivo_hasword(haystack TEXT, needle TEXT) -> INTEGER

gavo_hasword returns 1 if needle shows up in haystack, 0 otherwise. This is for "google-like"-searches in text-like fields. In word, you can actually employ a fairly complex query language; see http://www.postgresql.org/docs/8.3/static/textsearch.html for details.

gavo_ipix(long REAL, lat REAL) -> BIGINT

gavo_ipix returns the q3c ipix for a long/lat pair (it simply wraps the 13c_ang2ipix function). This is probably only relevant when you play tricks with indices or PPMXL ids.

BOX

POINT

CIRCLE

POLYGON

REGION

CENTROID

COORD1

COORD2

DISTANCE

CONTAINS

INTERSECTS

AREA

LOWER

ILIKE

OFFSET

CAST

IN_UNIT

WITH

TABLESAMPLE

Written after a table reference, TABLESAMPLE(10) will make the database only use 10% of the rows; these are `somewhat random' in that the system will use random blocks. This should be good enough when just testing queries (and much better than using TOP n).

UNION

EXCEPT

INTERSECT

text/xmlapplication/x-votable+xml;version=1.4vodmltext/htmlhtmlapplication/x-votable+xml;serialization=binary2votable/b2application/geo-jsongeojsonapplication/fitsfitstext/csvtext/csv;header=presentcsvapplication/x-votable+xml;serialization=tabledatavotable/tdapplication/jsonjsonapplication/x-votable+xmlvotabletext/plaintext/tab-separated-valuestsv1728003600200002000000020000000https://vo.astron.nl/__system__/tap/run/availabilityhttps://vo.astron.nl/__system__/tap/run/capabilitieshttps://vo.astron.nl/__system__/tap/run/tableMetadatahttps://vo.astron.nl/__system__/tap/run/examples