• State Not Answered
  • Replies 15 replies
  • Subscribers 18 subscribers
  • Views 792 views
  • Users 0 members are here
Options
Related

Spreadsheet Upload into a CIQ Field

DaveBrillhart
29 days ago

A rider would like me to write a data field that alerts them to the next Control Point along his route.

He has a spreadsheet that contains data like this....

The ask is simple... provide a running status of the NEXT Control Point simply comparing his currentDistance vs the distance along the route, and show the distance to the Control Point, the Name, and the amenities  (food, gas, etc).

It would be a pain to enter all this into User Settings. I could host a web site I guess and perform a "makeWebRequest" to grab the data, but that looks like it would blow out the small amount of transfer and cause the dreaded -403 status error. I could make multiple web requests... maybe send the current distance and only get back the next few items. Any other suggestions on how a user can make a set of data like this available to a CIQ field? Thanks!

  • 0 28 days ago in reply to peterdedecker

    True - and if we do that I can also hard code the Lat/Long. I would like a general solution so that anyone loading in a Course with Waypoints could have a view with the ETA, Distance, and Name shown. 

  • 0 28 days ago in reply to dpawlyk

    Thanks. The issue with GPS current/target is the straight line result. Generally someone riding a route will stay on the route with possibly brief/short stops for refills or possibly a very short wrong turn then back on. I use the distanceToDestination already and it really has improved in the latest 1050 firmware. There is an OffCourse distance that now works like I would expect it to work - finally - that is a nice indicator when you are off and how far to get back on. So I HOPED that the distanceToNext would work the same way to the next Waypoint in the loaded course.

  • 0 27 days ago in reply to peterdedecker
    peterdedecker said:
    as this is just for 1 specific end user the easiest to me looks to hard code all his points inside

    That could be a trap too. 

    The one user will likely want to be able to change them before and during the trip. 

    Even with hardcoding it, it might not be worth the effort for one person. 

    He’s planning a 29,000 km trip. All the points for that might not fit in a widget. (We don’t even know what device he’s using.) It might be more effort to split it up into separate widgets (which would be harder to use too).

  • 0 27 days ago in reply to DaveBrillhart
    DaveBrillhart said:
    Wait - so the CIQ functions: distanceToNext and nameOfNextPoint don't get those values from the next Waypoint in a loaded course?


    Those will work.

    That info is the course points. But you’ll only get the next one.

    The course points might include the turn instructions. If so, there could be many course points before the one he will be interested in. There’s no way of reading past the next upcoming one. 

    You aren’t going to do much more than the device can already do. He could decode the name himself.

    The course points page will show all of the points ahead.

    These are “course points “ (kinda like but not exactly like “waypoints”). You’ll only get course points from a FIT or TCX file.