Configure General

This tab of the Configure dialog specifies the general parameters controlling message reception and logging.

The options that can be changed here are:

• The maximum age of messages that will be seen in the GUI, and how long messages will be kept in memory. Anything older than the specified viewing time interval (relative to current time) will be hidden on the map or grayed out in the sniffer window. Any messages older than the retention limit will be deleted from memory.
• Whether or not received APRS packets and GPS sentence data should be recorded in log files. Note that transmitted packets are always logged, to comply with any local jurisdictional regulations.
• The directory where log files will be kept. The button at the end of the line launches a directory selection dialog to allow changing where log files will be kept.
• The format of AX.25 message log files (using the same formats available on the File->Load->APRS Packets and File->Save->APRS Packets menu choices).
• The format for GPS log files. The options include:
  • The legacy format used by older builds of YAAC, where whatever ASCII text was received from the GPS data source was logged in the received format, and both local and remote GPS data were merged into one file.
  • CSV (comma-separated values) format, with latitude, longitude (both in fractional degrees North or East), altitude in meters above (or below) mean sea level, and the date and time of the data point. Separate files will be written for the local source and each of the named remote sources. Note that this format is compatible with the latitude-first CSV format used by the draw layer.
  • NMEA-0183 sentence format (regardless of the incoming format). Separate files will be written for the local source and each of the named remote sources.
  • GPSD-structured JSON (regardless of the incoming format), one complete structure per line of text containing either a structure of "class":"TPV" (for position information) or "class":"SKY" (for satellite constellation information. Separate files will be written for the local source and each of the named remote sources. For further information, the JSON Structure is documented at the GPSD JSON protocol specification at https://gpsd.gitlab.io/gpsd/gpsd_json.html.
  • XML in the GPX (GPS eXchange format) schema for tracks. Only logged when valid GPS fixes are available; if a GPS reception drop-out occurs, that will end a track segment, and start another one when reception is restored. Separate files will be written for the local source and each of the named remote sources.
• The directory where the segmented binary-encoded (tile) copies of OpenStreetMap data should be stored, and also where such data will be read from when rendering maps upon the GUI. The button at the end of the line launches a directory selection dialog to allow changing where tile files will be kept.
• Message addressees that will be handled as locally addressed (directed to this station). Note these are in addition to any callsigns associated with TNC and APRS-IS ports on your installation of YAAC.