conversion of the "validTime" : SensorML 2.0 vs SensorML 1.0.1

[shehfeet]

Hello,
We use Insertsensor, InsertResultTemplete, and InsertResult requests to insert time-series data of climate stations (52north SOS Version: 5.4.1, installed on Ubuntu 20.04 server). The station descriptions are prepared based on SensorML 2.0 format. "validTime" of sensor descriptions are set as insertion time when using SensorML 1.0.1. Therefore we cannot indicate the data availability when parsing sensor data based on SensorML 1.0.1 format.

SensorML V1 :http://lafodata.uni-hohenheim.de:8080/sos2/service?service=SOS&version=1.0.0&request=DescribeSensor&procedure=SMN-HFH03-1&outputFormat=text%2Fxml%3B%20subtype%3D%22sensorML%2F1.0.1%22

SensorML V2 : http://lafodata.uni-hohenheim.de:8080/sos2/service?service=SOS&version=2.0.0&request=DescribeSensor&procedure=SMN-HFH03-1&procedureDescriptionFormat=http%3A%2F%2Fwww.opengis.net%2Fsensorml%2F2.0

Thank you

[shreyashkumar01]

Hello @shehfeet ,
Thank you for providing the detailed description of your issue. It appears you're facing a challenge with representing data availability in your 52North SOS system due to a mismatch between the SensorML versions used for station descriptions and data parsing.
To better understand the situation, could you please clarify a few points:

• How are you generating the SensorML 2.0 station descriptions? Are you using a specific tool or library?
• Is there a specific reason why the SOS system is configured to parse data availability based on SensorML 1.0.1? Is it a limitation of the 5.4.1 version?
• What is the exact process that you are using to insert the data into the SOS?
  The core of the problem lies in the 'validTime' element being interpreted differently between SensorML 1.0.1 and 2.0. In 1.0.1, it seems your system is defaulting to the insertion time. This prevents the actual data availability period from being correctly represented.
  Here are a few potential avenues to explore:
• SOS Configuration: Investigate if there are configuration options within the 52North SOS 5.4.1 that allow for parsing data availability based on SensorML 2.0.
• Data Preprocessing: Consider if you can preprocess your SensorML 2.0 descriptions to include the necessary information in a way that is compatible with the SOS's 1.0.1 parsing. This might involve adding custom extensions or transforming the 'validTime' representation.
• SOS Upgrade: If possible, consider upgrading to a newer version of 52North SOS that offers better SensorML 2.0 support.
• Data Insertion process: Review your current data insertion process, and see if there are any parameters that can be altered to correctly set the valid time.
  I recommend reviewing the 52North SOS documentation and the SensorML specifications for both versions to gain a deeper understanding of the differences.
  By providing the answers to my questions, we can narrow down the potential solutions.