You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 73 Next »


Please feel free to list yourself (and your institution):


Day 1,  , 15:00-18:00 CET - Introduction


  • 16:00 - 18:00 - Participants data 5-10 min presentations - all participants (see template below)

Similar service: spectro_asteroids, planets (simple CSV file)

Similar services: SNBAF, TNOsarecool, MPC, planets (simple CSV file)

Similar services: SNBAF, TNOsarecool? Or Vvex, Bass2000 (for ingestion from an existing database).
Priority : best value table (the other have series of successive measurements)

How do we present data file organisation? Need to insert this in the table?
Maps: convert to binary files (images) with one quantity each? (will allow using Aladin, and to make HiPS from these maps if high resolution available)
ascii files: convert to VOTable, which are self-described?
Some applications can handle some PDS4 datatypes: Autoplot (in progress); Splash ( ?); TOPCAT (tables only, beta version)

2 services, one with 2 tables (images + groups of sunspots) - TBC, can be related either via external_link or datalink_url

Update of DaCHS server will simplify consolidating the parameter descriptions (they are predefined in the latest version)
Is it possible to refer to filters characteristics in SVO service? 

  • Europlanet TA: data from lab and field studies Arie Bikker 

Test project with a familiar dataset: CSV file with spatial extension & time tag. 
Should also include an actual Europlanet collection from the start. 

  • Europlanet VA / ML: MESSENGER magnetometer data set
    for boundary 
    crossings (LMSU, Moscow and IWF, Graz)David Parunakian 

Important: check consistency of parameters with AMDA services

Day 2,  , 15:00-18:00 CET - Discussion

Round table (group discussions)

  •  15:00 - 17:00 - Participants Data/EPN-TAP modelling - all participants

(description of EPN-TAP parameters by function)


• Template for parameters, to be used to design your service:


• Longer discussion of EPN-TAP parameter: EPN-TAP v2 parameter description

  • SPHERE asteroid images and shape models (LAM, Marseille) 

  • MOVIS asteroids NIR colors (AIRA, Bucarest) 

  • Asteroid data catalogues - MP3C (OCA, Nice) 

  • PDS PPI (UCLA + Iowa Univ) 

  • Sunspots and coronal holes catalogues (ROB, Brussels) 

  • Various services at IRAP (GSO, Toulouse)

  • Europlanet TA: data from lab and field studies 

  • Europlanet VA / ML: MESSENGER magnetometer data set
    for boundary 
    crossings (LMSU, Moscow and IWF, Graz)

  •  17:00 - 18:00 - Summary of discussions - all participants

Day 3,   15:00-18:00 CET - Tutorial

Tutorial (interactive)

  • 16:30 - 17:15 - Importing data from CSV / SQL - Chloé Azria  

Day 4,  , 15:00-18:00 - CET - Hands-on & implementation


  • 15:00 - 17:00 - Participants implementation - all participants
  • 17:00 - 18:00 - Running / testing / optimising workflow - all participants

Connection info

Please register on: 

The same tools can be used for follow up activities in the forthcoming weeks. If you have any issue, please reach out to Angelo Pio Rossi or Carlos Henrique Brandt 

Software requirements

The workshop will use DaCHS on Docker container as it is meant to be simpler and to have it setup. For that, we need all the participants to have Docker (and, optionally, docker-compose) pre-installed.
Please, follow the instructions for your operating system as per Docker official documentation:

Since the workshop will be hosted on Zoom + asynchronous chat on Discord, we highly recommend using the Desktop app (instead of the web-app).
Please refer to Discord official documentation for install instructions:

We will use VOParis Gitlab instance to exercise in hosting DaCHS/data resources, it is recommended to have Git installed on your system:

See also VESPA Data provider on-boarding process

The workflow with Gitlab for VESPA is outlined below:

See Intro slides. Please fill in, if not already there server_name and service_name metadata on this 2021-workshop-service-info

  • STEP 1: Data provider team sends request for VESPA support (this is done with the call) 
  • STEP 2:VESPA teams invites an external user to EduTEAMS
  • STEP 3: External user to accept the invitation
  • STEP 4: VESPA to approve the new user and to setup groups memberships on EduTEAMS
  • STEP 5:External user connects to (using the EduTEAMS connection method). This action creates the gitlab account
  • STEP 6: VESPA to setup repositories, membership and groups on voparis-gitlab: External users can now access to their repositories

Documents & templates

Participant presentation template. Please feel free to use your own slides/templates, this is just to loosely guide the structure/content. 


  • No labels