Skip to main content
Seasoned ⭐️⭐️
June 22, 2023
Planned for development

CDF to handle String Timeseries

Related products:Charts
  • June 22, 2023
  • 21 replies
  • 400 views

Hello,

We’re currently having some issues with pulling our PI data from Cognite since we have several PI tags that are string timseries vs numeric (as in rather than having 0 or 1, the timeseries shows open or closed). It appears that Cognite cannot handle string timeseries because they cannot be aggregated, however some of the logic that’s built in to our devices can only be pulled in this manner. We’d at least need a way for Cognite to convert the data pulled as strings as numeric and maybe auto assigning numeric values to each string event? A bonus would be to have an associated conversion of those numeric values to the associated string from the pull

Example:

Cognite pulls timseries EXAMPLE.TIME.VALVE.A.STATUS that contains “Open” and “Closed” and auto assigns 0 to “Open” and 1 to “Closed”

There’s then an associated ‘conversion’ that states for timeseries EXAMPLE.TIME.VALVE.A.STATUS:

0 = “Open”

1 = “Closed”

 

then Cognite pulls another timeseries EXAMPLE.TIME.VALVE.B.STATUS and happens to assign 0 to “Closed” and 1 to “Open” for whatever reason

There’s then an associated ‘conversion’ that states for timeseries EXAMPLE.TIME.VALVE.B.STATUS:

0 = “Closed”

1 = “Open”

 

21 replies

Everton Colling
Expert ⭐️⭐️⭐️⭐️
Expert ⭐️⭐️⭐️⭐️
September 9, 2026

Hi ​@rmaidla!

In the upcoming Q4 release (December 1st 2026) we will be releasing in general availability a new type of time series for state like data: https://docs.cognite.com/dev/concepts/resource_types/state_timeseries. It’s already available for testing as a public beta feature.

This upcoming release will also include the ability to request some aggregates like countcountGoodcountUncertaincountBaddurationGooddurationUncertaindurationBadinterpolation, and stepInterpolation for all time series types (numeric, string and state).