This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
The more clarity about your desired application workflows and Ontology structure, the easier it is to logically create your supporting variables.
The COP you want to generate will be a simple, filterable map of airports affected by flight alerts. Due to an Ontology decision from our notional project team, the former has mappable data (e.g., lat/long) but the latter does not. All mapping will therefore be done around the [Example Data] Airport object type, which is transitively linked to your flight alert object type via [Example Data] Flight.
Your COP will also have an interactive pie chart of flight alert priority that can also act as an additional filter. Finally, you’ll want to display some statistics about flights, alerts, and affected airports across the top of the screen. We can therefore key in on three primary object types: flight alerts, flights, and airports.
In the previous section, we took an intentionally circuitous development route to more efficiently convey certain concepts. The tasks in this exercise will follow a more “natural” development path to create variables and widgets. Let’s begin by creating an airport filter list.
Click into the left Section header and set the following in the section configuration panel:
ℹ️ In your COP, you’re only concerned about airports with flights that have alerts, so there’s no need to create an [o] All Airports object set as the input to your filter. Instead, you need to create an object set of just those airports affected by flight alerts.
Add a Filter list widget to the section.
Change the new filter list widget’s name in its metadata tab to Filter list: Airport Filter.
Click into the Select object set variable . . . , in the Widget setup tab, field and choose ➕ New object set variable.
In the variable fly-out window, change the generic variable name to [o] Airports with Alerts.
For your Starting object set, choose [o] All Flight Alerts from the list of Existing object set variables.
Click the Get linked objects button under your starting object set selection to surface the available direct Ontology links to your current object set.
Choose [Example Data] Flight.
Click the Get linked objects button once more and choose [Example Data] Airport, making sure to choose the one that lists [Example Data] Destination Airport underneath. The Current value to the right should show 223 airports.
If you see 244 airports, you're searching around to [Example Data] Origin Airport instead of Destination.