Conversation
DX cluster nodes sometimes populate dxGrid with incorrect data — the spotter's grid, a cached home grid, or just wrong data. Since grid-from-spot was priority #1 (before DXpedition lookup), some TX5EU spots showed in Jersey and VK9 spots showed in Alaska. DXpedition entity lookup now runs FIRST, before any cluster-provided grid squares. DXpedition coordinates are authoritative — the NG3K entity mapped to cty.dat coordinates won't randomly change per spot. For non-DXpedition callsigns, the grid-from-spot remains highest priority since it's usually accurate for regular stations. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DX cluster nodes sometimes populate dxGrid with incorrect data — the spotter's grid, a cached home grid, or just wrong data. Since grid-from-spot was priority #1 (before DXpedition lookup), some TX5EU spots showed in Jersey and VK9 spots showed in Alaska.
DXpedition entity lookup now runs FIRST, before any cluster-provided grid squares. DXpedition coordinates are authoritative — the NG3K entity mapped to cty.dat coordinates won't randomly change per spot.
For non-DXpedition callsigns, the grid-from-spot remains highest priority since it's usually accurate for regular stations.
What does this PR do?
Type of change
How to test
Checklist
server.js: caches have TTLs and size caps (we serve 2,000+ concurrent users)var(--accent-cyan), etc.).bak,.old,console.logdebug lines, or test scripts includedScreenshots (if visual change)