SPL File FlightPathEncounterTypes.spl

Specialized toolkits - release 4.3.1.0-prod20190605 > com.ibm.streams.geospatial 3.3.2 > com.ibm.streams.geospatial > FlightPathEncounterTypes.spl

Types that are used together with the FlightPathEncounter operator.

FlightPathEncounterTypes.EncounterEvent = tuple<FlightPathEncounterTypes.Observation3D observation, FlightPathEncounterTypes.Observation3D encounter, float64 encounterDistance, int64 encounterTime>;

The FlightPathEncounter operator creates encounter events as output. An encounter consists of the original observation, the data for the encountered object and the distances in time and space between the colliding objects. The following tuple definition contains all necessary attributes with the correct types and the default attribute names. It is provided for convenience as it can be used as input and output type for the operator.

If you need additional attributes to be passed through or want to use different attribute names, you can create your own types and overwrite attribute names using operator parameters.

• observation

  The input observation encounters are calculated for. This is a tuple attribute of type Observation3D.

• encounter

  The data for the object that is encountered. This is a tuple attribute of type Observation3D.

• encounterDistance

  The latitude/longitude distance between the two objects at the time of the encounter. It is given in meters.

• encounterTime

  The time in the future the encounter will happen. It is an absolute time given in milliseconds since January 1st 1970 (Posix time).

FlightPathEncounterTypes.Observation3D = tuple<rstring entityId, float64 latitude, float64 longitude, float64 altitude, int64 observationTime, float64 azimuth, float64 groundSpeed, float64 altitudeChangeRate>;

The FlightPathEncounter operator processes observations of flying objects. Each observation needs to conform to the Observation3D type. The type contains the following attributes.

• entityId

  The unique identifier of the flying object. You may use the ICAO field from an ADSB feed.

• latitude

  The latitude of the object in degrees. Allowed values are in the range from -90 to 90.

• longitude

  The longitude of the object in degrees. Allowed values are in the range from -180 to 180.

• altitude

  The altitude of the object in meters. Allowed values are greater or equal 0.

  If you need to convert from feet to meters, multiply the feet by 0.3048.

• observationTime

  The time stamp of the last observation of this object. Given in milliseconds as Posix time (milliseconds since January 1st 1970).

• azimuth

  The azimuth of the object. This is the clockwise angle between the objects motion direction and a line from the object to the north pole. Given in degrees (for example if the plane is flying to the east, this will be 90 degrees). Allowed values are 0 to 360.

• groundSpeed

  The groundSpeed of the object in meters per second. There is a dependency between this value and the timeSearchInterval parameter of the operator. At the given speed the object must not travel more than 20000 kilometers within the given timeSearchInterval. For example with a time search interval of 15 minutes (900000 ms) the object speed must not be faster than 80000 km/h (~22000 m/s). For all practical purposes this should not be a serious limitation.

  If you need to convert from knots to meters/second multiply the knots by 0.514444.

• altitudeChangeRate

  The altitudeChangeRate of the object in meters per second. Positive values denote increasing altitude.