Weather by Email at Sea
How I get a 10-day weather forecast on a ship that only has company email
By John Winsome Munar (Trozovka), Master Mariner · November 2026 · Also on GitHub
This is a write-up of how I solved a real problem on board: getting a useful 10-day forecast with isobars and wind, when the weather fax is broken, the charterer's weather service is unreliable, and the only link to the outside world is the ship's company email.
I built a working system for my own use. The tool itself stays private. This page explains the ideas behind it, in enough detail that another seafarer (or a developer helping one) can understand every part and build their own.
Contents
- The problem
- What I needed
- Why GRIB files
- Where the forecast comes from
- Try the free service first: Saildocs
- My setup in one picture
- The mailbox is the memory
- Commands by email, and keeping strangers out
- A forecast area that follows the ship
- Keeping the files small
- Tropical cyclones
- Weather fax style charts
- Getting it through the ship's email
- Sending orders from the ship
- Reading it with no internet
- Living on 300 MB a week
- Cost and limits
- What I learned
- Disclaimer
1. The problem
I command a tramp ship. That means no fixed route: the next port can change while we are in the middle of an ocean. Good weather planning matters more on a tramp than on a liner, because I often have to decide a route a week ahead, and change it when a low or a typhoon is coming.
On board I had:
- a weather fax receiver that was not working,
- a weather routing service from the charterers that was late and unreliable,
- company email on the bridge PC, and nothing else from shore,
- sometimes a Starlink Wi-Fi allowance of 300 MB per week for the crew, which is gone fast if you open a normal weather website.
Apps like Windy and Ventusky are excellent, but they need a real internet connection. On my ship they were useless.
2. What I needed
I wrote the requirements down before writing any code:
- A real forecast, not news. At least 7 days ahead, better 10, so I can change course days before bad weather arrives.
- Isobars and wind. Pressure systems (highs, lows, fronts showing in the isobars) and wind on the Beaufort scale.
- Delivered by plain email. No app that needs internet at sea.
- Small. A few hundred KB a day at most.
- Following the voyage. I should give the passage plan once, before departure, and then only a position now and then.
- Easy to enter positions. Degrees and minutes with decimals, N/S, E/W, like on a chart. No strange codes to type.
- Two independent forecasts. So I can compare them, the same way I would never trust a single position fix.
- Zero cost to the company.
3. Why GRIB files
GRIB is the standard file format for weather model data. A GRIB file is not a picture. It is a grid of numbers: pressure and wind at every point, for every forecast hour.
That sounds less friendly than a picture, but for a ship it is much better:
| GRIB file | Picture (screenshot or fax) | |
|---|---|---|
| Size for 10 days | about 100 KB | 30 to 1000 KB per picture |
| Forecast times | every 12 or 24 hours, with a slider | one moment per picture |
| Zoom, units | zoom anywhere, Beaufort or knots | fixed |
| Works offline | yes, once received | yes |
You open GRIB files in free chart software such as OpenCPN (with its GRIB plug-in) or XyGrib. These show isobars, wind barbs and a time slider, all offline.
Later I also added black-and-white chart pictures, because a picture can be read on a phone in two seconds. More on that in section 12.
4. Where the forecast comes from
Two weather models are free and allowed for this use:
- GFS from NOAA (USA). Public domain. Available through NOAA's NOMADS service, which can cut out just the area and the fields you ask for.
- ECMWF (European centre). Their open data is free under the CC BY 4.0 licence, which only asks you to credit ECMWF. ECMWF is often the more accurate model several days ahead.
Why two models matter. At first I compared my own weather app with an email service, and then noticed both used GFS. That is not a real comparison: if GFS is wrong about a typhoon track, both are wrong together. A true second opinion needs a different model. When GFS and ECMWF agree, I trust the forecast more. When they disagree, I plan with extra margin. Professional weather routers work the same way.
The fields I use are only three: mean sea level pressure (for isobars) and the two wind components at 10 metres (for wind speed and direction).
5. Try the free service first: Saildocs
Before building anything, try Saildocs. It is a free service run since 1999 by the people behind Sailmail. You send a short request by email and it replies with a GRIB file. It can also send a forecast every day by itself (a subscription).
A request looks like this (sent as plain text, signature removed):
send gfs:0N,30S,30W,10E|1,1|0,12..240|PRMSL,WIND
That means: GFS model, a box from 0° to 30°S and 30°W to 10°E, a 1-degree grid,
every 12 hours out to 240 hours (10 days), pressure and wind. To get one every
day, start the line with sub instead of send.
Saildocs' website shows a "not secure" warning in the browser because it uses
plain http. That has nothing to do with the email service and you never give
a password there.
For many ships, Saildocs is enough. I built my own because I wanted three things it does not do: a forecast area that moves with my passage plan, two models side by side, and several recipients (ship email and my own email) from one setup.
6. My setup in one picture
Me (phone or laptop)
│ email: passage plan, position, commands
▼
A mailbox used only by the program
▲
│ reads commands, sends results
A small program run on a free schedule in the cloud
│ every 3 hours: answer new commands
│ once a day: download GFS + ECMWF, cut my area,
│ list tropical cyclones, draw charts
▼
Email to my recipients: ship email + my own email
├─ Forecast email: GRIB files + text
└─ Charts email: black-and-white pictures
Nothing runs on the ship except email. Nothing runs at home either: the program runs on a free scheduled job in the cloud (I use GitHub Actions, in a private repository). My laptop can be switched off for months.
The program is written in Python. It uses the ecCodes library (from ECMWF) to read and write GRIB files, and matplotlib with Cartopy to draw the charts.
7. The mailbox is the memory
The program keeps no database. Every time it runs, it reads all recent command emails in its mailbox, oldest first, and replays them:
- a passage plan replaces the old one,
- a position report updates the ship's position,
- "add recipient", "stop", "start" and so on change the settings.
At the end of the replay it knows the current state. This has two big advantages:
- No ship position is stored anywhere in the code. The code repository could be made public by mistake one day and there would still be nothing in it about where my ship is or was. In risky waters this matters.
- Nothing to break. There is no state file to corrupt. If something goes wrong, the next run rebuilds everything from the emails.
After a command email is answered, the program puts a label on it in the mailbox, so it sends only one confirmation per command.
8. Commands by email, and keeping strangers out
The commands are plain lines of text. For example:
GRIBPOST PLAN
WP 14-35.2S 048-12.7W 2026-12-01 06:00
WP 34-21.0S 018-28.0E 2026-12-10 12:00
TO captain@example.com
END
CODE xxxxxx
GRIBPOST POS 12-15.4S 080-02.1E 2026-12-05 08:00
CODE xxxxxx
Positions are written the way a navigator writes them: degrees, then minutes with a decimal, then the hemisphere. All times are UTC. I never type these by hand: a planner page writes them for me (section 14).
The program ignores lines it does not understand, and it ignores quoted text, so company disclaimers, signatures and old replies do not confuse it.
Keeping strangers out. Anyone who learns the program's address could send it a fake plan. Two checks stop that:
- Allowed senders. Only addresses on an allow list are obeyed. The list starts with my own email. I can add the ship's email by sending an "allow" command from an address that is already allowed.
- A command code. Every command email must contain a secret code line. Email "From" addresses can be faked; the code cannot be guessed.
If an allowed sender gets the code wrong, the program replies and says why ("no code line found" or "code does not match"). Strangers get no reply at all.
The mailbox password. The program logs in to its mailbox with an app password (Gmail calls it that). An app password opens the whole mailbox, so the program must have a mailbox of its own that holds nothing else. Never give a program the password of your personal email. Two traps I hit:
- Gmail only offers app passwords when 2-step verification is on.
- Changing the account password deletes all app passwords. The program then stops working until you make a new one.
The passwords live in the cloud service's secret store, never in the code.
9. A forecast area that follows the ship
This is the part that makes the forecast useful on a tramp ship.
The passage plan. Before departure I send the waypoints with ETAs. To save typing, the planner can fill in all ETAs from a departure time and a planned speed, using great-circle distances between waypoints. It can also import a route file exported from OpenCPN (GPX) or from an ECDIS (RTZ).
Where is the ship now? Between waypoints the program interpolates the position by time. That gives a planned position for any moment.
Correcting with a position report. Ships are early or late. When I send a position, the program finds the closest point on the planned route, looks up the time the plan expected the ship to be there, and works out the difference:
delay = time of my report − planned time at the closest point on the route
It then shifts the whole remaining schedule by that delay. If I report being two days late at a waypoint, every later ETA moves two days. If I skip reporting for a few days, the plan alone still gives a reasonable estimate.
How often to report. The plan gives a dead-reckoning style estimate: position by time along the route. Because the forecast box has 8° to 10° of margin and covers three days ahead, an estimate that is a few hours off doesn't change the forecast. My routine:
| Situation | What I send |
|---|---|
| Before departure | The passage plan (once) |
| Normal passage, on schedule | Noon position once a day if convenient, at least every 2 to 3 days |
| More than about 6 hours ahead of or behind the plan | A position report straight away |
| Route changed (new port, weather diversion) | A new passage plan, not just a position |
A position report only corrects the timing along the planned track. If the ship leaves that track, the forecast box must follow a new route, so a new plan is the right message. Each report is two lines and a few hundred bytes.
The forecast box. Each day the program takes the estimated track for the next 72 hours, draws a box around it, and adds margin: 8° of latitude and 10° of longitude on each side, so weather systems are seen before they arrive. The box is kept at least 20° by 25° and at most about 40° by 50°, and is snapped to whole degrees.
The date line. A route that crosses 180° must not turn into a box that wraps the whole world. Longitudes are "unwrapped" along the track (so 179°E is followed by 181°E instead of 179°W), the box is computed, and only at the end converted back. Most GRIB data is stored from 0° to 360°, while navigators use 180°W to 180°E, so this conversion is a classic source of bugs. I tested it on purpose with boxes across the date line.
Once a week, and when a new plan arrives, a second, coarser file covers the whole remaining route (2° grid), so I also see the big picture.
10. Keeping the files small
Size decides whether the forecast gets through a ship's email at all. What I do:
- 1° grid. Fine enough for synoptic planning, which is what a 10-day forecast is for anyway.
- Fewer time steps further out. Every 12 hours for the first 5 days, then every 24 hours to day 10. That is 16 steps instead of 41. Detail far ahead is not reliable anyway.
- Three fields only. Pressure, and the two wind components.
- Cut on the server. NOAA's NOMADS service cuts GFS to my box before sending. ECMWF's open data comes as whole-world files of about 2 MB per time step; the program downloads them in the cloud (where data is free) and cuts them down there.
- Sensible precision. The cut files are stored with GRIB "complex packing" (the same method NOAA uses for GFS, so every viewer can read it) at 10 bits per value. For pressure that is a few pascals, for wind a few hundredths of a m/s. Far finer than any chart needs.
Typical sizes per day:
| File | Size |
|---|---|
| GFS, my area, 10 days | about 110 KB |
| ECMWF, my area, 10 days | about 75 KB |
| ECMWF, whole route, 2° (weekly) | about 40 KB |
| Four chart pictures | about 160 KB |
I also tried zipping the GRIB files (bzip2). It saved almost nothing, because GRIB is already packed tightly. Not worth the trouble for the viewer.
11. Tropical cyclones
At the top of every forecast email there is a short tropical cyclone check:
- The main list comes from GDACS (the UN and European Commission disaster alert system), which covers all ocean basins and gives positions.
- For the Atlantic and Eastern Pacific, NHC is added as a cross-check.
- For every active storm the program calculates the great-circle distance to my expected track. Anything within 1,500 nautical miles gets a clear warning line at the top. Storms elsewhere are listed in one line.
This is a heads-up, not a warning service. Official tropical cyclone warnings still come from GMDSS: SafetyNET and NAVTEX.
12. Weather fax style charts
GRIB files need chart software. Sometimes I just want to look at the weather on my phone in two seconds, like a weather fax. So the program also draws black-and-white surface charts and sends them in a separate email.
Each chart page has two panels, one above the other, which fits a phone screen. There are 4 pages a day: analysis and +24 hours, +48 and +72, +96 and +120, +168 and +240 (day 7 and day 10).
What makes them useful:
- Each panel is centred on where the ship will be at that time. The day-7 panel shows the weather around my day-7 position, not around today's.
- Isobars every 4 hPa, labelled, like a fax chart.
- H and L centres. Found automatically: a point is a centre if it is the highest (or lowest) value in a window of about 6° around it, and at least 2.5 hPa above (or below) the average of that window. Before this, the pressure field is lightly smoothed, because pressure "reduced to sea level" over high land is noisy and would give fake highs over every mountain and island. The edges are handled so that a real low near the border of the chart is still found.
- Wind barbs in knots, the standard symbols: long line 10 knots, short line 5, flag 50. On the southern hemisphere the barbs are drawn on the correct side.
- The passage plan as a dashed line, the ship as a circle with a cross, and tropical cyclones marked on the first panel.
- Grey land, black lines, white sea. The pictures are reduced to 4 shades of grey, so each page is only about 30 to 40 KB.
The title of every panel gives the model, the forecast hour, the valid time and the estimated ship position, so a page is never confused with another day.
13. Getting it through the ship's email
Ship email systems often have size limits and filters. Some things that help:
- Two separate emails: one with the GRIB files, one with the pictures. If the company blocks pictures, the GRIB email still arrives.
- Splitting. If the GRIB email gets bigger than a set limit, the program sends each file in its own email instead of one big one.
- Several recipients. I send to the ship's email and to my own email. If the company system blocks it or is down, I can still read it on my phone when we have Starlink or a local SIM.
- Recognisable subject lines, so the ship's IT can allow them, and so I can find them.
- Ask IT once to allow the sender and the attachment types (.grb2, .png).
14. Sending orders from the ship
At sea my laptop has no internet. The ship's company email runs on the bridge PC, and my phone has a small Starlink allowance. So the tool to write commands must work completely offline.
The planner page. A single HTML file that runs in any browser with no internet. It has:
- boxes for degrees, minutes (with decimal) and N/S or E/W, for each waypoint,
- a button to fill ETAs from departure time and speed,
- route import from GPX or RTZ files,
- a "today's position" form with a "now" button,
- buttons for the other commands (add recipient, send now, stop, charts on/off).
It checks the input (minutes must be below 60, ETAs must go forward in time, and so on) and then either opens the email app with the message ready, or copies the message so I can paste it into any email program, including the company email on the bridge PC.
The phone app. On Android I wrapped the same page in a tiny app. It requests no permissions at all, not even internet. It only hands the finished message to the phone's email app (or the clipboard). The message is a few KB, so sending it over Starlink costs almost nothing.
The command code and the draft plan are saved only on that device.
15. Reading it with no internet
A common misunderstanding: OpenCPN does not need internet to show GRIB files. It needs internet only to download them, and I get them by email instead.
At sea I:
- open the forecast email on the phone and save the attachments,
- copy them to the laptop with a USB cable,
- open them in OpenCPN or XyGrib, offline.
The chart pictures I simply look at on the phone.
16. Living on 300 MB a week
A tiny forecast is pointless if the phone burns the whole data allowance in the background. On my Android phone I use a firewall app (Rethink DNS + Firewall, which needs no root) with two modes:
- At sea: only a short list of apps may use the ship's Wi-Fi: email, a couple of browsers, my navigation and weather tools, and the few banking apps I need even in the middle of the ocean. Everything else is blocked on Wi-Fi. Mobile data is left open for local SIM cards in port.
- At home: everything is allowed, only ads and known-bad sites are blocked.
Two lessons from setting this up:
- Don't use huge blocklists. My first setup had over a hundred lists, and some of them blocked Google services, the Play Store, even WhatsApp. A small set (malware, scams, spam, spyware, a standard privacy list, adult and gambling) is enough and breaks nothing.
- Don't mark the ship's Wi-Fi as "metered" if your firewall rules are set per Wi-Fi: some firewalls then treat it like mobile data and let every app through.
The daily forecast plus charts is about 300 to 400 KB, roughly 2.5 MB a week: under 1% of a 300 MB allowance.
17. Cost and limits
Cost: nothing. The weather data is free, the scheduled cloud job is within the free allowance of a private repository (a daily run takes about two minutes), and a normal free email account is the mailbox.
Limits:
- It is model output, not a forecaster's analysis. No fronts are drawn on the charts, because a computer guessing fronts and drawing them as fact would be worse than no fronts.
- A 1° grid does not show small features such as local sea breezes or squalls.
- Day 7 to day 10 forecasts are guidance for planning, not for decisions on their own. That is exactly why I compare two models.
- The cloud job runs on a schedule that may be delayed now and then by the provider. A forecast that has not gone out in 26 hours is sent at the next check, so a missed run does not mean a missed day.
18. What I learned
- Write the requirements first. "Forecast, not news" and "zero cost to the company" decided half of the design.
- Test the simplest option before building. For many ships Saildocs alone is enough.
- Redundancy is seamanship. Two models, two delivery routes (company email and personal email), two ways to view (GRIB and pictures).
- Keep positions out of code and logs. The mailbox holds the state; the code holds no ship data.
- Small details bite. Longitude conventions (0 to 360 against −180 to 180), app passwords disappearing after a password change, and over-eager blocklists each cost me time.
- Test the whole chain for real. Unit tests passed long before the first real email arrived. Only sending a real plan and opening a real file proves it works.
19. Disclaimer
This is how I solved my own problem. It is not a certified weather service and not a replacement for official forecasts and warnings (GMDSS, SafetyNET, NAVTEX) or for a professional weather routing service where one is required. Always use your own judgement as a seafarer.
Data credits: NOAA/NCEP GFS (public domain). ECMWF open data, CC BY 4.0. GDACS (UN/EC). NHC (NOAA).
About the author. John Winsome Munar (Trozovka) is a Master Mariner who builds practical software for seafarers, including WX weather apps for slow ship internet, PocketMOB Alert (man-overboard alarm), PocketVDR (voyage data recorder) and OpenCPN GPS Server. More at trozovka.github.io.
Text © 2026 John Winsome Munar. Shared under CC BY 4.0: you may share and adapt it with credit.