Skip to main content

More Ham Radio Antenna Site Elevation Profiles and a Datasette Plugin

 As with most of my project, I'm probably having way too much fun with this elevation path thing! I got a new look at our usual Pantoll campground site this morning, and it's really, really cool! 

First though, let me point you towards the code that enables my recent fascination with our the layout of the terrain at our POTA activations. I've worked the datasette plugin that returns the coordinate's of a portion of the path between two points code through it's first very simple test case. I do not know if it will install correctly in any installation of Datasette yet, but it install's in mine, and it plays well with the instance in the test case, so here's the repository.

Note for new readers:

Datasette is a Python tool from Simon Willison, described as:

"Datasette is a tool for exploring and publishing data. It helps people take data of any shape, analyze and explore it, and publish it as an interactive website and accompanying API."

The gang and I have been slowly but surely working at applying Datasette to mapping our ham radio QSOs over the last several months, and in the process have been learning about ionosonde data sources, how to release Python packages, vector math, including cross products, (seriously, check that post out, it includes CoCalc plugins that let you see the cross product process we used to calculate the distance between a point and a path on the Earth. I think it's really cool), and GIS in the form of geocoding via Google Maps, We've use all that information to map the paths between QSOs along the ground as well as the paths of signals skipping between the ground and the F2 layer of the ionosphere. The maps have helped us better visualize high frequency radio propagation.


OK, so now onto more elevation paths! 

On our most recent trip to Mt. Tamalpais the gang and I, using TouCans on 20 meters, made POTA QSOs to both Alaska and New Hampshire among other places. I estimated—using a topo map—that the hill rolled down from our campsite at an 18 degree angle. Taking a look at the New Hampshire QSO with WK1V today, I was able to more accurately measure the elevation angle at 22 degrees. Here's the elevation profile of the starting from the campsite at the left hand edge, and extending down the mountain. My vague memories of RF engineering from grad school tell me that only the elevation over the first few wavelengths matter, but it's a lot of fun to look at the a longer path:




So, that's cool, but what about that Alaska, QSO? Does the elevation angle of our campsite point downwards towards Alaska as well? It's possible. Our campsite is at the top of a ridge. Let's look.


As it turns out, to get to Alaska from our campsite, you walk along the ridge and over Mt. Tamalpais!

What's that mean for my favorite radio journal assertion that the angle of the hill subtracts from the elevation angle? Well, for the first three wavelengths along the path, the ridge only rises 20 feet or so. Comparing that 20 foot rise over 60 meters to the 20 meter wavelength of the transmitted waves, that's basically flat, so while the upward slope may not have helped, it also just wasn't very noticeable to the signal at all. At least that's my contention at the moment.





Comments

Popular posts from this blog

How Many Files Can You Add to a GPT Project? An Interview with GPT-5 on Limits, Context Engineering Tips, and Chats

 Setting the scene: I’m tinkering with Project TouCans, knee-deep in radio logs, SQLite dumps, and Cesium code. Naturally, I’m wondering if shoving all this into one GPT Project is a recipe for brilliance… or for disaster. So I turn to Vril — you know, after Brainy from the Legion of Super-Heroes , because what else do you call your AI sidekick who always has the answers? Time to ask him straight up. [ As an aside, yes, GPT-5 has decided to sometimes call me Vail. I'm not sure why to be honest. Also, I asked Vril, er GPT-5, to write up our interview for me. Apparently, me asking it to 'Bro' up a few stories, just for fun, has convinced Vril that I use 'Like,' more than I actually might. ] Me (Vail): So Vril, how many files can I throw into a GPT Project before it just starts choking? Like, is there some magic number where the context window taps out and everything falls apart? GPT-5 (Vril): Great question. There’s no single hard file limit. What matters is ...

The Alcubierre Warp Drive Tophat Function and Open Science with Sage

I transferred yesterday's Mathematica file with the Alcubierre warp drive[2] line element and space curvature calculations to the  +Sage Mathematical Software System  today, (the files been  added to the public repository [3]).  If you haven't used Sage before, it's a Python based software package that's similar in functionality to Mathematica.  Oh, and it' free.  I also worked a little more on understanding the theory, but frankly, I made far more progress with the software than the theory.  What follows will be a little more of the Alcubierre theory, plus, a cool Sage interactive demo of one of the Alcubierre functions[1], as well as a bit about my first experience with using Sage. Theory The theory is fun, but it's moving slowly.  Here's the chalk board from this morning's discussion Alcubierre setup the derivation using something called the 3+1 formalism which means we consider space to be flat, (in this case), slices that are labelled ...

When Codex CLI Met Port 9 (Debugging WinError 10061 in a Whisper Pipeline)

When Port 9 Ate My Transcript When Port 9 Ate My Transcript A small debugging story about proxies, Codex CLI, and why localhost isn’t always your friend. CopaseticFlow field notes WinError 10061 Codex CLI + Whisper Environment gremlins There’s a particular kind of bug that feels like someone's been messing with your network stack again. You run a script from cmd.exe . It works. You run the exact same script from Codex CLI. It stops with: [WinError 10061] No connection could be made because the target machine actively refused it FFmpeg happily splits the audio. The Whisper API call dies immediately. No 401. No timeout. Just an instant refusal. Translation: that’s not an API error. That’s a socket being rejected. ...