Making GIS music from yesterday’s run

Runner in full stride on the beach
Runner in full stride on the beach

I was looking for GIS music for my podcast intro. Long story short, I didn’t find any, but I did figure out how to make it!

GIS Music: That Hill

This is a hill that I like to attain Strava local legend status on. I ran it yesterday, so it was fresh in my feed when I started this project. The pitch is the longitude, the note duration is the latitude. In this short piece, you can hear that it is an out and back, and that it starts with a corner.

How I made this GIS Music

I used Strava GPX data, but you could really use any other tabular latitude and longitude data for this. For extra fun, I also made a second track using the elevation column…. but the music wasn’t as nice.

Step 1: Get your coordinates (and trim them, if they’re really long)

  1. My path was long, so I wanted to shorten it a bit. I downloaded the GPX file from Strava. I edited to a shorter path for appropriate test scale using GPX Studio.
  2. If you don’t want to edit your route, you can skip to this step: Convert from GPX to CSV. I converted it to CSV using Mygeodata Converter. The track points are the ones you need for the output.

Step 2: Clean up the coordinate data

  1. Open your CSV in Excel (or your favorite spreadsheet software).
  2. Open the track points file. If yours are like mine, you’ll have longitude & latitude in columns A and B. We’ll just use these for now 🙂
  3. In two other columns in your spreadsheet (I used J and K), you’ll make a formula that will create the list of values that the music algorithm site wants.
  4. In the top cell of your columns (J and K in my example), use a formula to set equal to the top values in your latitude adn longitude columns. In my case, J2 is set “=A2”. In the NEXT CELL down, use a formula that points to that first cell, then adds the next cell in your original list. In this case, J3 is set “=J1&”,”&A3″. & concatenates the values and the “,” puts a comma between them. Then cascade this formula to all remaining cells. Repeat for the other column (my column K).
  5. You’ll know this worked if you see a cascade of numbers increasing in size by one in descent from the top.
  6. For the next step, you want only the contents of the last cell in your formula column (the longest list.

Step 3: Make music!

  1. Follow the steps under “How To” on the Music Algorithms website.

Note: I used my longitude string for pitch and the latitude string for duration. Even though it took a couple of tries to figure out how input worked, the result was this short sequence of notes!

Sites I used

Note on privacy

The Musical Algorithms app applies an algorithm (it’s in the name!) to assign notes to your data points. It’s possible to tell that I’m running southeast then northwest… but the actual locations are obscured in the music above.

Ableist language is both violent and lazy: Let’s do better with clearer word choices

You might have heard me mutter “wait, that was ableist language” and find a more specific term for whatever I just said. I am not the first person to argue that ableist langauge is violent. Or that it is lazy. I’m definitely not an authority on it. It frustrates me to realize how much the world, language, and idiom has been built around the elevation of abled bodies and the cutting-down of all other bodies.

More for myself than any other reason, I’m assembling a compilation of lists and ideas found on the websites below. I encourage you to turn to them for more thoughtful treatments of this topic.

Citation Style Revisions: I promise it’s not that hard

I am going through the transition from Endnote to Zotero. I have loved Endnote since I was 18 (what a little history major nerd I was then). It's generally great, but has been a little frustrating lately. It was time for change - even my librarian chuckled at how old-school I was with Endnote. Moving to Zotero has been an adventure. Fewer out-of-the-box citation styles exist. Publishers only seem to provide Endnote styles. It was time to learn to create my own citation style.

Thanks to a supportive friend, who tolerated an hour of my pouting about citation styles, I learned how to find, revise, and save a citation style. Here are my provisional steps - they're not perfect, but I wish I had found them somewhere 3 weeks ago!

All of this uses citationstyles.org (featuring the very obvious Author Guide, which I missed). They have a .csl extension that works in Zotero. If you can use search by name and find your style, AWESOME. The steps below assume that you can't.

Getting to the right citation style

  1. Go to Citation Styles search by example. Using your journal's style examples, revise the in-text citation and bibliographic entry to match theirs. If the default example it gives you isn't helpful (I think it defaults to chapter), then use the previous and next cited item buttons to find one that is helpful. For me this is usually journal article. But to each their own!
  2. Click on search and review the matches. Choose the one that seems to be the fewest revisions away from your target style. I'd pick one that notes pages incorrectly ("pages" instead of "pp") but is otherwise correct over one that has periods where I need commas. Each piece of the citation that is wrong requires its own correction.
  3. Use the Visual Editor (in the tabs at the top of the page) to browse this citation style on a number of citations and bibliography entries. You can add more, to reflect the document types you're actually using. The "example citations" drop-down it the top right took me FOREVER to find, so, you're welcome.
  4. You can click on the part of the citation that is wrong to find the parts of the style that impact it. Trial and error to figure out how to change the errant period to a comma, non-italicized text into italics, etc. There is help in the CSL specification document (make sure you're in the relevant version!). Search for the type of thing (eg. "et al" or "page range") and it will tell you what to look for in the code. If it sends you to the code, use crtl+F (or command+F) to find the string on the code editor page (also in the tabs at the top of the page). Changes you make in the visual editor persist into the code editor and vice versa.

Save and Validate your Citation Style

  1. Save your Style: Once you've wrestled with the style a bit, it's time to save and validate it. From the visual editor tab (by now you have noticed the tabs!), go to Style > Save Style to save the style to your desktop. I find it's helpful to save the styles with a version number to keep track of the changes (there will be changes).
  2. Validate your style: Upload the csl you downloaded to the validator. It will tell you if this style will work in a citation manager or throw errors. If it validates, great! Add it to the citation manager and apply to your document. If it doesn't, go back into the editor and make revisions. Note: If you skip this step, you'll get sad little errors later and nobody wants that.

Iterative Style Corrections

  1. Apply and check your style: Apply the style to your document and compare your citations to the journal style guide. Format still not right? Go back to the editor, make changes, save as, validate, and try again.
  2. Content not right? To get just the list of documents cited in your current paper, this handy tool to select in to highlight  and drag into a new folder (only works with zotero). Then you can make sure that most-cited-author's name is actually spelled the same in each of their references (this was my biggest problem).