satnogs-db issueshttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues2020-07-25T23:39:30Zhttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/256Error on submitting transmitter after clicking on driffted field2020-07-25T23:39:30ZAlfredos-Panagiotis DamkalisError on submitting transmitter after clicking on driffted fieldSTR:
1. Open modal for suggesting new transmitter
2. Fill Name, Frequency, Mode, Baud rate and Source
3. Click on Frequency drifted
4. PPB becomes "NaN"
5. Press Send
6. Getting " We are sorry, but some error occured :("STR:
1. Open modal for suggesting new transmitter
2. Fill Name, Frequency, Mode, Baud rate and Source
3. Click on Frequency drifted
4. PPB becomes "NaN"
5. Press Send
6. Getting " We are sorry, but some error occured :("Improved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/253Follow-up from "Change model of transmitter to include drift and type"2019-07-02T05:19:44ZPierros Papadeaspierros@papadeas.grFollow-up from "Change model of transmitter to include drift and type"The following discussion from !307 should be addressed:
- [ ] @acinonyx started a [discussion](https://gitlab.com/librespacefoundation/satnogs/satnogs-db/merge_requests/307#note_126485139): (+1 comment)
> I think it may be better ...The following discussion from !307 should be addressed:
- [ ] @acinonyx started a [discussion](https://gitlab.com/librespacefoundation/satnogs/satnogs-db/merge_requests/307#note_126485139): (+1 comment)
> I think it may be better to store the frequency drift in PPM instead of frequency in the database. The user can still input the drift (or better the actual observed frequency) in Hz and we can calculate the PPMs in JS with the `Hz * 10^6 / f` formula.Improved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/252Follow-up from "Change model of transmitter to include drift and type"2019-03-04T13:31:09ZPierros Papadeaspierros@papadeas.grFollow-up from "Change model of transmitter to include drift and type"The following discussion from !307 should be addressed:
- [ ] @acinonyx started a [discussion](https://gitlab.com/librespacefoundation/satnogs/satnogs-db/merge_requests/307#note_126450661): (+5 comments)
> What is the use case for...The following discussion from !307 should be addressed:
- [ ] @acinonyx started a [discussion](https://gitlab.com/librespacefoundation/satnogs/satnogs-db/merge_requests/307#note_126450661): (+5 comments)
> What is the use case for having both `uplink_drift` and `downlink_drift`?Improved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/222Add additional TLE sources2019-01-08T17:22:33ZFabian P. SchmidtAdd additional TLE sourcesCurrently we fetch TLEs automatically from Celestrak only. For some satellites their TLE aren't published by Celestrak. Fortunately there are other sources for these satellites.
## Steps.
- [x] Write/Improve a python package which suppo...Currently we fetch TLEs automatically from Celestrak only. For some satellites their TLE aren't published by Celestrak. Fortunately there are other sources for these satellites.
## Steps.
- [x] Write/Improve a python package which supports other TLE sources: https://gitlab.com/kerel-fs/python-satellitetle/ (based on the currently used https://github.com/comzeradd/orbit)
- [x] Use this package in satnogs-db
- [x] Use the new TLE-source `CalPoly` in satnogs-db
- [x] Fetch from `CalPoly` if `CelesTrak` fails
- [x] Save the TLE source in the database
- [ ] Show the TLE source in the frontend (currently hard-coded to `CelesTrak`)Improved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/206list/search by mode, band2020-07-25T22:55:59ZCorey Shieldslist/search by mode, bandWe should offer the capability to search satellites by mode or band. For instance, searching for all satellites with an AFSK1k2 transmitter..We should offer the capability to search satellites by mode or band. For instance, searching for all satellites with an AFSK1k2 transmitter..Improved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/197Transmitter type field2019-04-16T12:58:30ZGhost UserTransmitter type fieldWhen a transponder (repeater) is present in a satellite, we need some additional information.
Proposing the following:
Add a field for "transmitter type". Options should be:
- Telemetry (Only downlink low should be visible from fr...When a transponder (repeater) is present in a satellite, we need some additional information.
Proposing the following:
Add a field for "transmitter type". Options should be:
- Telemetry (Only downlink low should be visible from frequency fields and named Downlink
- Transponder (All freq fields visible and another tone field should be added)
- Telecommand (Downlink_low and Uplink_low marked as Downlink and Uplink fields)
We shall be expanding this in the future to accommodate more options.
Improved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/115Moderate/Approve Suggestions from the frontend2019-04-16T12:43:42ZNikos RoussosModerate/Approve Suggestions from the frontendImproved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/66add interval field2019-04-16T12:53:57ZNikos Roussosadd interval field*Created by: cshields*
In the case that a beacon has a known interval for transmission we should add that.
*Created by: cshields*
In the case that a beacon has a known interval for transmission we should add that.
Improved User Experiencehttps://gitlab.com/librespacefoundation/satnogs/satnogs-db/-/issues/38Need options for beacon/tlm transmitters2019-04-16T12:58:30ZNikos RoussosNeed options for beacon/tlm transmitters*Created by: cshields*
When suggesting a transmitter it is assumed a mix of uplink/downlink ranges. It would be cleaner to cut the ranges down to a single frequency for beacon or tlm downlinks
similarly for FM repeaters... the low/h...*Created by: cshields*
When suggesting a transmitter it is assumed a mix of uplink/downlink ranges. It would be cleaner to cut the ranges down to a single frequency for beacon or tlm downlinks
similarly for FM repeaters... the low/high ranges are good for linear transponders, but that's about it.
Alternatively, UI could be added to indicate which should be used, low or high, when just a single frequency is to be added. (I assume from some other data already there that "low" is the standard in this case - but new contributors might not know that)
Improved User Experience