Geospatial Asset Association (GAA) is a feature that allows customers to record post alarm footage from nearby cameras based on a configurable radius or geofence. This allows them to have camera recordings without having to manually link each alarm point to each camera one by one.
NOTE: GAA has no UI visualization when running, this feature has no relation to the Camera Spotlight feature within the Map component on Site Monitor.
In addition to your standard core components, GAA requires Alarm Responder and V1 Data Service to function correctly.
Update the SVAlarmResponder.exe.config file, setting the appropriate values for the following settings:
- GAAUserID - This needs to be the id of a user within SureView that has access to V1 and can see all areas.
- DataServiceEndpoint - Location of the V1 Data Service. If local, the value will be http://localhost/Data/SVDataSvc.svc. If remote, then "localhost" will likely be replaced with the appropriate server name.
Please restart Alarm Responder after setting these values.
Within the Systems Settings page, on the system level, enable the EnableGAAResponseActions pref. This will allow Alarm Responder to process GAA requests. Please restart Alarm Responder after changing this value.
Configuring GAA Rules
There are 2 ways to configure GAA rules, by Response (Figure 1.1), or by ServerTypeEvent (Figure 1.2). If a rule is setup on both a Response and a ServerTypeEvent then the Response rule will take precedence.
Figure 1.1 - Responses
The settings available in both configuration options are as follows:
Match Radius - Match cameras within x meters of the alarm point. This value should be a whole number, greater than 0.
Match Geofence - Match cameras within the same geofence of the alarm point. Note: Geofences are setup and managed through the Map Setup.
There is currently no global setting for Match Radius or Match Geofence for GAA.
Figure 1.2 - ServerTypeEvents
Alarm Clips are not being recorded through GAA
If clips aren't being recorded here are a few suggestions of why that may be?
- Please double check you have rules set up (using the methods mentioned above) and that the alarms you are triggering are hitting those rules. Check the alarm responder logs, this will tell you if GAA is enabled and if any cameras are being found. If you find some alarms work with GAA and some don't you may be missing the GAA rule configuration on the alarms that aren't working
- Take care when testing as certain situations may not trigger GAA. For example, if you have rules set on ServerTypeEvents, and you trigger a test alarm on a default Alarm (Response) then it will not trigger GAA as there is no event type being triggered.
- Ensure your Alarm Responder configuration is correct, taking care to set the GAAUserID and DataServiceEndpoint mentioned above. GAA will not function correctly if either of these values are incorrect.