[mkgmap-dev] [PATCH v1] grok unpavedness
From Steve Hosgood steve at tallyho.bc.nu on Wed Dec 9 11:48:36 GMT 2009
Mark Burton wrote: > >> The trouble with the "mkgmap:unpaved=???" approach is that it duplicates >> existing functionality in OSM. We should strive to get the existing >> functionality better specified if it doesn't already do the job for us. >> Otherwise, mapping effort will be spent on adding a set of tags to OSM >> which only benefit the Garmin routable maps project. What about the >> TomTom people? Or the AndNav2 users? They'll want to know about >> routeable or unrouteable unpaved roads too. >> > > The whole point of using a mkgmap: prefix is that it does not force a > particular OSM tag to be used for a garmin gps specific purpose. But this isn't Garmin-specific. It's the choice of whether a way should be considered "routeable" or not. That's useful info for all the autoroute programs and GPS navigators. Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20091209/e6a2f627/attachment.html
- Previous message: [mkgmap-dev] [PATCH v1] grok unpavedness
- Next message: [mkgmap-dev] [PATCH v1] grok unpavedness
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list