As I’m working on long term asteroid propagations more I need to have third body perturbations for the the larger asteroids. Baer and Chesley came up with a set of table of states they call BC-405/BC-430. Along with the definition of a sun and solar system barycenter locked Frame I’m going to be coding up a classes for reading a SQLite version of the asteroid data based off of the BC data. The total data set is on the order of 100 MB. This seems to be a very edge case for the library so I’m thinking perhaps this would be better as an augmented library like Rugged is. I like the idea of using the DataContext methodology for registration and simulating the JPL DE loader implementation but against this data set. The factoring I’m thinking of is:
- Adding the JPL sun centered and solar system Barycenter Centered frames to Orekit proper
- Creating an Asteroid 3rd Body library hosted on the Orekit Gitlab and posted to Maven repos like with Rugged. This could be another sub-project on Orekit but not in the main source tree.
- Creating a light weight landing page for the library to help people find the data files etc.