What are the differences between derived and raw positional data?

FlightStats Positions v2 provides a richer set of positional data to be used within flight tracker applications. FlightStats Positions v2 includes several new fields as well as derived positions when observed positions are not available.

-----------------------

Additional Fields:

- course: The direction of travel in degrees relative to geographic north, clockwise. The range for this data field is -179 to 180.

- vrateMps: The velocity of ascent or descent (if negative) in meters per second.

- phase: Description used to indicate the most likely activity of the plane at a given time. Phases include: Ground, Take-Off, Departure, Climb, Leveled, Cruise, Descend, Approach, Landing. Not all positions will include a phase.

- lastObserved: The timestamp of when FlightStats last received an observed position. In cases where no observed positions are provided for a flight, this field will not be present. The 'date' field in each of the positions blocks identifies the time when the plane is believed to be at that specific location -- either observed or calculated. FlightStats continues to calculate the position even when no additional observed data is provided. In such cases, there will be a difference between date and lastObserved, a gap that increases as the flight continues.

- stationID: The station identifier used by the FAA for TFMS data. Examples: KZLA, KZAB, KZDV.

-----------------------

Special Note regarding stationID:
The FAA TFMS stream consists of a collection of observations from different regional and national tracking systems. Each of these has a separate stationId. A single aircraft may be observed by multiple stations at once, each of which may report a slightly different position due to the inherent inaccuracy of radar. Because of this, trackers showing ASDI streams should either show all signals separately, maintain an affinity between a callsign and single stationId as long as possible, or integrate the different signals.
(Note: ADS-B data payloads are unchanged in the new system. FAA TFMS data payloads include one additional field - stationID.)

Request Parameters:
Applications do not need to make any changes to their current request in order to receive derived positions -- derived is the sourceType by default. If you want to receive raw positional data, you need to add a single argument. (sourceType=raw)

If you would like to take advantage of the new fields, your application will need to include that value in the 'extendedOptions' n/v pair, as shown below.

Here is an example request that will return positional data without the new fields.

https://api.flightstats.com/flex/flightstatus/rest/v2/json/flight/track/[FSflightID]
?appId=[appID]
&appKey=[appKey] 
&sourceType=raw
&includeFlightPlan=true

This example will return the new derived data. sourceType is not needed, because it defaults to sourceType=derived. In this case, new fields will be included.

https://api.flightstats.com/flex/flightstatus/rest/v2/json/flight/track/[FSflightID]
?appId=[appID]
&appKey=[appKey]
&extendedOptions=includeNewFields
&includeFlightPlan=true

This example will return the new derived data and include new fields (extendedOptions=includeNewFields)

https://api.flightstats.com/flex/flightstatus/rest/v2/json/flight/track/[FSflightID]
?appId=[appID]
&appKey[appKey]
&includeFlightPlan=false
&maxPositions=25
&sourceType=derived
&extendedOptions=includeNewFields

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk