Orekit 11.0 release

Orekit announcements
1

The Orekit team is pleased to announce the release of Orekit version 11.0. This is a major
version, including both new features and bug fixes.

First, the Orekit team would like to thank all the people who contributed to the development of this new version!

The main changes are:

  • Orbit determination using TLE orbit propagator
  • Sequential batch least squares orbit determination
  • New method signatures for IOD using directly the measurement classes
  • Writer and parser for all CCSDS Navigation Data Messages in both KVN and XML formats
  • Version 2 of CCSDS Tracking Data Messages
  • Version 3 of CCSDS Orbit Data Messages
  • Support for Rinex navigation files
  • Support for IGS clock files
  • Support for IGS real time data including both SSR and RTCM messages and Ntrip protocole
  • Consideration of eclipses by Moon in solar radiation pressure force
  • New API for analytical GNSS propagators
  • Addition of the finish method to finalize propagation by step handlers. It replaces the previous isLast parameter of the handleStep method.
  • Removal of propagation modes (master, slave, and ephemeris)
  • Possibility to add several step handlers for the same orbit propagation
  • A lot of fixed bug

This version depends on Hipparchus 2.0

For complete release notes please see:
https://www.orekit.org/site-orekit-11.0/changes-report.html

The maven artifacts are available in maven central.

The source and binaries can be retrieved from the forge releases page:
https://gitlab.orekit.org/orekit/orekit/-/releases

For people having trouble upgrading their applications to Orekit 11.0 version, the forum is an open place to ask questions and we will be happy to help you :slight_smile:

2

An additional information about the release:

ODM V3 support is an experimental feature and may change.
The standard is not yet endorsed by CCSDS and we have worked on
draft documents only. Orekit is indeed one of the reference
implementations needed for acceptance of the standard, which explain
why we developed it before the standard is accepted (it is some
kind of chicken and egg problem). This implies that users should not
use it for production, but may well use it for anticipating the
offical publication of the standard. Of course, if CCSDS committee
asks for modifications in the draft before it is published as a
standard, Orekit will implement that changes and an 11.x version
will be published (in this case we will most probably keep the
major number to 11, even if some changes are incompatible, because
we warn users here that this feature is considered experimental).
Orekit still supports ODM V2 in parallel to ODM V3.

1 Like