Information on Service 'GAVO Data Center TAP service'

The GAVO 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.

In GAVO's data center, we in particular hold several large catalogs like PPMXL, 2MASS PSC, USNO-B2, UCAC4, WISE, SDSS DR16, HSOY, and several Gaia data releases and ancillary resources for you to use in crossmatches, possibly with uploaded tables.

Tables exposed through this endpoint include: nucand from the amanda schema, main from the annisred schema, data from the antares schema, data from the antares10 schema, dr10 from the apass schema, frames from the apo schema, main from the applause schema, gfh, id, identified, master, nid, unidentified from the arigfh schema, main from the arihip schema, main from the auger schema, data, phot_all, ssa_time_series from the bgds schema, data from the boydende schema, cat from the browndwarfs schema, cubes, fluxposv1200, fluxposv500, fluxv1200, fluxv500, objects, spectra from the califadr3 schema, images, srccat from the cars schema, meta from the carsarcs schema, line_tap from the casa_lines schema, main from the cns5 schema, main from the cns5update schema, main from the cs82morphoz schema, geo from the cstl schema, data from the danish schema, main from the dfbsplates schema, raw_spectra, spectra, ssa from the dfbsspec schema, main from the dmubin schema, main from the emi schema, data from the feros schema, fk6join, part1, part3 from the fk6 schema, data from the flare_survey schema, data, ordersmeta from the flashheros schema, data from the fornax schema, dr2_ts_ssa, dr2epochflux, dr2light, dr3lite, edr3lite from the gaia schema, hyacob, maglims5, maglims6, maglims7, main, missing_10mas, rejected, resolvedss from the gcns schema, data from the gcpms schema, main from the gdr2ap schema, main from the gdr2dist schema, main, photometry from the gdr2mock schema, spectra, ssameta, withpos from the gdr3spec schema, main from the gedr3auto schema, litewithdist, main from the gedr3dist schema, generated_data, maglim_5, maglim_6, maglim_7, main, parsec_props from the gedr3mock schema, main from the gedr3spur schema, columns, services, tables from the glots schema, main from the gps1 schema, main from the hdgaia schema, data from the hiicounter schema, main from the hipparcos schema, main from the hppunion schema, main from the hsoy schema, nucand from the icecube schema, data from the inflight schema, obs_radio, obscore from the ivoa schema, events, photpoints, timeseries from the k2c9vst schema, plates from the kapteyn schema, katkat from the katkat schema, data from the lamost5 schema, ssa_lrs, ssa_mrs from the lamost6 schema, disk_basic, h_link, ident, mes_binary, mes_mass_pl, mes_mass_st, mes_radius_st, mes_sep_ang, mes_teff_st, object, planet_basic, provider, source, star_basic from the life_td schema, geocounts, measurements, stations from the lightmeter schema, rawframes from the liverpool schema, rmtable, spectra, ssameta from the lotsspol schema, main from the lspm schema, plates, wolfpalisa from the lsw schema, main from the magic schema, reduced from the maidanak schema, exts from the mcextinct schema, cubes, slitspectra from the mlqso schema, epn_core, mpcorb from the mpc schema, main, stars from the mwsc schema, main, stars from the mwsce14a schema, data from the obscode schema, bibrefs, maps, masers, monitor from the ohmaser schema, measurements, ssa from the onebigb schema, data, shapes from the openngc schema, main from the pcc schema, data from the plc schema, data from the plc2 schema, data from the plc3 schema, data from the plts schema, data from the polcatsmc schema, cubes, maps from the ppakm31 schema, data from the ppmx schema, main, usnocorr from the ppmxl schema, map10, map6, map7, map8, map9, map_union from the prdust schema, dr2, dr3, dr4, main from the rave schema, images, photons from the rosat schema, alt_identifier, authorities, capability, g_num_stat, interface, intf_param, registries, relationship, res_date, res_detail, res_role, res_schema, res_subject, res_table, resource, stc_spatial, stc_spectral, stc_temporal, subject_uat, table_column, tap_table, validation from the rr schema, objects, photpar from the sasmirala schema, main from the sdssdr16 schema, sources from the sdssdr7 schema, main from the smakced schema, main from the species schema, main from the spm4 schema, sources from the supercosmos schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, main from the taptest schema, main from the tenpc schema, main from the tgas schema, data from the theossa schema, data, line_tap from the toss schema, data from the twomass schema, icrscorr, main, ppmxlcross from the ucac3 schema, main from the ucac4 schema, main from the ucac5 schema, main from the urat1 schema, data, platecorrs, plates, ppmxcross, spurious, twomasscross from the usnob schema, data from the veronqsos schema, stripe82 from the vlastripe82 schema, main from the wdsdss10 schema, archives, main from the wfpdb schema, main from the wise schema, main from the xpparams schema, data from the zcosmos schema.

For a list of all services and tables belonging to this service's resource, see Information on resource '__system__/tap'

Service Documentation

This service speaks TAP, a protocol designed to allow the exchange of queries and data between clients (that's normally something running on your computer) and servers (e.g., us).

You will want to use some sort of client to query TAP services; examples for those include:

You can, in a pinch, use our service in an XML-enabled browser, too. Under Overview, look for the bullet point on tap and follow the link to "this service". Then, click on "New job..." in the job list, enter your query, click "Set query", then "Execute query". Reload the page you are redirected to now and then to see when your job is finished, then retrieve the result.

The queries this service executes are written an a dialect of SQL called ADQL. You need to learn it to use this service. See our ADQL tutorial. Also do not miss the local examples.

By the way, for quick ad-hoc queries from within a browser, our ADQL form service may be more convenient than TAP.

Also see the table metadata of the tables exposed here.

Local information: This service may put a much lower limit on uploads in sync queries than advertised in the table metadata. Unfortunately, current TOPCAT versions don't give terribly helpful error messages when the server rejects a query because the attached upload is too large (something like “Error writing request body to server“). If that happens to you, just switch to asynchronous querying (in TOPCAT, that's in the “Mode” combo box just above the query editor).

Issues

For information on our ADQL implementation, see the ADQL service info.

If multiple output columns in a query would end up having the same name, in the output VOTable they are disambiguated by appending underscores. This is in violation of the specification, but since fixing it would require rather intrusive changes into our software and it is not clear why one should want to use names when they are not unique to begin with, this will probably not be fixed.

Overview

You can access this service using:

This service is published as follows:

local means it is listed on our front page, ivo_managed means it has a record in the VO registry.

Input Fields

The following fields are available to provide input to the service (with some renderers, some of these fields may be unavailable):

NameTable Head DescriptionUnitUCD
format Format Deprecated alias of RESPONSEFORMAT N/A N/A
lang Lang A name of a language that QUERY should be parsed as. See capabilities for what you can pass in here. N/A N/A
maxrec Match limit Maximum number of records returned. Pass 0 to retrieve service parameters. N/A N/A
maxrec Match limit Maximum number of records returned. Pass 0 to retrieve service parameters. N/A N/A
query Query The query to be executed. N/A N/A
request Request Type of operation requested; this can be doQuery or getCapabilities. Preferably, don't pass it at all. N/A N/A
responseformat Output Format File format requested for output. N/A meta.code.mime
responseformat Output Format File format requested for output. N/A meta.code.mime
upload Upload A TAP-compliant upload; roughly: (tablename,source-uri), where source-uri can also have a param: scheme. N/A N/A
verb Verbosity Exhaustiveness of column selection. VERB=1 only returns the most important columns, VERB=2 selects the columns deemed useful to the average user, VERB=3 returns a table with all available columns. N/A N/A
verb Verbosity Exhaustiveness of column selection. VERB=1 only returns the most important columns, VERB=2 selects the columns deemed useful to the average user, VERB=3 returns a table with all available columns. N/A N/A
version Version Don't use this parameter. You'll only break stuff. N/A N/A

VOResource XML (that's something exclusively for VO nerds)