[mkgmap-dev] Multiple Relations and Admin levels

Sat Aug 7 14:04:12 BST 2010

Hi Markus,

I think this problem arises due to a mixture of an mkgmap bug in the 
multipolygon processing and the broad mixture of how multipolygons are 
tagged. Some mps are tagged only in the mps, some do have the same tags 
in the mp and on their ways, some have tags in the mp and only some ways 
tagged and some mps only have relevant tags on their ways. This makes it 
quite complicated to handle all cases correctly.

I will need some time to fix one bug I have found in the mp processing. 
Can you post me some of your problematic mp ids? This makes it easier 
for me to test my bug fix.
One note: --generate-sea-:no-mp should be --generate-sea:no-mp

Have fun!
WanMil

> Hi WanMil,
>
> Without the --process-boundary-relations I don't get a number of national
> parks that I imported to OSM for South Australia. These needed to be
> relations due to there size and a number of them had multiple looped ways.
>
> The problem also seems to be there from the maps supplied from
> http://garmin.na1400.info/routable.php
>
> They also now use the --process-boundary-relations as I pointed out that
> this option was new and now appears it is needed for relations.
>
> I mentioned this after other users were missing boundaries that were there
> before the option was added.
>
> Regards,
>
> Markus_g
>
>
> -----Original Message-----
> From: mkgmap-dev-bounces at lists.mkgmap.org.uk
> [mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk] On Behalf Of WanMil
> Sent: Friday, 6 August 2010 4:35 AM
> To: Development list for mkgmap
> Subject: Re: [mkgmap-dev] Multiple Relations and Admin levels
>
> Hi Markus,
>
> I have no time now to check that in deep (will do that later).
>
> Do you really need the --process-boundary-relations option? Without this
> option multipolygon boundary relations are not processed. I think you
> only need that in case you have some polygon rules for boundaries in
> your style file but there aren't some in the default style.
> I guess removing that option could fix your problem.
>
> Have fun!
> WanMil
>
>> Hi WanMil,
>>
>> Here are the options I normally use. The style is the default.
>>
>>
>> Java -Xms2000m -ea -jar mkgmap.jar --nsis --net --route
>> --process-boundary-relations --tdbfile --index --preserve-element-order
>> --reduce-point-density=0 --max-jobs=8 --drive-on-left --check-roundabouts
>> --generate-sea-:no-mp --remove-short-arcs --adjust-turn-headings
>> --extend-sea-sectors --no-sea-sectors --close-gaps=1000 --make-poi-index
>> --add-pois-to-areas -c template.args
>>
>>
>> And here are the splitter options I use.
>>
>> Java -Xmx3000m -jar splitter.jar --mixed --no-trim --overlap=5000
>> australia.osm
>>
>> Regards,
>>
>> Markus_g
>>
>> -----Original Message-----
>> From: mkgmap-dev-bounces at lists.mkgmap.org.uk
>> [mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk] On Behalf Of WanMil
>> Sent: Thursday, 5 August 2010 4:08 AM
>> To: Development list for mkgmap
>> Subject: Re: [mkgmap-dev] Multiple Relations and Admin levels
>>
>>> Hello,
>>>
>>> I have noticed a problem with mkgmap if a way is included in multiple
>>> relations and Admin levels are used in the relations.
>>>
>>> What seems to happen is that mkgmap chooses the relation with the lowest
>>> Admin Level and only will display the way in mapsource when the matching
>>> zoom level is reached.
>>>
>>> This causes problems such as an example if the way is part of a state
>>> border, it will only show up if zoomed right in even though the state
>>> border relation has a higher Admin level.
>>>
>>> Also it appears to effect coastlines if a coastline is included in a
>>> relation with a low admin level.
>>>
>>> Regards,
>>>
>>> Markus_g
>>>
>>
>> Markus,
>>
>> could you please post your mkgmap-options?
>> Do you use the default style?
>>
>> Have fun!
>> WanMil
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>