Shaping and Via Point imports by a gpx file into the Locus Routeplanner

CLEAR Result: Route point creation. (By Locus routeplanner action)
When using the Routeplanner to produce a design you do this by using direct placed Shaping or Via references, clear, so are route points. 
In the track calculation (according to the routing profile) these points are then also by snap to street action placed on the street pattern. Works.

RANDOM result:  Gpx file import with waypoints.
If you import a file with waypoints into the Routeplanner how can the Locus routeplanner know if these are simple free located individual waypoints or if they are meant to act as routewaypoints ? 
A file import with simple waypoints to produce a track is nonsense. It can by chance turn out the way you expect but it can just as well turn out completely different. Clarity trumps clarity.
And even worse, you do not even want to make a track calculation with these  waypoints?  The Locus planner has to guess what you so do expect?  This is not how it works.
The wrong thing in the Locus planner is that it gives you the ILLUSION (blue square Icons) to suggest it recognizes some imported waypoints as Via Points. This is thoroughly ERRONEOUS.

CLEAR result: Via Route Points on gpx file import.
A desing consisting of a track with snap to street track points is so calculated from a route with Via or Shaping Routepoints. 
The route points are by "snap to street" action by the routing engine automatically "snapped" but now as track points !

RANDOM result: Gpx file import with simple free located waypoints.
Waypoints are mainly meant to be used to indicate a simple individualistic free interesting position. 
One exception is a Locus track by ASSOCIATED 'special' navigation waypoints but this only works within the Locus app. 
Associated 'special' waypoints are so promoted to "substitute" routepoints in the Locus app and so are usable for the route planner.
So at imports, use those simple waypoints for what they are originally intended are only. Simple independent individualistic positions !

CLEAR result. Gpx file import with (rte)route_(rtept)routepoints.
With such a file import only Shaping or Via routepoints ar to be considered as 'real' good clear references for the Routeplanner. 
Route points are usually not snapped to street reference positions with such imports. That comes later in the result track calculation.
After the routing engine calculates a track with track points from it, you will find the route points as snapped to the street track points.

* These snapped to street points can even keep their original Shaping of Via Point function nicely in the resulting track points.
Using the trackpoint type Shaping or Via, you can indicate the origin function very simply and discreetly but perfectly clear.
By marking trackpoints with type Shaping or Via type, you can even 'distill' the route points back but now as snapped to street route points.

* := Not implemented in Locus. Could be (= still idea proposal) !  (A certain other app is already implementing this very simply to implemnet method by the point type)

End.