Skip to content

Capability: answer APRS queries #200

Closed
2 of 2 issues completed
Closed

Description

@gx1400

Goal: a station built on APRS.NET answers the standard queries like a good citizen: directed queries such as ?APRSP and ?PING?, and general ones such as ?APRS? and ?IGATE?, with the random delays APRS101 asks for. AprsMap needs this to respond to queries (F2.8).

Recognising queries and building the answers does no I/O: the app supplies its state (position, status, heard stations) and sends what comes back.

Done when:

  • the APRS101 chapter 15 examples are recognised and answered as the spec describes;
  • the API is in a release AprsMap can reference.

Brief: AprsMap docs/aprsnet/gaps.md G19.

Activity

  1. added this to the 0.6.0-alpha.1 milestone on Oct 17, 2026
  2. added
    capabilityA release goal; its sub-issues are the work
    blocks: AprsMapBlocks an AprsMap feature issue; see its milestone in APRS-NET/AprsMap
    priority: lowDo if time allows; can move to a later milestone
    on Oct 17, 2026
  3. gx1400 commented on Oct 20, 2026

    @gx1400
    ContributorAuthor

    Done in 0.4.0-alpha.12: QueryReport recognises general and directed queries (4d2d3c1), and QueryResponder in AprsNet.Messaging answers them with APRS101's random delays (2fbd157). The APRS101 chapter 15 examples are covered in QueryResponderTests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blocks: AprsMapBlocks an AprsMap feature issue; see its milestone in APRS-NET/AprsMapcapabilityA release goal; its sub-issues are the workpriority: lowDo if time allows; can move to a later milestone

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions