Search

Start Over Subject virtual-observatories Capability Type Data Access Layer Interface
11. OCA Data Center TAP service
ID:
ivo://purx/dachs/tap
Title:
OCA Data Center TAP service
Short Name:
OCA DC TAP
Date:
04 Mar 2022 16:03:46
Publisher:
Observatoire de la Côte d'Azur
Description:
The OCA 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: epn_core from the mp3c_best_epn schema, best, body, mpcorb, name, prop_albedo, prop_diameter, prop_family, prop_g, prop_h, prop_mass, prop_proper_elements, version from the mp3c_main schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema.
12. OCA Data Center TAP service
ID:
ivo://OCA/tap
Title:
OCA Data Center TAP service
Short Name:
OCA DC TAP
Date:
06 Sep 2024 07:01:24
Publisher:
Observatoire de la Côte d'Azur
Description:
The OCA 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: epn_core from the mp3c_best_epn schema, best, body, mpcorb, name, prop_albedo, prop_diameter, prop_family, prop_g, prop_h, prop_mass, prop_proper_elements, version from the mp3c_main schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema.
13. PADC TAP Server on voparis-rr.obspm.fr TAP service
ID:
ivo://purx/tap
Title:
PADC TAP Server on voparis-rr.obspm.fr TAP service
Short Name:
PADC TAP
Date:
30 Dec 2024 11:06:13
Publisher:
Paris Astronomical Data Centre
Description:
The PADC TAP Server on voparis-rr.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: columns, services, tables from the glots schema, obscore from the ivoa schema, alt_identifier, authorities, capability, g_num_stat, interface, intf_param, registries, relationship, res_date, res_detail, resource, res_role, res_schema, res_subject, res_table, stc_spatial, stc_spectral, stc_temporal, subject_uat, table_column, tap_table, validation from the rr schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema.
14. PADC TAP Server on voparis-tap-planeto.obspm.fr TAP service
ID:
ivo://padc.obspm.planeto/tap
Title:
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.
15. Validator for IVOA Identifiers
ID:
ivo://org.gavo.dc/ivoidval/q/val
Title:
Validator for IVOA Identifiers
Short Name:
ivoid val
Date:
27 Dec 2024 08:31:05
Publisher:
The GAVO DC team
Description:
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
16. VESPA PA team server TAP service
ID:
ivo://bira-iasb/tap
Title:
VESPA PA team server TAP service
Short Name:
BIRA-IASB TAP
Date:
08 Oct 2024 09:26:16
Publisher:
bira-iasb
Description:
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.