The Physiology of Endurance Running Podcast · Dan Nash and Owain Zerilli

Meteopace, the game-changing weather app - with creator Phil Richardson

·1 hr 13 min·4 clips

Phil says 48 hours before race day is the point when weather expectations become useful.

1. The Physiology of Endurance Running Podcast episode centers on MeteoPace, the weather-and-course pacing app created by Phil Richardson. 2. Awain hosts the episode, Dan joins as co-host, and Phil Richardson appears as the founder and runner whose own pacing problems shaped the app. 3. The episode asks what MeteoPace is for: translating weather, elevation, and race conditions into pacing decisions runners can actually use. 4. Phil says MeteoPace takes race-window weather data and course elevation and turns it into an adjusted pacing plan for events like a marathon or 10k. 5. Dan describes the app as something every runner has heard of, and Awain says it has become a tool he expects to refresh before Seville Marathon. 6. Phil explains that the app tries to prevent the week-before-race anxiety that comes from checking weather sites and wanting the forecast you hope for. 7. He says the goal is not to force a rigid pace but to help runners set expectations and make decisions before race day starts. 8. Phil traces the idea back to his own running background, where he experimented with heart rate, power, and pacing while trying to get better at racing. 9. He says that work made him feel like the watch was controlling him, rather than pace or heart rate reflecting what he was actually doing. 10. He describes building the first version for himself, then for friends, before turning it into an app that launched in April of the previous year. 11. Phil says London Marathon showed how a forecast can look manageable while still being made hard by sun, still air, and radiation. 12. He notes that temperature readings are often taken in the shade, while runners on a marathon course are exposed directly to the sun. 13. Phil gives 48 hours before race day as the point when weather expectations become stable enough to shape pacing and logistics. 14. He says the earlier forecasts still move too much to justify stress, although they can give a rough indication. 15. He explains that MeteoPace can also be used after a race to compare actual splits with what the conditions were worth in perfect weather. 16. Phil says that analysis can reveal pace instability, showing when a runner did not hold an even effort through the course. 17. Phil’s delivery is technical but conversational, with Awain and Dan asking practical questions about weather, wind, and race execution. 18. The episode moves from app overview to modeling details, then to race-day decision making, and the tone stays curious and analytical throughout. 19. Listeners who race marathons, monitor weather, or like running data tools will get the most from it. 20. Listeners wanting a simple running chat without data modeling may skip it.

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from The Physiology of Endurance Running Podcast