Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Our hydro reservoirs have water level measurements at different locations. These measurements are linked to the reservoir asset, which can have a geolocation assigned, but we would also like to assign a geolocation to each specific time series.
A workaround could of course be to set up a “measurement station” asset for each time series, but I think a geolocation directly on the timeseries would be a more elegant solution.
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.
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.
We also have added support for a Data Modeling geoLocation and Geography support onto our roadmap. Current hypothesis is to make that capability available during the fall of 2023.
Great suggestion,@Kristian Nymoen ! We appreciate your input. We have taken note of your idea have opened another discussion thread specifically for the Data Modelling Service. Please add your vote there and feel free to share your thoughts and insights there as well. Thanks again for your contribution!