[mkgmap-dev] [PATCH v4] - beware of the bollards!
From Felix Hartmann extremecarver at googlemail.com on Mon Jul 20 22:03:37 BST 2009
2009/7/20 Mark Burton <markb at ordern.com> > > Hi Felix, > > > Well but one allways has to remap these values to motorcar=yes for > special > > purpose maps, as only car/motorcycle provides proper routing. > > Never understood that need to route as a car, but I am happy to cater > for such a foible. > bicycle does rely only on routeclass, not on speedclass. So you can only have 0-4 as differentiation in bicycle mode, no different speed (o.k. you have 0 and 1 (2-7 get degraded to 1), basically bicycle mode equals motorcar shorter distance, so you miss the faster / shorter time routing option (though choosable) when going for bicycle modus. With only 5 different classes of roads it is more or less impossible to prefer i.e. a mtbroute over a cycleroute over a ......., you get too many roads/ways classified equally and too few possibilites to heavily downgrade something. One could of course use taxi, emergency, .... also as they route as good as car/motorcycle - but bicycle and pedestrian do not produce any reasonable routes (basically only good for shortest route while avoiding some road types, but not enough to prefer specific road types). The problem is that while every garmin unit (except edge) supports car/motorcycle not all support emergency or taxi. I don't think maps where you expect cyclists to choose emergency mode because car/motorcycle is really kept for cars but they can only choose car/motorcycle will work well for them. That's why I prefer to use car/motorcycle, it is the best to provide consistent results. > > > I have not > > really read through the patch as it does not interest me, but you have to > > make sure that it runs before the style-file for the access values, > > otherwise routing with a bicycle on car/motorcycle mode will not work > > anymore. > > Well, it runs after the style file stuff so to avoid making you > unhappy, I shall make it disabled by default and the switch will enable > it. if it is enabled by default, but you can disable it, it would be fine with me too. I just think we should have a possibility for speciality maps not to need to calculate things that are not needed. > > > > I'm a bit skeptical if this will really not pose any problems for > speciality > > maps. With a switch it would be cleaner (and not cost any additional > > calculation time for other maps). > > Your scepticism is well placed. > > Cheers, > > Mark > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090720/8ca87296/attachment.html
- Previous message: [mkgmap-dev] [PATCH v4] - beware of the bollards!
- Next message: R: [mkgmap-dev] [PATCH v3] - beware of the bollards!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list