Search

Start Over Subject virtual observatory
91. The ivoa data model
ID:
ivo://ivoa.net/std/ivoadm
Title:
The ivoa data model
Date:
19 May 2018 09:00:00
Publisher:
IVOA
Description:
Ultimately all types in a VO-DML model are defined as hierarchies of primitive types. This Model defines a special, predefined model that contains a set of the most common of such types: integer, real, string etc. This
92. The National Radio Astronomy Observatory Authority Name
ID:
ivo://nrao
Title:
The National Radio Astronomy Observatory Authority Name
Short Name:
NRAO
Date:
08 May 2019 17:27:09
Publisher:
The National Radio Astronomy Observatory (NRAO)
Description:
The authority identifier for NRAO resources.
93. The National Radio Astronomy Observatory Authority Name
ID:
ivo://nrao.archive/nrao.archive
Title:
The National Radio Astronomy Observatory Authority Name
Short Name:
NRAO
Date:
08 May 2019 17:23:48
Publisher:
The National Radio Astronomy Observatory (NRAO)
Description:
The authority identifier for NRAO resources.
94. The National Radio Astronomy Observatory Authority Name
ID:
ivo://nrao.archive
Title:
The National Radio Astronomy Observatory Authority Name
Short Name:
NRAO
Date:
04 Apr 2008 11:10:31
Publisher:
The National Radio Astronomy Observatory (NRAO)
Description:
The authority identifier for NRAO resources.
95. The VO @ ASTRON TAP service
ID:
ivo://astron.nl/tap
Title:
The VO @ ASTRON TAP service
Short Name:
ASTRON VO TAP
Date:
22 Feb 2021 22:05:19
Publisher:
ASTRON
Description:
The The VO @ ASTRON'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: main from the lbcs schema, main, msssvf_img_main from the mvf schema, frb_det, frb_obs from the arts_dr1 schema, img_main, main from the lofartier1 schema, mosaic, source_catalog from the lolss schema, frb_det, frb_obs from the arts_dr2 schema, main from the svc schema, img_main, main from the tgssadr schema, main, mom0 from the sauron schema, images, source_catalog from the apertif_dr_bootes schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, hetdex_images, main, main_merged from the hetdex schema, img_main from the msss schema, obscore from the ivoa schema, beam_cubes, calibrated_visibilities, continuum_images, flux_cal_visibilities, pol_cal_visibilities, pol_cubes, raw_visibilities, source_catalog, spectral_cubes from the apertif_dr1 schema, main_gausses, main_sources, mosaics from the lotss_dr2 schema.
96. Tohoku University VO Server TAP service
ID:
ivo://tohoku.univ.jp/tap
Title:
Tohoku University VO Server TAP service
Short Name:
Tohoku TAP
Date:
23 May 2017 13:26:14
Publisher:
Tohoku University
Description:
The Tohoku University VO 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 iitatehf schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, epn_core from the iprt schema, epn_core from the irtf_cshell schema, epn_core from the hisaki schema, epn_core from the sw_model schema, emptyobscore, obscore from the ivoa schema.
97. UCL DaCHS server TAP service
ID:
ivo://astro.ucl.ac.uk/tap
Title:
UCL DaCHS server TAP service
Short Name:
UCL Astro TAP
Date:
08 Mar 2017 14:59:34
Publisher:
astro.ucl.ac.uk
Description:
The UCL DaCHS 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: columns, groups, key_columns, keys, schemas, tables from the tap_schema schema, emptyobscore, obscore from the ivoa schema, epn_core from the mdisc schema.
98. Units in the VO
ID:
ivo://ivoa.net/std/VOUnits
Title:
Units in the VO
Short Name:
VOUnits
Date:
04 Dec 2019 16:44:00
Publisher:
IVOA
Description:
This document describes a recommended syntax for writing the string representation of unit labels ("VOUnits"). In addition, it describes a set of recognised and deprecated units, which is as far as possible consistent with other relevant standards (BIPM, ISO/IEC and the IAU). The intention is that units written to conform to this specification will likely also be parsable by other well-known parsers. To this end, we include machine-readable grammars for other units syntaxes.
99. VODataService: a VOResource Schema Extension for Describing Collections and Services
ID:
ivo://ivoa.net/std/VODataService
Title:
VODataService: a VOResource Schema Extension for Describing Collections and Services
Date:
21 Oct 2016 08:20:00
Publisher:
IVOA
Description:
VODataService refers to an XML encoding standard for a specialized extension of the IVOA Resource Metadata that is useful for describing data collections and the services that access them. It is defined as an extension of the core resource metadata encoding standard known as VOResource [Plante et al. 2008] using XML Schema. The specialized resource types defined by the VODataService schema allow one to describe how the data underlying the resource cover the sky as well as cover frequency and time. This coverage description leverages heavily the Space-Time Coordinates (STC) standard schema [Rots 2007]. VODataService also enables detailed descriptions of tables that includes information useful to the discovery of tabular data. It is intended that the VODataService data types will be particularly useful in describing services that support standard IVOA service protocols.
100. VO-DML: a consistent modeling language for IVOA data models
ID:
ivo://ivoa.net/std/VODML
Title:
VO-DML: a consistent modeling language for IVOA data models
Date:
31 May 2018 09:00:00
Publisher:
IVOA
Description:
This document defines a standard modelling language, or meta-model, for expressing data models in the IVOA. Adopting such a uniform language for all models allows these to be used in a homogeneous manner and allows a consistent definition of reuse of one model by another. The particular language defined here includes a consistent identification mechanism for model which allows these to be referenced in an explicit and uniform manner also from other contexts, in particular from othe IVOA standard formats such as VOTable. The language defined in this specification is named VO-DML (VO Data Modeling Language). VO-DML is a conceptual modeling language that is agnostic of serializations, or physical representations. This allows it to be designed to fit as many purposes as possible. VO-DML is directly based on UML, and can be seen as a particular representation of a UML2 Profile. VO-DML is restricted to describing static data structures and from UML it only uses a subset of the elements defined in its language for describing "Class Diagrams". Its concepts can be easily mapped to equivalent data modelling concepts in other representations such as relational databases, XML schemas and object-oriented computer languages. VO-DML has a representation as a simple XML dialect named VO-DML/XML that must be used to provide the formal representation of a VO-MDL data model. VO-DML/XML aims to be concise, explicit and easy to parse and use in code that needs to interpret annotated data sets. VO-DML as described in this document is an example of a domain specific modeling language, where the domain here is defined as the set of data and meta-data structures handled in the IVOA and Astronomy at large. VO-DML provides a custom representation of such a language and as a side effect allows the creation and use of standards compliant data models outside of the IVOA standards context.