[mkgmap-dev] [PATCH] improve handling of access restrictions in osm routing
From Mark Burton markb at ordern.com on Fri Feb 13 09:38:23 GMT 2009
Hi Johann, > > The attached patch improves the handling of access restriction tags so that > > you can now restrict on a vehicle class basis i.e. hgv=no > > > With a short glance at your patch I've seen that the keywords are > contained in the sourcecode. Shouldn't it be in defined in the style file? > > As far as I can see, at the moment there is no possibility to define > default restricitions for different tracktypes. > I would propose further keywords in the lines file, e.g. > > highway=cycleway [0x0a road_class=0 road_speed=1 *access=bycycle,foot* > resolution 21] > > or > > highway=cycleway[0x0a road_class=0 road_speed=1 *access_bycycle=yes > access_foot=yes* resolution 21] The most recent version of my code now pays attention to these OSM tags: access, bicycle, foot, hgv, motorcar, motorcycle, psv. Unfortunately, the Garmin codes don't appear to know about motorcycles (they lump motorcycles and cars together) or horses (or taxis, either). So if a way is tagged with one of those, i.e. hgv="no", the gps will know about it. If this is not adequate, we can look into adding extra information in the style file. Cheers, Mark
- Previous message: [mkgmap-dev] [PATCH] improve handling of access restrictions in osm routing
- Next message: [mkgmap-dev] [PATCH] improve handling of access restrictions in osm routing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list