[mkgmap-dev] what makes a way a road?
Hi all, I am looking at the problem described by Enrico: http://gis.19327.n5.nabble.com/Different-rendering-tp5803738.html One of the reasons for the problem is that mkgmap treats "roads" different to other lines. Another problem is that it is not clearly documented how you can change a way to a road. If I got that right, Garmin will not route over lines with non-routable types. A routable type is between 0x01 and 0x13 or one of: 0x1a, 0x1b, 0x16, so all other are non-routable. The problem: We calculate the road network for all ways with a road_class/road_speed atttribute and a type that is not extended ( < 0x1), no matter if the type is routable. Is this intended? Gerd ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] what makes a way a road?
Am 23.04.2014 08:03, schrieb Gerd Petermann: Is this intended? I don't think so. Henning ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] what makes a way a road?
Henning Scholland wrote > Am 23.04.2014 08:03, schrieb Gerd Petermann: >> Is this intended? > I don't think so. Okay, then I've added a correct test to the check-styles option. I think I'll change the code to accept only the routable types as roads and print one warning (for each tile) when style uses a wrong type for roads. I've also found a better solution for the problem with the distorted lines, but I want to test that a bit longer. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/what-makes-a-way-a-road-tp5803906p5803987.html Sent from the Mkgmap Development mailing list archive at Nabble.com. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
