GuidesAPI Reference
Guides
  1. Network Positioning API v1
  2. Guide
  3. How to find a position

Recommendations for Indoor Positioning WiFi and Bluetooth Scanning

Note

HERE Network Positioning API v1 is in maintenance and is not actively developed. Use HERE Network Positioning API v2 to get the latest features and updates. To learn more, see the HERE Network Positioning API v2 Developer Guide.

WiFi

  • The objective of WiFi scanning is to capture all the WiFi APs (Access Point) observable by the device.
  • Limiting the number of WiFi APs in the object sent to server in any way is highly undesirable.
  • Indoor Positioning specifics:
  • Rx level is mandatory
  • About timestamps
    • Including measurement timestamps to the object sent to server is highly recommended.
    • If measurement timestamps are available in the device, we recommend including up to a 10-second tail of measurements to the object sent to server.
    • If measurement timestamps are unavailable in the device, only include the instantaneous measurements (no tail) to the object sent to server.

Bluetooth

  • The objective of Bluetooth scanning is to capture all the Eddystone/iBeacon Bluetooth beacons observable by the device.
  • Limiting the number of beacons in the object sent to server in any way is highly undesirable.
  • Only include Eddystone and/or iBeacon beacons to the object sent to server.
  • Always include one of {MAC Address, EddystoneID, iBeaconID}. Prefer MAC Address.
  • About timestamps
  • Including measurement timestamps to the object sent to server is highly recommended.
  • If measurement timestamps are available in the device, we recommend including up to a 10-second tail of measurements to the object sent to server. In this case, make 500ms scans continuously.
  • If measurement timestamps are unavailable in the device, only include the instantaneous measurements (no tail) to the object sent to server. For an instantaneous measurement make a single 3000ms scan.

Updated last month