Skip to main content

Data

Working directly with the computed SkyPath data​

Get map data is used to fetch SkyPath computed turbulence data in raw JSON format (not GeoJson). Then, to build a map layer on the client side using this data.

SkyPath Tick​

Satcom communication is expensive, and in order to minimize bandwidth usage the SkyPath REST API supports incremental updates of turbulence data. This is done using a virtual time unit called “SkyPath Tick” which is attached to each calculated turbulence report. This enables the fetching of updates from a point in time.

The SkyPath tick is incremented approximately every 1 minute.

When getting replies from our API you will get all data for the requested time span and also get the current SkyPath tick.

Leave the tick parameter empty to get all updates in the specified time (hours), or specify the desired tick in the skypath_tick parameter and leave hours empty to get only updates that occurred since that tick including ones that happened in that tick.

Pseudo algorithm when working with SkyPath tick​

  1. Upon starting, request the data and specify hours back in hours parameter.
  2. Observe the returned skypath tick and turbulence data.
  3. Save the turbulence data in a local data structure in the app/client.
  4. On the next request, send the same tick you got in the skypath_tick reply and leave hours empty.
  5. You will get in the reply only updates that happened since and in that specified tick and the current SkyPath tick.
  6. Merge the new turbulence update records by their index hex_id and skypath_alt, throw or overwrite duplicate records you already have, and delete old records (for example if working for 3 hours delete any record in your local array which is older than 3 hours).
  7. The resulting local array represents the current turbulence conditions.

fields - is used to select which data you are interested in, default is turbulence, if you wish to get other types you will add them as a comma delimited string to the fields parameter.