If the meanderings of my work hasn't confused you enough yet, then here is something different. In a recent project I assembled and released the very first free open source topographic maps of the entire 2000+ mile Appalachian Trail (AT). Every Winter tens of thousands of folks (maybe even hundreds of thousands) are preparing/desiring some sort of AT thru-hike or section hike. (I myself am addicted to 100-200 mile section hike trips) In my mind the Appalachian Trial is one of the best things this f***ed up country has. And the more time we as a society spend on computers and networks, the more relevant and important backcountry experiences become. But I'll step off the soapbox because most of you probably wouldn't want to spend weeks or months all dirty and sweaty, constantly hungry and achy in a beautiful "green tunnel" with the bugs and snakes.

Sorry but de-romanticized statements like that are for your own safety. And so are my free Android maps. Two years ago I posted instructions here at the WhiteBlaze.net forums on how to make your own free smartphone backpacking maps. The post has received nearly 10,000 hits, but unfortunately those instructions no longer work. All the topographic map sources which were once freely available to Mobile Atlas Creator (MOBAC) have been yanked. Mapping services have matured to a point where the free ride is over as data pushers pay attention to the dollar signs. Luckily I found an alternative map tile source... OpenStreetMap (OSM) to the rescue! An amazing organization. However they too have bills to pay and don't allow map tile downloads via map making software such as MOBAC due to server/bandwidth costs. (Keep in mind that maps *must* be fully downloaded in advance of your backcountry trip and used offline due to network and battery constraints) Luckily I found an alternative OSM tile hosting source... Stamen Design to the rescue! This heavy-duty, San Francisco based visualization agency hosts OSM tiles, and they generously gave me permission to use their server to assemble and release these Appalachian Trail maps. 

Traditionally an AT thru-hiker would spend $100-$200 on paper maps. So many maps are too heavy to carry all at once, and must be strategically snail-mailed to various post offices along the trail. Many of those paper maps, in my opinion, look so "1990's desktop PC". (not that there's anything wrong with that aesthetic!) Nowadays you can also purchase an iPhone or Android app that has topo offline maps of the trail. Costs for those are typically $30-$60, which compared to paper seems fair, but then again is it? Not in my mind, and I didn't spend a bunch of money testing them because I found OruxMaps. This Android app is free (donations welcomed) and is of great quality. I have field-tested OruxMaps for hundreds of mountain trail miles without a single crash or issue. So I chose the OruxMaps format when I compiled the maps.

Something I learned this time around is that OruxMaps is a "dead end" data format - one cannot convert maps from OruxMaps to a different format, yet one *can* easily convert from a more standardized format to OruxMaps plus many others. Perhaps next year I will try to make better maps, in a more open data format so folks can choose their own platform/app. Though I am a software professional with thousands of trail miles under my feet, I am just a map-making amateur. I am learning as I go along, step by step, just like when I am hiking. (oooh that was cheesy) I hope more folks start creating and sharing open source offline maps, as I see them as an integral part of taking breaks and finding adventure off the grid. Sounds weird but yes I am advocating the use of the Internet to help us get away from the Internet!

Spun up another Thread called Ragged Lists. I have been wanting to assemble these works together for a while now, most were made in 2007-2008 when I was monkeying around with the aesthetics of ragged typographic layouts. This is something I feel we often take for granted. Every day we see, use, or make such lists, which in the western world are typically flush left aka left aligned aka ragged right. Because the elements of the list are of varying length, a rhythm occurs along the ragged edge that is based on the underlying data of the list. The rhythms could be very random, have gradual fluctuations, jumpy, etc. Most of these particular ragged lists are made of weird datas that I like... found text, spam, random dictionary data, or hastily written poems. The longer lists are software generated HTML and CSS, while the shorter ones are handmade. Some of the longer lists become "interactive" when you scroll up or down, an action which tends to accentuate the rhythm of the ragged edge.

If it is the artist's job to find beauty in simple things then here you go. What could be more simple and beautiful than information, existing in a list, with its very own rhythm. It is also the artist's job to communicate this perceived beauty to others, and these ragged lists may or may not be all that successful there, since that wasn't necessarily the goal when making them. They were created while I was going in many directions at once, which is often the case with me, and also the reason I named these collections Threads, not Bricks.  

A few months ago I was very happy to learn that a website which I worked on and launched as lead engineer won a 2012 Webby Award for Best Community Website! Cancer is something of a dirty word, and the website takes that bull by the horns, providing a new experience for those who may feel victimized and helpless. While not the only honor/award given to the I Had Cancer project, I see this as "kind of a big deal" for everyone involved, especially considering the competing sites in this category included Tumblr and Flickr. Please note this was not my project, I was a hired Lead Drupal Consultant and my involvement is documented at the project page. Software developers rarely get credit for what they do, thanks to a completely unorganized and unregulated software industry, so for now we have to give ourselves the pat on the back. And I recommend more software developers do just that... ain't no shame!