An example of using Social Hiking whilst on a hike

Setting up Social Hiking can, for some people, be a frustrating experience – there are quite a few steps to allow Social Hiking to be able to talk to the plethora of media and location services supported before you get going (some easier than others!) – but what happens once everything is all set up and you have successfully shared your first map?

As a lot of my focus is on helping guide new users through the set up process, ‘graduates’ of that process are left to discover, thankfully with the help of the wonderful Social Hiking community (who are amazing at welcoming new users and sharing their knowledge), some of the more advanced ‘power’ features and to work out how best to share their adventures.

What I thought might be useful to these ‘graduates’ is an insight into how other people use Social Hiking, not just the final map, but the process of creating the map. So, on a recent hike with Rich (@FlintyRich), I recorded a series of mini-podcasts (they are only a few minutes each) describing how I use Social Hiking during, and after, a hike. This is not THE way, just MY way – the site can be used in many different ways depending on your personal preference. It would be brilliant if other users would be willing to share with the community how they use Social Hiking for their outdoor adventures (it does not have to be in audio form!)

The podcasts cover a range of topics: starting a walk and switching on location source (and what Social Hiking does when you start sharing location), setting a map title using Twitter, adding media to your map, automatic peak bagging, adding context to your tweets, changing a map icon and uploading gpx files and photos when you get home.

You can listen to the podcast using the player below, or you can listen to them direct on Audioboo website. The map referred to during the podcasts is also below.

Share with Others:
  • Digg
  • StumbleUpon
  • Facebook
  • Twitter
  • FriendFeed
  • Google Buzz
  • Posterous

Got something to say? Go for it!