AIP DaCHS

The AIP DaCHS'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: dens256, fof, redshifts from the bolshoi schema, columns, services, tables from the glots schema, fof, fofmtree, fofparticles, particles85, redshifts, treesnapnums from the mdr1 schema, rave_dr4 from the ravedr4 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, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema.

Tables containing the information in the IVOA Registry. To query these tables, use `our TAP service`_. For more information and example queries, see the `RegTAP specification`_. .. _our TAP service: /__system__/tap/run/info .. _RegTAP specification: http://www.ivoa.net/documents/RegTAP/

Operators of publishing registries can use this service to request a re-harvest of their registry by pasting in their registry's IVOID below. If you paste in the magic value ``ivo://ivoa.net/rofr``, we will also fetch new registries from the RofR. You usually want to use this when you want to see the effect of some change in your registry on, say, TOPCAT. Note that you cannot start a full re-harvest of a registry from this interface. Contact the operators if you think you need that.

This service gives access to the 4th data release of RAVE (RAdial Velocity Experiment). It contains radial velocities of stars, stellar atmospheric parameters, some abundances and distances.