Routes and Marks
Information about
routes and marks is accessed through the "Tools→Route Manager" window.
From the Route
Manager, you can also modify the options for each route: Tools→Route
Manager→right-click on a route→Route
Options. The most important options are the start time of the route and the
polar data file.
The Route Manager
lists the routes and their lengths in nautical miles. In addition, if wind data has been loaded
that covers the start time for the route, then the estimated time of arrival
(ETA) at the last route point is displayed, and the corrected handicap time enroute (ETE) is shown.
The handicap formula can be modified from the options window. The handicap formula is any formula using two
variables, "$time" and "$dist". The former refers to the uncorrected ETE (in
decimal hours) and the latter the distance in nautical miles. So for a distance handicap formula given by,
say, +1/2 a minute per nautical mile, your corrected time formula would be
"$time + (0.5/60)*$dist", giving corrected time in hours.
You may choose to see
detailed information for each route, by double-clicking on a route in the list,
or using the "details" button.
This gives heading, time, distance and more info for each leg of the
course.
In the route details
window, GC Course means the initial course if the leg is to be sailed as a
great circle. The GC course will change
as you progress along the leg, but presumably you are using a GPS to sail the
course, and the GPS will automatically adjust.
"Rhumb course" means the constant
course you would use to sail that leg along the rhumb
line. The rhumb
line is the straight line drawn on a Mercator projection chart. (Pre-GPS, a navigator would divide a great
circle course into a sequence of short constant-heading rhumbline legs.)
Additional route
options:
- Visible: if
unchecked, the route will not be displayed.
- Nondestructive:
if checked, optimization will create a new route. If unchecked, it will overwrite the old
route.
Making a Route Point Refer to a Mark
You can make a route
point be located at a mark by entering Edit
mode, right-clicking on the route point, and
changing the mark field to be the desired mark.
This is called a mark reference. The advantage of a mark reference is that if
the mark is moved, then all route points that reference that waypoint will also
be moved. Also, if itճ a course mark, you donմ
need to keep typing in the coordinates, or carefully moving the point on the
chart. Just edit the point to set the
mark reference, and it instantaneously moves to the markճ location.
Importing Position Reports
Race committees often
provide the positions of all competitors by email. BLUEWATER
has a function to import these reports and append the positions to existing
routes. For example, here is a position
report for competitors in division 2 of the 2007 Transpac race.
From: "Dave
Lee" <dlee@w6zl.com>
To: wdc3829,
undisclosed-recipients:
Subject: Transpac
Daily Position Report
Date: 23 Jul 2007 16:57:00 -0000
Follows 0600 positions as taken at
0800 SSB roll call by Alaska Eagle
2A,HOLUA,97656,7/23/2007
06:00,22.5667,-145.2833
2B,HUGOBOSS II,GBR 3055L,7/23/2007
06:00,24.3167,-146.0167
2C,LUCKY,USA 52152,7/23/2007
06:00,23.6333,-143.5167
2D,MORNING LIGHT,USA
52007,7/23/2007 06:00,22.5333,-145.3667
2E,PEGASUS OP-50,101,7/23/2007
06:00,24.0167,-145.3833
2F,SAMBA PA TI,USA13131,7/23/2007
06:00,22.1833,-145.3833
AE,ALASKA EAGLE,US 59707,7/23/2007
06:00,22.4333,-155.6833
ANNA KATARINA has retired, motor
sailing to Honolulu
If you wish to discontinue
receiving this daily report, send an email to dlee@w6zl.com with REMOVE in the
subject line.
Suppose you are
sailing on HOLUA and you are keeping track of your competitors in division
2. You have created routes for HUGOBOSS II, LUCKY, etc. that mark their daily positions up till
now. You want to include the July 23
positions.
Select File→Import Positions. You will be asked for an import file, an import field specification, and the import field separator character(s). The import specification describes the layout of a position data, such as in this line:
2A,HOLUA,97656,7/23/2007 06:00,22.5667,-145.2833
The fields necessary
for Bluewater are the route ID (which should match the name of an
existing route in your race), the latitude, longitude, and the date-time
fields. All other fields in the line are
junk. The import specification is a list
of keywords taken from the set:
id, date,
time, datetime, lat, lon,
latu, lonu,
junk.
So for Transpac 2007 position reports, the import spec
reads:
"junk id junk datetime
lat lon".
The
field separator character is ",".
Ҽspan class=SpellE>datetimeӠrefers to a field in which the date and time
are combined, as in the above example. Ҽspan class=SpellE>latuӼ/span>
and Ҽspan class=SpellE>lonuӼ/span>
refer to latitude and longitude values in the special format Ҽspan class=SpellE>dd:mmsssӮ
The position file is
scanned, and any line that does not look like a position report line (e.g. mail header line) is ignored. For any ID that can be matched to a loaded
route, the position is appended to the route.
For unmatched IDs, you are offered a choice of creating a new route with
that ID, or ignoring them.
The import function
can only handle positions that are provided as a single line of text fields
separated by some consistent characters (such as commas, spaces, or tabs). The scanning is not guaranteed to be perfect,
and you may need to delete email headers etc. before trying to import. But the above example imports just fine so
with any luck you'll be mostly okay.
You can add a default import file spec via the preferences, Tools→Preferences.
If the import file
contains multiple positions with the same id, then each successive position is
added in order to the end of the route.
This gives yet another way to create a route -- simply write a little
text file of positions with the same route id, and then import it.
Yellowbrick Position Reports
Yellowbrick trackers are often used on offshore or coastal yacht races. Yellowbrick makes position reports available for download on their website as small text files. When Bluewater is connected to the internet, File→Import Positions→Yellowbrick will download the most recent positions stored at Yellowbrick and load them into the program in the same way as position reports described above.
The Yellowbrick download is controlled via Tools→Preferences. The details of how to get the
data are generally provided by the race committee. Each race monitored by Yellowbrick trackers is given a race identifier on their
website, for example “fastnet2021”. This
should be entered into the Yellowbrick
preferences. The URL for the Yellowbrick website should also be entered. Currently it is
http://yb.tl
The positions can be downloaded in two ways: from the Expedition format
files, which is simpler and may be more reliable but will give you information about
all competitors, or from the individual text files created by Yellowbrick for each division. To use Expedition data, mark the checkbox. Here is a snapshot of the available files for
the 2021 Fastnet race, located at:
https://yb.tl/Links/fastnet2021
Text
Leaderboard (all classes) |
|
Text
Leaderboard (Line Honours Monohull only) |
|
Text
Leaderboard (Line Honours Multihull only) |
|
Text
Leaderboard (IRC Overall only) |
|
Text
Leaderboard (IRC Zero only) |
|
Text
Leaderboard (IRC 1 only) |
|
Text
Leaderboard (IRC 2 only) |
|
Text
Leaderboard (IRC 3 only) |
|
Text
Leaderboard (IRC 4 only) |
|
Text
Leaderboard (IRC 2H only) |
|
Text
Leaderboard (Open Multihull only) |
|
Text
Leaderboard (Class40 only) |
|
Text
Leaderboard (MOCRA Multihull only) |
|
Text
Leaderboard (IMOCA 60 only) |
|
Text
Leaderboard (Figaro III only) |