Subscribe to the gold package and get unlimited access to Shamra Academy
Register a new userSpace-Time Coverage in the VO Registry
144
0
0.0
(
0
)
Authors
Markus Demleitner
Ask ChatGPT about the research
No Arabic abstract
With VODataService 1.2, service providers in the Virtual Observatory (VO) have a reasonably straightforward way to declare where in space, time, and spectrum the data within a resource (i.e., service or data collection) lie. Here, we discuss the the mechanism and design choices, current limitations (e.g., regarding non-electromagnetic or solar system resources) as well as ways to overcome them. We also show how users and clients can already run queries against resource coverage using a scheme that is expected to become part of RegTAP 1.2 (or a separate standard). We conclude with an ardent plea to all resource creators to provide STC metadata -- only wide adoption will make this facility useful.
rate research
Read More
Modern studies of the Sun involve coordinated observations collected from a collage of instruments on the ground and in orbit. Each instrument has its own constraints, such as field of view, duty cycle, and scheduling and commanding windows, that must both be coordinated during operations and be discoverable for analyses of the resulting data. Details on the observed solar features, i.e. sunspots or filaments, and solar events, i.e. flares or coronal mass ejections, are also incorporated to help guide data discovery and data analysis pipelines. The Heliophysics Coverage Registry (HCR) provides a standards-based system for collecting and presenting observations collected by distributed, ground and space based solar observatories which form an integrated Heliophysics system. The HCR currently supports all instruments on the Interface Region Imaging Spectrograph (IRIS) and Hinode missions as well as associated ground-based observatories. Here we present an overview of the HCR along with details on how it provides scientists with tools to make flexible searches on observation metadata in coordination with searches of solar features and events.
In the Virtual Observatory (VO), the Registry provides the mechanism with which users and applications discover and select resources -- typically, data and services -- that are relevant for a particular scientific problem. Even though the VO adopted technologies in particular from the bibliographic community where available, building the Registry system involved a major standardisation effort, involving about a dozen interdependent standard texts. This paper discusses the server-side aspects of the standards and their application, as regards the functional components (registries), the resource records in both format and content, the exchange of resource records between registries (harvesting), as well as the creation and management of the identifiers used in the system based on the notion of authorities. Registry record authors, registry operators or even advanced users thus receive a big picture serving as a guideline through the body of relevant standard texts. To complete this picture, we also mention common usage patterns and open issues as appropriate.
Just as the astronomical Time Domain is a catch-phrase for a diverse group of different science objectives involving time-varying phenomena in all astrophysical regimes from the solar system to cosmological scales, so the Virtual Observatory is a complex set of community-wide activities from archives to astroinformatics. This workshop touched on some aspects of adapting and developing those semantic and network technologies in order to address transient and time-domain research challenges. It discussed the VOEvent format for representing alerts and reports on celestial transient events, the SkyAlert and ATELstream facilities for distributing these alerts, and the IVOA time-series protocol and time-series tools provided by the VAO. Those tools and infrastructure are available today to address the real-world needs of astronomers.
The Virtual Observatory Registry is a distributed directory of information systems and other resources relevant to astronomy. To make it useful, facilities to query that directory must be provided to humans and machines alike. This article reviews the development and status of such facilities, also considering the lessons learnt from about a decade of experience with Registry interfaces. After a brief outline of the history of the standards development, it describes the use of Registry interfaces in some popular clients as well as dedicated UIs for interrogating the Registry. It continues with a thorough discussion of the design of the two most recent Registry interface standards, RegTAP on the one hand and a full-text-based interface on the other hand. The article finally lays out some of the less obvious conventions that emerged in the interaction between providers of registry records and Registry users as well as remaining challenges and current developments.
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.
Log in to be able to interact and post comments
comments
Fetching comments
Sign in to be able to follow your search criteria
