DR2 Neighbourhood (gaiadr3.dr2_neighbourhood)
The table has 2113600501 rows, 5 columns.
Users wishing to look up the E/DR3 record for an astrophysical source identified in DR2 must NOT simply extract the record from E/DR3 having the same source identifier.As described in the detailed description of attribute designation in GaiaSource it is not guaranteed that the same astronomical source will always have the same source identifier in different Data Releases. Hence the only safe way to compare source records between different Data Releases in general is to check the records of proximal source(s) in the same small part of the sky. This table provides the means to do this via a precomputed crossmatch of such sources, taking into account the proper motions available at E/DR3.Within the neighbourhood of a given E/DR3 source there may be none, one or (rarely) several possible counterparts in DR2 indicated by rows in this table. This occasional source confusion is an inevitable consequence of the merging, splitting and deletion of identifiers introduced in previous releases during the DR3 processing and results in no guaranteed one–to–one correspondence in source identifiers between the releases.For more details of the procedure used to create this crossmatch, see Chapter [chap:archive] in the online documentation.
If you have used Gaia data in your research, please use the following acknowledgement:
This work has made use of data from the European Space Agency (ESA) mission Gaia (https://www.cosmos.esa.int/gaia), processed by the Gaia Data Processing and Analysis Consortium (DPAC, https://www.cosmos.esa.int/web/gaia/dpac/consortium). Funding for the DPAC has been provided by national institutions, in particular the institutions participating in the Gaia Multilateral Agreement.
More information can be found on the credit and citation instructions page.
Source identifier in Gaia DR2
Source identifier in Gaia E/DR3
Angular distance between the two sources
G band magnitude difference between the sources
Flag indicating whether E/DR3 coordinates were proper motion corrected