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/A+AS/128/485
  Library of UES spectra late-type stars (Montes+ 1998)
ReadMe+ftp
1998A&AS..128..485M
Similar Catalogs
Post annotation 		img(gal)
1.J/A+AS/128/485/table6List of stars, Spectral type and name of the corresponding FITS spectra (105 rows)

Simple ConstraintList Of Constraints
 
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)
  HD (char) HD number (meta.id)
  HR (char) HR number (meta.id)
  Name (char) name of the star (meta.id)
  SpType (char) Spectral type (src.spType)
  Spectra (char) Original name of FITS file (Note 1)   (meta.fits)
  fitsFile (char) Name of file found in subdirectory spectra (Note 1)   (meta.id;meta.file)
  RA2000 "h:m:s" (i) Right Ascension 2000 (hours) (Note 2)   (pos.eq.ra;meta.main)
  DE2000 "d:m:s" (i) Declination 2000 (sign) (Note 2)   (pos.eq.dec;meta.main)

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

.errorfile=/tmp/VR4090371.err (2026-01-14T13:42:06)
-3
-source=J/A+AS/128/485/table6
-ref=VIZ69679d2e3e6a03
elapse time 2