VizieR

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

VizieR

Looking for catalogs ..
Show the target form
Show constraint information
The 3 columns in color are computed by VizieR, and are not part of the original data.

Note: This version of the GSC-II has no proper motions, but the limits on brightness which existed on GSC2.2 (F<18.5, Bj<19.5) were removed.

I/305/out The Guide Star Catalog, Version 2.3.2 (GSC2.3) (STScI, 2006)
ReadMe+ftp
2008AJ....136..735L

The Full GSC2.3.2 Catalogue (945592683 objects) (945592683 rows)		img(gal)

start AladinLite
Full
_r
arcsec
 _RAJ2000
"h:m:s"
 _DEJ2000
"d:m:s"
GSC2.3
RAJ2000
deg
DEJ2000
deg
Epoch
yr
Fmag
mag
jmag
mag
Vmag
mag
Nmag
mag
Class
a
pix
e
1 0.45921 25 09.43752-22 49 26.0796SC6D010577321.289323-22.8239111994.65220.95      3 1.53 0.27
Problematic Query

The following unexpected problem occured in VizieR:

Report:

If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR4060063.err (2026-04-19T14:02:28)
-4
-out.add=_r
-out.add=_RAJ,_DEJ
-sort=_r
-out.max=20
-c=321.289458-22.823939
-c.rs=10
-ref=VIZ69e4e0743df39f

Detailed errors:

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_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_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_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
elapse time 4