Eclipses, node crossings and the ground track

For power, thermal and payload planning: when the satellite is in the Earth’s shadow, where it crosses the equator and over which ground it flies, found on its orbit.

client.assets.update(satellite, orbit_events_enabled=True)  # with every new orbit, or
events = client.events.request(satellite).wait()  # now, for the current one
for eclipse in events.eclipses:
    print(eclipse.start, eclipse.end, eclipse.duration_s, eclipse.umbra_duration_s)
print(events.nodes[0].local_solar_time_h, events.nodes[0].beta_deg)
track = events.ground_track()  # a data frame (pandas); events.download("ground_track", "track.csv")
  • eclipses: each with the penumbra’s and the umbra’s start and end (none where the eclipse has no umbra, or is under way at the orbit’s start or end), duration_s and umbra_duration_s. The Earth is taken as a sphere of its equatorial radius, as in the orbit’s own radiation pressure; over the poles a contact comes a few seconds later.

  • nodes: each crossing of the equator with its longitude_deg, the local apparent solar time there (local_solar_time_h), the Sun’s elevation above the orbit’s plane (beta_deg) and the number of its orbit.

  • orbits: from ascending node to ascending node: period_s, the time in eclipse and in the umbra and the sunlit share.

  • Products: ground_track (CSV: epoch, latitude_deg, longitude_deg, height_km on WGS84 and sun_fraction, every minute), events (JSON) and, beyond a day, oem.

  • They reach as far ahead as the passes (Ground stations and passes): a day on the orbit’s own prediction, up to seven on that prediction continued.