@Gerd-Heinzmann-0 said in Alert when reaching a Viapoint:
@Tim-Thompson said in Alert when reaching a Viapoint:
The better solution perhaps is for the navigation app to navigate to each of the stops (vias). Not the shapping points (although there are arguments to make this a selectable option). The stops (vias). That means that the distance/time to, next turn, etc. information is displayed for each via. The problem with an "alert" - assuming that it's momentary - is that it can be easily missed (paying attention to the road etc. vs. the nav device). If the nav app is navigating to the next stop (via) you're not going to miss it.
Right now, this is the main issue that has me still using CoPilotGPS as my main mobile nav app. Hopefully this gets addressed in Next.
Right Tim, for me this is not a crazy feature, nobody ever will need, for me this is essential 
btw.: CoPilotGPS is no alternative, cause you can't import GPX files (as far as I know)
True... You can't import GPX files into CoPilotGPS. You either have to use an app to convert the GPX files to .trp or use a trip/route planner (for example - Furkot) that can export to .trp.
What CoPilotGPS will do is navigate to the stops. CoPilotGPS has it faults, but it's actually a pretty functional navigation app. Two display fields (displayed while navigating) are user configurable (on the fly) and can display - amongst other things - distance to next stop, ETA at next stop, time remaing until next stop.
I agree that this is an essentional functionality. The nav app needs to either navigate between stops (and/or shaping points) or have a notification/alert that manifest (in an unmistakenly noticeable fashion) well in advance (user configurable distance) and persist until the stop is reached.