
Hi all, attached is v4 of the patch. The drive-on parameter now accepts the following values: left|right|detect|detect,left|detect,right - detect is equal to detect,right - with detect all roads are counted to find out whether the map is a drive-on-left or drive-on-right map - if the detection doesn't return a clear result, the 2nd option is used - the polish reader only checks the "LeftSideTraffic" string, it doesn't count anything (for now) @Steve, WanMil: I've added methods getDriveOnLeft() to MapperBasedMapDataSource and use it in MapBuilder before a TREFile or NODFile is written to configure the corresponding flags. Classes that are able to detect the dr I think this is a bit cleaner compared to v3 and to trunk.

@Steve, WanMil: I've added methods getDriveOnLeft() to MapperBasedMapDataSource and use it in MapBuilder before a TREFile or NODFile is written to configure the corresponding flags. Classes that are able to detect the dr I think this is a bit cleaner compared to v3 and to trunk.
Hi Gerd, I couldn't test the patch. The trunk implementation is a hack to pipe the drive-on-left flag to the NodHeader using a ThreadLocal. This was just a bugfix to fix random drive-on-left flags when mkgmap uses more than one thread and the tiles have different drive-on-left-flags. Your implementation seems to be much cleaner. Good :-) WanMil
participants (2)
-
Gerd Petermann
-
WanMil