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 DR7, for you to use in crossmatches, possibly with uploaded tables.

Tables exposed through this endpoint include: data, phot_all, ssa_time_series from the bgds schema, plates, wolfpalisa from the lsw schema, data from the ppmx schema, exts from the mcextinct schema, main from the hdgaia schema, geocounts, measurements, stations from the lightmeter schema, data from the plts schema, data from the zcosmos schema, epn_core, mpcorb from the mpc schema, archives, main from the wfpdb schema, main from the hppunion schema, main from the wise schema, main from the annisred schema, katkat from the katkat schema, main from the smakced schema, main from the emi schema, cubes, fluxposv1200, fluxposv500, fluxv1200, fluxv500, objects, spectra from the califadr3 schema, main from the spm4 schema, data from the plc2 schema, main, usnocorr from the ppmxl schema, stripe82 from the vlastripe82 schema, nucand from the amanda schema, data from the boydende schema, main from the gps1 schema, epn_core from the titan schema, main from the dmubin schema, data, platecorrs, plates, ppmxcross, spurious, twomasscross from the usnob schema, nucand from the icecube schema, sources from the sdssdr7 schema, alt_identifier, authorities, capability, interface, intf_param, registries, relationship, res_date, res_detail, res_role, res_schema, res_subject, res_table, resource, stc_redshift, stc_spatial, stc_spectral, stc_temporal, table_column, validation from the rr schema, main from the hipparcos schema, main, stars from the mwsce14a schema, data from the polcatsmc schema, spectra, ssa from the dfbsspec schema, data from the gcpms schema, images, srccat from the cars schema, images, photons from the rosat schema, map10, map6, map7, map8, map9, map_union from the prdust schema, data from the veronqsos schema, data from the plc schema, main from the gdr2dist schema, data, ordersmeta from the flashheros schema, rawframes from the maidanak schema, obscore from the ivoa schema, frames from the apo schema, main from the lspm schema, dr2, dr3, dr4, main from the rave schema, data from the antares10 schema, data from the inflight schema, meta from the carsarcs schema, main, photometry from the gdr2mock schema, data from the obscode schema, data from the hiicounter schema, data from the danish schema, cubes, slitspectra from the mlqso schema, main from the tgas schema, main from the maclega schema, data from the theossa schema, main, stars from the mwsc schema, bibrefs, maps, masers, monitor from the ohmaser schema, data from the twomass schema, dr1, dr2_ts_ssa, dr2epochflux, dr2light from the gaia schema, icrscorr, main, ppmxlcross from the ucac3 schema, main from the ucac5 schema, main from the ucac4 schema, main from the urat1 schema, sources from the supercosmos schema, data from the toss schema, rawframes from the liverpool schema, data from the flare_survey schema, main from the hsoy schema, data from the openngc schema, main from the auger schema, plates, rawplates from the potsdam schema, gfh, id, identified, master, nid, unidentified from the arigfh schema, objects, photpar from the sasmirala schema, events, photpoints, timeseries from the k2c9vst schema, cat from the browndwarfs schema, data from the antares schema, data from the fornax schema, main from the taptest schema, main from the applause schema, main from the arihip schema, data from the feros schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, plates from the kapteyn schema, fk6join, part1, part3 from the fk6 schema, main from the dfbsplates schema, columns, services, tables from the glots 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).


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.


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.

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