The creation hub: build a roadbook on the map from a GPX, a live recording, a public roadbook or from scratch — design each note to rally standards and export it in every format.
Open the EditorStart from anything
Load a GPX, a live recording, a .rdbk file, or fork a public roadbook — or draw a route on the map from scratch.
Roadbook-Suite import
Open and convert legacy Roadbook-Suite JSON files; the route, notes and vignettes come across into the canonical model.
roadbook-system.comEdit the route on the map
Draw, cut, smart-join, reverse, simplify and re-record segments on the trail — the result is always one continuous track.
Design each note
Text, road type, FIA danger grading, CAP, waypoint type + validation radius, speed limits, icons and the junction vignette.
Geotagged photo gallery
Use the photos captured while recording, pinned on the map, to refine your notes after the run.
Export everything
Self-contained .rdbk, GPX (track + named waypoints, OpenRally), and a print-ready A4 PDF — plus save to your profile, public or private.
Supported formats: what goes in, what comes out
The Editor is the conversion hub: load a route from several formats, edit it in the canonical model, then export to whichever format your device or event needs. Here is what it reads and writes.
| Format | Import | Export | What travels |
|---|---|---|---|
.rdbk |
Everything — the native, self-contained format | ||
| GPX | Track + named waypoints (optional Garmin / OSMAnd icons) | ||
| OpenRally GPX | Notes (distance, CAP, danger, waypoint type) + the vignette as a flat image | ||
| KMZ (Google Earth) | — | Track + named waypoints, open in Google Earth | |
Garmin .wpt |
— | Waypoints only, loaded alongside a GPX track | |
| Roadbook-Suite (legacy JSON) | — | Pre-standard files, converted to the canonical model on open | |
| Public roadbook | Loaded from / saved to the public library (signed in) | ||
| — | Print-ready A4 roadbook |
RDBK (.rdbk) — the native format
A single self-contained JSON file that embeds the track, every note and all the symbols it uses. Round-trips with full fidelity — icons, junction vectors, CAP, danger, waypoint types and radii all survive. This is the format to keep for re-editing. See the open .rdbk standard.
GPX
Standard GPS exchange. On import the track and any named waypoints become notes; if the GPX has waypoints but no track, a route is built through them to redraw. On export you choose track, waypoints (notes) or both, optionally tagging waypoints with Garmin or OSMAnd symbol names.
Garmin .wpt
A companion waypoint file: load it together with a GPX and its points fill in the notes when the GPX itself carries none. Import only.
OpenRally GPX
The rally interoperability standard. On import RDBK reads the route and each note's structured data — distance, CAP, danger grade and FIA waypoint type. But the vignette (the tulip) is stored by the OpenRally schema as an opaque flat image (a base64 PNG, sometimes wrapped in SVG), so it comes in as one full-box picture that can't be broken back into editable icons and junction vectors — that structure was lost when the producer exported. On export RDBK renders each note's vignette to an embedded SVG tulip, so the file stays self-contained. In short: OpenRally is a delivery / interchange format, not an editable source — for full re-editing keep the native .rdbk.
KMZ (Google Earth)
Export your roadbook as a KMZ — a KML 2.2 document zipped for Google Earth. The track becomes a path and each note becomes a named placemark with its coordinates, so you can visualise the entire route and all waypoints in Earth's 3D terrain. Export only — for re-editing keep the native .rdbk.
Roadbook-Suite (legacy JSON)
Older pre-standard JSON roadbooks open directly and are converted to the canonical model — the route, notes and vignettes come across so you can keep working. Import only.
roadbook-system.comPublic roadbook
Signed in, you can fork any roadbook from the public library into the Editor and save your own back to your profile — public (listed and shareable) or private. Saved roadbooks stay re-editable and sync across your devices.
A print-ready A4 roadbook for the co-driver's clipboard or the event's paper archive. Export only.
Roadbook editing workflow: Tips & tricks
Clean the GPS track
Simplify (Douglas-Peucker) removes zig-zag from a noisy track while keeping your note anchors; Draw extends the nearest open end and Insert adds a point on a segment. The point tools have one-key shortcuts.
Build notes in order
Road surface → junction vectors in the vignette → context icons (houses, trees, hazards). It keeps notes consistent and fast to read.
Load support images
Insert images of the junctions to help design the roadbook — you can right-click the map to go to Street View and check. Paste an image with Ctrl+V onto a note, or use Upload icon in the palette; roughly square images render best.
Set the road surface first
A note's Road carries forward to the following notes until another note changes it — so set it on the first note and again wherever the surface changes (asphalt → track → off-piste).
Set Waypoint type & radius
Choose the FIA waypoint type (it sets the map badge and, in a rally roadbook, how it's scored) and a validation radius — the Reader's geofence for automatic pass detection.
Junctions & roundabouts
Draw the junction vectors so the exit is unmistakable, and drop the waypoint at the real exit so the Reader's detection radius validates the pass where it should.
CAP & speed
Toggle a Red CAP and pick its type (exit / average / calculated / turning). A declarative speed limit also marks the note a controlled zone.
Save locally or on server
Keep your work two ways: export a self-contained .rdbk file to your device, or — signed in — Save to your profile so it's stored on the server, syncs across devices and stays re-editable.
Export & share
Export to GPX / OpenRally for other devices, or a print-ready PDF; publish a saved roadbook as public (shareable) or keep it private.
Works onWindowsmacOS / iOSAndroidLinux — runs in the browser, no install needed.