[mkgmap-dev] PATCH v1: highwayCount

Fri Feb 8 17:26:11 GMT 2013

Hi,

I did not yet find the reason for the routing problem, but I can reproduce
it with the patched version with a few steps now:
1) download austria.osm.pbf from geofabrik
2) split with
java -Xmx2000m -jar splitter.jar --output-dir=e:\austria --max-nodes=1200000
austria.osm.pbf
3) execute mkgmap
routing works:
java -Xmx7000m -jar d:\mkgmap\dist\mkgmap.jar --route --nsis --max-jobs
--preserve-element-order e:\austria\6324*
routing is broken over long distances:
java -Xmx7000m -jar d:\mkgmap\dist\mkgmap.jar --transparent --route --nsis
--max-jobs --preserve-element-order e:\austria\6324*

So, routing somehow depends on the background shape that is either written
or not depending on the --transparent option.

@Steve:  Can the display tool help me to find out what's going wrong?

Gerd

Felix Hartmann-2 wrote
> yes I'm still using that one. I think I can drop the --x , which I used 
> because sometimes it was broken on the commandline check, but working 
> below the hood. Never noticed any routing problems due to it.
> I probably don't have any time over the next 3 days though...
> 
> Area to small to split, is not my aim. My aim is to make the map faster 
> to draw on GPS. 6 is the highest value that leads to very small visible 
> changes, therefore I use it over the default.
> On 08.02.2013 10:48, GerdP wrote:
>> oops, seems I was trapped by some caching in BaseCamp.
>>
>> --x-reduce-point-density-polygon=6 doesn't break routing.
>>
>> Gerd
>>
>>
>> GerdP wrote
>>> Hi Felix,
>>> Felix Hartmann-2 wrote
>>>> Routing over long distances is not working at all anymore (much much
>>>> worse to before).
>>>> Don't have time (need to sleep) to find out if any roads become
>>>> unroutable though...
>>> please check: Are you still using this option?
>>> --x-reduce-point-density-polygon=6
>>>
>>> 1) It seems to be the reason for the broken routing (also in the trunk
>>> version)
>>> 2) althrough not documented, it is interpreted as
>>> --reduce-point-density-polygon=6
>>> The help file for this option says that the recommended value is 8, but
>>> if
>>> the value is
>>> not specified, it uses the value from reduce-point-density.
>>> If both are not specified, the default for both is 2.6
>>>
>>> I assume that you use the higher values because you see the
>>> severe "Area to small to split at ..." messages. Please ignore them
>>> as long as you don't see empty img files or try the
>>> MapArea_v1.patch
>>> http://gis.19327.n5.nabble.com/Why-do-we-have-the-Area-too-small-to-split-at-message-tp5744612p5744766.html
>>>
>>> @Steve:
>>> I have no good idea why this option breaks routing over long distances.
>>> It just changes the way how DouglasPeucker works for shapes.
>>> The higher the value, the more points of shapes are removed.
>>> Maybe fewer shapes are written, maybe more sub divisions are empty.
>>> Any hints?
>>>
>>> Gerd
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://gis.19327.n5.nabble.com/PATCH-v1-highwayCount-tp5748554p5748593.html
>> Sent from the Mkgmap Development mailing list archive at Nabble.com.
>> _______________________________________________
>> mkgmap-dev mailing list
>> 

> mkgmap-dev at .org

>> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> -- 
> keep on biking and discovering new trails
> 
> Felix
> openmtbmap.org & www.velomap.org
> 
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

--
View this message in context: http://gis.19327.n5.nabble.com/PATCH-v1-highwayCount-tp5748554p5748624.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.