-
Notifications
You must be signed in to change notification settings - Fork 7
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
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
Comments
@pkritzinger I got the feedback from Roberto, he said that the proposed configuration is fine and easily extensible also to the other datasets. I would suggest to proceed with the proposal you did. |
@gappc I would suggest to reuse as much as possible already existing components.
In my point of view, it could be useful as preview of what could be displayed in the Open Data Hub Analytics tool. But for now this feature is a nice to have. @mrabans and @rcavaliere do you agree? In case I can create a dedicated issue to proceed with the 7 days preview |
@sseppi I agree! |
@pkritzinger @sseppi @rcavaliere I think the configuration proposed by studiohug is fine. The use-case of showing data of the last X days seems interesting, too. As @sseppi suggested I would open a dedicated issue for that functionality. |
@pkritzinger and @gappc as emerged duuring the discussion I suggest to proceed with the configuration of the single fields for the first PoC. I've also create a dedicated issue for the 7 days preview: #456 |
This issue wants to integrate the data of the Mobiltiy Domain in the existing Data Browser structure.
The user flow should be the following:
Note: for all mobility datasets the value
smetadata
shoudl be rendered as a JSON since the content it could be different from Data Provider to Data Provider.Here below I post some useful link to start with for the first PoC:
Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/MeteoStation
Station last values: https://mobility.api.opendatahub.com/v2/flat/MeteoStation/*/latest
Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/EnvironmentStation
Station last values: https://mobility.api.opendatahub.com/v2/flat/EnvironmentStation/*/latest
https://mobility.api.opendatahub.com/v2/flat/EChargingPlug
https://mobility.api.opendatahub.com/v2/flat/EChargingStation
Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/LinkStation
Station last values: https://mobility.api.opendatahub.com/v2/flat/LinkStation/*/latest
In the first iteration maybe we should disable the search and filter options for all mobility datasets (@gappc do you think is better to create a separate issue for the management of filters and search in mobility domain). For the filter and search functionality, a dedicated issue has been created #427
The text was updated successfully, but these errors were encountered: