CONFIG_NRF_CLOUD_PGPS_TRANSPORT_NONE

No transport

Type: bool

Help

Enabling this option will make the nRF Cloud P-GPS library not request
data from nRF Cloud when its APIs are called. This will instead let
it be up to the user to request, receive and process P-GPS data.

Direct dependencies

(Includes any dependencies from ifs and menus.)

Kconfig definition

At <nRF>/subsys/net/lib/nrf_cloud/Kconfig.nrf_cloud_pgps:74

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:92 → <nRF>/subsys/Kconfig:20 → <nRF>/subsys/net/Kconfig:8 → <nRF>/subsys/net/lib/Kconfig:29 → <nRF>/subsys/net/lib/nrf_cloud/Kconfig:24

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Networking → Application protocols → Enable nRF Cloud Predicted GPS (P-GPS) → nRF Cloud P-GPS transport

config NRF_CLOUD_PGPS_TRANSPORT_NONE
    bool "No transport"
    depends on <choice NRF_CLOUD_PGPS_TRANSPORT>
    help
      Enabling this option will make the nRF Cloud P-GPS library not request
      data from nRF Cloud when its APIs are called. This will instead let
      it be up to the user to request, receive and process P-GPS data.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)