You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I took a deeper look into it and it looks like the end dates (at least for Niedersachsen 2024) are wrong.
According to the ical spec this: BEGIN:VEVENT DTSTAMP:20220919T193841Z DTSTART:20240201 DTEND:20240202 SUMMARY:Winterferien Niedersachsen 2024 END:VEVENT
Means an Event starting at (german date format) 01.02.2024 00:00:00 and ending at 02.02.2024 00:00:00 or in other words, it is an allDay Event for the 01.02.2024
However the vacations are actually 01.02. and 02.02.
So the Event should look like this: BEGIN:VEVENT DTSTAMP:20220919T193841Z DTSTART:20240201 DTEND:20240203 SUMMARY:Winterferien Niedersachsen 2024 END:VEVENT
This is for all events for Niedersachsen 2024, so I assume it is affecting all events for all states.
You can test it e.g. importing the ics into the Thunderbird Calendar and it shows that the 02.02. is not taken into account on import of these data.
The text was updated successfully, but these errors were encountered:
First thanks to this awesome data set!
I took a deeper look into it and it looks like the end dates (at least for Niedersachsen 2024) are wrong.
According to the ical spec this:
BEGIN:VEVENT DTSTAMP:20220919T193841Z DTSTART:20240201 DTEND:20240202 SUMMARY:Winterferien Niedersachsen 2024 END:VEVENT
Means an Event starting at (german date format) 01.02.2024 00:00:00 and ending at 02.02.2024 00:00:00 or in other words, it is an allDay Event for the 01.02.2024
However the vacations are actually 01.02. and 02.02.
So the Event should look like this:
BEGIN:VEVENT DTSTAMP:20220919T193841Z DTSTART:20240201 DTEND:20240203 SUMMARY:Winterferien Niedersachsen 2024 END:VEVENT
This is for all events for Niedersachsen 2024, so I assume it is affecting all events for all states.
You can test it e.g. importing the ics into the Thunderbird Calendar and it shows that the 02.02. is not taken into account on import of these data.
The text was updated successfully, but these errors were encountered: