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.2
- 6.2
- 6.1

Back Next

geointersect

The geointersect analytic validates whether two geo polygons intersect.

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

Syntax

geointersect(count of coordinates in 1st polygon,count of coordinates of 2nd polygon,1st polygon coordinates,2nd polygon coordinates)

The following table describes the required and optional arguments:

Argument	Required Optional	Description
count of coordinates in 1st polygon	Required	The count of all the geo points of the first polygon. If the polygon points are accessed from a watchlist, the value for the count of the coordinates is 0.
count of coordinates in 2nd polygon	Required	The count of all the geo points of the second polygon. If the polygon points are accessed from a watchlist, the value for the count of the coordinates is 0.
1st polygon coordinates	Required	All the geo points of the first polygon.
2nd polygon coordinates	Required	All the geo points of the second 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 polygon p1 ,1 polygon p2  with geointersect(p1.count,p2.count,p1.x1,p1.y1,p1.x2,p1.y2,p1.x3,p1.y3, p2.x1,p2.y1,p2.x2,p2.y2,p2.x3,p2.y3) 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
p1.count : 6 p2.count: 6 p1.x1=50,p1.y1=50,p1.x2=0,p1.y2=0,p1.x3=100,p1.y3=0 p2.x1=20,p2.y1=20,p2.x2=0,p2.y2=0,p2.x3=50,p2.y3=0	Verifies whether the two polygons are intersecting.	true

Rename Saved Search

Table of Contents

User Guide

User Guide

geointersect

geointersect

Syntax