Information on resource '__system__/tap'

Services defined within this resource descriptor

• ALeRCE TAP service TAP service

  The ALeRCE TAP service's TAP end point. The Table Access Protocol (TAP) lets you execute queries against our database tables, inspect various metadata, and upload your own data. It is thus the VO's premier way to access public data holdings.

  Tables exposed through this endpoint include: allwise, band, catalog_id_lut, classifier, detection, feature, feature_name_lut, feature_version_lut, forced_photometry, lsst_detection, lsst_dia_object, lsst_forced_photometry, lsst_mpc_orbits, lsst_ss_detection, lsst_ss_object, magstat, object, probability, sid_lut, taxonomy, xmatch, ztf_dataquality, ztf_detection, ztf_forced_photometry, ztf_gaia, ztf_non_detection, ztf_object, ztf_ps1, ztf_reference, ztf_ss from the alerce_tap schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema.

Tables defined within this resource descriptor

• tap_schema.columns – queryable through TAP and ADQL

  Columns in tables available for ADQL querying.

• tap_schema.groups – queryable through TAP and ADQL

  Columns that are part of groups within tables available for ADQL querying.

• tap_schema.key_columns – queryable through TAP and ADQL

  Columns participating in foreign key relationships between tables available for ADQL querying.

• tap_schema.keys – queryable through TAP and ADQL

  Foreign key relationships between tables available for ADQL querying.

• tap_schema.schemas – queryable through TAP and ADQL

  Schemas containing tables available for ADQL querying.

• tap_schema.supportedmodels

  Standard data models supported by this service.

  This is a non-standard tap_schema table used by DaCHS in the creation of registry records. It is manipulated through gavo imp on tables with supportsModel and supportsModelURI properties.

• tap_schema.tables – queryable through TAP and ADQL

  Tables available for ADQL querying.

• tap_schema.tapjobs

  A non-standard (and not tap-accessible) table used for managing asynchronous TAP jobs. It is manipulated through TAP job creation and destruction internally. Under very special circumstances, operators can use the gavo admin cleantap command to purge jobs from this table.

  Note that such jobs have corresponding directories in $STATEDIR/uwsjobs, which will be orphaned if this table is manipulated through SQL.

[Manage RD]