locations can be computed every month. Paid plan quotas range from the hundreds of thousands to many
millions. See the link
https://www.loracloud.com/portal/geolocation/subscription_management
for further
information on pricing plans.
Getting Localization Results
To utilize the LoRa Cloud™ Geolocation API, the LR1110 Tracker will provide scan information for LoRa®
signals, Wi-Fi scan or GNSS measurements. The LoRa® signals and Wi-Fi scan will be passed through the
provided gateway, to the LNS and then onto the cloud systems which will compute location and display
them on a map (discussed later).
Getting Almanac Data for GNSS Aiding
GNSS operates by utilizing ranging measurements from a satellite to a receiver (in this case the LR1110
Tracker device). The acquisition of the signals can be improved by providing information about the GNSS
satellites and the currently local conditions. The LoRa Cloud™ Device & Application Service (DAS) allows for
timing information to be provided to the LR1110 Tracker through the clock synchronization protocol.
Additionally, there are two supported levels of almanac aiding to provide GNSS satellite predictions. The
two almanacs are the “efficient” (i.e., compact) almanac as well as the full almanac. The efficient approach
is optimized for lower communication bandwidth. Over time, the true satellite positions diverge from the
fixed Almanac parameters, which requires them to be updated. DAS is designed to allow for those updates
on a regular basis.
Creating your LoRa Cloud™ Geolocation Application Token
The Geolocation Application Token is provided at:
https://www.loracloud.com/portal/geolocation/token_management
. This will be needed for the
provisioning on the Tago.io account interface.
