Overview
Sensor object types are a more advanced configuration of time series data where the sensor object holds the sensor data for its linked parent (also referred to as a root object). Review the time series documentation to decide if a time series property set up or sensor object type configuration is right for your use case.
This documentation will walk through the various steps to write a pipeline in Pipeline Builder, set up sensor object types in Ontology Manager, and create a Quiver dashboard and Workshop module using an example aviation ontology and the power of time series in Foundry.
The aviation ontology is made up of example Flight, Carrier, Route, Airport, and Flight Sensor object types. A Flight is linked to Aircraft, Flight Sensor, Route, Airport, and Carrier objects through the flight_id foreign key on those objects.
The aviation ontology comes from a reference ontology of notional data, and it may not be available for your enrollment. Regardless of the availability for your enrollment, these examples built using this reference ontology will serve as a reference as you create your own pipelines, object types, and Workshop modules using sensor object types.
The Workshop module that you will produce using the guide will allow you to view and interact with flight sensor time series data for a selected flight.
The following guides will lead you through the steps to create and support this Workshop module: