VizieR

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

VizieR


Simple TargetList Of TargetsFast Xmatch with large catalogs or Simbad
Target Name (resolved by Sesame) or Position:
Target dimension:
NB: The epoch used for the query is the original epoch of the table(s)Radius Box size

  
J/ApJ/703/1323
  Spectroscopy of stars in the Galaxy's nuclear cluster (Do+ 2009)
Post annotation
img(gal)
1.J/ApJ/703/1323/table4OSIRIS spectra with unknown spectral type (54 rows)

 
Query by Constraints constraints help applied on Columns (Output Order: + - )
ShowSortColumn  Constraint Explain   (UCD)
  recno  Record number assigned by the VizieR team. Should Not be used for identification. (meta.record)
  Name (char) Star identification (SN-NNN) (meta.id;meta.main)
  K'mag mag KeckII/OSIRIS K'-band magnitude (∼2.2um) (phot.mag;em.IR.K)
  RAoff arcsec Offset in right ascension from Sgr A* (pos.eq.ra)
  DEoff arcsec Offset in declination from Sgr A* (pos.eq.dec)
  Rad arcsec Projected distance from Sgr A* in the plane of the sky (pos.angDistance)
  Epoch yr Epoch in decimal years (time.epoch)
  S/N  Signal to noise per pixel calculated between 2.212 and 2.218um. (stat.snr)
  R07  (n)Link to objects within 0.5" in Rafelski et al. 2007, Cat. J/ApJ/659/1241 when available (meta.ref.url)
  Simbad  ask the Simbad data-base about this object
  _RA deg (i) Position, computed from Sgr A* position (17:45:40.041-29:00:28.12) with offsets (right ascension part) (pos.eq.ra;meta.main)
  _DE deg (i) Position, computed from Sgr A* position (17:45:40.041-29:00:28.12) with offsets (declination part) (pos.eq.dec;meta.main)

ALL cols
    
(n) indicates a possible blank or NULL column(i)indexed column
Adapt form
Display your selection only Reset to default columns
usage  Display UCD1+    UCD1  


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_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
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR683541.err (2025-07-13T00:42:15)
-3
-source=J/ApJ/703/1323/table4
-ref=VIZ687300e7a6e15
elapse time 1