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.

7 catalogs found


	17110928 J/ApJ/711/928	27218 (density 7)	^(c) 438 438	Low-redshift Ly{alpha} galaxies from GALEX (Cowie+, 2010) ReadMe+ftp 2010ApJ...711..928C	7
	17830119 J/ApJ/783/119	32742 (density 7)	^(c) 0	z~1 Ly{alpha} emitters. I. 135 candidates from GALEX (Wold+, 2014) ReadMe+ftp 2014ApJ...783..119W	7
	18690123 J/ApJ/869/123	1196 (density 7)	^(c) 139 139	Keck Lyman continuum spectroscopic survey (KLCS) (Steidel+, 2018) ReadMe+ftp 2018ApJ...869..123S	7
	22370011 J/ApJS/237/11	6860 (density 7)	^(c) 9k 9174	Gal. redshift survey near HST/COS AGN sight lines (Keeney+, 2018) ReadMe+ftp 2018ApJS..237...11K	7
	22650021 J/ApJS/265/21	175044 (density 7)	^(c) 952k 952138	The Coronal Line Activity Spectroscopic Survey cat. (Reefe+, 2023) ReadMe+ftp 2023ApJS..265...21R spectrum	7
	51590167 J/AJ/159/167	4710 (density 7)	^(c) 701 701	AMUSING++ nearby galaxy compilation. I. Sample (Lopez-Coba+, 2020) ReadMe+ftp 2020AJ....159..167L	7
	18530095 J/ApJ/853/95	2975	^(c) 163 163	Galaxies probing galaxies in PRIMUS. I. (Rubin+, 2018) ReadMe+ftp 2018ApJ...853...95R	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_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
**** 
**** -- 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/VR635543.err (2026-01-28T15:27:32)
-2
-kw.cat=18530095
-ref=VIZ697a2ae49b297

elapse time 3