FAQ on GAia Data Access
When using the Gaia Archive, you might not be aware of some essential information that could help you to use the Gaia Archive more effectively. Also, you might encounter an issue that is easily solvable by yourself. Here you can find this type of information. When things are still unclear, we welcome you to raise your question at the Gaia Helpdesk.
Upcoming upgrades to the Gaia Archive
Our Gaia Archive team is continuously working towards making the Gaia Archive more efficient and easy to use. New releases of the Gaia Archive come out every now and then. Here you can find information on the current and previous releases. The first upcoming release and the expected new features or fixes are described below.
Release version 2.4.0: release date still unknown
- New ADQL feature: OFFSET will become availabe in Gaia Archive version 2.4.0
First aid solution to Access issues
Planned maintenance to the Gaia Archive is announced through Gaia Cosmos. If you cannot access the Gaia Archive, and the unavailability of the Gaia Archive is not announced there, please contact us through the Gaia Helpdesk.
The first aid solution to most issues with the Gaia Archive (from seemingly disappeared tables or strange behaviour after a query or problems signing in or out), is to close your browser, clear your cache and then retry. In most cases, there is no issue really and things are working the way they should and you will be able to continue working in no time.
A second solution might be to switch browsers. Some browser show more hickups than others in combination with the use of the Gaia Archive.
First aid solution to exceeded file quota
Assumed is that you entered the Gaia Archive with a registered account. A registered account has the benefits of a dedicated user space with more space and larger quota. If you get an error message that you have exceeded your file quota, but you did not according to the information in your account, first check if you have jobs that failed to complete. You could see whether deleting the jobs that failed solve the issue. Even though they seem to take up no space (0 bytes), sometimes they do and deleting them will free up space.
Another quick test to try and see if you can solve the exceeded file quota yourself, is to clear your cache (so close your browser and start a new private window) and then check again.
First aid solution to questions
Perform a search on the internet with your question. You probably find that the answer to your question is already around on one of the Gaia information pages. Maybe you can find the answer as one of the FAQ on Gaia data access below, or there might be an answer available already from the Gaia FAQ (answering questions on the Gaia Mission and Data Releases).
Please also have a look at the Gaia Archive help pages which contains lots of helpful information and tutorials or perform a search through the Gaia Data Release Documentation and the Gaia Data Release papers (for DR1, for DR2). The question might have been raised on the Gaia Community Forum or hidden in the information on some other Gaia Cosmos page or Gaia pages of our DPAC partners. When not sure what information is around for a certain data release, check out the overview pages for each release: Gaia Data Release 1 and Gaia Data Release 2.
For all questions on the Gaia Archive, use of the Gaia Archive, content of the Gaia Archive and more, feel free to contact the Gaia Helpdesk.
The Gaia Archive data model (column description, units, etc.) along with the extensive documentation of the data and its processing can be found here, with the opportunity to download the full data release documentation.
The headers of FITS files of Gaia Data Release 1 as served from the Gaia Archive indeed contain constructs like TUNIT16 = 'Angular Velocity[mas/year]' which are not compliant with FITS standard 3.0. This was corrected for Data Release 2 (DR2). Gaia DR1 users can continue using the FITS files: their data contents are correct while the non-compliances in the headers may give warning messages (but not errors).
This is the unavoidable consequence of using the Initial Gaia Source List (IGSL) for bootstrapping the cross-match procedures for Gaia Data Release 1. The IGSL is a collection of multiple, incomplete pre-Gaia catalogues, known to contain spurious and duplicate sources. To avoid dropping Hipparcos stars in the IGSL, those entries not matched were added as a "fake" Tycho-2 star with Tycho-2 identifier idTYCHO = 9999999000000+idHIP. Because of a bug in the matching procedures, approximately 12000 Hipparcos stars have been entered twice. These can be identified as objects with auxHIP = 1 and idTYCHO > 9999999000000 and should not be used.
This table provides a link between the HEALPix identifier (level 6, so Nside = 26 = 64) and equatorial, Galactic, and ecliptic coordinates. The text file has four header lines and 49152 data lines, each with eight columns separated by commas:
- HEALPix identifier [ring scheme, Gaia default]
- HEALPix identifier [nest scheme]
- Right ascension [deg]
- Declination [deg]
- Galactic Longitude [deg]
- Galactic Latitude [deg]
- Ecliptic Longitude [deg]
- Ecliptic Latitude [deg]
When using the TAP service for queries in anonymous mode, these limits indeed exist (as documented here). Users can, however, self-register through the "SIGN IN" button in the top-righter corner of the Archive, after which the reported user quota apply. Upon demonstrated need, users can request (temporary) changes to their quota by sending a motivated request to the Gaia Helpdesk.
There may be several reasons for this. First of all the SAMP hub must be up and running. For instance, if TOPCAT is being used a SAMP hub is automatically started.
Then there is a known limitation of current SAMP standard related to the use of HTTPS connections. Current implementations of SAMP hubs does not support HTTPS connections. If you are using the Gaia Archive in HTTPS mode this can be the cause of the inability to connect to the SAMP hub. There are two possible workarounds for this.
First workaround: allow your browser to connect to insecure content. This will allow connections to the SAMP hub using HTTP from your secure Gaia Archive application.
Second workaround: use the Gaia Archive HTTP version. Be aware though that the latter implies a security risk as the communication between your browser and the Gaia Archive server is not being encrypted!
These stars might be too bright for Gaia. They would saturate the sensitive CCD detectors on-board of Gaia. The brightest object included in Gaia DR1 has a G magnitude (phot_g_mean_mag) of 3.155 but there is no complete data at that magnitude until at least G = 5. For Gaia DR2 the bright limit is G ≈ 3. So practically, no star visible to the naked eye made it into Gaia DR1. More information on this topic can be found in the Gaia Data Release documentation or more specifically here.
A five-parameter astrometric solution, including proper motions and parallaxes, has only been computed for the TGAS sub-sample comprising circa 2 million objects for Gaia Data Release 1 and for a sub-sample of about 1,3 billion sources of the total of about 1,7 sources in Gaia Data Release 2. More information can be found here.
Negative parallaxes are caused by errors in the observations. Even if a negative distance has no physical meaning, there are a certain number of stars expected to have negative parallaxes just from an error propagation perspective. The negative parallax tail is a very useful diagnostic on the quality of the astrometric solution. Further details can be found here and here.
A tutorial is available that explains the steps to take to upload your list of targets to the Gaia Archive and then extract Gaia data for this list of targets. Please follow the White Dwarfs Exploration tutorial that can be found here.
The file to be uploaded to the "simple form" of the Gaia Archive online search tool requires a specific format. The description of the format can be found by hoovering the mouse over the "Select a file with Target Names" and clicking once the question mark appears. Only files with sources specified through their SIMBAD or NED resolved names will work for the "simple form file upload". The current situation where the option "equatorial" can be selected within the tab "file" is a bit confusing.
For a search based on coordinates, please access the Gaia Archive through the "ADQL form". Tutorials are available in the Help tab to demonstrate access through the "ADQL form". Especially the "White dwarfs exploration" tutorial is helpful for learning how to upload tables to the Gaia Archive and use them for a search.
More frequently asked questions on the Gaia Mission and Gaia Data Releases can be found here.