Login
Finalizing Thoughts on the Elevation API Datasette Enrichment for Ham Radio QSO Paths
24 April 2024 at 15:46
I've outlined the work on the ham radio QSO Google Maps Elevation API Datasette Enrichment (try saying that 3 times fast) over the last several days. What I haven't talked about much, but thought about pretty often is what the released elevation enrichment should do. Here goes.
The Datasette enrichment will store the JSON data returned from the Elevation format in a database column named 'elevation'. Remember, the enrichment is taking two coordinate pairs that form a QSO like the brown line shown between Villa Nueva, NM and Idaho (KJ7DT's QTH).
It then determines the endpoint of a line that only covers the first 200 meters of that path, shown as the blue line below:
(Yes, 8 year-old Tawnse and I were sitting on the side of the 'cliff' on the other side of the Pecos River from the campground during that QSO. Yes, Tawnse does have a lower center of gravity than I do and led me up that path. Yes, I did have a heck of a time getting back down once I turned around and saw where I was. Please reference Tigger. Up the Tree. With Roo. for a literary example.)
{
"results" :
[
{
"elevation" : 123.6165237426758,
"location" :
{
"lat" : 37.72489522009444,
"lng" : -122.4229361744053
},
"resolution" : 9.543951988220215
},
{
"elevation" : 123.4337463378906,
"location" :
{
"lat" : 37.72489438728456,
"lng" : -122.4229250613661
},
"resolution" : 9.543951988220215
},...
From there, I've written at length over the last few days about how to make an elevation chart like the one shown below. 
Only the data labeled as "elevation" is used in the chart even though there's more information to be had in the JSON response. At the moment, that data is simply being discarded. Other users of the enrichment might have a need for it. Other users might also have different uses for the data altogether than an elevation chart in base64 text encoded png format, (the sole output of the enrichment at this time.)
So! The enrichment will be modified to simply store the JSON data. I'll make a second enrichment that will create the charts I require. The inputs to datasette-enrichments-gmap-elevation will be:
latitude1,longitude1,latitude2,longitude2,optional_sub_path_length_default_200_m
Where the first four arguments are the start and end coordinates of the entire path, and final, optional argument specifies how many meters long the path segment should be and defaults to 200 m.
The output will simply be the returned JSON data stored in a column titled 'elevation'.
I'll create a second enrichment datasette-enrichments-elevation-chart that consumes JSON elevation data and produces text encoded png charts.
Fun References:
KML/KMZ revelation inspired by the POTA from the above map.
UAP siting on the same trip
