trusat-frontend
trusat-frontend copied to clipboard
The React codebase for space-sustainability tool TruSat
See error in console when you navigate away from the "catalog" view before the data is returned from the API: ``` Warning: Can't perform a React state update on an...
Currently it is difficult to ascertain some information on the activity of all users in TruSat. One way to do this would be via a user leaderboard. It could just...
The ability for users to highlight objects of interest could be a nice way to point fellow users to a specific object to help bump its observation count. Some reasons...
![Screen Shot 2020-03-10 at 2 35 20 PM](https://user-images.githubusercontent.com/30157175/76347081-65e42880-62dc-11ea-8c40-a36892d92b8c.png) On the Object [view](https://trusat.org/object/45076), it would be nice if the information in the header also included the total number of observations, and...
It is only in the email that they receive upon signup are they told to visit the `/login` route. This is not as friendly a UX pattern as it could...
The raw observations, as they were submitted, should be downloadable, preferably through an API. The API could provide a filter for satellite ID, observer, observation format and a time range.
It would be great to provider the user with a list of objects that will pass by them tonight, similar to how [Heavens Above](https://www.heavens-above.com/PassSummary.aspx) does.
Ideally our users can determine when and where to look to see an object without having to avail of tools like Heavens Above. This feature needs utilize their precise location...
It would help observers if they could have access to the TruSat TLEs through a single, static URL. Observers will want to pull the latest TLEs of all objects from...
With the current implementation: - User submits their IOD(s) - Success/error messaging rendered at the bottom of the form The problem with this is that the user may miss the...