detailed step by step workflow for adding a track. track geometry revisited.
goal is to streamline/automate as much of this as possible.
git checkout -b add-track-xyz
hugo new track/us/ca/xyz.md
titlefield in front matter if formatted strangely.
tagsas applicable to the venue.
elevation_meters(rounded to two decimal places)
git add content/track/us/ca/xyz.md
git commit -m "add new track xyz (ca)"
git push -u origin add-track-xyz
how to get yaml out of my google sheet quickly?
example csv->yaml converter: https://www.browserling.com/tools/csv-to-yaml
i could create a derived google sheet tab which crafted the column headers to match my yaml format. get rid of other columns and i could drop it in. of course i could do this via a command line tool as well. non-sensitive information so web based is a fast way to try it out.
this smells a little funny. my data starts as csv via google form. then i do a bunch of work to make it yaml. so i ultimately can download it as csv again.
turn diameter at the common finish: 68.84. a third point to the apex of the turn: 117.87-68.84 = 49.03
we get a right triangle.
c = 49.03.
a = 68.84⁄2 = 34.42.
b = ?
a^2 + b^2 = c^2
34.42^2 + b^2 = 49.03^2
1184.7364 + b^2 = 2403.9409
b^2 = 2403.9409 - 1184.7364
b = square root of 1219.2045
b = 34.9171
if a is roughly equal to b, then can we say it is a single radius track? i think so.
assumption: measurer can quickly eyeball an isosceles triangle. you can probably get close.
I’ll measure/derive A and B for each track. and various thresholds i think we determine which general geometry the track is: single radius vs. double bend. then within double bend, we can show which configuration it likely is.