# FAQ

## Are geotemporal series generally available?

Geotemporal series are in the [beta](../../platform-overview/development-life-cycle/index.md) phase of development and may not be available on your enrollment. Functionality may change during active development.

## When should I use geotemporal series instead of time series to display geospatial data?

If you plan to display your geospatial data on a [Gaia map](../add-ontology-data-to-gaia/index.md), then you should use geotemporal series. [Geotemporal series](../overview/index.md) require latitude and longitude coordinates alongside a timestamp and series ID. Use geotemporal series if your tracking data includes an additional measurement value alongside its coordinates, such as speed or altitude. Geotemporal series store latitude, longitude, and a measurement value together in a single series, which can simplify your data model when you need to correlate location with other values. [Learn more about integrating geotemporal series with the Ontology.](../integrate-geotemporal-series-with-the-ontology/index.md)

If you plan to display your geospatial data on a [Foundry map](../../map/overview/index.md), then you should use [time series](../../time-series/time-series-overview/index.md). You can use [time series properties](../../time-series/time-series-properties/index.md) to track the movement of entities over time by storing latitude and longitude pairs as *separate* time series to display on a Foundry map as [track objects](../../map/integrate-objects/index.md#track-objects). Using time series for geospatial entity tracking is appropriate when your data contains latitude and longitude measurements recorded at different timestamps, such as GPS coordinates for ships or vehicles, *without* an additional measurement value. [Learn more about creating time series syncs that back track objects in your Ontology.](../../time-series/geospatial-time-series-use-case/index.md)

### Can I implement both geotemporal series and time series simultaneously?

If you plan to view your geospatial data on *both* Foundry and Gaia maps, then you can [create a geotemporal series sync that produces a geotemporal reference property](../integrate-geotemporal-series-with-the-ontology/index.md) *and* [create a time series sync that produces time series properties](../../time-series/geospatial-time-series-use-case/index.md) on your object type. Objects displayed on a Foundry or Gaia map that implement both are read-only, so users may *only* view the objects on each map as opposed to executing actions on one or multiple. You should avoid implementing both series types unless necessary for your specific use case.