Difference between revisions of "User:Ekorren/Bicycle geohashes"

From Geohashing
imported>Ekorren
m (+elevation)
imported>Ekorren
m (+1 category)
Line 160: Line 160:
 
* '''distances''' are usually taken from the bike's speedometer.
 
* '''distances''' are usually taken from the bike's speedometer.
  
* '''hills''' is an approximate sum of significant uphill slopes. A steady slight up and down isn't significant. The numbers are estimated from the map, as the GPS adds too much static in the tracklog (and thus usually gets a much higher number)
+
* '''hills''' is an approximate sum of significant uphill slopes. A steady slight up and down isn't significant. The numbers are estimated from the map, as the GPS adds too much noise resp. measuring errors in the tracklog (and thus usually gets a much higher number)
 +
 
 +
[[Category:Bicycle geohash achievement]]

Revision as of 14:41, 26 April 2009

Hash Distance (to/from) hills other transport comment
2008-11-15 48 9 22.69km (appr. 15.5/7.2) 120m First bike expedition, very near location
2008-11-18 48 9 35.86km (14.21/21.65) 120m
2008-11-19 48 9 36.72km (11.34/25.38) 120m includes 12 km with a half-flat tyre
2008-11-22 48 9 19.33km (~ 8.5/10.8) 160m sub-zero temperature, lost a glove, snowfall
2008-11-29 48 9 41.95km (18.09/23.86) 500m partly ice covered slope
2008-12-12 48 9 77.30km (40.03/37.27) 700m Up a mountain, down a valley, through the fireiceswamps. 700m, lots of snow.
2008-12-15 48 9 78.63km (59.35/19.28) 300m back by train (49km) Notrespassing.gif Coordinates not reached, took train back after it got dark
2008-12-17 48 9 32.7km (14.2/18.5) 280m several km on ice covered forest tracks, back through heavy snowfall
2009-01-03 48 8 30.85km (15.9/14.95) 80m
2009-01-04 48 8 55.93km (25.77/30.16) 270m
2009-01-07 48 9 34.58km (11.90/22.68) 220m detour with some lake biking on the way back ;-)
2009-01-26 48 9 63.55km (~ 26/37.5) 400m several detours
2009-01-28 48 8 57.94km (23.91/34.03) 300m +1.2 km walking hash was not reachable by bike. detours account for most elevation and serious ice encounters
2009-02-13 48 8 24.51km 120m Plan B: train and bus Trainwreck.png Didn't make it by bike to the hash because of a torn tyre. Went by train & bus instead
2009-03-01 48 8 69.20km (37.52/31.68) 650m There were too many slopes, too much water (both frozen and fluid), not enough gravel, too little time and no food.
2009-03-08 48 8 45.23km (20.76/24.47) 300m 24px Got frequently stuck in a huge mess of sticky snow, and didn't reach the coordinates. Feels like at least 1000 elevation metres.
2009-03-19 48 9 46.45km (33.88/12.57) 980m back by public transport Trainwreck.png Distance back includes about 2 km of pushing the bike, excludes public transport and intentional walking parts. Also got stuck in snow again at +10°C. 980 m of significant uphill slopes.
2009-03-22 48 8 69.45km (ca. 35/34.5) 680m A no-snow expedition. Felt really easy...
2009-03-24 48 9 38.86km (ca. 17/22) 350m
2009-03-26 48 9 41.37km (16.39/24.98) 270m
2009-04-04 48 8 64.90km (32.84/32.06) 570m
2009-04-13 49 9 30.93km (19.75/11.18) ~420m Train Distances are (home->station + station->hash) / hash->station (with different stations)
2009-04-16 48 9 37.68km (ca. 13.5/rest) 120m Notrespassing.gif Total failure as expected. Went to Reutlingen afterwards
2009-04-25 48 8 56.1km (22/34) 220m Train
Sum (24 expeditions) 1112.71km 8250m
  • distances are usually taken from the bike's speedometer.
  • hills is an approximate sum of significant uphill slopes. A steady slight up and down isn't significant. The numbers are estimated from the map, as the GPS adds too much noise resp. measuring errors in the tracklog (and thus usually gets a much higher number)