pjl wrote:

Joe, is there any other setting than having the course active that would cause the destination to be incorrect?  I have looked and can't find one.  last year all this worked fine and i don't remember any particular bumps to get it active, but I did miss checking track other boats per nick's comment.  Still waiting to hear if there is any way to play this back in order to test operation.  Does Oxley's book deal with any of this?  I don't remember anything, but it has been awhile.

For testing, I go about a couple of different approaches. First, if you have the files you downloaded, clear everything from Expedition, and import them one by one. That should give you a set to test with. The YB Tracking button only automates the download of those files. Otherwise, it is the same import process.

Second, is for a race I didn't compete in, which is already finished. You can use the YB API to pull down XML files back over a specified range of updates. (You can pull the last update, last two updates, etc.). With those, you can build whichever combination you need. It's a bit of work, but valuable for reference. Also, the XML provides COG and SOG from the device, rather than calculated.

I am testing now to see if the built in delay is also reflected in the API data. Will get back later on that, once I have a race I can test with.

definitely going to work on this thought.  i've gotten a long way forward with my understanding as a result of following the CYC Mac race this past weekend.  Definitely want to pull the history per above to have the ability to review the entire BYC race via Exp pos rpts.
Thx for the thoughts, pjl

Nick wrote:

I haven't looked at the API XML files. Would it be any help if I added support for them in Exp?

Good question. I like the API, because I get to manipulate the raw data, as well as control the feed. That said, I still prefer to use the schedules that get published for Expedition purposes. The only reason I would use the API itself, would be if I needed to get the data and the race schedule wasn't working for me. For example, I have used the XML data to pull specific multiple check-ins, whereas the race schedule only pulls the last check-in. I assume this is why Expedition needs multiple schedule updates to plot a track.

I think the real value of the API is the flexibility it offers around the data. I am just not sure how you would integrate that into Expedition, while retaining the same level of flexibility. That isn't really an application issue, but rather a difference between raw data and interpreted data. That said, I would be interested in seeing what you would develop from the data. /grin

Here is a link to the API Integration Notes:
http://cdn.yb.tl/docs/Yellowbrick%20XML%20API%20Notes.pdf

If you click the 'View all' button, does your boat show in the list?

Do you have your boat selected to be able to be plotted in Exp's boats interface?

Last edited by Nick (5/02/2018 6:01 pm)

If you click the 'View all' button, does your boat show in the list?