Hello,
You are very welcome to improve it. This project is totally open to contributors. If we all contribute to it, we can build something very useful for everyone.
About duplicate satellite, this is an issue of using the norad id as id and will be solved once and for all when we move to satellite uuid.
For the transmitters indeed, there is a mess right now due to having in the past new transmitter for each drift on frequency.
There is currently a lot of work on the database to clean it.
By the way, this is also the database that is used by Gpredict.
To contribute you can meet the community there : https://riot.im/app/#/room/#satnogs:matrix.org or IRC #satnogs on freenode forum : https://community.libre.space/
If you have more questions, feel free to ask.
Julien
Le 15/06/2019 2:37, Martin Cooper via AMSAT-BB a écrit :
I'd been contemplating using the SatNOGS database to do automated lookups of transmitter info for satellites (from code), but frankly the database seems to be a bit of a mess. For example, in the 'satellites' database, there are cases of the same satellite name mapping to multiple NORAD catalog ids, the 'names' field being used inconsistently (and even containing an essay about the satellite in one case), and so forth. Similarly, the 'transmitters' database also has issues.
Is there a more reliable source that can be queried through an API? I know N2YO has an API, but it's focused on real-time tracking, and doesn't appear to include transmitter info (though the site's satellite pages do).