Hi

 

Based on the versions supplied I could bring it down to 4373 still being OK and 4384 reveals the problem

 

 

 

Build date	Mkgmap		Device	Style	Pink line	Crash/Deadloop	Result	Comment
24-8-2017	r3995	Joris Bo	Oregon 650	Default 2020	Yes	No	Ok
	r4195	Felix Hartmann		Felix Personal		?	Wrong	Felix thinks he uses this version and his own style but is not sure
16-4-2019	r4286	Joris Bo	Oregon 650	Default 2020	Yes	No	Ok
26-10-2019	r4323	Joris Bo	Oregon 650	Default 2020	Yes	No	Ok
17-11-2019	r4373	Joris Bo	Oregon 650	Default 2020	Yes	No	Ok
	< to be investigated>
6-12-2019	r4384	Joris Bo	Oregon 650	Default 2020	No	Yes	Wrong
8-12-2019	r4386	Joris Bo	Oregon 650	Default 2020	No	Yes	Wrong
25-1-2020	r4431	Joris Bo	Oregon 650	Default 2020	No	?	Wrong
	r4479	Jan Meisters	Oregon 450	Jan Personal	No	No	Half
19-6-2020	r4551	Joris Bo	Oregon 650	Default 2020	No	Yes	Wrong
19-6-2020	r4551	Joris Bo	Oregon 650	Joris Personal	No	No	Half

 

 

Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens jan meisters
Verzonden: zaterdag 27 juni 2020 14:55
Aan: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk>
Onderwerp: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

 

@ Joris: mkgmap-r4373

 

@ Felix: retested my map based on your .osm.pbf with same result: No crashes, no recalculations.

But still no pink routing on (northbound) Castillo de Alarcon.

(Sorry, mixed up streetnames: in both tests northbound had no pink, westbound had)

 

Am 27.06.2020 um 12:54 schrieb Joris Bo <jorisbo@hotmail.com>:

 

Hi

 

Is there a online repository of compiled mkgmap versions?

I found an answer form Gerd that ‘you can create one form svn, but I don’t have those skills.

 

I am looking for versions between

r4323 (29-10-2019)                  still ok

r4386 (8-12-2019)                    problem persist

 

@Felix Yes, I always used the most recent default style also with the older mkgmap versions for the tes.

 

Kind regards

Joris

 

 

 

Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens jan meisters
Verzonden: zaterdag 27 juni 2020 11:42
Aan: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk>
Onderwerp: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

 

Tested on Oregon 450 without crash: runs until destination.

 

Map used is from 04/2020, created with mkgmap-r4479 using my own (pure cycle) style.

Therefore routing still set to bicycle (fastest / avoid unaved), but as well no crash with ATV.

 

Nevertheless, here Calle Castillo de Ponferrada isn`t pink while simulation, but Calle Castillo de Alarcón is.

 

 

Am 26.06.2020 um 14:39 schrieb Felix Hartmann <extremecarver@gmail.com>:

 

https://www.openstreetmap.org/way/27866666/history#map=15/40.4752/-3.9411 

 

 

Trying to route along this route crashes the GPS device - not sure what i going on here. In demo mode - just set location to: https://www.openstreetmap.org/way/27866666/history#map=18/40.48063/-3.94040

 

and route to:

 

https://www.openstreetmap.org/way/27866666/history#map=19/40.46711/-3.94385 

(Calle Castillo de Ponferrada)

 

 The route will first be normal pink, however as soon as it goes onto the Calle Castillo de Alarcón

it will keep on routing - but the pink colour is gone. Then after maybe half of the road it stops routing and asks to recalculate (which will be in a loop if you click yes).

 

 

map produced with. 

start /low /b /wait java -jar -XX:+AggressiveHeap -XX:StringTableSize=1000003 -Xms15000M -Xmx29000M C:\openmtbmap\mkgmap.jar --max-jobs=8 --order-by-decreasing-area  --code-page=1252 --add-boundary-nodes-at-admin-boundaries  --nsis --index --levels="0:24, 1:23, 2:22, 3:21, 4:20, 5:19, 6:18" --overview-levels="7:17, 8:16, 9:15, 10:14, 11:13, 12:12" --add-pois-to-areas --pois-to-areas-placement=entrance=main;entrance=yes;building=entrance;barrier=entrance --reduce-point-density=3.4 --reduce-point-density-polygon=6 --add-boundary-nodes-at-admin-boundaries=2 --poi-excl-index=0x6405,0x4316,0x2f00 --cycle-map --check-roundabout-flares --ignore-fixme-values --housenumbers --road-name-config=C:\openmtbmap\openmtbmap_svn\roadNameConfig.txt --split-name-index --link-pois-to-ways --ignore-turn-restrictions --polygon-size-limits="24:16, 23:14, 22:12, 21:11, 20:10, 19:9, 18:8, 17:7, 16:6, 15:5, 14:4, 13:3, 12:2, 11:0, 10:0" --description=omtb_es --show-profiles=1  --location-autofill=bounds,is_in,nearest   --route --country-abbr=es --country-name=spain --mapname=64130000 --family-id=6413 --product-id=1 --series-name=omtb_spain_26.06.2020 --family-name=mtb_es_26.06.2020 --tdbfile --overview-mapname=mapsetc --keep-going --area-name="spain_26.06.2020_omtb" D:\openmtbmap\maps\64130028.osm.pbf   1>NUL 2>NUL

 

 

Routing setup on device as:

ATV/Off Road Driving

Minimize Distance

No Avoidances 

 

but I think this does not matter.

 

 

I have uploaded the broken tile/map here:

https://openmtbmap.org/maps.7z

the osm.pbf for that tile is:

https://openmtbmap.org/64130028.osm.pbf

 

 

I have no real clue what is happening here. If you set highway=residential from road_class=0 / road_speed=2 to say 1 / 1 crash is even earlier.

 

I cannot find anything special looking at the road with GPSMapedit. Garmin Edge devices supposedly crash too - not sure about other devices.

 

 

Felix

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

 

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

 

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev