We’ve made some changes to the download process to extend the range of PointType names used in downloaded Course files. Let us know how you get on. My only concern is whether this might adversely affect people with devices that don’t recognise the full range of PointTypes, so if it does create a problem we may have to roll back the changes, but from tests we’ve done it seems to be OK.
The PointType we select will now be one of the following:
Depending on the turn type....
Depending on the symbol type...
For the other symbols in the list Peter provided there aren’t really corresponding symbols in the symbol set we use, but I think these are probably less important anyway.
Hope that all helps!
John
Thanks for the quick update John!
I now understand what you mean by conflict between turn arrow and the symbol. From a quick test, it looks like if I've got an arrow selected, the pointtype will always be a turn of some kind. If the arrow is "none", I can use one of the other symbols. Correct?
Certainly looks good from that test and reading the .tcx created - I'll transfer over to the Edge810 and report back on device behaviour, but no reason why it shouldn't work.
Becuase not all the plotaroute symbols map to a pointtype, it would be handy if there was a subtle indicator of valid selections. A different border shade in the picker, perhaps? Not important, just handy.
For anyone testing this, note you can't use the mobile Garmin Connect app (on android at least) to transfer coursepoints (including pointtype detail) - you'll get the route as usual, but coursepoints are not included. Download on PC and transfer to the device using a cable.
Great that you did some quick work on this.
There are some problems in the fit file, though. Sended you a mail with more detailed info.
There do appear to be some issues with this so we've rolled back the changes for now while we investigate further. It seems that TCX files don't support the range of PointTypes that are supported by FIT files, so this complicates things.
John
I think we've got to the bottom of this now! We've made some more changes that should enable the use of course point types in FIT files that aren't supported in TCX files, so this includes:
We've also added support for the following course point types in both TCX and FIT files:
Where a coursepoint has both a turn and one of the supported symbols, the point type for the turn will be used.
Have a try and let us know how you get on.
John
Tested this and it's working great. Thanks a lot.
A belated "works well, thanks!"
Can I flag again that it would be helpful if it was obvious from the symbol-picker popup which plotaroute symbols mapped to a valid coursepoint type? Either a different border, or an asterisk, or some kind of filter?
I know that's a very niche request, but so was this entire thread, so thought I'd chance my arm :)
Thanks Rob, it might be something we can add in a future update. My only concern is that flagging certain symbols in this way might cause confusion, as not everybody creates routes to download to TCX or FIT files.
John
Add a Waypoint precisely located on top of existing trackpoint by the Flag Icon.
@ tcx course export I expect the PointType "Generic".
But Plotaroute generates PointType "Straight".
(For manual adding a "Straight" = use turn Arrow Up).
Thanks Willy - we'll look into this.