https://youtu.be/81R5TjPrVVI
There is a very interesting utility in the video description that imports a route file and can add an adjustable number of shaping points between via points. It can also add a sequential prefix to each routing point name.
My route planning is 99.9% in Basecamp, but I thought this might be useful for those using other route planners. I did try renaming points in a route gpx from Basecamp, but that did not work.
Using shaping/via points for Rever or Google kml files
-
jfheath
- Posts: 3067
- Joined: Sat Oct 19, 2019 4:17 pm
- Location: West Yorkshire, Uk
- Has liked: 421 times
- Been liked: 921 times
Re: Using shaping/via points for Rever or Google kml files
I was going to ask a separate question - but came across this post and thought it was worth a bump.
That looks as though it could be a very useful utility.
I had a look at Rever last night and found it hard to understand how to get it to work as I think it should.
I was not impressed with what I managed to achieve. I'm sure that must be a criticism of me rather than of Rever.
What I managed to achieve
I created a route of 6 route points.
Curved roads between route points
Shifted order of route points
Saved route.
Exported it as gpx
Loaded into XT2 and into BC.
Issues.
I could not find a way of making route points into Via / Shaping
After deleting a route point and adding a new one, that section of route became a straight line (solved - user error - deselect pen tool)
The gpx file contained the plot of the route and reproduced correctly in BC and on XT2
The route had no intermediate points - only start and finish
All route points plotted in Rever were sent to BC and XT2 as stored Waypoints.
None of the waypoints formed any part of the route.
In the Zumo, if the route recalculated, it lost the route completely and plotted start to finish.
I must be missing something. That can't be it, can it ?
That looks as though it could be a very useful utility.
I had a look at Rever last night and found it hard to understand how to get it to work as I think it should.
I was not impressed with what I managed to achieve. I'm sure that must be a criticism of me rather than of Rever.
What I managed to achieve
I created a route of 6 route points.
Curved roads between route points
Shifted order of route points
Saved route.
Exported it as gpx
Loaded into XT2 and into BC.
Issues.
I could not find a way of making route points into Via / Shaping
After deleting a route point and adding a new one, that section of route became a straight line (solved - user error - deselect pen tool)
The gpx file contained the plot of the route and reproduced correctly in BC and on XT2
The route had no intermediate points - only start and finish
All route points plotted in Rever were sent to BC and XT2 as stored Waypoints.
None of the waypoints formed any part of the route.
In the Zumo, if the route recalculated, it lost the route completely and plotted start to finish.
I must be missing something. That can't be it, can it ?
Have owned Zumo 550, 660 == Now have Zumo XT2, XT, 595, 590, Headache
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC . . . Navigating with Zumo Booklet
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC . . . Navigating with Zumo Booklet
-
smfollen
- Subscriber
- Posts: 90
- Joined: Wed Jan 10, 2024 8:31 pm
- Location: Boston Area
- Has liked: 53 times
- Been liked: 44 times
- Contact:
Re: Using shaping/via points for Rever or Google kml files
So I'm a bit late to this post - sorry I don't look at The Other route planning software thread very often. Apparently I should.
That is my video and my software (Track To Route or Trk2Rt) that @lkraus referred to.
I use Rever regularly for Route planning, partly because of its Butler Motorcycle Maps overlays - sorry the overlays US only I think?
Rever is a good tool even without the overlays.
As the name implies, Trk2Rt is intended to convert a track to a route, more specifically a track exported from Rever or Google my maps.
Rever can export a track and waypoints to a gpx file; Google my maps exports a "linestring" (a track) and "placemarks" (waypoints) to a kml file.
Those waypoints or placemarks are really the points the user originally placed to create a route - that is they are really route points (via and /or shaping points). In both cases, they are exported in route order.
What Trk2Rt does is convert those exported gpx / kml files to useful Garmin style routes in gpx files. The waypoints become via points and, optionally, a few intermediate track points can become shaping points. The youtube video, or the documentation packaged with the [free] software, explain further. https://drive.google.com/file/d/15Rianz ... drive_link
What @jfheath ran into is what happens when Rever exports a route (vs track) and is why I wrote Trk2Rt. Rever's routing algorithm produces nice routes but when it exports a route, it writes only the start and end points into the gpx file as via points. All of the other points are written as route point extensions (aka hidden points). As a result, the route is fine in Basecamp or on a zumo, until it is recalculated. The recalculation uses only the 2 (start and end) via points.
That is my video and my software (Track To Route or Trk2Rt) that @lkraus referred to.
I use Rever regularly for Route planning, partly because of its Butler Motorcycle Maps overlays - sorry the overlays US only I think?
Rever is a good tool even without the overlays.
As the name implies, Trk2Rt is intended to convert a track to a route, more specifically a track exported from Rever or Google my maps.
Rever can export a track and waypoints to a gpx file; Google my maps exports a "linestring" (a track) and "placemarks" (waypoints) to a kml file.
Those waypoints or placemarks are really the points the user originally placed to create a route - that is they are really route points (via and /or shaping points). In both cases, they are exported in route order.
What Trk2Rt does is convert those exported gpx / kml files to useful Garmin style routes in gpx files. The waypoints become via points and, optionally, a few intermediate track points can become shaping points. The youtube video, or the documentation packaged with the [free] software, explain further. https://drive.google.com/file/d/15Rianz ... drive_link
What @jfheath ran into is what happens when Rever exports a route (vs track) and is why I wrote Trk2Rt. Rever's routing algorithm produces nice routes but when it exports a route, it writes only the start and end points into the gpx file as via points. All of the other points are written as route point extensions (aka hidden points). As a result, the route is fine in Basecamp or on a zumo, until it is recalculated. The recalculation uses only the 2 (start and end) via points.