Difference between revisions of "2008-09-19 49 -123"

From Geohashing
imported>Robyn
(I liked geohashing better when the geohash stayed in the same place all day!)
 
imported>Robyn
(Come on peerrrron!)
Line 1: Line 1:
 
==Location==
 
==Location==
 
Drawing on yesterday's experience, I'm going to assume that because peeron isn't reporting anything yet, that the coordinates listed at [[2008-09-19]] will change. At 7 a.m. those coordinates are .3528730, .7527032, putting the geohash very near to where it first appeared yesterday, this time about 5 km off the Sunshine Coast, between Sechelt and Roberts Creek. I'm willing to drive up and rent a boat more substantial than a kayak, but I want to make sure it's the right geohash location first. This is frustrating!
 
Drawing on yesterday's experience, I'm going to assume that because peeron isn't reporting anything yet, that the coordinates listed at [[2008-09-19]] will change. At 7 a.m. those coordinates are .3528730, .7527032, putting the geohash very near to where it first appeared yesterday, this time about 5 km off the Sunshine Coast, between Sechelt and Roberts Creek. I'm willing to drive up and rent a boat more substantial than a kayak, but I want to make sure it's the right geohash location first. This is frustrating!
 +
 +
==Location at 08:30==
 +
Still no peeron. Still .3528730, .7527032 on the day page.

Revision as of 15:28, 19 September 2008

Location

Drawing on yesterday's experience, I'm going to assume that because peeron isn't reporting anything yet, that the coordinates listed at 2008-09-19 will change. At 7 a.m. those coordinates are .3528730, .7527032, putting the geohash very near to where it first appeared yesterday, this time about 5 km off the Sunshine Coast, between Sechelt and Roberts Creek. I'm willing to drive up and rent a boat more substantial than a kayak, but I want to make sure it's the right geohash location first. This is frustrating!

Location at 08:30

Still no peeron. Still .3528730, .7527032 on the day page.