Table Access Protocol (TAP)
The IVOA's table access protocol (TAP) provides tabular metadata to astronomers via a standard interface. The most common use of the TAP service is within a VO client, such as TOPCAT or pyvo. For more background information on the IVOA and using VO protocols, please see IVOA: Information for Astronomers.
The TAP service URL is:
Using TOPCAT to access the MWA TAP Service
- Download and install the freely available TOPCAT.
- Start TOPCAT. On most systems this just involves double clicking the topcate JAR file.
- Select VO→Table Access Protocol (TAP) Query from the main menu.
- Copy and paste or type the following into TAP URL in the Selected TAP Service section
- Click Use Service
- You should now be taken to a new window which contains a list of available tables on the left and an ADQL Text box in the lower section.
- At this point you can type in ADQL queries and click Run Query to execute and return data.
- Each time you run a query a new entry will appear in another window TOPCAT creates.
- You can then view the data returned (use the View→Table Data menu option) or produce plots, etc via the Graphics menu.
- This is intended to be a quick start guide for using TOPCAT. It is a very powerful tool and you should review TOPCAT's full documentation to get the most out of it.
Using PyVO to access the MWA TAP Service
PyVO is a library that is affiliated with astropy which allows astronomers to programmatically access VO services via Python. You can access MWA metadata very easily using this method.
- Install PyVO
- Then, using import pyvo, you can execute ADQL queries against MWA's TAP service.
Using ADQL to Write TAP Queries
The Astronomical Data Query Language (ADQL) an SQL-like language used by astronomers to interact with TAP services. The full specification is available here: http://www.ivoa.net/documents/ADQL, however if you have a little or no familiarity with SQL you can get started writing queries in ADQL.
Please also see the following excellent resources to help you learn ADQL syntax:
Available MWA TAP Tables
The ivoa.obscore table is a common table implemented by most TAP services to allow TAP client applications access any TAP service in a standard way. Due to the fact it is designed to cover most possible astronomical datasets, obscore provides only limited metadata for MWA observations. However, obscore does provide basic temporal and spatial data for each MWA observation which can be useful for cross-matching with other datasets. For more MWA-specific metadata, please see the tables in the "mwa" schema (below).
This is a custom table which stores one record per MWA observation. An MWA observation can include correlator observations, voltage captures, mode changes, and "no capture" events and can be thought of as a record of the configuration of the telescope the time of the observation.
This is a custom table which stores a summary of the size and number of files of each type for an observation. Data files include raw correlator visibilities (aka gpubox files), raw voltages, incoherent sums, flag files, etc. Each data file is related to an MWA observation via the "obs_id" field which is in both the ivoa.obscore and mwa.observation tables.
Simple Cone Search (SCS)
The MWA ASVO also provide an implementation of the simple cone search protocol. This is a quick search tool which will perform a coordindate search based on an RA, Dec and radius and provide a list of observations which match the criteria.
The cone search url is: http://vo.mwatelescope.org/mwa_asvo/scs/obscore/
The most common use of the SCS is within a VO client, such as TOPCAT.