The PADC TAP Server on voparis-tap-sandbox.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 amdadb schema, epn_core from the apis schema, epn_core from the basecom schema, epn_core from the bass2000 schema, epn_core, observatories from the bdip schema, epn_core from the cassini_rpws schema, epn_core from the ceres_test schema, epn_core from the csa schema, epn_core from the cubesat_project schema, main from the esor schema, epn_core from the exoplanet schema, epn_core from the expres schema, epn_core from the gmap schema, obscore from the hess_dr schema, epn_core from the hfc1ar_backup schema, epn_core from the hfc1ar schema, epn_core from the hfc1ar_majtrim schema, epn_core from the hfc1sunspots schema, epn_core from the hfc1t3 schema, epn_core from the hst_asteroids schema, epn_core from the hst_planeto schema, epn_core from the iitatehf schema, epn_core from the iks schema, epn_core from the i_lofar schema, epn_core from the impex schema, ipda from the ipda schema, epn_core from the ir_stars schema, obscore from the ivoa schema, epn_core from the juno_waves schema, epn_core from the jwst schema, epn_core from the lathys schema, epn_core from the luckystar schema, epn_core from the lunar_craters schema, epn_core from the m4ast schema, epn_core from the m_aster schema, epn_core from the meteor_showers schema, epn_core from the missions_ipda schema, epn_core from the moonsprop schema, main from the naroo schema, epn_core from the nda schema, epn_core from the nrh schema, epn_core from the orfees schema, epn_core from the parsec schema, epn_core from the pds_speclib schema, epn_core from the planetary_features schema, epn_core from the planets schema, epn_core from the planets_tuto schema, main, rawplates from the posse schema, epn_core from the profils schema, epn_core from the radiojove_hnrao_fsx8sraw schema, epn_core from the rosetta_anaglyphs schema, epn_core from the ros_recal schema, main from the siamama schema, epn_core from the spase_vespa schema, epn_core from the spectro_asteroids schema, epn_core from the spectro_planets schema, epn_core from the spectro_star schema, epn_core from the spectro_trojans schema, epn_core from the stereo_waves schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, epn_core from the terrestrial_impact_craters schema, epn_core from the test_datalink1 schema, epn_core from the test_datalink2 schema, epn_core from the test_datalink3 schema, epn_core from the test_hst_planeto schema, epn_core, fogg_akr_wind, leblanc_nda_jupiter_emi, leblanc_nda_jupiter_obs, louis_juno_waves, marques_nda_jupiter, taubenschuss_frp_saturn, wu_anomalous_nsmr, wu_nkom_saturn, wu_skr_harmonic from the tfcat schema, epn_core from the titan_profiles schema, epn_core from the tnosarecool schema, main from the ufe schema, epn_core from the usgs_wms schema, epn_core from the vims_satellites schema, epn_core from the vir_ros schema, epn_core from the vispecstar schema, epn_core from the vistcalib schema, epn_core from the voccdb schema, epn_core from the voyager_pra schema, epn_core from the vvex_db schema, epn_core from the vvex schema, epn_core from the vvex_test schema, epn_core from the wind_waves schema.
Columns in tables available for ADQL querying.
Columns that are part of groups within tables available for ADQL querying.
Columns participating in foreign key relationships between tables available for ADQL querying.
Foreign key relationships between tables available for ADQL querying.
Schemas containing tables available for ADQL querying.
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.
Tables available for ADQL querying.
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.
Please report errors and problems to the site operators. Thanks.