Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Maybe a question: does it make sense to do "settings only" backups?
....When I was fixing the problem you wrote here, I had an idea to improve times by comparing expected time (returned from BRouter) with real-time user spend on the segment and modify then expected total time by this ... so task on some calm evening.
# BEGIN - Internal parareters for hills = 6 - experimental avoiding of too steep hills via strongly penalizing uphillcostfactor
# slope below this uphill limit ( % ) has no penalization
assign TooSteepUphill 6.0
# hilly penalization is done by uphillcostfactor and downhillcost, not by uphillcost.
# can be used optionally, but is rather overrun by the uphillcostfactor.
assign TooSteepUphillCost 0.0
# Implemented as BRouter variable uphillcostfactor for uphill scope > TooSteepUphill + TooSteepbufferreduce
# with the transient zone TooSteepUphill .. TooSteepUphill + TooSteepbufferreduce
# There is normal costfactor for uphill scope <= TooSteepUphill
# and costfactor = TooSteepCostFactor for uphill scope >= TooSteepUphill + TooSteepbufferreduce
assign TooSteepCostFactor 200
# The width of the uphill scope transient zone
assign TooSteepbufferreduce 2.0
# Altitude buffer to catch steep SRTM artefacts
# It has to be high enough, otherwise it may suggest an over the hill route
# instead of a flat route along the river, with very steep SRTM artefacts,
# like the route From Obrany to Bilovice at NE border of Brno, Czech Republic
# if TooSteepPenaltybuffer = only 10.0 ( BRouter default is 5.0 )
# http://brouter.de/brouter-web/#map=14/49.2412/16.6745/standard&lonlats=16.649287,49.227407;16.674995,49.245971
assign TooSteepPenaltybuffer 12.0
# Altitude buffer for downhills, does not affect uphill penalization with zero uphillcost.
assign TooSteepMaxbuffer 20.0
# END - Internal parareters for hills = 6 - experimental avoiding of too steep hills via strongly penalizing uphillcostfactor
Tu část kódu co je v citaci rámečku mohu vložit nad část # bstart /global?
Díky moc, já na plánování v naprosté většině případů používám vlastní profil - přikládám. Je to už sice starší kousek, ale plánuje velmi vyváženě pro dálkové cykloturistické trasy. Pokud to neznamená velkou zajížďku tak se vyhýbá nezpevněným cestám i kopcům.Preferuje cyklostezky, ale už trochu méně cyklotrasy.
Myslíš, že by šel ten parametr na omezení stoupání vložit do něj?
Zkusil jsem ten Tebou přiložený profil na rovinnáté trase Veselí n. M. - Kroměříž a chová se divně. Všimni si jak na snímku ...16 zbytečně ignoruje cyklostezku podél vody a na snímku ...49 zase vede trasu po rozbité cestě lesem i když podél železnice vede naprosto po rovině pohodlná cyklostezka.
assign UnpavedCostfactor 50.0
assign PavingUnsureCostfactor 8.0
assign TooSteepUphill 7.0
assign SteepHillsCostFactor 200 # Implemented as BRouter variable uphillcostfactor for uphill > TooSteepUphill
assign validForBikes 1
# the elevation parameters
assign downhillcost switch consider_elevation 80 0
assign downhillcutoff 0.5
assign uphillcost 0
assign uphillcutoff TooSteepUphill
assign elevationpenaltybuffer = 2.0
assign elevationmaxbuffer = 10.0
assign elevationbufferreduce = 3.0
