Skip to content

ETL-Active911

Bring Active911 Alerts into the TAK System

Setup🔗

  1. Request a Username & Password to the Active911 with a minimum of Read Only permission for Alerts
  2. Manually Log into the account and grab the AgencyID from the URL after you log in
  3. Provide the above information to the ETL Active911 Integration

CAD Notes🔗

The free text details of an alert are formatted differently by every CAD vendor. Known formats are parsed into individual notes which are rendered as a Markdown table in the remarks and included as metadata.narrative.

Each agency has a Parser option:

Parser Details
auto Default - detect the format, falling back to raw
raw Leave the details as is
spillman Spillman/Flex - HH mm ss MM DD YYYY : text notes with a Dispatch: trailer
dated-dash A single leading date followed by HH:mm:ss user - text notes with a TIME: trailer

To support a new format add a parser to lib/parsers/, register it in lib/parsers/index.ts and add a scrubbed sample of the details to test/parsers.test.ts - CAD notes routinely contain names & medical information.

Development🔗

Development Information ## Configuration Setting up an Active911 ETL will require the following: - An Active911 User/Password that can login to the [online portal](https://interface.active911.com/interface/index.php) - The account should be created specifically for TAK and only 1 account should be used per layer as only 1 login can be active at a time - The account must have the permissions to view Alerts to be able to export the active alerts as a CSV ## Development DFPC provided Lambda ETLs are currently all written in [NodeJS](https://nodejs.org/en) through the use of a AWS Lambda optimized Docker container. Documentation for the Dockerfile can be found in the [AWS Help Center](https://docs.aws.amazon.com/lambda/latest/dg/images-create.html) 
npm install
Add a .env file in the root directory that gives the ETL script the necessary variables to communicate with a local ETL server. When the ETL is deployed the `ETL_API` and `ETL_LAYER` variables will be provided by the Lambda Environment 
{
    "ETL_API": "http://localhost:5001",
    "ETL_LAYER": "19"
}
To run the task, ensure the local [CloudTAK](https://github.com/dfpc-coe/CloudTAK/) server is running and then run with typescript runtime or build to JS and run natively with node 
ts-node task.ts

npm run build
cp .env dist/
node dist/task.js
### Deployment Deployment into the CloudTAK environment for configuration is done via automatic releases to the DFPC AWS environment. Github actions will build and push docker releases on every version tag which can then be automatically configured via the CloudTAK API. Non-DFPC users will need to setup their own docker => ECS build system via something like Github Actions or AWS Codebuild.

Info

This page is generated daily from the README of dfpc-coe/etl-active911 (last fetched 2026-10-08). Changes should be made in that repository.