gocldb: Club Log DXCC database handling library

How to use

• Run gocldb.LoadCtyXml() to initialize the database
  • Takes one or two seconds to startup
  • ~ 200msec on Mac mini 2023 (M2 Pro)
• Changed: the debug log output is discarded by default
  • Use gocldb.SetDebugOutput(os.Stderr) to enable debug output
• Use gocldb.CheckCallsign(call, qsotime) to search the databse
  • result in gocldb.CLDCheckResult format defined in checkcall.go
    • Use only the public members of gocldb.CLDCheckResult
• See ctyxmldump and dxcccl command source code for the basic usage details

Usage example

• From 0.2.0: make DebugLogger unexported and provide a setter: func SetDebugOutput(w io.Writer) that calls DebugLogger.SetOutput(w). This preserves the existing dxcccl.go use case (gocldb.DebugLogger.SetOutput(os.Stderr)) without exposing the variable itself.

// Initialize the database
gocldb.LoadCtyXml()
// Enable debug logging if needed
if *debugmode {
  gocldb.SetDebugLogger(os.Stderr)
}
// Print version string
// gocldb.CLDVersionDateTime has the type time.Time 
fmt.Println(gocldb.CLDVersionDateTime.Format(gocldb.ClublogTimeLayout))
//...
// Look up the database
result, err := gocldb.CheckCallsign(call, qsotime)

cty.xml file

cty.xml is distributed from Club Log with individual explicit permission for each user. See Downloading The Prefixes And Exceptions As XML for the further details to obtain the file.

Note: use the cty.xml verion 2023-12-07T20:31:25+00:00 or later for proper handling of E5/N prefix.

File search sequence of cty.xml

• /usr/local/share/dxcc/cty.xml
• (directory where the executable file resides)/cty.xml

Tools

• ctyxmldump: Dumping cty.xml loaded data as maps
• dxcccl: search the database with a callsign and optional date/time
• See goadifdxcccl in goadiftools

LICENSE

MIT

Acknowledgment

• Michael Wells, G7VJR, for the generous support from Club Log

Usage of AI

• Claude Code is used to verify and fix the vulnerabilities of the code.

[End of document]