[mkgmap-dev] Problem with drive-on

Fri Dec 6 15:14:52 GMT 2019

I agree it seems admin_level value is wrong. I've added a comment on 
changeset aobut it. A warning as you suggest may be useful to detect 
such cases.

El 6/12/19 a las 8:19, Gerd Petermann escribió:
> Hi Carlos,
>
> see https://www.openstreetmap.org/way/303677783 and https://www.openstreetmap.org/way/303677781
> I guess the admin_level of those two ways is wrong. There are more ways in this area with admin_level=2.
>
> To find them I've added
> highway=* {echotags "c"}
> as last line in the lines file to check what values the roads have in mkgmap:admin_level2 and mkgmap:country
>
> Maybe I should add code in the boundary generator to warn when it stores a name for mkgmap:admin_level2 which doesn't
> show up in LocatorConfig.xml?
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen at hotmail.com>
> Gesendet: Donnerstag, 5. Dezember 2019 20:08
> An: Carlos Dávila; mkgmap-dev at lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] Problem with drive-on
>
> Hi Carlos,
>
> seems my file was even older. I can reproduce the problem with the bounds file created 2019-11-29.
> I'll have a closer look tomorrow.
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cardavilam at gmail.com>
> Gesendet: Donnerstag, 5. Dezember 2019 19:58
> An: mkgmap-dev at lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] Problem with drive-on
>
> I have just realized my bounds.zip file is more than one year old (it
> should be automatically updated every week=-O). I'll try with a new one.
>
> El 5/12/19 a las 15:13, Gerd Petermann escribió:
>> Hi Carlos,
>>
>> I just tried to reproduce the problem. I've downloaded the area in your bbox (a bit larger) to file in.osm.pbf
>> and used splitter to cut out your area with
>> java -jar splitter.jar --split-file=areas.list in.osm.pbf
>> Then I used
>> java -jar mkgmap.jar --drive-on=detect --bounds=bounds.zip --route 63240001.osm.pbf
>> I don't see the message.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen at hotmail.com>
>> Gesendet: Mittwoch, 4. Dezember 2019 21:16
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] Problem with drive-on
>>
>> Hi Carlos,
>>
>> My understanding is that your style (or the bounds file) sets at least two different mkgmap:country values for the tile.
>> Maybe you can post a link to that tile?
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cardavilam at gmail.com>
>> Gesendet: Mittwoch, 4. Dezember 2019 12:15
>> An: Development list for mkgmap
>> Betreff: [mkgmap-dev] Problem with drive-on
>>
>> I am preparing an  areas.list file to split Oceania, so that each tile
>> contains only roads driven on the same side. I have found a tile where
>> all roads should be driven on left side, as it all lies within
>> Indonesia, but mkgmap reports "Tile contains both drive-on-left (2695)
>> and drive-on-right roads (57)". I have reduced tile size to narrow down
>> the problem. These are its coordinates: -288768,6178816 to
>> -210944,6219776. It includes two islands, right one is detected by
>> mkgmap as right side driven, but it is left driven (to my knowledge).
>> Any idea why this happens?
>>
>>
>>