Training Log Archive: SpikeIn the 1 days ending May 4, 2016:
| ||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||
| |||||||
| We |
Wednesday May 4, 2016 #
cycling 50:00 [1]
Work commute with a quick errand (stopping at the grocery store for garbanzo beans and mint cookies).
After reading cedarcreek's AP thread on Strava heat maps and QGIS, I discovered that Strave heat map data can be used for OSM editing. I did some OSM editing at Cliff Cave and at the Perry bike trails. Cliff Cave had most of the trails in place, but the heat map data showed some newer (or maybe just unmapped) trails. OSM didn't have any of the Perry bike trails. It has some of them now. I'll add more later.
I like OSM for a couple of reasons. First, I like the idea of open mapping. Second, I have this idea that with a little bit of training on map making, I might be able to get some of the local adventure race organizers to use OSM and lidar to create maps that are better than the crummy USGS maps that they currently use.
1
After reading cedarcreek's AP thread on Strava heat maps and QGIS, I discovered that Strave heat map data can be used for OSM editing. I did some OSM editing at Cliff Cave and at the Perry bike trails. Cliff Cave had most of the trails in place, but the heat map data showed some newer (or maybe just unmapped) trails. OSM didn't have any of the Perry bike trails. It has some of them now. I'll add more later.
I like OSM for a couple of reasons. First, I like the idea of open mapping. Second, I have this idea that with a little bit of training on map making, I might be able to get some of the local adventure race organizers to use OSM and lidar to create maps that are better than the crummy USGS maps that they currently use.
1