South Roadside Falls

So this post marks one of those extremely rare occasions where I actually wrap up a series of posts, without leaving any unfinished ones forgotten in Drafts or letting the project scope creep out of control so it can never finish at all. Or at least that will be true assuming I can get this one finished. This series covers a group of mostly-nameless seasonal waterfalls along the Sandy River stretch of the Historic Columbia River Highway. To recap, this was part of a mid-pandemic effort to find obscure and less-visited places to go, in order to get outside while avoiding all other human beings to the greatest possible degree. That worked out really well in a lot of places but not here, exactly, as people kept stopping to take photos of whatever I was taking photos of. Ok, technically it happened twice. So far we've had a look at:

• Keanes Creek Falls, the southernmost of the five
• City Limit Falls, the northernmost of the bunch
• North Roadside Falls, continuing south from there
• Middle Roadside Falls, apparently the tallest one, if you trust my math and map-point-picking skills

And this one finishes the set, unless you count a couple of others that are so seasonal that they only seem to run literally in the middle of big winter storms. Which to me just doesn't seem worth pursuing.

Heightwise, given the top (167.75' / 162.25') and bottom (61.45' / 61.22'), the math says it's around 100.8 - 106.5 feet high. Which, possibly.

You might notice that the highway shoulder is especially wide along this stretch of road. It turns out the stretch of riverbank through here is a small Metro-owned public park, and it's here to provide public river access, specifically public fishing access. There aren't any signs around that say this, but there's plenty of room to park, and usually a car or truck or two parked here, so I guess enough people find out about the place by word of mouth. This is actually not the only spot like this; depending on whose map you look at there are either three (lettered A thru C) or five (numbered 1-5) of them, all on the east bank of the Sandy, and located between the Stark St. & Troutdale bridges.

And if this doesn't sound like a very Metro thing to do, you're absolutely right; these sites were part of the old Multnomah County park system before Metro absorbed it in 1994, and you can check out a 2008 post of mine for more than you probably care to know about that whole thing. I couldn't find any info on when the county may have purchased these places, the closest data point I have is a

a March 1963 Oregonian article about the county's ambitious new parks plan, with a map showing roughly where the county's new parks would be. Their focus at the time was on adding neighborhood parks to serve then-unincorporated parts of the county, and the only ones, current or proposed, east of the Sandy would have been neighborhood playground-type ones in the Springdale and Corbett areas. The river access parcels aren't mentioned and don't appear on the map, so either the county hadn't bought them yet, or river access fell under a separate budget category or a whole different department and didn't count.

As I understand it, the rationale behind these fishing spots is that the Sandy might be the best river for salmon in the region, and the stretch between the two bridges is possibly the best part of the river, and it would be undemocratic to have it limited people who can afford to own a boat, or build a house on the river. For many years the state prohibited fishing from boats anywhere upstream of the Stark St. bridge for similar reasons, the idea being boaters had an unfair advantage over people fishing on the riverbank when both were allowed. So when the state pushed the no-boats boundary back four miles to Oxbow Park in December 1987, some people reacted like democracy itself was being eroded in favor of rich people always getting whatever they want. And who knows, maybe that really was an early symptom on the way to January 6th 2021. This happened in the middle of the Reagan-Bush era, when a lot of little things like this happened, so the timing's spot on, at least.

Anyway, here's the list, starting here and heading downstream:

• Unit C (1.21 acres, aka unit 4) is where we're at now. If I'm reading it right, a 2007 iFish forum post is saying this place is called "The Willows" out in the real world.
• Unit 5 is not actually river access, but two tiny pieces of land on the waterfall side of the road, 0.11 and 0.01 acres respectively, with the larger one possibly including the falls we came here to look at. For anyone who missed the wrong day in grade school weights and measures class, one one-hundredth of an acre is equal to about 344 square feet, equivalent to an 18.5' square.
• As for unit 2? Maps that have the sites numbered it show it as a long and extremely skinny bit of riverbank, roughly the whole stretch between City Limit Falls and North Roadside Falls, while maps that give the sites letters don't show this one at all, and PortlandMaps has it listed as private property, so I'm not sure what's going on here. I think the forum post from above is saying this area goes by "Duck Hole", unless maybe the highway speed limit signs have moved around since 2007. Google seems to think it's a popular place, or at least one that gets talked about a lot, so I dunno. I guess my point here is that if you want to know more about it (and what the legal situation is, etc.) your best bet is to go ask someone who actually knows what they're talking about, because I sure don't.
• Unit B (0.43 acres, aka unit 3) is further downstream, right around the (relatively) busy intersection of the Columbia River Highway & Woodard Road. Thing is, there's not really anywhere to park around this one, and there are several "No Parking" signs are posted on both streets just in case anyone even thinks about trying it. So this one may be more of a locals-only thing. Or maybe it isn't a thing at all; I am absolutely clueless about the fish situation here, and you're on your own for that.
• And finally there's Unit A (0.1 acres, aka unit 1), which may have been public access at one point but is now home to a boat launch for the Multnomah County Sheriff's River Patrol, accessed from a shared driveway to the south that's clearly posted No Trespassing. Given what the river patrol does, and the kind of river the Sandy is, the place is probably haunted too. I mean, if you believe in that sort of thing, and I'm not saying I do.

Middle Roadside Falls

Continuing from the previous post, a short walk or drive south on the Columbia River Highway brings us to the next seasonal waterfall. "Middle Roadside Falls", which is another of the 'meh' names I made up just so I'd have some titles for blog posts. This one might be the tallest of the five waterfalls in the area, assuming you trust any of the height numbers I've been coming up with, which I'm not sure I do. The top (189.14' - 198.31') and bottom (64.93' - 86.06') points I came come up with once again give a height number that seems to be on the high side. As in 100-130 feet high, or technically 103.08 - 133.38, although I doubt the second decimal place is significant. I guess what I'm trying to figure out is whether my LIDAR-assisted guessing is any more accurate than the old-fashioned kind, and what I'm doing wrong if it isn't.

On the subject of whether to believe state GIS systems, the unnamed stream here (like the others nearby) appears on a state map of barriers to migratory fish. Which is technically true, but the entry here is just for the long culvert under the street, with no mention at all of the maybe-130' waterfall about a foot or two upstream of the pipe. So if anyone's divvying up habitat grant money sight unseen based on that dataset, it could lead to some really odd projects getting approved. At least the map has you click through a EULA first, agreeing that the data comes "as is" and isn't guaranteed to be accurate or complete or useful for any purpose whatsoever, which I guess is nice because nobody ever clicks though EULAs without reading them.

(The same dataset insists there's an 8' waterfall on Johnson Creek just west of Bell Ave. in Milwaukie, complete with a midcentury fish ladder, that as far as I can tell doesn't actually exist. But I haven't yet gone looking for it in person, and I may need to go do that just to be extra sure.)

North Roadside Falls

In the previous post we made a quick visit to "City Limit Falls" (a name I just made up), one of about five seasonal waterfalls you'll see right along the Columbia River Highway as it heads south out of Troutdale. Continuing south from there brings us to the middle trio of the five, which occur within sight of each other on a 0.2 mile stretch of the road. Inconveniently the middle three don't have names or much in the way of distinguishing features, so these photos got hung up in Drafts for months while I figured out what to call them. Which is a really dumb problem to have, so I'm not going to bore you going on about it. The important thing is that we're visiting "North Roadside Falls" this time around. The name describes the location, and (to me) "Roadside" also has an air of "roadside attraction" which kind of fits because of a weird phenomenon I noticed: Normally people just drive on through here on their way to the big tourist spots, but if you stop and people see you standing there taking photos, they'll stop and take photos too. Or at least it's happened to me a couple of times. I dunno, maybe I just look like I know what I'm doing, and people think if they don't stop where the experts do they'll miss out on the full Gorge tourist experience. Ok, that or I'm drawing a lot of unjustified conclusions from a sample size of two. And your mileage may vary, obviously.

But if people will stop if they see you taking photos, maybe they'll also stop for actors pretending to take photos and then decide they need a cup of your "famous" hot cocoa or lemonade or maybe a hot dog from your stand nearby. And maybe pick up a commemorative shot glass or spoon from your gift shop next door for their display case back home, and while they're occupied you slap a bumper sticker on their RV and they proceed to drive around the country proudly advertising your cozy little tourist trap. And more tourists come, and you put in a motel, and a petting zoo, and you light the falls at night, and add a pump system so they don't dry up in the summer, and you put the kids thru college that way. But then they're off doctoring and lawyering and succeeding generally and don't want to take over the family business, so after a while you sell the place and retire to Florida, and the new owners let it go to seed and eventually burn it all down for the insurance money and do 6-10 years in the state pen for it, and I've completely forgotten where I was going with this idea.

Anyway, as in the previous post, I looked at the state LIDAR map to try to figure out how tall this one is. Given a top point somewhere between 132.53' and 152.59' above sea level, and a base in the 62.47' - 79.21' range, that comes to, er, 53.32' - 90.12', which is broad enough to be almost meaningless. I think the 79.21' number is an outlier for the base as most of the other height measurements around that point are more like 64'. And yet, a height somewhere in the 70'-90' range seems way too tall again, even knowing that we're only looking at the bottom part of the thing from street level. So who knows, really.

City Limit Falls

Ok, so back in May of last year I did a post about Keanes Creek Falls, one of the little seasonal waterfalls along the Sandy River stretch of the old Columbia River Highway. (Specifically, the one across from where the old Tippy Canoe dive bar used to be.) I mentioned in passing that it was the southernmost of about five waterfalls along a 0.6 mile stretch of the road, and it should come as no surprise to anyone that I decided I had to go back and visit the others. Which I did, so (after the usual delays) here we are at another of them.

Now, the problem with this sort of mini-project is that blog posts need titles, but none of these waterfalls seem to have names, and the creeks they're on also don't have names. So I figured I'd have to make up some nicknames for them just to tell them apart. Which is the hard part, of course; there's an old tech industry saying dad joke that the two genuinely hard problems in Computer Science are cache invalidation, naming things, and off-by-one errors.

In any case, here we are at the northernmost of the five, which happens to be just a few feet outside, or possibly inside, of the current (as of December 2022) Troutdale city limit along the old highway. That seems to be the only landmark nearby so I went with "City Limit Falls" for this one. Google seems to think there aren't any other waterfalls by that name anywhere on Earth, which may be a clue that it's a dumb name. For one thing, the name instantly becomes wrong if the city limit ever moves. But hey, I just need titles for a few blog posts, I'm not trying to be Columbus or anything.

For a little context on what's going on here, this stretch of the highway runs along a narrow bit of floodplain with the Sandy River one one side and near-vertical basalt cliffs on the other, generally about 150'-250' high. Those cliffs are actually the eroded west side of Chamberlain Hill, an old volcano that's part of the same Boring Lava Field as Portland's Mt. Tabor and Kelly Butte. Above the vertical edges the mountain is mostly gentle rolling farmland, with a steeper cone at the 909' summit. Note that you can't actually visit the top; the road that seems to go to there ends in a cluster of gated driveways, as you can see on Street View here. So you should probably ignore the auto-generated Peakbagger and Lists of John pages about the place. The key point right now is that it rains a lot here, and rain that falls on the west side of the hill has to go off a cliff to get to the Sandy River. This particular creek has carved sort of a north-facing grotto so it doesn't get a lot of direct sunlight even in late afternoons, and it's harder to see from the road than some of the others. You catch a glimpse of it heading south but there's nowhere to park when you're going that direction. Heading north there's room for about one car to park on the shoulder, though you won't really see the waterfall until it's in your rear view mirror going that way. So if you want a good look at this one, you sort of have to study a map and plan it out ahead of time. Honestly it's probably easier to walk or bike this one, though admittedly I haven't actually tried that.

I don't have any fun facts to share about this one, so I guess the next order of business is to figure out how tall it is. I'm not very good at just looking at things and guessing, and I don't own any climbing gear or surveying equipment to measure it either of those ways. But I do know my way around the state LIDAR map fairly well, so we'll see what we can come up with that way. The map has a "Bare Earth Slope (degrees)" layer, where the steepest terrain is coded as white and flattest is a dark grey. So the trick is to find the river/creek/stream you're interested in, then squint at the map and find the points where it becomes very steep and then flattens out again, and and take those as our top and base. Each point on the map has several elevation numbers, up to around 10-12 of them; then the slope at a given point is derived from those altitude numbers with a bit of simple calculus, which you fortunately don't need to compute on your own. For the overall height, take the highest and lowest elevation from both points (124.77' and 117.37' for the top point and 68.06' and 61.54' for the base), then do a little subtraction, and that gives you a range. Sounds easy, right? The only problem (which may not be a problem at all) is that this consistently produces numbers that are quite a bit higher than what I come up with standing at the base and guessing (which -- as I keep saying -- I am notoriously bad at). As in, I get around 50-60 feet (49.31' - 63.23' to be precise) from the map and would not have guessed over 25-30' here. I'm not sure where the discrepancy is creeping in; maybe the map numbers are absolutely spot on, and you just can't see the very top of the falls due to the angle. Or the point I picked as the top is somewhere above the real top and I'm picking up extra height that way. I'm honestly not sure.

Upper Perdition Falls

Back in October of last year (2021), I did a post about Perdition Falls, which is an unofficial name for the seasonal waterfall just to the right of Multnomah Falls. In that post I briefly mentioned something about there being another smaller waterfall on the same creek, just upstream and right next to the long-closed Perdition Trail. The trail closure means there's no legal way to visit the upper falls in person. It didn't occur to me that they might be visible from below, at least. But I happened to be at Multnomah Falls last week for lunch and as soon as I got out of my car some dusty weird corner of my brain went "Wait a minute, what's that?". There's really no mistaking it once you know it's there, and as a bonus that makes it easy to tell where the old trail was (and still is, unofficially).

The mildly weird part is that I don't recall ever seeing it before. This is only mildly weird, because my powers of observation are... a bit off. So it's entirely possible I've seen it regularly for years and it just sort of never registered somehow. But it also may have been completely hidden by trees before the 2017 fire, and it seems as though you can only see it from the I-84 parking lot and not from any closer, and I can probably come up with even more excuses if I have to.

In any case, I think I've located the falls on the state LIDAR map right around here, and I used the latitude & longitude from that placemark to create the embedded Google Map here, for anyone who has, I dunno, rocket boots and can get there without using the trail. The advanced technique of clicking around the area on the LIDAR map and guessing what spots might the top and bottom of the falls gives me height numbers in the 20-40 foot range most of the time, with the wide error bar completely due to the human in the loop.

The original dataset has latitude & longitude numbers out to a whopping eleven digits, which I actually had to trim down to six to make Google Maps happy. Which got me wondering just what these decimal places mean in terms of physical distance. One degree latitude comes to about 69 nautical miles, or 111.1 km, anywhere in the world, while the length of one degree longitude varies by latitude: It's the same 111.1 km at the equator, but around 79km at the 45th parallel, and a bit shorter than that in the gorge (the number eventually goes to zero at the poles). Going with the latitude number, one decimal place is 1/10 degree, or 11.1km, while a change in the sixth decimal place is 11.1cm. At eleven decimal places (or 10^-11 degrees), a change in the last digit is a distance of 1111 nanometers, which just so happens to be about one wavelength of near-infrared light of the type typically used in LIDAR. So while 11 digits looks impressive, I'm not sure how many of those are actual significant digits.

So I stumbled off a Google tangent at that point, as I tend to do, so here's a short list of links mostly about lasers that I'm not even going to try to relate back to the subject of this post.

• Slides from a Portland State geography class explaining how airborne LIDAR works, aimed at people who might be using the data later in the term.
• A 2018 paper calculates theoretical accuracy limits for LIDAR in self-driving cars, and comes up with something around 0.1mm.
• A 2019 paper proposes that better resolution can be achieved by ditching the lasers in favor of spooky quantum magic with entangled photons.
• Which in turn leads to Wikipedia articles about things like quantum metrology (which LIGO might use someday) and quantum lithography (which might be used in chipmaking someday)
• A paper about a specialized Leica camera designed for LIDAR applications. This particular model was from way back in 2011, so it's useful information in case they start showing up at Goodwill or something.
• There seems to be a lot of overlap between LIDAR vendors and major defense contractors, so you're always just a few clicks away from stuff like this article. One of the lesser-known Geneva conventions from the 1970s bans using lasers to blind people, and another bans any weapons that cause 'undue suffering'. The article argues that there's a way around these unfortunate legal obstacles, which is to use a laser powerful enough to instantly vaporize whoever it's used on, so they don't suffer first. And no suffering means there's no problem and you can go around lasering people to your heart's delight. Of course those lasers don't actually exist yet, not in airborne form at least, so (as usual) a massive federal research program is needed in order to bring this inspiring dream to life.

Rowena Plateau, June 2022 (II)

As promised in part I back in August, here are more photos from the Nature Conservancy preserve at Rowena, OR, taken back in June around the tail end of desert wildflower season. These were taken with an old Sony DSLR from Goodwill and a couple of equally old Sony/Minolta lenses, including a 50mm macro lens that I've decided I'm a huge fan of. If there's a trick to taking sorta-ok macro photos, without a tripod, on a windy day in the Gorge, I guess it would be to just take a ton of photos to boost the odds you'll get some decent ones between wind gusts. If I was actually trying to make money off this stuff it would probably help to find a really pretentious way to phrase that, maybe some mumbo-jumbo about the zen of inhabiting the still spaces inside the wind, and offer to teach people how to do that in expensive multi-day workshops. If only I could say all that with a straight face, and I was more of a people person, and also unscrupulous.

In any case, I unfortunately don't have an ID on the beetle in the first couple of photos. You can kind of make out that it has tiny hairs on its thorax that pick up pollen as it wanders around this arrowleaf balsamroot flower, sipping on nectar (or eating pollen, or whatever it's doing.) It seems reasonable to guess that some pollination happens while it goes about its business.

As the saying goes, the plural of "anecdote" is not "data", but a brief search came back with a few other photos on the internet of similar beetles on balsamroot flowers, so at minimum this is not a one-off occurrence: Someone's Flickr photo (taken further east on the Washington side of the Gorge), and stock photos on Getty Images and Alamy The Alamy one shows a pair of pollen-covered beetles mating on the side of a balsamroot flower, so it may not be safe for work if your boss is an especially prudish entomologist.

But I haven't seen anything in writing saying the plant is pollinated by such-and-such beetle. I did run across a 2005 study on the pollination needs of the plant. It notes that essentially no previous studies had been done on pollination for the whole balsamroot genus, but then zooms in on the habits of a couple of native bee species and never mentions beetles at all. The study was motivated by practical concerns, namely an interest in growing balsamroot seed commercially, as the plant seems to be good for habitat restoration, and both livestock and wildlife seem to think it's delicious. There are already other seed crops that rely on native bees, such as Eastern Washington's alfalfa seed industry and its dependence on alkali bees, so maybe it just seemed natural to focus on that and not the care and feeding of some weird desert beetle. And admittedly this beetle didn't seem to be in any great hurry to buzz away to the next flower, which helps if you want photos, not so much if you're an international seed conglomerate and your CEO needs a new yacht.

So we're at a dead end regarding beetles, but a Forest Service info page about the plant has a couple of other unrelated nuggets. First, it describes the flowers as "bigger than a silver dollar but smaller than a CD; about the size of a small floppy disk", which is overly wordy but gives you a strong clue as to the age of the author. Later, toward the end when it describes the plant's culinary and medicinal uses, it says cryptically that "The root could be used as a coffee substitute", without elaborating any further. A page at Eat The Planet repeats the claim, as do a lot of other search results, but nobody on the whole wide internet says whether the resulting beverage is regular or decaf. Which to me is the one key detail about anything described as a coffee substitute. No caffeine and it's just another way to make hot water taste bitter, which is not so interesting. Either way, the public deserves answers.

hnl ✈️ maui, september 2019

maui ✈️ hnl, september 2019

willamette sunset, 1/16/22

willamette sunset, 4/9/22

sunrise, 1/29/19

sunrise, 1/30/20

willamette sunset, 9/26/19

pdx ✈️ hnl, december 2019

pdx ✈️ hnl, may 2017

Kerf

Here are a few photos of Kerf, a pair of huge concrete rings at the SE Tacoma/Johnson Creek MAX station. It was (or they were?) created by artist Thomas Sayre for TriMet's Orange Line, and the Orange Line public art guide describes them briefly:

Two landmark sculptures, “earth-cast” on site, represent the influence of wheels on the area, from a 19th-century sawmill on Johnson Creek to the wheels of the MAX train.

By "earth-cast", they mean casting concrete onsite, in a Kerf-shaped hole in the ground, without the use of the usual wooden forms. This technique gives the concrete a sort of rough natural look, and it was the subject of Earthcaster, a 2016 documentary from North Carolina Public Broadcasting about Sayre and his work, including the creation of Kerf here.

But what if there's more to it than that? This spot is a major transit hub, with a lot of TriMet buses, the Springwater trail, US 99E (McLoughlin Blvd.), and even the Union Pacific line that Amtrak uses on its way to and from California. (It doesn't actually stop here, but in theory it could someday.) So it seems only logical to round things out with a couple of stargates, like in that one movie.

So in theory you could step through one of the Kerves here and pop out of Ring of Time or the Carwash Fountain, both along the downtown transit mall, or Big Pipe Portal on Swan Island, or possibly Arch with Oaks out in Beaverton. Sounds pretty amazing, if you ask me. The only problem being that this system isn't actually open to the general public right now, and TriMet officially denies all knowledge of any such thing being in the works. Maybe they're still quietly working out bugs in the system, or trying to bring down operating costs. Or maybe they're done with that part and are slogging thru federal bureaucracy now, trying to determine whether a stargate is considered an airport, a highway, or a railroad for regulatory purposes; whether each stargate needs a US Customs office, if there's no way to prevent international arrivals, that sort of thing.

International arrivals are certainly possible, by the way. A quick scan of the interwebs led me to a Chinese company in Shijiazhuang, Hebei Province that offers to crank out any kind of oversized custom art you need on an industrial scale, including large stainless steel rings that look unmistakably stargate-like.

But I have no idea if those -- or the varied local examples I listed earlier, for that matter -- are even compatible with Kerf. I don't know much of anything about stargate networking, but if it's anything like train networking, it's bound to be a lot more complicated than any layperson would expect. So if it turns out the two here can only talk to other Sayre stargates, I don't think there are any other local ones in Portland , but the internet says there are others in Raleigh and Lenoir, NC (saving a 3 hour drive between the two cities), plus one in Aurora, CO. And the latter one could be a problem due to its altitude (~5400') and the resulting air pressure difference. If you punch in "send me to Colorado" and as soon as the portal opens you're sucked through like it's a broken airliner window, that's going to lead to some bad yelp reviews, at minimum.

Rowena Plateau, June 2022 (I)

And here are some photos from a visit to the Nature Conservancy's Tom McCall Preserve at Rowena, out in the eastern Columbia Gorge on the way to The Dalles. This is another place that has showed up here from time to time over the course of this humble blog, most recently in 2017.

The (I) in the title is there because this slideshow is just phone photos, and I also have a bunch of DSLR ones from the same trip that I still need to sort through and upload. Now, a bunch of those photos aren't keepers because that's just inevitable when you bring a macro lens here on a windy day, but IIRC there were still a decent number worth sharing. I know better than to promise an exact date on when they might go up, but I'll try not to drag it out unneccessarily, if possible.

Tanner Springs wildflowers, July 2022

A few recent photos from Portland's Tanner Springs Park, a sort of pseudo-natural nature park righ in the middle of the Pearl District. This place was a regular staple here for a number of years, starting in 2006 and tapering off in 2014 for no particular reason. I happened to be in the area last month and wasn't in a hurry so I stopped in and ended up with a few wildflower photos, so here they are.

(I think it's fine to call them wildflowers, even if someone technically planted them here as part of a planned garden. I'm using the term in the sense of "local native species of flowering plant" and not by how "wild" an individual plant appears to be. Just tossing that out there in case any angry internet flower pedants stumble across this post. I have never actually met an angry internet flower pedant, mind you, but generally speaking if a thing exists, someone is mad about it on the internet. So it just sort of stands to reason.)

Fairy Falls

Ok, now we're paying a visit to the Columbia Gorge's Fairy Falls, a little 20' waterfall above Wahkeena Falls on a side branch of Wahkeena Creek. It isn't the tallest one, or the widest, or the loudest, or the most famous. It doesn't have the most water going over it; it doesn't have a weird name, or much in the way of historical anecdotes, or any of that. It's one of my favorites, though -- just look at it. Feel free to page through the photoset for a bit first and then come back to the post, if you want.

One of the many occasional projects I have going here is a very slow virtual trip around the Multnomah-Wahkeena Loop trail, with a post about each waterfall along the route in (roughly) clockwise order. So with this post we've finally made it up and across the top of the loop and down into the Wahkeena Creek watershed, and Fairy Falls is the first one we encounter on the way down. These posts have tended to run away from me, ending up full of all sorts of irrelevant tangents that I don't quite have the heart to delete. But Fairy Falls here is not really a complicated place and this post ought to be relatively short by my usual standards. I've combed the history books and the usual sources online and whatnot, and here's what I've got about today's destination...

• Back in the Upper Multnomah Falls post from last year I mentioned that a lot of guides to the Gorge insist there are exactly eight kinds of waterfall in the world, and go on to say that you can see five of the eight kinds right here along the Multnomah-Wahkeena Loop, and you can complete the set with a couple of other quick stops in the vicinity. So under that scheme, Fairy Falls is the canonical "fan-type" waterfall. There actually aren't many "fan-type" ones in the Gorge besides this one. In the wider region, the best-known example is probably Ramona Falls up near Mt. Hood. Something to keep in mind if you ever find yourself in a high-stakes "match the name to the waterfall photo" contest and need some easy points.

• I'm not sure who named Fairy Falls or when, since I couldn't find any mentions of it at all from before the Columbia River Highway and Wahkeena Trail opened. And afterward, any references to it just used the current name like it had always been called that. Given the steep terrain in the area, it probably didn't get a lot of foot traffic before the trail went in, so my guess would be that they stumbled across it while laying out the trail, decided to route the trail right past the base of it for dramatic effect, and figured it would need to be called something, as a highlight of the trail.

  Fairy Falls was first mentioned by The Oregonian as part of a 1921 article covering all the fun new hiking options that were now available out in the Gorge.

  Meanwhile the Oregon Journal first mentioned Fairy Falls in a similar 1919 hiking article, suggesting it as a refreshing pit stop on your way down after doing the overnight hike up Larch Mountain to watch the sunrise. (This used to be a very popular hike, right up until they built a road to the top of Larch Mountain in 1937.)

• I did find exactly one one example of someone calling it something besides "Fairy Falls", an undated photo with a caption calling it "Ghost Falls". The photo -- or at least the caption -- can't be any earlier than right around 1916 as it mentions the brand-new Columbia River Highway by name, and uses the new name "Wahkeena Falls" instead of the previous "Gordon Falls". No other examples have turned up besides this one so I don't think the name ever really caught on. Though if you squint just right the falls do kind of look like a ghost, of the ectoplasmic bedsheet variety. Given the politics of 1910s & 1920s Oregon, it's probably pure luck that nobody tried naming it "Grand Wizard Falls" or something, for reminding them of the Klan robes in their closets at home.

  Searching on the name "Ghost Falls" did come up with a couple of results elsewhere. The 1940 Federal Writers Project guide to Oregon claimed there was a Ghost Falls somewhere along the Eagle Creek Trail. That name obviously didn't stick either, and it's not even clear which falls they were referring to to since the guide didn't include a photo or a map. The same book also listed Punchbowl Falls as "The Devil's Punchbowl", which also didn't quite stick, maybe due to the famous Devil's Punchbowl out on the coast.

  Further afield, the search also returned an AllTrails hike page titled "Ghost Falls Trails via Bonneville Shoreline Trail", which sounds like something that would be in the Gorge, but it turns out to be for a Ghost Falls in Utah, and the shoreline in question was the shore of a vast former lake that existed during the last Ice Age, not the reservoir behind Bonneville Dam.

• Switching gears again, in several posts now I've mentioned a 2016 study on aquatic insects in the gorge. Wahkeena Creek has a special significance in that particular area, as it has several endemic species that exist nowhere else in the universe. However Fairy Falls (or "Fairy Falls of the East Fork" as the doc likes to call it) is on a side tributary and is apparently not interesting from a bug standpoint. The study just mentions the falls briefly: "trail goes through stream near base of falls; after multiple collections at this site since 1989, no sensitive species have been encountered.". So it might be that any weird caddisflies or stoneflies that may have once been here were wiped out at some point due to hikers tromping right thru their habitat. But the main stem of the creek is unique in flowing out of a nearby underground spring, with water several degrees colder than the other streams in the area, and the endemic species might require those specific conditions, which the East Fork has never had.
• Since Fairy Falls is one of the more photogenic waterfalls, it makes sense (to me) that there's a bit of recent classical music written about it, a piano solo for advanced students, one of several named after Gorge waterfalls by composer Ian Evans Guthrie. (The 'piano tune for...' link above goes to a page with a recording of the song, which seems to play in Firefox but not Chrome for whatever reason). If I didn't know it was recent, I could almost see it being composed for the Wahkeena Trail opening circa 1916. I say almost because the ending is probably a bit avant-garde for the conventional tastes of 1910s Portland.
• Oh, and one other thing from the Oregonian database: The May 9th 1937 Oregonian ran a page of photos from along the Multnomah-Wahkeena trail, with the reporter's wife and kids in most of them for scale. The Fairy Falls photo just showed the falls, though, so it looked just the same as it does now. Which should be normal and expected, but somehow it feels like photos and films from 1937 ought to contain a bit more 1937-ness somehow. And I'm not 100% sure what I mean by that. Maybe hardboiled Mafia goons at the top of the falls, dangling a rival gangster over the edge by his ankles. Maybe German or Japanese or Soviet spies, barely visible in the underbrush, casing the joint and taking detailed notes for future reference in a few years' time. And maybe then our hero & heroine (Fred Astaire as a tap-dancing G-man, and plucky reporter / aspiring swimsuit model Esther Williams) show up, and suddenly the falls transform into a water slide and pool and an all-singing, all-dancing, all-swimming, all-tapping musical extravaganza breaks out, and the various bad guys soon try to slink away into the shadows, twirling their mustaches, but then a big pie fight breaks out, and in the end they're defeated by the sheer power of Hollywood movie magic, and everyone lives happily ever after. The End.

Montgomery Pride

In a post back in January I mentioned something about there being another City Repair street mural on a closed section of SW Montgomery St., on the Portland State campus, which I was bound to do a post about sooner or later. So here are a few photos of Montgomery Pride, on the block of Montgomery between 6th & Broadway. The blurb for it on the City Repair project map describes it as "a design pattern that celebrates LGBTQ Pride, the 50th Anniversary of the Stonewall Uprising, and Marsha P. Johnson" and the 2019 painting of it as "an event that would bring together the LGBTQ community, Urban Planning community, and the PSU community to turn an unattractive street into an enriching temporary public event space."

The street closure happened as part of the university's major renovations to the business school building next door. The business school was the newest and swankiest building on campus when I was a student circa 1990 -- a student environmental group I was involved with tried to schedule meetings there, strictly for the nice cushy chairs -- but it couldn't compete with the new engineering school buildings, facilities-wise, and that simply wouldn't do. But there's always donor money available for re-swank-ifying business schools, and the one at PSU has reclaimed its rightful place as the newest, shiniest, swankiest, most blindingly metallic edifice on campus. Across Montgomery, for contrast, is the brutalist University Services Building, built in 1970 and seemingly unchanged since then (except for some late-2000s public art on the east side of the building).