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

[sseppi]

The details for the integration of this data type are mentioned in the EPIC #296

This datasets are interesting since introduces the concept of Parent (ECharginStaton) -Child (EChargingPlug) station

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

• [ ] The link to the eCharging APIs (concept of parent child station): https://mobility.api.opendatahub.com/v2/flat/EChargingPlug https://mobility.api.opendatahub.com/v2/flat/EChargingStation

[gappc]

@sseppi these are the related Data Browser links:

• https://databrowser.opendatahub.testingmachine.eu/dataset/table/mobility/v2/flat/EChargingPlug
• https://databrowser.opendatahub.testingmachine.eu/dataset/table/mobility/v2/flat/EChargingStation

[sseppi]

@gappc As for the LinkData I would show the last measurement of a station.

As example for the Following eCahrgingPug: https://databrowser.opendatahub.testingmachine.eu/dataset/detail/mobility/v2/flat/EChargingPlug/00001-0#measurements

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

• "tname" --> name of the data type
• "ttype" --> description of the data type
• "tunit" -->unit of measurement
• "mperiod" update period
• "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

      "tname": "echarging-plug-status",
      "ttype": "",
      "tunit": "",
      "mperiod": 600,
      "mtransactiontime": "2018-04-26 10:20:58.951+0000",
      "mvalidtime": "2018-05-08 05:05:25.485+0000",
      "mvalue": 1,

And I would do the same also for the eCharging Stations.