On this page...
Basic searches involve two steps:
- select a collection
- input a valid search criterion
Valid search inputs are either the target name of an astronomical object, or the target coordinates, e.g., Right Ascension (RA) and Declination (Dec). The search box takes specific formatting for target names or coordinates. See the tables within each section below for allowed formatting to ensure correct syntax for proper searches. The search can be initiated by clicking the Search button or by pressing the Enter key on your keyboard while the cursor is in the input search box.
The basic search form. Select a collection from the pull-down menu (left), enter a target name or target coordinates (right), then click Search.
Selecting Collections
Users can choose which collection of data they wish to perform a search in. Most, but not all, collections allow for basic searching by target name or coordinate. The default collection to search is all MAST Observations. Unless you wish to search within a specific dataset, it is recommended to leave the default set as is. For more information on searching with the other collections, see sections Catalog Search and Special Searches.
Collection | Description | Allows Basic Search |
---|---|---|
MAST Observations | The combined observations from all MAST collections. These include HST, JWST, Kepler, GALEX, EUVE, FUSE, IUE, SWIFT, and several other missions. | yes |
Virtual Observatory (VO) | A worldwide collection of repositories providing astronomical images, catalogs and spectra. | yes |
Hubble Source Catalog (HSC) | A catalog of tens of millions of sources from the Hubble Legacy Archive (HLA), derived from HST imaging in multiple instruments and passbands. | yes |
Hubble Source Catalog Spectra | A collection of spectra associated with sources in the HSC. | no |
Hubble Spectroscopic Legacy Archive (HSLA) | A collection of spectra housed in the Hubble Legacy Archive. | no |
MAST Catalogs | MAST-held collections of source lists, e.g. GAIA, TESS input (TIC) catalogs. | yes |
Hubble Wide-Field Camera PSF | Libraries of observed, reference point-sources for higher-precision photometry and astrometry. | no |
Observations in a DOI | Search for MAST data associated with a Digital Object Identifier. | yes |
JWST Instrument Keywords | Search for JWST data by instrument that match a selection of header keyword values. | no |
JWST WSS | Search for JWST Wavefront products. | no |
Choosing a Target...
...by Name
Users can search for data by inputting the astronomical name of a target object on the sky. Names of objects are passed to a NED or SIMBAD name resolver, which associates known object names with sky coordinates. A wide variety of catalog and common names can be resolved to known objects.
Allowed Format
Allowed formats for target names are the following:
Example | Description |
---|---|
M101, NGC45 | Objects from standard catalogs such as Messier and NGC will be resolved |
Antennae, Eta Carinae | Common names often work |
T Tau | Variable star names often work |
BD+19 706 | Star catalogs with coordinate symbols |
png 000.8-07.6 | Other catalogs with coordinate and decimal symbols |
2MASS J04215943+1932063 | All-sky catalogs with coordinate symbols |
TYC 1272-470-1 | All-sky satellite catalogs with restricted symbols |
...by Coordinates
Users can search for data by providing a target on-sky coordinate of Right Ascension (RA) and Declination (Dec). Coordinates can be given in a variety of formats. Right ascensions must be positive and southern declinations require a leading negative sign. A cone search is performed around the input coordinate at a default radius of 0.2 degrees.
Specify the Search Radius
A custom search radius can be specified by appending to the coordinates r=[
number][
unit]
, where number is any valid decimal number and unit is one of "d" (degrees), "m" (arc-minutes), "s" (arc-seconds). The default cone search depends on the size of the object but is usually 0.2 degrees for most targets. Note that some collections have search radius limitations. See the table below for examples of various custom search radius inputs.
Example | Description |
---|---|
14:03.210 54:20.945 r=0.5 | Coordinate search with radius of 0.5° |
14:03.210 54:20.945 r=1d | Coordinate search with radius of 1° |
14:03.210 54:20.945 r=1.2m | Coordinate search with radius of 1.2 arc-minutes |
Allowed Format
Coordinates can be input either as decimal degrees, sexagesimal or galactic coordinates, with various formatting. Allowed formats for target coordinates are the following:
Example | Description |
---|---|
14 03 12.6 54 20 56.7 | Sexagesimal coordinates delimited with spaces |
14:03.210 54:20.945 | Sexagesimal coordinates delimited with colons; decimal minutes/arcminutes |
14h03m12.6s +54d20m56.7s | Sexagesimal coordinates with explicit hms/dms |
g102.0373+59.7711 | Galactic coordinates of the form:
with no spaces |
180.468 -18.866 | Coordinates in decimal degrees |
...by Observation ID
Most MAST missions assign a unique identifier to individual observations. When selecting the collection MAST Observations by Observation ID, the input search box changes to accept only valid mission observation IDs, rather than target names or coordinates, as input. This collection option is for use cases when you know exactly the mission observation you wish to search for. A single observation ID is valid input, as well as a comma-separated list of IDs.
Example | Description |
---|---|
tess-s0015-4-1 | Search for a single TESS observation |
tess-s0015-4-1, n4ro01020 | Search for multiple observations by id: a TESS and HST observation |
Notes on Searching
When formulating a search, note the following:
- Leading zeros are ignored in the name. For example,
M5
returns results for object Messier 005. - Object names are not case-sensitive, and spaces between the characters (e.g.
M51
andM 51
) are ignored unless the space is significant in the name. - All coordinates are interpreted as J2000.
- The maximum allowed search radius is limited on a collection-by-collection basis.
- The results of a search of Virtual Observatory collections may have arbitrary limits on the number of rows returned, on a resource-by-resource basis (i.e., limits which may imposed by the collection provider).
- Most queries are limited to a single object or position, except for searches by observation ID. However, multiple queries may be submitted sequentially, even if one or more queries are still executing.