[mkgmap-dev] Problem in AngleFixer?

Wed Aug 14 16:48:33 BST 2024

Hi Thorsten

I can't explain the turn instructions being in the wrong direction for some
ranges of angles. What are you seeing this on - Basecamp / MapSource / Garmin
Device?

At the moment I'm more concerned with why, for your first example, we get
different arcs being adjusted. I've added more diagnostics to show if the
continuous way has been split and been given different ids.

Can you send me the same sections of the log file, the first should look like
this:

fixSharpAngles_v4 at 49.478507,10.942814 mask 2 smallestAngle 15.375715 nArcs 3
nDirectArcs 3 nGroups 3
Arc heading -32.3756 328° angToPrev 166.0431 class 2 speed 3 way 144732811
isFake false rdDef 318472903 name null paved true
Arc heading -16.999884 343° angToPrev 15.375715 class 1 speed 3 way 36138336
isFake false rdDef 1286211837 name null paved true
Arc heading 161.5813 162° angToPrev 178.58118 class 1 speed 3 way 36138336
isFake false rdDef 1286211837 name null paved true
Angle 15.375715 between -32.3756 and -16.999884 minAngle 46.0 wantedInc
30.624285 deltaPred 120.043106 deltaNext 132.58118
decreasing arc with heading 328° by 30.624285
modInitialHeading arc from -32.3756 by -30.624285 to -62.999886

If, in this example, way 36138338 has been split, I need to see if there is any
way of finding the associated bits of road

Attached is new patch.

Regards
Ticker

On Tue, 2024-08-13 at 19:44 +0200, Thorsten Kukuk wrote:
> Hi Ticker,
> 
> The code is identical.
> 
> But: how do you explain, that on all junctions, where your logging 
> reports headings
> in the 3xx° area, Garmin navigation instructions are wrong, and where 
> the
> headings are < 180°, the navigation instructions are correct? In between 
> it looks like, turn instructions for both directions are given.
> And I don't speak here about the two junctions I brought up in this mail 
> thread,
> I selected several random junctions from the log file with "sharp angle" 
> and created routes for it.
> And for all, where the headings are in the 3xx° area, the notifications 
> were "wrong", and in all, where
> it was below 180°, it was correct.
> 
> Examples for "wrong" routing instructions:
> sharp angle 13.183327 ° at 49.294696,11.107571 headings 307° 320° speeds 
> 2 2 classes 3 1
> increasing arc with heading 320° by 32.816673
> 
> sharp angle 32.202377 ° at 49.445028,11.075047 headings 322° 354° speeds 
> 3 2 classes 1 3
> decreasing arc with heading 322° by 13.797623
> 
> My observation:
> headings below < 180° seem to be fine. Or I had always luck when 
> testing.
> headings around 270° seems to give you instructions for both directions.
> headings in the 3xx° area will give you "wrong" instructions.
> 
> Regards,
> Thorsten

-------------- next part --------------
A non-text attachment was scrubbed...
Name: AngleChecker_v4.patch
Type: text/x-patch
Size: 9808 bytes
Desc: not available
URL: <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20240814/8989e330/attachment.bin>