Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Ah, okay, seems I removed the icon. Now it's back I found that option. Von: mkgmap-dev im Auftrag von Felix Hartmann Gesendet: Mittwoch, 8. Juli 2020 19:57 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

In the satellite screen. On Wed, 8 Jul 2020, 20:56 Gerd Petermann wrote: > How / where do I select the position? > > > Von: mkgmap-dev im Auftrag von > Felix Hartmann > 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)

How / where do I select the position? Von: mkgmap-dev im Auftrag von Felix Hartmann 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

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 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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi I'll try this. on eTrex, satellites screen, sub menu has "demo mode" or "use with satellites" off, then another option "set location on map", zoom in and cursor to a position then OK. On 30x in demo mode, can use normal find, then goto, choose fast/distance/off-road, then next menu has

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

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,

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

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

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 wrote: > Hi all, > > I tried to reproduce the routing errors on my Oregon 600 as Felix > described. I see similar problems with a map

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

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 +, Gerd Petermann wrote: > Hi Ticker, > > I don't understand. When I update the branch it would identical to > the trunk

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi Ticker, regarding order of roads: Yes, seems also to be related to the crash reported by Felix. It seems that a routing island like that including way 37139575 can cause invalid NOD data. Problem disappears when I use Steves patch just for this one way, it also disappears when I change the

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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 im Auftrag von Ticker Berkin Gesendet: Dienstag, 7. Juli 2020 11:11 An: Development list for mkgmap Betreff: Re:

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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/2786/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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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,

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi Steve I just tested the newly compiled jar and the pink line is there again! Also routing in Demo-mode works on my Oregon 650. Used bike, foot and car with default-style of recent April 2020 and the test area in Madrid that Felix pointed out. I also tested it with my own style which uses the

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

so I guess it would be good if we could have a current mkgmap without the NOD patches - or without the img patches of 4360 - and see which one causes the problem - and revert it. Those problems are really pretty common now. On Mon, 29 Jun 2020 at 11:18, Joris Bo wrote: > Update, previous

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Thank you Felix I’ll test them tommorow Kind regards Joris Van: mkgmap-dev Namens Felix Hartmann Verzonden: zaterdag 27 juni 2020 20:37 Aan: Development list for mkgmap Onderwerp: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles) Oh yeah - and

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Cool ! Thx, Joris -Oorspronkelijk bericht- Van: mkgmap-dev 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

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

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 wrote: > Hi Joris, > I right now can't test.

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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:

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi I suspect some of these routing problems are related to NET-no-NOD changes which were merged into r4360, 11-Nov-2019. However, using demo mode on my eTrex HCx demonstrates all sorts of weird behaviour that doesn't occur when navigating the same routes live. So I don't think it is a reliable

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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/ ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

@ Joris I have r4359 https://pinns.co.uk/osm/bts/mkgmap-r4359.zip On 27/06/2020 11:54, Joris Bo wrote: 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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

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 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 wrote: > >>

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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 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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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,

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

One suggestion perhaps is to save the area as a mp and use cgpsmapper to create the map? On 26/06/2020 16:49, Felix Hartmann wrote: It's fine in Basecamp and mapsource. On Fri, 26 Jun 2020, 18:40 Ticker Berkin > wrote: Hi Joris & Felix Can you test

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

It's fine in Basecamp and mapsource. On Fri, 26 Jun 2020, 18:40 Ticker Berkin 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 > > >

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

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

[mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

https://www.openstreetmap.org/way/2786/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/2786/history#map=18/40.48063/-3.94040 and route to: