VizieR

CfA VizieR . ADAC VizieR . Cambridge (UK) VizieR . IUCAA VizieR . INASAN VizieR .

VizieR

Looking for catalogs ..
Show the target form
Show constraint information
Show constraint information
The 8 columns in color are computed by VizieR, and are not part of the original data (note that the computed coordinates are computed from the positions and the proper motions given in the table)
I/311/hip2
Post annotation 		Hipparcos, the New Reduction (van Leeuwen, 2007)
ReadMe+ftp
2007A&A...474..653V

The Astrometric Catalogue (117955 rows)		img(gal)
Full
_RAJ2000
"h:m:s"
 _DEJ2000
"d:m:s"
 _RAB1950
"h:m:s"
 _DEB1950
"d:m:s"
 _Glon
deg
 _Glat
deg
HIP
n_
Sn
So
RArad
deg
DErad
deg
Plx
mas
e_
mas
pmRA
mas/yr
pmDE
mas/yr
Hpmag
mag
B-V
mag
 HIP1
118 21 03.3825495+72 43 58.25179218 21 57.4919924+72 42 41.985071103.4572652252+28.0583694464 89937   754275.25974417+72.73369776 124.11 0.87 531.21 -349.71 3.6666 0.489HIP1
Show constraint information

Note: Errors found in the Hipparcos catalogue are reported in the file errata.htx

I/239/hip_main
Post annotation 		The Hipparcos and Tycho Catalogues (ESA 1997)
ReadMe+ftp
1997HIP...C......0E

The Hipparcos Main Catalogue
timeSerie
(118218 rows)		img(gal)
Full
_RAJ2000
"h:m:s"
 _DEJ2000
"d:m:s"
 _RAB1950
"h:m:s"
 _DEB1950
"d:m:s"
 _Glon
deg
 _Glat
deg
HIP
RAhms
DEdms
Vmag
mag
RAICRS
deg
DEICRS
deg
Plx
mas
pmRA
mas/yr
pmDE
mas/yr
e_Plx
mas
B-V
mag
Notes
_RA.icrs
deg
_DE.icrs
deg
118 21 03.3826653+72 43 58.23488718 21 57.4938418+72 42 42.062044103.4572650955+28.0583689839 8993718 21 02.34+72 44 01.3 3.55275.25974572+72.73369763 124.11 531.08 -351.59 0.48 0.489  275.26409444+72.73284302

The following problems were encountered in this VizieR run:
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR2426519.err (2024-05-01T06:01:20)
-4
elapse time 1