Understanding Maps in Zoho IoT: A Comprehensive Guide

Understanding Maps


The Maps feature in Zoho IoT assists with static placement, real-time tracking, geofence boundaries setting, location history tracking of any managed entity such as 
devices, assets, and locations, providing clear visibility into their current placement and movements. By knowing the exact placement, you can plan new allotments, and streamline logistics efficiently. By configuring geofences you can track managed entities more attentively by associating the geofences to alarm rules, where you can set options to raise an alarm whenever an vehicle enters or exists a geofence. 

Any placement of a managed entity on the map is determined using the geolocation property, which includes the latitude and longitude values of a location. This geolocation property is configured for all devices and assets that must be placed on a map.
 
Zoho IoT uses Zoho Maps by default, to use Google Maps, you need to integrate the Google Maps API.

Understanding Geolocations

For example, consider the scenario where you have Zylker Diesel Generator Service Company with multiple branches in Bangalore(city) and Chennai(city) across India(county) with multiple Diesel Generators (DGs) and a gateway distributed in the two cities. Now, Zylker wants to create a map view "Bangalore - All Assets" and "Chennai - All Assets" to view all the assets and devices placed in Bangalore and Chennai, respectively.
 
To achieve this, first ensure that all the assets in Bangalore and Chennai that need to be displayed in the
map are updated with the geolocation property. This latitude and longitude values of the geolocation must point to the exact location on the map.

Any asset without geolocation will not be displayed on the map.
 
 
Image: Bangalore -All Assets and Chennai-All Assets mapping




Image: All Diesel Generators map view
 

Map Types
   

Static Entities  Map 

The Static Entities map helps identify the fixed location of a managed entity, such as a building, or any stationary asset. It is useful for monitoring the status of entities that do not move, providing a clear spatial context for device placement and easier management of static infrastructure. 

To place static components managed entities on a map, you need to configure the geolocation property. This property value places the managed entity in the configured location. This can be set in the Details page of the managed entity. In the  above scenario DG 1, DG 2, GW 1, and so on are static components of a map.

Refer to the Working with Maps document for a step by step procedure to configure geolocation.
 

 
Image: Geolocation property in a location

 
Live Tracking Map 

Live Tracking enables real-time monitoring of devices, allowing you to view their current location and movement on the map as it happens. This is especially useful for tracking vehicles, assets in transit, or mobile personnel, ensuring timely updates, route accuracy, and improved operational visibility. 

For live tracking, you need to configure the following in addition to configuring the geolocation.
  1. Create a Location datapoint with GPS property enabled.
  2. Enable the Live Tracking feature during map creation.
 Geolocation will place the managed entity in a specific location, and the properties location datapoint, GPS property, and live tracking helps in defining its movement.



Image: Data Type Location and GPS Type settings for live tracking

In the above scenario, VAN 1, which is associated with Bangalore, is the moving asset. To live-track VAN 1 on the map, you must create a location datapoint with the  parameter that determines the movement of VAN 1.
 
The movement of VAN 1 will be updated in the map whenever the Location datapoint value is received for VAN 1.
 



Image: Live Tracking enabling and Map Marker icon setting in the map
 
InfoRefer to the Working with Maps and Working with Datapoints for a step-by-step procedure to create a Location type datapoint, and to create a GPS enabled map.

Location History Map 

Location History allows you to track the path taken by a vehicle or any moving managed entity over a selected time period. This feature is valuable for analyzing past routes, verifying trip completion, identifying delays or deviations, and improving route planning and accountability. 

For tracing the location history, you need to configure the following in addition to configuring the geolocation.
  1. Create a Location datapoint with GPS property enabled.
  2. Ensure Default Location Preference is set with Location Datapoint selected for the monitored managed entity.
  3. Enable the Location History feature during map creation.



    Geofences Map 

    With the new Geofence feature in Maps, you can create virtual boundaries around specific locations for your managed entities. Set up alarm rules to automatically trigger alerts whenever vehicles or assets enter or leave these designated areas, enabling more intelligent, location-aware monitoring and control.

    For configuring geofence, you need to configure the following in addition to configuring the geolocation.
    1. Create a geofence.
    2. Create map with Geofence feature enabled, and associate it to the geofence.


    Image 1: Create Geofence

    Image 2: Associate Geofence by editing map

    Refer to the Working with Maps and Working with Datapoints for a step-by-step procedure to create a Location type datapoint, and to create a GPS enabled map.

    Availability

    All Map operations require necessary permissions. Refer to Users and Profiles document for more details.

    Check Feature Availability and Limits


    See Also
    Working with Maps
    Maps - FAQ
    Working with Geofences