Greg Rice's Rally Bonus Planner β€” Help

← Back to app

The web-based Rally Bonus Planner is / will be a replacement for my Rally Planning spreadsheet that I first started working on back in 2013. Hundreds of rally riders over the years have used my spreadsheet for many different rallies including the Iron Butt Rally. Many top ten riders of past Iron Butt Rallies have also used my spreadsheet. All of the functionality from the spreadsheet will be implemented in the new web-based Rally Planning app. With the new web-based app you will be able to build out and format the the bonus names and then export the bonus list to a GPX file or and Excel spreadsheet. You will start by entering a bonus name for a long-distance motorcycle rally: enter or import bonus locations for each leg, look up their address, timezone, sunrise/sunset and 10-day weather automatically, see them plotted on a map colored by point value, and availability by shape. Export the finished list as GPX file (for a GPS or mapping program) or XLSX (for a spreadsheet).

Benefits of my rally planning web app

I developed the spreadsheet to help me get to routing faster in my mapping programs (now Basecamp), and it has evolved over the past 12 years.

  • Easy to import bonus data, including points files from a rally master, and automatically create a GPX file ready for Basecamp or a GPS.
  • Easy bonus name creation with bonus code, points, and availability.
  • Automatic calculation of time zone, sunrise, and sunset based on latitude and longitude β€” good information for daylight-only bonuses.
  • Easy to tag a bonus's availability: anytime, daylight only, group photo, etc.
  • Easy to tag a bonus as part of a combo bonus.
  • Automatic bonus symbol selection based on points value and bonus availability.
  • Easy to add comments to a bonus that carry through into Basecamp and then your GPS, so you can see them riding up to a bonus.
  • A Google Maps link is created for each bonus location β€” Street View in many cases.
  • Generates a formatted GPX file for Basecamp and/or a GPS that includes comments, sunrise, and sunset times.
  • Fast entry into Basecamp with the generated GPX file, bonus symbols already set by point value and availability. You can also load the GPX file directly onto a GPS.

The page is organized by rally β†’ leg β†’ bonus. A rally is the overall event (e.g. "2027 Iron Butt Rally"). Each rally has one or more legs (the segments between checkpoints). Each leg has a list of bonuses β€” the individual bonus locations worth points that you build a route out of for the rally.

A quick walkthrough of the app β€” signing up, creating a rally and leg, importing bonuses, running lookups, and the map view.
What's new

Recent updates

A running log of what's changed in the app recently, newest first, in plain language rather than developer notes. Nothing here requires you to do anything β€” these are all things that just work differently (or are newly available) the next time you sign in.

November 10, 2026

Seasonal road closures when planning out of season

Planning a summer rally in winter? Roads closed for the season (like a snowed-in mountain pass) used to make Google's check of a whole route fail. Now just that hop is filled from saved road distances or an estimate, and the card says so. See seasonal road closures for what to check before you ride.

Fixes from a code review

The Big Brain's "Without combo bonuses" routes now show every combo they happen to complete, even after being fitted to real roads (they could under-count before). A ⭐ mandatory bonus reached after it closes now waits for its next opening (up to two days) instead of being missed. The printed Route Schedule shows the same total score as Route Info (scoring rules and combos), and the Bonus Book's arrival times line up even when a stop has no coordinates. Importing a GPX route matches codes with dashes (like SB-12) and leaves your Start/End bonus as the route's ends instead of adding it as a stop. Review my route is greyed out while The Big Brain is running.

A tidier toolbar, and daylight saving set automatically

The grid toolbar is now one row with Import, Rally Setup and Export menus and the Route Planner on the right; actions for checked rows appear in a selection bar only when you need them, and your account settings are under your name. A leg's Daylight saving in effect box is now set from its date (it could show unchecked while sunrise/sunset were calculated with daylight saving on β€” an hour late in November); legs with wrong sunrise/sunset times are corrected when you open them.

Import a GPX route, print a bonus book, pace vs. drive time, extra points and late penalties

πŸ“₯ Import GPX Route loads a BaseCamp route as your stop list and offers to review it with The Big Brain. πŸ“– Print Bonus Book prints your bonuses in riding order. Pace vs. drive time plans legs as a percent of Google's drive time. New scoring rules: Extra points (BOLO, photo or call-in bonuses that aren't at a location) and a Late penalty table. Route Info and points-per-mile now use the total score.

🧠 Review my route, and a route check on every card

Built your own route? Review my route checks it on real roads and suggests changes β€” the same order improved, plus reworks β€” each with its points and time. Every Big Brain card now has a Route check: tight timed windows, low-value stops and access to verify.

🧠 Fewer Google requests

The Big Brain now uses the free OpenRouteService for its checks while searching, and Google only for the final routes β€” about 80–90% fewer Google requests per run.

🧠 Think longer searches every direction

Think longer now runs one search for routes heading north from the Start, one east, one south and one west, and shows the 3 best different routes; each card says which way it heads.

🧠 Slow roads take longer; Think longer on every leg

The Big Brain now plans each leg with its real drive time: city and town legs take longer, interstate legs less, averaging out to your speed β€” so a dense city cluster only wins when it really pays. Build Route Schedule does the same after Recalculate Route. Think longer is now offered on every leg, including one-day rallies.

November 9, 2026

🧠 Big Brain cushion, and a better Think longer

A new Big Brain cushion setting on the route screen (default 60 minutes) makes The Big Brain finish its routes at least that long before the deadline. Think longer now runs three complete searches from different starting points and keeps the 3 best different routes, so it can no longer come out worse than Normal.

Mandatory bonuses: the schedule waits for them to open

Arriving early at a ⭐ mandatory Timed bonus now waits as long as it takes (even into a later day it's open), instead of counting as a miss. The Big Brain plans that way too, and if a route reaches a mandatory bonus after it closes, it leaves out bonuses before it so you get there in time.

🧠 The Big Brain plans with real road distances between nearby bonuses

The Big Brain now gets the real road distance between each bonus and its nearest neighbors before it plans (saved for everyone on that rally after the first run), counts ferry crossings in each route's checked finish, and keeps working a fitted route until any missed window is fixed.

November 8, 2026

🧠 The Big Brain's routes now fit on real roads

Routes that came back late after the Google check are now fixed in place: The Big Brain keeps the ride order, leaves out the bonuses that cost the most time for their points, and checks again, so the routes it offers finish on time on real roads. Spare time is used to add bonuses back. Each card says what changed.

Schedules wait for a bonus to open; The Big Brain checks and fixes every route it offers

Reaching a Timed or Daylight-only bonus a little early now means waiting for it to open (up to 4 hours), shown as its own line in the schedule, instead of a missed bonus. 🧠 The Big Brain plans that way too, checks all three routes it offers against real roads, quickly reworks any that real roads make late, and lists the routes that really fit first.

🧠 The Big Brain learns real road distances, and can think longer

Instead of stretching every leg by the same amount after checking with Google, The Big Brain now learns how much longer real roads are for short hops versus long legs, and area by area. It uses the exact distance of every leg it has checked, re-checks after re-planning, and reworks the best route if it would run long. On multi-day or very large legs it also offers Think longer (about 2 minutes) for better routes.

Scoring rules can be copied from another rally or loaded from a shared set

The Scoring Rules… window can now copy the rules from another of your rallies, or load a shared rule set an admin has published, so riders in the same rally don't each have to type the rules in.

Routes can now have up to 150 stops

The limit on stops in one route (including Start and End) went from 50 to 150, so multi-day rallies can be planned with 100 or more bonus stops, and 🧠 The Big Brain can plan routes that long. On a multi-day leg it also searches longer, up to about 30 seconds. Long routes are sent to Google in pieces of about 20 stops, so a 100-stop route costs a few cents to calculate rather than one. Build Route Schedule now uses the road distances from the last Recalculate Route for each stop-to-stop leg. Optimize Route still works with real road distances up to 50 stops and uses straight-line distances above that.

New: Scoring Rules, for rally books that score more than each bonus's points

Some rallies score bonuses in ways beyond their listed points: a bonus that unlocks others, an award for how many of a group you get, a bonus that doubles the next one, meal bonuses. The new Scoring Rules… button lets you enter those rules once per rally. 🧠 The Big Brain then plans for them, and the Route calculated popup shows the route's Rally score with them applied.

🧠 The Big Brain asks how to plan for combo bonuses

When the leg has combo bonuses with points, 🧠 The Big Brain now asks how to plan before it starts: With combos (routes can go out of their way to complete a combo when it's worth it), Without combos (bonuses chosen on their own points), or Show both, which lists the best routes each way and tells you how many points planning for combos is worth.

New help: How PDF import works

A new How PDF import works section explains how a rally book PDF is read, the seven bonus-listing layouts the app recognizes (with a sample of each and the rally book it was built from), what's read from each bonus, how to check the preview, and what to do when a book doesn't import, including a book that has every leg in one PDF.

November 7, 2026

Timed bonuses now use the hours typed in the Timed column

Before, a Timed bonus's hours were only checked by the route tools (🧠 The Big Brain, 🎯 AI Suggested Route and the route schedule) if you'd also set them with the πŸ• next to the Timed column. Now, when the πŸ• hasn't been set, the hours are read straight from the Timed text: 1000-1830, 0900-1700, 10:00am-1:00pm, 10am-1pm and so on, every day of the leg. A πŸ• that's using the Timed text is shown a little brighter, and hovering it shows the hours it read. Text that's more than one plain time range, such as Thu-Fri: 0800-2000 or 1100-1500 Sun, still needs the πŸ• set by hand, and The Big Brain lists those bonuses. Use the πŸ• to limit a window to a single date.

Clearer message when a bonus has no road to it

Some bonuses can't be reached by road at all, such as one on Mackinac Island (no cars allowed) or one whose coordinates are a little off. Before, the route error only said "Could not find routable point … coordinate 3" with raw numbers. Now it names the bonus and explains what to do: if you reach it by ferry or on foot, use that bonus's new β›΄ (below); otherwise remove it from the route. 🧠 The Big Brain now spots these bonuses itself, leaves them out, plans again, and tells you which ones it left out.

New: ferries

Ferries Google knows about are now timed properly. Google already includes car ferries in road routes. Before, the app counted the miles on the boat as if you were riding them at your average speed. Now it uses Google's own crossing time instead, plus a Ferry wait (min) allowance for each crossing, for waiting for a departure and boarding. That's a new box in the Route Planner, default 30 and remembered on this device. The Route calculated popup shows the crossings, the route schedule shows each one as its own β›΄ line, and 🧠 The Big Brain's best route includes them. Google doesn't know departure times for driving routes, so the wait is your allowance; check the ferry schedule for your day.

For ferries or access Google doesn't know about, use the new β›΄ column next to the πŸ• in the grid. Click it on a bonus to set:

  • Route to (lat, lon): where road routing should take you instead of the bonus itself, such as the ferry dock or the parking lot. The bonus keeps its own coordinates on the map and in the GPX.
  • Extra minutes: added to that one stop, for example the ferry both ways plus waiting, a long walk, or a shuttle.

Step-by-step instructions are in Ferries & hard-to-reach bonuses. Road routes, the schedule, Optimize Route, 🎯 AI Suggested Route and 🧠 The Big Brain all use them. The β›΄ only appears on bonuses that have them set (hover it to see what's set). On any other bonus the cell is blank; move the mouse over that row and a faint β›΄ shows where to click.

November 6, 2026

New: 🧠 The Big Brain β€” a stronger route planner that offers you its 3 best routes

Next to 🎯 AI Suggested Route in the Route Planner is a new button, 🧠 The Big Brain. You don't check candidate bonuses first: it looks at every bonus in the leg that has coordinates, tries many different starting ideas (each big bonus forced in first, each combo completed, and so on), keeps improving its best routes for several seconds, then checks the best one against a real Google road route and re-plans if the roads turn out longer than it estimated. It then shows you the three best different routes it found, each with its points, finish time, and what your finish would be if you ride 10% or 15% slower than planned. Click Use this route on the one you like.

New: combos can have a points value

The Combo codes… window now has a Points box on each row (and Paste list… accepts an optional third column with the points). The Big Brain uses it to decide when completing a combo is worth the extra riding. A combo left blank is simply ignored when planning.

October 18, 2026

Road routing switched back to Google, with OpenRouteService as an automatic backup

OpenRouteService, the free routing service the Route Planner had been using, became unreliable: requests would hang with no answer, especially on longer routes. It's also retiring its old web address in early November. Road routes are now calculated by Google first. If Google is ever unavailable, the app quietly falls back to OpenRouteService on its own, and only shows a straight-line estimate if both are down. Routes of up to 19 bonus stops (plus your Start and End) go to Google in a single request; longer ones are split behind the scenes and stitched back together, so you'll never notice.

New: a "Route calculated" summary after Recalculate Route, showing which routing engine was used

Clicking Recalculate Route now pops up a summary once the road route is ready: Stops, Total points, Distance, Est. ride time, the routing service's own driving estimate, Est. finish, Points per mile, and the Routing engine (Google, or OpenRouteService if the backup was needed). The engine also shows in the Route Planner's stats line, e.g. "2312.6 mi (road, Google)", and in the popup you get by clicking the route line on the map.

New: PDF import catches "decoy" text hidden in a rally book

Some rally masters plant text in a bonus book PDF that never shows on screen or on paper (white text, tiny text, or text covered by a shape) to catch riders who machine-read the book. PDF import now checks for that automatically. Any bonus built from hidden text gets a ⚠ in the Flag column, with a warning above the preview. For a deeper check, the new Verify against printed page button in the import window reads each bonus page the way you'd see it printed and flags any bonus whose code, coordinates, or points don't actually appear there. That catches tricks like text hidden under a photo, or numbers whose underlying characters don't match what's printed. It takes a few minutes on a large book. Either way, settle every ⚠ against the printed book.

New: the Rally Bonus Planner has its own logo

Rally Bonus Planner logo: a dotted route leading to a map pinThe app now has a logo: a dotted route leading to a map pin. You'll see it beside the app's name in the header and on the sign-in page, at the top of every popup and window (the Welcome message, "Route calculated", Route Planner, Import, and the rest), and as the icon on your browser tab. If you save the app to your phone's home screen, it uses the logo there too. If your browser tab still shows the old blank icon, a hard refresh (Ctrl+F5, or Cmd+Shift+R on a Mac) picks up the new one.

Fixed: your default motorcycle is now filled in on new routes

A new route draft could open in the Route Planner with Motorcycle set to "None" even though you have a default bike. Your default motorcycle (set in β›½ My Motorcycles) is now filled in automatically, along with its fuel range. Picking a different bike, or "None", for a route still sticks.

Improved: leg Start/End locations are looked up for you when you save

Typing a leg's Start or End address used to need a separate Look up click before it would show on the map or fill in the Route Planner's Start/End. If you skip it, or change the address afterward, Save now looks it up for you. If an address can't be found, you're asked whether to go back and adjust it (adding a city and state usually helps) or save it without a map location. Clearing an address now also clears its old map pin.

September 2, 2026

New: route stats now show your total points, plus a Route Info popup with points-per-mile efficiency

The Route Planner already showed stop count, distance, and estimated ride time β€” now it also shows a live points total in the stats line, the route summary chip, and next to each stop, updating as you add, remove, or reorder stops. A new ℹ️ Route Info button pops up a clean, screenshot-friendly summary β€” Stops, Points, Distance, Riding time, and Points per mile β€” the efficiency number riders and spectators like to compare after a rally. It's also on the printed route schedule now, so it travels with whatever you already save or share.

New: mark a bonus mandatory β€” AI Suggested Route now guarantees it's included

A new ⭐ column in the bonus grid lets you mark a bonus mandatory β€” a plain manual toggle, never set automatically, for the bonuses your rally book or the start rider meeting says you must ride. 🎯 AI Suggested Route now treats every starred bonus as a hard requirement, seeding it into the route first so a 5-point mandatory bonus can no longer get edged out by a 500-point optional one. If a mandatory bonus genuinely can't fit, or has no coordinates on file, you're told clearly instead of finding out from a route that's quietly missing it.

New: AI Suggested Route warns you if a Daylight-only bonus is missing its sunrise/sunset lookup

If any candidate bonus is Daylight-only and its sunrise/sunset was never looked up, AI Suggested Route now warns you before the search even runs β€” naming the bonuses, so you can cancel and run Look up selected/missing first, or continue knowing the search will treat them as unrestricted. The completion popup also flags the total number of schedule warnings, so a missed daylight window is never something you'd only notice by scrolling down.

Switched the road-routing engine to OpenRouteService β€” the stop cap is now 50 (was 25)

Road routing for the Route Planner moved from the free OSRM demo server to OpenRouteService, which comes with a documented, reliable free tier instead of an informal best-effort one β€” and supports far more stops per route. The app's own stop cap went up accordingly, from 25 to 50, so a longer multi-day leg no longer needs to be split into several routes just to fit. You'll also see a live warning as you approach the new 50-stop limit, the same way the old 25-stop warning worked.

New: bulk-delete several saved routes for a leg at once

A Manage Routes… button next to + New Route in the Route Planner opens a checklist of every saved route on the current leg, with Select all and Delete Selected β€” handy after importing several route options from a rally book leaves a leg with more saved routes than you actually want to keep.

Fixed: Recalculate/Optimize Route could hang forever

Right after leg locations shipped, Recalculate Route or Optimize Route could sit on "Calculating…" forever and never finish. The underlying cause was a server-side session-locking issue that could let one slow request block every other request in the same browser tab β€” fixed across every part of the app that could trigger it, not just the route planner.

Fixed: road-route calculation was failing for everyone

A leftover duplicate function definition on the server was causing Recalculate Route and Optimize Route to fail outright with a server error, for every rider, every time. Fixed.

Documented: exactly what AI Suggested Route does (and doesn't) take into account

The AI Suggested Route help section now spells out precisely what feeds into a suggested route β€” rider profile settings, fuel range, rest/lunch rules, Timed/Daylight windows, riding intensity β€” and what doesn't (gas stations, traffic, elevation, combo codes), plus how it differs from the separate Optimize Route button.

New: PDF import now falls back to OCR for scanned bonus books, plus one-click host-hotel autofill

Some rally books print their Bonus Listing pages as flattened images with no real selectable text β€” importing one used to come back empty. PDF import now recognizes that and reads those pages with OCR automatically. Separately, the leg edit popup's Start/End location fields each got a From PDF… button that reads the host hotel's address straight off a chosen rally book PDF and looks it up for you β€” no retyping needed.

New: a Route Options reference list, imported straight from the rally book, with one-click "Import as Route"

Many rally books define predefined route options β€” ride every bonus on the list, claim a lump-sum bonus. A new Route Options… button imports these straight from the PDF and shows each one's code, mileage, points, and full bonus checklist, right next to your own grid. Every option also gets an Import as Route button (and there's an Import All as Routes for the whole list) that turns it straight into a real, saved Route Planner route β€” no manual re-selecting bonuses required.

New: import now catches duplicate bonus codes before adding them

Appending an imported file to a leg that already has some of those same bonuses now warns you first, with a choice: skip the duplicates, replace the existing rows with the new import, or append everything anyway.

Big accuracy jump: OCR switched from Tesseract to Google Cloud Vision

The free in-browser OCR engine (Tesseract) that reads scanned bonus book pages was flagging over 70% of imported bonuses as low-confidence β€” too many to be a useful "check these few" signal. Switched to Google Cloud Vision, which reads noticeably more accurately β€” and, as a bonus, pages now get OCR'd several at a time instead of strictly one after another, so a big rally book imports faster too.

Six different rally-book layouts now supported

The importer started out recognizing two bonus-book page layouts. Real rally books kept turning up new ones, and each is now supported: a two-column flag-icon layout, a no-points layout (points come from a separate file), a fixed-position layout with no text labels to match on, and a labeled-row layout with everything spelled out in text. Whatever layout a book uses, import now tries all of them (fastest first) before ever falling back to OCR.

Several smaller import/OCR reliability fixes

  • A coordinate reading that comes back numerically valid but implausible (near the North Pole, say) now gets flagged for review, the same as a missing field.
  • Fixed a rare case where a coordinate's OCR misread could silently drop the entire bonus from the import instead of just misreading it.
  • A PDF that had already been run through a different OCR tool before importing (leaving garbled but present text behind) now correctly falls back to this app's own OCR instead of trying to read the garbled text as-is.
  • An import that's clearly never going to succeed now fails fast, after sampling a handful of pages, instead of running (and billing) a full OCR pass on every page of a doomed import.
  • Availability text the importer doesn't recognize as a structured value (a specific calendar date, a business-hours notice) is now kept in the bonus description instead of silently discarded.
  • OCR misreading a bonus code's digit "0" as the letter "O" is now caught and corrected automatically β€” flagged in the Import Flag column so it's still easy to double-check β€” without touching codes that are genuinely all letters (MANGO, CHACO, and the like).

New: a clear ⚠ Flag column and "trust but verify" reminders for imported/OCR'd data

Anything OCR flags for a closer look (a missing field, a low-confidence coordinate, an implausible location) now shows up in its own ⚠ Flag column with a specific reason and PDF page number β€” instead of a generic note stuffed into the Comment field, which used to leak into GPX/KML exports and your GPS unit. The welcome popup and a post-import notice both remind you that imported and OCR'd data is a starting point, not a guarantee β€” always double-check against the real rally book before riding on it.

Fixed: correcting a bonus's coordinates now refreshes its cached timezone/sunrise/sunset

Hand-correcting a bonus's Lat or Lon in the grid used to leave its cached timezone, address, and sunrise/sunset stale β€” computed from the old coordinate, with no visual sign anything was wrong. Editing a coordinate now clears those cached fields so they get picked up automatically on the next Look Up API Data pass.

Fixed: a leg's saved location now reaches Hours & Miles and the Map page too

A leg's saved Start/End location (from the leg edit popup), the Hours & Miles Checkpoints table, and the Map page's own start/end markers used to be three separate, disconnected places to enter the same real-world hotel or gas stop. Entering a location in any one of them now fills in the other two automatically β€” only when they're still blank, so anything you've already entered yourself is never overwritten.

Clearer divider between Rallies and Legs in the sidebar

As a rally grows a few legs, the Legs list used to run right up against the Rallies list above it with no visual break. There's now a clear divider between the two sections.

New: full database backup on the admin page

A ⬇ Download Database Backup link on the admin page streams a complete SQL dump of every table β€” schema and data β€” ready to restore through phpMyAdmin.

New: a much fuller rider overview table on the admin page

The admin rider table grew from a handful of columns to nearly two dozen: Logins, Rallies, Legs, Bonuses, Flagged (bonuses still carrying an unreviewed import flag), Routes, whether a rider has ever set up a Rider Profile, and how many motorcycle profiles they've created β€” a much fuller picture of how each rider is actually using the app.

Rider/Email/status columns now stay pinned while scrolling on the admin page

With so many more columns, scrolling right on the admin page to see usage numbers used to lose track of whose row you were even looking at. Rider, Email, and the online-status dot now stay pinned to the left edge no matter how far right you scroll.

A handful of admin-page readability fixes

  • The "Reading the columns" explanatory text on the admin page is bigger, and now stretches the full width of the table instead of hugging the left edge in a narrow column.
  • A rider's login history date is fully visible again β€” it used to get squeezed down to an unreadable stub by the frozen-column styling.

New: the ℹ️ Route Info popup now shows projected gas/rest/lunch stops

The ℹ️ Route Info popup adds four more rows once you've clicked πŸ“… Build Route Schedule for the current route: Gas stops, Rest stops, Lunch stops, and a Total stops row adding those to your Bonus Stops count β€” the same rest/lunch/fuel projection Build Route Schedule already builds from your motorcycle's fuel range and the rally/leg's rest & lunch rules, just summarized here too. Haven't built a schedule yet? The popup shows a Build Schedule Now button in its place β€” click it and the popup refreshes with the real counts.

August 28, 2026

Help file: documented what happens when you delete and re-import bonuses

Added an explanation, in Selecting & deleting rows, of what deleting a bonus actually does and what re-importing the same rally book afterward does (and doesn't) restore β€” including how it can affect a saved route's stops or Start/End location if any of the deleted bonuses were used in one.

August 25–26, 2026

New: each leg can save its own start/end hotel location

The leg edit popup now has Start location and End location fields β€” usually the hotel a leg begins or ends its overnight stop at. Type an address, click Look up, and it geocodes and saves the coordinates along with it.

  • Once a leg has a saved location, opening that leg β€” or clicking New route for it in the Route Planner β€” automatically fills in the route's Start/End points from those saved locations, so you're not re-typing or re-searching the same hotel address every time you plan a route for that leg. You can still change or clear either one for a specific route same as before.
  • Since the hotel a leg ends at is usually the very same hotel the next leg starts from, saving a leg's end location now automatically fills in the next leg's start location too β€” but only if that next leg doesn't already have its own start location saved, so nothing you've entered yourself ever gets overwritten. If you have an existing rally and want this to catch up on legs you set up before this update, just open an earlier leg and click Save (no changes needed) to push its end location forward.

Hours & Miles: new per-leg columns, and a totals fix

The Hours & Miles Legs table has five new columns showing each leg's real totals, not just the daily rate you type in: Rest hrs, # Gas stops, Gas stop hrs, # Bonus stops, and Bonus stop hrs β€” each one correctly accounts for legs that span more than one day.

  • The Rally totals row now correctly sums Rest hrs/day, Gas stops/day, Gas stop min, Bonus stops/day, and Bonus stop min across all your legs β€” 4 rest hours on Leg 1 + 4 on Leg 2 + 4 on Leg 3 now shows 12, not 4. Avg MPH, Avg MPG, and Fuel $/gal still show an average across legs, since adding those together wouldn't mean anything.
  • Every column on the Hours & Miles Legs table is now centered, to match the layout of the original spreadsheet. The separate Checkpoints table (addresses and coordinates) is unchanged.

Fixed: Hours & Miles now stays in sync with your legs

  • Editing a leg's start or end date now automatically updates its matching Hours & Miles block to match, instead of leaving you to copy the dates over by hand.
  • Fixed a rare bug where editing an already-saved leg could silently shuffle the internal order of your legs, which could in turn make a leg's Hours & Miles numbers β€” or its Out of range flag β€” show up matched to the wrong leg.
  • Fixed a bug where clicking the Hours & Miles tab could show a completely blank screen instead of the worksheet.

Help file: documented the Out of range flag

Added an explanation, with screenshots, of the Range column in the grid and the dimmed map markers it's paired with β€” see The bonus grid and Map view.

Getting started

Creating an account

From the sign-in screen, click Need an account? Sign up. Enter your email, a password, and your name, then click Sign up. You'll be signed in immediately and dropped into the main app with an empty rally list.

Create your account form with Email, Password and Name fields
The sign-up form β€” email, password, and display name are all that's required.

New accounts sign up as a regular rider. If you need admin access (to manage other users, see below), ask an existing admin to promote your account from the admin portal.

Signing in

Enter your email and password on the sign-in screen and click Sign in. Forgot your password? Use the Forgot password? link to request a reset email.

Sign in form with Email and Password fields
The sign-in screen. Sessions stay active across browser restarts, so you generally only need to do this once per device.

Every time you sign in, a Welcome popup greets you by name and repeats a standing reminder: anything the app imports automatically β€” especially OCR'd data from a scanned rally book PDF β€” is a starting point, not a guarantee. Click OK to dismiss it and get to your rally list.

Welcome popup greeting the rider by name, with a standing reminder to trust but verify anything imported or OCR'd from a rally book PDF before riding on it
The Welcome popup β€” a "trust but verify" reminder every sign-in, so it's never just a one-time notice you can miss.

How the app is organized

Everything lives under three levels, shown in the left-hand sidebar once you're signed in:

  1. Rallies β€” the top-level events you're planning for(eg.. 2027 Iron Butt Rally ). Click + New under "Rallies" to add one.
  2. Legs β€” appear once you select a rally. Each leg is a part of a rally which you would create a route with its own start/end time, used to calculate sunrise/sunset for bonuses on that leg.
  3. Bonuses β€” appear once you select a leg, in the grid on the right. This is where you'll spend most of your time: entering codes, coordinates, points, and availability.

The toolbar above the grid is one row:

  • Grid / Map / Hours & Miles / Points β€” switch views.
  • + Add Bonus β€” a new blank row.
  • Import β–Ύ β€” a bonus file (rally book PDF, GPX, KML, Excel, CSV) or a bonus points file.
  • Rally Setup β–Ύ β€” things you set once per rally: Combo codes, Scoring rules, Route options.
  • Export β–Ύ β€” GPX for this leg or the whole rally, an Excel spreadsheet, and the ASCII-fold option for GPS units that can't show accented characters.
  • Look Up API Data β€” time zone, address and sunrise/sunset for bonuses missing them.
  • 🧭 Route Planner… (right) β€” build, check and plan routes, including 🧠 The Big Brain.

When you check rows in the grid, a selection bar appears under the toolbar with what you can do to them: Add to Route, Look Up API Data, Clear Timed, Clear Comment, Delete and Clear selection. Your account settings (βš™ Settings, 🏍 Rider Profile, β›½ My Motorcycles, Sign out) are in the menu under your name at the top right.

Sidebar showing a selected rally and its list of legs
Selecting a rally reveals its legs underneath. Selecting a leg loads its bonuses into the grid on the right.

Units & time format

Click βš™ Settings in the header to choose Imperial (Β°F, mph, miles, gallons) or Metric (Β°C, km/h, kilometers, liters), and 12-hour or 24-hour time. This covers riders outside the US planning a rally in kilometers and Celsius.

Settings modal with Units set to Imperial and Time format set to 12-hour, and Cancel/Save buttons
The Settings dialog, opened from the βš™ Settings button in the header.

Units affects the weather forecast popup's temperatures and the Hours & Miles worksheet's speed, distance, and fuel columns (Avg moving MPH/MPG, Miles, Gallons become Avg moving km/h, Avg km/L, Km, Liters). Time format affects every place sunrise/sunset is shown β€” the grid columns, a bonus's popup, and GPX/XLSX export previews.

Both are saved to your account, so they follow you to any device you sign in from. Changes apply immediately β€” no need to reload the page.

Using this app in another language

This app is only written in English, but riders outside the US can use their browser's built-in page translation to view it in Spanish, French, German, or any other language β€” the whole page, including the bonus grid, buttons, and popup messages, gets translated automatically.

In Microsoft Edge or Google Chrome, right-click anywhere on the page and choose Translate to [your language] from the menu. You can also click the translate icon that appears in the address bar on some pages, or open the browser's Settings and set a preferred language so pages translate automatically going forward.

Right-click context menu in Microsoft Edge with the Translate to English option highlighted
Right-click anywhere on the page and choose Translate to [your language] β€” Edge and Chrome both offer this.

Translation works well for the page itself, but a couple of things may not translate: text inside tooltips (like the column header tooltips), and any emails the app sends (like a password reset link) β€” those stay in English unless your email program offers its own translation.

Rider profile

Click 🏍 Rider Profile in the header to record how you like to ride: your night-riding and bad-weather/rain tolerance, average moving speed, how often and how long you like to stop and rest, how hard you push daily mileage (relaxed/moderate/aggressive), and how much sleep/off-bike rest you need each day. This is saved once to your account β€” not per rally β€” and feeds the route planner's Build Route Schedule feature (see Building a route below).

Rider Profile dialog with Night riding, Riding in bad weather, Average moving speed, break frequency and duration, riding intensity, and daily rest hours fields
The Rider Profile dialog, opened from the header.

Average moving speed is worth a closer look, since the app asks for it three different places and a few riders have written in wondering if they mean three different things. They don't β€” all three are your speed only while the bike is actually moving. Rest, fuel, meal, and bonus-stop time are never blended into any of them; the app already tracks those separately and adds them on top wherever it estimates a schedule. The Route Planner's own Avg moving speed field is this exact number, pre-filled here but editable per route, and the Hours & Miles worksheet's Avg moving MPH column is the same idea again β€” just a separate number you type in per leg rather than one pulled from this profile, since a leg's real moving speed can vary rally to rally (traffic, terrain, weather) more than your personal baseline does.

None of this is required β€” leave the defaults if you'd rather not fill it in, and creating and saving routes works exactly the same either way. It only changes anything once you click Build Route Schedule.

My motorcycles

Click β›½ My Motorcycles in the header to keep one or more fuel-range profiles β€” main tank and auxiliary tank capacity, average fuel consumption, a fuel reserve you never want to plan below, and a safety buffer percentage on top of that. Mark one Default motorcycle and it pre-fills automatically β€” motorcycle, fuel range, average speed, and minutes per stop β€” when you start planning a new route. Every field here (tank sizes, fuel consumption) follows your Units setting: imperial shows gallons/MPG, metric shows liters/L per 100km.

My Motorcycles dialog listing a BMW R1250 GS Adventure marked as default, with its tank capacity and MPG, and an Add motorcycle button
The My Motorcycles dialog β€” one row per bike, with its usable range and MPG at a glance.

Click a motorcycle to edit it, or + Add motorcycle for another.

Edit motorcycle dialog with Name, Main tank, Auxiliary tank, Average MPG, Fuel reserve, Safety buffer fields and a Default motorcycle checkbox
Editing a motorcycle profile. Delete removes it; Default motorcycle marks it as the one that pre-fills new routes.

Like the rider profile, this is optional β€” the route planner's own Fuel range (mi) field works fine on its own without picking a motorcycle here. Picking one attaches it to the route (so you know which bike it was planned for) and fills in Fuel range for you β€” usable tank capacity (main + auxiliary, minus your fuel reserve) times average fuel consumption, minus your safety buffer β€” recalculated any time you switch bikes. You can still type over it with your own number afterward if you'd rather.

Planning a rally

Creating a rally

Click + New above the rally list, give it a name and (optionally) a year and notes, then Save.

New rally modal with Name, Year, and Notes fields filled in
The New rally dialog. Year defaults to the current year but can be changed.

To edit or delete a rally later, click the ✎ that appears next to its name in the sidebar β€” this opens the same dialog with a Delete button. Deleting a rally also deletes all of its legs and bonuses, so it asks for confirmation first.

Creating a leg

With a rally selected, click + New above the leg list. Give the leg a name and, ideally, a start and end date/time β€” these are used to compute accurate sunrise and sunset times for every bonus on that leg. Daylight saving in effect is set for you from the leg's start date using US/Canada rules (2nd Sunday of March to the 1st Sunday of November) β€” a note under the box says whether it applies on that date, and warns if the box disagrees. Change it only for a place that doesn't follow those rules (most of Arizona, Hawaii, Saskatchewan, or outside North America). Saving the leg refreshes its bonuses' sunrise/sunset, and a leg whose sunrise/sunset were calculated with the wrong setting is corrected automatically when you open it.

New leg modal with Name, Start, End fields and a Daylight saving checkbox
The New leg dialog. Start/End are optional but unlock sunrise/sunset lookups for that leg's bonuses.

Click a leg's name (or the small pencil that appears next to it) to edit or delete it later. The same popup also has Start location and End location fields β€” usually the hotel a leg begins or ends its overnight stop at. Type an address and click Look up to geocode and save it, the same address-lookup pattern as the Hours & Miles checkpoints. If you forget to click Look up, or change the address afterward, Save looks it up for you. If the address can't be found, you're asked whether to go back and adjust it or save without a map location. Once a leg has a saved location, opening that leg β€” or starting a new route for it β€” automatically fills in the Route Planner's Start/End points from those saved locations, and shows them on the map right away; see Start, End, and your motorcycle below for what that looks like. And since the hotel a leg ends at is usually the very same hotel the next leg starts from, saving a leg's end location automatically fills in the next leg's start location too, as long as that next leg doesn't already have one of its own. Each field also has a From PDF… button (Β§51) that reads the host hotel's name and address straight off a rally book PDF's Schedule of Events page and fills it in for you, geocoding it immediately β€” handy for skipping the typing on a rally where every checkpoint is the same host hotel.

The bonus grid

Selecting a leg loads its bonuses into a spreadsheet-style grid. Click any cell to edit it in place β€” changes save automatically (watch the small save indicator next to your name in the header). Use + Add bonus to insert a blank row.

Bonus grid populated with many bonus rows including code, coordinates, points, availability, timed column with a clock icon, timezone, and sunrise/sunset
A leg's bonus grid. Columns can be reordered, sorted, and resized; scroll right for more (Sunrise, Sunset, Address, Symbol).

The Formatted Bonus Code column, just before Code, is read-only and updates automatically as you edit a row β€” it's the bonus's CODE-POINTS-AVAIL-TIMED name, the same format used for the <name> in an exported GPX waypoint.

All column headers have tooltips β€” hover over any one to see an explanation of what it means and how it's used, like the Formatted Bonus Code column below.

Bonus grid with the Formatted Bonus Code column header hovered, showing a tooltip that reads: Calculated, not editable β€” built automatically as CODE-POINTS-AVAIL(-TIMED) from the Code, Points, Avail, and Timed columns. This is the name used in the exported GPX/XLSX.
Hovering any column header shows a tooltip β€” here, the Formatted Bonus Code column explaining how the value is calculated.

The Range column flags any bonus where a round trip from Start to it and back to End alone already exceeds this leg's Hours & Miles "Miles possible" budget β€” meaning it couldn't be reached even if it were the only stop you made all leg. It's a heads-up to help narrow down which bonuses are worth planning around, not a hard rule: it never removes a bonus from the grid or map, never stops you from adding it to a route, and the column is sortable β€” click its header to group flagged bonuses together.

Bonus grid with a Range column showing red Out of range pills on three bonus rows
Bonuses flagged Out of range in the grid β€” sortable like any other column, and still fully part of the grid.

The match to the Hours & Miles worksheet is by position: this rally's 1st leg reads its budget from that worksheet's "Leg 1" block, 2nd leg from "Leg 2," and so on β€” the same way the worksheet already names them. A leg won't show any flags until that worksheet's matching block has dates filled in and both checkpoints looked up; that failure mode is silent rather than showing a false flag. One limitation worth knowing: the worksheet caps at 3 legs like the original spreadsheet, so a 4th+ leg in a longer rally won't get this flag.

⭐ Marking a bonus mandatory

The ⭐ column, right next to the ⚠ Flag column, marks a bonus you already know you have to ride β€” something the rally book itself calls mandatory, or a bonus (often a timed one, sometimes a group photo) the rally master specifically called out at the start rider meeting. Click the column to toggle it on (⭐) or off (β˜†) β€” like every other grid edit, it saves automatically. This is entirely your own call: the app has no way to read the rally book or listen in on the rider meeting, so nothing here is ever set for you automatically, including on import β€” a bonus a source file happens to label "mandatory" still comes in unstarred, and needs the same click as any other.

Starring a bonus doesn't change its points, availability, or anything else about the row by itself. Its whole effect is in 🎯 AI Suggested Route: a starred bonus is treated there as a hard requirement rather than an optional candidate bonus, seeded into the route ahead of the normal points-per-hour search, so it can no longer lose its spot to a higher-value bonus the way an ordinary candidate bonus can. See that section below for the full details, including what happens when a mandatory bonus genuinely can't be made to fit.

Two things worth being explicit about, since they change how you should think about a ⭐ bonus:

  • You don't have to also check it. A ⭐ bonus joins 🎯 AI Suggested Route's search automatically whether or not it's also checked in the grid or on the map β€” and because it's a hard requirement, it gets first claim on the leg's available time. If the leg can't fit both it and everything you checked, one of your checked, non-mandatory bonuses is what gives way, not the starred one β€” see 🎯 AI Suggested Route below for exactly how that trade-off gets reported.
  • ⭐ only does anything inside 🎯 AI Suggested Route. It has no effect anywhere else in the app. Building a route by hand β€” dragging bonus markers onto the map in Route Mode, or Add Selected to Route β€” completely ignores it, and so do Optimize Route, Build/Print Route Schedule, and the GPX/KML/XLSX exports. Nothing warns you if you build or save a route by hand that leaves a starred bonus out. Think of the star as a note to yourself that only becomes an enforced requirement the moment you actually click 🎯 AI Suggested Route.

Entering or changing bonus points

The Points column is a normal editable cell β€” click it, type the new value, and press Enter or click away to save. Use this to correct a bonus's points after import, or to fill in points for bonuses whose import didn't include them (some bonus listing files publish codes and coordinates first, with points released or corrected later).

Bonus grid with a single row's Points cell in edit mode showing the value 109
Click a Points cell to edit it in place, same as any other editable column.
Bonus grid with a row selected via its checkbox and that row's Points cell in edit mode
Editing works the same whether or not the row is checkbox-selected.
Bonus grid for a leg imported without points data, showing a mostly empty Points column with two rows filled in manually
A leg imported without points β€” the column stays blank until you fill it in row by row, or use Import Bonus Points… to merge in a separate points file.
Walkthrough: entering and changing bonus points directly in the grid.

Availability codes

The Avail column controls how a bonus is scored and how it's shaped on the map:

A = 24 Hour D = Daylight T = Timed S = Special G = Group Photo H = Checkpoint AC / DC / TC = Combo (24-hour / Daylight / Timed)

For timed bonuses, fill in the Timed column with the available window (e.g. 930a-6p). This is a plain text column β€” it's what shows up in the exported GPX/XLSX, and what the map's legend and popups display.

For a Timed or Timed-Combo (T/TC) bonus, a small πŸ• column next to Timed shows an icon β€” click it to open a small dialog with two date/time pickers, Available from and Available until. This is optional, structured data separate from the plain text: it doesn't change what's exported, but it's what the route planner's Build Route Schedule feature (see Building a route) checks your estimated arrival time against, flagging anything that would miss the window. If you leave it unset, the route tools read the hours from the plain Timed text instead, as long as it's a single time range such as 1000-1830 or 10am-1pm, applying to every day. Text with days or notes (Thu-Fri: 0800-2000) can't be read, so set the πŸ• for those, or for a window that only applies on one date. Clear in that dialog removes the structured window entirely without touching the plain Timed text.

The β›΄ column right after the πŸ• is for a bonus you can't simply ride up to, such as one reached by a ferry that doesn't carry vehicles, or a long walk from parking. It's blank on most bonuses; hover over a row to see a faint β›΄ to click. See Ferries & hard-to-reach bonuses for how to use it.

Bonus grid scrolled right showing the Timed text column, the small clock icon column next to it, Comment, Combo, TZ, Sunrise, Sunset, Address, Symbol, Weather, and Lookup columns
Scrolled right in the grid β€” the plain Timed text column with its small πŸ• column right beside it (a filled clock next to 0800-1700 and 1500, Wedne... means a structured window is already set for that row).
Timed bonus window dialog with Available from and Available until date and time pickers, and Clear, Cancel, and Save buttons
The Timed bonus window dialog that opens when you click the πŸ• icon β€” set Available from and Available until with the date/time pickers, then Save. Clear removes the structured window; Cancel closes without changes.

Tagging combo bonuses

Some rally packs group individual bonuses into a named combo β€” collect all of a river's bonuses and the combo pays extra, for example. Click Combo codes… in the toolbar to define your rally's list of combo codes and names (e.g. MISS1 = "Mississippi River"). This list is shared across every leg in the rally, since a combo can span more than one leg. Add codes one at a time with + Add combo code, or click Paste list… to paste in several at once β€” copy two columns (code, name) straight from a spreadsheet, or paste a comma-separated list; a code that already matches one in your list gets its name updated instead of creating a duplicate.

Each combo row also has a Points box for what completing that combo is worth (Paste list… accepts it as an optional last column, e.g. CMB1 Eagle combo 2000). A combo with points is planned for by 🧠 The Big Brain, and when your route includes every bonus tagged with it, it's added to the route's Total score in ℹ️ Route Info, the route stats line and the bonus book (e.g. "Combo CMB5 +1,000"). Leave it blank and the combo is ignored for scoring.

Combo codes modal with a paste-list panel open showing three tab-separated code and name rows ready to add
The Combo codes modal β€” add codes one at a time, or click Paste list… to add several at once from a pasted spreadsheet copy.

Once you've defined some codes, click a bonus's Combo cell in the grid to open a checklist of them β€” check every combo that bonus belongs to (a bonus can be part of more than one) and click Done. Hover the cell afterward to see the full combo names, not just the codes.

A bonus's combo tags are written to the exported GPX file as <gpxx:Category> entries, so they show up as categories on your GPS the same way they did from the spreadsheet's export.

Selecting & deleting rows

Check the boxes on the left of any rows you want to act on β€” the header checkbox selects all. With rows selected, Delete selected removes them, and Look up selected fetches address/timezone/weather for just those rows.

Bonus grid with nine rows checked and the Delete selected and Look up selected buttons active, along with a 9 selected count
Nine rows selected β€” the toolbar's Delete and Look up selected buttons light up, and a count appears.

Deleting is permanent, and re-importing afterward does not undo it. If you delete a batch of bonuses and then re-import the same rally book PDF to bring them back, the app doesn't restore or reconnect to what you deleted β€” it reads the PDF fresh and adds each bonus back as a brand-new row, even though the code, coordinates, and points may look identical to what was there before. As far as the app is concerned, it's a different bonus than the one you deleted.

That distinction matters if any of the deleted bonuses were used in a saved route. A route remembers its stops, and its Start/End location if one is set to a bonus, by pointing at that specific bonus row β€” not by its code. So:

  • A stop built from a bonus you delete is quietly dropped from the route the next time you open it β€” and once the route is saved again after that, the stop is gone from it for good. The freshly re-imported version of that bonus does not automatically rejoin the route; you'll need to re-add it from the grid or map yourself.
  • If a deleted bonus was set as a route's Start or End location, that field is cleared back to blank as soon as the bonus is deleted.

If you're planning to delete and re-import a leg's bonuses, it's worth checking first whether any of your saved routes on that leg use bonuses from it β€” plan on rebuilding those stops (and Start/End, if needed) afterward rather than assuming the re-import will pick up where the route left off.

Looking up address & timezone

Once a bonus has coordinates, click Look up missing in the toolbar to fill in its timezone, reverse-geocoded address, and (if the leg has start/end times set) sunrise and sunset β€” automatically, for every bonus that's missing this data. This runs in the background with a small progress indicator, and results are cached, so re-running it doesn't re-charge lookups for bonuses already looked up.

Lookups are rate-limited per account to keep API costs down. If you hit the limit, wait a bit and try again.

Bonus grid toolbar with Look Up API Data highlighted, showing a progress bar and Retrieving data... 11 of 40 location(s)
A lookup running in the background β€” the progress bar shows how many of the leg's bonuses are left to process.
Rally Planning App popup reading: Lookup failed for 11 bonus row(s): HURR, INGAP, LACEF, LNHWY, MAQUO, PATCH, PITT, PONCE, POST, PROV, SROCK. Try Look Up Selected/Missing again for those rows.
If a large batch runs into the timezone API's rate limit, this popup lists exactly which bonus codes were missed β€” run Look Up Selected/Missing again to fill in just those rows.

Importing bonus files

Click Import file… and choose a .gpx, .kml, .csv, .tsv, .txt, Excel (.xlsx/.xlsm/.xls), or .pdf bonus listing file. The app parses it entirely in your browser and shows a preview grid so you can review and fix anything before committing β€” nothing is written to your leg until you click Append to leg or Replace leg's bonuses.

Import bonus data modal showing 162 bonus records read from a GPX file, with a preview grid of code, coordinates, points, availability, and comment columns
The import preview for a 162-bonus GPX file β€” column headers, availability codes, and coordinates are auto-detected. Replace clears the leg's existing bonuses first; Append adds to them.
Rally Planning App popup reading: Imported 40 bonus row(s) into Leg 1. Saving now β€” you can use Look up missing to fill in timezone, address, and sunrise/sunset.
Once you click Append or Replace, this confirms how many rows were imported and reminds you to run Look up missing next.

PDF import recognizes several different rally-book layouts and can read image-only (scanned) books with OCR. Only bonuses with real GPS coordinates come through; monitoring bonuses (call-in, rest, tracking), combo definitions and checkpoint info are skipped automatically. See How PDF import works for the layouts it recognizes, what it reads from each bonus, and what to do when a book doesn't import.

Some rally books' bonus-listing pages are flattened images rather than real selectable text (common in newer, more graphically designed packets). If a PDF like that comes up with "No bonus records were found," the app automatically retries with OCR before giving up β€” this can take several minutes on a large book, with a page counter in the import window so it doesn't look stalled; leave the window open and the results land in the preview grid below once it finishes.

Import bonus data modal showing an OCR progress bar reading page 12 of 49
OCR reading a scanned rally book, page by page β€” this window stays open and updates its own progress bar until every page's been read.

OCR is less reliable than reading real text, so give the preview grid a closer look afterward: a row OCR isn't confident about gets a ⚠ in its own Flag column (far left) with a specific reason β€” hover it to see why β€” most often a coordinate a misread digit could throw off. A clean-looking row isn't a guarantee either: trust but verify, and check codes, coordinates, and points against the actual PDF before importing, not just at a glance.

Import bonus data preview grid for an OCR'd PDF, with a yellow trust-but-verify banner and most rows carrying a warning triangle in the flag column
The review grid after an OCR'd import β€” the ⚠ flag column and the banner above it both point at rows worth a closer look before you click Append or Replace.

Decoy and hidden text. Some rally masters plant text in a PDF that never shows on screen or on paper (white text, text hidden under a photo, or numbers whose underlying characters differ from what's printed) to catch riders who machine-read the book. Every text-based PDF import automatically checks for text that leaves no visible ink on the page. Any row built from it gets a ⚠ in the Flag column, and a warning shows above the preview. For a full check, click Verify against printed page in the import window (shown for text-based PDFs only). It OCRs each bonus page and confirms every row's code, coordinates, and points actually appear in the printed text, flagging any that don't. It takes a few minutes on a large book and needs the same lookup access as OCR import. A flag can also mean OCR misread a digit, so always settle it against the printed book.

Importing bonuses from a PDF bonus listing.

How PDF import works

Rally books come in many different layouts, and a PDF doesn't label which number is the points value or which line is the coordinates. So the app looks for layouts it has learned from real rally books, one after another, and uses the first one that finds bonuses. Here's what happens when you choose a PDF in Import Bonus File…:

  1. Read the text. The PDF is opened in your browser and its text is read, along with where each word sits on the page and how big it is. Repeating page headers and footers ("Leg 1 Page 5 of 18") are removed. Nothing is uploaded for this step.
  2. Try each known layout in turn (table below). As soon as one finds bonuses, the rest are skipped.
  3. Check for hidden text. Any bonus built from text that doesn't actually print on the page (white text, text under a photo, text off the page) gets a ⚠ flag. See Decoy and hidden text in Importing bonus files.
  4. If no layout matched, try OCR. Pages that have almost no readable text (scanned or flattened-image pages) are sent to Google Cloud Vision to be read, with a page counter in the import window. If that finds nothing either, the app OCRs a small sample of pages spread through the book, and only reads the whole book if the sample finds bonuses, so a book that doesn't match isn't OCR'd page by page for nothing.
  5. Preview. Whatever was found lands in the import preview grid for you to check and fix before you click Append or Replace.

What it reads from each bonus

  • Code and Points. One layout has no points in the book at all; import those afterward with Import Bonus Points….
  • Lat/Lon. Each layout reads the coordinate style its book uses: decimal degrees (33.4484, -112.0740) or degrees and decimal minutes (N33Β° 28.567' W82Β° 01.415', N27 12.953 W81 51.505). They're stored as decimal degrees. A bonus block without coordinates is never imported.
  • Avail and Timed. The book's hours text ("24 Hours", "Daylight only", "0800-1700", "10am-1pm") is turned into the app's availability code (A, D, T…), and a time window is kept in the Timed column, which the route tools read (see the bonus grid).
  • Comment. The bonus name and the requirement/description text.
  • Not read: street addresses (use Look up missing afterward to fill in address, time zone and sunrise/sunset from the coordinates), combo membership (tag combos yourself in the Combo column), and ⭐ mandatory (always your call).

Layouts it recognizes

Each layout below was built from, and tested against, a real rally book. A book doesn't have to look identical: what matters is the pattern described in the middle column.

LayoutHow to recognize itBuilt from
1. Code-and-points row Each bonus starts with a row holding the code on the left and "NNNN points" on the right, followed by the name, address, coordinates on their own line, available hours and the description.
ARDA                      165 points
Bonus Name
123 Main St
City, ST
33.4484, -112.0740
24 Hours
Take a photo of…
Iron Butt Rally 2023
2. Asterisk blocks with labels Bonuses separated by a full line of asterisks, with "Points:" and "Available:" written out in the text and degrees-minutes coordinates.
****************************************
CODE  Bonus Name
City, ST          Points: 750
N33Β° 28.567' W82Β° 01.415'   Available: 24 Hours
Take a photo of…
SNAFU Rally 2025
3. Two-column with flag icons A table-like row with the code far left and points far right, a βš‘ before the coordinates, and "βŒ– Requirement:" before the description.
Daylight
CODE                         1234 points
Bonus Name
βš‘ 49.1657 / -123.9370
βŒ– Requirement: Take a photo of…
54-40 Rally 2026
4. Large code headings, no points The code is printed in a noticeably bigger font on its own line, and there's no points value anywhere (the rally publishes points separately). Use Import Bonus Points… afterward.
CODE          (bigger font)
Bonus Name
33.4484, -112.0740
Available Hours
Description…
Senior Butt Rally 2021
5. Fixed columns Asterisk lines between bonuses; the name on the left with the code on the right of the same line, points right-aligned below, and the two-letter state, hours and coordinates sharing one row.
****************************************
Bonus Name                         CODE
Street address                      450
City
TX  Daylight            31.5493   -97.1467
Description…
Heart of Texas Rally 2018
6. Labeled rows City, coordinates (with N/W letters, no Β° sign) and "Points:" on one row, and a separate "Code:" row with blank Date/Time/Odo boxes to fill in.
City, ST    N27 12.953   W81 51.505    Points: 300
Bonus name
Description…
Code: ABC   Date: ___   Time: ___   Odo: ___
Cape Fear 1000 Rally 2015
7. Scanned / image pages (OCR) The bonus pages are pictures rather than text (you can't select the words in your PDF viewer). OCR reads bordered boxes labeled Bonus Code, Bonus Name, Latitude - Longitude, Availability and Bonus Points, usually several to a page with a photo beside each. Iron Butt Rally 2025

Quick test for layout 7: open the PDF and try to highlight a bonus's code with the mouse. If you can't select it, the page is an image and the import will use OCR. OCR sends those page images to Google Cloud Vision through the app's server, takes a few minutes on a large book, and needs lookup access (the same permission as Look Up API Data); ask the site admin if you don't have it. Every other layout is read entirely in your browser.

Checking the preview

  • Count. Compare the number of bonuses found (top of the import window) with the book. A few missing usually means bonuses without coordinates (wild cards, call-ins, rest bonuses, combo definitions), which is expected, or a typo in the book's own coordinates (for example minutes over 60), which the app rejects.
  • ⚠ Flag column. Hover a ⚠ to see why it was flagged:
    • OCR: a missing code or points, a coordinate that lands somewhere implausible, or a coordinate OCR wasn't confident about.
    • Hidden text in PDF: the row was built from text that doesn't print.
    • Not on printed page: from Verify against printed page; the code, coordinates or points weren't found in the printed page.
  • Spot-check a few bonuses against the book: code, points, both coordinates and the hours. Any cell in the preview can be edited before importing.

When a PDF doesn't import, or imports badly

  • "No bonus records were found" after OCR too means the book's layout isn't one the app knows yet. Options:
    • Ask the rally master for a GPX, CSV or Excel version; many will provide one, and those import with no guesswork.
    • Copy the bonus table into a spreadsheet and import that as CSV or Excel. Any file with a code, latitude and longitude column works; points, availability and comment columns are picked up if present.
    • Send the PDF to the app's developer so the layout can be added for everyone.
  • The whole rally is in one PDF. Import reads every bonus in the file, so a book covering three legs puts all three legs' bonuses into the leg you're importing into. Save just that leg's pages as a new PDF first (in most PDF viewers: Print, choose "Save as PDF" or "Microsoft Print to PDF", and enter the page range), then import that.
  • Garbled codes or coordinates in a text PDF. This often happens when a book was run through someone else's OCR tool before you got it. The app falls back to its own OCR when the text layouts don't work; if you have the original book, import that instead.
  • A password-protected PDF may not open in the browser. Use an unprotected copy.

Other things the app reads from a rally book PDF

  • Leg Start/End location: the From PDF… button in the leg's Edit Leg window reads the host hotel's name and address from the book's schedule page and looks it up.
  • Route options: Route Options… reads a book's predefined route choices (each route's code, miles, points and member bonuses).
  • Points released separately: Import Bonus Points… reads a code-and-points file and updates the Points column of bonuses already in the leg.

Scoring rules

Most rallies score a route as the sum of its bonuses' points plus any combos. Some rally books add rules on top, where which bonuses you get and in what order changes their value. Enter those with Scoring Rules… in the grid toolbar. They're saved for the whole rally (every leg), and used by 🧠 The Big Brain, the Total score in ℹ️ Route Info, the route stats line and the Route calculated popup.

Each rule names bonuses by code. * means "anything" (BF* is every code starting BF), commas list several (BF*, DRGN*), and in an unlock rule ? means "the same letter" in both boxes.

RuleWhat it doesExample (54-40 Rally)
UnlockThese bonuses score 0 unless the unlocking bonus was claimed earlier in the ride.Unlocked by BOOK?, unlocks BF?*: each Research Center unlocks its own lettered Bigfoot series.
Count awardAn award for how many of these bonuses you claim: the points next to the highest count reached. Paste the book's table, one "count points" pair per line (two pairs per line is fine too).Bonuses counted BF*, table 5 200, 10 400 … 130 20000 (Progressive Sasquatch).
Boost next bonusClaiming a trigger bonus multiplies and/or adds to the next matching bonus. Several triggers in a row still boost it once.When you claim SCT*, the next BF* is multiplied by 2. A second rule: LAIR* adds 100 to the next BF*.
Boost rest of rideEach trigger bonus adds points to every matching bonus claimed after it.Each SCNC* adds 15 to every later BF*, CRYD*, DSM*, MRMD*, DRGN*.
Meal bonusPoints for a meal each day of the leg, plus extra when the meal is at a matching bonus stop (at most one per day). Days defaults to the leg's calendar days.1000 per day, extra 1000 when the meal is at FOOD*.
Extra pointsPoints every route earns that aren't at a bonus location β€” a BOLO, photo, call-in or rest bonus you plan to claim. Added to every route's total so it matches the rally's score. Add one rule per bonus.(SNAFU 2026) Name BOLO, points 500; a second rule PBON, 250.
Late penaltyWhat finishing late costs. One "minutes percent" pair per line: up to that many minutes late keeps that percent of your score; later than the last line counts as a DNF (0). It doesn't make The Big Brain plan to be late β€” it shows what a late finish would score.15 75 then 30 50: up to 15 min late keeps 75%, up to 30 min keeps 50%, later is a DNF.

Getting rules without typing them. At the top of the Scoring rules window:

  • Copy from another of my rallies: pick one of your rallies that already has rules (for example last year's version of the same event) and click Copy.
  • Shared rule sets: rule sets an admin has published for everyone, named by rally and year. Pick one and click Load.

If the window already has rules, you're asked whether to Replace them or Add the new ones after them. Loaded rules aren't saved until you click Save, so check them against your rally book first. Admins also see a Publish box at the bottom of the window, which shares the rules shown as a named set any rider can load (publishing with an existing name replaces that set), and a Delete button for shared sets. A rider who already loaded a set keeps their own copy if it's changed or deleted.

When the rally has scoring rules, The Big Brain scores every route it considers by them. It puts unlocking bonuses before the bonuses they unlock, places boosts ahead of the bonuses they boost, and chases count awards. Each result shows the rally score with a breakdown, for example "Not yet unlocked (scored 0) βˆ’343 Β· Progressive Sasquatch (40 claimed) +2,600 Β· Meals (5 days, 5 at a bonus location) +10,000".

With a Late penalty rule, ℹ️ Route Info shows a "Late N min β€” penalty" row when your built route schedule finishes after the leg's deadline (keeps P% β†’ the score after the penalty, or DNF), and a Big Brain or Review my route card that's late on real roads says what it would score after the penalty.

Worked example: entering the 54-40 Rally's rules

The 2026 54-40 Rally book layers five scoring rules on top of its bonus points. Here's how each one was read from the book and entered. Open Scoring Rules…, click the button for each rule type, fill it in, then Save.

  1. Research Centers unlock the Bigfoot sightings. The book: a Bigfoot bonus only scores if you've already visited the Research Center for its series (BOOKA for the BFA bonuses, BOOKB for BFB, and so on). β†’ click Unlock. Unlocked by BOOK?, Unlocks these bonuses BF?*. The ? is "the same letter" in both boxes, so one rule covers every series.
  2. Progressive Sasquatch. The book's table: 5 Bigfoot = 200, 10 = 400 … 130 = 20,000. β†’ click Count award. Name Progressive Sasquatch, Bonuses counted BF*, and paste the table, one "count points" pair per line (5 200, 10 400, …). The points are the total award at that count, not an amount added per step.
  3. Scouting doubles the next Bigfoot. β†’ Boost next bonus: when you claim SCT*, the next BF* is multiplied by 2.
  4. Lairs add 100 to the next Bigfoot. β†’ a second Boost next bonus: when you claim LAIR*, the next BF*, multiplied by 1, plus points 100.
  5. Weird Science adds 15 to everything after it. β†’ Boost rest of ride: each SCNC* adds 15 to every later BF*, CRYD*, DSM*, MRMD*, DRGN*.
  6. Daily meal. β†’ Meal bonus: 1000 points per day, Days blank (the leg's days are used), extra 1000 when the meal is at FOOD*.

Save, then check the rules before trusting a plan built on them.

Which rule fits the rally book's wording

The rally book says something like…Use
"Only counts if you've first visited…", "must be unlocked by…", "you need the key/book/clue before…"Unlock
"Collect 5 of these for 200, 10 for 400…", "progressive bonus", "bonus for the number of … you get"Count award (paste the table)
"Doubles (or adds to) the next … you claim", "wild card", "multiplier for your next…"Boost next bonus
"Adds X to every … claimed after it", "each … increases the value of later …"Boost rest of ride
"Meal bonus each day", "eat at a … location for extra points"Meal bonus
"BOLO", "photo/selfie bonus", "call-in", "rest bonus", "registration/check-in bonus" β€” points not tied to a location you ride toExtra points (one per bonus you'll claim)
"Late finishers lose X% for the first 15 minutes…", "time-barred after 30 minutes"Late penalty
"Visit all of these for a combo bonus of X"Not a scoring rule β€” use Combo codes (enter the combo with its points, tag its bonuses)

Checking your rules are right

A typo in a code pattern silently changes the score, so test the rules on a small route before planning with them:

  1. In the Route Planner, make a scratch route (+ New Route) with a few bonuses a rule affects β€” for an unlock, the key and one of its bonuses.
  2. Click Recalculate Route. The Route calculated popup shows the Rally score with a line for each rule that changed it (e.g. "Not yet unlocked (scored 0) βˆ’343", "Next-bonus boosts +2,749"); ℹ️ Route Info shows the totals.
  3. Now put the stops in the wrong order (the unlocked bonus before its key, the boosted bonus before its trigger) and recalculate. The score should change exactly the way the book says it would.
  4. For a count award, add enough bonuses to cross a step in the table and confirm the award line appears with the right count.

When the scores match what you'd work out by hand from the book, delete the scratch route and run 🧠 The Big Brain.

Common mistakes

  • Codes must match the grid. Patterns are matched against each bonus's Code column (capital or small letters don't matter). If the book says "BF-A-01" but your grid has BFA01, use the grid's form.
  • Patterns match the whole code. BF* means "starts with BF" β€” it also catches BFF06 and BFX. BF with no * only matches a code that is exactly BF. Use commas for several groups: BF*, CRYD*.
  • ? is one character. In an unlock, the character the ? matches in the key must be the same one in the unlocked group (BOOK? / BF?*). Outside unlock rules it's just "any one character".
  • Order matters. Unlocks and both boost rules depend on what you claimed earlier in the ride β€” the Route Planner's stop order. A locked bonus still uses up a pending next-bonus boost and still counts toward count awards (it was scored, at 0).
  • Count tables are totals. Enter the award for each count exactly as the book lists it, not the difference between steps.
  • Don't enter combos as rules. All-of-these combos belong in Combo codes; putting them in a count rule would double-count them.
  • Rules are for the whole rally. They apply to every leg. A meal rule with Days blank uses each leg's own calendar days.
  • Extra points are added to every route. Only add the ones you actually plan to claim.
  • Saving is required. Copied or loaded rule sets aren't used until you click Save.

What the rules engine can't do (yet)

Some rally scoring can't be expressed with these rules. The Big Brain won't plan for it, so allow for it yourself:

  • Caps: "at most 3 bonuses from each state/category count", "only your best 10 of these".
  • Choose-one groups: "claim only one of A, B or C" (the planner may take more than one).
  • Time-based values: bonuses worth more at night or on a certain day, or points that change by time of day.
  • Mileage or distance awards: points per mile, or for crossing a distance.
  • Penalties for skipping: losing points for missing a required bonus (mark it ⭐ mandatory instead, so the planner always includes it).
  • Sequence-only bonuses: "visit these in this exact order for a bonus".
  • Late finishes aren't planned for: the Late penalty shows what a late finish would score, but The Big Brain still plans to finish on time.

If your rally book has one of these, let the developer know β€” a sample page from the book is the most useful thing to send.

Examples you can copy

Ready-made rules for scoring styles seen in real rally books. Codes in italic rows are only examples β€” use your own rally's codes.

Rally / styleRuleFill in
54-40 Rally 2026UnlockUnlocked by BOOK? Β· Unlocks BF?*
54-40 Rally 2026Count awardProgressive Sasquatch Β· BF* Β· 5 200, 10 400 … 130 20000 (from the book's table)
54-40 Rally 2026Boost next bonusSCT* β†’ next BF* Γ— 2
54-40 Rally 2026Boost next bonusLAIR* β†’ next BF* Γ— 1, + 100
54-40 Rally 2026Boost rest of rideEach SCNC* adds 15 to every later BF*, CRYD*, DSM*, MRMD*, DRGN*
54-40 Rally 2026Meal bonus1000 per day Β· Days blank Β· extra 1000 at FOOD*
SNAFU 2026Extra pointsBOLO 500 Β· and a second rule PBON 250
"Planets"-style collection (Heart of Texas)Count awardPlanet bonuses PL* Β· the book's table, one "count points" pair per line
Wild cards (SBR style)Boost next bonusWhen you claim WC* β†’ the next * (any bonus) Γ— 2
Late-finish scheduleLate penalty15 75 Β· 30 50 (75% up to 15 min late, 50% up to 30, DNF after)

Admins can publish a finished set as a shared rule set (see above), so riders of the same rally can load it instead of typing it in.

Notes: a bonus scored before it's unlocked still counts toward count awards (it was scored, at 0 points) and still uses up a pending next-bonus boost. Meal points are an estimate: the app doesn't plan where you eat. Make sure the leg's lunch rule (Edit Leg) matches the rally's meal requirement so the time is in the schedule.

Importing a points file

Some rally masters publish the bonus locations and the bonus point values as two separate files β€” a codes/lat/lon file, and a second file (usually CSV, sometimes plain text) with just the bonus code and its point value, sometimes released later than the location file. Click Import points… and choose that file to merge it into the current leg.

Import bonus points modal showing 71 code/points pairs read from a CSV file, with a status column reporting no match in this leg for each row so far
The Import bonus points preview β€” Code, New points, Current points, and a Status column flagging codes with no matching bonus in the current leg.

Unlike Import file…, this never adds or removes rows β€” it only matches each code in the file against a bonus already in the leg's grid and updates its Points column. A preview lists every code from the file, whether it found a match, and its current vs. new point value, so you can check for typos or mismatched codes before applying anything.

Matching ignores case and extra whitespace in the code, since the two files often come from different sources. Codes in the file with no matching bonus in the current leg are listed but skipped β€” nothing is created for them.

Rally-book route options

Many rally books define their own predefined route choices β€” ride every bonus on a list (e.g. "AAAA6," 3229 miles, 372 points) and claim that option's own lump-sum bonus on top. Click Route Options… in the grid toolbar to see this leg's own list, straight from the rally book PDF, with each option's code, mileage, points, and full bonus checklist right next to your grid β€” no need to keep re-reading the PDF to remember which bonuses a given option needs.

Route options modal listing several rally-book route choices, each with its own mileage, points, bonus checklist, and an Import as Route button
This leg's rally-book route options β€” Import from PDF (re)reads the list from a rally book PDF; each card's own Import as Route turns it into a real, saved Route Planner route, and the βœ• removes just that card from this reference list.

This list is purely a reference β€” importing it, removing a card, or clicking Import as Route never touches your grid's scoring or the Combo column above it. Import as Route only works once every bonus on that option's checklist is already in your grid (import or add them first if any are missing) β€” it then creates a new, independent Route Planner route with those bonuses as its stops, same as building one by hand. Import All as Routes does that for every option in the list at once. Re-clicking Import from PDF replaces this whole reference list with a fresh parse of the PDF β€” it doesn't touch any routes you've already created from it.

Exporting GPX & XLSX

The toolbar's right-hand buttons export the current leg (or the whole rally, for GPX):

  • Export GPX β€” waypoints for the current leg, ready to load onto a GPS.
  • Export GPX (whole rally) β€” every leg's bonuses in one file.
  • Export XLSX β€” a spreadsheet copy of the current leg's grid.

Check ASCII-fold export (on by default) to strip accented characters from exported names β€” useful for older GPS units that don't handle non-ASCII text well.

Want a route line, not just a flat waypoint list? See Building a route below β€” it has its own GPX and KML export with the road-following line included.

Hours & Miles planning

Click Hours & Miles next to Grid and Map in the toolbar to open this rally's planning worksheet β€” how much riding time a leg actually has once rest, gas stops, bonus stops, and routing time are subtracted, and how many miles that riding time makes possible. It covers 1 to 3 legs, and use the Legs +/βˆ’ control at the top to match however many legs your rally has. Everything here is saved per rally and shared across every leg, the same as combo codes.

Hours and Miles view for a 3-leg rally showing a Checkpoints table with four looked-up addresses and a centered Legs table with stop-time assumptions, Rest hrs, # Gas stops, Gas stop hrs, # Bonus stops, and Bonus stop hrs columns, plus a bold Rally totals row summing across all three legs
The Hours & Miles view β€” a Checkpoints table (address, then Look up for coordinates and time zone) and a Legs table (your inputs on the left, computed hours/miles/fuel on the right, and a bold Rally totals row along the bottom).

Rest hrs, # Gas stops, Gas stop hrs, # Bonus stops, and Bonus stop hrs show each leg's real total β€” not just the daily rate you typed into Rest hrs/day, Gas stops/day, etc. β€” correctly accounting for legs that span more than one day (a 61-hour leg at 4 gas stops/day works out to 10.17 gas stops for the leg, for example). The bold Rally totals row sums Rest hrs/day, Gas stops/day, Gas stop min, Bonus stops/day, and Bonus stop min across every leg in use β€” 4 rest hours on each of 3 legs shows 12, not 4 β€” while Avg MPH, Avg MPG, and Fuel $/gal still show an average, since adding those together wouldn't mean anything.

Each leg is bounded by two checkpoints β€” its start and its end. Type an address for each checkpoint (city and state is usually enough) and click Look up to resolve it to coordinates and a time zone; that's the one place this page calls out to Google. A 2-leg rally shares its middle checkpoint (leg 1's end is leg 2's start), so you'll only ever look up legs + 1 checkpoints total, not two per leg.

For each leg, fill in its start and end date/time and your planning assumptions β€” routing hours, planned rest hours per day, gas and bonus stops per day and how long each takes, any misc hours, and your Avg moving MPH, fuel economy, and fuel cost per gallon. Leg hours, riding hours available, and miles possible update automatically as you type, and the bold Rally totals row at the bottom of the Legs table adds them up across every leg in use β€” averaging the per-day assumptions over however many legs you actually have, rather than always dividing by three.

Avg moving MPH is your speed only while actually riding β€” never blended with rest, gas, bonus-stop, or misc time, which this table already subtracts out on its own into Riding hrs before multiplying by Avg moving MPH to get Miles. It's a separate number per leg (not pulled from your Rider Profile), since real moving speed tends to vary rally to rally more than a personal baseline does. See Rider profile for the fuller explanation of "moving" speed, which means the same thing everywhere the app asks for it.

Like the bonus grid, changes save automatically β€” watch the small save indicator in the toolbar. Only your inputs are stored; every hours/miles/fuel figure is recalculated from them each time you open this page.

Once a leg block here has both dates and both checkpoints looked up, its Miles possible number automatically feeds the bonus grid and map's Range flag for that same leg β€” matched by position (this worksheet's Leg 1 to your rally's first leg, Leg 2 to its second, and so on). See The bonus grid for what that flag means.

Bonus point planning

Click Points next to Hours & Miles in the toolbar to open this rally's bonus point plan β€” how many points each leg needs, and how your planned route and actual score compare to that target. Like Hours & Miles, it covers 1 to 3 legs (use the Legs +/βˆ’ control at the top), and everything is saved per rally, shared across every leg.

Points planning view for a 1-leg rally showing target points, non-riding bonus columns, a red Points needed column, planned route points, and a bold Rally totals row
The Points planning view β€” target and non-riding bonus inputs on the left, the red Points needed column, planned-route and actual-scored comparisons on the right, and a bold Rally totals row along the bottom.

For each leg, enter the Target points the rally master published for that leg, then your planned non-riding bonuses β€” rest bonus, both call-in bonuses, tracking bonus, and arrival bonus. The Gold target (+40%) column, each bonus's percent of target, the Non-riding total, and the red Points needed column (how many bonus points your route still needs to hit target once non-riding bonuses are counted) all update automatically as you type.

Fill in Planned route pts with the bonus total from your planned route in Basecamp or your mapping program, and the Diff vs target column shows whether that's enough β€” it turns pink when you're short. After the rally, fill in Actual scored to see your final +/− vs target for each leg. The bold Rally totals row adds every column up across all legs in use.

Changes save automatically β€” watch the small save indicator in the toolbar. Only your inputs are stored; every gold target, percentage, and points-needed figure is recalculated from them each time you open this page.

Map & weather

Map view

Click Map next to Grid in the toolbar to switch views. Each bonus is plotted as a marker whose shape encodes its availability (circle, square, flag, diamond, star, triangle β€” see the legend) and whose color encodes its point value. Combo bonuses (AC/DC/TC) get a bolder outline.

Map view with dozens of colored bonus markers and a legend explaining shapes and colors
Map view for a leg with many bonuses plotted β€” the legend in the lower-left explains the shape/color encoding and shows a running total of plotted points.

Click any marker to see its details in a popup, including a one-click link to its weather forecast.

Map marker popup showing bonus code, points, availability, timezone, address, and a 10-day weather button
A marker popup β€” availability, timezone, address, and a shortcut to the 10-day forecast.

A marker shown dimmed and grayed-out is the same Range flag as the bonus grid's Range column β€” a bonus a round trip from Start to it and back to End can't fit inside this leg's Hours & Miles budget (see the bonus grid for how that budget is matched to each leg). It's still fully clickable and still shows on the map either way β€” never hidden or removed, only dimmed β€” so the bonuses actually worth planning around stand out.

Map view with a hovered marker's tooltip reading HURR β€” 5566 pts Β· Out of range
Hovering a flagged marker shows "Out of range" right in its tooltip, alongside its code and points.

Building a route

Pick the bonuses you want to ride, in order, and the app draws a route line on the map with a stop count, distance, and estimated ride time β€” then export it as its own GPX or KML file, separate from the plain bonus-list exports above.

Two ways to add stops, and you can mix both on the same route:

  • In Grid view, check the bonuses you want (same checkboxes used for delete/ lookup) and click Add Selected to Route.
  • In Map view, click Route Mode: Off (top-right) to turn it on, then click bonus markers in the order you'd ride them β€” a numbered badge appears on each one you've added. Click again to remove a stop. Turn Route Mode back off to go back to clicking markers for their normal popup.
Bonus grid with several rows checked via their checkboxes and the Add Selected to Route button active in the toolbar
Check the bonuses you want in Grid view, then click Add Selected to Route β€” order follows the grid's row order, not the order you checked them in.
Route Planner panel open after adding stops from the grid, showing the Route picker, Start/End fields, and the resulting stop list, with the bonus grid visible behind it
The selected bonuses land in the route as new stops β€” open Route Planner… to see them in the stop list, reorder them, or mix in more stops from Map view.

Many rally legs start and end at the same bonus location. To close a loop like that, click the route's first stop again once you've added the rest of the stops β€” instead of removing it, that adds it a second time as the final stop, and its map marker shows both stop numbers (e.g. "1 & 6"). Click it once more to undo the loop and go back to a one-way route. To remove a specific occurrence of a repeated stop (say you want to drop the closing one but keep the bonus as the start), use the βœ• in the Route Planner panel's stop list instead of the map marker β€” it removes exactly the one you click, not every use of that bonus.

Map view of a 12-stop loop route with the start/end bonus marker labeled 1 & 12 (Start/Finish), the header buttons, the Route Planner toolbar, and the Radar toggle highlighted
A closed loop route β€” the start/end bonus's marker shows both stop numbers, "1 & 12," plus "(Start/Finish)" since it's also set as this route's Start and End point. (The header's 🏍 Rider Profile/β›½ My Motorcycles buttons, the Route Planner toolbar, and the Radar toggle are visible here too.)
Map view toolbar with the Route Planner… button highlighted
Map view's toolbar β€” Add Selected to Route picks up whatever's checked in the grid, Route Planner… opens the route panel, and Route Mode (top-right of the map) is what turns marker clicks into route stops instead of popups.
Map with Route Mode on, sixteen numbered stops connected by a dashed straight line, and a Route 8: 16 stops summary in the toolbar
Route Mode on β€” each click adds a numbered stop, connected by a dashed line until a road route's been calculated (see below).

Click Route Planner… in the toolbar any time to open the route panel: drag stops (☰) to reorder, click βœ• to remove one, and set your Avg moving speed and minutes-per-stop β€” those two feed the estimated ride time. Start date/time defaults to the leg's own start date/time but is yours to change (say the route doesn't start the instant the leg does) β€” set it and the panel shows an estimated finish time too. Recalculate Route refreshes the road distance and the map's route line from Google's road routing (with OpenRouteService as an automatic backup), then shows a Route calculated summary that includes which routing engine was used; Save Route keeps the route for next time you open this leg; Delete This Route deletes it. Export Route GPX downloads the stops as a route for Basecamp/Garmin β€” the GPS recalculates the actual road path itself when you activate the route, so the file doesn't carry a separate road-line track. Export KML downloads the stops and the road-following line (Google My Maps/Earth have no route-recalculation feature of their own, so the line is the only way to see the road path there).

Route Planner modal with the Route picker, Start/End pickers with address search, Fuel range/Motorcycle fields, the AI Suggested Route button, Find Gas Stations, Build/Print Route Schedule, and the resulting schedule with warnings all highlighted section by section
The full Route Planner panel, section by section: the Route picker at top; Start/End (pick a bonus, search an address, or drop a pin on the map); your pace, stop-time, and fuel assumptions; 🎯 AI Suggested Route's candidate-pool button; β›½ Find Gas Stations; πŸ“… Build/πŸ–¨ Print Route Schedule; and the resulting timeline with its advisory warnings.

Click the ℹ️ Route Info button (next to the route-stats line near the top of the panel) any time for a clean, screenshot-friendly summary: every stop broken down by kind β€” Bonus, Gas, Rest, and Lunch stops, plus a Total β€” followed by the route's points, Distance, Riding time, and Points-per-mile efficiency. The points are broken down as Bonus points (the stops' own points), With scoring rules (when the rally has scoring rules, including Extra points), one line per combo the route completes (e.g. Combo CMB5 +1,000), and the Total score. Points per mile uses the total score. If the built schedule finishes after the leg's deadline and the rally has a Late penalty rule, a penalty row shows what the late finish would score. Gas/Rest/Lunch counts and the Total row only show up once you've clicked πŸ“… Build Route Schedule for this route (see below) β€” until then, the popup offers a Build Schedule Now button in their place instead of showing stale or missing numbers.

Route Info popup listing Bonus Stops, Gas stops, Rest stops, Lunch stops, Total stops, Points, Distance, Riding time, and Points per mile for a 9-stop route
The ℹ️ Route Info popup β€” every stop-count row grouped together, Bonus Stops first, followed by the ride's other headline numbers.
Route Planner modal after Recalculate Route, now showing road-distance stats and OSRM driving estimate, with a Route saved confirmation dialog
Recalculate Route swaps the straight-line estimate for a real road distance (plus the routing service's own driving-time estimate, shown for reference only) β€” Save Route then confirms once it's stored.
Map view with a solid road-following route line through seventeen numbered stops and a Route 4: 17 stops, 3402.3 mi (road), 54h 17m summary in the toolbar
The finished route β€” a road-following line through every stop, with a running summary in the toolbar even when the panel's closed.

The road distance/line comes from Google's routing service, with OpenRouteService as an automatic backup if Google is unavailable. The stats line names whichever one was used, e.g. "(road, Google)". If both are unavailable, the map shows a dashed straight line instead and labels the distance as an estimate, so it's never mistaken for the real road distance. The estimated ride time is always calculated from your own speed/stop-time settings, not a car-driving estimate.

Start, End, and your motorcycle

The Start and End pickers each accept either an existing bonus (the dropdown, same list as the grid) or a custom point β€” a hotel, rally HQ, or any other spot that isn't itself a bonus. Two ways to set a custom point:

  • Type an address into the search box above Set from map… and click πŸ”Ž Find (or press Enter). Works best with a city/state included β€” "Hampton Inn, Springfield IL" rather than just "Hampton Inn" β€” since it's a street-address lookup, not a full place-name search. The label defaults to whatever you typed; the line underneath shows the address it actually found, so you can confirm it landed in the right spot before relying on it.
  • Click Set from map…, then click anywhere on the map to drop a pin by hand and give it a label β€” the fallback for anywhere the search box can't resolve.

If this leg has a saved Start/End location β€” set in the leg's own edit popup, see Creating a leg β€” the Start and End pickers here default to that location automatically, the moment you open this leg or start a new route for it, so you're not re-typing or re-searching the same hotel address every time. You can still change or clear either one for this specific route same as before; it only sets the starting point.

Map view for Leg 1 with a green Start pin labeled 777 Aten Rd, Coraopolis, PA and a red/white Finish pin labeled 6110 S Yale Ave, Tulsa, OK, connected by a dashed line
Leg 1's saved Start/End locations, filled in automatically and shown on the map β€” 🟒 Start at the rally's home base, 🏁 Finish at that night's hotel in Tulsa, OK.
Map view for Leg 2 with a green Start pin labeled 6110 S Yale Ave, Tulsa, OK and a red/white Finish pin labeled 7007 S Clinton St, Greenwood Village, CO, connected by a dashed line
Leg 2 of the same rally β€” its Start is the very same Tulsa hotel Leg 1 just ended at, filled in automatically since Leg 2's own start location was never set separately (see Creating a leg for how that hand-off works).

A bonus picked as Start/End gets "(Start)"/"(Finish)" added to its existing map marker; a custom point gets its own 🟒/🏁 marker instead. The Motorcycle dropdown lets you attach one of your saved motorcycle profiles to this route β€” it's saved with the route so you know which bike it was planned for, and it fills in Fuel range (mi) from that bike's own tank/consumption numbers (switching bikes updates it again); overwrite it with your own number any time if you'd rather. A fresh route also starts with Avg moving speed and Minutes per stop pre-filled from your rider profile, instead of a generic guess.

🧠 The Big Brain

🧠 The Big Brain is the heavy-duty route planner. Instead of choosing from bonuses you've checked, it considers every bonus in the leg that has coordinates and offers you the three best different routes it can find.

Before you click it, set the route's Start and End points and its Start date/time, and make sure the leg has an End date/time. These settings are used:

  • Your average speed (or Pace vs. drive time, if set) and minutes per stop (the Route Planner's own settings, filled in from your rider profile), and your Big Brain cushion.
  • The rally/leg's rest and lunch rules and your motorcycle's fuel range.
  • Timed and Daylight-only windows: arriving before a bonus opens means waiting for it (up to 4 hours; a ⭐ mandatory bonus waits as long as needed, even to a later day it's open), and arriving after it closes is a miss. A Timed bonus without its structured window (the πŸ• in the Timed column), or a Daylight-only bonus without sunrise/sunset looked up, can't be checked, and the results tell you which ones those are.
  • ⭐ Mandatory bonuses are always included if they can fit at all.
  • Each bonus's β›΄ settings: its "Route to" point and extra minutes. Ferries in Google's road route for the best plan are timed with Google's crossing time plus your Ferry wait allowance.
  • Combos that have Points set, using the bonuses tagged with them in the Combo column. A combo counts when every bonus tagged with it is in the route. When the leg has such combos, The Big Brain first asks how to plan:
    • With combos: routes can go out of their way to complete a combo when its points are worth the extra riding.
    • Without combos: routes choose bonuses on their own points only. A combo a route happens to complete is still counted in its points.
    • Show both: the best routes each way, in two groups, with a line saying how many points planning for combos is worth on the best route. It takes about twice as long and uses up to twice as many Google road checks.
  • Your rider profile's riding intensity: relaxed and moderate riders get routes planned to finish a little before the real deadline.

How it works: The Big Brain first does a quick pass (about a fifth of its search time) using straight-line distances (Γ— 1.2), then asks Google for the real road route of that plan and learns from every leg Google measured: how much longer than a straight line the roads really are for short hops, medium hops and long legs, and in which areas (twisty coast and mountain roads versus straight open country). It remembers the exact distance of every leg it checked. The full search then runs with that road knowledge, and its best route is checked with Google too. If that estimate is still more than 1% off, it re-plans and checks again (up to twice), and then fits each of the three routes to its real road distances (see below).

Which service checks what: while it searches and fits, The Big Brain checks routes with OpenRouteService, which is free. Only the final routes it shows you are checked with Google (and fitted again if Google's roads say they don't fit), so a run uses only a handful of Google requests. Each card says which service checked it; if Google's daily limit has been reached, the card says so and OpenRouteService's check is shown.

Checked with Google: all three routes are checked against real roads at the end of a run, and each card shows a Checked with Google line with its finish time on real road distances, in red if it would finish after the deadline or miss a Timed/Daylight window. Routes that really fit are listed first, highest points first. If a check couldn't be done, the card has a Check with Google button to try again.

⚠ Planning in a different season than the rally? Watch for seasonal road closures.

Google and OpenRouteService route on the roads as they are on the day you plan, not on the rally's dates. If you plan a summer rally in winter (or test with an old rally book), mountain passes and other roads that close every year for snow β€” for example OR-242 over McKenzie Pass, Beartooth Highway, Going-to-the-Sun Road, Tioga Pass, and many forest and park roads β€” show as closed, and the router may say there's no road to a bonus on them or send you on a long detour around them.

When Google can't route a hop, The Big Brain fills that one hop from the road distances saved for the rally (or an estimate) and keeps Google's roads for the rest. The route card then says "N hop(s) Google couldn't route today β€” e.g. a road closed for the season". That's usually a seasonal closure, not a problem with the bonus.

The opposite is true too: closures that will happen on rally day β€” summer wildfire closures, construction, events β€” don't show up when you plan months ahead. Before you ride, check the state DOT or park road status for the bonuses on your route, and re-check the route with Recalculate closer to the rally.

Real road distances between nearby bonuses: before planning, The Big Brain gets the real road distance from every bonus to its ~10 nearest bonuses (and to Start and End), so hops across water or over mountains aren't guessed from a straight line. These come from OpenRouteService at no cost and are saved on the server for everyone riding that rally, so only the first run on a rally waits for them (about a minute for 250 bonuses). Ferry crossings Google finds are counted in each route's checked finish time.

Fitted to real roads: if real roads make a route late (or make it miss a window), The Big Brain keeps the route's order and leaves out the bonuses that cost the most time for their points until it fits, then checks it with Google again. If a route has spare time, it adds bonuses where they fit best and checks again, keeping the change only if the route still fits and scores more. The card's Fitted to real roads line says what was left out or added. This usually takes 2–4 Google road checks per route, so a run uses roughly 6–12 (each is one road route, a few cents).

Think longer: The Big Brain asks how hard to think on every run. Normal runs one search (up to about 30 seconds, plus the road checks). Think longer runs four complete searches β€” one for routes heading north from the Start, one east, one south and one west β€” fits every route they find to real roads, and keeps the 3 best different routes, so a good route in a less obvious direction isn't missed. Each card says which way it heads. It takes about four times as long as Normal and uses about four times the Google road checks (a few cents each). Every search, Normal included, also tries starting toward the best bonuses in each of 8 compass directions. You can cancel while it runs.

Slow roads take longer: The Big Brain (and Build Route Schedule, after Recalculate Route) uses the drive time Google or OpenRouteService gives for each leg, compared with that service's average: legs through towns, cities or on twisty roads take proportionally longer than your average speed, interstate legs a bit less (at most 1.3Γ— your average), so over a whole route you still average your own speed β€” the time just lands on the right legs. Google's times here don't include live traffic, so for a big-city cluster at rush hour, add a few minutes per stop.

πŸ“₯ Importing a GPX route (e.g. from Garmin BaseCamp)

If you plan in BaseCamp (or any app that exports GPX), you don't have to rebuild the route by hand:

  1. In BaseCamp, export the route (File β†’ Export, or right-click the route β†’ Export) as a .gpx file.
  2. In the Route Planner, pick or create the route to load it into (+ New Route keeps your current one), and set its Start/End and start time.
  3. Click πŸ“₯ Import GPX Route and choose the file. Its route points become the stop list, in the same order. Each point is matched to a bonus in this leg by the code at the start of its name (WIRE-581 β†’ WIRE, VALD-788-11:00-2:00 β†’ VALD) or, failing that, by location (within about ΒΌ mile). Shaping points, your hotel and gas stops aren't bonuses, so they're skipped and listed.
  4. The road route is recalculated and the app offers to run 🧠 Review my route right away. Click Save Route to keep the imported stops.

If the file has no route, its waypoints are used in file order. Importing replaces the current route's stops (you're asked first).

πŸ“– Printing a bonus book

πŸ“– Print Bonus Book (next to Print Route Schedule) opens a printable page with one block per bonus in riding order: its number, code, name and points; its hours (Timed window, or Daylight-only sunrise–sunset) and ⭐ if mandatory; address; GPS in degrees-minutes and decimal; any combo it's part of with the combo's points; extra access minutes; and the bonus's description and photo instructions from the rally book. Click πŸ“… Build Route Schedule first to include your arrival time at each bonus. Print it, or save it as a PDF for your phone or tank bag.

Pace vs. drive time (%): optional, on the route screen next to Avg moving speed. Instead of one average speed, every leg is planned at a percent of Google's drive time for it β€” 100 = Google's time, 90 = 10% faster, 110 = 10% slower β€” the way many riders set their BaseCamp speeds ("I ride about 10% faster than BaseCamp"). Leave it blank to use your average speed. Legs with no drive time yet (before a road check) always use your average speed. It's used by The Big Brain, Review my route and Build Route Schedule (after Recalculate Route), and remembered on this device.

🧠 Reviewing your own route

🧠 Review my route: if you planned your own route (in BaseCamp or by hand), put its stops in the route list in your riding order β€” or import its GPX β€” and click Review my route. The Big Brain checks it on real roads with Google and shows up to four cards: your route as planned (finish time and a route check), your route improved in the same order (stops it would skip if you're late or miss a window, and bonuses it would add where you have spare time), and up to two reworks it finds starting from your route. Each improvement says what it adds and drops and how many points and minutes that changes. Nothing replaces your route unless you click Use this route.

Tip: run the review at the pace you'll really ride (average speed or Pace vs. drive time, minutes per stop, Big Brain cushion) β€” the "as planned" card tells you honestly whether your route fits at that pace, and the improved card shows the cheapest way to make it fit.

Route check: every Big Brain card has a Route check you can open: Timed and Daylight-only bonuses reached with 45 minutes or less to spare (or that you'd wait for), stops that earn noticeably fewer points per minute than the rest of the route (the first to skip if you run behind), and stops whose description mentions a walk, trail, fee, gate, closing time, tour road, refuge or ferry β€” set extra minutes for those with the β›΄ in the grid.

Download test data: after a run, the ⬇ Download test data button saves a file with exactly what that run used β€” your bonuses, settings, start and finish, scoring rules and combos, the real road distances and drive times it learned, and the routes it found. Send it to the developer when a result looks wrong, so The Big Brain can be tested on the same data.

Big Brain cushion: set on the route screen (default 60 minutes, remembered on this device). The Big Brain plans and fits every route to finish at least that long before the leg's deadline, so a slow stretch or a long gas stop doesn't make you late. A route that's on time but inside the cushion is shown in orange. Set it to 0 to plan right up to the deadline.

Reading the results: each route shows its points (including any combo bonus), the number of stops, miles, the finish time with rest/lunch/fuel stops included, and how much time is left before the deadline. If you ride slower shows the finish if every ride between stops takes 10% or 15% longer than planned. A route marked ⚠ late at 10% has very little slack, so you may prefer an alternative with fewer points but more cushion. Click Use this route to load it into the Route Planner. It replaces your current stop list, recalculates the road route and builds the schedule, but nothing is saved until you click Save Route.

Like every route estimate in the app, it plans at a flat average speed. If you know a route goes through a lot of towns, choose one with more cushion, or lower your average speed before running it.

🎯 AI Suggested Route

Where Optimize Route (below) only reorders stops you've already picked, 🎯 AI Suggested Route picks which bonuses to ride in the first place β€” and in what order β€” out of a pool of candidate bonuses you check off, aiming to score the most total points while still getting you back to your End point by the leg's own end date/time.

Set these up first

Two of these are required β€” 🎯 AI Suggested Route simply won't run without them, and tells you which one's missing if you click it too soon. The rest are optional and fall back to sensible defaults, but are worth setting once so every route you plan uses your own numbers instead of a generic guess.

  1. Your Rider Profile (optional). Sets your average moving speed and preferred stop length β€” pre-fills Avg moving speed and Minutes per stop below on every route. Skip it and those default to 55 mph / 15 minutes instead.
  2. A motorcycle profile (optional). Pre-fills Fuel range (mi) from that bike's tank size and MPG. Skip it, or don't pick one from the Motorcycle dropdown, and the route defaults to a flat 200-mile fuel range instead.
  3. The leg's Start and End date/time (required). Set under Creating a leg when you create the leg, or any time after via its ✎ edit button β€” this is per-leg, not a rally-wide setting, so a multi-leg rally needs it set on each leg separately. 🎯 AI Suggested Route uses the leg's End date/time as its hard deadline for getting back to your End point, so it refuses to run without one.
  4. Rest stop and/or lunch break rules (optional β€” only if your rally requires them). Set on the rally itself (✎ next to the rally name) so every leg uses the same rule by default, or override a specific leg individually (✎ next to that leg) β€” the fields are Rest stop every (hours)/Rest stop duration (minutes) and the matching Lunch break every (hours)/Lunch break duration (minutes), both optional clock-time windows, and a Required every day checkbox for Iron Butt-style "once per calendar day" rules instead of an hours-since-last-stop interval. Leaving a leg's fields blank inherits whatever the rally has set; leaving both blank means that rule simply isn't required. One exception: if you leave the rest-stop interval/duration blank on both the rally and the leg, it quietly falls back to your Rider Profile's own "How often do you want a break?"/"How long is each break?" answers instead of skipping rest stops entirely β€” lunch has no such personal fallback, so a lunch break only ever happens if the rally or leg actually asks for one. See Rest, lunch & fuel schedule below for exactly how these get applied once a route's built.

Then, build your candidate pool

A pool of candidate bonuses β€” bonuses you'd be willing to ride if they make the cut, not a final list. Two ways to do this, and they both feed the exact same pool so you can mix and match:

  • Check them off in the bonus grid's checkbox column, same checkboxes Add Selected to Route uses.
  • Switch to Map view and turn on the 🎯 AI Candidates toggle (next to Route Mode) β€” then click bonus markers on the map to check/uncheck them. A checked bonus gets a small amber ring around its marker so you can see the pool build up as you click. AI Candidates and Route Mode are mutually exclusive β€” only one can be on at a time, so a click always means one clear thing (check a candidate bonus, vs. add/remove an actual stop).

Any bonus you've marked ⭐ Mandatory joins the candidate pool automatically, whether or not you've also checked it here or on the map β€” starring it is enough by itself, and it's treated as a hard requirement rather than an ordinary candidate bonus once the search runs (see "Click it" below).

A checked (or ⭐ mandatory) bonus only actually joins the candidate pool if it has coordinates on file β€” an ordinary candidate bonus that's never been looked up (see Looking up address & timezone) is silently skipped rather than breaking the run, but a mandatory one missing coordinates is called out up front instead β€” see below.

Then fill in the route fields

See Start, End, and your motorcycle above for the full explanation of each β€” quick reference:

  • Start / End β€” an existing bonus from the dropdown, an address typed into the search box (works well for a hotel with its city/state, e.g. "Marriott, Chicago IL" β€” see above for why a bare business name alone can fail), or a pin dropped by hand with Set from map…. In some rallies the start/end hotel is itself one of the imported bonuses β€” check the dropdown first before searching or dropping a pin.
  • Start date/time β€” pre-filled from the leg's own Start date/time (step 3 above); change it here any time the route itself won't start the instant the leg does.
  • Avg moving speed (mph) β€” pre-filled from your Rider Profile (step 1); overwrite it for just this route any time, including to see how a slower or faster pace changes whether Daylight-only bonuses stay reachable.
  • Minutes per stop β€” same source as above, and same "just this route" override. This is dwell time at each bonus stop only β€” fuel stops use their own fixed ~15-minute dwell regardless of this setting.
  • Fuel range (mi) β€” pre-filled from the Motorcycle dropdown (step 2), or 200 mi flat if none is picked; overwrite it any time.

Click it

With everything above in place, click 🎯 AI Suggested Route. It replaces your current stop list with whichever subset and order of your checked candidate bonuses scores the most points, while respecting:

  • ⭐ Mandatory bonuses β€” every bonus you've starred (see ⭐ Marking a bonus mandatory) is treated as a hard requirement and seeded into the route first, in its own pass, before the normal points-per-hour search runs β€” whether or not you also checked it. A low-value mandatory bonus can no longer lose its spot to a higher-value optional one the way it could before this existed; if the leg's time doesn't stretch to cover both, it's one of your checked, non-mandatory bonuses that gets dropped instead.
  • The leg's own deadline β€” it never builds a route that gets back to End later than the leg's End date/time.
  • Timed and day/time-specific bonuses β€” a bonus with a Timed window, or one only available on specific day(s), is only included at a position where it's actually reachable inside that window.
  • Daylight-only bonuses β€” only included where the schedule has you arriving between that bonus's own sunrise and sunset, using the sunrise/sunset already looked up for that bonus (see Looking up address & timezone) β€” nothing new is fetched to make this decision.
  • Rest, lunch & fuel stops β€” the rules from "Set these up first" above, applied exactly as described in Rest, lunch & fuel schedule below.

A candidate bonus with no structured Timed/Daylight window data on file isn't excluded just because it can't be checked β€” it's left in as a soft, visible warning on the built schedule instead (same as a manually-built route already shows), never silently dropped for being unverifiable. Specifically for Daylight-only bonuses, if the sunrise/sunset lookup was simply never run for one or more of your candidates (see Looking up address & timezone), 🎯 AI Suggested Route warns you about it before the search even starts, naming which ones β€” a chance to cancel, run Look up selected/missing, and try again, or continue anyway knowing the search will treat those bonuses as if they had no daylight restriction at all.

If a ⭐ mandatory bonus has no coordinates on file at all, 🎯 AI Suggested Route stops and tells you before it even runs the search β€” an ordinary candidate bonus missing coordinates is just quietly skipped (see above), but a mandatory one is important enough that you get a chance to fix it, or knowingly continue without it, rather than finding out only after the fact.

When it's done, a confirmation tells you the total points scored, how many candidate bonuses made the cut vs. were left out, and β€” for smaller candidate pools β€” the specific reason each excluded one didn't fit (missed its window, or couldn't be fit in without blowing the leg's deadline). If a ⭐ mandatory bonus genuinely couldn't be made to fit anywhere it was tried, that's called out on its own line β€” "⚠ N mandatory bonus(es) could NOT be included…" β€” ahead of and separate from the ordinary list of optional bonuses that simply didn't make the value cut, so it's never easy to miss. It also builds the full rest/lunch/fuel schedule for you automatically β€” the same one πŸ“… Build Route Schedule produces by hand β€” so any Daylight-only or Timed bonus your resulting arrival time would actually miss, or couldn't be verified at all, both shows up in the timeline below at the exact stop it applies to and gets a total count called out right there in the same completion popup ("⚠ The built schedule has N warning(s) β€” this route may not actually be valid"), so it's never something you'd only notice by scrolling down. Like everything else in the route planner, nothing is saved to the database until you click Save Route β€” so it's safe to try, look at the result and warnings, tweak the average speed or stop time to see if that fixes a close daylight call, and try again with a different candidate pool if it's still not quite what you wanted. The route it builds is a normal, fully editable route afterward β€” add, remove, or reorder stops by hand same as any other. There's also a hard cap of 50 total stops (start + chosen + end) to match the road-routing service's own limit.

What parameters are used for the AI Suggested Route functionality

Quick reference for everything the search actually reads, and how each one behaves β€” some can change which bonuses get picked, others only ever add a warning to the resulting schedule:

  • ⭐ Mandatory status β€” read straight from each bonus's own ⭐ column in the grid at the moment you click 🎯 AI Suggested Route. Definitely changes which bonuses get picked: a starred bonus is a hard requirement, not just a higher-priority candidate bonus.
  • Avg Moving Speed β€” is pulled from the Route Planner's "Avg moving speed" field. That field is pre-filled from your Rider Profile's average moving speed when you open Route Planner or switch motorcycles, but it's editable per-route, so whatever value is showing in that field at the moment you click 🎯 AI Suggested Route is what's used.
  • Fuel Range β€” pre-filled from the selected motorcycle's tank + aux tank βˆ’ reserve, times MPG, times (1 βˆ’ safety buffer %), but editable, so it's whatever's currently in the "Fuel range (mi)" field.
  • Rest/Lunch Rules β€” come from the resolved leg β†’ rally β†’ (rest only) your Rider Profile's break-interval/duration as a fallback, but only if neither the leg nor the rally has its own rest interval and duration set. Lunch has no rider-level fallback at all β€” leg β†’ rally β†’ none.
  • Night Riding Preference β€” is read from your Rider Profile, but it's advisory only. It never changes which bonuses get picked or excludes a route; it only adds a warning to the resulting schedule if a stop would be reached after dark.
  • "How Hard Do You Ride?" / Intensity β€” scales the pre-filled "Avg riding speed" default (relaxed βˆ’8%, moderate unchanged, aggressive +8% β€” still editable per-route), and gives 🎯 AI Suggested Route's search a safety buffer before the leg's real deadline (relaxed β‰ˆ8% of the leg's own window held back, moderate β‰ˆ3%, aggressive 0 β€” the full window, same as before this feature existed). Unlike night riding and bad weather, this one can change which bonuses get picked. When a buffer is applied, the results popup says so in plain language.
  • "Riding In Bad Weather / Rain" β€” an advisory-only warning, same pattern as night riding: it never changes which bonuses get picked. It only fires when you've already looked up the 10-day forecast for a bonus (grid's ☁ column, or a popup's "10-day weather" button) during this browser session, and that cached forecast's condition looks rainy/stormy/snowy on the day the schedule would actually reach that stop. No new API calls are made on your behalf β€” if you haven't looked up a bonus's weather, no warning can appear for it, regardless of preference.

Route optimizer

Optimize Route reorders your existing stops for the shortest overall ride, keeping any Start/End you've set fixed at the ends. It never adds or removes stops β€” bonus selection stays entirely your own manual pick β€” and it automatically recalculates the real road route afterward, so the map never shows a stale straight line after optimizing.

Under the hood, it asks for real road distances between every pair of your stops (one request covers the whole set, up to 50 stops) and uses those to work out a short overall order β€” good, not necessarily mathematically perfect, but close enough that hunting for a better one by hand isn't worth the effort. If road distances are briefly unavailable, or the route has more than 50 stops, it falls back to straight-line distances instead of failing outright, and tells you so.

Once it's done, a message tells you exactly what changed β€” how many stops moved (and which ones, by name, for smaller routes), plus roughly how much distance the new order saves. If your stops were already in the shortest order, it tells you that too, rather than leaving you to wonder whether the click did anything.

Detailed technical explanation of how the route optimizer works: nearest-neighbor construction, 2-opt local search improvement, the road-distance matrix request, and the fallback to straight-line distances
A closer look under the hood, for anyone curious exactly how Optimize Route finds a short order: it builds a rough starting order (nearest-neighbor), then repeatedly improves it (2-opt) until no single swap shortens it further.
Confirmation dialog reading: Stop order optimized β€” 2 of 17 stop(s) moved (NJAC-989-A, NJV-623-D), cutting about 20.0 mi of road distance off the route.
The confirmation shown after optimizing β€” which stops moved and roughly how much shorter the new order is.

β›΄ Ferries & hard-to-reach bonuses

Some bonuses involve a ferry. How you handle one depends on whether Google's road maps know about that ferry.

Ferries Google knows about: nothing to set up

Google's road routes already include car ferries that carry vehicles, such as BC Ferries to Vancouver Island, Washington State Ferries, the Outer Banks ferries and the Lake Michigan car ferries. When your route needs one, Google puts the crossing in by itself and the app:

  • uses Google's crossing time for the miles on the boat, instead of counting them as riding at your average speed, and
  • adds your Ferry wait (min) for each crossing. It's in the Route Planner next to Fuel range, defaults to 30, and is remembered on this device. Google doesn't use departure times for driving routes, so set it from the ferry schedule for your day.

After Recalculate Route, the Route calculated popup shows a Ferry crossings line, for example "2 (278 min on the boat + 60 min wait, included above)". The route schedule shows each crossing as its own β›΄ line, and 🧠 The Big Brain includes them in its best route's finish time.

Ferries Google doesn't know about: use the bonus's β›΄

If a bonus is on an island with no car ferry Google knows, for example Mackinac Island where motor vehicles aren't allowed, Google can't build a road route to it. When you click Recalculate Route you'll see a message like:

"Could not calculate a road route: MIMI (45.84880, -84.61830) has no road within about 350 m of its coordinates, so neither Google nor OpenRouteService could route to it…"

To fix it, tell the app where the road part ends and how long the rest takes:

  1. Find the ferry dock you'll leave from. In Google Maps, right-click the dock or its parking area on the mainland side, then click the coordinates at the top of the menu to copy them.
  2. Open the bonus's β›΄. In the grid, find the bonus's row, hover over it, and click the faint β›΄ just right of the πŸ• column.
  3. Route to: paste the dock's coordinates, for example 44.12345, -85.67890. Road routes now end at the dock. The bonus keeps its own coordinates on the map and in the GPX.
  4. Extra minutes: enter the total time from arriving at the dock to riding away from it again. Include:
    • waiting for a departure (check the ferry schedule for that day)
    • the crossing there, plus loading and unloading the bike if it goes with you
    • getting from the island dock to the bonus and back
    • waiting for a return boat, and the crossing back
    Don't include the photo time itself: your normal Minutes per stop is already added to every bonus. Leave Ferry wait alone too; it's only for ferries Google finds on its own.
  5. Save, then click Recalculate Route. The popup shows an Extra bonus time (β›΄) line with your minutes, and they're included in the ride time and finish. In Build Route Schedule that bonus's stop is longer by your extra minutes.

Once set, the β›΄ shows at full strength on that bonus, and hovering it shows what's set. Road routes, the schedule, Optimize Route, 🎯 AI Suggested Route and 🧠 The Big Brain all use these settings. If The Big Brain finds a bonus with no road to it and no β›΄ Route to, it leaves that bonus out, plans again, and tells you which one it left out, so you can set its β›΄ and run it again.

The same β›΄ works for any bonus you can't ride right up to: a long walk from the nearest parking, a gated site where you park outside, or a shuttle. Set Route to the parking spot and Extra minutes for the walk or shuttle. Clear both in the β›΄ dialog puts the bonus back to normal. β›΄ settings aren't included in the Excel export or import.

Rest, lunch & fuel schedule

πŸ“… Build Route Schedule goes a step further than distance/time stats: it builds a full timeline β€” arrival and departure at every stop β€” inserting rest, lunch, and fuel stops wherever they'd actually trigger (even mid-leg, if one stretch is long enough to need more than one). It uses your rider profile and the rally/leg's rest & lunch rules where set, falling back sensibly when either is missing, and flags β€” but never blocks β€” any Daylight-only or Timed bonus your arrival time would miss. Every warning is advisory only; re-running it after any change is one click away.

Waiting for a bonus to open. If the schedule reaches a Timed or Daylight-only bonus before it opens that day, it now shows a Wait for … to open line and continues from the opening time, the way you'd actually ride it, instead of flagging the bonus as missed. It waits up to 4 hours; arriving earlier than that, or on a day the bonus isn't open, is still flagged. 🧠 The Big Brain plans the same way.

The rest/lunch rules themselves live on the rally (Edit under the rally in the sidebar) and can be overridden per leg (Edit next to the leg) β€” Rest stop every (hours)/Rest stop duration (minutes) and the matching Lunch fields, all optional. A leg left blank inherits the rally's value for that field; a rally left blank means "not required" for it.

Rest and lunch can each also require the mandatory stop to start within a specific clock-time window β€” Rest window start/Rest window end (e.g. an Iron Butt-style 11:00 PM–4:00 AM overnight window) and Lunch window start/Lunch window end (typically daytime, e.g. 11:00 AM–4:00 PM) β€” set independently of each other; both fields in a pair need a value for that window to apply. Once a stop is due, Build Route Schedule checks the clock: if it's already inside the window, the stop starts right then (and still runs its full required duration even if that extends past the window's close). If not, rather than showing the rider as parked and idle, the timeline simply keeps going as normal riding β€” any fuel or other due stops in between still appear exactly as they would anyway β€” right up until the window opens, at which point the rest/lunch stop starts there, with its required duration counted only from that moment. A rest stop and a lunch stop are never combined into a single stop even if both happen to be due around the same time β€” whichever one's window opens sooner takes its stop first, and the other follows immediately after.

Some rallies (Iron Butt-style ones especially) require the rest and/or lunch stop every single day of the rally β€” including day 1 β€” landing inside that rule's window, rather than every so many hours. Check Rest required every day (or Lunch required every day) on the rally to switch that rule to this daily mode; a rally uses either the hours-based interval or daily mode for a given rule, never both at once, and daily mode only takes effect when that rule's window is also set (a specific clock-time target is what "once a day" anchors to). A leg can override this independently via its own Rest required every day/Lunch required every day dropdown β€” Same as rally inherits the rally's checkbox, or pick Required every day/Not required to explicitly override it just for that leg. If a day's window already closed before it could ever be reached β€” the rally's own start time is already past day 1's window, or a long stop elsewhere ate into the clock β€” Build Route Schedule flags an advisory warning and skips straight to the next day rather than forcing something impossible.

Route Planner panel showing Start/End pickers, a Motorcycle profile, Fuel range, a 12-stop list, Find Gas Stations and Build Schedule buttons, and the resulting timeline with its advisory warnings
The full Route Planner panel β€” Start/End pickers and a Motorcycle profile near the top, then Build Schedule's resulting timeline: fuel stops inserted along the way, a Timed bonus flagged for having no structured window set, and a Daylight-only bonus flagged for an after-sunset arrival.
Build Schedule timeline scrolled down, showing Start, fuel stops, multiple Timed and Daylight-only bonus warnings across three days, and the Finish stop
Scrolled further down the same timeline β€” fuel stops recur every few hours per the motorcycle's range, each Timed/Daylight-only warning appears right at the stop it applies to, and the timeline runs all the way to Finish at the route's End point.

Build Route Schedule's Timed-bonus check uses the structured window set via the πŸ• icon next to the Timed column when there is one, and otherwise the hours in the plain Timed text when it's a single time range β€” see the bonus grid above. Ferry crossings show as their own β›΄ lines, and a bonus's β›΄ extra minutes are part of its stop time β€” see Ferries & hard-to-reach bonuses.

The schedule is saved along with the route the next time you click Save Route β€” reopening the route later shows it immediately, no need to click Build Route Schedule again unless you've changed the stops, Start time, average speed, stop time, or fuel range since (any of those clears the saved schedule, since it's no longer accurate). Use πŸ–¨ Print Route Schedule to open a clean, print-friendly copy of the timeline in a new tab; your browser's Print dialog (Save as PDF) covers keeping a copy as well as printing one.

Multiple routes per leg

A leg isn't limited to one route β€” the Route: dropdown at the top of the Route Planner panel lets you build and save several named route scenarios for the same leg, and switch between them at any time. This matters because Google Maps-based tools (including my separate Route Planner & Cannonball AI app, which this app's GPX route export is designed to feed into) can only handle around 10–25 stops in one route before Google's own routing API rejects the request outright. A leg with more bonuses than that doesn't fit in a single route β€” so instead of forcing every bonus into one oversized route, you can split it into a few smaller ones, each kept comfortably under that limit.

Route Planner modal with the Route dropdown open showing Route 1 and Route 2, a Route 2 name field, a plus New Route button, and a seven-stop list for Route 2
The Route: dropdown lists every saved route for this leg β€” pick one to load its stops, start time, and pace settings into the panel. The name field next to it is editable (it only takes effect the next time you click Save Route), and + New Route starts a blank scenario β€” nothing is written to the database until you add stops and save it. Delete This Route removes whichever route is currently selected; if you haven't saved the current scenario yet it reads Discard Draft instead, since there's nothing in the database yet to delete.
Map view with one saved route selected, showing a 12-stop road-following route and a 12 stops, 3463.8 mi (road), 53h 56m summary in the toolbar
One saved route for this leg β€” 12 stops.
Map view with a different saved route selected, showing a shorter 9-stop road-following route and a 9 stops, 2864.6 mi (road), 44h 23m summary in the toolbar
A different, shorter scenario for the same leg β€” 9 stops covering a different subset of bonuses. Switching the Route: dropdown swaps the map's route line and stats to match whichever saved route is selected.

Exporting GPX/KML from the route panel now names the file after the specific route ("<Rally> - <Leg> - <Route name>"), so exporting two different scenarios from the same leg gives you two distinct files instead of one overwriting the other.

Opening a leg with saved routes doesn't automatically draw one on the map β€” you'll see just the bonus markers until you pick a route from the Route: dropdown (or start a new one). Clear Route from Map, next to the route summary in the toolbar once a route is showing, hides the current route and its gas stops from the map without deleting anything β€” pick it again from the dropdown any time to bring it back.

Map view with a 17-stop route line still plotted and the Clear Route from Map button highlighted in the toolbar next to the route summary
Clear Route from Map in the toolbar β€” click it any time a route is showing to hide the route line and stops from the map. Nothing is deleted; the route is still there the next time you pick it from the Route: dropdown.

Gas station search

Once a route has at least two stops, the Route Planner panel's β›½ Find Gas Stations button searches a local gas station dataset for stops near the route line and suggests where to fuel up along the way. Set Fuel range (mi) to your bike's real tank range first β€” the search places a suggested stop roughly every 90% of that range (a built-in reserve buffer). At each stop, a 24h-reliable station (a truck stop or a known 24-hour brand) is preferred over a regular one when there's a nearby choice β€” if none is nearby, it falls back to the nearest regular station rather than skipping the stop. Click β›½ Find Gas Stations to run it; if the route fits inside a single tank, no stops are suggested.

Route Planner panel with the Find Gas Stations button highlighted, above the Build Schedule button and stop list
β›½ Find Gas Stations in the Route Planner panel, just above πŸ“… Build Schedule.
Map view with a route line and a numbered fuel-stop marker popup showing the station name, an hours badge, address, distance off route, and fuel type, with an Open in Google Maps button
Click a fuel-stop marker for its details β€” station name with an "hours vary" or "24h" badge, address, how far off the route it sits, and its fuel type. Open in Google Maps opens the station directly for turn-by-turn directions on your phone.
Map view of a full cross-country route with several numbered fuel-stop markers, truck-icon markers highlighted for the 24h-reliable picks, and the toolbar showing Route Planner, Clear Route from Map, Point ranges, Route Mode, and Radar with its opacity slider
A full route with its suggested fuel stops plotted β€” the truck icon marks a 24h-reliable pick. Clear Route from Map (next to the route summary) hides the route and its fuel stops from view without deleting anything; pick the route again from the Route Planner's Route: dropdown to bring it back.

Clear Gas Stops removes the suggested stops from the map. This is a planning aid only β€” nothing here is saved with the route or included in GPX/KML exports, and it resets automatically whenever the route's stops change.

Point color ranges

Click Point ranges… (top-right of the map) to customize the point thresholds and colors used on the map. A bonus is colored by the highest range it meets or exceeds. Add, remove, or reset ranges to defaults at any time β€” this only affects the map's coloring, not scoring.

Bonus point color ranges modal with four rows mapping point thresholds to colors
Default point color ranges β€” edit the thresholds or colors, or add more rows.

Weather forecasts

From a marker's popup, click 10-day weather to open a forecast panel for that bonus's location β€” daily highs/lows, conditions, and precipitation chance.

10-day weather forecast panel listing daily conditions, high and low temperatures
The weather panel, opened from a map popup. Close it with the Γ— in the top-right corner.

Weather radar overlay

Click Radar: Off (top-right of the map) to switch on a live precipitation radar overlay across the whole map β€” useful for spotting weather along a route at a glance instead of checking each bonus's forecast individually. Click it again (now labeled Radar: On) to turn it off. The slider next to the button controls the overlay's opacity, so you can fade it back enough to still see bonus markers and the route line underneath instead of letting it cover them completely.

Map view with the Radar: On toggle button and opacity slider in the top-right, and a semi-transparent precipitation radar overlay across the map
The radar overlay turned on, with its opacity lowered so bonus markers and the route line still show through.
Administration

Admin portal

Admin accounts see an Admin link in the header. The admin portal lists every rider with their status, role, when they were created, when they were last active, and how many live lookups they've used (broken out by timezone/geocode/weather, hits vs. misses β€” misses are what actually cost against the API quota).

Only existing admins can promote another account to admin, from this screen.
Admin portal table listing riders with status, role, last seen, timezone, geocode, weather usage and total live calls
The admin user table. Use the range buttons (Today / 7 days / 30 days / All time) to change the usage window.

Adding a user

Click + New user, fill in their email, display name, and a temporary password (minimum 8 characters), then Create user. Share the temporary password with them directly β€” there's no email invite flow, so they should sign in and can change it via Forgot password? if you'd rather not hand off your own choice.

New user modal with Email, Display name, and Temporary password fields
Creating a new user from the admin portal.

Each row's Actions column lets you deactivate, promote/demote, or delete a rider. Deactivating blocks sign-in without deleting their data.

Lookup access

The Lookup access column controls whether a rider can use the lookup buttons at all β€” separately for address/timezone lookups and for weather forecasts. New riders start with both switched on; click Disable next to either one if you want to withhold it from a specific rider, or Enable to turn it back on. Admin accounts always have full access and show an "Admin: full access" badge here instead of the toggle buttons.