Difference between revisions of "2022-03-10 53 10"

Revision as of 00:56, 15 July 2022

Location

on the train tracks in Hamburg-Wandsbek

Participants

Leidenfrost

Expedition

I paid 6,90€ for a day-ticket in Hamburg AB, got on the bus, rode to Hamburg-Rahlstedt, got on the RE81 until Hasselbrook which was the train that passed over the hash. I tried to take photos while we passed over the hash, but we were travelling at a substantial speed, and my GPS accuracy was very low, so I failed there, but the train did not derail, so I claim I got the hash. I took care to sit in the appropriate direction to make sure to get there as close as possible there and back again.

I rode this exact line many times from Hamburg-Rahlstedt, where I live, to Hamburg-Dammtor, where I study. I do not carry an actual GPS device with me, but google does track me, so I got a takeout of my location-data, which I will supply here for an example travel, this was at night:

 {
   "latitudeE7": 535531337,
   "longitudeE7": 100071936,
   "accuracy": 55,
   "source": "VISIT_DEPARTURE",
   "deviceTag": 1073881512,
   "timestamp": "2019-10-31T01:57:38.036Z"
 }, {
   "latitudeE7": 535497103,
   "longitudeE7": 100124841,
   "accuracy": 65,
   "deviceTag": 1073881512,
   "timestamp": "2019-10-31T01:57:56.849Z"
 }, {
   "latitudeE7": 535714425,
   "longitudeE7": 100232083,
   "accuracy": 200,
   "deviceTag": 1073881512,
   "timestamp": "2019-10-31T02:00:14.999Z"
 }, {
   "latitudeE7": 535690554,
   "longitudeE7": 100728474,
   "accuracy": 165,
   "deviceTag": 1073881512,
   "timestamp": "2019-10-31T02:04:34.804Z"
 }, {
   "latitudeE7": 535866650,
   "longitudeE7": 101237365,
   "accuracy": 200,
   "deviceTag": 1073881512,
   "timestamp": "2019-10-31T02:08:54.998Z"
 }, {
   "latitudeE7": 535878703,
   "longitudeE7": 101257108,
   "accuracy": 691,
   "deviceTag": 1073881512,
   "timestamp": "2019-10-31T02:10:55.976Z"
 }, {
   "latitudeE7": 536039370,
   "longitudeE7": 101539279,
   "accuracy": 54,
   "source": "VISIT_ARRIVAL",
   "deviceTag": 1073881512,
   "timestamp": "2019-10-31T02:12:14.999Z"
 }