Tiamat NSR GTFS E-Tag changes daily on unchanged dataset

[kareblak]

We're pulling the NSR GTFS stop dataset daily to sync against local databases. Upon retrieval we launch a HEAD request to compare E-Tags before pulling and syncing the dataset.

It seems like the E-Tag is changed on every push of the file to GCS, even though no changes are observed.

curl -I https://storage.googleapis.com/marduk-production/tiamat/Current_latest-gtfs.zip

HTTP/2 200 
content-type: application/octet-stream
x-guploader-uploadid: AAO2VwrVAxp2BJP-BHyDfj3RFn4PvzHPLA6e6WpHSNmIz5QTdOY2hEjEfd1dOKHirqfeeBoS
expires: Wed, 14 May 2025 10:25:26 GMT
date: Wed, 14 May 2025 09:25:26 GMT
cache-control: public, max-age=3600
last-modified: Wed, 14 May 2025 01:30:04 GMT
etag: "57d384c00814a627954e47b18fd0bb4e"
x-goog-generation: 1747186204859602
x-goog-metageneration: 1
x-goog-stored-content-encoding: identity
x-goog-stored-content-length: 2810293
x-goog-hash: crc32c=Skpd3g==
x-goog-hash: md5=V9OEwAgUpieVTkexj9C7Tg==
x-goog-storage-class: STANDARD
accept-ranges: bytes
content-length: 2810293
server: UploadServer
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

Will comment on the next days' changes