I know, I can't find anything obvious. It would be great if the big can be found, because there are definitely some bugs about routing in mkgmap and it's hard to track down where they can be replicated. So if this one could be fixed, maybe it will improve a lot because it helps understanding of what is wrong in mkgmap m On Fri, 26 Jun 2020, 17:52 Joris Bo <jorisbo@hotmail.com> wrote:

Hi Felix

I retested your example and have more or less the same results on my Oregon 650

Builded a map with both default style and with my own style.

Both maps have the confusing problem

The default map askes for recalculation every time and does not finish. It stays in loop.

My own style recalculates automatically but still finishes at the end

But when passing the demo route, it is thrown back to the beginning of the Castillo Alarcon every time.

Constantly Showing: Go right Castillo Alarcon, Go Left Castillo Penafiel

Renamed all maps, including my Oregon 650 default maps, to be invisible

The pink line is not visible for the road you specified (Castillo Alarcon) but it is visible prior to entering this street and also again after it.

My style

highway = residential [0x06 road_class=0 road_speed=2 resolution 24]

mkgmap:car and all other vehicles are set to yes

But I do not have any idea, data looks normal to me.

Kind regards,

Joris

*Van:* mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> *Namens *Felix Hartmann *Verzonden:* vrijdag 26 juni 2020 14:39 *Aan:* Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> *Onderwerp:* [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

It's fine in Basecamp and mapsource. On Fri, 26 Jun 2020, 18:40 Ticker Berkin <rwb-mkgmap@jagit.co.uk> wrote:

Hi Joris & Felix

Can you test this in both Basecamp and Mapsource. I have found problem areas recently where Mapsource and my old eTrex have no routing problems but Basecamp does.

Ticker

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

Hi all Have you experienced these problem while actually 'on-the-ground' - maybe it is just a problem with Demo Mode. I've just been experimenting with Demo and the route calculations look fine, it follows the road, but at one junction I got the turn pop-up but the simulation went straight on, then went into the 'recalculate' dialog. Will experiment a bit more with routes that I know work in live mode. Ticker

Oh yeah - i also tried several other road_class and road_speed. It is not related to it. On Fri, 26 Jun 2020 at 19:03, Felix Hartmann <extremecarver@gmail.com> wrote:

I got notified by someone using it on the ground, it results in complete crash, needs reboot

On Fri, 26 Jun 2020, 19:59 Ticker Berkin <rwb-mkgmap@jagit.co.uk> wrote:

...

Hi all

Have you experienced these problem while actually 'on-the-ground' - maybe it is just a problem with Demo Mode.

I've just been experimenting with Demo and the route calculations look fine, it follows the road, but at one junction I got the turn pop-up but the simulation went straight on, then went into the 'recalculate' dialog.

Will experiment a bit more with routes that I know work in live mode.

Ticker

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

-- Felix Hartman - Openmtbmap.org & VeloMap.org

I also think routing problems were much less frequent over 1 year ago. I think I tried 4195 however and it also didn't work. But I wasn't using default style. Still I think it's not directly related to the style. So you used the current default style, and it worked on the older versions? On Sat, 27 Jun 2020, 10:19 Joris Bo <jorisbo@hotmail.com> wrote:

Hi,

I did some more testing.

- I created a style with only 10 highway types and access=yes to everything. Didn’t help. - Reversed the route: did not help

- If I go back to mkgmap r3995 (24-8-2017) (random pick of version I found in my backups) it works again ! (Used today’s recent default style) - r4286 also works (16-4-2019) - Version r4431 (25-1-2020) still reveals the problem.

So it looks like somewhere between April 2019 and January 2020 something is done different.

Kind regards

*Van:* mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> *Namens *Felix Hartmann *Verzonden:* vrijdag 26 juni 2020 19:59 *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)

Oh yeah - i also tried several other road_class and road_speed. It is not related to it.

On Fri, 26 Jun 2020 at 19:03, Felix Hartmann <extremecarver@gmail.com> wrote:

I got notified by someone using it on the ground, it results in complete crash, needs reboot

On Fri, 26 Jun 2020, 19:59 Ticker Berkin <rwb-mkgmap@jagit.co.uk> wrote:

Hi all

Have you experienced these problem while actually 'on-the-ground' - maybe it is just a problem with Demo Mode.

I've just been experimenting with Demo and the route calculations look fine, it follows the road, but at one junction I got the turn pop-up but the simulation went straight on, then went into the 'recalculate' dialog.

Will experiment a bit more with routes that I know work in live mode.

Ticker

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

--

Felix Hartman - Openmtbmap.org & VeloMap.org

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

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<mailto: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<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Am 27.06.20 um 12:54 schrieb Joris Bo:

Is there a online repository of compiled mkgmap versions?

Here are all the versions I still have: http://www.kleineisel.de/ralf/gps/mkgmap/

@ Joris: <http://cornerbug.com/html/mkgmap/mkgmap-r4373.zip>mkgmap- <http://cornerbug.com/html/mkgmap/mkgmap-r4373.zip>r4373 <http://cornerbug.com/html/mkgmap/mkgmap-r4373.zip> @ 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 <mailto: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 <mailto: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 <mailto: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 <mailto:extremecarver@gmail.com>>:

https://www.openstreetmap.org/way/27866666/history#map=15/40.4752/-3.9411 <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 <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 <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 <https://openmtbmap.org/maps.7z> the osm.pbf for that tile is: https://openmtbmap.org/64130028.osm.pbf <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 <mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>

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

Hi Joris, I right now can't test. Forgot my charger for the batteries of my Garmin. But I compiled you verison 4374 to 4383 (leaving out 4375 as it has no functional change - only documentation. Likely 4381 is also not related to routing at all). you can download them here: https://openmtbmap.org/mkgmap_dist.7z Felix On Sat, 27 Jun 2020 at 17:06, Joris Bo <jorisbo@hotmail.com> wrote:

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- <http://cornerbug.com/html/mkgmap/mkgmap-r4373.zip>r4373 <http://cornerbug.com/html/mkgmap/mkgmap-r4373.zip>

@ 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

-- Felix Hartman - Openmtbmap.org & VeloMap.org

Thank you Felix I’ll test them tommorow Kind regards Joris Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Felix Hartmann Verzonden: zaterdag 27 juni 2020 20:37 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) Oh yeah - and maybe you are lucky and get through the whole road not in pink, my Oregon never made it further than 2/3 before dropping the route. As long as it's not pink - there is some serious error. On Sat, 27 Jun 2020 at 20:30, Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> wrote: Hi Joris, I right now can't test. Forgot my charger for the batteries of my Garmin. But I compiled you verison 4374 to 4383 (leaving out 4375 as it has no functional change - only documentation. Likely 4381 is also not related to routing at all). you can download them here: https://openmtbmap.org/mkgmap_dist.7z Felix On Sat, 27 Jun 2020 at 17:06, Joris Bo <jorisbo@hotmail.com<mailto:jorisbo@hotmail.com>> wrote: 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<mailto: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<mailto:mkgmap-dev@lists.mkgmap.org.uk>> Onderwerp: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) @ Joris: mkgmap-<http://cornerbug.com/html/mkgmap/mkgmap-r4373.zip>r4373<http://cornerbug.com/html/mkgmap/mkgmap-r4373.zip> @ 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<mailto: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<mailto: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<mailto: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<mailto: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<mailto: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<mailto: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<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Openmtbmap.org & VeloMap.org -- Felix Hartman - Openmtbmap.org & VeloMap.org

Cool ! Thx, Joris -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Steve Ratcliffe Verzonden: zondag 28 juni 2020 10:22 Aan: mkgmap-dev@lists.mkgmap.org.uk Onderwerp: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) Hi Joris

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

Thanks for narrowing it down. There was a large change not long before that in version 4360 with the merge of the NET-no-NOD branch that did affect the routing a lot. It causes the NodCheck utility to crash, I don't know why yet. I've put all precompiled jar files at: http://www.mkgmap.org.uk/jars/ Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Update, previous version had some errors, conclusion is the same 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 r4358 Joris Bo Oregon 650 Default 2020 Yes No Ok r4359 Joris Bo Oregon 650 Default 2020 Yes No Ok r4360 Joris Bo Oregon 650 Default 2020 No Yes Wrong This is what Ticker suspected and also Steve suggested. 4360 introduced new routing behaviour by design r4361 Joris Bo Oregon 650 Default 2020 No Yes Wrong r4372 Joris Bo Oregon 650 Default 2020 No Yes Wrong 17-11-2019 r4373 Joris Bo Oregon 650 Default 2020 Yes No Ok Orginally tested with jar file supplied by Jan Meisters: Thought it was oke!, still have the working img, but I cannot prove again this img was really created by that version. The Jar version of Steve creates an img that is not oke? 2nd & 3th time compile again with Jan's jar file to double check also suddenly is wrong: So I must have made a mistake in copy/paste or documenting the testresults. Conclusion 4373 is not oke 17-11-2019 r4373 Joris Bo Oregon 650 Default 2020 No Yes Wrong r4374 Joris Bo Oregon 650 Default 2020 No Yes Wrong r4376 Joris Bo Oregon 650 Default 2020 No Yes Wrong r4379 Joris Bo Oregon 650 Default 2020 No Yes Wrong 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 Joris Bo Verzonden: maandag 29 juni 2020 11:05 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) Hi I finished testing and it narrows down to 4360 Kind regards, Joris 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 r4358 Joris Bo Oregon 650 Default 2020 Yes No Ok r4359 Joris Bo Oregon 650 Default 2020 Yes No Ok r4360 Joris Bo Oregon 650 Default 2020 No No Wrong This is what Ticker suspected and also Steve suggested. 4360 introduced new routing behavior by design r4361 Joris Bo Oregon 650 Default 2020 No No Wrong r4372 Joris Bo Oregon 650 Default 2020 No No Wrong 17-11-2019 r4373 Joris Bo Oregon 650 Default 2020 Yes No Ok Orginally tested with jar file supplied by Jan Meisters: Thought it was oke!, still have the working img, but I cannot prove again this img was really created by that version. The Jar version of Steve creates an img that is not oke? 2nd & 3th time compile again with Jan's jar file to double check also suddenly is wrong: So I must have made a mistake in copy/paste or documenting the testresults. Conclusion 4373 is not oke 17-11-2019 r4373 Joris Bo Oregon 650 Default 2020 No No Wrong r4374 Joris Bo Oregon 650 Default 2020 No Yes Wrong r4376 Joris Bo Oregon 650 Default 2020 No Yes Wrong r4379 Joris Bo Oregon 650 Default 2020 No Yes Wrong 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 -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> Namens Steve Ratcliffe Verzonden: zondag 28 juni 2020 10:22 Aan: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) Hi Joris

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

Thanks for narrowing it down. There was a large change not long before that in version 4360 with the merge of the NET-no-NOD branch that did affect the routing a lot. It causes the NodCheck utility to crash, I don't know why yet. I've put all precompiled jar files at: http://www.mkgmap.org.uk/jars/ Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi

Update, previous version had some errors, conclusion is the same

OK, Thanks that is great. So I don't think that there wasn't really intended to be a change to routing in that branch, but there was an experimental option that was added, and then removed, with a couple of lines of code omitted, probably unintentionally. This is what causes the failure in NodCheck and maybe causes the failure on the device too. The attached patch restores the functionality and NodCheck does not crash on the result There is a pre-compiled jar there: http://files.mkgmap.org.uk/download/484/mkgmap.jar It may interact or interfere with the routing island removal code that was also made in that branch. I've no idea if it does or not, it is just something to check. Steve

Hi all, the patch reverts one of the major size improvements of the branch. It adds again routing nodes at the end of all roads. Seems there are special cases. Will look at them again when I am back. Gerd ---- Steve Ratcliffe schrieb ---- Hi

Update, previous version had some errors, conclusion is the same

OK, Thanks that is great. So I don't think that there wasn't really intended to be a change to routing in that branch, but there was an experimental option that was added, and then removed, with a couple of lines of code omitted, probably unintentionally. This is what causes the failure in NodCheck and maybe causes the failure on the device too. The attached patch restores the functionality and NodCheck does not crash on the result There is a pre-compiled jar there: http://files.mkgmap.org.uk/download/484/mkgmap.jar It may interact or interfere with the routing island removal code that was also made in that branch. I've no idea if it does or not, it is just something to check. Steve

Hi Gerd I've been trying to pin down another routing problem that shows on MapSource and eTrex 30x & HCx, but not BaseCamp. It also happens on an old version I have (r42950) which is pre NET-no-NOD. When you were looking at some of the problems I was having with NET-no -NOD, changing the order of roads affected routing errors I was getting. However, most problems were only demonstrated in BaseCamp, where having a lineType that should be routable but isn't (because of the NOD removal or explicitly using one) makes a non-routable area around the feature. It would be handy if you updated the NET-no-NOD branch to the latest trunk. Ticker On Tue, 2020-07-07 at 08:38 +0000, Gerd Petermann wrote:

Hi all,

I am back home and started to look at the data. I assume the special case with way https://www.openstreetmap.org/way/27866666/history#map= 16/40.4820/-3.9354 is that it is not connected to other roads in both end nodes AND that is is connected to multiple other roads between the ends. I guess I didn't think of this case before.

I can reproduce the crash with NodCheck when I create a map for 64130028.osm.pbf using only the option --route, but up to now I was not able to reproduce it with a smaller input file just containing the area around the special way, so there might be a 2nd problem...

Gerd

Hi Gerd If you were to use it to experiment with routing, I'd keep updated with the branch and use it to investigate my problem. Ticker On Tue, 2020-07-07 at 09:21 +0000, Gerd Petermann wrote:

Hi Ticker,

I don't understand. When I update the branch it would identical to the trunk version. How does that help?

Gerd

________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 7. Juli 2020 11:11 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi Gerd

I've been trying to pin down another routing problem that shows on MapSource and eTrex 30x & HCx, but not BaseCamp. It also happens on an old version I have (r42950) which is pre NET-no-NOD.

When you were looking at some of the problems I was having with NET -no -NOD, changing the order of roads affected routing errors I was getting.

However, most problems were only demonstrated in BaseCamp, where having a lineType that should be routable but isn't (because of the NOD removal or explicitly using one) makes a non-routable area around the feature.

It would be handy if you updated the NET-no-NOD branch to the latest trunk.

Ticker

On Tue, 2020-07-07 at 08:38 +0000, Gerd Petermann wrote:

...

Hi all,

I am back home and started to look at the data. I assume the special case with way https://www.openstreetmap.org/way/27866666/history#map= 16/40.4820/-3.9354 is that it is not connected to other roads in both end nodes AND that is is connected to multiple other roads between the ends. I guess I didn't think of this case before.

I can reproduce the crash with NodCheck when I create a map for 64130028.osm.pbf using only the option --route, but up to now I was not able to reproduce it with a smaller input file just containing the area around the special way, so there might be a 2nd problem...

Gerd

_______________________________________________ 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

I've got feedback that with the patch from steve applied - the actual routing for that street is working again. On Wed, 8 Jul 2020 at 08:10, Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:

Hi all,

I tried to reproduce the routing errors on my Oregon 600 as Felix described. I see similar problems with a map produced with r4555, but I never see good routing results in demo mode. Neither the patch from Steve nor a map produced with r4359 produce better results. For me they look even worse. I've never used the demo mode on this device so I have no idea if it ever worked or if I do something wrong. I create a short route with two nodes and select "map". The device first shows a plausible pink line but when I press OK it first tells me that the calculation may take long and then that there are no routable ways in this area.

Gerd

________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 7. Juli 2020 13:34 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi Gerd

If you were to use it to experiment with routing, I'd keep updated with the branch and use it to investigate my problem.

Ticker

On Tue, 2020-07-07 at 09:21 +0000, Gerd Petermann wrote:

...

Hi Ticker,

I don't understand. When I update the branch it would identical to the trunk version. How does that help?

Gerd

________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 7. Juli 2020 11:11 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi Gerd

I've been trying to pin down another routing problem that shows on MapSource and eTrex 30x & HCx, but not BaseCamp. It also happens on an old version I have (r42950) which is pre NET-no-NOD.

When you were looking at some of the problems I was having with NET -no -NOD, changing the order of roads affected routing errors I was getting.

However, most problems were only demonstrated in BaseCamp, where having a lineType that should be routable but isn't (because of the NOD removal or explicitly using one) makes a non-routable area around the feature.

It would be handy if you updated the NET-no-NOD branch to the latest trunk.

Ticker

On Tue, 2020-07-07 at 08:38 +0000, Gerd Petermann wrote:

...

Hi all,

I am back home and started to look at the data. I assume the special case with way https://www.openstreetmap.org/way/27866666/history#map= 16/40.4820/-3.9354 is that it is not connected to other roads in both end nodes AND that is is connected to multiple other roads between the ends. I guess I didn't think of this case before.

I can reproduce the crash with NodCheck when I create a map for 64130028.osm.pbf using only the option --route, but up to now I was not able to reproduce it with a smaller input file just containing the area around the special way, so there might be a 2nd problem...

Gerd

_______________________________________________ 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 _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- Felix Hartman - Openmtbmap.org & VeloMap.org

Hi Gerd Can you have an option, possibly hidden (not in options.txt), that doesn't force the route node at the start and/or end of a road. With the current trunk (r4555) my gmapsupp.img is 5.5% smaller than with a pre NetNoNod version (r4295), both using the default style from r4295. Ticker

Hi all, attached is a patch with changes the order of the nodes without arcs to appear first. The binary is here: http://files.mkgmap.org.uk/download/485/mkgmap.jar The patch seems to improve routing with Felix' test case but I still have trouble to get the demo mode working, so it woud be great to hear your results. I seem to be unable to tell the device were it should start to simulate the route, it always starts somewhere else. Guess I have to read the manual to find out how this simulation mode has to be used... Advantage of this patch is that it has nearly no impact on the img size. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen@hotmail.com> Gesendet: Mittwoch, 8. Juli 2020 10:57 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) Hi developers, I analysed the Garmin demo maps with routing data and found out that there is a difference compared to the map produced by mkgmap. Garmin maps also have route nodes without arcs, but those always appear in the first route center while mkgmap doesn't care about this order. Also, this first route center contains ONLY contains nodes without arcs. Such a node without arcs is typically a routing island, e.g. if a map contains a T-shaped junction without further road connections. These nodes without arcs don't occur with Steves patch, so it might be the place which causes the trouble. I am not yet sure what happens when a single tile contains so many nodes without arcs that they don't fit into a single route center. I did not yet find such a case in the Garmin maps. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen@hotmail.com> Gesendet: Mittwoch, 8. Juli 2020 08:42 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) Hi Felix, OK, so I guess we have to prefer stabilty for now. I try to find out under what circumstances Garmin uses route nodes at the end of ways in their demo maps. If I don't find anything today I'll commit Steves patch. Better safe than sorry. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Mittwoch, 8. Juli 2020 08:34 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) I've got feedback that with the patch from steve applied - the actual routing for that street is working again. On Wed, 8 Jul 2020 at 08:10, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote: Hi all, I tried to reproduce the routing errors on my Oregon 600 as Felix described. I see similar problems with a map produced with r4555, but I never see good routing results in demo mode. Neither the patch from Steve nor a map produced with r4359 produce better results. For me they look even worse. I've never used the demo mode on this device so I have no idea if it ever worked or if I do something wrong. I create a short route with two nodes and select "map". The device first shows a plausible pink line but when I press OK it first tells me that the calculation may take long and then that there are no routable ways in this area. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto:rwb-mkgmap@jagit.co.uk>> Gesendet: Dienstag, 7. Juli 2020 13:34 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) Hi Gerd If you were to use it to experiment with routing, I'd keep updated with the branch and use it to investigate my problem. Ticker On Tue, 2020-07-07 at 09:21 +0000, Gerd Petermann wrote:

Hi Ticker,

I don't understand. When I update the branch it would identical to the trunk version. How does that help?

Gerd

________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto:rwb-mkgmap@jagit.co.uk>> Gesendet: Dienstag, 7. Juli 2020 11:11 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi Gerd

I've been trying to pin down another routing problem that shows on MapSource and eTrex 30x & HCx, but not BaseCamp. It also happens on an old version I have (r42950) which is pre NET-no-NOD.

When you were looking at some of the problems I was having with NET -no -NOD, changing the order of roads affected routing errors I was getting.

However, most problems were only demonstrated in BaseCamp, where having a lineType that should be routable but isn't (because of the NOD removal or explicitly using one) makes a non-routable area around the feature.

It would be handy if you updated the NET-no-NOD branch to the latest trunk.

Ticker

On Tue, 2020-07-07 at 08:38 +0000, Gerd Petermann wrote:

...

Hi all,

I am back home and started to look at the data. I assume the special case with way https://www.openstreetmap.org/way/27866666/history#map= 16/40.4820/-3.9354 is that it is not connected to other roads in both end nodes AND that is is connected to multiple other roads between the ends. I guess I didn't think of this case before.

I can reproduce the crash with NodCheck when I create a map for 64130028.osm.pbf using only the option --route, but up to now I was not able to reproduce it with a smaller input file just containing the area around the special way, so there might be a 2nd problem...

Gerd

_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto: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<mailto: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<mailto: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<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Openmtbmap.org & VeloMap.org _______________________________________________ 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

Hi Gerd I've been out driving with new map on an eTrex HCx. On shortest distance it chose a route that didn't seem best; I need to look at the roads on another map to see if it made sense. I I also got a turn pop-up off the road I was on that went into a car -park only. I'll try same map on MapSource & BaseCamp and see how they behave for the same routes. Also try with a more standard style and an older version. Ticker

How / where do I select the position? ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Mittwoch, 8. Juli 2020 19:54 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) Put the gps reception into demo mode, then select the position. It is pretty tedious however. On Wed, 8 Jul 2020, 15:47 Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto:rwb-mkgmap@jagit.co.uk>> wrote: Hi Gerd I've been out driving with new map on an eTrex HCx. On shortest distance it chose a route that didn't seem best; I need to look at the roads on another map to see if it made sense. I I also got a turn pop-up off the road I was on that went into a car -park only. I'll try same map on MapSource & BaseCamp and see how they behave for the same routes. Also try with a more standard style and an older version. Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

In the Oregon 600 demo mode works well. It's just you have to go back after each time to set location again to the start point. Then don't use the search but simply go into map screen and click onto the destination point and route there. With Search I also had problems, same as simple simulation of a route. On Wed, 8 Jul 2020, 20:57 Felix Hartmann <extremecarver@gmail.com> wrote:

In the satellite screen.

On Wed, 8 Jul 2020, 20:56 Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:

...

How / where do I select the position?

________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com> Gesendet: Mittwoch, 8. Juli 2020 19:54 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Put the gps reception into demo mode, then select the position. It is pretty tedious however.

On Wed, 8 Jul 2020, 15:47 Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto: rwb-mkgmap@jagit.co.uk>> wrote: Hi Gerd

I've been out driving with new map on an eTrex HCx.

On shortest distance it chose a route that didn't seem best; I need to look at the roads on another map to see if it made sense. I

I also got a turn pop-up off the road I was on that went into a car -park only.

I'll try same map on MapSource & BaseCamp and see how they behave for the same routes. Also try with a more standard style and an older version.

Ticker

_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto: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

Hi Gerd Testing the same map on MapSource shows the same fault as on the eTrex HCx device, where, in one direction, the instructions are to turn up a dead-end road, make a U-turn, turn back onto the main road. On BaseCamp it makes a 5 km detour to avoid this point. I haven't had a chance yet to try different versions and a stable style, so I don't know if the patch has make things worse. This is similar to behaviour I've seen with an old version and I'm reducing the map to the smallest area and will send this when I've assembled all the necessary info. Ticker On Wed, 2020-07-08 at 13:47 +0100, Ticker Berkin wrote:

Hi Gerd

I've been out driving with new map on an eTrex HCx.

On shortest distance it chose a route that didn't seem best; I need to look at the roads on another map to see if it made sense. I

I also got a turn pop-up off the road I was on that went into a car -park only.

I'll try same map on MapSource & BaseCamp and see how they behave for the same routes. Also try with a more standard style and an older version.

Ticker

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