A February 2004 announcement associated XRF Technologies with a proposed wireless installation in Lancaster, California. The surviving account is evidence of a proposal and its claims. Establishing a working deployment, its performance or its later fate requires records beyond that announcement.
What the surviving account establishes
The February 18, 2004 account described initial internet access and possible later uses including municipal work, voice services and first responders. It attributed ambitious range, throughput, compatibility and security claims to XRF. Those statements describe the proposed system and its promotion; commissioning and measured service results remain unverified in the documentation reviewed here.
As of this October 3, 2026 review, a city acceptance record, a reproducible technical test and equipment-specific documentation have not been located for this proposal. That evidence gap leaves the outcome open. It does not establish either successful deployment or technical failure.
Turn each claim into an evidence question
| Claim in the 2004 account | Evidence needed to evaluate it | Present interpretation |
|---|---|---|
| Lancaster installation | City procurement, installation and acceptance records identifying the equipment and dates | A proposed deployment; operational status unresolved. |
| Range up to 15 miles | Antenna arrangement, frequency, terrain, link budget and measured test results | A claimed reach with insufficient conditions for comparison. |
| More than 500 megabytes per second | Original measurement units, endpoints, payload, direction and test logs | An unverified throughput claim with a consequential unit question. |
| Broad compatibility and strong security | Named interfaces, supported products, protocols and evaluated security properties | General descriptions awaiting equipment-specific evidence. |
The table is an audit plan. A product brochure may resolve an interface question while leaving deployment status unresolved; a city purchase order may establish an order while leaving performance unresolved. Match each new record to the particular claim it can support.
Preserve the difference between bits and bytes
The account used megabytes per second. NIST’s explanation of data units gives eight bits per byte and distinguishes decimal prefixes from binary ones. Using decimal units:
500 MB/s × 8 = 4,000 Mbit/s = 4 Gbit/s.
By contrast, 500 Mbit/s ÷ 8 = 62.5 MB/s.
This calculation translates units; it does not validate either speed. Changing “bytes” to “bits” would alter the claim by a factor of eight. Retain the recorded wording and seek the underlying technical document before deciding whether a transcription error occurred. A comparison expressed only as a multiple of another service also needs that service’s rate and a matching measurement basis.
What would change the historical conclusion
The most useful next record would identify both the city project and the actual equipment: a dated contract, acceptance report or city staff report with model numbers and scope. A subsequent performance report would need enough test conditions to explain the results. Preserve where each document came from and distinguish an approved plan from completed work.
Until such records are available, describe this as the XRF Lancaster proposal. For a documented wireless milestone with a narrower claim, compare Novatel’s reported WiMAX prototype test; for planning repeatable observations, see mobile broadband route testing.