Quote from Guido on 28.08.2022, 07:30

Yes. It’s on the list to add time stamp and altitude to GPX.

Quote from massi on 23.09.2022, 06:03

Hi Guido,

thanks for putting elevation tag to the scenic GPX export!

Unfortunately it does not work with Garmins Basecamp, I tested it with several GPX exports from scenic, but it says always, that it's not a regular GPX file and could not be opened, or does this only work for newly created tracks?

Other Applications like Google Earth or mytracks have no problems to load these files.

 

Regards

Marc-Antón

Quote from Guido on 23.09.2022, 06:30

Hmmm. I did not check with Basecamp. Let me try a few things today and see what’s happening.

Quote from Guido on 23.09.2022, 06:55

Did a quick check on my phone. It does import into the Garmin iOS apps (at least on my). I suspect this is an issue with basecamp, but will try it on my desktop once I’m behind my desk.

Quote from massi on 23.09.2022, 08:33

Sorry for not telling you, I had the problem with the desktop app, I did not test the iOS Apps, because I have not installed them on my phone.

Quote from Guido on 23.09.2022, 09:01

So, I did some tests. Indeed Basecamp is not importing the GPX because it contains the elevation data. When I remove the elevation tags, it imports fine. This is definitely a bug in Basecamp!

I've run the GPX through several GPX validation tools and successfully imported it into several other websites and apps. The elevation tag <ele> is a standard GPX element that should be supported by all GPX tools. Even if Garmin does not use the <ele> element, it should at least ignore it and import the GPX successfully.

Honestly, I don't feel like removing the elevation because of this. I could make it optional in a future version of Scenic, but still seems like a lot of trouble while the problem lies with Garmin Basecamp. Perhaps you could try contacting Garmin support about this?

There is a workaround for the moment. Two actually:

1) Open the GPX in a text editor and remove all lines containing <ele>. If your text editor support RegEx (regular expressions) this is pretty easy. Find ^.*<ele>.*$ and replace it with nothing. I use BBEdit (https://www.barebones.com/products/bbedit/). The free version will do this and it's available for Windows and Mac.

2) Convert the GPX to a new GPX using GPSVisualiser website: https://www.gpsvisualizer.com/convert_input Simply select GPX as output format and click the choose files button to upload the Scenic GPX. This will create a new GPX from it without elevation tags.

I prefer option 1, because GPXVisualiser makes some other changes to the GPX as well.

Sorry to disappoint, but hope this helps at least.

Quote from massi on 23.09.2022, 10:45

Thanks Guido, maybe it's a bug in Basecamp, but I think I've found a workaround that you may implement easily to scenic.

I did the following, exported a (Non-Scenic-)Track from Basecamp which includes elevation information.

And reimported it to basecamp, there was no error message, it was imported without a problem.

The information in the GPX file I've exported from basecamp looks like this:

"<trkpt lat="50.53432272747159" lon="7.120239157229662">
<ele>218</ele>
<time>2020-08-04T09:55:05Z</time>
</trkpt> ...

"

The track exported from scenic looks like this

"<trkseg>
<trkpt lat="50.267550" lon="7.153813">
<time>2022-09-08T16:13:26.770Z</time>
<ele>514</ele>
</trkpt> ...

"

I don't see there any differences, except that the positions of <time> and <ele> are reversed.

So I made a test and reversed <time> and <ele> tag lines in the scenic track with BBEdit and it loads without a problem to Basecamp.

 

Regards

Marc-Antón

Quote from Guido on 23.09.2022, 12:55

Hi Marc-Anton,

That's awesome! Thank you for this analysis. I've changed the order and it works now! I was assuming the order did not matter, but obviously, it does.

It already works if you download the GPX through the share link (you do need to re-create the share link from the iOS app). And I'll make sure this change will also be in the iOS app (for the 'export GPX' button) for the next update!

Thanks again!
Best regards,
Guido

Quote from massi on 23.09.2022, 14:16

Hi Guido,

I'm glad I could help! And I'm happy that it works with the share link, thank you!

Best regards,

Marc-Antón

 

Quote from massi on 10.10.2022, 12:05

Thanks for fixing it in the new version, works perfectly!

Quote from Trashhauler on 18.10.2022, 02:56

Hi Guido

When importing to Basecamp the file is adding two start and two finishes. I thought it was only Basecamp but it also occurring with the Harley GPS app. I thought this was fixed previously but the glitch seems to have returned following the last update as it imported into Basecamp prior to the update but now it has the double start and finish problem again.

Thoughts or tips?

Roger

Quote from Guido on 18.10.2022, 06:38

Hi Roger,

If you export a route from Scenic to GPX file, the GPX contains:

- All the stops in the route as waypoints

- A track of the route

- Two versions of the route

Could it be that you are just seeing the two routes overlapping? Or Althea route start overlapping with the waypoints?

I don’t know about the Harley app, but in Garmin Basecamp you can select which elements to show on the map.

Let me know how it goes? If unclear, could you paste some screenshots of Garmin Basecamp here so that I can see what you are referring to exactly?

 

Best regards,

Guido

Quote from Trashhauler on 18.10.2022, 14:30

Thanks Guido - now I understand