Swarm access through VirES

Abstract: VirES is a server/client architecture to help access time series of Swarm data and models. Access is enabled through a token generated on the website, and a Python package, viresclient, which provides the connection with the Python ecosystem (e.g. xarray).

# Display important package versions used
%load_ext watermark
%watermark -i -v -p viresclient,pandas,xarray,matplotlib
Python implementation: CPython
Python version       : 3.9.7
IPython version      : 8.0.1

viresclient: 0.11.0
pandas     : 1.4.1
xarray     : 0.21.1
matplotlib : 3.5.1

VirES (Virtual environments for Earth Scientists) is a platform for data & model access, analysis, and visualisation for ESA’s magnetic mission, Swarm

This tutorial introduces the Python interface to VirES, viresclient. We demonstrate usage of the primary Swarm magnetic dataset (SW_OPER_MAGA_LR_1B) and geomagnetic field models produced as part of the Swarm mission. Some knowledge of pandas and matplotlib is assumed.

Run this on the VRE (Virtual Research Environment), where viresclient is already installed, or check the instructions to set it up on your own Python environment.

For more information see:


In order to authenticate access to the VirES server, viresclient requires an access token - this ties communications between the server and the client to your account. If you are using the VRE, this is handled automatically so you can skip this step.

If you are running viresclient on a different machine, you will need to follow these instructions:

  1. Create a user account at https://vires.services if you haven’t already done so

  2. Install viresclient in your Python environment - see https://viresclient.readthedocs.io/en/latest/installation.html

  3. Create a new code cell here and execute the following:

    from viresclient import set_token
    set_token("https://vires.services/ows", set_default=True)
  4. You will now be directed to the VirES token management page, and prompted to generate a new token and enter it here

Your access token should now have been saved to your environment and you won’t need to provide it again. The token and its associated access URL are stored in a file: ~/.viresclient.ini (this file can also be edited directly). You may generate and set a new token, or revoke old tokens, at any point. These are similar to passwords, so should be kept secret - if you accidentally leak a token, you can revoke it at the token management page and generate a new one. It is also possible to set access tokens via CLI. For more information, see https://viresclient.readthedocs.io/en/latest/config_details.html

To remove the configuration (assuming you left it in its default location), you can use the CLI command: viresclient clear_credentials

Fetching some data

Import the SwarmRequest object which provides the VirES interface, and datetime which gives convenient time objects which can be used by SwarmRequest.get_between()

from viresclient import SwarmRequest
import datetime as dt

The following code will fetch one day (i.e. around 15 orbits) of the scalar (F) measurements from Swarm Alpha.

Several keyword arguments can be provided to .set_products() to specify the type of data you want. The measurements available depend on the collection chosen in .set_collection(). The same set of auxiliaries are available for all collections - here we also choose to fetch the MLT - magnetic local time.

sampling_step="PT10S" downsamples the data to 10 seconds, from the MAGx_LR default of 1 second. If no sampling_step is provided, the data will be accessed in its original form (i.e. here, 1-second sampling). These strings to choose the sampling_step should be provided as ISO 8601 durations (e.g. "PT1M" for 1-minute sampling).

start_time and end_time in .get_between() together provide the time window you want to fetch data for - executing this line causes the request to be processed on the server and the data returned to you. NB: this returns data up to but not including end_time. Alternatively we can provide the start and end times as ISO_8601 strings.

# Set up connection with server
request = SwarmRequest()
# Set collection to use
# Set mix of products to fetch:
#   measurements (variables from the given collection)
#   models (magnetic model predictions at spacecraft sampling points)
#   auxiliaries (variables available with any collection)
# Reference: https://viresclient.readthedocs.io/en/latest/available_parameters.html
# Also set additional configuration such as:
#   sampling_step
# Fetch data from a given time interval
data = request.get_between(

The data is now contained within the object which we called data:

<viresclient._data_handling.ReturnedData at 0x7f21a5c32d30>

The data is temporarily stored on disk and not yet loaded into memory - the ReturnedData object is actually a wrapper around a temporary CDF file which could be written to disk directly:

# data.to_file("test_file.cdf", overwrite=True)

… but it is possible to directly transfer it to a pandas.DataFrame object:

df = data.as_dataframe()
<class 'pandas.core.frame.DataFrame'>
Spacecraft MLT Longitude Radius Latitude F
2016-01-01 00:00:00 A 1.724749 92.793967 6833853.08 -72.499224 46935.8083
2016-01-01 00:00:10 A 1.498856 93.091639 6833864.74 -73.130685 46908.3246
2016-01-01 00:00:20 A 1.256029 93.414902 6833875.98 -73.761537 46878.3804
2016-01-01 00:00:30 A 0.996315 93.766833 6833886.81 -74.391708 46846.0555
2016-01-01 00:00:40 A 0.720387 94.151014 6833897.24 -75.021114 46811.5549

… or a xarray.Dataset:

ds = data.as_xarray()
<class 'xarray.core.dataset.Dataset'>
Dimensions:     (Timestamp: 8640)
  * Timestamp   (Timestamp) datetime64[ns] 2016-01-01 ... 2016-01-01T23:59:50
Data variables:
    Spacecraft  (Timestamp) object 'A' 'A' 'A' 'A' 'A' ... 'A' 'A' 'A' 'A' 'A'
    Radius      (Timestamp) float64 6.834e+06 6.834e+06 ... 6.823e+06 6.823e+06
    Latitude    (Timestamp) float64 -72.5 -73.13 -73.76 ... 29.82 30.46 31.1
    F           (Timestamp) float64 4.694e+04 4.691e+04 ... 3.83e+04 3.861e+04
    MLT         (Timestamp) float64 1.725 1.499 1.256 ... 17.15 17.15 17.15
    Longitude   (Timestamp) float64 92.79 93.09 93.41 ... -95.37 -95.37 -95.37
    Sources:         ['SW_OPER_MAGA_LR_1B_20160101T000000_20160101T235959_050...
    MagneticModels:  []
    AppliedFilters:  []

Try plotting some things to visualise the data. The following shows the variation in field strength measured by the satellite as it passes between high and low latitudes, varying from one orbit to the next as it samples a different longitude.

df.plot(y="F", x="Latitude")
df.plot(y="Latitude", x="Longitude")
df.plot(y="Latitude", x="Longitude", c="F", kind="scatter");
../_images/02a__Intro-Swarm-viresclient_17_0.png ../_images/02a__Intro-Swarm-viresclient_17_1.png ../_images/02a__Intro-Swarm-viresclient_17_2.png ../_images/02a__Intro-Swarm-viresclient_17_3.png

Fetching model evaluations at the same time

Various (spherical harmonic) models of the geomagnetic field are produced as Swarm mission products and these are available through VirES. They are evaluated on demand at the same points and times as the data sample points. Here we ask for the MCO_SHA_2D model, a dedicated core field model produced from Swarm data. By supplying residuals=True we will get the data-model residuals, named in the dataframe as F_res_MCO_SHA_2D.

request = SwarmRequest()

data = request.get_between(

df = data.as_dataframe()
Spacecraft F_res_MCO_SHA_2D Longitude Radius Latitude
2016-01-01 00:00:00 A 111.980426 92.793967 6833853.08 -72.499224
2016-01-01 00:00:10 A 108.278648 93.091639 6833864.74 -73.130685
2016-01-01 00:00:20 A 104.358770 93.414902 6833875.98 -73.761537
2016-01-01 00:00:30 A 100.296102 93.766833 6833886.81 -74.391708
2016-01-01 00:00:40 A 96.294332 94.151014 6833897.24 -75.021114

The core field has been removed from the data so the amplitudes are much smaller. Can you interpret the new signals in terms of external fields, i.e. from the ionosphere and magnetosphere?

df.plot(y="F_res_MCO_SHA_2D", x="Latitude")
df.plot(y="Latitude", x="Longitude", c="F_res_MCO_SHA_2D", kind="scatter");
../_images/02a__Intro-Swarm-viresclient_21_0.png ../_images/02a__Intro-Swarm-viresclient_21_1.png ../_images/02a__Intro-Swarm-viresclient_21_2.png

More complex model handling

We can also remove a magnetospheric field model at the same time, by specifying a new model (which we call MCO_MMA here, but can be named whatever you like) which is the sum of core and magnetospheric models.

See Swarm_notebooks/notebooks/02b__viresclient-Available-Data for more examples of this - it is also possible to specify the spherical harmonic degrees (min/max) to use, and to provide your own .shc model.

The remaining signal is now primarily due to the ionosphere.

Note that here we are instead using the CI (comprehensive inversion) core and magnetosphere models (indicated by 2C in the product names). The magnetospheric model (MMA) is split into two parts - “primary”: external to the Earth, and “secondary”: the induced counterpart internal to the Earth.

request = SwarmRequest()
    models=["MCO_MMA = 'MCO_SHA_2C' + 'MMA_SHA_2C-Primary' + 'MMA_SHA_2C-Secondary'"],

data = request.get_between(

df = data.as_dataframe()
Spacecraft MLT F_res_MCO_MMA Longitude Radius Latitude
2016-01-01 00:00:00 A 1.724749 81.375437 92.793967 6833853.08 -72.499224
2016-01-01 00:00:10 A 1.498856 77.563881 93.091639 6833864.74 -73.130685
2016-01-01 00:00:20 A 1.256029 73.531297 93.414902 6833875.98 -73.761537
2016-01-01 00:00:30 A 0.996315 69.342331 93.766833 6833886.81 -74.391708
2016-01-01 00:00:40 A 0.720387 65.190126 94.151014 6833897.24 -75.021114
df.plot(y="F_res_MCO_MMA", x="Latitude")
df.plot(y="Latitude", x="Longitude", c="F_res_MCO_MMA", kind="scatter");
../_images/02a__Intro-Swarm-viresclient_24_0.png ../_images/02a__Intro-Swarm-viresclient_24_1.png ../_images/02a__Intro-Swarm-viresclient_24_2.png