The Earth rotates around its polar axis and orbits around the Sun:
the sky above us (the celestial sphere) is in constant apparent
motion. Stellarium is the perfect tool to demonstrate the motions of
the sky, the use of coordinates and to illustrate constellations.
Stars have different colors and luminosities. Following this tutorial
we will learn what star luminosity and color are, and which
information about stellar evolution we can obtain from them.
This tutorial will show how tabular data can be easily transferred
from Topcat to Aladin or the other way, and it will illustrate the
benefits of this inter-client communication for VO users. This is
shown with a quick look at filtering members of the Coma Cluster from
SDSS.
This tutorial is a dense course through the advanced functions of
TOPCAT and STILTS. It covers detailed information of how to use TOPCAT
and STILTS to find data in the VO, access them, perform crossmatches
and how to do visualisations.
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
This is a course on using the Virtual Observatory (VO), an
international research data infrastructure in Astronomy and
Astrophysics. Starting with a brief discussion of some general
concepts, it introduces some of the major client programs like TOPCAT
and Aladin, together with some simple discovery protocols. A first
focus topic is the query language ADQL, which is treated within the
equivalent of three lectures. The second major focus of the course is
the premier Python interface to the VO, pyVO, which is used to also
more deeply investigate the topics treated before. The course is
complemented by a number of side tracks, brief discussions of more
fundamental or more specialised VO topics.
The course comes with many exercises, most of which also have
solutions. We hope it is suitable for both self-study and as lecture
notes in teacher-led situations. In the latter case, it is designed to
work as a semester-long course with two hours of lectures and lab work
each per week.
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.
In this document, we discuss practices related to the use of RDF-based
consensus vocabularies in the Virtual Observatory, that is the creation,
publication, maintenance, and consumption of hierarchical word lists
agreed upon within the IVOA. To cover the wide range of use cases
envisoned, we define different vocabulary types for informal knowledge
organisation on the one hand, and strict hierarchies of classes and
properties on the other. While the framework rests on the solid
foundations of W3C RDF, provisions are made to facilitate using IVOA
vocabularies without specific RDF tooling. Non-normative appendices
detail the current vocabulary-related tooling.
New entries in the
`Virtual Observatory <http://www.ivoa.net>`_'s registry in RSS format;
this service lets you use a common "news aggregator" to learn of
services appearing in the VO in almost real time.
The data is taken from the VO registry by querying for new records
twice a day. New items are announced here for 30 days.
To subscribe to this feed, point your browser/news aggregator
to http://dc.g-vo.org/regrss.
If you can configure your client's update frequency, for this feed it
is sufficient to update every 12 hours -- it is only updated morining and
afternoon UTC.
New entries on this feed are also distributed `on the Fediverse`_. To
get notifications of new VO services, subscribe to `gavo@astrodon.social`_.
.. _gavo@astrodon.social:
.. _on the Fediverse: https://astrodon.social/@gavo