Public Satellite and aircraft data
ATLAS-X 0.9.6 — LIVE CONNECTIONS
=====================================
INSTALL
1. Extract the ZIP to a normal folder.
2. Run installer.bat.
3. Atlas-X installs per-user under %LOCALAPPDATA%\Atlas-X.
4. Confirm the interface says 0.9.6 ANOMALY MATH + SOURCE PINPOINT.
WHAT THIS BUILD CHANGES
- Adds a real measurement-ingestion stage before the automatic classifier.
- Attempts to discover and normalize public spectrum/PSD measurements exposed by SpecScape's public web/API surface.
- Adds a concrete local wideband path for an attached RTL-SDR using rtl_power.
- Local RTL-SDR scans measure PSD energy/peaks only; Atlas-X does not decode communication content.
- Every accepted spectrum measurement is passed through the existing automatic classifier:
explicit authorized/private metadata -> private/red
credible public-context match -> known/public
unmatched measured emission -> unresolved/amber
valid located-source coordinates -> cyan source-fix ring/cross immediately
compatible separated bearings -> cyan source-fix ring/cross from triangulation
- Public aircraft/satellite/RF layers remain background reference data even when hidden on the map.
LIVE SPECTRUM PANEL
Public spectrum network:
- "Discover + ingest" calls Atlas-X's local SpecScape adapter.
- The adapter is deliberately restricted to specscape.org and tries public GET endpoints it can discover.
- If the current public deployment does not expose an unauthenticated PSD route in a form Atlas-X can normalize, the panel says so explicitly instead of reporting a fake success.
Local wideband receiver:
- Atlas-X looks for rtl_power.exe in Atlas-X\Tools, the Atlas-X folder, or PATH.
- Connect a compatible RTL-SDR and provide the receiver latitude/longitude.
- Choose start/end MHz, bin width, and peak threshold, then press "Scan local spectrum".
- Detected PSD peaks become real measured reports and are auto-classified.
- Without direction-finding information, local peaks are plotted at the receiver position. If a receiver/feed already supplies a valid target/source/object location, Atlas-X uses it immediately and overlays a cyan source-fix ring/cross. Bearing fusion is only needed when the source location is not already supplied.
IMPORTANT LIMITS
- A normal PC alone cannot measure arbitrary RF activity worldwide. It needs public spectrum-sensor data, a local SDR, or other authorized receiver feeds.
- "Private" is never inferred merely because a source is unknown. Red requires explicit authorized/private metadata.
- "Unknown" means a real measurement survived current known-source matching; it does not establish origin or intent.
- Atlas-X does not access protected/private communications or decode their contents in this build.
DIAGNOSTICS
Installer log: %TEMP%\Atlas-X-install.log
Server log: %TEMP%\Atlas-X-server.log
UNINSTALL
Run uninstaller.bat.
LOCATED SOURCE RULE (0.9.6)
- A cyan source-fix ring/cross is shown immediately for any measured report with a valid located source coordinate.
- Supported coordinate names include targetLat/targetLon, sourceLat/sourceLon, objectLat/objectLon, locatedLat/locatedLon, locationLat/locationLon, detectedLat/detectedLon, fixLat/fixLon, and geolocatedLat/geolocatedLon.
- Generic lat/lon can also be treated as the source location when isLocated/located/geolocated/sourceLocated is true or positionRole/locationRole is target/source/object/located/fix/geolocated/detection.
- receiverLat/receiverLon remain the receiver coordinates and do not create a source-location marker by themselves.
- Triangulated bearing intersections still create a cyan source-fix ring/cross as an additional location method.
LIVE CONNECTIONS (0.9.6)
- Atlas-X reads current Windows TCP connections and UDP endpoints from the local machine through its localhost backend.
- PRIVATE = remote/local endpoint is in loopback, RFC1918, link-local, or IPv6 local ranges. Display: red dot.
- UNKNOWN = active endpoint is not classified as private by the local address rules. Display: neon-green crosshair.
- PRIVATE and UNKNOWN connection filters are normal editable checkboxes and default on.
- The live list refreshes automatically every 2.5 seconds.
0.9.6 ANOMALY / MAP RULE
- Unresolved effective anomaly >= 0.75 = animated white→yellow→green→blue crosshair.
- The marker is awarded by anomaly state, not by localization confidence.
- If a target/source location is supplied, the special crosshair is placed there immediately.
- If separated receiver bearings triangulate the source, a high-anomaly fused source keeps the same special crosshair at the solved coordinates.
- Ordinary lower-anomaly fused fixes remain cyan.
- Selecting a high-anomaly report or pinpointed high-anomaly fused fix shows captured/decoded source data when the feed supplied it, plus the derived Atlas-X fingerprint.
0.9.6 NOVELTY MATH
- Robust per-feature z-scores use median and MAD over recent comparable background reports.
- Combined robust distance is converted into a 0..1 novelty score.
- Supported signal features include frequency, bandwidth, SNR/power, symbol/PRF/pulse characteristics, Doppler/chirp, entropy/flatness, kurtosis/skewness, autocorrelation, and spectral prominence when supplied.
- Computed novelty can raise the effective anomaly after sufficient background support; it never lowers a feed-supplied anomaly score.
ATLAS-X 0.9.6 — LIVE CONNECTIONS
=====================================
INSTALL
1. Extract the ZIP to a normal folder.
2. Run installer.bat.
3. Atlas-X installs per-user under %LOCALAPPDATA%\Atlas-X.
4. Confirm the interface says 0.9.6 ANOMALY MATH + SOURCE PINPOINT.
WHAT THIS BUILD CHANGES
- Adds a real measurement-ingestion stage before the automatic classifier.
- Attempts to discover and normalize public spectrum/PSD measurements exposed by SpecScape's public web/API surface.
- Adds a concrete local wideband path for an attached RTL-SDR using rtl_power.
- Local RTL-SDR scans measure PSD energy/peaks only; Atlas-X does not decode communication content.
- Every accepted spectrum measurement is passed through the existing automatic classifier:
explicit authorized/private metadata -> private/red
credible public-context match -> known/public
unmatched measured emission -> unresolved/amber
valid located-source coordinates -> cyan source-fix ring/cross immediately
compatible separated bearings -> cyan source-fix ring/cross from triangulation
- Public aircraft/satellite/RF layers remain background reference data even when hidden on the map.
LIVE SPECTRUM PANEL
Public spectrum network:
- "Discover + ingest" calls Atlas-X's local SpecScape adapter.
- The adapter is deliberately restricted to specscape.org and tries public GET endpoints it can discover.
- If the current public deployment does not expose an unauthenticated PSD route in a form Atlas-X can normalize, the panel says so explicitly instead of reporting a fake success.
Local wideband receiver:
- Atlas-X looks for rtl_power.exe in Atlas-X\Tools, the Atlas-X folder, or PATH.
- Connect a compatible RTL-SDR and provide the receiver latitude/longitude.
- Choose start/end MHz, bin width, and peak threshold, then press "Scan local spectrum".
- Detected PSD peaks become real measured reports and are auto-classified.
- Without direction-finding information, local peaks are plotted at the receiver position. If a receiver/feed already supplies a valid target/source/object location, Atlas-X uses it immediately and overlays a cyan source-fix ring/cross. Bearing fusion is only needed when the source location is not already supplied.
IMPORTANT LIMITS
- A normal PC alone cannot measure arbitrary RF activity worldwide. It needs public spectrum-sensor data, a local SDR, or other authorized receiver feeds.
- "Private" is never inferred merely because a source is unknown. Red requires explicit authorized/private metadata.
- "Unknown" means a real measurement survived current known-source matching; it does not establish origin or intent.
- Atlas-X does not access protected/private communications or decode their contents in this build.
DIAGNOSTICS
Installer log: %TEMP%\Atlas-X-install.log
Server log: %TEMP%\Atlas-X-server.log
UNINSTALL
Run uninstaller.bat.
LOCATED SOURCE RULE (0.9.6)
- A cyan source-fix ring/cross is shown immediately for any measured report with a valid located source coordinate.
- Supported coordinate names include targetLat/targetLon, sourceLat/sourceLon, objectLat/objectLon, locatedLat/locatedLon, locationLat/locationLon, detectedLat/detectedLon, fixLat/fixLon, and geolocatedLat/geolocatedLon.
- Generic lat/lon can also be treated as the source location when isLocated/located/geolocated/sourceLocated is true or positionRole/locationRole is target/source/object/located/fix/geolocated/detection.
- receiverLat/receiverLon remain the receiver coordinates and do not create a source-location marker by themselves.
- Triangulated bearing intersections still create a cyan source-fix ring/cross as an additional location method.
LIVE CONNECTIONS (0.9.6)
- Atlas-X reads current Windows TCP connections and UDP endpoints from the local machine through its localhost backend.
- PRIVATE = remote/local endpoint is in loopback, RFC1918, link-local, or IPv6 local ranges. Display: red dot.
- UNKNOWN = active endpoint is not classified as private by the local address rules. Display: neon-green crosshair.
- PRIVATE and UNKNOWN connection filters are normal editable checkboxes and default on.
- The live list refreshes automatically every 2.5 seconds.
0.9.6 ANOMALY / MAP RULE
- Unresolved effective anomaly >= 0.75 = animated white→yellow→green→blue crosshair.
- The marker is awarded by anomaly state, not by localization confidence.
- If a target/source location is supplied, the special crosshair is placed there immediately.
- If separated receiver bearings triangulate the source, a high-anomaly fused source keeps the same special crosshair at the solved coordinates.
- Ordinary lower-anomaly fused fixes remain cyan.
- Selecting a high-anomaly report or pinpointed high-anomaly fused fix shows captured/decoded source data when the feed supplied it, plus the derived Atlas-X fingerprint.
0.9.6 NOVELTY MATH
- Robust per-feature z-scores use median and MAD over recent comparable background reports.
- Combined robust distance is converted into a 0..1 novelty score.
- Supported signal features include frequency, bandwidth, SNR/power, symbol/PRF/pulse characteristics, Doppler/chirp, entropy/flatness, kurtosis/skewness, autocorrelation, and spectral prominence when supplied.
- Computed novelty can raise the effective anomaly after sufficient background support; it never lowers a feed-supplied anomaly score.