Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPS constellation: display Pseudo-Random Noise (PRN) number #115

Closed
rouseabout opened this issue Sep 4, 2023 · 2 comments
Closed

GPS constellation: display Pseudo-Random Noise (PRN) number #115

rouseabout opened this issue Sep 4, 2023 · 2 comments

Comments

@rouseabout
Copy link

Feature request: for GPS satellites, display PRN number on the transceivers data page.

All NAVSTAR/GPS satellites transmit on the same L1/L2 frequencies, and use Pseudo-Random Noise (PRN) sequences, or Gold codes, to differentiate themselves from one another. PRNs are published here: https://www.navcen.uscg.gov/gps-constellation Another list with NORAD IDs: https://www.n2yo.com/satellites/?c=20

Alternatively, Issue #78 ("own short comment to each tracked satellite") might satisfy this feature request.

@rt-bishop
Copy link
Owner

Hey @rouseabout, thanks for reporting this. Look4Sat uses various providers of TLE files, which only contain the info for the satellites orbits, and uses SatNOGS api to get info about the active transponders on the satellites. Since PRN info is only related to transponders, it should be received from transponders data providers.

Ideally it would be great to get SatNOGS to display GPS transponders with frequencies and all the other info you may need just like they do for Amateur satellites. https://db.satnogs.org/api/transmitters/

So it'd be great if you're willing to chat to SatNOGS about including this additional data into their DB and API. It'd be even better to cover much more transponders, like the Starlinks for example. I'm happy to extend the amount of fields I read from their api, to make the UI adjustments for additional info regarding the GPS transponders, but I don't see much value in parsing separate websites just to get this piece of info.

Alternatively, you may want to wait until I implement #78, and I can't give you any estimations on that.

@rouseabout
Copy link
Author

Understood. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants