n

number of latitude and longitude pairs. For example, it can be polyLat1, polyLong1, polyLat2, polyLong2, ..., ..., polyLatN, polyLongN . The number of latitude arguments must be equal to the number of longitude arguments. Specify the values directly in the analytic or it can be accessed as an event property.

Access list of latitudes and a list of longitudes from watchlists whose type is list. Both latitude and longitudes coordinate lists must be the same size, and each coordinate in either list must correspond to the coordinate in the same position in the other list. For example, geoinbound ( l.lat1,l.long1,l.lat2,l.long2, Watchlist:lats, Watchlist:longs ). In this case, Watchlist:lats and Watchlist:longs are watchlists of type list.

Access a single two-dimensional list of comma-separated latitudes and longitudes as arguments from watchlists whose type is text . For example, geoinbound ( l.lat1,l.long1,l.lat2,l.long2, Watchlist:polgygon ). In this case, Watchlist:polgygon is of type text.

The polygon must have at least three sides.

Polygons are always two-dimensional, horizontal shapes.

All polygons must be closed. If you do not close the polygon in the analytic, the analytic automatically closes the polygon by connecting the last specified point to the first point. To close the polygon in the analytic, set the arguments for the last polygon point to be the same as those of the first polygon point.

Calculate all lines between polygon points as straight.

Polygon lines can be crossed to create multiple inside areas.

The order of the arguments in the analytic define the order in which the points of the polygon connect. For example, if you define the points as A, D, C, B, the polygon is constructed from point A to D, D to C, and C to B.

Coordinate literal arguments must be strings placed within quotation marks.