-
Notifications
You must be signed in to change notification settings - Fork 67
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
[QUESTION] Ephemeris file source #176
Comments
Hello im also interested in this. |
I have no idea unfortunately. My own watch died a couple of years ago, so I can't really help here. Sorry. |
No problem @ryanbinns @TiceRex I found this : https://choaristudio.com/ I wish I knew where the person that hosts that is getting the files from. |
Unfortunately the extended ephemeris is a proprietary file format. The files that can be found online are all provided by either the chipset manufacturer or third-party service provider that don't necessarily have the ability to generate the files themselves.. I guess being so protective of the file format, means it's still generating licensing revenue, and we won't see any open sourced tool to generate them (even though it might not be too difficult given that the underlying ephemeris and almanac data are publicly available). Once tomtom stops serving the files, we would rely on another provider (like the one mentionned by @falsovsky, however I asked, and they also plan to stop serving the files in the near future..). |
An alternative config for the ephemeris file exists thanks to #181. Pull and rebuild the project! |
Thank you for this excellent project!
Regarding the demise of TomTom Sports product line by the end of September 2023: does anybody know any alternative source to the ephemeris file?
Is it a proprietary file format? Can it be generated from the official sources like this one?
https://cddis.nasa.gov/Data_and_Derived_Products/GNSS/broadcast_ephemeris_data.html
I would like to use the watch as long as I can, but without correct GPS data it seems to be impossible.
The text was updated successfully, but these errors were encountered: