As an Open data hub Manager I want that the Vehicular Time data is browsable through the Data Browser 2.0 to test the integration of the Mobility Domain

[sseppi]

The detail for the integration of this data are collected in the Epic #296

This data type is interesting because it introduces the concept of beginn and end station.

Here below I post some useful link to start with for the first PoC:

The link to the Vehicular Time data (concept of parent child with beginn and end station) Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/LinkStation Station last values: https://mobility.api.opendatahub.com/v2/flat/LinkStation/*/latest

[gappc]

@sseppi the vehicular time data can be found e.g. here: https://databrowser.opendatahub.testingmachine.eu/dataset/table/mobility/v2/flat/LinkStation

Note that at the moment we don't show the last values for any mobility dataset. Should we add this info? How is it related to #456?

[sseppi]

@gappc

Note that at the moment we don't show the last values for any mobility dataset. Should we add this info?

Yes I would add the last measured value for this last station. As example for the station "Galilei_Roma->druso-poste " (https://databrowser.opendatahub.testingmachine.eu/dataset/detail/mobility/v2/flat/LinkStation/Galilei_Roma-%3Edruso-poste#measurements)

I would suggest to show the mvalue returned by the following API call: https://mobility.api.opendatahub.com/v2/flat/LinkStation/*/latest?where=sname.eq.%22Galilei_Roma-%3Edruso-poste%22

In the measurement section I would suggest to show all existing values in the JSON that starts wit t or m:

• "tdescription" --> description of the measured value
• "tname"
• "ttype" --> type of the data or unit of measurement
• "mperiod"--> interval of measurements
• "mtransactiontime" --> the timestamp when the data has been written in the database
• "mvalidtime" --> the timestamp when the data has been generated/measured
• "mvalue": --> the measured vale

"tdescription": "Count matches within 15minutes",
"tname": "Bluetooth Count match",
"ttype": "Count",
 "mperiod": 3600,
 "mtransactiontime": "2020-01-18 21:54:13.328+0000",
 "mvalidtime": "2021-06-24 08:30:00.000+0000",
 "mvalue": 3,

How is it related to #456?

The idea is that in this issue we will show only last measured value, in the #456 we will extend it to show also a preview of a longer period (eg. last day, last week, etc.).