Add RealtimeDecoder for realtime processing

[ccostes]

Intent

Enable realtime message processing by creating a stateful RealtimeDecoder class which maintains aircraft state across decode calls to for position decoding. The RealtimeDecoder decode() method matches the API and behavior of the existing rs1090.decode().

Running the new example script should return something like the following

 % python realtime_decoder.py
Realtime vs Batch Processing Comparison
==================================================
Loading data from: ../../crates/rs1090/data/short_flights.csv
Loaded 486 ADS-B messages

============================================================
SUMMARY
============================================================
Messages processed: 486
Messages decoded: 486
Position messages: 163
Aircraft tracked: 9

Batch processing:    0.004s (128438 msg/s)
Realtime processing: 0.003s (176091 msg/s)
Performance: 27.1% faster

Context

I wanted to use rs1090 in python to do live decoding, particularly of aircraft position, which currently does not seem practical (if possible at all).

Notes

• I added a short_flights.csv recording with a minute's worth of messages, containing 486 total messages with 163 positions from 9 different aircraft.

[ccostes]

Not totally sure this is the best idea.

[xoolive]

Thank you I will be able to have a look in the coming days 👍

Just a minor comment I have as I check from the phone, I will probably revert the version change in your commit 😅

[ccostes]

Thanks! I know I'm dropping a big PR on you out of the blue without any design discussion, so feel free to reject any or all of this if it doesn't make sense for the project.

…

On Mon, Aug 4, 2025 at 3:21 AM Xavier Olive ***@***.***> wrote: *xoolive* left a comment (xoolive/jet1090#270) <#270 (comment)> Thank you I will be able to have a look in the coming days 👍 Just a minor comment I have as I check from the phone, I will probably revert the version change in your commit 😅 — Reply to this email directly, view it on GitHub <#270 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN6EBDYIKSQAJXWIXUNLXT3L4CWJAVCNFSM6AAAAACC6CLAGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNBZGQZDIOJWGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xoolive]

Sorry I didn't have time to look at it yet, and the days off don't help :)

Another question about what you have in mind: for the moment, all the real-time decoding is taken care of by the jet1090 executable (in the same workspace, documentation https://mode-s.org/jet1090/).

So what's the use case?

Do you think wrapping the process_single_message for Python and providing the RealtimeDecoder class in pure Python would be enough?

[ccostes]

Good question! Since they are organized as separate crates and the python bindings are only for rs1090 I thought it made sense to implement this functionality there to keep that self-contained. This would enable rs1090 to handle all the low-level decoding while jet1090 just handles the higher-level/UI functionality.

Functionally it seems like exposing the jet1090 processing should work, I just didn't get deep enough in that code to know how to do it. Totally up to you!

[xoolive]

Thank you for the update.
I will consider this all a bit later, probably after implementing the pure Rust rtlsdr though 😉

Maybe I will reimplement things by moving code from crate to crate rather than using your PR, but will definitely keep your suggestions open and credit for the idea.

Let's leave this open for now 👍

[ccostes]

Sounds good! I ended up not needing this for the project I was working on, so no worries on my end what you decide to do or when.

…

On Tue, Aug 26, 2025 at 9:13 AM Xavier Olive ***@***.***> wrote: *xoolive* left a comment (xoolive/jet1090#270) <#270 (comment)> Thank you for the update. I will consider this all a bit later, probably after implementing the pure Rust rtlsdr though 😉 Maybe I will reimplement things by moving code from crate to crate rather than using your PR, but will definitely keep your suggestions open and credit for the idea. Let's leave this open for now 👍 — Reply to this email directly, view it on GitHub <#270 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN6EBHUSP6CDHBBBYKHWQD3PRMODAVCNFSM6AAAAACC6CLAGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMRUGEZDQNRUHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>