Information on resource '__system__/tap'

Services defined within this resource descriptor

• ROB Virtual Observatory Data Center TAP service

  The ROB Virtual Observatory Data Center'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_links from the link_ch__hss_arrivalforecast schema, epn_links from the link_cme__2ddetection schema, epn_links from the link_cme__3devaluation schema, epn_links from the link_cme__geomagnetic_forecast schema, epn_links from the link_cme__geomagnetic_impact schema, epn_links from the link_cme__icme_arrival schema, epn_links from the link_cme__icme_arrival_forecast schema, epn_links from the link_ssg__flare schema, datalink, epn_core, tracking from the rob_spoca_ch schema, epn_core from the sidc_categorical_geomagnetic_forecast schema, epn_core from the sidc_cme schema, epn_core from the sidc_cme2ddetection schema, epn_core from the sidc_cme3devaluation schema, epn_core from the sidc_flare schema, epn_core from the sidc_flare_proton_forecast schema, epn_core from the sidc_flare_proton_forecast_fulldisk schema, epn_core from the sidc_geomagnetic_forecast schema, epn_core from the sidc_geomagnetic_impact schema, epn_core from the sidc_icme_arrival schema, epn_core from the sidc_icme_arrival_forecast schema, epn_core from the sidc_ssg schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, epn_core from the uset_caii schema, epn_core from the uset_halpha schema, epn_core, epn_links from the uset_sunspot_drawing schema, epn_core from the uset_sunspot_group schema, epn_core from the uset_whitelight 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]