TripManager support GPX Files from Kurviger also

[proofresistant]

We have already encountered the BC import problem with GPX when using <trp:AdventurousLevel>Adventurous</trp:AdventurousLevel> in another thread.
This also happens with Adventurous attributes for routes exported from the XT2, Tread 2, or Tread app with Adventurous profiles.

Background information:
The problem is not the <trp:AdventurousLevel> itself, but rather the corresponding lack of structure in the GPX header. In any case, BC refuses to import the file; BC is very strict in this regard.

It may help to deselect “Embedded Garmin route points,” which will omit <trp:AdventurousLevel>.
“Embedded Garmin route points” are probably not needed anyway, as the route has to be recalculated. Alternatively, the track can be exported as well.

[Peobody]

It may help to deselect “Embedded Garmin route points,” which will omit <trp:AdventurousLevel>.

I had thought this is what was causing the BC import errors so just did two test exports as file .GPX, one with embedded points and one without. Both imported into Basecamp. I then did two more exports as device=XT but with embedded route points in one and not the other. This revealed that the combination of device=XT AND embedded Garmin route points is what causes the import error in BC. There are a number of route variances between Kurviger and BC but that is not surprising. FWIW, my last set of test exports had additional waypoints enabled at intervals of 25 mi.

[proofresistant]

By the way, we had discussed this AdventurousLevel Tread App export / BC import issue in the following post:
Adventure tours exported from the Tread App cannot be imported into BaseCamp
Thanks again @0709 for the really relevant tips.

[Peobody]

Another observation related to Kurviger export and the XT is that the XT accurately reproduced the route of an export done as .GPX with embedded Garmin route points. So, in my limited testing, the combination of .GPX with embedded both imported to BC and produced an accurate reproduction on the XT (not in BC though). Unfortunately, the fact that there are no route point POI names or details makes the route impractical to use.

[proofresistant]

You can give the waypoints (though perhaps not the POIs) a name and export them, at least with GPX Advanced.
Or not?

[Peobody]

You can give the waypoints (though perhaps not the POIs) a name and export them, at least with GPX Advanced.

Renaming the waypoints in Kurviger before exporting showed some promise. This was the start, end, and an interim waypoint.
In BC, the new names are what showed in the "Via Point Name" column of the route details window.
On the XT, the start and interim waypoint showed the new names however the end point named "Dairi-O Asheboro" was named "Area" on the XT.

Code: Select all

		<rtept lat="35.68737" lon="-79.82129">
			<name>DairiO Asheboro</name>
			<sym>Flag, Red</sym>
			<type>destination</type>
			<extensions>
				<trp:ViaPoint/>
			</extensions>
		</rtept>

Maybe this is one of those situations where the XT changes a route point name, something I have read about but not experienced. Regardless, I apologize for hijacking this discussion, turning it into a tutorial on how to use Kurviger. I am really impressed by its ease of use, but trying to determine whether it could be good fit for me should be a separate discussion, one that I will start if I choose to pursue it further.

[proofresistant]

Regardless, I apologize for hijacking this discussion, turning it into a tutorial on how to use Kurviger.

You didn't take over the discussion, but contributed constructively to it!

I am also positively surprised by Kurviger. Actually, I just wanted to test what happens when TM is supplied from other sources.

I will have to find out for myself too, how much I will ultimately use it.