Reading the Sky with Astrospheric and Meteoblue
How I use two forecast apps together to decide whether a night is worth setting up
Urban astrophotography is an exercise in reading imperfect signals. Under Bortle 9 skies, the difference between a productive night and a wasted one often comes down to whether two forecast models agree. I've settled into a simple pairing: Astrospheric for timing and structure, Meteoblue for atmospheric truth-telling.
Both apps look at the same sky, but they speak different dialects. When they align, I trust the night. When they diverge, I lower my expectations and simplify the plan.
Astrospheric — The Timing Engine
Astrospheric excels at the things that matter most when you're imaging in narrow windows:
- Hour-by-hour cloud structure
- Transparency and high-cloud layers
- Seeing mapped visually
- Jet stream position
- Moon altitude and illumination
- A clean "astro clock" that shows when the sky is even worth trying
It's the app that tells me when to set up, when to start, and when to stop. If Astrospheric shows a two-hour clear band, I treat it as a real opportunity—especially in winter, when Chicago's sky can shift from clear to opaque in minutes.
Meteoblue — The Atmosphere's Second Opinion
Meteoblue approaches the sky from a different angle. Instead of focusing on timing, it focuses on where the turbulence lives:
- Index 1 — boundary-layer seeing (ground → ~1 km)
- Index 2 — free-atmosphere seeing (upper air → jet stream)
- Arcsecond seeing estimates
- Multi-model transparency and cloud predictions
The indices are the key:
| Index Combination | What It Means |
|---|---|
| Both good | Rare Chicago clarity—commit to the night |
| One good, one bad | Mixed seeing—stick to bright nebulae |
| Index 1 poor | Ground layer is boiling—stars will bloat |
| Index 2 poor | Jet stream is shredding fine detail |
| Both poor | Treat the night as practice, not production |
Meteoblue is usually more pessimistic than Astrospheric, which makes it a perfect counterweight.
How I Use Them Together
The workflow is intentionally simple:
1. Check Astrospheric first. I look for 2–3 hour windows where clouds, transparency, and seeing all line up. This sets the shape of the night.
2. Cross-check with Meteoblue. If Index 1 and Index 2 agree with Astrospheric's seeing forecast, I treat the window as reliable. If they disagree, I downgrade the target difficulty.
3. Choose a target based on agreement:
| Agreement Level | What to Shoot |
|---|---|
| Strong (both apps align) | Galaxies, RGB stars, bright emission nebulae |
| Partial (one off) | Narrowband only |
| None | Framing tests, experiments, or night off |
4. Keep the plan short. Under Bortle 9, the first two hours after astronomical dusk are usually the most productive—especially with a waning moon rising late.
This pairing keeps the decision tree small. I don't need five apps or a wall of models. I just need two voices saying roughly the same thing.
A Note on Coverage
Astrospheric covers North America (US and Canada). If you're imaging elsewhere, Meteoblue works globally and can be paired with Clear Outside for UK/Europe coverage.
A Tip for Quick Forecasts
If you want a quick sense of whether the next few nights are worth setting up, you can ask an AI assistant like Claude or ChatGPT:
"Summarize imaging conditions for [your location] over the next 3 nights using Astrospheric and Meteoblue."
It will pull the same agreement-based view I use—a practical, Bortle-9-aware snapshot of what the sky is likely to offer.
Clear skies,
Pete
See also— The Ecosystem Behind Every Image