We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
docs: add FAQ & Troubleshooting page (dump1090 checks, empty lists, alerts, updating)
Home: add public satellite-transit alert signup (GitHub Pages + Actions worker) Link the free mass-alert signup (https://joergs-git.github.io/sun-moon-transit-predictor/alerts/) to the wiki TOC — a Pushover 24-48 h before the ISS/HST/Tiangong crosses the Sun/Moon at a subscriber's location, run by a GitHub Actions cron worker.
Usage: add Sky-target passes section (satellite × DSO, plan, scope target, catalogue, plan-alerts) Documents the v0.34.0+ sky-target feature: the Sky-target plan timeline + confidence ampel, horizon vs next-opportunity views, the 🔭 Scope-target pulldown driving the SharpCap capture, the editable Catalog tab, Pushover plan-alerts, and the imaging-difficulty reality check. Home + Usage TOCs updated.
Usage: multi-satellite transits (ISS/HST/Tiangong) + imaging feasibility Rewrite the ISS-transits section into a general "Satellite transits" section covering ISS, Hubble and Tiangong (v0.32.0), and add two worked-example subsections people kept asking about: - "Can you actually photograph it? — the numbers": apparent-size formula with a per-target table (ISS ~50" vs HST ~5" vs Tiangong ~20"), a plate-scale / arcsec-per-pixel table across focal lengths (HST is ~3 px at the reference 714 mm rig), the ~0.6 s transit duration and the resulting high-fps need. - "How precisely is the transit point predicted?": along-track timing error (~0.13 s, absorbed by a 2–4 s window) vs cross-track position error (~1 km fresh = ~7' = ~23% of the disc), the ~4–5 km centre-line corridor, why the 72 h trust window exists, and the resolution-vs-catchability trade-off. Home + Usage TOCs updated; intros now say "satellites (ISS, Hubble, Tiangong)".
Restructure wiki: Home master TOC + Setup/Usage/Advanced/Reference pages
Initial Home page