Information on resource '__system__/tap'

Services defined within this resource descriptor

• PADC TAP Server on voparis-tap-planeto.obspm.fr TAP service

  The PADC TAP Server on voparis-tap-planeto.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 apis schema, epn_core from the basecom schema, epn_core, observatories from the bdip schema, epn_core from the crism_speclib schema, epn_core from the dynastvo schema, epn_core from the exoplanet schema, epn_core from the gmap schema, epn_core from the hst_planeto schema, epn_core from the iks schema, epn_core from the lunar_craters schema, epn_core from the m4ast schema, epn_core from the mars_craters schema, epn_core from the mars_craters_lagain schema, epn_core from the mercury_craters schema, epn_core from the meteor_showers schema, epn_core from the moonsprop schema, epn_core from the planets schema, epn_core from the spectro_asteroids schema, epn_core from the spectro_m_ast schema, epn_core from the spectro_planets schema, epn_core from the spectro_stars schema, epn_core from the spectro_trojans schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, epn_core from the titan_profiles schema, epn_core from the tnosarecool schema, epn_core from the usgs_wms schema, epn_core from the venus_craters schema, epn_core from the vims_satellites schema, epn_core from the vir_ros schema, epn_core from the voccdb schema, epn_core from the vros_geocor schema, epn_core from the vvex 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]