Posts for this topic...
-
Post your comments.... Sign In to Post
-
Willy Van Driessche Wednesday 22 Jun 2022 19:51:38
Opening Wr160b_11pts.gpx
1 waypoints
0 routes (0 points))
1 tracks (307 points in 1 track segments)
TGPX
Track Segment #1 (307 points)
14.7 km / 3:59:29 = 3.7 km/h
Remove duplicates:
Track Segment #1 (295 points)
14.7 km / 3:59:29 = 3.7 km/h
#
Opening Wr160c_Aps_Only.gpx
1 waypoints
0 routes (0 points))
1 tracks (297 points in 1 track segments)
TGPX
Track Segment #1 (297 points)
14.7 km / 3:59:30 = 3.7 km/h
Remove duplicates:
Track Segment #1 (297 points)
14.7 km / 3:59:30 = 3.7 km/h
#
Opening Wr160Traced.gpx
1 waypoints
0 routes (0 points))
1 tracks (339 points in 1 track segments)
TGPX
Track Segment #1 (339 points)
14.7 km / 2:56:18 = 5.0 km/h
Remove duplicates:
Track Segment #1 (312 points)
14.7 km / 2:56:18 = 5.0 km/h
-
Jim O''''Dwyer Wednesday 22 Jun 2022 20:48:31
Thanks for your detailed analysis Willy.
Your counts, give or take a point, mirror mine and appear to confirm duplicates in one file and none in the other.
Was that a manual exercise on your part (incliuding the removal of the duplicates)?
Mark - have a great trip around Ireland - my part of the world (obviously).
Yes, the routes will appear identical when shown on the map but if you look at the gpx file in a text editor you can locate the duplicates by checking the location co-ordinates of the trkpts. I also upload them to basecamp where they are easier to spot visually.
I downloaded your traced route and scanned the gpx data - there are in excess of 20 duplicates there. I suspect the number will reflect the number of times you clicked in tracing the route.
-
Willy Van Driessche Wednesday 22 Jun 2022 21:27:44
@ Jim.
You can analyse and solve that very quickle by the freeware gpx editor.
In the left down panel you find the anaylyse window. (Copy paste text)
(See also the you tube video) https://t.ly/-2M0
This issue anyway is caused by the GH engine.
A design by GH online.
https://t.ly/7252
Tap gpx for download.
Opening GraphHopper.gpx
6 waypoints.
0 routes (0 points)
1 tracks (55 points in 1 track segments)
TGPX
Waypoint list
Track Segment #1 (55 points)
3.6 km / 0:14:31 = 14.9 km/h
Remove duplicates.
Track Segment #1 (51 points)
3.6 km / 0:14:31 = 14.9 km/h
-
Jim O''''Dwyer Wednesday 22 Jun 2022 23:14:15
Willy - thanks for those links.
I have found that editor and used it to remove duplicates.
Yet another viable workaround.
Jim
-
Mark Worthington Thursday 23 Jun 2022 16:19:10
Yes, Jim, it would have me about 20 clicks to copy the route.
In practice, the presence of these duplicate points does not seem to affect the usefulness of a plotted route. I have cycled thousands of miles following routes I created in PR with no issues at all.
Does it causes you a problem, Jim, or is it something you noticed and are seeking to understand?
So a question for Admin, then; is this a bug albeit one with (maybe) no visible impact?
On the ferry to Dublin, as I type!
Mark
-
Jim O''''Dwyer Thursday 23 Jun 2022 18:40:39
You are correct on all counts Mark. And it doesn't impact on my gps nor Fenix in the field. So from a practical perspective it has no navigational impact
And now that I have at least two viable workarounds to remove the duplicates I can still process the gpx data to produce my custom routecard.
So yes, a curiousity that Admin might want to look at sometime in the interests of consistency of outcomes for the product. That is, plotting a route by progressively extending it from the start point to the eventual finish point produces a different gpx download from one arrived at by reshaping an autoplotted route between the start point and the finish point - with the latter producing the'cleaner' gpx file.
So thanks to both you and Willy for your interest and insights and I guess we can leave it at that
Jim
-
Mark Worthington Sunday 03 Jul 2022 16:20:40
It seems to me that this is just the result of how the routing algorthim works. You select teh start and then the 1st point, and it calculates a route from the start to that point. When you click the next point, it does not want/need to recalculate teh entire route from the start, so it sets a new "start" as the finish if the first (last) section and the end as the last point, and auto-routes that section. In an ideal world, it would remove the extra point, but the process might incur some penalties that are just not worth the effort.
When using the auto-router point by point, what we may think of as a single resultant route is just a combination of many individual sections.
All the apps/devices I’ve used seem to manage this with no issues.
Regards
Mark
-
Jim O''''Dwyer Sunday 03 Jul 2022 17:09:08
Thanks for that additional clarification Mark. Much appreciated.
I totally get and accept that explanation and we can close it there.
Jim
