Right after launch the train is tight and predictions are accurate within seconds. As the train drifts apart over a few days, the same pass becomes a long string of dimmer dots rather than a visible train. The page handles this with a status field on each upcoming row: tight, dispersing, or scattered. Visitors see the geometry before they walk outside.

Yes. Each upcoming train row carries a launch_group field that resolves to a /starlink-launches/{slug}/ URL in a parallel page group. A templated href on the row inserts the link, so visitors can pivot from 'what's tonight' to 'where did these satellites come from' in one click.

Within hours of launch, the orbit is being refined continuously. A 6-hour cache catches the major refinements without overloading the source feeds. For dormant periods, drop to 24 hours. The base page renders identically; only the cached row changes.

Yes. Run two page groups against the same shape of data, like /starlink-passes/chicago/ and /satellite-trains/chicago/, or merge both constellations into one page group with a constellation column. The base page reads from a single data source either way.

Starlink's inclination of about 53 degrees means far-northern and far-southern cities see fewer or no trains depending on the launch group. The base page renders a 'no visible trains in the next ten days' message when the upcoming-trains list is empty, and reactivates automatically when a polar launch group brings high-latitude passes into range.

Yes. Each page emits a JSON-LD Event block for the next predicted train with startDate, endDate, location coordinates, and a descriptive name. The structured data graduates the page from text to an event search engines can render in event-style previews when relevance and freshness combine.

A scrub field on each upcoming row flags trains whose underlying launch slipped. A selector mapping renders a 'launch rescheduled' badge in place of the train time, so visitors get accurate context without the page going stale. The next sync replaces the badge once the new launch is on the manifest.

Yes. The same model handles Tiangong, OneWeb, the ISS visible passes group, and any future mega-constellation that publishes pass predictions in a similar shape. Each constellation gets its own page group or a column in a merged feed. The base page logic is the same; only the source identifier changes.