• State Not Answered
  • Replies 2 replies
  • Subscribers 17 subscribers
  • Views 150 views
  • Users 0 members are here
Options
Related

Accessing Saved Waypoints from a Connect IQ Data Field on Edge 1040

Fohnbit

Hi everyone,

I am building a Connect IQ data field for Garmin Edge 1040 and I am trying to understand whether saved waypoints can be read directly inside a data field app.

My use case:

  • I want to alert the rider when approaching refill points.
  • Refill points are saved as waypoints on the device.
  • In my data field, Activity.Info.nameOfNextPoint and distanceToNextPoint mostly return the next turn instruction, not the saved waypoint I expect.
  • I can see saved waypoints elsewhere in the Edge UI, but I cannot reliably access them as “next relevant waypoint” from the data field.

What I tested:

  • Activity.Info:
    • nameOfNextPoint
    • distanceToNextPoint
    • nameOfDestination
    • distanceToDestination
  • PersistedContent classes (Waypoint/Route/Course), but in this context I only found metadata-level access (name/id/intent), not a clear way to get usable waypoint coordinates/list for my data field logic.

Questions:

  1. Is it currently possible for a data field to read saved waypoints (including location) from device storage?
  2. Is there any supported API path to access course points/waypoints (not just next turn text) in a data field?
  3. If not, is this a known limitation on Edge devices, and is there a recommended workaround?

Any guidance or confirmation from Garmin team or developers who solved similar use cases would be very helpful.

Thanks!

  • 0

    Since there are different interpretations of the names of points on the map or along the route, here is my take:

    Waypoints are points on the map that represent points of interest for the user. However, they are generally not located on the planned route but in its vicinity—such as castle ruins, restaurants, museums, etc.

    Course points are always located on the planned route. They can be similar to waypoints, especially for food, water, etc., but they can also be turn points generated by Garmin.

    A route can therefore contain both when the turn-by-turn setting is enabled.

    And this is where the problem lies for CIQ data fields.
    There is only an API for “next point.”

    If turn-by-turn is active, the turn points are displayed.

    If turn-by-turn is deactivated, the created course points are displayed.

     

  • 0 in reply to mcinner1

    Thank you. Yes, this appears to be a limitation in how course points are exposed to Connect IQ data fields.

    On the Edge device itself, the course points are shown correctly in Garmin’s waypoint/course-point list. However, from a data field, we can only access the “next point” API, which is not reliable for this use case (especially with turn-by-turn enabled).

    It also seems that building a separate Edge app does not solve the issue, because app-to-data-field data sharing is not practically available in a way that helps here.

    As a workaround, I now download refill points via HTTP and calculate distances directly on the device. This works reliably, but it is less convenient than having proper native access to the route/course-point data.