VizieR

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

Catalog

Looking for catalogs ..
The VizieR service is now hosted by CDS domain (cds.unistra.fr). Please, modify your configuration for the new domain.
4 catalogs found
  
J/ApJ/698/2048
  Abundances of red giants in {omega} Cen (Johnson+, 2009)
img(gal)
    J/ApJ/698/2048/stars(c)Photometry, membership, atmospheric parameters, and abundances of the 66 giants (tables 1 and 3 of paper) (66 rows)
    J/ApJ/698/2048/ewEquivalent Widths (5676 rows)
  
J/ApJ/836/168
  Abundances & RVs for stars near (or in) NGC6273 (Johnson+, 2017)
  
  
J/A+A/563/A76
  CaII triplet equivalent widths in 30 globulars (Mauro+, 2014)
img(gal)
    J/A+A/563/A76/table1(c)List of reddest parts of the Horizontal Branch (RHB) levels in the 30 glubular clusters (30 rows)
    J/A+A/563/A76/table8(c)Equivalent widths of the Ca-II triplet ({lambda}~850nm) (443 rows)
  
J/AJ/155/71
  RGB & HB members of the bulge cluster NGC 6569 (Johnson+, 2018)
img(gal)
    J/AJ/155/71/table2(c)M2FS Star Identifiers, Coordinates, Photometry, and Velocities (85 rows)
    J/AJ/155/71/table3(c)FLAMES Star Identifiers, Coordinates, Photometry, and Velocities (788 rows)
    J/AJ/155/71/M2FSM2FS RGB Cluster Member Model Atmosphere Parameters (table 4), Abundance Ratios and Uncertainties: Oxygen to Calcium (table 5) and Chromium to Europium (table 6) (19 rows)
    J/AJ/155/71/table7FLAMES RGB and HB Calcium Triplet Metallicity Data for Cluster Members (106 rows)

ALL
     
       (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/VR230294.err (2025-12-06T12:50:06)
-2
-kw.cat=35630076
-ref=VIZ6934267e38396
elapse time 1