PADC TAP Server on voparis-tap-maser.obspm.fr TAP service
Short Name:
PADC TAP
Date:
16 Jul 2024 14:07:24
Publisher:
Paris Astronomical Data Centre
Description:
The PADC TAP Server on voparis-tap-maser.obspm.fr'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: epn_core from the cassini_jupiter schema, epn_core from the cassini_rpws schema, epn_core from the expres schema, epn_core from the juno_waves schema, epn_core from the lofar4sw_proto schema, epn_core from the maser_services schema, epn_core from the spase_vespa schema, epn_core from the stereo_waves schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, epn_core, fogg_akr_wind, leblanc_nda_jupiter_emi, leblanc_nda_jupiter_obs, louis_juno_waves, marques_nda_jupiter, taubenschuss_frp_saturn, wu_anomalous_nsmr, wu_nkom_saturn, wu_skr_harmonic from the tfcat schema, epn_core from the voyager_pra schema, epn_core from the wind_waves schema.
PADC TAP Server on voparis-tap-planeto.obspm.fr TAP service
Short Name:
PADC TAP
Date:
18 Oct 2024 18:07:32
Publisher:
Paris Astronomical Data Centre
Description:
The PADC TAP Server on voparis-tap-planeto.obspm.fr'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: epn_core from the apis schema, epn_core from the basecom schema, epn_core, observatories from the bdip schema, epn_core from the crism_speclib schema, epn_core from the dynastvo schema, epn_core from the exoplanet schema, epn_core from the gmap schema, epn_core from the hst_planeto schema, epn_core from the iks schema, epn_core from the lunar_craters schema, epn_core from the m4ast schema, epn_core from the mars_craters schema, epn_core from the mars_craters_lagain schema, epn_core from the mercury_craters schema, epn_core from the meteor_showers schema, epn_core from the moonsprop schema, epn_core from the planets schema, epn_core from the spectro_asteroids schema, epn_core from the spectro_m_ast schema, epn_core from the spectro_planets schema, epn_core from the spectro_stars schema, epn_core from the spectro_trojans schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, epn_core from the titan_profiles schema, epn_core from the tnosarecool schema, epn_core from the usgs_wms schema, epn_core from the venus_craters schema, epn_core from the vims_satellites schema, epn_core from the voccdb schema, epn_core from the vvex schema.
This is the OAI-PMH endpoint of the purx publishing registry proxy.
purx lets you publish VOResource records by just putting XML into a
web browser. For details, see http://dc.g-vo.org/PURX.
Shomydl shows Datalink_ documents in a web browser using the
`XSLT used in DaCHS`_. It is meant to give authors of such documents
an idea of how clients would interpret their document.
.. _Datalink: http://ivoa.net/documents/DataLink/
.. _XSLT used in DaCHS: https://github.com/msdemlei/datalink-xslt
The UCD resolver uses the metadata in the current
Registry to suggest UCDs pertinent to natural language column descriptions.
In that, it fulfills a similar function as the `CDS UCD builder`_
but uses an entirely different approach.
.. _CDS UCD builder: http://cdsweb.u-strasbg.fr/UCD/cgi-bin/descr2ucd
A validator for IVOA identifiers, checking
conformity to version 2 of the specification.
The service returns results in a tabular format, where an identifier is
valid if no row with msg_type="ERROR" is present.
As per DALI, the format of the table returned can be controlled
through the RESPONSEFORMAT parameter; for machine consumption, the
most useful values for that parameter are probably json and votable.
The code used here is available at
http://svn.ari.uni-heidelberg.de/svn/gavo/hdinputs/ivoidval
The VESPA PA team server'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: epn_core from the gem_mars schema, epn_core from the nomad schema, epn_core from the soir schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema.
