What Device Profiles are

A Device Profile is a configuration you define once and assign to one device or an entire fleet. When a profile is active, our server delivers corrections according to that profile. That means the rate, the signals, the station selection logic, and the datum are all customized to your spec. No client-side parsing required. No reconnection needed. Changes apply in real time across every connected device on that profile.

We shipped the Device Profiles UI at app.pointonenav.com. If you’re already using the API, this capability has been available via GraphQL for some time, the UI makes it accessible without writing a single line of code.

What you can configure

Correction rate

Stream corrections at 1Hz for high-precision active operation, or drop to once every 10 or 30 seconds for a docked or idle device. One customer reduced their corrections data cost by roughly 80% using rate throttling combined with signal filtering — without any measurable impact on the positioning accuracy they needed for their application.

Signal filtering

If your receiver is dual-band, there’s no reason to receive L2 corrections it can’t use. Signal filtering lets you define exactly which constellations and frequencies your device gets, stripping everything else before it ever leaves our servers. This means smaller payloads, less processing, and lower data cost.

Required signals

The flip side of filtering: if your application depends on a specific signal like Galileo E6, for example, you can require it. Our network will automatically associate your device with a station that carries that signal, even if a closer station doesn’t. You get the signal you need without having to hardcode a station ID or manage that logic yourself.

Maximum baseline

For surveying workflows with contractual accuracy requirements, you can set a hard distance limit. If a device moves beyond that threshold, corrections stop. This is enforced server-side, which means it applies regardless of what the client does.

Auto Virtual RTK

When a device moves outside the range where single-baseline corrections are reliable, it can now automatically transition to our Virtual RTK network. You set the threshold; the switch happens without any intervention, mount point change, or client reconnection. The device goes from centimeter-grade single-baseline corrections to decimeter-grade Virtual RTK coverage, continuously, wherever it is.

Local datum

For surveyors working in the United States and other regions with local datum requirements, you can configure a profile to deliver corrections in the appropriate local datum (NAD83, for example) rather than ITRF 2014. This used to require separate mount points. Now it’s a profile option.

Profiles are composable

Each of these options can be combined in a single profile. A robot operating profile might include 1Hz corrections, L1/L5 only, and auto Virtual RTK enabled. A docked mode profile for the same robot might throttle to once every 30 seconds and drop to GPS-only. Switching between them takes one API call or a click in the UI  and the change applies immediately to every device on that profile.

See it in action

We ran a live webinar to walk through every Device Profile feature with a real-time demo, terminal output and all. If you want to see exactly how the correction stream changes as profiles are applied and switched, the recording is worth watching. Watch the webinar.