SEASCOPE-DRIFT documentation
Drift engine v0.3.1 Drift-UI v0.1.15

On-demand drift modelling for search and rescue

SEASCOPE-DRIFT documentation

User guide and system description

Documents Drift engine v0.3.1 and Drift-UI v0.1.15 · last updated 2026-10-22 · what's new

1 Introduction#

SEASCOPE-DRIFT is an on-demand drift modelling system for marine search and rescue (SAR) and, more generally, for tracking objects and material at sea. It predicts where persons, life rafts, vessels and debris drift from a last known position, and turns that prediction into a search plan. It was developed by Calypso Science and Oceanum, in collaboration with New Zealand Police and Coastguard New Zealand, around the needs of operational SAR teams.

This guide follows the application as it is: the screenshots are taken from the version named in the header, and the ranges and defaults of every control are read from that version at each update.

Table 1. Code versions this documentation was generated from.
ComponentVersion documentedRelease date
Drift enginev0.3.12026-10-22
Drift-UIv0.1.152026-10-22

1.1 Purpose and intended users#

SEASCOPE-DRIFT is used to simulate drift trajectories of objects or persons at sea and in coastal waters, and to plan the resulting search. Its users are:

1.2 System overview#

SEASCOPE-DRIFT is a web application, used from any modern browser with nothing to install. The simulations run on Oceanum's cloud platform, on a drift engine fed with the best ocean and wind model data available for each region — high-resolution coastal models where they exist, relaxing to GFS or ECMWF winds and Mercator SMOC surface currents elsewhere (Section 5). A 48-hour simulation of a few thousand particles typically returns in seconds.

Best available model data High-resolution ocean models (SCHISM) Tidal models PredictWind 1 km winds relaxing to: GFS / ECMWF winds, Mercator SMOC currents Drift engine Leeway model, ensembles, forward and backward on Oceanum.io SEASCOPE-DRIFT web app run, compare, plan the search, export to GIS and GPS in the browser
Overview. The drift engine reads the best available ocean and wind data for the region; the web application sets up the runs, shows the results and plans the search.

The application computes no physics in the browser: every current, particle position and tide curve comes from the drift engine, so what the screen shows is exactly what was simulated. Each region has its own address, its own models and its own defaults (Section 5.3).

1.3 About this documentation#

This documentation is regenerated as the application evolves: at each update the screenshots are re-taken from the current release, the tables of controls are re-read from it, and what changed is listed on the What's new page.

2 Getting started#

2.1 Opening the application#

The Drift-UI opens in a web browser at the address of the region's deployment; nothing is installed on the user's computer. Each region has its own address, and the deployment decides who may open it (an Oceanum login, or open access). At start-up the quick guide summarises every control and the usual workflow: set a datum, run, compare, plan, export. Tick Don't show this again to skip it next time; it can be re-opened from the About box.

The quick guide, shown at start-up until Don't show this again is ticked.
Figure 1. The quick guide, shown at start-up until Don't show this again is ticked.

2.2 A typical incident, end to end#

  1. Check the forcing. Choose Dynamic mode for forecast currents and wind (or Tide mode for a short, sheltered-water case) and open the domain pill to check that the forecast covers the period of interest (Section 3.3).
  2. Set the datum. Right-click the map at the last known position and choose New datum, or press Edit position in the Release panel and type the coordinates. Set the seed radius to the uncertainty of the position, and the release window to the uncertainty of the time (Section 3.4).
  3. Set the time. Enter the time of the incident, the duration, and the direction — forward to predict where the object is now, backward to find where an object found at sea came from (Section 3.5).
  4. Choose the wind and the object. Choose the forecast wind (ECMWF or GFS) and the drifting object — usually a Leeway category such as a person in the water with a buoyancy aid, or a life raft (Section 3.6).
  5. Run. Press the red Run button. The result appears within seconds and plays through the drift; drag along the timeline to the time the search units will be on scene (Section 3.7).
  6. Compare. Save the run, switch to the other wind forecast and run again: the two ensembles side by side show how much the answer depends on the wind forecast (Section 3.8).
  7. Plan. Open the search pattern toolbox: a search area is proposed from the particle cloud; adjust it, choose the pattern and track spacing, name it and save it (Section 3.9).
  8. Export and share. Export the patterns as GPX or KML for the units, and the drift as KML, GeoJSON or CSV for the GIS (Section 3.11). Re-run as new information arrives.

SEASCOPE-DRIFT supports, and does not replace, the judgement of the SAR mission coordinator. A drift prediction is a probability distribution, not a position: plan on the spread of the ensemble, not on its centre alone (Section 7).

3 Drift-UI user guide#

This chapter describes the Drift-UI screen by screen. Each screenshot is followed by a table of its numbered controls: what each does, and its range and default as the code of the documented version has them. Some defaults — the release position, the time step, the seed radius, the starting mode — are set per region (Section 3.14); the screenshots are from the Drift-UI v0.1.15 in the Hauraki Gulf region.

3.1 Screen layout#

The map fills the screen. The three pills at the top centre identify the run — the application, the simulation mode and the domain. The five round tool buttons at the top right open the panels. The colour scale and the cursor read-out sit at the top left, the map tools at the bottom left, the timeline at the bottom centre, and the run buttons at the bottom right. Right-clicking the map opens a context menu (Section 3.4).

Main screen in tide mode with the animated tidal currents. The numbered controls are listed in the table below.
Figure 2. Main screen in tide mode with the animated tidal currents. The numbered controls are listed in the table below.
Table 2. Controls numbered in Figure 2.
No.ControlWhat it doesRange / default
1SEASCOPE-DRIFT pillOpens the About box, which also re-opens the quick guide.
2Mode pillShows the simulation mode, Tide or Dynamic; opens the mode panel.
3Domain pillShows the domain in use — the tidal dataset in tide mode, the forecast stack in dynamic mode; opens the domain panel.
4ReleaseOpens the Release panel — where, how many particles, how spread out.
5TimeOpens the Time panel — start, duration, step, forward or backward.
6Wind & objectOpens the Wind and drifting object panel.
7Search patternOpens the search pattern toolbox.
8Layers & displayOpens the layers panel, the saved runs and patterns, and export.
9Colour scaleScale of the current speed (and the wind and density, when those layers are on).
10TimelinePlay and step buttons, the clock (local time and UTC), the tide gauge and its sea level, and the tide curve or time slider.
11MeasureClick points on the map for the distance (nautical miles) and true bearing of each leg, and the total; double-click to finish, Esc or the button again to clear.
12Zoom inZooms in (also mouse wheel).
13Fit domainZooms back to the whole region.
14Save runKeeps the finished run as a layer in its own colour, after asking for a name, so another run can be compared with it.
15RunStarts the simulation. A progress card shows the elapsed time; the result appears within seconds and starts playing. Esc or ✕ cancels the wait.

Only one panel is open at a time; pressing its tool button again, pressing Esc or clicking the map closes it (except the search pattern and release panels while they are being used on the map). In dynamic mode the map animates the forecast surface currents instead of the tide:

Main screen in dynamic mode, with the forecast surface currents animated.
Figure 3. Main screen in dynamic mode, with the forecast surface currents animated.

3.2 About and quick guide#

The SEASCOPE-DRIFT pill opens the About box: what the system is, who built it, and its disclaimer. Its button Show the quick guide re-opens the guide shown at start-up (Section 2.1).

The About box, opened from the SEASCOPE-DRIFT pill.
Figure 4. The About box, opened from the SEASCOPE-DRIFT pill.

3.3 Simulation mode and domain#

The mode pill opens the mode panel. Tide mode drives the drift with tidal currents reconstructed from harmonic constituents, which are available at any date, past or future, and a uniform wind entered by the user. Dynamic mode drives it with the forecast current stack and a forecast wind (Section 4.8). The mode the page opens in is set per region. In a region with no tide model, Tide is greyed out and the page opens in Dynamic; Dynamic is greyed out while no forecast is staged for the domain.

Simulation mode panel.
Figure 5. Simulation mode panel.
Table 3. Controls numbered in Figure 5.
No.ControlWhat it doesRange / default
1Simulation modeTide drives the drift with tidal currents reconstructed from harmonic constituents, with a wind you enter. Dynamic uses the forecast current stack and a forecast wind. Custom is reserved and disabled.Tide · Dynamic
2Mode descriptionWhat the selected mode uses and when to choose it.

The domain pill opens the domain panel. In tide mode it selects the tidal dataset:

Domain panel in tide mode — the tidal dataset.
Figure 6. Domain panel in tide mode — the tidal dataset.
Table 4. Controls numbered in Figure 6.
No.ControlWhat it doesRange / default
1Tidal datasetThe tidal model driving tide mode, among those available in the region.
2Dataset descriptionThe tidal model, its resolution and constituents.

In dynamic mode there is nothing to choose — the order of the ocean models is fixed for the region — so the panel lists the forecast stack instead: each current and wind source in priority order, the period it covers and when it was staged. Check it before a long run: the sources do not all reach the same horizon.

Domain panel in dynamic mode — the forecast stack, in priority order, with the period each source covers and when it was staged.
Figure 7. Domain panel in dynamic mode — the forecast stack, in priority order, with the period each source covers and when it was staged.
Table 5. Controls numbered in Figure 7.
No.ControlWhat it doesRange / default
1Forecast stackEach current and wind source in priority order, with its type, time step, the period it covers and when it was staged.
2Stack noteHow the stack is combined (the finest source answers wherever it covers a particle).

3.4 Release#

The Release panel sets the last known position (the datum) and the ensemble of particles released there.

Release panel.
Figure 8. Release panel.
Table 6. Controls numbered in Figure 8.
No.ControlWhat it doesRange / default
1Coordinate formatHow positions are written and typed — decimal degrees (DEG), degrees and decimal minutes (DMD) or degrees, minutes and seconds (DMS). The choice is remembered by the browser and also used by Copy location.12.3456° · 12° 34.56' · 12° 34' 56"
2LatitudeLatitude of the release point (datum), in the chosen format. Locked until Edit position is pressed.default set per region
3LongitudeLongitude of the release point.default set per region
4Edit positionUnlocks the position. The cursor becomes a crosshair; a click on the map or a typed coordinate moves the point. Save locks it again, Cancel (or Esc) restores the previous position. The lock stops a stray click from moving an agreed datum.
5Position checkWhether the point is in the domain, the current there and which source provides it — or a warning that the point is on land.
6ParticlesSize of the ensemble. More particles give a smoother density map, at a modest cost in run time.1–10,000; default 1,500
7Seed radiusParticles are seeded uniformly over a circle of this radius around the release point — the uncertainty of the last known position.0–2,000 m; default 100 m, or the region's
8Release overSpreads the release evenly over this many minutes after the start time, for an uncertain time of loss. 0 is an instantaneous release.0–360 min; default 0 min
9DiffusivityHorizontal diffusivity K of the random walk that represents unresolved current variability (standard deviation √(2 K Δt) per step and component).0–50 m²/s; default 0.2 m²/s

The position is locked once saved, so that a stray click on the map cannot move an agreed datum. To move it, press Edit position — the cursor becomes a crosshair, and a click on the map or a typed coordinate moves the point (Enter in a coordinate box saves) — then Save to lock it again, or Cancel / Esc to put it back. The note under the buttons checks the point: in the domain, the current there and which model provides it, or a warning that it is on land. A release outside the region is refused.

The quickest way to start is the right-click menu on the map:

The right-click menu on the map.
Figure 9. The right-click menu on the map.
Table 7. Controls numbered in Figure 9.
No.ControlWhat it doesRange / default
1New datumPlaces the release point here and walks through Time and Wind & object (each step can be skipped). Run at any point keeps the position.
2New search patternOpens the search pattern toolbox with the area centred here instead of on the drift.
3Copy locationCopies the position to the clipboard, in the chosen coordinate format.

New datum opens a short guided set-up: the position is placed where you clicked, then the Time and the Wind & object panels follow (Step 2 of 3, Step 3 of 3), each with a Skip button — their defaults already run. Pressing Run at any point keeps the position and runs.

Regions that define named release points (offshore installations, for instance) offer them in a Preset location list under the coordinates, and draw them on the map.

3.5 Time#

Time panel.
Figure 10. Time panel.
Table 8. Controls numbered in Figure 10.
No.ControlWhat it doesRange / default
1Start timeStart of the simulation (for a backward run, the time the object was found). In regions with a time zone it is entered in local time and the UTC equivalent is shown below it; otherwise in UTC. In dynamic mode it cannot be earlier than the data — an earlier start is moved to the first available time.
2UTC equivalentThe start time in UTC, when the start is entered in local time.
3DurationLength of the simulation.0.5–96 h; default 48 h
4StepIntegration time step. Shorter steps follow sharp current gradients more closely and cost more.5–900 s; default 300 s or the region's, whichever is shorter
5DirectionForward predicts where the object goes; Backward estimates where an object found at sea came from.Forward · Backward

Times are entered in local time in regions that define a time zone, with the UTC equivalent shown underneath; otherwise in UTC. In dynamic mode the start cannot be earlier than the data: a start typed or reached earlier is moved to the first available time, with a note saying so. The data can reach back up to about a week, kept from past forecasts (Section 5.5), and forward to the end of the forecast; the domain panel shows the period covered.

A backward run starts at the time and place an object was found and integrates back in time, giving the ensemble of positions it may have come from (Figure 17).

The timeline at the bottom shows the clock and, where a sea level is available, the tide curve at a gauge. Before a run, dragging along it (or pressing play) moves the clock through the available period and animates the currents; after a run it scrubs through the result.

The timeline in tide mode, with the tide curve at the selected gauge.
Figure 11. The timeline in tide mode, with the tide curve at the selected gauge.
Table 9. Controls numbered in Figure 11.
No.ControlWhat it doesRange / default
1Step backMoves the clock one step earlier (10 minutes, or the model output step if longer).
2Play / pausePlays the run through its output frames. Before a run it sweeps the clock through the available period, animating the currents.
3Step forwardMoves the clock one step later.
4ClockThe displayed time — local time where the region has a time zone, with UTC below.
5Tide gaugeThe gauge whose sea level is drawn as the curve. Tide gauges of the tidal model in tide mode; in dynamic mode, the region's gauges read from the forecast sea level (where configured).
6Sea levelSea level at the selected gauge at the displayed time.
7Fold tide curveHides or shows the tide curve, leaving the play buttons and clock.

3.6 Wind and drifting object#

This panel sets the wind and what it acts on. In tide mode the wind is uniform and steady, entered as a speed in knots and the direction it blows from:

Wind and drifting object panel in tide mode — a uniform wind and a windage.
Figure 12. Wind and drifting object panel in tide mode — a uniform wind and a windage.
Table 10. Controls numbered in Figure 12.
No.ControlWhat it doesRange / default
1Wind on/offWith the wind off only the current moves the particles, and the object settings do not apply. Off at start in tide mode; switching to dynamic mode turns it on.off at start
2Wind speedTide mode only — a uniform, steady wind speed.0–80 kt; default 15 kt
3Wind fromTide mode only — the direction the wind blows from, in degrees true (meteorological convention). The compass rose below shows it.0–360 °; default 270 °
4Wind roseThe wind direction drawn on a compass.
5Object typeWhat the wind acts on: a windage (a fixed percentage of the wind), a Leeway object from the US Coast Guard table, or surface oil (a 3 % windage by default, no weathering or spreading).Windage % · Leeway object · Surface oil
6WindagePercentage of the 10 m wind added to the current.0–6 %; default 3 %
7DeflectionRotates the wind-driven drift clockwise (positive) or anticlockwise from downwind.-40–40 °; default 0 °

In dynamic mode the wind is a forecast. The panel offers the global models available (ECMWF and GFS) and lists, for the chosen one, each wind source that will be used — including 1 km regional nests where the region has them — with its area, grid spacing and period:

Wind and drifting object panel in dynamic mode — forecast wind and a Leeway object (PIW-2, person in water with a buoyancy aid).
Figure 13. Wind and drifting object panel in dynamic mode — forecast wind and a Leeway object (PIW-2, person in water with a buoyancy aid).
Table 11. Controls numbered in Figure 13.
No.ControlWhat it doesRange / default
1Wind on/offWith the wind off only the current moves the particles, and the object settings do not apply. Off at start in tide mode; switching to dynamic mode turns it on.off at start
2Forecast windDynamic mode only — which global wind forecast drives the run (ECMWF or GFS). Where the region has 1 km nests (e.g. PredictWind) they are used inside their box, above the chosen model.
3Wind coverageThe period the selected wind forecast covers, and its time step.
4Object typeWhat the wind acts on: a windage (a fixed percentage of the wind), a Leeway object from the US Coast Guard table, or surface oil (a 3 % windage by default, no weathering or spreading).Windage % · Leeway object · Surface oil
5Leeway objectOne of the US Coast Guard Leeway categories (persons in water, life rafts, vessels, debris…), grouped.
6Leeway coefficientsThe object's downwind and crosswind leeway as a percentage of the wind.
7Jibe / hourProbability per hour that an object flips to the other side of downwind. Converted to a per-step rate, so the result does not depend on the time step.0–0.5 /h; default 0.04 /h
8Downwind leewayApplies the downwind component of the leeway. Untick to see the crosswind effect alone.on at start
9Crosswind leewayApplies the crosswind component, which produces the two lobes of a Leeway ensemble. Untick to see the downwind drift alone.on at start
10Leeway at this windWhat the object does at a given wind speed — downwind and crosswind speeds and the divergence angle of its two lobes.

The drifting object is one of:

ControlWhat it doesRange / default
Oil windageSurface oil only — the windage applied to the slick.0–6 %; default 3 %

With the wind switched off only the current moves the particles, and none of the object settings apply.

3.7 Running a simulation and reading the result#

The red Run button starts the simulation. A small progress card shows what is being done and the elapsed time; the map stays visible underneath. A run usually takes a few seconds; Esc or the ✕ button stops waiting for it. Running an identical simulation again — same release, settings and forcing — returns the stored result at once (Section 4.7).

When the result arrives it plays through the drift. The particles are drawn with their tracks, the run statistics card gives the state of the ensemble at the displayed frame, and the cursor read-out gives the position and current under the mouse:

A 48 h forward run in dynamic mode (PIW-2, ECMWF wind) at its last frame — particles, their tracks and the run statistics.
Figure 14. A 48 h forward run in dynamic mode (PIW-2, ECMWF wind) at its last frame — particles, their tracks and the run statistics.
Table 13. Controls numbered in Figure 14.
No.ControlWhat it doesRange / default
1Run statisticsAt the displayed frame — integration step and frame, particles adrift and beached, how many each current source drives, the ensemble centroid, the 95 % radius and the time.
2Colour scaleScale of the current speed (and the wind and density, when those layers are on).
3Cursor read-outPosition under the cursor and the current there (speed and direction it flows to).
4TimelinePlay and step buttons, the clock (local time and UTC), the tide gauge and its sea level, and the tide curve or time slider.
5Run detailsOpens the run details — the settings the run was made from and its result. The same details head every exported file.
6Save runKeeps the finished run as a layer in its own colour, after asking for a name, so another run can be compared with it.
7Clear / cancelClears the run from the map. While a run is computing, cancels it.

The statistics card lists, at the displayed time, how many particles are adrift and how many have beached, how many each current model is driving (so you can see when the drift leaves a high-resolution domain), the ensemble centroid and the 95 % radius — the distance from the centroid within which 95 % of the particles lie. If a run is refused — outside the forecast period, on land, outside the region — the card says why and, where it can, what to change.

The same run as a density map shows the probability of presence at the displayed time (Layers panel, Density):

The same run drawn as a particle density map (probability of presence).
Figure 15. The same run drawn as a particle density map (probability of presence).

The ⓘ button opens the run details: everything the run was made from (release, time, forcing sources and when they were staged, object and its coefficients) and what it came to. The same rows head every file the run is exported to, so an exported file is self-describing.

Run details — everything the run was made from and came to. The same rows head every file the run is exported to.
Figure 16. Run details — everything the run was made from and came to. The same rows head every file the run is exported to.

A backward run (Time panel, Backward) is read the same way: the cloud is where the object may have been at the displayed time before it was found.

A 24 h backward run — where the object may have been 24 hours before it was found at the release point.
Figure 17. A 24 h backward run — where the object may have been 24 hours before it was found at the release point.

3.8 Saved runs and comparison#

The save button (the floppy disk above Run) keeps the finished run as a layer in its own colour, under a name you give it — by default its object, wind and start time.

Naming a run as it is saved.
Figure 18. Naming a run as it is saved.
Table 14. Controls numbered in Figure 18.
No.ControlWhat it doesRange / default
1Run nameName of the saved run, pre-filled from its object, wind and start time. It names the layer and the exported files.

Saving a run, changing one setting and running again puts the two on one chart. Comparing the ECMWF and GFS wind forecasts this way is the most direct way to see the forecast uncertainty; the same works for two Leeway objects, two release times or two seed radii.

Two saved runs from the same datum compared — PIW-2 driven by ECMWF and by GFS winds.
Figure 19. Two saved runs from the same datum compared — PIW-2 driven by ECMWF and by GFS winds.

Saved runs are listed in the Layers panel, where each can be shown or hidden, opened in run details (ⓘ), downloaded (↓) or deleted (×) (Figure 24). They are kept by the page for the session: reloading the page clears them, so export what must be kept.

3.9 Search patterns#

The search pattern toolbox designs a search over the drift. When it opens after a run, a search area is proposed from the particle cloud at the displayed time — fitted on the cloud's principal axis — and follows the cloud as the timeline moves, until you take it over. It can then be moved (drag the middle), resized (drag an edge) and rotated (drag a corner) on the map, drawn afresh (Draw area), or reset to the cloud. New search pattern in the right-click menu starts one at the clicked point instead.

Search pattern panel (parallel track), with the search area proposed from the particle cloud.
Figure 20. Search pattern panel (parallel track), with the search area proposed from the particle cloud.
Table 15. Controls numbered in Figure 20.
No.ControlWhat it doesRange / default
1PatternParallel track, expanding square or sector search. Geometry after the US Coast Guard SAROPS formulation (Kratzke, Stone & Frost, 2010).Parallel · Expanding square · Sector
2Draw areaDrag a new search area on the map, replacing the proposed one.
3Reset to cloudGoes back to the area fitted automatically to the particle cloud, which follows the timeline.
4Search areaSize and orientation of the search area, and how to change it on the map (the middle moves, edges resize, corners rotate).
5Track spacingDistance between parallel legs (or between successive legs of the expanding square).100–4,000 m; default 500 m
6AlongLength of the search area along the legs (parallel track).500–30,000 m; default 6,000 m
7AcrossWidth of the search area across the legs (parallel track).500–30,000 m; default 4,000 m
8Orientation / first legOrientation of the legs (parallel track) or direction of the first leg (square, sector), in degrees true.0–359 °; default 0 °
9First turnWhich way the craft turns at the end of the first leg, and therefore at every leg after it.Right · Left
10NameThe pattern's name. It follows the pattern into the saved layer, the file name and the route name inside GPX and KML files.
11Save patternKeeps the pattern as a layer, listed under Search patterns in the layers panel, where it can be shown, hidden and exported.
12Pattern summaryNumber of legs, distance to fly (km and nautical miles), spacing and area.

Three patterns are available, with their geometry after the US Coast Guard SAROPS formulation (Kratzke, Stone & Frost, 2010):

Table 16. Controls of the expanding square and sector patterns.
ControlWhat it doesRange / default
Search radiusRadius of the expanding square or sector search around the datum.200–20,000 m; default 2,000 m
RoundsSector search — number of rounds (each round is a set of legs through the datum, rotated from the previous one).1–6; default 3
Parallel track search fitted to the drift at its last frame. The area can be moved, resized and rotated on the map.
Figure 21. Parallel track search fitted to the drift at its last frame. The area can be moved, resized and rotated on the map.
Expanding square search on the same drift.
Figure 22. Expanding square search on the same drift.
Sector search on the same drift.
Figure 23. Sector search on the same drift.

The summary under the controls gives the number of legs and the distance to fly. A green dot marks the start and a red dot the end. Save pattern keeps it as a named layer; saved patterns are listed in the Layers panel and are what Search patterns (shown) exports (Section 3.11).

3.10 Layers and display#

The layers panel controls what is drawn on the map, lists the saved runs and patterns, and holds the export.

Layers and display panel, with two saved runs, one saved search pattern and the export section.
Figure 24. Layers and display panel, with two saved runs, one saved search pattern and the export section.
Table 17. Controls numbered in Figure 24.
No.ControlWhat it doesRange / default
1Satellite imagerySatellite basemap under the map.on at start
2ENCNautical chart overlay (in New Zealand, LINZ charts).off at start
3CurrentAnimated current particles, coloured by speed (scale in the legend).on at start
4WindAnimated wind layer, from the selected forecast (dynamic mode).off at start
5Model domainsOutlines of the model domains in the current stack, so you can see where each model drives the drift.off at start
6TracksParticle tracks behind the particles.on at start
7DensityParticle density map — the probability of presence at the displayed time.off at start
8Density cellSize of the density map cells, in screen pixels.4–28 px; default 10 px
9Track colourColours tracks by particle age, by speed, or in a single colour.by age · by speed · single colour
10Saved runsEach saved run in its colour, with a checkbox to show or hide it, ⓘ for its run details, ↓ to download it and × to delete it.
11Saved search patternsEach saved pattern — tick to show it (and include it in a pattern export), ↓ to download it, × to delete it.
12Export — whatThe run on screen, any saved run, all saved runs (one file each, in a zip), or the search patterns that are ticked (shown).
13Export — formatThe formats available for the selected item (see the export table).
14Centreline onlyDrift tracks only — export the path of the ensemble centroid alone, without the particles. A full export includes the centreline too.off at start
15ExportWrites and downloads the file. Red when there is something to export.
The forecast wind layer animated over the map.
Figure 25. The forecast wind layer animated over the map.
Model domains layer — the outline of each source in the forecast stack.
Figure 26. Model domains layer — the outline of each source in the forecast stack.
Nautical chart (ENC) layer.
Figure 27. Nautical chart (ENC) layer.

3.11 Export#

The export section at the bottom of the layers panel writes the drift or the search patterns to a file. The formats on offer follow what is being exported:

Table 18. Export choices and the formats offered for each, from the UI code.
WhatFormats
Drift tracks (run on screen, or a saved run)CSV, GeoJSON, GPX, KML
All saved runs (zip, one file each)CSV, GeoJSON, GPX, KML
Search patterns (those shown)GeoJSON, CSV, GPX, KML, GeoPackage

What the files contain:

Particle status codes are 0 adrift, 1 beached, 2 out of the domain and 3 not yet released. A saved run is exported from the copy the page holds, so it can be exported for as long as the page is open.

3.12 Measuring distances#

The ruler button at the bottom left measures on the chart: click points for the distance in nautical miles and the true bearing of each leg, and the total; double-click to finish; Esc or the button again clears it.

The measuring tool — distance in nautical miles and true bearing of each leg, and the total.
Figure 28. The measuring tool — distance in nautical miles and true bearing of each leg, and the total.

3.13 Keyboard and mouse#

Table 19. Keyboard and mouse.
ActionEffect
Drag the mapPan
Mouse wheel, + / −Zoom; ⤢ fits the region
Right-click the mapContext menu: New datum, New search pattern, Copy location. While a position is being edited, a right-click places it
EscCloses the innermost thing open: cancels a run being computed, then a dialog, the menu, a measurement, an area being drawn, a position being edited, and finally the open panel
Enter in a coordinate boxSaves the position being edited
Drag along the timelineMoves the clock; step buttons move one step

3.14 Regional settings#

The same application serves every region; what differs is set per region:

The controls are capped at the limits of the region (maximum particles, duration, minimum time step).

4 Drift model#

This chapter explains what a SEASCOPE-DRIFT simulation computes, so that its results can be read with the right confidence.

4.1 Lagrangian particle tracking#

The search object is represented by an ensemble of particles — up to 10,000 per run. At each time step every particle moves with the surface ocean current at its position plus a wind-driven drift that depends on the object (Section 4.2, Section 4.3). Currents and winds are interpolated in space and time from the model data of the region (Section 5). Simulations last up to 96 hours, with a time step of 5 to 900 seconds (Time panel, Section 3.5).

4.2 Wind-driven drift: the Leeway model#

SAR objects are driven by the US Coast Guard Leeway model (Allen and Plourde, 1999; Allen, 2005), as implemented in OpenDrift (Dagestad et al., 2018) and on which the IAMSAR leeway tables are based. The leeway of an object is split into a downwind and a crosswind component, each a linear function of the 10 m wind speed W (m/s):

downwind = ((DWSLOPE + εdw/20) · *W* + DWOFFSET + εdw/2) / 100 [m/s] crosswind = ((CWSLOPE + εcw/20) · *W* + CWOFFSET + εcw/2) / 100 [m/s]

The slopes and offsets are the object's coefficients from the US Coast Guard table (Section 9). The random terms ε are drawn once per particle at release from the published standard deviations — this is what spreads a Leeway ensemble even in a uniform wind — and redrawn where they would send an object upwind. Each object settles on one side of downwind (half the ensemble on each side) and keeps it until it jibes; the jibe probability is set per hour (default 0.04 per hour) and does not depend on the time step. This produces the two divergent lobes of a Leeway ensemble that SAR planners expect. Either component can be switched off to see the other alone.

4.3 Generic windage and surface oil#

For objects without a Leeway category, a windage adds a fixed percentage of the 10 m wind to the current, optionally deflected from downwind. Surface oil uses the same drift at 3 % of the wind by default, with no deflection; no weathering, evaporation or spreading of the oil is modelled.

4.4 Spreading and uncertainty#

The prediction is stochastic: its uncertainty is the spread of the particle ensemble, which comes from four sources:

From the ensemble come the density map, the 95 % radius and the search area proposed in the search pattern toolbox.

4.5 Forward and backward simulation#

A simulation runs forward, to predict where the object is now or will be, or backward, to estimate where an object found at sea came from. A backward run integrates the same equations back in time; the ensemble still widens going back, as the uncertainty about the origin grows.

4.6 Release and coastline#

Particles that would start on land are moved into the water; a release point on land is refused. A particle that reaches the coastline is stranded (beached) and stays there. In tide mode the coastline is that of the tidal model; in dynamic mode it is a detailed coastline prepared for the region (in New Zealand, LINZ 1:50,000). The coastline drawn on the map is the one the simulation uses, and the statistics count particles adrift and beached — beaching locations indicate the shorelines to search.

4.7 Reproducibility#

A simulation is reproducible: the same release, settings and forcing give the same result, and running it again returns the stored result at once instead of recomputing it.

4.8 Simulation modes#

Tide mode drives the drift with tidal currents reconstructed from the harmonic constituents of a tidal model (for the Hauraki Gulf: Z0, M2, S2, N2, K2, M4, MS4, MN4). The tide is computed analytically, so it is available at any date, past or future, independently of any forecast; the wind is uniform and entered by the user. Tide mode suits sheltered, tide-dominated waters, quick what-if analyses, and dates outside the forecast period.

Dynamic mode drives the drift with forecast ocean currents — which include the tide, the wind-driven and the large-scale circulation — and the forecast wind of the chosen global model, each from the best data available along the path (Section 5). It is recommended when winds are strong or changing, offshore, and for drifts longer than a few hours. Running the same incident with both wind forecasts shows the forecast uncertainty directly (Section 3.8).

5 Best available ocean and wind data#

Every SEASCOPE-DRIFT simulation is driven by the best model data available along the path of each particle. Where Calypso Science runs a high-resolution hydrodynamic model — typically resolving harbours, estuaries and headlands at tens to a few hundred metres — that model drives the drift. Where a 1 km PredictWind downscale of the wind exists, it drives the wind-driven part of the drift. Outside these domains the simulation relaxes to global models:

The switch happens particle by particle and step by step, so a drift that starts in a harbour and leaves for open water is driven by the harbour model, then by the coarser models as it goes. The run statistics show how many particles each model is driving at the displayed time (Section 3.7).

5.1 High-resolution domains#

The map shows the high-resolution domains currently used around New Zealand and in France. Extents are read from the model metadata at each documentation update.

High-resolution ocean forecastNational ocean model (SCHISM NZ)Tidal modelPredictWind 1 km wind
Figure 29. High-resolution model domains. Everywhere else the drift is driven by GFS or ECMWF winds and Mercator SMOC surface currents.
Table 20. High-resolution domains shown on the map.
AreaDomainTypeExtent (W, S, E, N)
New ZealandSCHISM HaurakiHigh-resolution ocean forecast174.31, -37.22, 175.93, -35.62
New ZealandSCHISM NZNational ocean model (SCHISM NZ)165.05, -49.15, 179.90, -33.14
New ZealandPredictWind 1 km — Great BarrierPredictWind 1 km wind175.01, -36.67, 175.81, -35.87
New ZealandPredictWind 1 km — TaurangaPredictWind 1 km wind175.80, -37.99, 176.60, -37.19
New ZealandHauraki Gulf — SCHISMTidal model174.31, -37.22, 175.93, -35.62
New ZealandSCHISM RaglanHigh-resolution ocean forecast174.70, -37.89, 174.97, -37.71
New ZealandPredictWind 1 km — RaglanPredictWind 1 km wind174.27, -38.34, 175.07, -37.54
New ZealandRaglan Harbour — Oceanum tideTidal model174.75, -37.84, 174.98, -37.74
New ZealandSCHISM WellingtonHigh-resolution ocean forecast174.70, -41.43, 174.91, -41.23
New ZealandPredictWind 1 km — WellingtonPredictWind 1 km wind174.43, -41.64, 175.23, -40.84
New ZealandPredictWind 1 km — PictonPredictWind 1 km wind173.77, -41.73, 174.57, -40.93
New ZealandCook Strait — SCHISMTidal model174.03, -42.26, 175.40, -40.70
New ZealandSCHISM NelsonHigh-resolution ocean forecast173.07, -41.33, 173.33, -41.17
New ZealandPredictWind 1 km — NelsonPredictWind 1 km wind172.85, -41.47, 173.65, -40.67
FranceGulf of Saint-Malo SCHISMTidal model-3.18, 48.50, -1.02, 50.03
FranceBrest & Iroise SCHISMTidal model-5.64, 47.79, -4.18, 48.75
FranceQuiberon SCHISMTidal model-3.66, 47.08, -2.31, 47.82
FranceSouth Brittany — 250 m gridTidal model-4.23, 46.78, -1.96, 47.93
FrancePertuis Charentais SCHISMTidal model-2.77, 45.23, -0.69, 46.54

5.2 How the models are combined#

The ocean models form an ordered stack, finest first. For each particle at each time step the finest model whose domain contains the particle provides the current, and coarser models take over as the particle leaves it. Inside a fine model's domain, that model also decides where the land is, so a coarse model can never put current where the fine model knows there is land.

Winds work the same way: a PredictWind 1 km nest answers inside its own box and forecast period, and the chosen global model everywhere else. The nest follows the global model chosen — ECMWF runs use the ECMWF downscale, GFS runs the GFS one — so comparing the two wind forecasts compares the whole wind chain.

The order of the ocean models is fixed for each region; the choice of wind forecast is the user's. The domain panel lists the models of the region in priority order, with the period each covers (Section 3.3).

5.3 Regions#

The same application serves several regions, each with its own models:

Table 21. Regions and the models that drive them.
RegionModesOcean models (finest first)Tidal modelsWind
North Atlantictide + dynamic—
then Copernicus global surface
Gulf of Saint-Malo SCHISM
Brest & Iroise SCHISM
ECMWF 10 m wind
GFS 10 m wind
South Brittanytide + dynamic—Quiberon SCHISM
South Brittany — 250 m grid
Brest & Iroise SCHISM
Gulf of Saint-Malo SCHISM
Pertuis Charentais SCHISM
ECMWF 10 m wind
GFS 10 m wind
Côte d'Ivoiredynamic—
then Copernicus surface globale
—ECMWF vent à 10 m
GFS vent à 10 m
nested: WRF Abidjan 3 km vent à 10 m
Hauraki Gulftide + dynamicSCHISM Hauraki
SCHISM NZ
then Copernicus global surface
Hauraki Gulf — SCHISM
Hauraki Gulf — Oceanum 400 m
ECMWF 10 m wind
GFS 10 m wind
nested: PredictWind 1 km Great Barrier, PredictWind 1 km Tauranga
NelsondynamicSCHISM Nelson
SCHISM NZ
—ECMWF 10 m wind
GFS 10 m wind
nested: PredictWind 1 km
Raglantide + dynamicSCHISM Raglan
then Copernicus global surface
Raglan Harbour — Oceanum tideECMWF 10 m wind
GFS 10 m wind
nested: PredictWind 1 km
Phuket & Phang Nga Baytide + dynamic—Phuket & Phang Nga Bay — Oceanum 400 mECMWF 10 m wind
GFS 10 m wind
Western AustraliadynamicSCHISM WA
then Copernicus global surface
—ECMWF 10 m wind
GFS 10 m wind
Wellington & Cook Straittide + dynamicSCHISM Wellington
SCHISM NZ
Cook Strait — SCHISMECMWF 10 m wind
GFS 10 m wind
nested: PredictWind 1 km Picton, PredictWind 1 km Wellington

5.4 Coastlines#

Particles strand on a coastline prepared for each region — in New Zealand from the LINZ 1:50,000 coastline, elsewhere from other coastline data — and in tide mode on the coastline of the tidal model. The coastline drawn on the map is the one the simulation uses.

5.5 Forecast updates#

Forecasts are refreshed automatically as each model publishes a new cycle — typically daily for the ocean models and twice daily for the global winds. Each update also keeps the past: a rolling archive of up to about a week is built from the first part (the nowcast) of each past forecast, the best estimate of that period any forecast made, so a dynamic run can start in the recent past. Gaps in the record are never filled in. The domain panel shows, for each model, the period covered and when it was last updated.

6 Validation and performance#

6.1 Validation against OpenDrift#

The engine is validated against OpenDrift (Dagestad et al., 2018), the open-source trajectory framework of the Norwegian Meteorological Institute, widely used for operational SAR. Both models are run on the same forcing files (in the Hauraki Gulf: SCHISM Hauraki, SCHISM NZ and Copernicus currents with ECMWF wind), the same landmask and the same configuration, in three steps from the simplest to the most uncertain, so that each step adds one source of difference:

  1. one particle, current only — interpolation, integration and geodesy;
  2. 3 % windage, 1,500 particles — adds the wind; diffusion is the only random term;
  3. Leeway objects, 1,500 particles each — adds the Leeway coefficients drawn per particle.

The results below are those of the documented version of the drift engine.

Step 1 — one particle, current only#

Release 175.0520 E, 36.3650 S at 2026-10-11T00:00:00Z, 48 h, 100 particles, jibe 0/h, diffusivity 0 m2/s, 600 s step, wind_ec wind.

Table 22. Single particle advected by the current alone: SEASCOPE-DRIFT against OpenDrift.
quantity value
separation at +6 h 7 m
separation at +12 h 11 m
separation at +24 h 17 m
separation at +48 h 38 m
separation at +48 h (end) 38 m
max separation 38 m
path length travelled 27.8 km
final separation as % of path 0.14%
SEASCOPE-DRIFT (solid) and OpenDrift (dashed) trajectories of one particle advected by the current alone, and their separation through time.
Figure 30. SEASCOPE-DRIFT (solid) and OpenDrift (dashed) trajectories of one particle advected by the current alone, and their separation through time.

With no random term the two trajectories should coincide; their small separation comes from the interpolation of the currents and from SEASCOPE-DRIFT's spherical geodesy against OpenDrift's ellipsoidal one.

Steps 2 and 3 — windage and Leeway ensembles#

Release 175.0520 E, 36.3650 S (radius 100 m) at 2026-09-26T00:00:00Z, 48 h, 1500 particles, jibe 0.04/h, diffusivity 0.2 m2/s, 600 s step, wind_ec wind.

Table 23. SEASCOPE-DRIFT against OpenDrift after 48 h: centroid drift, gap between the two models' ensemble centroids, Monte Carlo error of a centroid, and overlap of the final-position histograms (in brackets, the overlap two halves of one ensemble achieve).
run centroid drift API vs OpenDrift centroid gap at +48 h Monte-Carlo error (1 sigma) overlap (halves)
OceanDrift, 3% windage 68.6 km 0.13 km (0.2%) 0.01 km 1.00 (1.00)
Leeway PIW-5, person in water, scuba suit 29.5 km 0.57 km (1.9%) 0.35 km 0.76 (0.66)
Leeway LIFE-RAFT-DB-10, deep ballast, general 70.4 km 0.50 km (0.7%) 0.37 km 0.75 (0.65)
Leeway LIFE-RAFT-SB-6, shallow ballast and canopy, general 48.8 km 0.25 km (0.5%) 0.83 km 0.65 (0.54)

Because the two models draw their random numbers from different generators, particle i is not the same object in both runs: the comparison is between ensembles. The gap between centroids is read against the Monte Carlo error of a centroid (spread/√n), and the overlap of the final-position histograms against the overlap two halves of the same ensemble achieve.

Summary of the windage and Leeway comparisons.
Figure 31. Summary of the windage and Leeway comparisons.
Leeway PIW-5 (person in water, scuba suit), 1,500 particles, +48 h: SEASCOPE-DRIFT (left), OpenDrift (centre) and both final positions overlaid (right).
Figure 32. Leeway PIW-5 (person in water, scuba suit), 1,500 particles, +48 h: SEASCOPE-DRIFT (left), OpenDrift (centre) and both final positions overlaid (right).
Centroid gap between the two models against the Monte Carlo error of the centroid.
Figure 33. Centroid gap between the two models against the Monte Carlo error of the centroid.

For objects whose leeway is poorly constrained — a person in the water especially — the plume is wide and the relative gap between the two ensembles is largest, but it remains small against the spread of the plume itself: for such objects the search area is set by the object, not by the choice of drift engine.

6.2 Automated tests#

The engine is also checked by an automated test suite against independent references rather than against earlier runs of the same code: geodesic distances against pyproj, tidal reconstruction against the oceantide package, and the Leeway model against a transcription of OpenDrift's implementation.

6.3 Performance#

The engine is built so that a prediction returns in seconds. The forecast period a run needs is read once into memory and kept for the following runs, the mesh and tidal interpolation reuse precomputed structures, and the land test is folded into the last integration stage. The progress card shows the elapsed time of each run, and the run details give the compute time (Section 3.7).

Run time grows roughly linearly with the number of particles and the number of time steps; the limits per run are 10,000 particles and 96 hours.

7 Limitations and good practice#

7.1 Data availability#

7.2 Forecast and model uncertainty#

7.3 Recommended use#

8 References#

Allen, A. A. (2005). Leeway divergence. US Coast Guard Research and Development Center, Report CG-D-05-05.

Allen, A. A., & Plourde, J. V. (1999). Review of leeway: field experiments and implementation. US Coast Guard Research and Development Center, Report CG-D-08-99.

Breivik, Ø., & Allen, A. A. (2008). An operational search and rescue model for the Norwegian Sea and the North Sea. Journal of Marine Systems, 69(1–2), 99–113.

Dagestad, K. F., Röhrs, J., Breivik, Ø., & Ådlandsvik, B. (2018). OpenDrift v1.0: a generic framework for trajectory modelling. Geoscientific Model Development, 11(4), 1405–1420.

IMO/ICAO. International Aeronautical and Maritime Search and Rescue (IAMSAR) Manual, Volume II: Mission Co-ordination.

Kratzke, T. M., Stone, L. D., & Frost, J. R. (2010). Search and Rescue Optimal Planning System. 13th International Conference on Information Fusion (FUSION), IEEE.

Zhang, Y. J., Ye, F., Stanev, E. V., & Grashorn, S. (2016). Seamless cross-scale modeling with SCHISM. Ocean Modelling, 102, 64–81.

9 Appendix — Leeway object categories#

The 85 categories of the US Coast Guard Leeway table offered in the Wind & object panel, in the order of the table, with what each does at a 10 m/s wind (mean of the ensemble coefficients). Further categories, for example specific aircraft debris, can be added on request.

Table 24. Leeway of the 85 object categories at a 10 m/s wind (mean of the ensemble coefficients).
IdKeyDescriptionDownwind (% of wind)Crosswind (% of wind)Divergence (°)
1PIW-1Person-in-water (PIW), unknown state (mean values)0.960.5429.4
2PIW-2PIW, vertical PFD type III conscious0.480.1517.4
3PIW-3PIW, sitting, PFD type I or II1.600.137.7
4PIW-4PIW, survival suit (face up)1.711.3629.5
5PIW-5PIW, scuba suit (face up)0.630.3126.2
6PIW-6PIW, deceased (face down)1.120.0411.4
7LIFE-RAFT-DB-10Life raft, deep ballast (DB) system, general, unknown capacity and loading (mean values)3.520.625.6
8LIFE-RAFT-DB-114-14 person capacity, deep ballast system, canopy (average)3.500.787.2
9LIFE-RAFT-DB-124-14 person capacity, deep ballast system, no drogue3.750.786.8
10LIFE-RAFT-DB-134-14 person capacity, deep ballast system, canopy, no drogue, light loading3.751.007.6
11LIFE-RAFT-DB-144-14 person capacity, deep ballast system, no drogue, heavy loading3.590.487.8
12LIFE-RAFT-DB-154-14 person capacity, deep ballast system, canopy, with drogue (average)1.910.7811.9
13LIFE-RAFT-DB-164-14 person capacity, deep ballast system, canopy, with drogue, light loading1.950.2110.1
14LIFE-RAFT-DB-174-14 person capacity, deep ballast system, canopy, with drogue, heavy loading2.191.3916.0
15LIFE-RAFT-DB-1815-50 person capacity, deep ballast system, canopy, general (mean values)3.680.342.8
16LIFE-RAFT-DB-1915-50 person capacity, deep ballast system, canopy, no drogue, light loading3.930.380.7
17LIFE-RAFT-DB-2015-50 person capacity, deep ballast system, canopy, with drogue, heavy loading3.150.394.4
18LIFE-RAFT-DB-21Deep ballast system, general (mean values), capsized0.880.1811.6
19LIFE-RAFT-DB-22Deep ballast system, general (mean values), swamped0.990.148.0
20LIFE-RAFT-SB-6Life-raft, shallow ballast (SB) system AND canopy, general (mean values)2.681.1022.3
21LIFE-RAFT-SB-7Life-raft, shallow ballast system, canopy, no drogue2.961.2122.2
22LIFE-RAFT-SB-8Life-raft, shallow ballast system AND canopy, with drogue2.310.9522.4
23LIFE-RAFT-SB-9Life-raft, shallow ballast system AND canopy, capsized1.680.248.1
24LIFE-RAFT-SB-10Life Raft - Shallow ballast, canopy, Navy Sub Escape (SEIE) 1-man raft, NO drogue3.300.5022.4
25LIFE-RAFT-SB-11Life Raft - Shallow ballast, canopy, Navy Sub Escape (SEIE) 1-man raft, with drogue1.700.0023.5
26LIFE-RAFT-NB-1Life-raft, no ballast (NB) system, general (mean values)3.701.9828.2
27LIFE-RAFT-NB-2Life-raft, no ballast system, no canopy, no drogue5.342.2620.5
28LIFE-RAFT-NB-3Life-raft, no ballast system, no canopy, with drogue3.151.5129.2
29LIFE-RAFT-NB-4Life-raft, no ballast system, with canopy, no drogue3.391.4923.7
30LIFE-RAFT-NB-5Life-raft, no ballast system, with canopy, with drogue1.210.9237.2
31USCG-RESCUESurvival Craft - USCG Sea Rescue Kit - 3 ballasted life rafts and 300 meter of line2.480.327.4
32AVIATION-1Life-raft, 4-6 person capacity, no ballast, with canopy, no drogue3.391.4923.7
33AVIATION-2Evacuation slide with life-raft, 46 person capacity2.710.7214.9
34LIFE-CAPSULESurvival Craft - SOLAS Hard Shell Life Capsule, 22 man3.521.4422.2
35OVATEK-CRAFT-1Survival Craft - Ovatek Hard Shell Life Raft, 4 and 7-man, lightly loaded, no drogue (average)3.511.0813.9
36OVATEK-CRAFT-2Survival Craft - Ovatek Hard Shell Life Raft, 4 man, lightly loaded, no drogue3.860.326.7
37OVATEK-CRAFT-3Survival Craft - Ovatek Hard Shell Life Raft, 7 man, lightly loaded, no drogue3.262.3222.3
38OVATEK-CRAFT-4Survival Craft - Ovatek Hard Shell Life Raft, 4 and 7-man, fully loaded, drogued (average)1.040.038.1
39OVATEK-CRAFT-5Survival Craft - Ovatek Hard Shell Life Raft, 4 man, fully loaded, drogued1.090.035.3
40OVATEK-CRAFT-6Survival Craft - Ovatek Hard Shell Life Raft, 7 man, fully loaded, drogued0.990.026.9
41PERSON-POWERED-VESSEL-1Sea Kayak with person on aft deck1.160.4110.2
42PERSON-POWERED-VESSEL-2Surf board with person1.930.5114.8
43PERSON-POWERED-VESSEL-3Windsurfer with mast and sail in water2.250.6911.5
44SKIFF-1Skiff - modified-v, cathedral-hull, runabout outboard powerboat3.151.2922.3
45SKIFF-2Skiff, V-hull2.870.320.5
46SKIFF-3Skiffs, swamped and capsized1.650.3913.3
47SKIFF-4Skiff - v-hull bow to stern (aluminum, Norway)2.521.0710.5
48SPORT-BOATSport boat, no canvas (*1), modified V-hull6.542.1918.5
49SPORT-FISHERSport fisher, center console (*2), open cockpit5.552.2722.2
50FISHING-VESSEL-1Fishing vessel, general (mean values)2.472.7648.2
51FISHING-VESSEL-2Fishing vessel, Hawaiian Sampan (*3)2.672.9848.1
52FISHING-VESSEL-3Fishing vessel, Japanese side-stern trawler2.803.1348.2
53FISHING-VESSEL-4Fishing vessel, Japanese Longliner (*3)2.472.7648.2
54FISHING-VESSEL-5Fishing vessel, Korean fishing vessel (*4)1.802.0148.2
55FISHING-VESSEL-6Fishing vessel, Gill-netter with rear reel (*3)3.721.4123.9
56COASTAL-FREIGHTERCoastal freighter. (*5)1.872.0948.2
57SAILBOAT-1Sailboat Mono-hull (Average)4.504.9547.7
58SAILBOAT-2Sailboat Mono-hull (Dismasted, Average)3.943.9845.3
59SAILBOAT-3Sailboat Mono-hull (Dismasted - rudder amidships)6.274.0132.6
60SAILBOAT-4Sailboat Mono-hull (Dismasted - rudder missing)2.420.7918.1
61SAILBOAT-5Sailboat Mono-hull (Bare-masted, Average)5.235.8948.4
62SAILBOAT-6Sailboat Mono-hull (Bare-masted, rudder amidships)6.667.3647.9
63SAILBOAT-6bSailboat Mono-hull (Bare-masted, rudder hove-to)2.692.8146.2
64SAILBOAT-7Sailboat Mono-hull, fin keel, shallow draft (was SAILBOAT-2)2.672.9848.1
65SAILBOAT-8Sunfish sailing dingy - Bare-masted, rudder missing1.790.1012.2
66FV-DEBRISFishing vessel debris1.970.3610.4
67SLDMBSelf-locating datum marker buoy - no windage0.000.000.0
68SEPIRBNavy Submarine EPIRB (SEPIRB)0.400.0070.2
69BAIT-BOX-1Bait/wharf box, holds a cubic metre of ice, mean values (*6)0.721.8630.8
70BAIT-BOX-2Bait/wharf box, holds a cubic metre of ice, lightly loaded2.531.0913.3
71BAIT-BOX-3Bait/wharf box, holds a cubic metre of ice, full loaded1.151.4836.7
72OIL-DRUM55-gallon (220 l) Oil Drum0.750.4837.1
73CONTAINER-1Scaled down (1:3) 40-ft Container (70% submerged)1.780.270.8
74CONTAINER-220-ft Container (80% submerged)1.250.1910.5
75MINEWWII L-MK2 mine1.070.4119.1
76REFUGEE-RAFT-1Immigration vessel, Cuban refugee-raft, no sail (*7)1.560.088.3
77REFUGEE-RAFT-2Immigration vessel, Cuban refugee-raft, with sail (*7)6.432.2220.0
78SEWAGESewage floatables, tampon applicator1.790.165.1
79MED-WASTE-1Medical waste (mean values)2.750.5010.3
80MED-WASTE-2Medical waste, vials3.640.6710.4
81MED-WASTE-3Medical waste, vials, large4.340.749.7
82MED-WASTE-4Medical waste, vials, small2.950.5410.4
83MED-WASTE-5Medical waste, syringes1.790.165.1
84MED-WASTE-6Medical waste, syringes, large1.790.165.1
85MED-WASTE-7Medical waste, syringes, small1.790.165.1