Other useful files

This page describes various data files used in producing our website that might be useful to you while using our GNSS-IR data. Where files are marked with an "e.g." and reference ID 10001, there is one file available for each site, and you can replace it with the ID of the site you are interested in.


This is a simple, comma separated file, mapping our site IDs to the IGS-type IDs commonly used elsewhere. Note we've avoided using these as our identifier as they aren't always globally unique.


This is a JSON file containing the information used in producing the table of sites, and a few extra fields such as data supplier. The file is structured as a dictionary, with each entry mapping one of our IDs to the metadata for that site.


The data file used to create the layer of pins on our map page showing sites where GNSS-IR works well. This file is in the GeoJSON format commonly used by web mapping software.

Three other files describe the other layers on that map: questionable_sites.json, bad_sites.json, and decommissioned_sites.json.

10001.zip (e.g.)

The main data file for each site, as described on our data format page

10001.json (e.g.)

This is the data used to populate the site page for each location. It is in GeoJSON format to allow it to be added to the map on the page - most of the metadata fields are in the "properties" property of the object.

10001_daily.csv (e.g.)

CSV files containing daily averages (see our example notebook for how these are calculated) from the processed GNSS-IR data, along with daily averages from nearby tide gauges where available. These files are used in the daily plots on our station pages.

Please don't use the daily tide gauge data used here, as the level of quality control varies considerably between sites. Instead, refer to a proper data centre for high frequency data (e.g. UHSLC or GESLA, or appropriate local suppliers such as NOAA, JODC or SHOM.)

10001_mask.json (e.g.)

This is used to draw the polygons on the map on each site page illustrating the GNSS footprint we've used in generating the data file. This is in GeoJSON format.