Table of Contents

1 · What is URDS Log Validator?

The URDS Log Validator is a browser-based tool for FM DXers. It reads CSV log files that were recorded by TEF6686 / TEF6687-based receivers (URDS format), validates each entry against the live fmdx.org transmitter database, and assigns a confidence score to every reception.

The tool helps you to:

• Identify which stations you actually received (PI code + PS name cross-checked with the real transmitter database)
• Preserve mixed log data (file headers, DAB logs, etc.) perfectly intact in their exact original chronological sequence during export
• Correct wrong or incomplete station metadata directly in the browser
• Filter your log by distance, score, country, or free text
• Visualise receptions on an interactive embedded map, and apply fixes directly from the map
• Export a cleaned, enriched CSV that is ready for upload to FMLIST or further analysis in the URDS Map Viewer

2 · Interface Overview

2.1 · Header Bar and Manual Link

The header bar runs across the full width of the page and consists of three zones:

2.2 · Upload Bar Buttons

Directly below the header bar is the upload / action bar. Its buttons change visibility depending on the application state:

3 · Quick Start – Uploading a Log File

3.1 · Upload via File Button

Click the Upload File button in the upload bar. A file picker opens. Select your .csv log file. The tool accepts only .csv files. If you select a file with a different extension a warning toast appears and the upload is blocked.

3.2 · Upload via Clipboard / URL

If your log is already in the clipboard (copied from a text editor or directly from the receiver software), click Process from Clipboard. The tool reads the clipboard text and processes it exactly like a file upload. An empty clipboard triggers an orange warning toast.

3.3 · No Import Duplicates Option

The checkbox No import duplicates (next to the upload buttons) controls what happens when the CSV contains multiple rows with identical Frequency + PI + PS combinations:

3.4 · AI RDS Validation Toggle

The TEF Logger App (version 6.0 and later) or the RDS AI Decoder for the FM-DX Webserver can provide AI-processed PI and PS values. The "No validate AI RDS" checkbox controls how this AI data (which is provided in fields 45–47) is handled during validation:

4 · The Station Database (fmdx.org)

Immediately after the CSV is loaded, the tool determines the receiver location from the GPS coordinates stored in the first valid log row. It then downloads the complete FM transmitter database for that location from:

https://cors-proxy.de:13128/https://maps.fmdx.org/api/?qth={lat},{lon}

The download is cached in the browser's localStorage for the current calendar day. On the next load the cached data is used – no second network request is made unless you clear your browser storage or use a different location.

5 · Validation Progress and Cancellation

After the station database is loaded, all rows are validated asynchronously. This keeps the browser responsive even for very large log files (thousands of rows). The progress is shown in the header bar centre zone:

The table updates live every 500 ms during validation – you can already sort, filter, and interact with already-validated rows before the full validation completes.

6 · The Results Table – Column Reference

7 · Validation Score – How it Works

Each log row is validated against the fmdx.org database. The result is a score between 0 and 100 that reflects how confidently the received station has been identified.

7.1 · Score Components

7.2 · Match Levels

7.3 · Row Colours and Score Circles

Each row in the table is colour-coded. Fixed rows always appear in blue regardless of score:

The score circle in the Score column mirrors the row colour:

85  ≥74% (green)    55  40–73% (orange)    12  <40% (red)    100  Fixed (blue)

8 · Summary Bar and Statistics Rings

The summary bar appears directly below the upload buttons as soon as a log is loaded. It shows at a glance how many entries are in the log and how they are distributed across score categories.

9 · Filters and Search

Click the Show Filters button (toggles to Hide Filters) to reveal the filter bar. The filter bar is organised in two rows. All filters are applied simultaneously and update the table in real time.

9.1 · Score / Colour Filter and Pills

The dropdown Score / colour limits the table to rows in a specific confidence category:

The five coloured filter pills (🟢 ≥74%, 🟡 40–73%, 🔴 <40%, 🔵 Fixed, ⬜ Unidentified) act as toggle buttons for the same filter. Clicking an active pill deactivates the filter (returns to "All entries"). The pills are located in filter row 1, directly after the Reset Filters button.

9.2 · Distance Filter

The distance filter features an interactive Radius Range slider that allows filtering rows based on their distance from the receiver to the transmitter:

Only rows whose calculated distance falls within the selected slider range will be displayed. If the maximum handle is pulled all the way to the right, it equates to "Infinity" (∞ km), placing no upper limit on the distance.

9.3 · PI Code Exclusion

The Exclude PI codes input field (filter row 2) accepts a comma-separated list of PI codes to hide from the table, e.g. F201,F731. This is useful to temporarily suppress known local stations. The filter is case-insensitive and the leading 0x prefix is stripped automatically.

9.4 · Free-text Search

The search box (🔍 Search table…) in filter row 2 filters the table by any text. The following fields are searched simultaneously: Date, Time, Frequency, PI, PS, Station, City, ITU, Station ID.

9.5 · Hide Duplicates / Hide Unidentified

The Reset Filters button (filter row 1) clears all filters, checkboxes, text inputs, and slider positions in one click.

10 · Sorting the Table

Click any column header to sort the table by that column. A second click on the same header reverses the sort direction. The current sort column is indicated by a ▲ (ascending) or ▼ (descending) arrow next to the header text.

11 · Detail Row – Validation Breakdown

Click the ▶ button at the start of any row to expand its detail view. The button changes to ▼ when open. Click again to collapse.

The detail row shows a full breakdown of how the validation score was computed:

At the bottom of the detail row, a collapsible "All DB entries on X MHz" table shows every station the database knows for this frequency – useful for manual cross-checking in ambiguous cases. This table includes the calculated distance (Dist) to each transmitter, and you can click on any column header to sort the list. This section only appears when there are two or more DB entries on the frequency.

12 · Fix Functions

When the validation reveals that metadata is missing or incorrect, the fix functions let you update the row with correct data directly from the database.

12.1 · Manual Fix (✏ Fix Button)

The ✏ Fix button opens the Fix overlay for that row. The overlay has three sections:

1 – Transmitter selector

A checkbox "Show only transmitters with matching PI" pre-filters the candidate list to entries that match the PI code. Uncheck it to see all transmitters on this frequency. By matching only the PI and ignoring the PS, the tool easily handles instances where your receiver captured an incomplete PS fragment or dynamic text. The dropdown starts with an empty default option—you must actively select a transmitter from the list to prevent accidental wrong assignments. The transmitter list is sorted by ascending distance from the receiver (nearest first). Each entry shows station name, city, PI, PS, ERP, ITU code, calculated distance in km, and calculated azimuth in degrees.

2 – PS variant selector

After selecting a transmitter, the second dropdown shows all known PS name variants for that transmitter. The default option "Keep logged PS: …" preserves the received PS with its original casing as-is. You can also choose the "Leave PS empty" option to clear the PS field, or select a DB variant to replace it in the exported CSV. Original casing from the database is preserved throughout.

3 – Diff table

A comparison table shows the current values (left column) and the new values from the selected candidate (right column). Distance and azimuth are dynamically recalculated based on the selected transmitter's coordinates. Changed values are shown underlined and bold in blue. Hover over an underlined value to see the old value in a tooltip ("Was: …").

Apply buttons

12.2 · Auto Fix per Row (⚡ Auto Button)

The ⚡ Auto button applies an automatic best-candidate fix to a single row without opening the overlay. The algorithm picks the best candidate using this priority ladder:

1. Station ID lookup: If the row already has a valid FMLIST station ID, look up that ID directly in the database. If the frequency matches (within ±0.15 MHz), use it immediately.
2. Copy from existing row: Search all other rows in the log for a row with the same Freq + PI + PS that already has a valid station ID and a confirmed bestMatch. If found, copy that match directly (avoids redundant DB lookups for frequently-logged stations).
3. Level 1 DB match: Find all DB entries on this frequency matching both PI and PS. If multiple, pick the one with the highest tx_search score (ERP weighted by distance).
4. Level 2 DB match: PI-only match (no PS requirement), ranked by tx_search score.
5. Level 3 DB match: PS-only match (one candidate only).

If no candidate can be found at all, a red toast notification "Row N: no DB candidate found." is shown and no changes are made.

12.3 · Auto-Fix All (⚡ Auto-Fix All Button)

The ⚡ Auto-Fix All button (in the upload bar, visible after loading) runs the automatic fix algorithm on every row that is not yet complete. An animated progress overlay shows the current progress:

13 · Deleting Entries

The 🗑 Del button opens the Delete confirmation overlay. It always shows a preview table of the row(s) that would be affected. The overlay can also be dismissed by clicking outside the modal box.

14 · Map View (🌐 Globe Icon)

The 🌐 globe icon appears in the ID column for any row that has a database match (a best-match entry with known coordinates). Clicking it opens a full-screen embedded map overlay powered by Leaflet.js and OpenStreetMap tiles. Leaflet is loaded lazily – no map libraries are downloaded until the globe icon is first clicked.

14.1 · Opening the Map

Click the 🌐 globe icon in the ID column of any row. The map overlay appears, covering the full viewport. It can be closed at any time with the ✕ Close Map button (top-right of the overlay) or by clicking anywhere outside the map box.

14.2 · Map Markers and Layers

The map always shows the following layers simultaneously:

Hovering over any marker highlights its connecting line (if present) and opens the tooltip. Moving the mouse away restores the default line style.

The map viewport is automatically fitted to encompass all plotted markers with 40 px padding. If only the QTH is available (no TX coordinates found), the map centres on the QTH at zoom level 7.

14.3 · Applying a Fix from the Map

Clicking a red alternative TX marker opens the Fix from map dialog on top of the map overlay. The dialog shows a summary table of the values that would be written to the row if the alternative transmitter is applied:

15 · Download and Clipboard Export

15.1 · ⬇ Download Filtered CSV (Web Version)

Clicking this button generates a new CSV file containing all currently visible FM rows. Crucially, the export strictly preserves the exact chronological sequence of your original log file. This means any non-FM lines (such as file headers like 10, 11 or DAB logs starting with 20, 21) are kept completely intact and are written back exactly where they appeared in the original file.

For the FM data, it exports exactly what is shown in the table (meaning all active filters, like distance limits or "Hide unidentified", apply to the exported FM rows). The exported file is named validated_{original_filename}.csv.

15.2 · 📋 Copy to Clipboard (Web Version)

Copies the filtered, enriched CSV data directly to your system clipboard, maintaining the exact same sequential preservation of headers and non-FM logs as the file download. You can immediately paste this into Excel, a text editor, or directly into the FMLIST manual upload page.

15.3 · Fixed Column Count Guarantee

Whether downloading or copying to clipboard, the tool ensures every row has exactly 49 columns (including the Comment column), padding empty fields with commas. This guarantees strict compatibility with the FMLIST Upload portal and preserves RAW data perfectly.

16 · TEF Logger App Integration (Smartphones)

When the URDS Log Validator is launched directly from within the TEF Logger App on a smartphone, it operates in a special integrated mode optimized for mobile workflows:

• Automatic Synchronization: Manual file upload, download, and clipboard buttons are completely hidden. The app automatically pushes your selected log data straight into the validator interface.
• 💾 Save to App: A dedicated "Save to App" button replaces the standard export options. Clicking it syncs your validated log (and any edited comments) directly back to the app's local storage. The app will prompt you if you wish to overwrite the existing log or save it as a new file.
• Inline Comment Editing: The "Comment" column becomes interactive. You can tap directly into the comment cells to add or edit text using your on-screen keyboard. These edits are preserved perfectly when you save the log back to the app.

17 · Webtools Panel

At the very top of the page, a collapsible panel links to the entire suite of Highpoint's FM DX web tools (such as the TEF Converter, URDS ID Inserter, Map Viewer, etc.).

18 · Supported CSV Format (URDS)

The tool parses standard URDS format. While the validator specifically processes and visualises FM log entries (Record type 30), it safely reads and preserves all other record types (e.g., headers, AM/DAB logs) in the background. The crucial fields for the FM validation are:

• 0: Record type (30)
• 3: Frequency (Hz)
• 5: Signal strength (dBµV)
• 8/9: Receiver Latitude/Longitude
• 12: ISO 8601 Timestamp
• 13: PI Code (hex)
• 15: PS Name
• 30: Station ID
• 31: AF List
• 45: AI RDS
• 46: AI PI
• 47: AI PS
• 48: Comment

19 · Typical Workflow

1. Open the Validator and upload your raw receiver CSV log (or let the TEF Logger App auto-load it).
2. Wait a few seconds for the station database download and automatic validation to complete.
3. Click ⚡ Auto-Fix All to automatically resolve the easy cases.
4. Click the 40-73% or <40% filter pills to isolate uncertain matches.
5. Use the ✏ Fix button or the 🌐 map to manually assign the correct station ID to the remaining ambiguous receptions.
6. (Optional) If using the App, click the Comment cell to type notes directly into the table.
7. Click Download filtered CSV (or Save to App if integrated) to save your enriched, clean log file.