[mkgmap-dev] [PATCH v1] grok unpavedness
From Felix Hartmann extremecarver at googlemail.com on Mon Dec 7 23:24:33 GMT 2009
On 08.12.2009 00:17, Chris-Hein Lunkhusen wrote: > Mark Burton schrieb: > > >> The attached patch allows you to add either unpaved=yes/true/1 or >> paved=no/false/0 to a way and then it will be ignored for routing >> purposes when the GPS has been told to avoid unpaved roads. >> >> Not sure if those are the best tags to use - any thoughts? >> > I think the most used tag is surface=unpaved, but as usual > we can do this in the style file. > > highway=*& (surface=unpaved | surface=dirt | surface=sand | > surface=ground | surface=gravel) {add unpaved=yes} > > Chris > > Well I prefer if it it is kept like right now, and surface=* is not automatically considered as unpaved avoidance and the tag itself is not present in OSM database. This leaves more choice in the style-file to abuse the unpaved tag (and allows the choice if for example tracktype=grade2 is considered to be avoided or not via "avoid unpaved roads". The default style-file of course should have something like below: highway=*& (surface=unpaved | surface=dirt | surface=sand | surface=ground | surface=gravel | tracktype=grade2 | tracktype=grade3 | tracktype=grade4 | tracktype=grade5 | sac_scale=* | smothness= ........) {add unpaved=yes} > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >
- 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