Information on resource '__system__/tap'

Services defined within this resource descriptor

• PADC TAP Server on voparis-cdpp.obspm.fr TAP service

  The PADC TAP Server on voparis-cdpp.obspm.fr'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: epn_core from the spectro_planets2 schema, epn_core from the luckystar schema, epn_core from the titan schema, epn_core from the cadc schema, epn_core from the planets schema, vo_lightcurve, vo_obscore, vo_spectrum from the hess schema, vo_obscore from the hess_dr schema, epn_core from the herschel schema, epn_core from the pspecf schema, epn_core from the irtf_juno schema, data from the hess2 schema, epn_core from the lunar_crater_database schema, epn_core from the tnosarecool schema, epn_core from the vims schema, epn_core from the vvex schema, epn_core from the vvex_db0 schema, epn_core from the iks2 schema, epn_core from the iks schema, epn_core from the exotopo schema, frames from the dfbs schema, epn_core from the planets2 schema, epn_core from the vvex_db schema, epn_core from the das2meudon schema, epn_core from the expres schema, epn_core from the vims_satellites schema, epn_core from the sbnaf schema, epn_core from the spectro_asteroids schema, epn_core from the das2uiowa schema, epn_core from the pds_speclib schema, epn_core from the hst_planeto schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, epn_core from the das2meudon_datalink schema, data from the hess_ssa schema, obscore from the ivoa schema, epn_core from the cadc_ssois_svo_fps schema, epn_core from the bass2000 schema, vo_obscore from the cta schema, epn_core from the spectro_planets3 schema, epn_core from the spectro_planets schema, epn_core from the cadc_test6 schema, epn_core from the cadc_test7 schema, epn_core from the basecom schema, epn_core from the cadc_test3 schema.

Tables defined within this resource descriptor

• tap_schema.columns – queriable through TAP and ADQL

  Columns in tables available for ADQL querying.

• tap_schema.groups – queriable through TAP and ADQL

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

• tap_schema.key_columns – queriable through TAP and ADQL

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

• tap_schema.keys – queriable through TAP and ADQL

  Foreign key relationships between tables available for ADQL querying.

• tap_schema.schemas – queriable 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 – queriable 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]