EDP Sciences
Gaia Data Release 1
Free Access
Issue
A&A
Volume 605, September 2017
Gaia Data Release 1
Article Number A52
Number of page(s) 16
Section Astronomical instrumentation
DOI https://doi.org/10.1051/0004-6361/201731059
Published online 07 September 2017

© ESO, 2017

1. Introduction

Visual data exploration plays a central role in the scientific discovery process; it is invaluable for the understanding and interpretation of data and results. From analysis to physical interpretation, most research tasks rely on or even require some kind of visual representation of data and concepts, either interactive or static, to be created, explored, and discussed. This is certainly the case of the ESA Gaia space mission (Gaia Collaboration 2016b), with its current and planned data releases (e.g. Gaia Collaboration 2016a). The particularity of Gaia is the volume – the number of sources and of attributes per source – of its data products, which makes interactive visualisation a non-trivial endeavour.

The Gaia Data Releases comprise more than 109 individual astronomical objects, each with tens of associated parameters in the earlier data releases, up to thousands in the final data release, considering the spectrophotometric and spectroscopic data which are produced per object and per epoch. The extraction of knowledge from such large and complex data volumes is highly challenging. This is a tendency that shows no sign of slowing down in the dawn of the sky surveys such as the LSST (Ivezic et al. 2008) and the ESA Euclid mission (Laureijs et al. 2011). As several authors have pointed out (e.g. Szalay & Gray 2001; Unwin et al. 2006; Hey et al. 2009; Baines et al. 2017), new science enabling tools and strategies are necessary to tackle these data sets; to allow the best science to be extracted from this data deluge, interactive visual exploration must be performed.

One essential issue is the inherent visual clutter that emerges while visualising these data sets. Although there can be millions or billions of individual entities that can be simultaneously represented in a large-scale visualisation, a naive brute-force system that simply displays all such data would not lead to increased knowledge. In fact, such a system would just hinder human understanding, due to the clutter of information that hides structures that may be present in the data (e.g. Peng et al. 2004). Thus, strategies have to be put in place to address the issues of data clutter and the clutter of the graphical user interface of the visualisation system (e.g. Rosenholtz et al. 2005).

Interactivity is also key for data exploration (e.g. Keim 2002). The ability to quickly move through the data set (e.g. by zooming, panning, rotating) and to change the representations (e.g. by re-mapping parameter dimensions to colours, glyphs, or by changing the visualised parameter spaces) are indispensable for productive exploration and discovery of structures in the data.

However, interactivity for large data sets is challenging (Goodman 2012) and current approaches require high-end hardware and having the data set locally at the computer used for the visualisation (e.g. Hassan et al. 2013). In the best cases, these systems are bounded by I/O speed (e.g. Szalay et al. 2008, for GPU-based visualisation of large-scale n-body simulations).

Another essential functionality for visual data exploration is the linking of views from multiple interactive panels with different visualisations produced from different dimensions of the same data set, or even of different data sets (e.g. Tukey 1977; Jern et al. 2007; Tanaka 2014). The simultaneous identification of objects or groups of objects in different parameter projections is a powerful tool for multi-dimensional data exploration (Goodman 2012, discusses this in a nice historical perspective). This surely applies to Gaia with its astrometric, photometric, and spectroscopic measurements (Lindegren et al. 2016; van Leeuwen et al. 2017; Katz et al. 2011) combined with derived astrophysical information such as the orbits of minor planets (Tanga et al. 2016), the parameters of double and multiple stars (Pourbaix 2011), the morphology of unresolved galaxies (Krone-Martins et al. 2013), the variable parameters of stars (Eyer et al. 2014), and the classifications and parameters of objects (Bailer-Jones et al. 2013).

Visualisation is not only for exploring the data, but also for communicating results and ideas. One of the most remarkable visualisations of our galaxy was created in the middle of the past century at the Lund Observatory1. It is a one-by-two-meter representation of the galactic coordinates of 7000 stars, overlaid on a painting of the Milky Way, represented in an Aitoff projection. This visualisation was produced by Knut Lundmark, Martin Kesküla and Tatjana Kesküla, and for decades was the reference panorama of our Galaxy. Another emblematic and scientifically correct visualisation of the Milky Way was produced from the data gathered by the ESA Hipparcos space mission, and published by ESA in 20132. This image represents, in galactic coordinates, the fluxes of ~ 2.5 million sources from the Tycho-2 catalogues. The Milky Way diffuse light, mostly created by unresolved stars and reflection or emission in the interstellar medium, is also represented. It was determined from additional data provided by background measurements from the Tycho star mapper on board the Hipparcos satellite. Minor additions of known structures not observed by Hipparcos (which just like Gaia was optimised to observe point sources) were made by hand. Now, the remarkable Gaia Data Release 1 (DR1) will deliver the next generation of Galactic panoramas, and will set our vision of the Milky Way galaxy probably for decades to come.

This paper introduces the Gaia Archive Visualisation Service, which was designed and developed to allow interactive visual exploration of very large data sets by many simultaneous users. In particular, the version presented here is tailored to the contents of DR1. The paper is organised as follows. First, in Sect. 2 the system concept is presented and the services described. Then, in Sect. 3 a brief overview of the deployment of the platform is given. Later, Sect. 4 presents a thorough description of the visual contents offered by the service and how they were created. Then, Sect. 6 addresses other visualisation tools with some degree of tailoring to Gaia data. Finally, some concluding remarks and planned developments for the near future are given in Sect. 7.

2. System concept

In addition to the central functionalities discussed above (e.g. interactivity, large data sets, linked views), many other features are required from a modern interactive visual data exploration facility. The Gaia Data Processing and Analysis Consortium (DPAC) issued an open call to the astronomical community requesting generic use cases for the mission archive (Brown et al. 2012). Some of these use cases are related to visualisation, and are listed in Appendix A of this paper. These cases formed the basis for driving the requirements of the Gaia Archive Visualisation Service (hereafter GAVS).

Visual queries.

In addition, GAVS introduces a new concept of how to deal with database queries: visual queries. Since the introduction of the Sloan Digital Sky Survey SkyServer and CasJobs infrastructures (e.g. York et al. 2000; Dawson et al. 2016), astronomers wanting to extract data from most modern astronomical surveys have been facing the need to learn at least the basics of the Structured Query Language, SQL, or more commonly of the Astronomical Data Query Language, ADQL (Ortiz et al. 2008), which is the astronomical dialect of SQL. These are declarative languages used to query the relational databases at the underlying structure of most modern astronomical data sources. Nevertheless, there are a multitude of querying tasks performed in Astronomy that should not require that these languages be mastered, for example spatial queries of data lying within polygonal regions of n-dimensional visual representation of tables. Accordingly, GAVS introduces to Astronomy a visual query paradigm; for Gaia it is possible to create ADQL queries directly from visual representations of data without having to write ADQL directly. The visual interface creates a query from a visual abstraction that can be used to extract additional information from the database. The visually created query string can be edited and modified, or coupled to more complex queries. It can be shared with other users or added to scientific papers, thus increasing scientific reproducibility.

2.1. Architecture

thumbnail Fig. 1

Static architecture diagram for the GAVS Server. It presents the components of the Server (Services, Plots Backend, Spatial Indexing, and Database Manager), how they are connected, and the context within the GAVS.

Open with DEXTER

From the architectural perspective, one of the fundamental requirements is that the interactive visual explorations of the whole archive should be possible with the common laptops, desktops, and (if possible) mobile devices available to most users.

The GAVS described here addresses this architectural issue by adopting a web service pattern. A server residing near the data is responsible for hiding as far as is possible the complexity and volume of the Gaia archive data from the user web interface. This avoids huge brute force data transfers of the archive data to the remote visualisation display that would congest the servers, the network, the user machine, and that in the end would not convey any additional scientific information. In a way, this reaffirms the concept of “bring the computation to the data” (Hey et al. 2009). However, the server can create an additional pressure on the archive, especially when several users access the service in parallel. To alleviate this pressure, the service includes caching mechanisms to prevent performance penalties from repeated requests and/or re-computations of the same data. This caching mechanism is active whether the request is being performed by the same user or not. While the server design is not tied to a specific hardware configuration, it pursues a scalable solution that can run on modest hardware (see Sect. 3).

The server was implemented as a Java EE application, designed to run in Apache Tomcat web containers. This application has two main functions, processing dynamic requests for interactive visualisation purposes and delivering static content to the user’s browser (images, CSS files, and client scripts).

The client side is a web application, designed in Javascript, HTML, and CSS to run in a web browser. Chrome and Firefox are the recommended platforms as these were the platforms used to test the service. Still, the client-side application should be compatible with any modern web browser.

The next two sections detail the server and client components of GAVS.

2.2. Visualisation Server

The structure of the Visualisation Server is depicted in Fig. 1. It is responsible for receiving and interpreting requests related to the different provided services (see Table 1) and responding accordingly.

The server’s components are divided into two different levels: the Services and the Plots Backend. The Services component receives REST requests (Fielding 2000), and performs checks to ensure the validity of the request and of its parameters. Then, it converts these parameters from the received text format to the correct abstractions and makes the necessary calls to the Plots Backend. Finally, it processes the answers of the Backend and adapts the replies to the visualisation client. The Plots Backend component processes the requests interpreted by the Services at a lower level, and is responsible for processing data, generating static images and image tiles, and calling further libraries as needed.

Spatial Indexing is a specialised module for indexing data in a spatial way, supporting an arbitrary number of dimensions and data points. Each specific visualisation will have its own separate index pre-computed (e.g. a scatter plot of galactic longitude and latitude will have an index built from those two coordinates). This pre-computation is key for providing interactivity. Scalability tests with the current implementation of the indexing were performed, indicating the feasibility of treating more than 2 × 109 individual database entries using a normal computer on the server side (16GB of RAM with a normal ~500 MB/s SSD attached to the SATAIII bus).

The indexing works in the following manner. First, the minimum and the maximum values are determined for each dimension of the data space being indexed. Based on this information, the root page of a tree is created. Then, data points are inserted into the root page one by one. If the number of data points in a page exceeds a certain configured threshold, the page is divided into children and the data points are also split among the child pages. The division of a page is performed by dividing each dimension by two; therefore, the number of children after a split will be 2d. In one dimension, each page is divided into two child pages, in two dimensions each page is divided into four child pages, and so on. When querying the index for data, only the pages that intersect the query range (in terms of area or volume, depending on the number of the dimensions of the index) are filtered, reducing significantly the amount of processing required.

The ideal threshold for the number of data points per page must be chosen taking into consideration that each page will always be retrieved from the database as a whole block. Accordingly, if this number is too high the amount of data retrieved from the database per request will be too big, even for spatial queries in small regions of the data space. On the other hand, if this threshold is too low, spatial queries will request a very high number of small blocks from the database. Both scenarios can hinder the performance of the application and prevent a satisfactory user experience on the client side. Our tests indicate that limiting the number of data points per page to the range 6–12 × 104 yields satisfactory response time for interactive visualisation.

Inside each page the data points are divided among different levels of detail. This is done for two main reasons: first, to prevent data crowding while producing the visual representation of the data (care is taken to avoid cropping or panning issues in the representation), and second, to keep the number of individual data points to be passed to the visualisation client and to be represented on the screen at a limit that permits the client side to experience interactivity.

Levels of details are numbered from 0 to n, with 0 being the level of detail containing the fewest data points or, in our terminology, the lowest level of detail. In our representation, the levels of detail are cumulative, i.e. level n + 1 includes all the data points of level n. Nonetheless, the data points are not repeated in our data structure, and any query processing just accumulates the data of each previously processed level up to the requested level of detail. The number of data points at each level of detail is 2d times the number of the previous one. For example, if the level of detail 0 has 500 data points, the level of detail 1 will have 2000, the level of detail 2 will have 8000 and so on. There are several ways in which the selection of points can be performed, but the most direct one, a simple random sampling, is known to present several advantages for visualisation. As discussed by Ellis & Dix (2007), among other features, it keeps spatial information, it can be localised, and it is scalable.

Storing the data structures and providing further querying functionalities require a final component, a Database Manager. The visualisation service described in this paper can use any Database Manager (e.g. MongoDB3, OrientDB4) that can provide at least the two most basic required functions, storing and retrieving data blocks. A data block is a string of bytes with a long integer number for identification. The internal data organisation within the database is irrelevant for indexing purposes. The present implementation of GAVS, tailored to DR1, adopts our own Java-optimised NoSQL Database.

While tree indexation is common in multi-dimensional data retrieval, the specific indexing and data serving schemes developed here are, to the best of our knowledge, unique in systems for interactive visualisation of (large) astronomical tables.

Table 1

Role of the services provided by the server side.

2.3. Web client

thumbnail Fig. 2

Client architecture diagram providing the structure and context in GAVS. The Client is structured in a Model-View-Controller design expressed in the Directives, Controllers, and Services modules.

Open with DEXTER

Table 2

Role of the services, directives, and controllers that compose the architecture of the client side.

The structure of the web client is depicted in Fig. 2. The client is responsible for the user interaction with the visualisation service and thus for the communication between the user’s computer and the visualisation server.

The Client is a single-page application structured in a Model-View-Controller (MVC) design pattern. Accordingly, the Client is divided into three major components:

  • the directives that manipulate the HTML and thus serve data to theclient’s display;

  • the services that communicate directly with the server side through REST requests;

  • the controller that works as the broker between the services and the directives.

The components, available services, and the specifications of each individual role are described in Table 2.

Grids of windows providing different functionalities can be created on the client web page using the gridster.js5 framework. Using these windows, the Visualisation Service deployed for DR1 provides the following types of plots: 1D histograms, 2D scatter plots, and the JS96 (FITS viewer) and Aladin lite7 (HiPS viewer) plug-ins. Options and configurations for each plot are available in modal windows that appear superposed on the main web page when requested.

The 1D histograms are visualised (but not computed) using the d3.js8 library. This library provides tools for drawing the histogram bins and axes. For 1D histograms, the client requests the bin values to the Server, specifying the number of bins and the maximum and minimum limits over which to compute the histogram. The Server then calculates the number of points in each bin and replies these values to the client using a JSON object. Performance at the server side is improved by not counting every single data point in the data set. If the limits of a data page in the index fall within the limits of a bin, the pre-computed total number of points of the page is used, instead of iterating over every data point. This provides quick response times, allowing to interactively change bin limits and sizes, even for the over one billion points in DR1.

The 2D scatter plots are produced using the leaflet9 interactive map library. This library is specialised in tile-based maps and has a small code footprint. The Server application generates the tiles from projections of the data based on client-side requests. The client side then uses these tiles via leaflet to display them to the user. The axes of the scatter plots are created following the same underlying logic and libraries as the 1D histograms, providing a homogeneous user experience throughout the visualisation service. Finally, the client-side application also supports additional overlays with interactive layers and vector objects.

3. Deployment

The entire development and prototyping phase of the service was performed using a virtual machine infrastructure at ESAC, together with a physical set-up at the Universidade de Lisboa.

The visualisation web service is deployed at ESAC in a dedicated physical machine. This service came online together with the Gaia DR1. It has been in continuous operation since the moment the archive went public on September 14, 2016.

The service is accessible through the Gaia Archive portal10, in a special pane dedicated to the online visual exploration of the data release contents. It can also be accessed via a direct link11.

The fundamental configuration and characteristics of the operational infrastructure are

  • CPU: Intel(R) Xeon(R) E5-2670 v3 @ 2.30GHz, 16 cores;

  • memory: 64 gigabytes;

  • storage: 3 TB SSD;

  • application server: Apache Tomcat 8;

  • Java version: 1.8.

The software and hardware deployed for the Visualisation Service proved robust. It has not crashed even once in the several months it has been online, despite several heavy access epochs, and also considering that the service is sustained by a single physical machine.

In the first four hours after starting online operations, the visualisation service had already served more than 4286 single users. These users created and interacted with 145 1D histograms and 5650 2D scatter plots, which triggered the generation of >1.5 × 106 different tiles12.

By the end of the DR1 release day, over 7500 individual users had been logged and interacted with the visualisation service.

thumbnail Fig. 3

Outline of the steps followed when creating visualisations for distribution and for viewing with external applications. It covers the creation of the DR1 poster image in various formats as well as HiPS and and FITS files.

Open with DEXTER

4. Contents produced for DR1

In the service deployed for DR1, the visualisation index pre-computations (Sect. 2.2) are determined by the GAVS operator. Hence, the GAVS portal serves a predefined list of scatter plots and histograms:

  • 1D histograms

    • GDR1 data: galactic latitude; galactic longitude; G mean magnitude; G mean flux.

    • TGAS data: parallax; proper motion in right ascension; proper motion in declination; parallax error; proper motion modulus.

  • 2D scatter plots

    • GDR1 data: galactic coordinates; equatorial coordinates;ecliptic latitude and longitude.

    • TGAS data: parallax error vs. parallax; proper motion in declination vs. proper motion in right ascension; colour magnitude diagram (GKs vs. G, with Ks from 2MASS).

In addition to the interactive scatter plots and histograms that can be explored in the visualisation portal, the service has also produced content for distribution or for viewing with other specialised software. It is made available at GAVS under the “Gallery” menu item. Here we list that other content and briefly describe how it was created:

  • all-sky source density map in a plane projection. This is the DR1poster image shown in GaiaCollaboration (2016a) and available in severalsizes, also with annotations13;

  • a similar map, but for integrated (logarithmic) G-band flux. It is shown and discussed below;

  • several zoom-ins of regions of interest, re-projected centred on those regions. Employed as presentation material. Two examples are shown and discussed below;

  • all-sky HiPS maps of source density and integrated (logarithmic) G-band flux for viewing with the Aladin Lite plug-in at the Archive Visualisation Service;

  • all-sky low-resolution FITS map in a Cartesian projection with WCS header keywords for viewing with the JS9 plug-in in the Archive Visualisation Service;

  • FITS images of selected regions in orthographic projection with WCS header keywords;

  • large format all-sky source density and integrated flux maps for projection in planetaria.

Images are produced with the pipeline presented in Fig. 3. The pipeline is written in Python. The input data are stored in tabular form in the file system. Schematically, the steps are as follows:

  • 1.

    Data are read in blocks. This allows images to be produced fromtables of arbitrary sizes, larger than would fit in memory, as long asthere is enough disc storage space. The pipeline uses the Pythonpackage Pandas14 in this process.

  • 2.

    The computation of the statistic to be visualised requires partitioning the celestial sphere in cells. The Healpy15 implementation of the Hierarchical Equal Area isoLatitude Pixelation (HEALPIX, Gorski et al. 2005) tessellation is used for this purpose. Each source is assigned a HEALPix from its sky coordinates. The statistic can be simply the number of sources in the cell, the integrated luminous flux of sources in the cell, or any other quantity that can be derived from the source attributes listed in the input table. The statistics determined for the data blocks are added to a list of values for each HEALPix. Averaged or normalised statistics (e.g. number of sources per unit area) are only computed in the end to avoid round-off errors. Finally, the central sky coordinates of each HEALPix are determined and a list of the statistics for those coordinates is produced.

  • 3a.

    The statistics determined on the sphere are represented on a plane. Because the sphere cannot be represented on a plane without distortion, many approaches exist for map projections (Synder 1993). The Hammer projection, used to produce the DR1 image, is known to be an equal-area projection that reduces distortions towards the edges of the map. The projection results in x, y positions in a 2:1 ratio with x confined to (–1, 1). The zoomed images use an orthographic–azimuthal projection, which is a projection of points onto the tangent plane.

  • 4.

    The x, y coordinates of the map projection are re-sampled (scaled and discretised) onto a 2D matrix with a specified range (image dimensions in arcminutes) and number of pixels in each dimension. The number stored in each pixel corresponds to the combined statistics of the HEALpix that fall in the pixel. Because the HEALPix and pixels have different geometries, they will not match perfectly. It is thus important that the pixel area should be substantially larger than the HEALPix area, i.e. that each pixel includes many HEALPix to minimise artefacts due to differences in the areas covered by both surface decompositions. In the case of the Hammer projection, we have found that a pixel area 32 times larger that the HEALPix area will keep artefacts at the percent level. Given the 2:1 aspect ratio of the Hammer projection, this corresponds to an average of 8 × 4 HEALpix per pixel.

  • 5.

    The image is rendered from the matrix built in the previous step. There are many libraries available, but only a few produce images with 16 bit colour maps. This is required to produce high-quality images with enough colour levels (65 536 levels of grey, compared to 256 levels for 8 bit images) to go through any post-processing that might be desirable for presentation purposes. Here the pyPNG16 package is used. The output is a PNG image.

  • 3b.

    HiPS and FITS image files are produced. Healpy can create FITS files with HEALPix support (embedded HEALPix list and specific header keywords) directly from the HEALPix matrix produced in step 2 of the image pipeline. HiPS images were then created from the HEALPix fits file with the Aladin/Hipsgen code following the instructions in http://aladin.u-strasbg.fr/hips/HipsIn10Steps.gml. The input data were mapped into HiPS tiles, without resampling, using the command java -Xmx2000m -jar Aladin.jar in=“HealpixMap.fits”. While this method allows a quick and easy creation of HIPS files, it does not handle well very high resolutions. To illustrate the issue, for a nside of 213 = 8192 the HEALPixs array has a length of 805306368, while for a nside of 214 it has a length of 3221225472. The DR1 HiPS maps provided in the Visualisation portal have a base nside of 8192. Regarding JS9, a javascript version of the popular DS9 FITS viewer17, the deployed version (1.9) does support HEALPix FITS files. For JS9, the HEALPIx map was directly projected on the Cartesian plane and converted to FITS using the Astropy18 FITS module astropy.io.fits.

The DR1 poster image (Gaia Collaboration 2016a) is available in several sizes19, also with annotations. It is a Hammer projection of the Galactic plane represented in galactic coordinates. This specific projection was chosen in order to have the same area per pixel.

The images of different sizes are scaled versions of a baseline image of 8000 × 4000 pixels, which corresponds to an area of ~ 5.901283423 arcmin2 per pixel. As explained above, the plane projected images are created from higher resolution HEALPix matrices. In this case, an NSIDE = 8192 was used, which corresponds to an area of 0.184415106972 arcmin2 per HEALPix or (~8 × 4) 32 HEALPix per pixel.

The greyscale represents the number of sources/arcmin2. In Gaia Collaboration (2016a) a scale bar is presented together with the map. The maps mentioned above, which are available at the ESA website, are based on a logarithmic scale followed by some post-processing fine-tuning of the scale with an image editing program. As noted in Gaia Collaboration (2016a), the scales were adjusted in order to highlight the rich detail of Galactic plane and the signature of the Gaia scanning.

The maximum density is slightly higher than 260 sources/ arcmin2 1.000.000 sources/degr2. The minimum is 0, but this mostly due to gaps in certain crowded regions where no sources have been included in DR1, noticeably the stripes close to the Galactic centre. Not considering these missing parts with zero density, the minimum at this resolution is about ~300 sources/degr2.

As mentioned above, an all-sky logarithmic integrated G flux map was also produced. It is shown in Fig. 4 together with the density map for comparison. While the density map highlights dense groups of stars, even very faint stars at the limiting magnitude, the flux map can highlight sparse groups of bright stars. This explains why the density map is so full of detail. Many very faint but dense star clusters and nearby galaxies are easily seen. Features in the dust distribution also become prominent as they create pronounced apparent underdensities of stars. It also explains why the striking Gaia scanning patterns in the density map are mostly absent in the flux-based map. As discussed in Gaia Collaboration (2016a), the patterns are an effect of incompleteness which affects mostly the faint end of the survey. This is confirmed with the density map in the lower panel of Fig. 4, which was built from sources brighter than G = 20 mag and shows many fewer scanning footprints.

thumbnail Fig. 4

All-sky maps of DR1: integrated flux (top), density (middle), density for sources brighter than G = 20 mag (bottom).

Open with DEXTER

thumbnail Fig. 5

12° × 10° density (left) and integrated flux (right) maps of the LMC.

Open with DEXTER

This illustrates how these density and flux-based maps provide complementary views, where one reveals structures that are not seen in the other. This is further illustrated in Fig. 5, which is a zoom into a field of ~12° × 10° centred on the LMC. Here the LMC bar and arms are seen differently in the two images. The density map displays scanning artefacts, specially in the bar, but also reveals many faint star clusters and clearly delineates the extent of the arms. The structure of the bar and the 30 Doradus region (above the centre of the images) are better revealed by the bright stars that dominate the flux-based image. It is worth noting that despite its photo-realism, this is not a photograph, but a visualisation of specific aspects of the contents of the DR1 catalogue.

thumbnail Fig. 6

15° × 11° field centred on the Orion-A region. Density (top left) and integrated flux (bottom left) maps with DR1 data. Coloured DSS (top right) and 2MASS (bottom right) images of the same field. The DR1 images reveal a cat-like structure created by an extinction patch, highlighting how the mere positions in DR1 can already reveal structures not seen in currently available optical and near-infrared images.

Open with DEXTER

While the astrophysical interest of Orion cannot be overstated, it also provides a highlight of how even though Gaia is an optical mission, the mere positions of the stars published in DR1 can reveal structures not yet revealed by other surveys. Figure 6 shows four panels of a ~ 15° × 11° field centred on the Orion-A cloud. The two panels on the left are DR1 density (upper) and flux (lower) maps. The panels on the right are coloured DSS (upper) and 2MASS (lower) images of the same field. The sources in the DR1 maps delineate a distinctive extinction patch that closely resembles a cat20 flying or jumping stretched from the left to the right, with both paws to the front. This structure is not seen in currently available optical and near infrared images, except for the shiny “nose” and the cat’s “left eye”.

Finally, to end this section, large 16 384 × 8192 pixel density and integrated flux maps in a Cartesian projection have been produced for display in planetaria. They are currently employed in several Digistar21 planetaria around the world.

5. Workflows

An online GAVS Quick Guide can be consulted under the “Help” menu button. The guide describes the full set of functionalities offered by GAVS. It includes explanations of the basic capabilities such as adding new visualisation panels, types of visualisations, presets, and configurations. It also covers more advanced features such as creating (and sharing) geometrical shapes for marking regions of interest, overlaying catalogues of objects, and generating ADQL visual queries.

This section gives a few examples of workflows using GAVS. More examples and details on the user interface can be found in the online guide.

thumbnail Fig. 7

Workflow for producing a visual ADQL query. Top panel: user selects a region to centre the view (top). Middle panel: selected polygonal region is shown in green. Region menu with the ADQL functionality also displayed. Bottom panel: resulting ADQL query.

Open with DEXTER

Figure 7 illustrates a workflow for centring on a field of interest (using the Sesame name resolver), marking a region, and producing an ADQL query that can be pasted into the archive query interface. In the first step (top panel) the user clicks on the lens icon in the top right corner of the window and enters the name of a region or object (in this example, Ophiuchus). The visualisation window will centre the field on the region if the CDS Sesame service can resolve the name. Alternatively, instead of a name, central coordinates can be used as input. Afterwards, the user clicks on the “Regions” menu of the visualisation window in the top left, and selects a polygonal region or rectangular region. The user then creates the region using the mouse, e.g. by clicking on each vertex of the polygon, and closing the polygon at the end (middle panel). Finally, the user clicks again on the “Regions” menu and selects the “ADQL” option. This will result in the creation of an ADQL query that is presented to the user (bottom panel). Behind the scenes, the software validates the resulting ADQL query before presenting it to the user, assuring that it is correctly constructed. The user can now run this query as is at the Gaia Archive search facility, or can customise it (e.g. to select which data columns to retrieve from the table or to perform a table join) before submitting it to the archive.

thumbnail Fig. 8

Archive and Simbad searches of object of interest.

Open with DEXTER

Figure 8 illustrates the functionality for archive and Simbad cone searches around objects of interest and also generates an ADQL query-by-identifier for the select object. At any visualisation panel, when the user clicks twice (not double-click) on an object, the system displays a dialog box with some options. These options, shown in Fig. 8, identify the selected Source ID from DR1 and give the possibility of generating an ADQL query with this source ID for retrieving further information from the archive. This dialog box also gives the option of retrieving more information from CDS/Simbad or of generating an ADQL cone search query centred on the selected source.

Figure 9 shows catalogues of open clusters (Dias et al. 2002, Version 3.5, Jan. 2016), globular clusters (Harris 1996), and nearby dwarf galaxies (McConnachie 2012) uploaded by the user and overlaid on a scatter plot of the DR1 sources in Galactic coordinates. To upload a catalogue of regions, the user must click on the “Regions” menu, at the top left of the visualisation window, then select the “Load Regions” options, and select the region file to be uploaded (we note that the user can save any region created earlier by using the “Save Regions” option). To overplot points, the region catalogues must be formatted as region files with points. An example file can be copied from the region file built from the catalogue of open clusters22.

6. Other Gaia oriented visualisation tools

This section provides a small list of applications or services that were identified as having been developed or improved with the exploration of Gaia in mind, and that offer features that complement those of the Archive Visualisation service. It does not intend to be a complete survey of visualisation tools for exploring Gaia data.

CDS/Aladin.

The CDS has an area dedicated to Gaia23. In par- ticular, a page for exploring a DR1 source density HiPS map in Aladin Lite, with optional overlay of individual sources from DR1, TGAS, and SIMBAD is offered24. The HiPS density map with different HEALPix NSIDE builds can also be downloaded25.

ESASky26.

Gaia catalogues are available in ESASky (Baines et al. 2017), allowing users to visually compare them with other science catalogues from other ESA missions in an easy way. In this case, users can overplot the Gaia DR1 and TGAS catalogues on top of any image from Gamma-ray to radio wavelengths, click on any single source in the image to identify it in a simplified results table below, and retrieve the selected table as a CSV file or as a VOtable. To cope with potentially slow retrieval times for large fields of view, the resulting table from any search is sorted by median G-magnitude; only the first 2000 sources are found and it is not possible to select more than 50 000 sources. In the future, ESASky will develop a more sophisticated way to display many sources for large fields of view.

thumbnail Fig. 9

User catalogue of open clusters, globular clusters, and nearby dwarf galaxies overlaid on a scatter plot of the DR1 sources in galactic coordinates.

Open with DEXTER

Gaia-Sky27

is a Gaia-focused 3D universe tool intended to run on desktop and laptop systems; its main aim is the production of outreach material. Gaia-Sky provides a state-of-the-art 3D interactive visualisation of the Gaia catalogue and offers a comprehensive way to visually explain different aspects of the mission. The latest version contains over 600 000 stars (the stars with relevant parallaxes in TGAS). The upcoming versions will be able to display the 1 billion sources of the final Gaia catalogue. The application features different object types such as stars (which can be displayed with their proper motion vectors), planets, moons, asteroids, orbit lines, trajectories, satellites, or constellations. The pace and direction of time can also be tuned interactively via a time warp factor. Graphically, it makes use of advanced rendering techniques and shading algorithms to produce appealing imagery. Internally, the system uses an easily extensible event-driven architecture and is scriptable via Python through a high-level Aplication Programming Interface (API). Different kinds of data sets and objects can also be loaded into the program in a straightforward manner thanks to the simple and human-readable JSON-based format. The system is 3D ready and features four different stereoscopic profiles (cross-eye, parallel view, anaglyphic, and 3DTV); it offers a planetarium mode able to render videos for full-dome systems and a newly added 360° panorama setting which displays the scene in all viewing directions interactively. Gaia Sky is an open source project, it is multi-platform and builds are provided for Linux (RPM, DEB, AUR), Windows (32 and 64 bit versions) and OS X.

TOPCAT.

Taylor (2005) is a desktop Graphical User Interface (GUI) application for manipulation of source catalogues, widely used to analyse astronomical data28. One of its features is a large and growing toolkit of highly flexible 1D, 2D, and 3D visualisation options, intended especially for interactive exploration of high-dimensional tabular data. It is suitable for interactive use with hundreds of columns and up to a few million rows on a standard desktop or laptop computer. It can thus work with the whole of the TGAS subset, but not the whole Gaia source catalogue. The visualisation capabilities are also accessible from the corresponding command-line package, STILTS (Taylor 2006), which can additionally stream data to generate visualisations from arbitrarily large data sets provided there is enough computer power.

None of TOPCAT’s visualisation capabilities are specific to the Gaia mission, but part of the development work has been carried out within the DPAC, and has accommodated visualisation requirements arising from both preparation and anticipated exploitation of the Gaia catalogue. New features stimulated to date by the requirements of Gaia data analysis include improved control of colour maps; options for assembling, viewing, and exporting HEALPix maps with various aggregation modes; options to view pre-calculated 2D density maps, for instance produced by database queries; improved vector representations, for instance to depict proper motions; plots that trace requested quantiles of noisy data; and Gaussian fitting to histograms. Though developed within the context of Gaia data analysis, all these features are equally applicable to other existing and future data sets.

Vaex.

Breddels (2017) is a visualisation desktop/laptop tool written with the goal of exploring Gaia data29. It can provide interactive statistical visualisations of over a billion objects in the form of 1D histograms, 2D density plots, and 3D volume renderings. It allows large data volumes to be visualised by computing statistical quantities on a regular grid and displaying visualisations based on those statistics. From the technical point of view, Vaex operates as a HDF5 viewer that exploits the possibilities of memory mapping those files and binning the stored data previous to the rendering and display. However, the full exploration of the over a billion objects requires that the variables of each plot are all loaded in memory. This has the effect of requiring high-end machines, with large amounts of RAM for multi-panel visual exploration of the full DR1. Vaex also operates as a Python library.

Glue.

Beaumont et al. (2015) is a Python library for interactive visual data exploration. While not specifically developed for Gaia, a number of uncommon features make Glue deserve a special mention here. It supports the analysis of related data sets spread across different files: a common need of astronomers when analysing data from various sources, including their own observations. A key characteristic is the ability of creating linked views between visualisations of different types of files (images and catalogues). Glue offers what the authors call hackable user interfaces. This means providing GUIs, which are better for interactive visual exploration, and an API, which is better suited to expressing and automating the creation of visualisations, allowing simple integration in Python notebooks, scripts, and programs. Among other features, Glue also provides advanced capabilities of 3D point cloud selection and support for plug-ins.

7. Concluding remarks and future developments

Online, fully interactive, and free visual exploration of the Gaia-sized archives up to the last of each of the more than 109 individual entries was something not offered by any service in the world. This scenario has changed with the Gaia Archive Visualisation Service for Data Release 1 presented in this paper. In addition to being used for scientific data exploration and public presentation, the GAVS has also been employed in the validation of DR1 (Arenou et al. 2017).

The software architecture, design, and implementation have proved highly stable throughout the past months, and is capable of serving a fully interactive visual exploration environment of the Gaia archive to thousands of users.

This work has also been extending the application of visual abstractions of astronomical data sets. It introduces for the first time the simple but powerful concept of a visual query. This visual query directly generates ADQL queries from visual abstractions of the data and tables. It effectively enables any researcher to create complex queries, which can later be executed against ADQL compliant databases such as the one provided by the Gaia Archive. This concept will be evolved in the future to enable even more complex queries, performed through multiple tables, to be built with no knowledge of the ADQL and SQL languages.

Gaia Data Release 2 will bring a multitude of new parameters. From the astrometric point of view, proper motions, and parallaxes for most of the more than one billion objects will be available. By building on top of concepts and prototypes developed during an exploratory ESA project (code name IVELA: Interactive Visualisation Environment for Large Archives), future versions of the Visualisation Service will provide 3D point cloud interactive visualisation, allowing a fully online 3D navigation and exploration of the release contents.

The future versions of GAVS will also bring useful features such as annotation tools, various image formats for exportation, and new plot types, such as 2D raster plots (e.g. histograms, density plots) and specialised panels for the analysis of time series, all prepared for very large data sets. Triggering of visualisation pre-computations by users is under analysis.

Also planned is the extension of GAVS to serve visualisation data (indexes, levels of detail, linked views, and more metadata) to other applications beyond the current web client/portal. The baseline is currently a REST API, with wrappers planned for Python and other languages. Advanced data analysis will then become possible with tools (e.g. Glue) that otherwise would not be able to handle the volume of the Gaia Archive, but the data feeds do not have to be limited to data analysis frameworks. The success of DR1 has demonstrated the high level of interest among the general public in the Gaia mission. It would thus also be natural to feed education and outreach Universe exploration tools such as Gaia-Sky or the World Wide Telescope30.

Finally, further ahead, a future which includes a deeper articulation with virtual organisations such as the Virtual Observatory seems unavoidable. In the light of this paradigm, it is only natural that code should be brought close to the data, and not the other way around. Accordingly, there have been studies, designs, and developments of platforms such as the Gaia Added Value Platform (GAVIP; Vagg et al. 2016), which would allow codes, for instance Python, to run near the Gaia data. The Visualisation functionality of the GAVIP platform, known as the Gaia Added Value Interface for Data Visualisation (GAVIDAV), has been developed in close contact with the Gaia Archive Visualisation Services. This proximity will enable any application running on such a platform, and thus near the Gaia Archive, to profit from many of the large-data visualisation capabilities of the tools described in this paper, thus bringing the power of visually exploring billions of database entries to the hands of any astronomer or human being, regardless of the levels of resources available in their country or institution.


12

The caching mechanism prevents a tile from being created twice.

20

At public presentations, some members of the audience have suggested that it is a fox. We are currently re-analysing the data and taking a deeper look into this issue.

31

The document can be accessed at http://www.rssd.esa.int/doc_fetch.php?id=3125400

Acknowledgments

The authors greatly appreciated the constructive comments by the referee, Alyssa Goodman. This work has made use of results from the European Space Agency (ESA) space mission Gaia, whose data were processed by the Gaia Data Processing and Analysis Consortium (DPAC). Funding for the DPAC has been provided by national institutions, in particular the institutions participating in the Gaia Multilateral Agreement. The Gaia mission website is http: //www.cosmos.esa.int/gaia. The authors are current or past members of the ESA Gaia mission team and of the Gaia DPAC. This work has received financial support from the European Commission’s Seventh Framework Programme through the grant FP7-606740 (FP7-SPACE-2013-1) for the Gaia European Network for Improved data User Services (GENIUS); from the Portuguese Fundação para a Ciência e a Tecnologia (FCT) through grants PTDC/CTE-SPA/118692/2010, PDCTE/CTE-AST/81711/2003, and SFRH/BPD/74697/2010; from the Portuguese Strategic Programmes PEstOE/AMB/UI4006/2011 for SIM, UID/FIS/00099/2013 for CENTRA, and UID/EEA/00066/2013 for UNINOVA; from the ESA contracts ESA/RFQ/3-14211/14/NL/JD and ITT-AO/1-7094/12/NL/CO Ref.: B00015862. This research has made use of the Set of Identifications, Measurements, and Bibliography for Astronomical Data (Wenger et al. 2000) and of the “Aladin sky atlas” (Bonnarel et al. 2000; Boch & Fernique 2014), which are developed and operated at Centre de Données astronomiques de Strasbourg (CDS), France. X.L. acknowledges support by the MINECO (Spanish Ministry of Economy) – FEDER through grant ESP2014-55996-C2-1-R, MDM-2014-0369 of ICCUB (Unidad de Excelencia “María de Maeztu”). This publication made use of data products from the Two Micron All Sky Survey, which is a joint project of the University of Massachusetts and the Infrared Processing and Analysis Center/California Institute of Technology, funded by the National Aeronautics and Space Administration and the National Science Foundation. Thomas Boch and Eric Mandel are warmly thanked for their always friendly assistance in integrating the Aladin Lite and JS9 plug-ins, respectively.

References

Appendix A: Gaia Data Access Scenarios related to visualisation

This appendix lists a subset of the Gaia Data Access Scenarios (Brown et al. 2012)31 that are related to visualisation and that were used to drive the design of the system presented in this paper.

  • GDAS-BR-10: I would like to be able to select objects based on anyset of the variables provided in the Gaia catalogue position,parallax, astrophysical parameters, proper motionuncertainties, etc. These selections should not be limited tosimple “axis-parallel” cuts or cone cuts, but permit a broaderarray of functions/functional dependencies. An example isselection of fractional parallax error and some relation betweenG magnitude and extinction. Another is selection on space velocities, which requires a combination of position, parallax, and proper motion.

  • GDAS-BR-07: I want data of all objects contained in a rectangular/circular region centred on a given sky position.

  • GDAS-GA-02: I would like to query the Gaia catalogue in some peculiar Galactic directions and retrieve the (U, V, W) velocities of the stars relative to the Sun when possible, together with their distance, metallicity, and error bars.

  • GDAS-ST-25: I want to display the information for a given source (for variability analysis): source attributes (e.g. mean magnitude, mean colour, period, amplitude, etc.), light curve, folded light curve, frequency gramme.

  • GDAS-ST-06: Proximity Queries: I would like to select targets in rectangle, polygon, ellipse; select objects in this circular part of the sky that are closer to target X than to target Y; coordinate systems: equatorial, ecliptic, galactic.

  • GDAS-EG-08: I want all quasars observed so far with Gaia to be plotted on the celestial sphere.

  • GDAS-GA-15: I would like to retrieve the astrometric and photometric data concerning any star hosting planets. I need positions, proper motions, parallaxes, and radial velocities (if available) and the associated covariance matrices.

  • GDAS-BR-16: Interactive plots (2D/3D zooming and rotation). I would like to have the possibility to select any attribute for any axis and customise the plot in that way; e.g. selecting mean values for colour and magnitudes, the user can produce the HR diagram. It should be possible to make a selection of points and store the set of sources for other plots or analysis. Aggregated plots: when the number of objects is huge, the data has to be aggregated for better visualisation. Kinds of aggregation plots include: IQR plot, Histogram, Mosaic plots, Bubble plots, Density plots. These aggregated plots are meant to analyse large sets of data without plotting detailed information for all sources.

  • GDAS-BR-02: Show me the area of sky which Gaia will be observing on any particular date.

  • GDAS-GA-04: I want whatever measurements of MW G2 stars only in a given sky region.

  • GDAS-PR-03: I want to make a movie of a flight through the Milky Way disc, respecting the distances and apparent luminosity of objects.

  • GDAS-PR-08: I want to produce user friendly interfaces to the Gaia data base which can even be used by students at school or citizen scientists.

  • GDAS-ST-05: Standard Queries: filter operations (==, !=, <, >, , ), combination logic (AND, OR, NOT, XOR); quite often a group of targets to be queried is not aligned along the axes of the parameter space provided by the Archive. Therefore linear combinations of quantities should also be queriable, e.g. 3 ≤ aX + bY + cZ ≤ 4 with a,b,c provided by the user and three X,Y,Z quantities archived for every star.

  • GDAS-GA-03: I want whatever measurements there are of Milky Way objects only in a given sky region.

  • GDAS-BR-15: I would like to be able to do on-the-fly smoothing/averaging of the data such that queries can be composed giving properties per spatial bin, e.g. binned in 1 arcmin elements.

  • GDAS-SA-01: I want to get all microlensing events detected in real time by Gaia and see their photometric light curves and astrometric curves.

  • GDAS-BR-14: I would like to be able to visualise the Gaia catalogue in multi-dimensional space preferably utilising a visualisation engine such as Google Sky or World Wide Telescope such that I can incorporate data from other surveys into the same tool.

  • GDAS-BR-06: I liked the statistical plots presented in Sect. 3 of Vol. 1 of the Hipparcos and Tycho Catalogues. Show me the same for Gaia and allow me to specify the statistic to explore.

  • GDAS-BR-09: I want to manipulate a 3D cube of the Milky-Way.

  • GDAS-GA-14: I would like to analyse the 5D, 6D phase space structure of stellar populations selected by magnitude, colour, abundances in a galactocentric (cylindrical) coordinate system.

  • GDAS-PR-01: For my named constellation, fly me along the line of sight giving me information of interest on each star as I pass it.

  • GDAS-ST-24: Find binary stars with specific colours where the colours of one or both of the binaries can be specified.

  • GDAS-ST-07: Fuzzy Queries. Most quantities in Gaia archive will have errorbars. This is relevant for queries, e.g. asking for all stars with Teff ≤ 4000 K would not include a star with Teff = 4050 ± 250 K. Fuzzy querying should allow this. Required for each quantity: the value, a standard deviation (errorbar), and a probability distribution for this quantity. Most often this will be a Gaussian distribution, but this may not always be the case, particularly if a quantity was computed by dividing two Gaussian quantities. A fuzzy query could add a qualifier to the request: almost certain (P> 90%), likely (70% ≤ P ≤ 90%), perhaps (30% ≤ P< 70%), unlikely (10% ≤ P< 30%), almost certainly not (P< 10%). The probabilities are computed using the density; the exact definition of the qualifiers could be configured by the user.

  • GDAS-GA-17: I would like to compare the spatial distribution and dynamics of open star clusters with numerical simulations.

  • GDAS-OA-18: I would like to use standard analysis and visualisation tools Aladin, Topcat, IDL, Python and compare Gaia data with data available in VO standard.

  • GDAS-OA-05: If probabilistic (Bayesian) methods were used to arrive at a particular parameter value please provide the full probability density function and not just value+error.

  • GDAS-ED-01: For my list of stars based on some ground-based observations or catalogue, give me SM CCD image thumbnails.

  • GDAS-SA-03: Fermi has detected a flaring blazar. It has a certain error ellipse, e.g. a few arc-minutes. An optical counterpart is not known. How can I get lightcurves for all objects in the error-ellipse to look for variability and thus possible counterparts to the blazar?

  • GDAS-GA-12: I want a face-on view of the velocity field(s) of any Galactic objects.

  • GDAS-OA-01: I have a sophisticated simulation code that produces full phase-space realisations of the stellar content of some fraction of the Milky Way. I want to vary certain inputs to my model that are of astrophysical interest and compare against the full Gaia catalogue. Provide me with the means to do this.

  • GDAS-GA-20: (same as GDAS-BR-11) I would like to make selections of Gaia objects based not only on Gaia data, but also based on other major catalogues available at that time, such as Pan-STARRS and SDSS.

  • GDAS-BR-05: I want a pretty colour picture for my power-point presentation, created using Gaia data. For example, I would like to select all stars belonging to the halo of the Milky Way and colour them according to their 6D phase space information, assigning to each group its own colour. Then I want to project this on the sky in ecliptic coordinates or any other I choose so that I can illustrate how the halo is structured and where the streams are, or to make a picture like the one from the SDSS, but with Gaia data. I would also like to be able to put labels with the stream names and then save that picture in one of the most common formats without having to actually download the data on my computer.

  • GDAS-ST-03: I want to find clusters of stars in the following way: I select a core set of the stars in the catalogue. The archive then finds me stars that are “similar” in distance, proper motion, radial velocity, etc. For all these parameters I can set cut-off values that define what “similar” means.

  • GDAS-OA-08: My target has been observed as part of a large spectroscopic survey (e.g. from 4MOST and/or WEAVE) and I would like to be able to interface (in a seamless manner) that external spectroscopic data and the Gaia data.

  • GDAS-OA-12: I would like to access the individual astrometric measurements or their residuals with respect to the standard astrometric model similar to the information provided by the Hipparcos Intermediate Data.

  • GDAS-OA-17: I would like to examine the properties of Gaia data in detail without querying the whole Gaia database.

  • GDAS-EG-03: I want the reconstructed image of my favourite source(s).

  • GDAS-ST-08: Pattern Queries: example “return stars like this set of stars, but avoid stars like that set of stars”, where the two sets are defined by the user. Rather challenging to implement, but incredibly useful.

  • GDAS-ST-10: Random Queries: return an unbiased random subset of size N of the Gaia Archive, according to a user-specified multi-variate distribution for quantitiesX, Y, and Z. Computing a reliable histogram, for example, can be done without using the entire archive, as long as you have a unbiased subset of the archive.

  • GDAS-ST-11: Whole-database queries; Sequentially; According to a space-filling curve.

  • GDAS-ST-12: Queries in the frequency domain: e.g. return stars with an excess in the Fourier spectrum in the frequency range [x, y]; e.g. return stars with a 1 /f noise profile in the Fourier domain.

  • GDAS-ST-13: Queries in the time domain: e.g. return stars with at least N points that are 5-σ below the median of the light curve.

  • GDAS-ST-17: I have my own private catalogue (of magnitudes, positions, chemical abundances, or other properties) of a globular cluster. I would like to match it with the Gaia catalogue and visualise any of the chosen properties of common objects in a graph, maybe even in 3D form. I also want to do some statistical tests. Maybe in the first exploratory phases I do not want my private catalogue to become public, but I would still like to avoid downloading locally a large chunk of data because I want an instant check of some idea that came when analysing my data. An example: I want a 3D plot of all the stars spatial positions (from Gaia), and I want the stars coloured differently according to their carbon abundance (which I measured). Then I want to project this in different ways and planes, and perform some Kolmogorov-Smirnov statistics, for example.

  • GDAS-ST-02: I want to fit a synthetic spectrum to the observed fluxes (BP/RP and/or RVS), as well as additional fluxes from other catalogues (e.g. 2MASS). I would like those data to be directly available in the Gaia catalogue, I don’t want to copy/paste from the 2MASS catalogue. I need to be able to degrade the synthetic spectrum with all the Gaia instrumental effects for a useful comparison between observation and theory.

  • GDAS-ST-09: Group Queries: rather than constraining the properties of targets, it is sometimes necessary to constrain the relation between two or more targets, e.g. return all stars with an apparent distance on the sky <= alpha; e.g.: return all stars within this circle on the sky that have the same apex with a tolerance of alpha.

  • GDAS-GA-18: I would like to measure the properties of spiral arms in the extended solar neighbourhood.

Appendix B: Adopted libraries and frameworks

This appendix includes a list of the most important external libraries and frameworks that were used in the development of, and that integrate, the Gaia Archive Visualisation Service.

Table B.1

External libraries used in Server (indicated with S) and Client (indicated with C).

All Tables

Table 1

Role of the services provided by the server side.

Table 2

Role of the services, directives, and controllers that compose the architecture of the client side.

Table B.1

External libraries used in Server (indicated with S) and Client (indicated with C).

All Figures

thumbnail Fig. 1

Static architecture diagram for the GAVS Server. It presents the components of the Server (Services, Plots Backend, Spatial Indexing, and Database Manager), how they are connected, and the context within the GAVS.

Open with DEXTER
In the text
thumbnail Fig. 2

Client architecture diagram providing the structure and context in GAVS. The Client is structured in a Model-View-Controller design expressed in the Directives, Controllers, and Services modules.

Open with DEXTER
In the text
thumbnail Fig. 3

Outline of the steps followed when creating visualisations for distribution and for viewing with external applications. It covers the creation of the DR1 poster image in various formats as well as HiPS and and FITS files.

Open with DEXTER
In the text
thumbnail Fig. 4

All-sky maps of DR1: integrated flux (top), density (middle), density for sources brighter than G = 20 mag (bottom).

Open with DEXTER
In the text
thumbnail Fig. 5

12° × 10° density (left) and integrated flux (right) maps of the LMC.

Open with DEXTER
In the text
thumbnail Fig. 6

15° × 11° field centred on the Orion-A region. Density (top left) and integrated flux (bottom left) maps with DR1 data. Coloured DSS (top right) and 2MASS (bottom right) images of the same field. The DR1 images reveal a cat-like structure created by an extinction patch, highlighting how the mere positions in DR1 can already reveal structures not seen in currently available optical and near-infrared images.

Open with DEXTER
In the text
thumbnail Fig. 7

Workflow for producing a visual ADQL query. Top panel: user selects a region to centre the view (top). Middle panel: selected polygonal region is shown in green. Region menu with the ADQL functionality also displayed. Bottom panel: resulting ADQL query.

Open with DEXTER
In the text
thumbnail Fig. 8

Archive and Simbad searches of object of interest.

Open with DEXTER
In the text
thumbnail Fig. 9

User catalogue of open clusters, globular clusters, and nearby dwarf galaxies overlaid on a scatter plot of the DR1 sources in galactic coordinates.

Open with DEXTER
In the text

Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.

Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.

Initial download of the metrics may take a while.