Base-station network portal
We designed and built the public and subscriber-facing portal for a GNSS reference-station network of 54 continuously operating stations: station health, RINEX availability and subscription-gated stream access, with sub-minute alerting and zero unnoticed outages since go-live.
The situation.
A GNSS reference-station operator running 54 continuously operating stations across two climate zones.
ScopePublic and subscriber-facing portal over a CORS network: station health (receiver temperature, supply voltage, lock status), RINEX availability windows, multipath signature panels per station, and subscription-gated stream access with key management.
Operational SLA dashboard for 50+ stations, sub-minute alerting, zero unnoticed outages since go-live.
What made it hard.
Receiver firmware updates silently changed the RTCM message set twice a year: we built a message-set fingerprinter that detects decoder drift before subscribers do.
Peak demand at 06:00 UTC from European rovers colliding with nightly RINEX packing: we staged files to edge storage and rate-limited by subscription tier.
Common questions.
What was the scope?
Public and subscriber-facing portal over a CORS network: station health (receiver temperature, supply voltage, lock status), RINEX availability windows, multipath signature panels per station, and subscription-gated stream access with key management.
Who was the client?
Client names are withheld under confidentiality agreements. References are available on request.
What was the outcome?
Operational SLA dashboard for 50+ stations, sub-minute alerting, zero unnoticed outages since go-live.
Application development
Full-stack web apps, portals, APIs, dashboards.
Explore this capability →This is one of roughly fifty engagements we ship per year. The full record, 2011 to today, lives on the delivery history page.