Manual Coursepoint Editing

Posts for this topic...

---

• Post your comments.... Sign In to Post
• plotaroute admin   Thursday 15 Aug 2019 15:41:56

  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:

  • Slight Left
  • Sharp Left
  • Slight Right
  • Sharp Right
  • U Turn

  We've also added support for the following course point types in both TCX and FIT files:

  • Summit (plotaroute Mountain symbol)
  • Water (plotaroute Drinking Water symbol)
  • Food (plotaroute Food symbol)
  • Danger (plotaroute Warning symbol)
  • First Aid (plotaroute First Aid or Ambulance symbols)
  • Sprint ((plotaroute Runners symbol)

  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 

   

• plotaroute admin   Monday 29 Jul 2019 14:44:55

  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

   

• Peter Höglund Monday 29 Jul 2019 13:40:39

  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.

• Rob Williams Monday 29 Jul 2019 12:58:57

  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.

• plotaroute admin   Monday 29 Jul 2019 09:21:55

  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....

  • Straight
  • SlightRight
  • Right
  • SharpRight
  • UTurn
  • SharpLeft
  • Left
  • SlightLeft

   

  Depending on the symbol type...

  • Summit
  • Water
  • Food
  • Danger (Warning triangle symbol)
  • FirstAid (First Aid or Ambulance symbols)
  • Sprint (Runners symbol)
  • Generic (anything else)

   

  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

   

• Rob Williams Friday 26 Jul 2019 14:20:11

  Thanks John, sounds good. And thanks Peter for that list!

  The turn/symbol conflict is probably unlikely in actual use? I can think of two use cases for someone manually adding in CoursePoints:

  1. The user is entering all direction and additional information in the form of coursepoints, and does not intent to use build-in turn-by-turn guidance from the device.
  2. The users is adding additional information only, and will use the devices turn-by-turn

  If 2, the coursepoints manually added will only be symbols.

  If 1, the user is unlikely to want to try and combine a turning with a symbol becuase Garmin devices at least couldn't cope with it - they only access a single symbol per coursepoint. When I used this approach, on the very rare occassions it was necessary I'd set the symbol ahead of the turn, eg:

  • -100m: WARNING "Cttl grd after turn"
  • -10m: RIGHT TURN "RT Green Ln"
  • 0m, the actual turn, which didn't take a course point.
  • 10m, the cattle grid, ditto.
• Peter Höglund Wednesday 24 Jul 2019 12:53:53

  Thanks, looking great that its in the plan.

  One thing I would like to add to this is like in gpx download, it could be possible to choose poi, directions or both.

• plotaroute admin   Wednesday 24 Jul 2019 09:54:14

  We did made a change a little while ago to extend the range of symbols for waypoints in GPX files (to select the symbol type based on any symbols that have been added to the directions or the map) but we didn't apply this change to TCX/FIT course downloads for some reason.  I can't recall why this was (possibly uncertainty about how this might affect devices that don't support the full range of PointTypes) but we can have another look into it.  At present the PointType for course files is either:

  Straight
  Left
  Right
  Generic

  It should be easy for us to extend this to include other turns (e.g. Slight Left, Sharp Left) and we could also set the PointType to something else on the list Peter has provided if a corresponding symbol from our symbol set has been added to the route directions. If the direction has both a turn and a symbol, the PointType would probably have to be based on the turn. It's possible that our TCX to FIT convertor would would need amending to support this, so that may have a bearing on how soon we can make the changes, but we'll look into it.

  John

• Peter Höglund Wednesday 24 Jul 2019 07:04:35

  At least for fit files the complete list of course point types are availible in ant fit sdk and I'm also really interested in this as I think is noted:)

  •         Generic = 0,
  •         Summit = 1,
  •         Valley = 2,
  •         Water = 3,
  •         Food = 4,
  •         Danger = 5,
  •         Left = 6,
  •         Right = 7,
  •         Straight = 8,
  •         FirstAid = 9,
  •         FourthCategory = 10,
  •         ThirdCategory = 11,
  •         SecondCategory = 12,
  •         FirstCategory = 13,
  •         HorsCategory = 14,
  •         Sprint = 15,
  •         LeftFork = 16,
  •         RightFork = 17,
  •         MiddleFork = 18,
  •         SlightLeft = 19,
  •         SharpLeft = 20,
  •         SlightRight = 21,
  •         SharpRight = 22,
  •         UTurn = 23,
  •         SegmentStart = 24,
  •         SegmentEnd = 25,
• Rob Williams Tuesday 23 Jul 2019 23:13:31

  Sorry to resurrect this - is the ability to set the PointType of a CoursePoint in the development backlog somewhere? Would be really helpful, although I admit is only likely to be of interest to a very small subset of users! :)

  Specifically:

  plotaroute creates CoursePoints in this format for tcx export:

  <CoursePoint>

    <Name>CRTL2</Name>

    <Time>2019-07-23T00:22:57Z</Time>

    <Position>

        <LatitudeDegrees>55.758773</LatitudeDegrees>

        <LongitudeDegrees>-4.436865</LongitudeDegrees>

    </Position>

    <PointType>Generic</PointType>

    <Notes>CRTL2</Notes>

  </CoursePoint>

   

  PointType is being set by the "Turn Arrow" options within the Add Directions menu. Options I think are left, right, and everything else maps to generic. Garmin Edge devices at least can display handy information using a range of other PointTypes, including Summit as Colin mentions below, food, water, danger (handy for cattle grids and main road crossings!), etc. (Annoyingly I can't find a full list anywhere, although happy to work one out if that would help).

  Ideally other PointTypes would be available within the Turn Arrow popup.

  Workaround is to set everything to Generic and use the name , but it's not quite as neat.