lasp / lasp/space_packet_parser

Investigate converting XTCE to Electronic Data Sheets format

Open
#296 1 comment 1 reaction 2 assignees View on GitHub

@medley56 is already working on this.

Since Sep 16, 2026.

  • #297 by @copilot-swe-agent — open
enhancement help wanted question
Dominant language
Python
Stars
39
Forks
15
Avg merge
2d 16h
Merged PRs (30d)
12

Description

Summary

EDS are used by some missions to describe packet structures. EDS is advertised as a similar configuration mechanism to XTCE in that it describes packet structures (confirm this understanding).

Driving Requirements

  1. Build an example of converting an XTCE document to EDS, similar to our CSV to XTCE converter but the other direction. This should demonstrate at a basic level what is required to map between these two formats (XTCE and EDS).
  2. Build an example of starting from an EDS file and building an XTCE definition from it to parse packets. This can be a contrived, simple example to demonstrate the pattern for creating a packet definition in memory from an EDS file.
  3. Analyze and produce a summary report on the feasibility and complexity of building a conversion system between EDS and XTCE into the Space Packet Parser library and supporting EDS-based configuration (via parsing EDS to an XTCE definition in memory). Consider the scope of each data model and the fidelity of mapping between the two.

Resources

https://ccsds.org/Pubs/876x0b1.pdf

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.