Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Orekit
Orekit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Orekit
  • OrekitOrekit
  • Issues
  • #671

Closed
Open
Opened Apr 10, 2020 by Clément Jonglez@yzokrasDeveloper

Add support for laser ranging file formats

It would be nice to add support in Orekit for laser ranging file formats:

  • Reading measurement files in Consolidated Laser Ranging Data Format (CRD) for both normal-point and full-rate data. The NASA webpage given here also contains sample C code to parse these files. Version 2.0 of the format is finalized, but small revisions were introduced in 2.01
  • Reading and writing prediction files in Consolidated Laser Ranging Prediction Format (CPF). The NASA webpage given here also contains sample C code to parse these files. Version 2.0 of the format is being finalized, so some changes in our code might be necessary once the version 2.0 is finally definitive.
  • Reading station coordinates and velocity files in SINEX format
  • Reading station eccentricities files in SINEX format

These file formats are not as widespread as GNSS or CCSDS formats, but it would be a good addition to Orekit, and they are standardized so the format should not change that often.

For now in my laser ranging OD example these file interfaces are written in Python, but this code is probably not bug-free. Furthermore the stations files and the full-rate CRD files are quite large, therefore we would gain in speed by parsing them in Java instead of Python.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
10.3
Milestone
10.3
Assign milestone
Time tracking
None
Due date
None
Reference: orekit/orekit#671