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


	17929002 J/ApJ/792/L2	1410	^(c) 6 6	C/2012 F6 (Lemmon) and C/2012 S1 (ISON) maps (Cordiner+, 2014) /fits ReadMe+ftp 2014ApJ...792L...2C image/fits	0
	36480049 J/A+A/648/A49	1617	^(c) 0	Comet 46P/Wirtanen millimetre-wave spectra (Biver+, 2021) ReadMe+ftp 2021A&A...648A..49B	0
	36510025 J/A+A/651/A25	935	^(c) 0	4 short-period comets spectra (Biver+, 2021) /fits ReadMe+ftp 2021A&A...651A..25B spectrum/fits	0
	36680171 J/A+A/668/A171	939	^(c) 29 29	Comet C/2020 F3 (NEOWISE) IRAM and NOEMA spectra (Biver+, 2022) ReadMe+ftp 2022A&A...668A.171B spectrum/fits	0
	36720170 J/A+A/672/A170	1380	^(c) 13 13	Comet 67P/Churyumov-Gerasimenko radio spectra (Biver+, 2023) /fits ReadMe+ftp 2023A&A...672A.170B spectrum/fits	0
	36900271 J/A+A/690/A271	544	^(c) 34 34	Comets C/2021 A1 and C/2022 E3 (ZTF) spectra (Biver+, 2024) ReadMe+ftp 2024A&A...690A.271B timeSerie	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
**** 
**** -- 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

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

.errorfile=/tmp/VR1110249.err (2026-01-14T11:43:58)
-2
-kw.cat=36480049
-ref=VIZ6967817e10f0e9

elapse time 2