Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
We do not currently support relative timestamps in the future - the pattern from the doc is the only one we support (though it also accepts `ms` for milliseconds). However, as you might know, these endpoints also accept Unix timestamps in milliseconds - for example, noon UTC on March 10, 2022 would be 1646913600000. So you could compute the timestamp of your desired future time and supply that instead.
@Ben Brandt You could add the idea that Thomas mentioned above to the Ideation Module to see if it gets upvotes from others as well, which would increase the likelihood of us prioritizing it.
I have updated https://docs.cognite.com/dev/concepts/pagination/ with a rephrased version of what Thomas wrote plus some further information.
Hi! I was just alerted to this - I took a brief look, and it would indeed have been useful if the error message had said which item was problematic, so I will register this as a potential improvement we could make to our systems. Unfortunately, since this report is now two weeks old, the logs for that request id seem to be gone - and even if I had found them, I don't think they would have contained more information about the value that failed to parse (I can see from our code that we do not log the actual input data or the position of the bad input data). However, as far as I can see from our code, this error can only happen if all of the value fields inside the datapoint list are strings (their values begin and end with double quotes) while the timeseries itself is a numeric timeseries. Note that even if a string seemingly contains a number, we still interpret it as a string: "value": "3.14" is only valid for a string timeseries, not for a numeric timeseries. If this happens again, pl
At the moment, the only approach we can offer is for you to add a metadata property to the timeseries in question, with the value being a textual representation of the geolocation. However, we are working on exposing Time Series as nodes in Data Modeling, and when that is in place, you will be able to add your own custom data containers to those nodes, with information such as geolocation.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
