Construct a HQSL from scratch.
No syntax checking is performed at this stage, though it will happen when anything calls signedData.
Optional
fields: {Optional
extra?: stringExtra data.
Frequency in MHz.
QSL sender call sign.
Communication mode.
Optional
signal?: stringSignal report.
QSL recipient call sign.
QSO datetime in UTC.
QSL sender Maidenhead grid location.
Optional
extraExtra data.
Optional
freqFrequency.
Optional
fromSender's call sign
Optional
modeMode.
Optional
reservedReserved field. Don't use it.
Optional
signalSignal report.
Optional
signatureBinary signature data.
Optional
toCorrespondent's call sign.
Optional
verificationVerification results.
Optional
whenQSO date in UTC. Requires the use of date-fns to properly work in UTC.
Optional
whereSender's grid square
Derives an ADIF-standardized band name from frequency.
Derives a date in a generic ISO-like format for display.
Derives a datetime formatted as per HQSL standard.
Constructs a signable string from the HQSL, throwing SyntaxErrors in case of missing or malformed data fields.
The entire HQSL as string sans the signature field.
Formats a complete HQSL as an ADIF string. Will contain a fully encoded .toString() in APP_HQSL_DATA.
A string of a single-QSO ADIF.
Formats a complete HQSL as string. Signed HQSLs will contain the encoded signature, while unsigned will have UNSIGNED in the signature field as the standard specifies.
A string containing the HQSL (sans a header)
Static
fromADIFParses an ADIF file string to construct a series of HQSL. Whether any of it will be signable depends on how complete the ADIF was.
An ADIF file string.
The default call to assume if none is present in the record.
The default grid to assume if none is present in the record.
Static
fromParses a HQSL from string, applying as many verification checks as feasible. Will ignore an URL header if present.
A string containing the HQSL
HQSL object
The HQSL object represents a QSO through the entire parsing, signing and verification life cycle.