NLAroutes - Vertical cross sections for flight routes


This returns various plots for flights used by Norsk Luftambulanse.

The plots are generated from the MEPS forecast model and are updated every 6th hour.


Vertical cross section for flight routes, given by ICAO ids.

This is a 2-dimensional plot, with the flight path on the X-axis and altitude along the Y-axis (from SFC to 15,000ft).


This is a 2-dimensional plot showing weather conditions for the next 66 hours at a particular location. The Y-axis shows altitude (from SFC to 15,000ft) and the X-axis denotes time.


Explanation of what you see in the diagrams:

The wind arrow indicate the direction and strength of the wind in knobs.

The wind direction is indicated as follows: North (360°) by arrows pointing straight, southern (180°) by arrows pointing upwards, west (270°) by arrows pointing to the right and eastern (90°) by arrows pointing to the left.

Isolines for temperature. The lines are "dashed" and blue for temperature below zero, red above zero, while the 0 isoterm is displayed as a black solid line.

The red palette show the relative humidity for 70, 80, 90 and 100%, darkest red shadow indicates the highest humidity

The blue palette show the density of clouds for degrees 0.2, 0.4, 0.6, 0.8 and 1, where 1 means completely cloudy. Darkest color indicates the highest density of clouds.

The gray pallete show the terrain (only in cross section).


A list of available data may be retrieved using the 'available' action, using the url


type (mandatory)

Specify what kind of plot to be returned

Values: timegraph

name (mandatory)

ICAO id for routes and name or ICAO of place for timegraph

Values for timegraph:

Values for routes:

(Yes, we know LCAO codes should be in upper case, but the API prefers lower case. Anyway the search is case insensitive.)

time (mandatory)

The time you want data for in ISO format (yyyy-mm-ddThh:00:00Z).

For vcross we have each hour after model reference time for the first 24 hours, then six hours interval from 30 to 66 hours.

For timegraph there is (currently) only one possible time value per location. (Yeah, we know this should have been made implicit by default...)

Example requests:

Change log

version 1.0 : 2016-10-31

- New product for vertical cross section for routes