Fix timestamps for map samples not being correct #21

New Issue

paul · 2022-05-08T15:06:02+02:00

paul commented

2022-05-08 15:06:02 +02:00

Currently, the Last-Modified header is used to determine the stamp of the maps.
This stamps is not only used to check if the maps are stale, but also to determine the timestamp base that is used for the samples.
Parse the time from the filename instead and use that as timestamp base, thus fixing all the timestamps of the samples.

Example:
It is currently 14:57, the Last-Modified header of of the maps is 14:52:17.
However, a part of the filename of maps indicates (in UTC) the date/time the maps start at: 202205081200, so 14:00:00. That should be used as the timestamp base, instead of 14:52:17.

Currently, the `Last-Modified` header is used to determine the stamp of the maps. This stamps is not only used to check if the maps are stale, but also to determine the timestamp base that is used for the samples. Parse the time from the filename instead and use that as timestamp base, thus fixing all the timestamps of the samples. Example: It is currently 14:57, the `Last-Modified` header of of the maps is 14:52:17. However, a part of the filename of maps indicates (in UTC) the date/time the maps start at: 202205081200, so 14:00:00. *That* should be used as the timestamp base, instead of 14:52:17.

paul added the

bug

label 2022-05-08 15:06:06 +02:00

paul self-assigned this 2022-05-08 15:06:11 +02:00

paul added reference 21-fix-ts-map-samples

2022-05-10 14:23:34 +02:00

paul referenced a pull request that will close this issue

2022-05-10 14:26:10 +02:00

Fix timestamps for map samples not being correct #22

paul closed this issue

2022-05-10 14:26:39 +02:00

Sign in to join this conversation.