As a traffic manager I would like to integrate "traffic events" of the regional roads in the Province of Bolzano in the Open Data Hub

[rcavaliere]

It deals with the integration of this PR: #306

It depends on #263 since it needs the extension for integrating events type

[Piiit]

@rcavaliere I think we can close this, right?

[rcavaliere]

@Piiit did you integrate the DC in testing environment (see above linked PR)?

[Piiit]

The related PR was automatically closed by Github, I will integrate it now (indirectly by myself, because I renamed a git branch)

[Piiit]

@rcavaliere The DC has only a event-uuid, but misses the event-series unique identifier...

The event UUID is composed of:

• beginDate
• endDate
• messageId
• messageTypeId
• X
• Y

Should I build the event-series-uuid with these fields?

• messageId
• messageTypeId

[rcavaliere]

@Piiit sorry I did not understand. We miss some fields to generate the event UUID, correct? In this case can't we use just these 4 fields to generate the UUID?

[Piiit]

we have two UUIDs here, one for the event itself and one for the event-series... since the second did not exist when the DC has been written, I ask, which fields form a single event, and which fields should be used to form an identifier for series of events? If this DC has only single events and no series, we can just use the same UUID (of all six fields) for event-uuid and event-series-uuid

[Piiit]

In this case can't we use just these 4 fields to generate the UUID?

The source code uses all 6 fields at the moment, which should I take out?

[Piiit]

@rcavaliere The date interval seems to be wrong, I check that now

[Piiit]

You can test everything with https://mobility.api.opendatahub.testingmachine.eu/v2/flat,event/PROVINCE_BZ

[rcavaliere]

@Piiit ok let me test it in the next days...

[Piiit]

@rcavaliere Perfect, the date issues are solved now

[rcavaliere]

@Piiit I have tested the DC. I have the following open points:

• description is expected to be a string providing more details about the event (formatted as "description_IT | description_DE")
• event_interval is not properly formatted (e.g. "["2022-04-20 00:00:00",)") -> please just use "[ ]" or "( )". I have seen that in some cases the information of the event end date ("evend") is not available - if not provided, I would expect to always receive this value but to have something like evend = ""
• what information is stored in our field "name" (I see a number at the moment...)?

I have already reported these points to @noctho. Please let me know, once checked / solved we can put the Data Collector in production