XAO Data Center TAP serviceXAO TAPivo://xaovo/tapXinjiang Astronomical Observatory,CASZhang Hailonghttps://data.xao.ac.cn/favicon.png2025-09-23T11:09:07ZZhang Hailong150 Science 1-Street, Urumqi, Xinjiang 830011, Chinazhanghailong@xao.ac.cn+86 18699134012virtual-observatoriescatalogsThe XAO Data Center's TAP end point. The Table Access
Protocol (TAP) lets you execute queries against our database tables,
inspect various metadata, and upload your own data. It is thus the
VO's premier way to access public data holdings.
Tables exposed through this endpoint include: agn from the agn schema, fast_pul from the fast_pul schema, dr3lite, edr3lite from the gaia schema, notf from the gallery schema, columns, services, tables from the glots schema, nowt from the nowt schema, data from the obscode schema, main from the ppmxl schema, data from the pulsarcatalog schema, pulsar from the pulsar schema, sf from the sf schema, main from the spm4 schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, data from the ucd schema.https://data.xao.ac.cn/__system__/tap/run/infoIsServiceForGaia DR3 source catalogue "light"GloTS, the Global TAP SchemaXAO Data Center Obscore Tablehttps://data.xao.ac.cn/taphttp://data.xao.ac.cn/tapGloTS 1.0ADQL2.02.1The Astronomical Data Query Language is the standard IVOA dialect of SQL; it contains a very general SELECT statement as well as some extensions for spherical geometry and higher mathematics.Returns a POINT (in the UNDEFINED reference frame) for the position
an object at ra/dec with proper motion pmra/pmde has after epdist years.
positions must be in degrees, PMs in should be in julian years (i.e., proper
motions are expected in degrees/year). pmra is assumed to contain
cos(delta).
This function goes through the tangential plane. Since it does not have
information on distance and radial velocity, it cannot reconstruct
the true space motion, and hence its results will degrade over time.
This function should not be used in new queries; use ivo_epoch_prop
instead.returns the authority part of an ivoid (or, more generally a URI).
So, ivo://org.gavo.dc/foo/bar#baz becomes org.gavo.dc.
The behaviour for anything that's not a full URI is undefined.gavo_ipix returns the q3c ipix for a long/lat pair (it simply wraps
the 13c_ang2ipix function).
This is probably only relevant when you play tricks with indices or
PPMXL ids.gavo_match returns 1 if the POSIX regular expression pattern
matches anything in string, 0 otherwise.returns the intersection of two MOCs.returns the union of two MOCs.returns the spectral value expr converted to dest_unit.
expr has to be in either energy, wavelength, or frequency, and dest_unit
must be a VOUnit giving another spectral unit (e.g., MHz, keV, nm, or
Angstrom). This is intended to let users express spectral constraints
in their preferred unit independently of the choice of unit in the
database. Examples::
gavo_specconv(obscore.em_min, "keV") > 300
gavo_specconv(obscore.em_max, "MHz") > 30
gavo_specconv(spectral_start, "Angstrom") > 4000
There is a variant of gavo_specconv accepting expr's unit in a third
argument.returns expr assumed to be in expr_unit expressed in dest_unit.
This is a variant of the two-argument gavo_specconv for when
the unit of expr is not known to the ADQL translator, either because
it because it is a literal or because it does not look like
a spectral unit. Examples::
gavo_specconv(656, 'nm', 'J') BETWEEN spectral_start AND spectral_end
gavo_specconv(arccos(phi)*incidence, 'Hz', 'eV')
Clearly, overriding known units is likely to yield bad results;
the translator therefore warns if an existing unit is overridden
with a different unit.returns 1 if matchagainst is term or narrower in the IVOA vocabulary
vocname, 0 otherwise.
This is intended for semantic querying. For instance,
gavo_vocmatch('datalink/core', 'calibration', semantics) would be 1
if semantics is any of calibration, bias, dark, or flat.
For RDF-flavoured vocabularies (strict trees), term will expand to the
entire branch rooted in term. For SKOS-flavoured vocabularies (where
narrower is not transitive), only directly narrower terms will be included.
Both the term and the vocabulary name must be string literals (i.e.,
constants). matchagainst can be any string-valued expression.Returns a 6-vector of (ra, dec, parallax, pmra, pmdec, rv)
at out_epoch for these quantities at ref_epoch.
Essentially, it will apply the proper motion under the assumption of
linear motion. Despite the name of the positional parameters, this is
not restricted to equatorial systems, as long as positions and proper
motions are expressed in the same reference frames.
Units on input and output are degrees for ra and dec, mas for parallax,
mas/yr for pmra and pmdec, and km/s for the radial velocity.
ref_epoch and out_epoch are given in Julian years.
parallax, pmra, pmdec, and radial_velocity may be None and will enter
the computations as 0 then, except in the case of parallax, which
will be some small value. When abs(parallax) is smaller or equal
to that small value, parallax and radial velocity will be NULL on
output.
In daily use, you probably want to use the ivo_epoch_prop_pos functions.Returns a POINT giving the position at out_epoch for an object
with the six parameters at ref_epoch.
Essentially, it will apply the proper motion under the assumption of
linear motion. Despite the name of the positional parameters, this is
not restricted to equatorial systems, as long as positions and proper
motions are expressed in the same reference frames.
Units on input are degrees for ra and dec, mas for parallax,
mas/yr for pmra and pmdec, and km/s for the radial velocity.
ref_epoch and out_epoch are given in Julian years.
parallax, pmra, pmdec, and radial_velocity may be None and will enter
the computations as 0 then, except in the case of parallax, which
will be some small value.A variant of ivo_epoch_prop_pos that behave as if parallax
and radial_velocity were both passed as NULL.The function transforms ADQL geometries between various reference systems.
geo can be a POINT, a CIRCLE, or a POLYGON, and the function will return a
geometry of the same type. In the current implementation, from_sys and
to_sys must be literal strings (i.e., they cannot be computed through
expressions or be taken from database columns).
All transforms are just simple rotations, which is only a rough
approximation to the actual relationships between reference systems
(in particular between FK4 and ICRS-based ones). Note that, in particular,
the epoch is not changed (i.e., no proper motions are applied).
We currently support the following reference frames: ICRS, FK5 (which
is treated as ICRS), FK4 (for B1950. without epoch-dependent corrections),
GALACTIC. Reference frame names are case-sensitive.The function takes two strings; the first is a list of words not
containing the hash sign (#), concatenated by hash signs, the second is
a word not containing the hash sign. It returns 1 if, compared
case-insensitively, the second argument is in the list of words coded in
the first argument. The behaviour in case the the second
argument contains a hash sign is unspecified.gavo_hasword returns 1 if needle shows up in haystack, 0 otherwise. This
is for "google-like"-searches in text-like fields. In word, you can
actually employ a fairly complex query language; see
https://www.postgresql.org/docs/current/textsearch.html
for details.returns a POINT corresponding to the center of the healpix with
the given index at the given order.Returns the index of the (nest) healpix with order containing the
spherical point (ra, dec).
An alternative, 2-argument form
ivo_healpix_index(order INTEGER, p POINT) -> BIGINT
is also available.The aggregate function returns a histogram of val with nbins+2 elements.
Assuming 0-based arrays, result[0] contains the number of underflows (i.e.,
val<lower), result[nbins+1] the number of overflows. Elements 1..nbins
are the counts in nbins bins of width (upper-lower)/nbins. Clients
will have to convert back to physical units using some external
communication, there currently is no (meta-) data as lower and upper in
the TAP response.The function returns 1 if the interval iv contains val, 0 otherwise.
The lower limit is always included in iv, behaviour on the upper
limit is column-specific.The function returns 1 if the interval [l1...h1] overlaps with
the interval [l2...h2]. For the purposes of this function,
the case l1=h2 or l2=h1 is treated as overlap. The function
returns 0 for non-overlapping intervals.ivo_nocasematch returns 1 if pattern matches value, 0 otherwise.
pattern is defined as for the SQL LIKE operator, but the
match is performed case-insensitively. This function in effect
provides a surrogate for the ILIKE SQL operator that is missing from
ADQL.
On this site, this is actually implemented using python's and SQL's
LOWER, so for everything except ASCII, your mileage will vary.The function returns a random number drawn from a normal distribution
with mean mu and width sigma.
Implementation note: Right now, the Gaussian is approximated by
summing up and scaling ten calls to random. This, hence, is not
very precise or fast. It might work for some use cases, and we
will provide a better implementation if this proves inadequate.gavo_simbadpoint queries simbad for an identifier and returns the
corresponding point. Note that identifier can only be a literal,
i.e., as simple string rather than a column name. This is because
our database cannot query simbad, and we probably wouldn't want
to fire off millions of simbad queries anyway; use simbad's own
TAP service for this kind of application.An aggregate function returning all values of
expression within a GROUP contcatenated with delimiterThe function converts a postgres timestamp to julian date.
This is naive; no corrections for timezones, let alone time
scales or the like are done; you can thus not expect this to be
good to second-precision unless you are careful in the construction
of the timestamp.The function converts a postgres timestamp to modified julian date.
This is naive; no corrections for timezones, let alone time
scales or the like are done; you can thus not expect this to be
good to second-precision unless you are careful in the construction
of the timestamp.Written after a table reference, TABLESAMPLE(10) will make the database only use 10% of the rows; these are `somewhat random' in that the system will use random blocks. This should be good enough when just testing queries (and much better than using TOP n).A geometry function creating MOCs. It either takes a string argument with an ASCII MOC ('4/13 17-18 8/3002'), or an order and another geometry.You can compute with vectors here. See https://wiki.ivoa.net/twiki/bin/view/IVOA/ADQLVectorMath for an overview of the functions and operators available.The SQL92 CASE expressiontext/tab-separated-valuestsvtext/plaintxttext/csvcsv_baretext/csv;header=presentcsvapplication/jsonjsonapplication/geo+jsongeojsonapplication/x-votable+xmlvotableapplication/x-votable+xml;serialization=BINARY2votable/b2votableb2application/x-votable+xml;serialization=TABLEDATAtext/xmlvotable/tdvotabletdapplication/x-votable+xml;serialization=TABLEDATA;version=1.1text/xmlvotabletd1.1application/x-votable+xml;version=1.1text/xmlvotable1.1application/x-votable+xml;serialization=TABLEDATA;version=1.2text/xmlvotabletd1.2application/x-votable+xml;serialization=TABLEDATA;version=1.6vodmlapplication/x-votable+xml;version=1.6vodmlbtext/htmlhtmlapplication/fitsfits172800602000020000000500000https://data.xao.ac.cn/__system__/tap/run/capabilitieshttp://data.xao.ac.cn/__system__/tap/run/capabilitieshttps://data.xao.ac.cn/__system__/tap/run/availabilityhttp://data.xao.ac.cn/__system__/tap/run/availabilityhttps://data.xao.ac.cn/__system__/tap/run/tableMetadatahttp://data.xao.ac.cn/__system__/tap/run/tableMetadatatap_schema XAO Data Center's Table Access Protocol (TAP) service with
table metadata.tap_schema.tablesTables available for ADQL querying.schema_nameFully qualified schema namecharnullabletable_nameFully qualified table namecharindexedprimarytable_typeOne of: table, viewcharnullabledescriptionBrief description of the tableunicodeCharnullableutypeutype if the table corresponds to a data modelcharnullabletable_indexSuggested position this table should take in a sorted list of tables from this data centerintnullablesourcerdId of the originating rd (local information)charnullablenrowsThe approximate size of the table in rowslongnullabletap_schema.schemasschema_nameschema_name
tap_schema.columnsColumns in tables available for ADQL querying.table_nameFully qualified table namecharindexedprimarycolumn_nameColumn namecharindexedprimarydescriptionBrief description of columnunicodeCharnullableunitUnit in VO standard formatcharnullableucdUCD of column if anycharnullableutypeUtype of column if anycharnullabledatatypeADQL datatypecharnullablearraysizeArraysize in VOTable notationcharnullablextypeVOTable extended type information (for special interpretation of data content, e.g., timestamps or points)charnullable"size"Legacy length (ignore if you can).intnullableprincipalIs column principal?intindexedIs there an index on this column?intstdIs this a standard column?intsourcerdId of the originating rd (local information)charnullablecolumn_index1-based index of the column in database order.shortnullabletap_schema.tablestable_nametable_name
tap_schema.schemasSchemas containing tables available for ADQL querying.schema_nameFully qualified schema namecharindexedprimarydescriptionBrief description of the schemaunicodeCharnullableutypeutype if schema corresponds to a data modelcharnullableschema_indexSuggested position this schema should take in a sorted list of schemas from this data center.intnullable
tap_schema.keysForeign key relationships between tables available for ADQL querying.key_idUnique key identifiercharindexedprimaryfrom_tableFully qualified table namecharnullabletarget_tableFully qualified table namecharnullabledescriptionDescription of this keyunicodeCharnullableutypeUtype of this keycharnullablesourcerdId of the originating rd (local information)charnullabletap_schema.tablesfrom_tabletable_nametap_schema.tablestarget_tabletable_name
tap_schema.key_columnsColumns participating in foreign key relationships between tables
available for ADQL querying.key_idKey identifier from TAP_SCHEMA.keyscharnullablefrom_columnKey column name in the from tablecharnullabletarget_columnKey column in the target tablecharnullablesourcerdId of the originating rd (local information)charnullabletap_schema.keyskey_idkey_id
tap_schema.groupsColumns that are part of groups within tables available for ADQL
querying.table_nameFully qualified table namecharnullablecolumn_nameName of a column belonging to the groupcharnullablecolumn_utypeutype the column within the groupcharnullablegroup_nameName of the groupcharnullablegroup_utypeutype of the groupcharnullablesourcerdId of the originating rd (local information)charnullabletap_schema.tablestable_nametable_name
agnXAO AGN Flux Monitoring DataActive Galactic Nuclei (AGNs)
are extragalactic objects characterized by extremely complex physical processes
and strong temporal flux variability over almost the whole electromagnetic
spectrum, which play a very important role in studying the formation and
evolution of galaxies, cosmology and many other astrophysical problems.
Flux variability is one of the most remarkable observational characteristics
of AGNs and the variability time scales are from minutes to dozens of years.
Multi-wavelength flux monitoring is the main means to study the nature of AGN flux variability.
In order to systematically study the total flux variability of AGNs in radio band,
we launched a long-term program, which is called the quasi- Simultaneous Multiwavelength
Monitoring of AGNs with the Nanshan 26-m radio telescope of Xinjiang Astronomical Observatory (XAO),
namely SMMAN program. The monitoring data were acquired monthly with the cross-scan mode at
C-band (4.8 GHz) and K-band (23.6 GHz) for a sample of about 100 AGNs selected from Fermi-LAT suvery.
Additionally, we also conducted weekly monitoring observations or Intra-Day Vairibility (IDV)
observations for some of flaring Blazars to reveal their more complex variability time scales.agn.agnActive Galactic Nuclei (AGNs)
are extragalactic objects characterized by extremely complex physical processes
and strong temporal flux variability over almost the whole electromagnetic
spectrum, which play a very important role in studying the formation and
evolution of galaxies, cosmology and many other astrophysical problems.
Flux variability is one of the most remarkable observational characteristics
of AGNs and the variability time scales are from minutes to dozens of years.
Multi-wavelength flux monitoring is the main means to study the nature of AGN flux variability.
In order to systematically study the total flux variability of AGNs in radio band,
we launched a long-term program, which is called the quasi- Simultaneous Multiwavelength
Monitoring of AGNs with the Nanshan 26-m radio telescope of Xinjiang Astronomical Observatory (XAO),
namely SMMAN program. The monitoring data were acquired monthly with the cross-scan mode at
C-band (4.8 GHz) and K-band (23.6 GHz) for a sample of about 100 AGNs selected from Fermi-LAT suvery.
Additionally, we also conducted weekly monitoring observations or Intra-Day Vairibility (IDV)
observations for some of flaring Blazars to reveal their more complex variability time scales.accrefAccess key for the datameta.ref.urlAccess.ReferencecharindexednullableownerOwner of the datacharnullableembargoDate the data will become/became publicyrcharnullablemimeMIME type of the file servedmeta.code.mimeAccess.FormatcharnullableaccsizeSize of the data in bytesbyteVOX:Image_FileSizeAccess.SizelongnullableraArea center RA ICRSdegpos.eq.ra;meta.mainfloatindexednullabledecArea center Declination ICRSdegpos.eq.dec;meta.mainfloatindexednullablecoverageField covered by the pointdegdoubleindexednullabledate_obsObservation datedtime.obsfloatnullableobjectObject observedmeta.id;meta.maincharnullable
fast_pulFAST Pulsar Data Query Test
The data could only be used with the permission of Dr. Na Wang (na.wang@xao.ac.cn), please send her an email for your request.fast_pul.fast_pul
The data could only be used with the permission of Dr. Na Wang (na.wang@xao.ac.cn), please send her an email for your request.accrefAccess key for the datameta.ref.urlAccess.ReferencecharindexednullableownerOwner of the datacharnullableembargoDate the data will become/became publicyrcharnullablemimeMIME type of the file servedmeta.code.mimeAccess.FormatcharnullableaccsizeSize of the data in bytesbyteVOX:Image_FileSizeAccess.SizelongnullableidArtificial identifier of the observationmeta.id;meta.maincharindexedprimaryraArea center RA ICRSdegpos.eq.ra;meta.maindoublenullabledecArea center Declination ICRSdegpos.eq.dec;meta.maindoublenullabledate_obsObservation datedtime.obsfloatnullableobjectObject observedmeta.id;srccharnullableobject_zhlObject observedmeta.id;srccharnullableobserverObserver Nameobs.observercharnullableprojidProject Namemeta.idcharnullablefrontendReceiver IDcharnullablebackendBackend IDcharnullablebeconfigBackend Configuration File Namecharnullableobs_modeObservation ModecharnullableobsfreqObservation FrequencyMHzem.bindoublenullableobsbwObservation BandwidthMHzinstr.bandwidthdoublenullableobsnchanNumber of Frequency Channelsdoublenullable
gaiaSelections from Gaia Data Release 3 (DR3)
This schema contains data re-published from the official
Gaia mirrors (such as ivo://uni-heidelberg.de/gaia/tap) either to
support combining its data with local tables (the various Xlite tables)
or to make the data more accessible to VO clients (e.g., epoch fluxes).gaia.dr3liteGaia DR3 source catalogue "light" This is gaia_source from the Gaia Data Release 3, stripped to just
enough columns to enable basic science (but therefore a bit faster and
simpler to deal with than the full gaia_source table).
Note that on this server, there is also The gedr3dist.main, which
gives distances computed by Bailer-Jones et al. Use these in
preference to working with the raw parallaxes.
The full DR3 is available from numerous places in the VO (in
particular from the TAP services ivo://uni-heidelberg.de/gaia/tap and
ivo://esavo/gaia/tap).1811709771source_idGaia DR3 unique source identifier. Note that this *cannot* be matched against the DR1 or DR2 source_ids.meta.id;meta.mainlongindexedprimaryraBarycentric Right Ascension in ICRS at epoch J2016.0degpos.eq.ra;meta.maindoubleindexednullabledecBarycentric Declination in ICRS at epoch J2016.0degpos.eq.dec;meta.maindoubleindexednullablera_errorStandard error of ra (with cos δ applied).masstat.error;pos.eq.rafloatnullabledec_errorStandard error of decmasstat.error;pos.eq.decfloatnullablepmraProper motion in right ascension of the source in ICRS at J2016.0. This is the tangent plane projection (i.e., multiplied by cos(δ)) of the proper motion vector in the direction of increasing right ascension.mas/yrpos.pm;pos.eq.rafloatindexednullablepmdecProper motion in declination at J2016.0.mas/yrpos.pm;pos.eq.decfloatindexednullablepmra_errorStandard error of pmramas/yrstat.error;pos.pm;pos.eq.rafloatnullablepmdec_errorStandard error of pmdecmas/yrstat.error;pos.pm;pos.eq.decfloatnullableparallaxAbsolute barycentric stellar parallax of the source at the reference epoch J2016.0. If looking for a distance, consider joining with gedr3dist.main and using the distances from there.maspos.parallaxfloatindexednullableparallax_errorStandard error of parallaxmasstat.error;pos.parallaxfloatnullablephot_g_mean_magMean magnitude in the G band. This is computed from the G-band mean flux applying the magnitude zero-point in the Vega scale. To obtain error estimates, see phot_g_mean_flux_over_error.magphot.mag;em.opt;stat.meanfloatindexednullablephot_g_mean_flux_over_errorIntegrated mean G flux divided by its error. Errors are computed from the dispersion about the weighted mean of the input calibrated photometry.stat.snr;phot.flux;em.opt;stat.meanfloatnullablephot_rp_mean_flux_over_errorIntegrated mean RP flux divided by its error. Errors are computed from the dispersion about the weighted mean of the input calibrated photometry.stat.snr;phot.flux;em.opt.Rfloatnullablephot_rp_mean_magMean magnitude in the integrated RP band. This is computed from the RP-band mean flux applying the magnitude zero-point in the Vega scale. To obtain error estimates, see phot_rp_mean_flux_over_error.magphot.mag;em.opt.Rfloatindexednullablephot_bp_mean_flux_over_errorIntegrated mean BP flux divided by its error. Errors are computed from the dispersion about the weighted mean of the input calibrated photometry.stat.snr;phot.flux;em.opt.Bfloatnullablephot_bp_mean_magMean magnitude in the integrated BP band. This is computed from the BP-band mean flux applying the magnitude zero-point in the Vega scale. To obtain error estimates, see phot_bp_mean_flux_over_error.magphot.mag;em.opt.Bfloatindexednullablephot_bp_rp_excess_factorBP/RP excess factor estimated from the comparison of the sum of integrated BP and RP fluxes with respect to the flux in the G band. This measures the excess of flux in the BP and RP integrated photometry with respect to the G band. This excess is believed to be caused by background and contamination issues affecting the BP and RP data. Therefore a large value of this factor for a given source indicates systematic errors in the BP and RP photometry.stat.fit.goodnessfloatnullableastrometric_excess_noiseThis is the excess noise of the source, measuring the disagreement, expressed as an angle, between the observations of a source and the best-fitting standard astrometric model (using five astrometric parameters). A value of 0 signifies a well-behaved source, a positive value signifies that the residuals are larger than expected.masstat.fit.goodnessfloatnullableradial_velocitySpectroscopic radial velocity in the solar barycentric reference frame. For stars brighter than about 12 mag, this is the median of all single-epoch measurements. For fainter stars, RV estimation is from a co-added spectrum.km/sspect.dopplerVeloc.opt;em.opt.Ifloatnullableradial_velocity_errorError in radial_velocity; this is the error of the median for bright stars. For faint stars, it is derived from the cross-correlation function.km/sstat.error;spect.dopplerVelocfloatnullablepseudocolourEffective wavenumber of the source estimated in the final astrometric processing. The pseudocolour is the astrometrically estimated effective wavenumber of the photon flux distribution in the astrometric (G) band, estimated from the chromatic displacements of image centroids. The field is empty when chromaticity was instead taken into account using the photometrically determined ν_eff given in the field nu_eff_used_in_astrometry.um**-1em.wavenumber;phot.colorfloatnullablepseudocolour_errorStandard error of the pseudocolour.um**-1stat.error;em.wavenumber;phot.colorfloatnullablevisibility_periods_usedNumber of visibility periods (groups of observations at least 4 days apart) used in the astrometric solution. A small value (less than 10) indicates that the calculated parallax could be more vulnerable to error not reflected in the formal uncertainties.meta.number;obsshortastrometric_params_solvedThis is a binary code indicating which astrometric parameters were estimated for the source. A set bit means the parameter was estimated. The least-significant bit represents α, the next bits δ, parallax, PM(RA) and PM(De). For Gaia DR2 the only relevant values are 31 (all five parameters solved) and 3 (only positions).meta.codeshortnullablerandom_indexRandom index that can be used to deterministically select subsetsmeta.codelongindexedruweRenormalized Unit Weight Error; this is a revised measure for the overall consistency of the solution as defined by GAIA-C3-TN-LU-LL-124-01. A suggested cut on this is RUWE <1.40) See the note for details.stat.weightfloatnullable
gaia.edr3liteGaia eDR3 source catalogue "light" This is a “light” version of the full Gaia DR3 gaia_source table. It
is just a view copying gaia.dr3lite, which should preferentially be
used in new queries. This table is being kept around in order to keep
legacy queries from breaking unnecessarily. However, it is actually
DR3 data rather than eDR3. The minute differences did not seem to
warrant keeping two copies of the relatively massive data around.1811709771source_idGaia DR3 unique source identifier. Note that this *cannot* be matched against the DR1 or DR2 source_ids.meta.id;meta.mainlongnullableraBarycentric Right Ascension in ICRS at epoch J2016.0degpos.eq.ra;meta.maindoubleindexednullabledecBarycentric Declination in ICRS at epoch J2016.0degpos.eq.dec;meta.maindoubleindexednullablera_errorStandard error of ra (with cos δ applied).masstat.error;pos.eq.rafloatnullabledec_errorStandard error of decmasstat.error;pos.eq.decfloatnullablepmraProper motion in right ascension of the source in ICRS at J2016.0. This is the tangent plane projection (i.e., multiplied by cos(δ)) of the proper motion vector in the direction of increasing right ascension.mas/yrpos.pm;pos.eq.rafloatindexednullablepmdecProper motion in declination at J2016.0.mas/yrpos.pm;pos.eq.decfloatindexednullablepmra_errorStandard error of pmramas/yrstat.error;pos.pm;pos.eq.rafloatnullablepmdec_errorStandard error of pmdecmas/yrstat.error;pos.pm;pos.eq.decfloatnullableparallaxAbsolute barycentric stellar parallax of the source at the reference epoch J2016.0. If looking for a distance, consider joining with gedr3dist.main and using the distances from there.maspos.parallaxfloatindexednullableparallax_errorStandard error of parallaxmasstat.error;pos.parallaxfloatnullablephot_g_mean_magMean magnitude in the G band. This is computed from the G-band mean flux applying the magnitude zero-point in the Vega scale. To obtain error estimates, see phot_g_mean_flux_over_error.magphot.mag;em.opt;stat.meanfloatindexednullablephot_g_mean_flux_over_errorIntegrated mean G flux divided by its error. Errors are computed from the dispersion about the weighted mean of the input calibrated photometry.stat.snr;phot.flux;em.opt;stat.meanfloatnullablephot_rp_mean_flux_over_errorIntegrated mean RP flux divided by its error. Errors are computed from the dispersion about the weighted mean of the input calibrated photometry.stat.snr;phot.flux;em.opt.Rfloatnullablephot_rp_mean_magMean magnitude in the integrated RP band. This is computed from the RP-band mean flux applying the magnitude zero-point in the Vega scale. To obtain error estimates, see phot_rp_mean_flux_over_error.magphot.mag;em.opt.Rfloatindexednullablephot_bp_mean_flux_over_errorIntegrated mean BP flux divided by its error. Errors are computed from the dispersion about the weighted mean of the input calibrated photometry.stat.snr;phot.flux;em.opt.Bfloatnullablephot_bp_mean_magMean magnitude in the integrated BP band. This is computed from the BP-band mean flux applying the magnitude zero-point in the Vega scale. To obtain error estimates, see phot_bp_mean_flux_over_error.magphot.mag;em.opt.Bfloatindexednullablephot_bp_rp_excess_factorBP/RP excess factor estimated from the comparison of the sum of integrated BP and RP fluxes with respect to the flux in the G band. This measures the excess of flux in the BP and RP integrated photometry with respect to the G band. This excess is believed to be caused by background and contamination issues affecting the BP and RP data. Therefore a large value of this factor for a given source indicates systematic errors in the BP and RP photometry.stat.fit.goodnessfloatnullableastrometric_excess_noiseThis is the excess noise of the source, measuring the disagreement, expressed as an angle, between the observations of a source and the best-fitting standard astrometric model (using five astrometric parameters). A value of 0 signifies a well-behaved source, a positive value signifies that the residuals are larger than expected.masstat.fit.goodnessfloatnullableradial_velocitySpectroscopic radial velocity in the solar barycentric reference frame. For stars brighter than about 12 mag, this is the median of all single-epoch measurements. For fainter stars, RV estimation is from a co-added spectrum.km/sspect.dopplerVeloc.opt;em.opt.Ifloatnullableradial_velocity_errorError in radial_velocity; this is the error of the median for bright stars. For faint stars, it is derived from the cross-correlation function.km/sstat.error;spect.dopplerVelocfloatnullablepseudocolourEffective wavenumber of the source estimated in the final astrometric processing. The pseudocolour is the astrometrically estimated effective wavenumber of the photon flux distribution in the astrometric (G) band, estimated from the chromatic displacements of image centroids. The field is empty when chromaticity was instead taken into account using the photometrically determined ν_eff given in the field nu_eff_used_in_astrometry.um**-1em.wavenumber;phot.colorfloatnullablepseudocolour_errorStandard error of the pseudocolour.um**-1stat.error;em.wavenumber;phot.colorfloatnullablevisibility_periods_usedNumber of visibility periods (groups of observations at least 4 days apart) used in the astrometric solution. A small value (less than 10) indicates that the calculated parallax could be more vulnerable to error not reflected in the formal uncertainties.meta.number;obsshortastrometric_params_solvedThis is a binary code indicating which astrometric parameters were estimated for the source. A set bit means the parameter was estimated. The least-significant bit represents α, the next bits δ, parallax, PM(RA) and PM(De). For Gaia DR2 the only relevant values are 31 (all five parameters solved) and 3 (only positions).meta.codeshortnullablerandom_indexRandom index that can be used to deterministically select subsetsmeta.codelongindexedruweRenormalized Unit Weight Error; this is a revised measure for the overall consistency of the solution as defined by GAIA-C3-TN-LU-LL-124-01. A suggested cut on this is RUWE <1.40) See the note for details.stat.weightfloatnullable
galleryXAO GalleryImages from Xinjiang Astronomical Observatory, Urumuqigallery.notfImages from Xinjiang Astronomical Observatory, UrumuqiaccrefAccess key for the datameta.ref.urlAccess.ReferencecharindexednullableownerOwner of the datacharnullableembargoDate the data will become/became publicyrcharnullablemimeMIME type of the file servedmeta.code.mimeAccess.FormatcharnullableaccsizeSize of the data in bytesbyteVOX:Image_FileSizeAccess.SizelongnullablecreatedObject Created Datecharnullable
glotsGloTS, the Global TAP Schema
The global TAP schema collects information on
tables and columns from known TAP servers. This facilitates locating
queriable data by physics (via UCD) or keywords (via description).
Note that this shouldn't really be necessary as all information
present here should be exposed through Registry records. However,
in reality data providers currently are much more liable to give
column metadata in their tap_schema than in their Registry records.
Hence, for the time being, we maintain this service by harvesting
tap_schemas about monthly.glots.servicesA table of TAP services harvested from the registry (and some
spoon-fed).ivoidIVOA identifier of providing servicecharindexedprimaryaccessurlBase URL of TAP endpointcharnullablenextharvestNext scheduled harvest of datacharnullableharvestintervalApproximate interval of harvestdintnullablelastsuccessLast successful harvest of this servicecharnullable
glots.tablesA table of tables accesible through the TAP services known to
glots.services.ivoidIVOA identifier of providing servicecharindexedprimarytable_nameFully qualified table namecharindexedprimarytable_descBrief description of the tableunicodeCharindexednullableutypeutype if the table corresponds to a data modelcharnullableglots.servicesivoidivoid
glots.columnsA table of columns within the tables listed in glots.tables.ivoidIVOA identifier of providing servicecharindexedprimarytable_nameFully qualified table namecharindexedprimarycolumn_nameColumn namecharindexedprimarydescriptionBrief description of columncharindexednullableunitUnit in VO standard formatcharnullableucdUCD of column (some services still have 1.0 UCDs).charindexednullableutypeUtype of columncharnullabledatatypeADQL datatypecharnullable"size"Length of variable length datatypesintnullableprincipalIs column principal?charnullableindexedIs there an index on this column?intnullablestdIs this a standard column?charnullableglots.tablesivoidivoidtable_nametable_name
nowt1M-WideField Images Images created by 1M-WideFieldnowt.nowt Images created by 1M-WideFieldaccrefAccess key for the datameta.ref.urlAccess.ReferencecharindexednullableownerOwner of the datacharnullableembargoDate the data will become/became publicyrcharnullablemimeMIME type of the file servedmeta.code.mimeAccess.FormatcharnullableaccsizeSize of the data in bytesbyteVOX:Image_FileSizeAccess.SizelongnullableidArtificial identifier of the observationmeta.id;meta.maincharindexedprimaryraArea center RA ICRSdegpos.eq.ra;meta.maindoublenullabledecArea center Declination ICRSdegpos.eq.dec;meta.maindoublenullableobjectObject observedmeta.id;srccharnullableexposure_timeExporsure TimesdoublenullabletelescopeThe name of telescope.instr.telcharnullabledate_obsObservation datedtime.obsfloatnullable
obscodeObservatory Codes List of Observatory Codes assigned by the Minor Planet Center (MPC).
The codes are used in cataloguing astrometric observations of small
bodies in the solar system. A code is unique for a certain location
and consists of three digits or one letter and two digits.
In this representation, we give the observatory code, the geocentric
coordinates, and the observatory designation.obscode.data List of Observatory Codes assigned by the Minor Planet Center (MPC).
The codes are used in cataloguing astrometric observations of small
bodies in the solar system. A code is unique for a certain location
and consists of three digits or one letter and two digits.
In this representation, we give the observatory code, the geocentric
coordinates, and the observatory designation.codeObservatory Code assigned by the Minor Planet Centermeta.id;meta.codecharnullablelongLongitude of the observatorydegpos.earth.longfloatnullablecosphipParallax constant, cosinefloatnullablesinphipParallax constant, sinefloatnullablegclatGeocentric latitude of the observatorydegpos.earth.lat;pos.geodeticfloatnullablegdlatGeodetic latitude of the observatory WGS84degpos.earth.lat;pos.geodeticfloatnullableheightAltitude of the observatorympos.earth.alitude;pos.geodeticfloatnullablenameOperator-chosen designation of the Observatorymeta.id;meta.maincharnullable
ppmxl PPMXL is a catalog of positions, proper motions, 2MASS- and optical
photometry of 900 million stars and galaxies, aiming to be complete
down to about V=20 full-sky. It is the result of a re-reduction of
USNO-B1 together with 2MASS to the ICRS as represented by PPMX.ppmxl.main PPMXL is a catalog of positions, proper motions, 2MASS- and optical
photometry of 900 million stars and galaxies, aiming to be complete
down to about V=20 full-sky. It is the result of a re-reduction of
USNO-B1 together with 2MASS to the ICRS as represented by PPMX.ipixIdentifier (Q3C ipix of the USNO-B 1.0 object)meta.id;meta.mainlongindexedraj2000Right Ascension J2000.0, epoch 2000.0degpos.eq.ra;meta.maindoubleindexednullabledej2000Declination J2000.0, epoch 2000.0degpos.eq.dec;meta.maindoubleindexednullablee_raepraMean error in RA*cos(delta) at mean epochdegstat.error;pos.eq.ra;meta.mainfloatnullablee_deepdeMean error in Dec at mean epochdegstat.error;pos.eq.dec;meta.mainfloatnullablepmraProper Motion in RA*cos(delta)deg/yrpos.pm;pos.eq.rafloatindexednullablepmdeProper Motion in Decdeg/yrpos.pm;pos.eq.decfloatindexednullablee_pmraMean error in pmRA*cos(delta)deg/yrstat.error;pos.pm;pos.eq.rafloatnullablee_pmdeMean error in pmDEdeg/yrstat.error;pos.pm;pos.eq.decfloatnullablenobsNumber of observations usedmeta.number;obsshortnullableepraMean Epoch (RA)yrtime.epoch;pos.eq.rafloatnullableepdeMean Epoch (Dec)yrtime.epoch;pos.eq.decfloatnullablejmagJ selected default magnitude from 2MASSmagphot.mag;em.IR.Jfloatnullablee_jmagJ total magnitude uncertaintymagstat.error;phot.mag;em.IR.JfloatnullablehmagH selected default magnitude from 2MASSmagphot.mag;em.IR.Hfloatnullablee_hmagH total magnitude uncertaintymagstat.error;phot.mag;em.IR.HfloatnullablekmagK_s selected default magnitude from 2MASSmagphot.mag;em.IR.Kfloatnullablee_kmagK_s total magnitude uncertaintymagstat.error;phot.mag;em.IR.Kfloatnullableb1magB mag from USNO-B, first epochphot.mag;em.opt.Bfloatnullableb2magB mag from USNO-B, second epochphot.mag;em.opt.Bfloatnullabler1magR mag from USNO-B, first epochphot.mag;em.opt.Rfloatnullabler2magR mag from USNO-B, second epochphot.mag;em.opt.RfloatnullableimagI mag from USNO-Bphot.mag;em.opt.IfloatnullablemagsurveysSurveys the USNO-B magnitudes are taken frommeta.codecharnullableflagsFlagsmeta.codeshort
pulsarXAO Pulsar Data QueryThe pulsar timing data were obtained with the Nanshan 25M radio telescope. Our observations, which commenced in January 2000, have been made using a dual-channel room-temperature receiver with a bandwidth of 320 MHz centered at 1540 MHz before June 2002. The de-dispersion was provided by a 2X128X2.5 MHz analog filter-bank. A cryogenic receiver was mounted in July 2002, which increases the sensitivity to 0.5 mJy. In January 2010, a digital filter-bank (DFB) system came into operation. The higher time resolution allows us to monitor about 280 pulsars, including ten millisecond-pulsars (MSP). The format of the DFB data is "Psrfit". The "psrchive" program could reads and analyzes the data.
Timing observations of 74 pulsars have been regularly carried out between 2002 July to 2009 December. These 74 pulsars have been monitored approximately once every 9d using a dual-channel cryogenic system that receives orthogonal linear polarizations at the central observing frequency of 1540 MHz. The folded profiles obtained are released in format PSRFITS for timing analysis, the file name extension is .FTp. Users can enter "~*.FTp*" in "Product key" filed to search and download it.
Non-public data could be used with the permission of Dr. Shengnan Sun (sunshengnan@xao.ac.cn), please send an email for your request.pulsar.pulsarThe pulsar timing data were obtained with the Nanshan 25M radio telescope. Our observations, which commenced in January 2000, have been made using a dual-channel room-temperature receiver with a bandwidth of 320 MHz centered at 1540 MHz before June 2002. The de-dispersion was provided by a 2X128X2.5 MHz analog filter-bank. A cryogenic receiver was mounted in July 2002, which increases the sensitivity to 0.5 mJy. In January 2010, a digital filter-bank (DFB) system came into operation. The higher time resolution allows us to monitor about 280 pulsars, including ten millisecond-pulsars (MSP). The format of the DFB data is "Psrfit". The "psrchive" program could reads and analyzes the data.
Timing observations of 74 pulsars have been regularly carried out between 2002 July to 2009 December. These 74 pulsars have been monitored approximately once every 9d using a dual-channel cryogenic system that receives orthogonal linear polarizations at the central observing frequency of 1540 MHz. The folded profiles obtained are released in format PSRFITS for timing analysis, the file name extension is .FTp. Users can enter "~*.FTp*" in "Product key" filed to search and download it.
Non-public data could be used with the permission of Dr. Shengnan Sun (sunshengnan@xao.ac.cn), please send an email for your request.accrefAccess key for the datameta.ref.urlAccess.ReferencecharindexednullableownerOwner of the datacharnullableembargoDate the data will become/became publicyrcharnullablemimeMIME type of the file servedmeta.code.mimeAccess.FormatcharnullableaccsizeSize of the data in bytesbyteVOX:Image_FileSizeAccess.SizelongnullableidArtificial identifier of the observationmeta.id;meta.maincharindexedprimaryraArea center RA ICRSdegpos.eq.ra;meta.maindoubleindexednullabledecArea center Declination ICRSdegpos.eq.dec;meta.maindoubleindexednullabledate_obsObservation datedtime.obsfloatnullableobjectObject observedmeta.id;srccharindexednullableobject_zhlObject observedmeta.id;srccharnullableobserverObserver Nameobs.observercharnullableprojidProject Namemeta.idcharnullablefrontendReceiver IDcharnullablebackendBackend IDcharnullablebeconfigBackend Configuration File Namecharnullableobs_modeObservation ModecharnullableobsfreqObservation FrequencyMHzem.bindoublenullableobsbwObservation BandwidthMHzinstr.bandwidthdoublenullableobsnchanNumber of Frequency ChannelsdoublenullablepreviewPreview URLcharnullable
pulsarcatalogATNF Pulsar Catalog
The Australia Telescope National Facility (ATNF) Pulsar Catalog is a catalog of
known pulsars compiled by R.N. Manchester et al. and is descended from pulsar
database used for the paper "Catalog of 558 Pulsars" by J.H. Taylor, R.N.
Manchester and A.G. Lyne 1993, ApJS, 88, 529-568. The current catalog has been
supplemented by inclusion of published data from more recent radio surveys, in
particular, the Parkes Multibeam (PM) Pulsar Survey (Manchester et al. 2001,
MNRAS, 328, 17-35) [available at the HEASARC as the PMPULSAR table] and the
Swinburne Intermediate Latitude Pulsar Survey (Edwards et al. 2001, MNRAS, 326,
358-374), both made using the ATNF Parkes 64-m radio telescope. Binary
parameters for known binary pulsars are also included as well as all available
astrometric and spin parameter information for all pulsars. The catalog
includes all published rotation-powered pulsars. Two separate small subsets of
pulsars detected ONLY at high energies are also included in the current table:
the first group comprises X-ray and gamma-ray pulsars which are apparently
powered by spin-down energy, but which have not been detected at radio
wavelengths, while the second group contains anomalous X-ray pulsars (AXPs) and
soft-gamma-ray repeaters (SGRs) for which coherent pulsations have been
detected. Accretion-powered pulsars such as Her X-1 and the recently discovered
X-Ray millisecond pulsars such as SAX J1808.4-3658 are not included in this
table, however. Many people have contributed to the compilation of the data
contained in this catalog and the database that it was derived from. The
authors particularly thank Andrew Lyne of the University of Manchester, Jodrell
Bank Observatory, David Nice of Princeton University, and Russell Edwards, then
at Swinburne University of Technology. The also acknowledge the efforts of
Warwick University students Adam Goode and Steven Thomas who compiled and
checked a recent version of the database. The original (summer 2003) database
at the ATNF website was compiled with the invaluable assistance of Maryam
Hobbs, while the ATNF web interface was designed and constructed by Albert
Teoh, a Summer Vacation Scholar at the ATNF in 2002/2003.
The authors would
appreciate if anyone making use of this catalog in a publication acknowledges
the source of their information by quoting the ATNF Pulsar Catalog website
address of http://www.atnf.csiro.au/research/pulsar/psrcat/pulsarcatalog.data
The Australia Telescope National Facility (ATNF) Pulsar Catalog is a catalog of
known pulsars compiled by R.N. Manchester et al. and is descended from pulsar
database used for the paper "Catalog of 558 Pulsars" by J.H. Taylor, R.N.
Manchester and A.G. Lyne 1993, ApJS, 88, 529-568. The current catalog has been
supplemented by inclusion of published data from more recent radio surveys, in
particular, the Parkes Multibeam (PM) Pulsar Survey (Manchester et al. 2001,
MNRAS, 328, 17-35) [available at the HEASARC as the PMPULSAR table] and the
Swinburne Intermediate Latitude Pulsar Survey (Edwards et al. 2001, MNRAS, 326,
358-374), both made using the ATNF Parkes 64-m radio telescope. Binary
parameters for known binary pulsars are also included as well as all available
astrometric and spin parameter information for all pulsars. The catalog
includes all published rotation-powered pulsars. Two separate small subsets of
pulsars detected ONLY at high energies are also included in the current table:
the first group comprises X-ray and gamma-ray pulsars which are apparently
powered by spin-down energy, but which have not been detected at radio
wavelengths, while the second group contains anomalous X-ray pulsars (AXPs) and
soft-gamma-ray repeaters (SGRs) for which coherent pulsations have been
detected. Accretion-powered pulsars such as Her X-1 and the recently discovered
X-Ray millisecond pulsars such as SAX J1808.4-3658 are not included in this
table, however. Many people have contributed to the compilation of the data
contained in this catalog and the database that it was derived from. The
authors particularly thank Andrew Lyne of the University of Manchester, Jodrell
Bank Observatory, David Nice of Princeton University, and Russell Edwards, then
at Swinburne University of Technology. The also acknowledge the efforts of
Warwick University students Adam Goode and Steven Thomas who compiled and
checked a recent version of the database. The original (summer 2003) database
at the ATNF website was compiled with the invaluable assistance of Maryam
Hobbs, while the ATNF web interface was designed and constructed by Albert
Teoh, a Summer Vacation Scholar at the ATNF in 2002/2003.
The authors would
appreciate if anyone making use of this catalog in a publication acknowledges
the source of their information by quoting the ATNF Pulsar Catalog website
address of http://www.atnf.csiro.au/research/pulsar/psrcat/namePulsar Designation, Based on J2000 Coordinatesmeta.id;meta.maincharnullableraRight Ascensiondegpos.eq.ra;meta.maindoubleindexednullabledecDeclinationdegpos.eq.dec;meta.maindoubleindexednullableperiodBarycentric Periodsdoublenullableperiod_errorBarycentric Period Uncertaintysdoublenullableperiod_dotFirst Time Derivative of Barycentric Periods/sdoublenullableperiod_dot_errorUncertainty in Period Dot (s/s)s/sdoublenullabledmDispersion Measure (pc/cm^3)pc/cm^3doublenullabledm_errorUncertainty in Dispersion Measure (pc/cm^3)pc/cm^3doublenullable
sfXAO SF Data Query
The molecular spectrum lines data include mainly ammonia and water masers lines at 1.3cm band,
as well as formaldehyde and recombination lines at 6cm band observed towards both our Galactic
plane and nearby molecular clouds and star-forming regions.sf.sf
The molecular spectrum lines data include mainly ammonia and water masers lines at 1.3cm band,
as well as formaldehyde and recombination lines at 6cm band observed towards both our Galactic
plane and nearby molecular clouds and star-forming regions.accrefAccess key for the datameta.ref.urlAccess.ReferencecharindexednullableownerOwner of the datacharnullableembargoDate the data will become/became publicyrcharnullablemimeMIME type of the file servedmeta.code.mimeAccess.FormatcharnullableaccsizeSize of the data in bytesbyteVOX:Image_FileSizeAccess.SizelongnullableraArea center RA ICRSdegpos.eq.ra;meta.mainfloatnullabledecArea center Declination ICRSdegpos.eq.dec;meta.mainfloatnullabledate_obsObservation datedtime.obsfloatnullableobjectObject observedmeta.id;meta.maincharnullableobsfreqObservation FrequencyHzem.bindoublenullable
spm4Yale/San Juan SPM4 Catalog The SPM4 Catalog contains absolute proper motions, celestial
coordinates, and B,V photometry for 103,319,647 stars and galaxies
between the south celestial pole and -20 degrees declination. The
catalog is roughly complete to V=17.5. It is based on photographic and
CCD observations taken with the Yale Southern Observatory's
double-astrograph at Cesco Observatory in El Leoncito, Argentina.spm4.main The SPM4 Catalog contains absolute proper motions, celestial
coordinates, and B,V photometry for 103,319,647 stars and galaxies
between the south celestial pole and -20 degrees declination. The
catalog is roughly complete to V=17.5. It is based on photographic and
CCD observations taken with the Yale Southern Observatory's
double-astrograph at Cesco Observatory in El Leoncito, Argentina.spmidUnique SPM4 id (field number + input catalog line number)meta.id;meta.maincharindexednullableraj2000Right Ascension (ICRS, epoch=2000.0)degpos.eq.ra;meta.maindoubleindexednullabledej2000Declination (ICRS, epoch=2000.0)degpos.eq.dec;meta.maindoubleindexednullablee_raj2000Expected uncertainty in Right Ascension at mean epochdegstat.error;pos.eq.ra;meta.mainfloatnullablee_dej2000Expected uncertainty in Declination at mean epochdegstat.error;pos.eq.dec;meta.mainfloatnullablepmraAbsolute proper motion in RA (mu_alpha*cos(Dec))deg/yrpos.pm;pos.eq.rafloatnullablepmdeAbsolute proper motion in Declinationdeg/yrpos.pm;pos.eq.decfloatnullablee_pmraExpected uncertainty in proper motion in RA (mu_alpha*cos(Dec)), at mean epochdeg/yrstat.error;pos.pm;pos.eq.rafloatnullablee_pmdeExpected uncertainty in proper motion in Declination, at mean epoch.deg/yrstat.error;pos.pm;pos.eq.decfloatnullablemagbB magnitudemagphot.mag;em.opt.BfloatnullablemagvV magnitudemagphot.mag;em.opt.Vfloatindexednullablei_magbsource flag for B magnitudemeta.flag;phot.mag;em.opt.Bchari_magvsource flag for V magnitudemeta.flag;phot.mag;em.opt.VcharmeanepWeighted mean epochyrtime.epochfloatnullableep1Weighted mean epoch of first observationyrtime.epochfloatnullableep2Weighted mean epoch of second observationyrtime.epochfloatnullablenplates1Number of 1st epoch plates usedmeta.number;instr.plateshortnplates2Number of 2nd epoch plates usedmeta.number;instr.plateshortnccd2Number of 2nd epoch ccd frames usedmeta.numbershorti_galGalaxy/extended-source flagsrc.class.starGalaxyshorti_catCode for the input catalogmeta.codeshortmagjJ selected default magnitude from 2MASSmagphot.mag;em.IR.JfloatnullablemaghH selected default magnitude from 2MASSmagphot.mag;em.IR.HfloatnullablemagkK_s selected default magnitude from 2MASSmagphot.mag;em.IR.Kfloatnullable
ucdUCD Query The Unified Content Descriptor (UCD) is a formal vocabulary
astronomical data that is controlled by the International Virtual
Observatory Alliance (IVOA). The vocabulary is restricted in order to
avoid proliferation of terms and synonyms, and controlled in order to
avoid ambiguities as far as possible. It is intended to be flexible,
so that it is understandable to both humans and computers. UCDs
describe astronomical quantities, and they are built by combining
words from the controlled vocabulary.ucd.data The Unified Content Descriptor (UCD) is a formal vocabulary
astronomical data that is controlled by the International Virtual
Observatory Alliance (IVOA). The vocabulary is restricted in order to
avoid proliferation of terms and synonyms, and controlled in order to
avoid ambiguities as far as possible. It is intended to be flexible,
so that it is understandable to both humans and computers. UCDs
describe astronomical quantities, and they are built by combining
words from the controlled vocabulary.ucdUnified Content Descriptors from IVOAcharnullableucd_descThe simple explaination of UCDcharnullable