Integrating Monitored & Sub-Areas

What are Areas of Interest (AOIs)?

Users are able to define areas which they wish to monitor (Area of Interest, “AOI”) through the interface.

An area is defined by a name, geographic extent and at least one notification delivery method.
The area is specified as a polygon that can be drawn on the main map, or be self-imported and updated by users within the platform.

Users belonging to the same organization can share and use the same monitoring areas.

We differentiate AOIs between: Monitored Areas and Sub-Areas.

Monitored Areas

Monitored Areas, as the name states, are the main areas where you monitor fire activity.
The notifications you receive per e-mail are generated from a specific Monitored Area.

Sub-Areas

Sub-areas are specific user properties (like plantations or natural reserves) within the Monitored Areas.
They are part of email notifications for a monitored area and are shown also in OroraTech’s Incident overview. 

Incident Overview

Email Notification

---

Upload Process 

There are two preferred options for uploading AOIs to WFS. Customers can send:

1. Monitored area(s) including subarea values 

• EVERY single monitored area must be uploaded separately if they need to be buffered by OroraTech. In this case only one (1) file per monitored area. 
• OroraTech can upload up to 5 separate monitored areas. 
• If monitored areas are spatially too close together or intersecting after the buffering (left image), please merge them into one file (right image).
   

2. If the Monitored Area(s) don’t require neither buffer nor subareas, they can be sent in one file. 

• We recommend having no more than 10 Monitored Areas
• In case of already existing Monitored areas, please decide if new areas should complement existing areas or replace them.

---

Data Format

• Possible file formats: Geojson(.geojson) and Shapefile( .shp, .dbf, .prj, .shx)
• Several sub-areas can be included as a row in the file
• Unified coordinate system for all files (e.g. EPSG 4326, or local coordinate system)
• Attribute table with id column or name column, no null values!
• Other values/columns for subarea properties (region name, area, land cover class)
• File naming and attributes without special characters like mutated vowel (ê, ã, é, ñ, ö)
• File naming and folders without spaces, instead use underscore
• File size per Monitored Area can not exceed 100 megabyte
• Features need to be valid polygons and not null (check validity!)

• Have a maximum number of subareas per monitored area no larger than 2000. If
  more subareas are needed, additional costs might be incurred due to increased
  operational effort.

---

Structure of the Monitored Area

Please fill out this Template for answering the following questions in the first sheet "Fill out Monitored Area": 

•  Buffer for each MA in kilometers
• Which Monitored Areas are shared throughout the organization?
• Are they new monitored areas substituting the old areas or are these additional areas?

---

User structure 

Please fill out the second sheet of the template "User selection and notifications"

• Please provide a list of each user who should get access to the platform or already has access (including name, Email, and phone number for notifications)
• If number is provided, shall notifications be sent via SMS or WhatsApp?
• Specify which user should see/control what zone
• Which user/s should get Admin rights? (remove/edit other users)

After filling out the template, please send it to your responsible Customer Success contact.

---

Notifications

Different notifications settings are available for Email, WhatsApp and SMS. 

Geostationary (GEO) and Low Earth Orbit Satellite detections (LEO): 

• Option 1 Default for integration: Only GEO detections until validated by LEO detections, then GEO notifications turn off 
• Option 2: Only LEO detection notifications 

We recommend using the default option 1. If you still wish to have option 2, please indicate in the attached spreadsheet.