[mkgmap-dev] Multiple Relations and Admin levels

Wed Aug 11 13:03:52 BST 2010

Thankyou WanMil,

I have tried the patch and it seems to fix a number of problems. It's great
that I now can see complete rivers that have been very patchy in the past
due to ways being used in multiple, multipolygons. 
Also some of the borders have improved.

I have though found some problems still with some junctions. An example is
below. 

The New South Wales/Queensland border doesn't continue past this spot in
mapsource.

Way id=32264526 Admin level 4
Way id=32284994 Admin level 4
Way id=32264521 admin level 10

Common Node id=362596528 lat=-29.0000128; lon=148.9583324;  
way referrer:
    32284994
    32264526
    32264521

Thanks also for the replies on performing patches from others. Not sure if I
will try compiling my own mkgmap yet though.

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: Tuesday, 10 August 2010 6:23 AM
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] Multiple Relations and Admin levels

Hi Markus,

I have posted a patch that seems to fix some of your problems.

Could you please test the patch and send me some feedback?

Thanks!
WanMil

> Hi WanMil,
>
> Here are two main examples of what is happing in various locations when
> viewed in mapsource. Also happens with coastline if it shares a way.
>
>
> Here are 2 ways from the state border New South Wales/Victoria with an
Admin
> level of 4.
> The problem is when the first way reaches an intersecting way of a
different
> Admin level of 10.
>
> The state border stops at Node id=360491546 and doesn't continue past the
> intersecting way.
>
> Way id=32120546 Admin level 4
> Way id=32257156 Admin level 4
>
> Way id=32120728 Admin level 10
>
>
> The border relations are 80372 and 80371
>
>
>
> Here is another example of the problem with another state border of
> Queensland/New South Wales. With these, the problem is also there even
> though the admin levels are in the ways and relations.
>
> Way id=31954430 Admin level 4
> Way id=31954265 Admin level 4
> Way id=32300702 Admin level 4
>
> Way id=32296848 Admin level 10
> Way id=31954436 Admin level 10
>
>
> Common node for 5 ways are Node id=357892114 and Node id=357892119
>
>
> One thing also to point out is the missing ways of the borders are viewed
> when zoomed right in but the name of the border is missing as a feature
and
> only the lower admin levels names are there as features.
>
> 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: Saturday, 7 August 2010 10:34 PM
> To: Development list for mkgmap
> Subject: Re: [mkgmap-dev] Multiple Relations and Admin levels
>
> 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
>>
>
> _______________________________________________
> 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