Landmarks (also known as geofences) determine virtual boundaries. Within the portal, you can use landmarks to trigger alerts, refine reports, filter maps and dashlets, and more. They also make location labels more intuitive on maps and reports. For example, rather than seeing a long, physical address each time a vehicle returns to your company parking lot, you might instead label that landmark as “Headquarters.”
The boundary that you set up for a landmark can exist as a circle or a polygon.
Circle – The default shape for a landmark boundary is a circle. The default radius is determined by your current zoom level. Circle landmarks are typically sufficient for most tasks (i.e., report labels, map filters, turn-by-turn directions, and so on).
Polygon – Polygons allow you to define a more precise boundary by tracing an outline around a specific area (up to 256* vertices). Polygon landmarks are more often used when the exclusion or inclusion of specific perimeters is important, such as when sending alerts when a vehicle enters or exits a specific location.
*Although there is no limit to the number of vertices on a polygon, there is a limit to the amount of space we have in the database to store them. (The smaller, the better.) If a polygon is uploaded with a polygon-string longer than we can store in the database, the system simplifies the points and compress it down to fit. For example, if the lat-long is specified to 11-12 points of precision, the system shortens that down to 7 points or 5 points of precision, so the total polygon-string is shorter. Also, longer polygon strings mean more operations in the code to check polygon boundaries. It is always advisable for polygons be simple with long straight lines wherever possible. With most vehicles tracking between 30-seconds to 2-minutes, there is almost never a reason to have very detailed polygons.