• Filter QSOs
• Find duplicate QSOs
• Find "invalid" QSOs
  • Checks for missing mode/band/callsign
  • Checks for an invalid date (01011970)
  • Checks if invalid continent is set
• Export QSOs to ADIF
• Print labels
• Batch edit QSOs
• Delete QSOs
• Show a map of filtered QSOs
• Update QSOs from a callbook (QRZ, HamQTH, QRZCQ, QRZ.ru)
• See a QSL slideshow with selected QSOs that contain an uploaded image of a QSL card
• Fix state where at least a 6 char gridsquare is set (only available for a limited set of DXCC's)

(from version 2.2.x - not yet released)

The Database Tools module in Wavelog provides a comprehensive suite of utilities for maintaining data integrity and repairing common issues in your logbook data. These tools are accessible through the Advanced Logbook interface and are designed to help operators keep their QSO records accurate and complete.

DBTools offers automated checking and fixing functionality for various types of QSO metadata that may be missing, incorrect, or outdated.

• Purpose: Updates missing CQ zone information
• Function: Validates DXCC against default CQ zone
• Use Case: Essential for award applications like CQ WAZ (Worked All Zones awards)

• Purpose: Updates missing ITU zone information
• Function: Validates DXCC against default ITU zone
• Use Case: Required for ITU-sponsored awards and contests

• Purpose: Updates missing or incorrect continent information
• Function: Determines continent based on DXCC entity
• Use Case: Useful for continental award tracking and statistics

• Purpose: Updates missing state or province information
• Function: Uses 6 char (or greater) grid square and location data to determine administrative divisions
• Use Case: Critical for WAS (Worked All States) and similar award programs

• Purpose: Calculates and updates distance information for QSOs
• Function: Computes great-circle distances between stations based on gridsquare set in station location and on QSO.
• Use Case: Important for distance-based awards and personal statistics

• Purpose: Identifies QSOs missing DXCC information
• Function: Cross-references callsigns and timestamps with DXCC entity database
• Use Case: Essential for DXCC award tracking and eQSL/LoTW verification

• Purpose: Re-evaluates all QSOs for correct DXCC assignment
• Function: Overwrites existing DXCC data using current Wavelog database
• Use Case: Useful when DXCC boundaries have changed or initial imports were incorrect

⚠️ Warning
This tool will overwrite ALL existing DXCC information.

1. Scanning: Each tool performs a comprehensive scan of the logbook database
2. Validation: Data is cross-referenced against various sources (DXCC lists, zone definitions, county/provinces geojson)
3. Reporting: Results display the number of records needing attention

• Tools can process thousands of QSOs efficiently

• Most tools operate in check mode first, allowing review before applying fixes

• Navigate to Advanced Logbook → DBTools tab
• Requires appropriate user permissions (typically admin or logbook owner)

• Left Panel: Tool selection and action buttons
• Right Panel: Real-time results and progress information
• Actions: Check, Fix, Run or Update buttons depending on tool type

1. Step 1: Use Check buttons to identify issues
2. Step 2: Review results and affected QSOs
3. Step 3: Apply fixes using the appropriate action button
4. Step 4: Wait until the fix is done

• DXCC entity database from CLub Log
• Zone definitions from CQ and ITU specifications
• Administrative boundary data for state/province determination

• Batch processing optimized for large logbooks
• Memory-efficient database queries

1. Backup First: Always create a logbook backup before running bulk fixes
2. Review Results: Carefully examine what will be changed before applying fixes
3. Monitor Progress: For large logbooks, allow adequate processing time
4. Verify After: Spot-check results after fixes are applied to ensure accuracy

• Memory Limits: Large logbooks may require increased PHP memory limits
• Timeout Issues: Long operations may need extended execution time limits
• Coordinate Accuracy: Some fixes depend on accurate grid square data