Preface
RulePoint
RulePoint Concepts
- RulePoint Concepts Overview
- Understanding RulePoint Entities
Using RulePoint
RulePoint Objects
- RulePoint Objects Overview
- State of RulePoint Objects
Working with Topics
Working with Connections
Working with Sources
Working with Responders
Working with Responses
Working with Watchlists
Working with Analytics
- Analytics Overview
- Analytic Types
- Creating an Analytic
- Copying an Analytic
- Editing an Analytic
- Deleting an Analytic
- Viewing Related Objects
- Predefined Analytics
  - abs
  - average
  - ceil
  - charat
  - clean
  - compareto
  - concat
  - confidence
  - correlation
  - count
  - current
  - date
  - datedifference
  - endswith
  - even
  - floor
  - getcurrentdate
  - getdatefrommillis
  - getdateinmillis
  - geodistance
  - geoinbound
  - geoinsidearea
  - geointersect
  - geooutbound
  - geooutsidearea
  - geopassthru
  - indexof
  - integer
  - isblank
  - isholiday
  - isnum
  - istext
  - isweekday
  - isweekend
  - large
  - list2vars
  - lower
  - max
  - min
  - mod
  - mode
  - mround
  - odd
  - parse
  - past
  - percentile
  - power
  - proper
  - range
  - regex
  - replace
  - round
  - rounddown
  - roundup
  - sign
  - small
  - startswith
  - stdev
  - stringequals
  - stringindexof
  - stringlastindexof
  - stringlength
  - substring
  - sum
  - trim
  - truncate
  - upper
  - xpath
- Predefined Operators
  - contains
  - equalsSet
  - has
  - in
  - match
  - notMatch
  - search
  - unique
  - group by
  - distinct
  - unmatched
- Using the distinct, group by, and ummatched Filters
DRQL
Working with Rules
Working with Alerts
Setting Access Controls
Troubleshooting RulePoint Issues
Connecting to an Ultra Messaging Application
Creating an Ultra Messaging JMS Source

User Guide

6.1
- 6.2
- 6.1.2

Back Next

geoinsidearea

The geoinsidearea analytic takes latitude-longitude reference points and multiple latitude-longitude points of a polygon, and returns true if the reference point falls inside the polygon. If the reference point falls on the points of the polygon, it returns true.

The criteria for creating a polygon and its coordinates is the same as for the geoinbound() analytic.

Syntax

geoinsidearea(pointLat,pointLong,polyLat1,polyLong1,polyLat2,polyLong2,polyLat3,polyLong3,[polyLat4],[ polyLong4],..)

The following table describes the required and optional arguments:

Argument	Required Optional	Description
pointLat, pointLong	Required	The two geo points that form the point.
polyLat1, polyLong1, polyLat2, polyLong2, polyLat3, polyLong3	Required	The minimum points that form a polygon. The number of latitude arguments must be equal to the number of longitude arguments.
[polyLat4],[polyLong4],...	Optional	The other points that form the polygon.

The following table provides the datatype for the parameters you can pass:

Parameter Input Options	Datatype
Event property	Real number
Watchlist values	Real number

Example

WHEN 1 boat b with geoinsidearea(b.lat, b.long, "100.0","100.0", "100", "-100.0", "-100.0", "-100.0", "100.0","-100.0") as result then response with body= “${result}”

The following table describes the result for the event property value that you pass:

Event Property Value	Description	Result
b.lat=0 b.long=0	Provide latitude-longitude reference points and multiple latitude-longitude points of a polygon to verify the points are within the defined polygon.	true

Rename Saved Search

Table of Contents

User Guide

User Guide

geoinsidearea

geoinsidearea

Syntax