Table Access Protocol Version 1.0

Dowler, Patrick; Rixon, G.; Tody, Doug

doi:10.5479/ads/bib/2010ivoa.spec.0327d

Cited by 38 publications

(45 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…additions of new local services, improvements on VOTable rendering and on the VO Services discovery GUI). We plan to add support for discovery and execution of Table Access Protocol (TAP; Dowler et al, 2010), also to handle potential multiple endpoints for a VO service in the discovery process, as well as the possibility to execute AstroTaverna workflows in the Taverna Server. We have explored the possibilities of adding a richer Python support through Jython, but the lack of a pure-python Numpy has precluded that possibility.…”

Section: Resultsmentioning

confidence: 99%

“…Specializations of the VO Resource exist for identifying image data services (Simple Image Access Protocol; Tody et al, 2009), spectral data services (Simple Spectral Access Protocol; Tody et al, 2012), positional-search table services (ConeSearch Protocol; Williams et al, 2008), and tabular complex searches (Tabular Access Protocol; Dowler et al, 2010). Each entry contains metadata identifying the curators and publishers of the data, service type, service-type specific descriptions, or the URL for the services entry points.…”

Section: The Virtual Observatory Architecturementioning

confidence: 99%

See 1 more Smart Citation

AstroTaverna—Building workflows with Virtual Observatory services

Ruíz¹,

Garrido²,

Santander-Vela³

et al. 2014

Astronomy and Computing

View full text Add to dashboard Cite

Section: Resultsmentioning

confidence: 99%

Section: The Virtual Observatory Architecturementioning

confidence: 99%

AstroTaverna—Building workflows with Virtual Observatory services

Ruíz¹,

Garrido²,

Santander-Vela³

et al. 2014

Astronomy and Computing

View full text Add to dashboard Cite

“…The software makes extensive use of the Figure 3: Flowchart of the main script. Dowler et al, 2010), an IVOA standard designed to provide access to relational table sets specifically annotated for astrophysical usage. The queries posted to TAP compliant services can be specified using the Astronomical Data Query Language (ADQL, Osuna et al, 2008, another IVOA standard).…”

Section: Libraries and Toolsmentioning

confidence: 99%

Exo-MerCat: A merged exoplanet catalog with Virtual Observatory connection

Alei

Claudi

Bignamini

et al. 2020

Astronomy and Computing

View full text Add to dashboard Cite

The heterogeneity of papers dealing with the discovery and characterization of exoplanets makes every attempt to maintain a uniform exoplanet catalog almost impossible. Four sources currently available online (NASA Exoplanet Archive, Exoplanet Orbit Database, Exoplanet Encyclopaedia, and Open Exoplanet Catalogue) are commonly used by the community, but they can hardly be compared, due to discrepancies in notations and selection criteria. Exo-MerCat is a Python code that collects and selects the most precise measurement for all interesting planetary and orbital parameters contained in the four databases, accounting for the presence of multiple aliases for the same target. It can download information about the host star as well by the use of Virtual Observatory ConeSearch connections to the major archives such as SIMBAD and those available in VizieR. A Graphical User Interface is provided to filter data based on the user's constraints and generate automatic plots that are commonly used in the exoplanetary community. With Exo-MerCat, we retrieved a unique catalog that merges information from the four main databases, standardizing the output and handling notation differences issues. Exo-MerCat can correct as many issues that prevent a direct correspondence between multiple items in the four databases as possible, with the available data. The catalog is available as a VO resource for everyone to use and it is periodically updated, according to the update rates of the source catalogs.

show abstract

“…VESPA is providing an infrastructure to search for data products based on science content and coverage query parameters. This is enabled through a data model called EPNcore (Europlanet core metadata; Erard et al, ), coupled with the Table Access Protocol (Dowler et al, ) developed and maintained by the IVOA. Many HP related data collections are available through the VESPA query interfaces (either the main VESPA query portal, http://vespa.obspm.fr, or from interfaces embedded in tools, such as in AMDA [Automated Multi‐Dataset Analysis; http://amda.irap.omp.eu from the CDPP]).…”

Section: Spase In Practice: Generation and Usementioning

confidence: 99%

The SPASE Data Model: A Metadata Standard for Registering, Finding, Accessing, and Using Heliophysics Data Obtained From Observations and Modeling

et al. 2018

View full text Add to dashboard Cite

The Space Physics Archive Search and Extract Consortium has developed and implemented the SPASE Data Model that provides a common language for registering a wide range of Heliophysics data and other products. The Data Model enables discovery and access tools such that any researcher can obtain data easily, thereby facilitating research, including on space weather. The Data Model includes descriptions of Simulation Models and Numerical Output, pioneered by the Integrated Medium for Planetary Exploration (IMPEx) group in Europe, and subsequently adopted by the Community Coordinated Modeling Center (CCMC). The SPASE group intends to register all relevant Heliophysics data resources, including space‐, ground‐, and model‐based. Substantial progress has been made, especially for space‐based observational data and associated observatories, instruments, and display data. Legacy product registrations and access go back more than 50 years. Real‐time data will be included. The National Aeronautics and Space Administration (NASA) portion of the SPASE group has funding that assures continuity in the upkeep of the Data Model and aids with adding new products. Tools are being developed for making and editing data descriptions. Digital Object Identifiers (DOIs) for Data Products can now be included in the descriptions. The data access that SPASE facilitates is becoming more uniform, and work is progressing on Web Service access via a standard Application Programming Interface. The SPASE Data Model is stable; changes over the past 9 years were additions of terms and capabilities that are backward compatible. This paper provides a summary of the history, structure, use, and future of the SPASE Data Model.

show abstract

Table Access Protocol Version 1.0

Cited by 38 publications

References 6 publications

AstroTaverna—Building workflows with Virtual Observatory services

AstroTaverna—Building workflows with Virtual Observatory services

Exo-MerCat: A merged exoplanet catalog with Virtual Observatory connection

The SPASE Data Model: A Metadata Standard for Registering, Finding, Accessing, and Using Heliophysics Data Obtained From Observations and Modeling

Contact Info

Product

Resources

About