Up to ten targets, one night: each gets its good/marginal/poor windows (darkness × altitude × Moon × clouds, as on the single-target page), then the night is handed out five minutes at a time to whichever target is best — with hysteresis, so you get a few solid blocks of at least 30 minutes, not a flicker. Targets that never win a block are listed with the reason.
Try: an autumn deep-sky night · ← previous night · next night →
Night of Thursday, 27 August 2026 · astronomical night 21:42 → 05:02 (7.33 h) · Moon 100% (full moon) · weather: ERA5 history
Each row is the target's quality through the night, white → amber → green for 0 → 0.3 → 0.6 → 1 (the same thresholds as poor / marginal / good). Dark blue: the schedule. Grey columns: twilight. Download: schedule CSV · targets CSV · JSON
| local | target | hours | mean quality |
|---|---|---|---|
| 20:00–21:45 | — nothing worth pointing at — | 1.75 | |
| 21:45–04:05 | HD 189733 | 6.33 | 0.44 |
| 04:05–06:45 | — nothing worth pointing at — | 2.67 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| HD 189733 | 44 | 43 | 21:45–04:05 (marginal) | 71.1° at 23:00 | 46.8° | 6.33 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-08-27"targets: names or RA Dec, separated by commas, semicolons or newlines, at most ten. The response carries targets[] (score, verdict, best_window, windows, transit, moon_separation), schedule[] (blocks with target, start/end in UTC and local, hours, mean_quality; target: null is idle time), unscheduled[] with a why, forecast_source, warnings[]. Missing targets → 400 {"error", "code": "targets_missing"}; an unreadable date → 400 {"error", "code": "invalid_date"}.