Configure MADIS Posting (Weather Data Exporting)

The MADIS Post plugin allows collecting and exporting weather data received by YAAC in a a specified file format. Either comma-separated value (CSV) or JavaScript Object Notation (JSON) format can be used, and any combination of the available weather parameters can be logged for each incoming weather report.

The configuration panel is split into three sub-sections:

• The first section specifies where, how often, and in what format the data will be logged to disk files. This includes:
  1. Whether or not to log weather data at all.
  2. Whether JSON or CSV format should be used.
  3. The directory where the rolling log files will be kept (defaulting to the current YAAC log file directory unless specified elsewhere).
  4. The prefix (before the variable timestamp part) of the filename.
  5. The format of the timestamp in the filename, using standard Java SimpleDateFormat syntax, where the following case-sensitive characters are reserved (and may be specified multiple times to specify the field width) and most other characters are just passed through as part of the formatting:

     Case-sensitive character	meaning
     y	year
     M	month (either number or name, depending on the number of consecutive M characters
     d	day of month
     D	day of year (Julian date)
     H	24-hour hour of day
     h	12-hour (AM/PM) hour of day
     m	minute of hour
     s	second of minute
     w	week of year
     W	week of month
     E	day of week name (Sunday, Monday, etc.); either an abbreviation or the full name, depending on the number of consecutive E characters
     a	AM/PM marker

  6. The suffix of the filename (after the timestamp portion). Typically, this will end with a file type such as .csv or .json.
  7. How often the log file is closed and a new file started. Note that this always lines up with UTC time, so (for example) specifying 1 day for rollover will always start at UTC midnight.
  8. Whether all heard weather-reporting stations should be logged, or only those with valid amateur radio or Citizens Weather Observation Program (CWOP) callsigns should be logged.
• The second section specifies the fields to be logged. A table lists all the fields in left-to-right order in the CSV file (or in the JSON structure for each report) as consecutive rows in the configuration table. For each field, the actual data to be displayed in that field (from a pick-list of available fields), the key name for that field in the JSON structure (or column heading for CSV files), the format the data should be displayed in, a scale factor (used to adjust the magnitude of values not stored in standard units; for example, APRS stores barometric pressure in tenths of millibars, not in millibars, so the value would have to be scaled by 0.1 to be displayed properly in millibars), and the text to be displayed if a given weather-reporting station does not report this type of data.

  The available field content types to choose from are:

  content type code	Meaning
  Callsign	identifier of the sending weather station, such as amateur radio callsign or CWOP ID
  Latitude	weather station latitude in fractional degrees North
  Longitude	weather station longitude in fractional degrees East
  Elevation	station elevation above mean sea level in meters
  Dewpoint	calculated dewpoint (wet bulb) temperature in degrees Fahrenheit
  Fixed Text	arbitrary fixed text to fill a table column
  Receive Time	date and time when weather data was received by YAAC
  Date/Time	date and time that weather data was collected according to weather station clock (if not provided, same as Receive Time)
  Course	wind direction in degrees from True North
  Speed	wind speed in knots
  Gust	peak gust speed in knots
  Temp	ambient temperature in degrees Fahrenheit
  Rain,Last Hour	amount of rain in last hour in .01 inch increments
  Rain,Last 24 Hours	amount of rain in last 24 hour in .01 inch increments
  Rain Today	amount of rain since midnight (station time) in .01 inch increments
  Humidity	percent relative humidity
  Pressure	barometric pressure in 0.1 millibar units
  Luminosity	light intensity in watts per square meter
  Snowfall	depth in inches in the last 24 hours
  Voltage	battery voltage of weather station power in volts

  If the user does not specify field ordering and formatting, a default order and format will be provided, compatible with previous versions of this plugin.

  Below the table are four buttons, allowing the user to add a new field to the list of fields, move a selected field up or down in the list order, or delete a selected field.

• The last part of the configuration panel specifies whether YAAC should send a completed periodic log file to another system via a network transfer. If desired, the user should specify an URL of the destination for the transferred file. For example, to make a secure FTP transfer of the last log file to a remote FTP server, the URL would be specified as:

  ftps://user:password@hostname/pub/weather/{f}
  

  where user is the login username at the FTP server, password is the password for that username, hostname is the domain name or numeric IP address of the FTP server, and the file is to be stored with the name specified in the first section of the configuration panel in the pub/weather subdirectory of the remote user's home directory.

  To do an HTTP POST of the document, replace ftps with http or https in the URL. Note that this is sent with Content-Type of application/json or text/csv (as specified in the first section), not as application/x-www-url-encoded or multipart/form-data. If you require form submittal, please contact the YAAC author to request an enhancement.