Catalog

JavaScript is used, and should be enabled to get full functionality.

Looking for catalogs ..

The VizieR service is now hosted by CDS domain (cds.unistra.fr). Please, modify your configuration for the new domain.

6 catalogs found


	2384 II/384	-1	^(c) 14M 14650348	KiDS-450: Weak lensing shear measurements (Hildebrandt+, 2017) ReadMe+ftp 2017MNRAS.465.1454H	0
	17490065 J/ApJ/749/65	1565	^(c) 64 64	H-ATLAS search for strongly lensed galaxies (Gonzalez-Nuevo+, 2012) ReadMe+ftp 2012ApJ...749...65G	0
	17770097 J/ApJ/777/97	1334	^(c) 0	SL2S galaxy-scale lens sample. III. (Sonnenfeld+, 2013) ReadMe+ftp 2013ApJ...777...97S	0
	18940078 J/ApJ/894/78	-1	^(c) 342 342	Strong gravitational lenses from DECaLS (Huang+, 2020) ReadMe+ftp 2020ApJ...894...78H	0
	22590027 J/ApJS/259/27	-1	^(c) 904 904	DES Bright Arcs Survey: strong lens systems (O'Donnell+, 2022) ReadMe+ftp 2022ApJS..259...27O	0
	74674220 J/MNRAS/467/4220	-1	^(c) 272 272	Galaxies inside 120 arcsec of HE 0435-1223 (Rusu+, 2017) ReadMe+ftp 2017MNRAS.467.4220R	0
ALL				or
			^(c) indicates tables which contain celestial coordinates

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_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
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- 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

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

.errorfile=/tmp/VR586967.err (2026-02-02T22:33:59)
-2
-kw.cat=22590027
-ref=VIZ698126578f4d7

elapse time 1