Schlagwörter: Garmin Basecamp GPX
Juni 2, 2017 um 03:13 #17458
I don’t know if this is an Orux issue or theme issue. I am using Orux for bike navigation and usually import the route in GPX/KML format for offline navigation.
On several occasions I have run into rendering issues with GPX files generated by Garmin’s Basecamp software. The issues that I am seeing are missing parts of the track and with the parts of the track that are present the track goes point-to-point from waypoint to waypoint instead of following the roads.
I am leaving tomorrow for a 3-day bike overnight and will attach the Basecamp GPX that shows the issue. I will also attach a KML that was generated by Google maps that displays correctly (that I can tell) in Orux. You will need the maps installed for North Carolina and Virginia to view it.
I have also taken the GPX file that fails in Orux and imported it into GPS visualizer (.com) and it displays properly. So it would appear that there is some incompatibility with Garmin Basecamp GPX files.
Anhänge:Juni 3, 2017 um 13:48 #17484ChristianKVerwalter
I’m pretty shure that this is an issue with the garmin GPX-Format and Ourx.
(It cant be an issue with maps).
I imported your GPX to QV and it shows well (3 seperate tracks in one file) – see screenshot.
Then I exported the Tracks in plain GPX10 format (attached), give this GPX a try in Orux.
There are several GPX converters out there like GPSBabel if I remember right.
Anhänge:Juni 5, 2017 um 16:42 #17523
Thanks for your converted file. I loaded it into Orux and although it is much better there are still a couple of issues. First, there are no waypoints as were present in the original GPX file. I don’t know if CV removed them or has its own issues with Garmin files. Second, although the tracks now look contiguous there are still several instances (through Franklinton and south of Stovall) where the track deviates from roads for considerable distances and is connected with straight lines, same as in the original Basecamp file on Orux.
So, It looks like these are Orux issues? I have left a note on the Orux bug forum but have not heard anything in about a week. Jose must be on holiday!
SteveJuni 5, 2017 um 19:32 #17529ChristianKVerwalter
where the track deviates from roads for considerable distances and is connected with straight lines
Thats an issue by design for GPX Tracks.
If you want a track without those straight lines you (or Basecamp during export) have to add numerous points in between the given points.
Orux (and all other APPs) are only able to display the given points by the GPX and connect these points by lines.
So look if its possible to configure basecamp for a higher point density or chose another Routing-Software.
And: The maps for creating Routes/Tracks have to be the same as for display on Smartphone. So you can use basecamp but with maps based on OSM otherwise you will have Tracks out of road/paths cause the maps differ.
And even if the same database is used (OpenStreetMap) there may different simplification algorithms for Mapsforge(OAM/Orux) and Garmin/IMG.
ChristianJuni 5, 2017 um 20:45 #17535
Thanks for your feedback. I do realize that track points are (or should be) connected with straight lines by whatever app is reading/interpreting them. However, I don’t believe that this is the display issue that I am seeing and that somehow increasing point density is going to solve it. I think the points are already there and Orux (and maybe QV – I have no way of checking) is having difficulty in properly interpreting them or just dropping them. The app appears to be just ignoring/dropping points for upwards of several miles. Point density won’t fix this.
I know what you are saying about different map sources. This effect shows up vividly in Ride With GPS when switching from OSM maps to Google Maps. I have not found this to be a big deal when navigating. The maps are close enough that the correct route is pretty obvious.
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.