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, use time series to view and analyze data associated with geospatial or geotemporal objects. Learn more about this in our geospatial time series use case tutorial.
Review the geospatial FAQ page or 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.
Review the existing documentation on geotemporal data modeling before proceeding.
Identify the streaming dataset that will back your geotemporal series sync and object type and follow the instructions below to add them to your pipeline.
![]()
Learn more about configuring your geotemporal series sync in Pipeline Builder.
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 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.

The Geotemporal Series interface is available for installation in Palantir's Core Ontology that is suitable for most use cases. Contact Palantir Support to install this interface on your enrollment if you are unable to access it in Ontology Manager.
Next, you will transform your geotemporal dataset to create a geotemporal series object type that is 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 geotemporal dataset, follow the instructions below to create a geotemporal series object type using Pipeline Builder's ontology output.


Series_ID property to map the GTSR property to your object type by choosing Geotemporal series > From this pipeline. You may also select a geotemporal series sync from another pipeline by choosing From Foundry... and selecting the corresponding geotemporal series integration.
An object type can have at most one geotemporal series reference property, and it may not be an array of geotemporal series references.

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.
Once your geotemporal series is integrated with the ontology, you can add its associated object type to your Gaia map.
You may also configure a GTSR property type directly in Ontology Manager. Using the geotemporal series sync you created above in a new or the same Pipeline Builder pipeline:

Series ID select the same column you selected as the series ID of your geotemporal series sync.Geotemporal series integration RID select the RID of your deployed geotemporal series sync.In Ontology Manager, create a new object type with the new dataset you created as the data source.
The corresponding Geotemporal Series Reference property type should be automatically configured from the column you created in Pipeline Builder. If not, you can add or edit an existing property type with the Geotemporal Series Reference type.

You must set the correct geotemporal series sync's RID to proceed. You should also implement the geotemporal interface in this workflow.
An object type can have at most one geotemporal series reference property, and it may not be an array of geotemporal series references.