Only class with name "Functional" on Sunday 5th has time: 09:30 (assumed BST) i.e. 08:30 UTC, 2 hours earlier than time on the feed
I imagine the issue here is something like the conversion from BST to UTC accidentally going the wrong way round. So rather than converting a 09:30 from BST (+01:00) to UTC (+00:00) by subtracting an hour (08:30) it has accidentally moved it to +02:00 (Egyptian time) by adding an hour. A Z has then been appended to the end of the time in order to label it (incorrectly) as UTC
Until this is fixed, we are going to have to manually subtract 2 hours from every time until we hear otherwise
So please let us know if and when you get to work on this so that we can remove our fix ASAP and ensure customers don't end up going to Leisure Centres 2 hours late!
Hi,
Big fan of the feed
However, we (at imin) have noticed a rather severe issue with the data - all session datetimes are out by 2 hours!
An example:
Example:
19876313
I imagine the issue here is something like the conversion from BST to UTC accidentally going the wrong way round. So rather than converting a 09:30 from BST (+01:00) to UTC (+00:00) by subtracting an hour (08:30) it has accidentally moved it to +02:00 (Egyptian time) by adding an hour. A
Z
has then been appended to the end of the time in order to label it (incorrectly) as UTCUntil this is fixed, we are going to have to manually subtract 2 hours from every time until we hear otherwise
So please let us know if and when you get to work on this so that we can remove our fix ASAP and ensure customers don't end up going to Leisure Centres 2 hours late!