As operator of the ParkingStation "Passo delle Erbe", I would like to integrate the real-time measurement of my parking in the Open Data Hub

[rcavaliere]

Please consider the annexed document (Word document) for a more detailed description of the motivation and how the data could be retrieved in the Open Data Hub. There is also an API specification document from the technological supplier of the parking monitoring solution.

The request for this issue is to implement the Data Collector (incl. transformer) so to enable the real-time data flow in the Open Data Hub.

Data should be licensed as open data, meaning that they should be then immediately visible on all demonstrative applications connected with the Open Data Hub.

250127_SpecificheAPI_Affluences.pdf

260629_SpecificheIntegrazione_NOI_v1.1.pdf

[Luscha]

@rcavaliere I started the analysis of the endpoint bellow is a report and a corrected integration proposal:

1. The api key they provided is not granted the rights to access https://data.affluences.com/v1/data/timetable/ resource (i get 104).
2. entries, exits, waiting_time are instant measurements in the realtime endpoint, they seems fo be populated only when someone is actually entering and leaving the facility meaning most of the time the value is "null" (0). This would lead to almost 0'ed timeseries. I honestly propose to drop them to avoid bloating the db with near-flat timeseries and since entries and exists.
3. I honestly discourage to add the timetable to the metadata with custom semantics, this would be the only provider providing this information in a free-custom format the clients will never be able to use.

[rcavaliere]

@Luscha some feedback to your concern:

1. Probably this method has been not been activated. I suggest therefore to not consider opening hours as metadata. We should instead include the field open as measurement, so to correlate with the occupancy information
2. No, I checked this with the Data Provider. Some of the real-time information supported by the API, in particular these entries and exits, is not available in the monitored parking station. We just have the occupancy information as relevant real-time data. We could then ping the API every 5 minutes and get the new data, as we usually do with parking Data Collectors.
3. Should be already answered in 1.

I have attached a new proposal for the data integration, also in the main issue description, what do you say?

260720_SpecificheIntegrazione_NOI_v1.2.pdf

[Luscha]

@rcavaliere v1.2 proposal is definitely more feasible and maintainable. I accept it and proceed with implementation

[Luscha]

@rcavaliere deployed in testing
https://mobility.api.opendatahub.testingmachine.eu/v2/flat,node/ParkingStation/*/latest?where=sorigin.eq.Affluences

please refer only to stations whit name "urn:*"