To establish a geotemporal series in the Ontology that drives analysis and visualization within Palantir applications, such as a Gaia map, you will use Pipeline Builder to:

If you plan to add data from the Ontology to a Foundry map and not Gaia, then you can use time series to view and analyze data associated with geospatial or geotemporal objects. Learn more about creating and managing a time series sync.
Contact Palantir Support with additional questions about which integration type you should use to index your geotemporal data into the Ontology based on your enrollment and specific use case.
Follow the instructions below to add a geotemporal series sync output as a reference to a geotemporal series object type.
After creating a new, empty pipeline, toggle on Pipeline Builder's advanced geotemporal capabilities.

Review the existing documentation on geotemporal data modeling before proceeding.
Identify the streaming and static datasets that will back your geotemporal series sync and object type and follow the instructions below to add them to your pipeline. While you can create both a geotemporal series object type and geotemporal series sync from one dataset, the steps below provide instructions using two: a live stream to back the geotemporal series sync and a static dataset to back the object type.
![]()
At a minimum, your streaming dataset should contain columns that capture a tracked entity's movement over time, such as its latitude and longitude at a given timestamp, as well as a string column that enables you to join the geotemporal series sync to the object type. Columns that contain data that changes over time are referred to as live fields, whereas those that remain consistent (such as an entity's name) are called static.
Your transform needs may vary depending on your streaming dataset's raw state upon ingest into Foundry. The example data outlined below contains the following columns that map to the sync's primary fields:
string column used to join the geotemporal series sync to the static dataset-backed object type. Learn more about configuring a series ID.timestamp column containing the time recorded for the entity's location.geopoint column containing the entity's latitude and longitude pair.
The dataset contains additional columns which will map to the geotemporal series sync's Properties but are not required for the sync to function in a Palantir map application.

If necessary, use Pipeline Builder's Cast and Create GeoPoint transforms to prepare your raw streaming dataset for output as a geotemporal series sync.

Follow the instructions below to create a geotemporal series sync output from your transformed streaming data:

Foundry records a Live property value for every new observation, such as an entity's velocity at a given timestamp. If you mark a property as static, then Foundry records and applies the latest value of that property for all observations in the series.
Contact Palantir Support with questions about expanding or contracting the default live retention window.
At a minimum, your static dataset should contain the same unique identifier for the tracked entity as the streaming dataset, such as a name or call sign.
Next, you will transform your object type backing dataset to ensure it can be linked to your geotemporal series sync though a geotemporal series reference (GTSR).
Column, expression, or value and choose your dataset's primary key column from Columns. In this example, the dataset's mmsi column contains a unique vessel identifier that can be used as the primary key.Series_ID that is a copy of the dataset's unique identifier, such as mmsi. You will use this new column to link your geotemporal series sync to the object type.

After transforming your static dataset, follow the instructions below to create an object type output and implement the Tracked Entity interface.


Series_ID property to map the GTSR property to your object type by choosing Geotemporal series > From this pipeline.
If you do not see Geotemporal series as an option, verify that you have enabled Pipeline Builder's advanced geotemporal series features.
Tracked Entity interface from the Palantir Core Ontology.
Contact Palantir Support to install the Tracked Entity interface on your enrollment if you are unable to access it in Ontology Manager.
After configuring your geotemporal series sync, creating an object type and interface, and establishing a link between the two via the GTSR, follow the instructions below to deploy your pipeline:


Once your pipeline deploys and your object type is created in your ontology, you can visualize its observations on a map.

Gaia is only accessible if your enrollment contains Gotham. Contact Palantir Support with questions about access to Gaia or its additional documentation available in platform.
To ensure Gotham can access object types in your Foundry ontology and render objects as part of a data layer on a Gaia map, you must follow the instructions to type map your object type in Ontology Manager.
To support Pipeline Builder's advanced geotemporal features, you must complete the type mapping process to discover your object type in Gotham even if your enrollment contains Map Rendering Service.
Once you ensure your object type is discoverable by Gotham, you can add it to your Gaia map.
In addition to adding data from your ontology, you can review the existing documentation to learn more about creating ontology data from Gaia.
With your pipeline deployed, you can add your object type as a layer on a new or existing map in Foundry. Object data on a map will update in real-time when upstream changes are made, with those updates stored both within the object type and the sync's dataset archive.
The ability to view real-time geotemporal series object updates on a map may not be available on all enrollments. Contact Palantir Support to enable this feature if you are unable to view object updates from your geotemporal series object type after successful configuration and deployment in Pipeline Builder.
Learn more about visualizing data from your ontology in Foundry.