Repository navigation
SigIntAtlas
A prepared SigMF pair also shows an explicit Save to SigIntAtlas panel using the
deployment's configured same-origin Atlas API proxy. Nothing is sent until the operator supplies the
local token and presses Save. Upload, server verification, saved recording and optional
analysis are separate visible states; cancellation, retry, offline download and the receiver
remain available. Configure a user token before recording under Settings → SigIntAtlas,
then use Test connection to check the current user and role. Remember on this browser
keeps the token across reloads; uncheck it and save for use only in this tab. Existing saved
tokens remain compatible. The Save panel and transfer recovery use the same credential and
session. Inline Save entry follows the configured persistence choice. Disconnect retains
the token; Forget token clears it locally and attempts server logout. Both actions are
blocked during an active transfer, and neither revokes the issued Atlas token. Browser
storage is origin-local and readable by app scripts, not an encrypted vault. IQ is not persisted by this
upload workflow. CI8 and structured-gap
captures remain valid archives but are not automatically analyzed. Configuration, limits and
the isolated real-stack command are documented in
the BSD-03 workflow.
The proxy must also expose read-only GET /api/v1/me for connection identity/role checks;
see the Apache example (configure the equivalent routes on your own reverse proxy). It also needs the exact
read-only station list and UUID-detail routes for catalog search.
Under receiver Channel settings, expand Find station in SigIntAtlas. Enter text, optionally minimum/maximum frequency in MHz, then press Search stations. Around channel fills a window from the current channel/profile without searching or tuning. The minimum is included and the maximum excluded; a matching station can have other references outside that window. Pages show up to 50 stations; use Previous/Next, or narrow the query after 20 pages. Clear search cancels the read and clears filters/results. Changing filters resets pagination. Search uses the configured token lazily and also works with viewer credentials, independently of recording storage/analysis availability.
Open in SigIntAtlas links to the station's stable ID and selected transmission; Open station list carries compatible text/MHz filters. Atlas may require its own sign-in; links never carry credentials. Choose a transmission before Use in receiver when there are several. FM/WBFM/WFM, AM and NBFM/NFM map to supported analog modes. Unknown/digital formats require an explicit WBFM, AM or NBFM choice. Catalog provisional/verified state is separate from reception evidence and station identity. Receiver use rechecks the current reference, validates the selected source and shows requested versus applied bandwidth. It never connects USB or starts reception. During a capture, preparation, retained-capture conflict, scan, receiver transition or Atlas transfer, receiver selection is blocked; search and links remain available. Replay requires switching to a live source or demo.
After selection, manually Start, record, prepare and Save to SigIntAtlas. The intended station/reference is copied at capture start; later search changes cannot relabel that capture. After byte-verified save, Confirm reception continues the existing human review workflow in Atlas.
For separate development services, set deployment-owned VITE_ATLAS_WEB_BASE in
.env.local to a trusted web origin, e.g. http://127.0.0.1:8000, then restart Vite.
It accepts HTTPS or loopback HTTP with no credentials/path/query/hash. If omitted, links
open https://sigintatlas.com; both production BrowserSDR hostnames always use that target.
This config changes web links only. Put a development HTTPS reverse proxy in front of
Vite and Atlas, forwarding /api/v1/session, /api/v1/me and the bounded station read
routes on the same BrowserSDR origin, using the Apache example with your local upstream.
Configure Atlas's exact trusted Host/Origin and secure session cookies for that front-end
origin. A plain Vite server without these API routes shows a proxy failure. Do not point
browser token requests directly at a different origin or relax Atlas authentication/CSRF.
Station reception now connects Atlas's Receive action to BrowserSDR's proposed tuning settings and returns a saved recording to Atlas's focused confirmation form. Save shows capture origin before submission; native RTL-SDR captures retain RDS observations from only their saved byte range. Timed capture, separate saved-range PI/PS guidance, Record next station, and a retained previous-recording link support repeated reception work. See the reception workflow for provenance, bounds and validation scope.