# how-to/vps2/vps2_config_partial

Source: https://www.nianticspatial.com/docs/nsdk/how-to/vps2/vps2_config_partial/

#### Configuration Fields

| Field | Default | What it controls |
|---|---:|---|
| **Universal Localization Enabled** | Disabled | When active, the VPS2 session sends camera imagery and the device's GPS position to the cloud for geopositioning, without needing a VPS map. This can improve geoposition accuracy beyond local sensor fusion but requires a network connection. If disabled, the device's geoposition away from VPS maps comes from local sensor fusion alone, which always runs. Either way, the VPS2 tracking state reaches at most `coarse` until it localizes to a VPS map. |
| **Universal Localization Requests per Second** | `1` | Frequency of network requests sent for universal localization. |
| **VPS Map Localization Enabled** | Enabled | When active, the VPS2 session sends AR sensor data and camera imagery to the server to localize against VPS maps. This only allows VPS map localization: no requests are sent until you call `localize` (Unity: `TryLocalize`) for a Site or a nearby coordinate. |
| **Initial Requests per Second** | `1.0` | Server request frequency prior to the first successful VPS map localization. For example, `1.0` is one request per second. |
| **Continuous Requests per Second** | `0.2` | Server request frequency after the initial VPS map localization. For example, `0.2` is one request every five seconds. |
| **Temporal Fusion Enabled** | Enabled | Fuses successive VPS map localizations against the same map into one estimate, instead of using only the newest. Localizations that agree raise the asset's tracking confidence and steady its pose, at the cost of reacting more slowly to a genuine pose change. Unrelated to local sensor fusion of GPS and compass. |
| **Geolocation Smoothing Enabled** | Enabled | Enables interpolation between localization updates. This minimizes "snapping" or visual jumps during abrupt GPS or compass recalibrations, for a more stable AR experience. |
| **Blur Detection Enabled** | Disabled | Enables an advisory image blur check on the frames VPS2 sends for VPS map localization. A frame whose sharpness score falls below the threshold produces a `FrameFlagged` localization request record with error `ImageTooBlurry`, but is still sent for localization, never rejected. Use the signal to coach the user, for example "hold the device steady". See [Prompt users through blurry frames](https://www.nianticspatial.com/docs/nsdk/how-to/vps2/guide_users_during_localization/#prompt-users-through-blurry-frames). |
| **Min Sharpness Score** | `0` | Sharpness threshold below which a frame is flagged as too blurry. The default of `0` flags nothing. Higher scores mean sharper images. There is no universal "sharp" value; `1000` is a good starting point and is the value the VPS2 samples use. |

Universal and VPS map localization are configured independently. VPS map localization is enabled by default; universal localization is disabled by default, so turn it on explicitly if you want cloud geopositioning. Local sensor fusion is not configurable and runs in both cases.