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


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

While columns with xtype adql:POINT are correctly ingested into the database, adql:REGION columns are left alone (i.e., they are strings in the database). The reason for this behaviour is that in order to infer a column type, one would have to inspect the entire table up front.

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)