List view
Many scenarios of APRS decode are handled, but yet many are not. For this milestone to be complete, the APRS Parser should handle the majority of APRS packet decodes successfully.
No due date•10/21 issues closedIt's likely that APRS# has been a console app before now. For this milestone to be complete, APRS# should be an app with a beautiful UI for viewing and creating APRS messages. Likely specialized screens for weather display or map view. Preferably this should be sharing code to run across mobile devices and computers. Consider Xamarin https://dotnet.microsoft.com/apps/xamarin, .NET MAUI https://devblogs.microsoft.com/dotnet/introducing-net-multi-platform-app-ui/, or another similar platform.
No due date•1/2 issues closedARPS# should be able to take user input APRS and AX.25 encode them and transmit them via TNC and FM radio.
No due date•4/4 issues closedAPRS# should be able to connect to the Automatic Packet Reporting System - Internet Service http://aprs-is.net/, receive packets, decode them, and display them on the screen in a human-readable format. ## User story User story: "As a amateur radio operator, I want to use APRS# to connect to the APRS-IS to view messages relevant to me." ## Acceptance Criteria * APRS# should be able to receive packets over the internet from the APRS-IS * APRS# should display received packets to the user in readable English * User should be able to specify packet filters on location or sending station call sign and see only packets which meet those filtering requirements
No due date•22/24 issues closedTo complete this milestone, demonstrate that APRS# can receive packets directly over the air with a terminal node controller connected to the computer via USB or another method (consider bluetooth or IP connections for software TNCs). The TNC should be connected to an FM receiver.
No due date•3/3 issues closedCameron has written starts to APRS message decoding, AX.25, and KISS protocol (for terminal node controllers) libraries. The should be open sourced and cleaned up including: * Transitioning libraries to .NET Standard (likely version 2.1) * Unifying namespaces in to the `AprsSharp` namespace instead of the various pet project names * Changing in to the directory structure for this repository * Unifying projects under a single new solution file to simplify building and testing Directory structure should be /src /Project Project.csproj /test /Project TestProject.csproj AprsSharp.sln
No due date•25/30 issues closed