Table Access Protocol

Table Access Protocol
Name	Table Access Protocol
Status	Draft
Developer	International Virtual Observatory Alliance
First published	2008
Latest version	1.0
License	Open

Table Access Protocol

The Table Access Protocol is a networked interface standard for querying and retrieving tabular astronomical data from remote services. It enables interoperability among archives, observatories, and analysis tools by specifying query parameters, result encodings, and access patterns for catalogs, time series, and spectral tables. The standard is used by data centers, archives, and virtual observatory software to allow clients to submit parameterized queries and receive machine-readable tables.

Overview

The protocol defines a RESTful-style HTTP binding that accepts structured queries and returns tabular results, facilitating integration between archives such as European Southern Observatory, Space Telescope Science Institute, National Radio Astronomy Observatory, European Space Agency, and Centre de Données astronomiques de Strasbourg. It complements other virtual observatory standards maintained by the International Virtual Observatory Alliance and works alongside services from Sloan Digital Sky Survey, Gaia Data Processing and Analysis Consortium, ALMA Observatory, Hubble Space Telescope, and Chandra X-ray Observatory. Clients such as TOPCAT, Aladin, AstroPy, VOClient, and pyVO implement bindings to query catalogs delivered by repositories including VizieR, NASA Exoplanet Archive, HEASARC, SIMBAD, and Vizier. The protocol supports parameterized positional constraints, column selection, and format negotiation used by tools from European Space Agency's Herschel Science Centre and research groups at Max Planck Institute for Astronomy.

History and Development

Work on the protocol originated within the International Virtual Observatory Alliance working groups to harmonize access to catalog services coordinated by data centers like Centre de Données astronomiques de Strasbourg and national facilities such as National Aeronautics and Space Administration and European Space Agency. Early design discussions involved contributors from Sloan Digital Sky Survey, UK Astronomy Technology Centre, Max Planck Institute for Radio Astronomy, Jet Propulsion Laboratory, and National Center for Supercomputing Applications. The specification evolved alongside related standards such as Simple Cone Search, Simple Image Access Protocol, and VOTable formats, and was refined through interoperability meetings at events hosted by ADASS and workshops at institutions like Caltech and Cambridge Observatory. Subsequent revisions incorporated feedback from archives operated by NOAO, Canadian Astronomy Data Centre, and survey teams from Pan-STARRS.

Protocol Specification

The specification prescribes request parameters, response codes, and allowed MIME types to ensure consistent behavior across servers operated by organizations like European Southern Observatory and Space Telescope Science Institute. It defines query parameters for spatial constraints (cone, box), time ranges referencing missions such as Kepler, column filters used in catalogs like Gaia Catalogue, and paging for large result sets served by infrastructures including Amazon Web Services used by some archives. Responses include status metadata compatible with tools such as TOPCAT and serialization in formats interoperable with libraries from AstroPy and NumPy. The protocol also specifies error handling, version negotiation, and capability discovery endpoints similar to those in services from Hubble Space Telescope and Chandra X-ray Observatory.

Data Models and Formats

Results are typically encoded in XML-based table formats standardized by the community, interoperable with formats produced by VOTable-aware tools, and convertible to FITS binary tables used by observatories like ALMA and JCMT. The specification supports alternate encodings including comma-separated values used by repositories such as VizieR and JSON serializations consumed by web portals at European Space Agency. Metadata vocabularies draw on models used by International Virtual Observatory Alliance data models and link to registry records maintained by services like the Virtual Observatory Registry. Column semantics often reference standard coordinate frames defined by International Astronomical Union recommendations and time systems used in missions such as Gaia and Kepler.

Implementations and Clients

Server-side implementations exist in software stacks developed by institutions such as Centre de Données astronomiques de Strasbourg (DaCHS), HEASARC, Canadian Astronomy Data Centre, and custom deployments at European Southern Observatory. Client libraries are provided by projects including AstroPy, pyVO, TOPCAT, and web clients embedded in portals from European Space Agency and NASA. Interoperability testing has been conducted at events organised by the International Virtual Observatory Alliance and demonstrated in services from Sloan Digital Sky Survey, Gaia Data Release teams, and archives hosted by Space Telescope Science Institute.

Use Cases and Applications

Typical use cases include cross-matching catalogs from Sloan Digital Sky Survey, extracting time series from surveys like Kepler and TESS, retrieving spectral line lists from ALMA archives, and serving large object catalogs from missions such as Gaia. Workflows link the protocol to visualization in Aladin and analysis in TOPCAT and AstroPy pipelines used in projects at Max Planck Institute for Astronomy and Harvard-Smithsonian Center for Astrophysics. It is also used in survey pipelines for Pan-STARRS, archival access at Space Telescope Science Institute, and data dissemination by the European Southern Observatory.

Security and Authentication

While many services provide open, unauthenticated access following practices at repositories such as VizieR and SIMBAD, authenticated endpoints integrate with identity federations and token systems like OAuth 2.0 or institutional authentication used by NASA and European Space Agency science platforms. Secure transport is typically provided by Transport Layer Security and access control policies mirror those deployed by data centers such as Centre de Données astronomiques de Strasbourg and NOAO. Audit trails and usage monitoring are implemented by archives hosted at Space Telescope Science Institute and cloud-backed services used by European Southern Observatory.

Category:Astronomical data standards