1. Overview

1. Overview

Setup workflow

A typical Indoor Location setup has 6 steps:

  • Site creation
  • Map import
  • Navigation walkways creation
  • Beacon deployment
  • Calibration and Positioning Database (PDB) generation
  • PDB publication (making it avalable for mobile SDK consumption)

Resources and their relationships

You will be interacting with the following resources: userssitesdeployment sessionsbuildingsfloorsgraphsbeaconsAPI keysPDB publications.

Resource structure
userhas many sites
sitehas many deployment sessions
deployment sessionhas many buildings
buildinghas many floors
deployment sessionhas one graph
sitehas many beacons
sitehas many API keys
API key of a sitehas many PDB publications

Note: A deployment session represents a version of the building’s maps and navigation graph

    • Related Articles

    • Overview

      Features Indoor positioning, using WiFI/BLE/GPS/MEMS sensors Beacon proximity detection, using BLE sensor Geofencing notification, using Indoor Positioning and Beacon proximity detection Geofencing-based analytics, using Geofencing notification ...
    • Overview

      You can find the API reference here. Older versions: API V1
    • Overview

      NAO Cloud provides APIs for 3rd party software to get information in real time.There are 2 main APIs, Location API and Monitoring API. Each API corresponds to a MQTT topic that a software can subscribe to receive information. The Location API returns ...
    • Overview

      We supply a .zip file with the X509 certificate for authentication, alongside a sample Python script (referenced below) that illustrates how to connect to the API and obtain information. Please modify it as necessary (such as changing the certificate ...
    • Restart the location service

      Overview NAOLocationHandle class provides the restart method that stops and stars the location service and therefore re-initializes the environment and variables are being used. However, we strongly recommend that you avoid calling this method ...