Difference between revisions of "2024-10-18 35 -97"

From Geohashing
(rewriting this too, i was never really proud of it)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{meetup graticule|date=2024-10-18|lat=35|lon=-97}}
 
{{meetup graticule|date=2024-10-18|lat=35|lon=-97}}
 
== Location ==
 
== Location ==
A crop field bounded by 29th, 2830, 44th, and US 81, north of Union City, OK
+
A crop field just off US 81, north of Union City, OK
  
 
== Participants ==
 
== Participants ==
Line 10: Line 10:
  
 
== Expedition ==
 
== Expedition ==
Oklahoma is where part 2 of my vacation is taking place. I don't know if I should say ''vacation'', though, because this is more like the beginning of a family restructuring; in a few days, we'll drive to Tampa and move things from there. Anyway, this is where I'll be moving next. How long I'll be there, I can't figure that out.
+
Oklahoma - not what you expect from a suburban dweller like me. My father lives here and is most proud to call this home. It was my 8th time staying over, and things were normal, really... aside from that getting out of Florida was now inevitable. The trip, therefore, was mainly for reassurance purposes, and this didn't do much because, almost at the last minute, I chose to live in California instead. Anyway, I was here for the time being.
  
Looking at the hashpoints this morning, I noticed this one was reachable without losing too much common sense: it's a fenced field divided by Union Pacific railroad, and on both sides of the track are openings of the fences according to Street View. This is in contrast to many other points around here, which usually land on parcels that are fenced thoroughly (with chained gates), sometimes have No Trespassing signs, and often no Street View as it's surrounded by unpaved roads which the drivers don't glance twice at. And I'm not too fond of going to these undocumented parcels or jumping gates.
+
Then I saw this in the morning. Union City. I've been there, mostly for the thoroughfare to Mustang. A bit far, but that's everywhere here anyway. Satellite and Street View showed it could be done; there was an opening among the fences, likely because a railroad runs through it. Any Midwestern geohasher will know this and call it blatantly obvious, but what I had figured out now: most other points are fully fenced, and every landowner is proud of their land, so often you find the signs that haunt geohashers. That and often there's no Street View coverage, so I can only assume in that case that it's not worth it.
  
Again, I waited until my father came home, then told him I was driving just for the fun of it; he doesn't know about geohashing yet, and I suppose if he realizes the goal is to go to people's fields (mostly), he'd lose it. In front of them, I drove the crossover ([[2024-09-15 27 -81|not the same one]]) down the long driveway, and so the adventure began.
+
I had done quite a bit of manual labor the previous days and figured I'd have to do more this day, and I already knew the Mazda wasn't there, so I waited for my father to come home, and wanted to make the trip quick. A few minutes after the door squeaked, I exclaimed my want for exploration, and only that; I haven't told him about, and don't think he'll ever understand geohashing, not especially the "where exactly" part. He's got the landowner attribute in him, too.
  
Almost. Pulling over, I turned on the eTrex to get it used to the satellites, programmed my phone to the location, and off I went. First, it was through miles and miles of county roads, but the route I've took, I'm familiar with at this point; you can call it running errands. It runs through flat roads, then a rollercoaster, then flat roads again. Now, let me enlighten you on the wonder of Midwestern state highways; OK-152 is a nice example of one. Two lanes, one each direction; the speed limit is 65 mph (105 km/h); the road is badly maintained, there's no shoulder, and turns do not have dedicated lanes... and I was going above the limit so I wouldn't be picked on by my father. Anyone want to wish me luck for getting a good score for the Oklahoma driving test?
+
So off I went, turning on the new eTrex a few hundred yards in. County roads, county roads, astoundingly vertical county roads, county roads. I actually know this route just by turns. It's one of two ways we get onto OK-152, which makes a good example of state highways in the Midwest. Speed limit: 65 mph, which means people drive at least 70. Two lanes, one each direction, each barely wider than a semi, practically no shoulder most of the way. No turning lanes. Vehicle passing rules change, but no one really pays attention to them. People actually live in homes by the highway. And I was used to all of this, so I can say only small things happened.
  
A large load pulled out in front of me, but it was a heavy duty pickup carrying bales of hay, specks of which would loosen up and smack into my car. Not a huge problem, really, it's gone through worse. 152 was once again feeling long, and I kinda recognize the landmarks that tell me roughly what percentage of the stretch before the turn I'm in. The turn came, left there after the cars end. Heading now towards Union City, two trucks on the other lane, each carrying a piece of oversized bridge; eventually, Union City, which you can't really call a city, came about. At this point, I branched off the path of 152; it makes a turn at the stop sign to go straight to Mustang, but right now it's closed and the detour is to turn right from the last turn and pass through Tuttle. Anyway, the highway became a four-lane divided, and I was going limit 70 by the time I had to turn left to make the final stretch to the hashpoint.
+
OK-152 runs to Union City (which is officially a town), then turns to Mustang just as it hits town limits<ref>Although at the time this segment of 152 was closed for maintenance.</ref>. All I had to do is keep going straight, and I was now on course to El Reno, probably a more famous name in Oklahoma. Of course, where the hashpoint sits was between the two, so I went into a left turn lane, and I was now on course to the hashpoint.
  
I went below the limit this time, but as I was approaching the rails, I noticed that dust was emanating from what I assumed was the field. ''They're doing work on it right now?'' As I approached the railroad crossing, where a Union Pacific train ran well before I could cross, I realized that it was more semis with oversized loads (by the way, on an unmarked unmaintained road), and I think the dust was kicked up from braking. Barriers still down, I got a good look at the openings of the field; it's undoored, contrary to my expectations. However, it looks different: bales of hay run along part of the fence. Now to do is to wait for the oversizes and their escort to move along.
+
And then slight panic. Approaching the crossing, lots of dust, and I couldn't see from where. ''Wait, they're doing work on it right now?'' I thought the tractors were raging at the edge of the field and therefore the trip would be for nothing. 500 feet later, though, I discovered this wasn't true. First, a pickup... then semis carrying oversized loads. I've seen many of these on interstates, but on a county road, this was the first time<ref>I have seen slightly similar, though: a few months earlier, I was taking the same route to Union City, and coming up on a very steep incline, I noticed a huge box emanating from the apex... which turned out to be a huge tractor taking up the entire road. Somehow, there was a driveway that I could pull to.</ref>. Oddly enough, a train beat the both of us, so as I came up I tried moving over to give the convoy some breathing room once they did pass. We only had to wait a minute, though; the train consisted of 4 cars, locomotive included. When I checked out the clearing, it turned out, rather than the problem I expected, to be the clearing that I cherished on Street View; no doors, no signs, just a fencepost. Inward the field was the only thing that was different: hay bales along the actual fence.
  
Them moved along, I parked the crossover on a horizontal grade, and got my things. The field was one that's used to grow crops; of what, I wouldn't know, but after another pickup passed, I crossed the road and started rolling video with the ZS70. Since the eTrex was set on multi-band, locating was quite easy; in fact, maybe a bit too easy, because like last time, I just wanted to find it and go; I unfortunately stepped on some crops in doing so. The exact point has crops that haven't sprouted quite yet, whilst further south the crops matured enough to have wide greens. In my haste, however, I just took photos of the proof, and left; I only took photos of the surroundings from outside the bounds, because I didn't want to walk back.
+
So I parked near that clearing on a ditch. I now wish I hadn't; it looked like the Mazda was about to tip over. Then I phased through the clearing, followed the GPS, and there I was. And it's as hasty as it sounds. I stepped on some crops trying to find my way through, and I never bothered to take photos of the point itself, relying instead on video I took. And the haste was worsened when I got there. Oklahoma, being a thoroughly conservative and agrarian state, is a haven for arms, people who have only three emotions, and harsh punishments, so as soon as I figured I was there, I got out, fearing that the two pickups that passed were potentially landowners. That small unluck never hit, but I didn't want to run past it again, so I just took photos of the field once I was outside.
  
Then home. Same route. I was going even faster now; I went 60 where I should be going 45. I'll really ace the Oklahoma driving test!<ref>Since I have a Florida license, there's actually no need for me to take a driving test to receive an Oklahoma license.</ref> Anyway, if you want to discount more oversizes on 152 and kids sitting on the side of the road with a dad running across, the trip back was fine, and maybe a good thing I went at speed because I was interrupted while writing the beginning to help my father. I wasn't scolded.
+
Now that was done, I went home, same way. Only other thing that happened: on a county road, two kids on the side of the road, and a dad running across. The haste did, however, prove effective; trying to write about this, I was called over to the barn.
  
Distance going to the hash, according to the eTrex, was 50 km (31 miles). It means I used slightly less than 2 gallons of fuel, even with my chaotic driving.
+
"Where did you go?" "Union City. I didn't realize it was that far." And then I got to work.
  
 
<references />
 
<references />

Latest revision as of 21:52, 8 March 2025

Fri 18 Oct 2024 in 35,-97:
35.4350572, -97.9540501
geohashing.info google osm bing/os kml crox

Location

A crop field just off US 81, north of Union City, OK

Participants

10d100h

Plans

Kind of on impulse, really: camera, eTrex Solar, go.

Expedition

Oklahoma - not what you expect from a suburban dweller like me. My father lives here and is most proud to call this home. It was my 8th time staying over, and things were normal, really... aside from that getting out of Florida was now inevitable. The trip, therefore, was mainly for reassurance purposes, and this didn't do much because, almost at the last minute, I chose to live in California instead. Anyway, I was here for the time being.

Then I saw this in the morning. Union City. I've been there, mostly for the thoroughfare to Mustang. A bit far, but that's everywhere here anyway. Satellite and Street View showed it could be done; there was an opening among the fences, likely because a railroad runs through it. Any Midwestern geohasher will know this and call it blatantly obvious, but what I had figured out now: most other points are fully fenced, and every landowner is proud of their land, so often you find the signs that haunt geohashers. That and often there's no Street View coverage, so I can only assume in that case that it's not worth it.

I had done quite a bit of manual labor the previous days and figured I'd have to do more this day, and I already knew the Mazda wasn't there, so I waited for my father to come home, and wanted to make the trip quick. A few minutes after the door squeaked, I exclaimed my want for exploration, and only that; I haven't told him about, and don't think he'll ever understand geohashing, not especially the "where exactly" part. He's got the landowner attribute in him, too.

So off I went, turning on the new eTrex a few hundred yards in. County roads, county roads, astoundingly vertical county roads, county roads. I actually know this route just by turns. It's one of two ways we get onto OK-152, which makes a good example of state highways in the Midwest. Speed limit: 65 mph, which means people drive at least 70. Two lanes, one each direction, each barely wider than a semi, practically no shoulder most of the way. No turning lanes. Vehicle passing rules change, but no one really pays attention to them. People actually live in homes by the highway. And I was used to all of this, so I can say only small things happened.

OK-152 runs to Union City (which is officially a town), then turns to Mustang just as it hits town limits[1]. All I had to do is keep going straight, and I was now on course to El Reno, probably a more famous name in Oklahoma. Of course, where the hashpoint sits was between the two, so I went into a left turn lane, and I was now on course to the hashpoint.

And then slight panic. Approaching the crossing, lots of dust, and I couldn't see from where. Wait, they're doing work on it right now? I thought the tractors were raging at the edge of the field and therefore the trip would be for nothing. 500 feet later, though, I discovered this wasn't true. First, a pickup... then semis carrying oversized loads. I've seen many of these on interstates, but on a county road, this was the first time[2]. Oddly enough, a train beat the both of us, so as I came up I tried moving over to give the convoy some breathing room once they did pass. We only had to wait a minute, though; the train consisted of 4 cars, locomotive included. When I checked out the clearing, it turned out, rather than the problem I expected, to be the clearing that I cherished on Street View; no doors, no signs, just a fencepost. Inward the field was the only thing that was different: hay bales along the actual fence.

So I parked near that clearing on a ditch. I now wish I hadn't; it looked like the Mazda was about to tip over. Then I phased through the clearing, followed the GPS, and there I was. And it's as hasty as it sounds. I stepped on some crops trying to find my way through, and I never bothered to take photos of the point itself, relying instead on video I took. And the haste was worsened when I got there. Oklahoma, being a thoroughly conservative and agrarian state, is a haven for arms, people who have only three emotions, and harsh punishments, so as soon as I figured I was there, I got out, fearing that the two pickups that passed were potentially landowners. That small unluck never hit, but I didn't want to run past it again, so I just took photos of the field once I was outside.

Now that was done, I went home, same way. Only other thing that happened: on a county road, two kids on the side of the road, and a dad running across. The haste did, however, prove effective; trying to write about this, I was called over to the barn.

"Where did you go?" "Union City. I didn't realize it was that far." And then I got to work.

  1. Although at the time this segment of 152 was closed for maintenance.
  2. I have seen slightly similar, though: a few months earlier, I was taking the same route to Union City, and coming up on a very steep incline, I noticed a huge box emanating from the apex... which turned out to be a huge tractor taking up the entire road. Somehow, there was a driveway that I could pull to.

Photos

Achievements

TwoToN.png
10d100h earned the Two to the N achievement
by reaching 21 hashpoints on 2024-10-18 35 -97 and is promoted to Level 1 (Coordinates reached).