Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As an Open data hub Manager I want that the Weather Data, is browsable through the Data Browser 2.0 to test the integration of the Mobility Domain #441

Closed
sseppi opened this issue Oct 31, 2023 · 2 comments
Assignees

Comments

@sseppi
Copy link
Contributor

sseppi commented Oct 31, 2023

The detail about the integration of this data are collected in the issue #296

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

The Link to the Weather Data:
Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/MeteoStation
Station last values: https://mobility.api.opendatahub.com/v2/flat/MeteoStation/*/latest

@sseppi sseppi added this to the Data Browser 2.4 - Beta milestone Oct 31, 2023
@sseppi sseppi changed the title EPIC: As an Open data hub Manager I want that the Weather Data, Air Quality Data, eCharging Dataset and Vehicular Time data is browsable through the Data Browser 2.0 to test the integration of the Mobility Domain#296 As an Open data hub Manager I want that the Weather Data, is browsable through the Data Browser 2.0 to test the integration of the Mobility Domain#296 Oct 31, 2023
@sseppi sseppi changed the title As an Open data hub Manager I want that the Weather Data, is browsable through the Data Browser 2.0 to test the integration of the Mobility Domain#296 As an Open data hub Manager I want that the Weather Data, is browsable through the Data Browser 2.0 to test the integration of the Mobility Domain Oct 31, 2023
@gappc
Copy link
Collaborator

gappc commented Jan 9, 2024

@sseppi this is the related Data Browser link:

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
Copy link
Contributor Author

sseppi commented Jan 9, 2024

@gappc

I suggest to use the same strategy mentioned in the issue #444.

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

https://mobility.api.opendatahub.com/v2/flat/MeteoStation/*/latest?where=sname.eq.%22Solda%20Cima%20Beltovo%22

As you can see from the API call above, in this case there is a list of different datatype that are shared from the station. For this reason I would suggest to show for each datatype all values that starts with m or t:

     "tdescription": "Direzione del vento",
      "tmetadata": {},
      "tname": "wind-direction",
      "tunit": "\u00b0 ",
      "mperiod": 1800,
      "mtransactiontime": "2021-09-02 10:20:04.999+0000",
      "mvalidtime": "2021-09-02 08:20:00.000+0000",
      "mvalue": 333,

@sseppi sseppi closed this as completed Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants