i have recently acquired a gps unit. a garmin device. and i have been look at ways to use osm to add detail to the gps maps the unit uses.
i can find the cycling route to the place i need to get to in google maps but have not been able to find the culvert they have routed the bike route under the highway through in OSM.
i want to put it on my gps.
so my task as i understand it is to edit the osm for the area and add the relevant info to either a private map that my gps will be able to see, or an osm that anyone can see. of course not everyone will need to go to the place i have to go to. but. you know. if it is indeed the most intelligent route, then it’s worth sharing the information. if it’s not passable because it’s under 2 meters of snow, we could perhaps document that too.
and then transfer the file into the gps unit. bob’s your uncle, as they say.
Discussion
Comment from Vincent de Phily on 18 February 2014 at 09:49
Welcome to OSM :)
Editing the map so that everybody can benefit is the whole idea of OSM. Working on private map data is only usefull/necessary in niche corner cases you’re probably not interested in.
You can wait until your OSM changes trickle down to your Garmin the usual way, or you can download more frequently-updates maps or even make your own.
Concerning your changes, you probably want to add layer=-1 to your tunnel. I also see that some of your ways seem to end nowhere. Make sure to connect them to the rest of the network if applicable.
It’s arguably not worth maping the “inacessible because of snow” bit, unless it is quite regular and predictible. In that case, you could use time-based conditional access but I’m not aware of a routing engine that actually uses that info.