{"id":4308,"date":"2012-06-05T11:41:12","date_gmt":"2012-06-05T15:41:12","guid":{"rendered":"https:\/\/nuxx.net\/blog\/?p=4308"},"modified":"2020-12-27T10:08:10","modified_gmt":"2020-12-27T15:08:10","slug":"mtb-trail-mapping-workflow-with-openstreetmaps","status":"publish","type":"post","link":"https:\/\/nuxx.net\/blog\/2012\/06\/05\/mtb-trail-mapping-workflow-with-openstreetmaps\/","title":{"rendered":"MTB Trail Mapping Workflow with OpenStreetMaps"},"content":{"rendered":"

With recent map drawing activities (1<\/a>, 2<\/a>, 3<\/a>) I’ve been asked about the process I use for creating maps. What follows here is the workflow I used with OpenStreetMap<\/a> (OSM) for the CRAMBA Stony Creek MTB Trail Maps<\/a>, and hopefully others will find it useful.<\/p>\n

I expect I’ll be following this same workflow for the next maps created, and even possibly revising previous ones using this process because it provides more solid base data than my previous method which consisted of little more than manually tracing SVGs of GPS tracks in Illustrator. It also helps get more map data in OSM, which is basically the cartographic version of Wikipedia<\/a>.<\/p>\n

One note, using OSM data in your maps requires that the resulting map be licensed under the Creative Commons Attribution-ShareAlike 2.0 Generic (CC BY-SA 2.0)<\/a> license. This basically means that anyone else can redistribute and reuse the map (or portions thereof), as long as they provide appropriate attribution and license their version in a similar way. As I’m intending these maps to be freely used by the general public (as part of my work with CRAMBA<\/a>) I’m happy to do so, but others should be aware of these restrictions before getting too far along in the process.<\/p>\n

Here’s the workflow:<\/p>\n

<\/p>\n

\n

 <\/p>\n

    \n
  1. If all trail data needed for a map is already in OpenStreetMap<\/a> (OSM), skip to step 5.<\/li>\n