search

noi-techpark / bdp-commons

GNU Affero General Public License v3.0
2 stars 12 forks source link

EPIC: As A22 I would like to integrate my new datasets in the Open Data Hub, so that they are available as open data with 3rd parties #657

Open rcavaliere opened 10 months ago

rcavaliere commented 10 months ago

A22 has shared with NOI new datasets related to information that is shown on their web-site (https://www.autobrennero.it/it/). This data will be licensed as open data. The data available is:

Web-cams: placed along the A22 highway, can provide a visual feedback of the current traffic conditions Rest areas: placed along the A22 highway, can be useful information for travelers along the highway. For each rest areas the available services are provided. Toll gates: information about the details of the toll gates available. Traffic forecasts: available traffic bulletins computed and published by Autostrade del Brennero Traffic events: real-time traffic events published on the A22 web-site Roadworks events: real-time traffic events published on the A22 web-site

For the first three datasets, the question is whether if we should integrate them in the tourism dataspace, since these can be treated as web-cams and POIs. The other data should on the contrary integrated in the mobility dataspace

The current user story should just focus on the design on how to best integrate this data into the Open Data Hub. The output is a specification document so to then start with the implementation, to be foresee in separate user stories

First draft: 230912_SpecificheIntegrazione_NOI_v1.1.docx

rcavaliere commented 9 months ago

First proposal on how to integrate this new data from A22 internally consolidate.

Some of the data (i.e. web-cams, toll gates and service areas) to be integrated in the Tourism Data Space (agreed with @RudiThoeni). Interesting: the service areas also include static information about the e-charging possibilities (@ohnewein I will suggest STA Green Mobility to then include this information in the available web-components for e-mobility).

The other data should be integrated in the Mobility Data Space. The first specification integration drafts covers the integration of the traffic forecasts, which is the most valuable dataset shared. I kindly ask @dulvui and @clezag to check my proposals there, there are some points that may lead to an internal discussion. If consolidated, we could start with next sprint to start with the implementation of the first Data Collectors 230912_SpecificheIntegrazione_NOI_v1.1.docx