Kurviger.de | Application | Blog | Frequently Asked Questions (FAQ) | Legal Notice | Privacy Policy

Show list of u-turns

@ Uli_LH…I suppose I am using the correct (new) tread for the next proposal ?

@ Robin. Not urgent !
Only when all the dust, caused by your new website, has settled :wink:

Unless a free extra offer for all ? Otherwise could be a niceTourer web extra ?

Planner agreement to do.
Desired scheduled U-turns should best be triggered by a Via Point.

Introduction.
Sloppy misplaced Shaping points at road intersections cause false turn instructions and *a nearby U-turn. These unexpected 180° U-turns (sign -98) indicate that something may have gone wrong with a somewhat too hasty route planning.

You can find the U-turns due to incorrect positioned Shaping waypoints in the turn instruction list pretty quickly. For a long route with many instructions you will have to spend a little longer tracking them all down. Click on a U-turn instruction and quickly find the corresponding Shaping Point on the map and correct it. When the unplanned unwanted (Shaping) U-turns are gone you will have *almost no false turn instructions left. By the way this procedure works very nice using the Kurviger app too !

The * Exceptions. So avoid planner mistakes and work accurately at waypoint placements !

  • It can sometimes happen that you are offered a return alternative over a nearby traffic circle.
  • In case of multiple lanes with a passage correction by a directional U-turn. EU:Left U. UK:Right U

Tourer web ? Cleaning tool.
Kurviger Planner notifies you of the total number of detected suspicious (Shaping) U-turns.
Shows a compact turn list with only the (Shaping) U-turns and the suspicious positions on the map.
You so do not have to search the entire Turn List manually. Then follow the same correction procedure as the non-tourer

I do have something planned for this, yes :slight_smile:. I think we have talked about this in a few several threads already :slight_smile:.

And now with the redesign there is finally enough space and the required basics to introduce new features like that.

Essentially the feature request is to present a list of route u-turns?

Yes, that would be very helpful. Especially when importing routes this happens very often and it is hardly visible in the planning.

It would be almost even better if this is automatically corrected

If admin thinks this should be a separate thread, please move “in block”.
It is primarily intended for the website with the aim of keeping the app simple.
Provided good experience or not, this is possible later in the app maybe.

That’s how I imagined it in the past.
Automatic was intended for the next idea.

But we’re still a long way from that, so …step by step ;-).

For the classic route planning, therefore, formulated a little less drastically.
With careful manual planning, the number of annoying U-turns is limited.
In this way, the user himself retains the desired correction control.

From my point of view it would be better to improve route automatically - if I understand right there is an easy way to identify “wrong” U-Turns.

There was a route example supplied by @llodiers :

Loading that route (app or web) and analyzing it, all “error” U-Turns are related to wapoints:
WP7, WP14, WP15, WP16, WP27, WP37, WP38, WP39, WP40, WP43, WP45, WP48, WP49

All of them besides WP45 and WP48 can be identified by an easy rule: U-Turn conected to a waypoint, with an other turn point less than 15m before / after. WP45 and WP48 have bigger deviations due to snapping next street.

So I would provide a rule, which is executed if a GPX route or track is imported:

  • If a U-Turn is connected to a waypoint, and an other turn instruction if less than 15m (to be discussed, if perhaps even 20m or 30m) before / after, shift that waypoint to the position of the turn instruction.
  • after shifting all waypoints, do a new route calculation

This would fix most of the “error” U-turns in that route.

If you have further examples of routes with “error” U-turns, please provide that examples here.

Even if stopover waypoints are snapped over 30m to an other turn instruction, from my point of view this will not harm even if user has to ride in an other street for 30m.

1 Like

There is also an easy workaround on website to search for U-turns (at least in German version):

  • show turn hints
  • show turn hints on map:
    image
  • use search function of browser, search “wenden”
  • click “next hit” in search function of browser
    image
  • click on shown hit
    image

Edit: Works also in English version, search for “u-turn” instead:
image

2 Likes

I am not sure if this should be done automatically. There are probably cases where this is desired to have a waypoint at such a position. For example for any parking / pause stops.

Having a system that helps to easily identify these places and maybe other potentially incorrectly set waypoints would certainly help :+1:

3 Likes

Thanks Rumbrummer for thinking along.
I will read this later with more attention am just getting to my beer now. (Rain)

A nice example by Wolfgang confirms the above.

So here no alarms nor automatic changes.

1 Like

Hey - thanks a lot for this “trick” to search “wenden” in turn hints! Up to now I scanned the .kurviger file with Notepad++ for “-98”.

Btw: My current workflow for taking tracks from outside is simply to “convert” them with GpxShaping to a route. The waypoints (intelligently set by GpxShaping) are then taken from kurviger import.

If you like a test: shorttrack.gpx (77.7 KB)
Directly imported in kurviger → 4 times “wenden”
Taking GpxShaping in account → no “wenden” at all

You should search for all u-turn types (see here):

  • U-turn unknown: -98
  • U-turn left: -8
  • U-turn right: 8

@ rumbrummer

A. The tip with search u-turn or “wenden” you thought up well. Makes locating easier.
In a tool version, of course, the presentation should be completely language independent.

B. Route planner design.
I do not think of automatic corrections actually. I prefer to keep control of this myself

C. The tip for automatic correction I doubt, since I prefer a ROBUST @ simple rule

The Rumbrummer proposal I had imagined as follows.

  1. Assign misplaced Shaping Point the coordinates of the enclosing turns then MAGIC ! Only the unannounced Shaping Point remains.

  2. But Shaping Point & U-turn(-98) are not necessarily enclosed between between 2 consecutive turns at exactly the same location.

     A. False turn > Shaping U-turn > Correction turn. U-turn CLEARLY enclosed. Robust.
     B. (Continue) > Shaping U-turn > Correction turn. U-turn not enclosed. Robust? 
     C. False turn > Shaping U-turn> (Continue). U-turn not enclosed. Robust? 
    

D. Left or Right U-turns because of this are extremely rare. I’m not worried about that.

The essential not to forget.
Design accurately then hardly any such corrections are needed

I tested the method a little more. Unfortunately not always 100% successful. I took the turn coordinates (6 digits after the comma), but sometimes still a track glitch appeared. It is too delicate for me. So I still do prefer manual correction. Fully automatic without final check I do not trust. You can just as quickly move a few wrongly positioned shaping points a bit further away from the critical road crossings.

1 Like

:+1:
This seems the best solution.

4 posts were split to a new topic: MotoPlaner GPX

Avoid undesirable U-turns by optimal map display.
Advise: “Unset Turn instruction nodes”.

  1. Plant desired U-turn by announced Via Point & Icon.
  2. Good Shaping Point. White Circle Icon. (Shaping-Continue combi).
  3. Bad Shaping Point. Red Circle Icon. (Shaping-U-turn combi).

See Circle Red ? Move until White.
20211107_111403

(Website & app)

1 Like

U-turns can also exist on via points.

True.
I suppose by a Via edit U-turns so are mostly intentionally planned so I did nog suggest a “red” light warning signal.
Anyway Emux if you have a different opinion you are completely free to (eventually) apply this also on Via’s. No objection, of course not.

By the way the import file in the .gif was next one.
TET_trk_0.50km_rte_ticks.gpx (13.9 KB)
Import (gpx) route
Overlay: Track
Routing: Route
Unchanged
Max waypoints: 200

Information.
Locus recently has introduced also a trackglitch alert into the Locus Planner using the offline BRouter engine.
After tests I found out there is a small difference in track generation production by both router engines GH or BRouter.
Locus so optimised this alert method mainly for the prefered Locus_BRouter offline planner.
Read more in next.

https://forum.locusmap.eu/index.php?topic=7575.msg65369#msg65369

1 Like