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 Friday, 12 May 2028 · astronomical night 22:25 → 04:08 (5.71 h) · Moon 82% (waning gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown
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:30–21:45 | — nothing worth pointing at — | 1.25 | |
| 21:45–02:45 | 3C 273 | 5.0 | 0.72 |
| 02:45–06:05 | — nothing worth pointing at — | 3.33 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| 3C 273 | 87 | unknown | 22:30–02:05 (good) | 50.2° at 22:25 | 97.6° | 5.0 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2028-05-12"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"}.