Evac alert is a demonstration of how to use Azure functions to pull evacuation notices as well as geo code addresses.
The solution is primarily an Azure function app, that contains various functions that support geocoding and determining which addresses are under an evacuation state.
Additionally, there is a simple Blazor Server application that visually shows the current evacuation zones in the province of BC.
There are several HTTP trigger functions in the Azure Function App inside EvacAlert. These typically are used in conjunction with Azure Data Factory.
| Function Name | Purpose |
|---|---|
| GeocodeAddresses | Used for geocoding addresses. Supports csv or json. This function resturns the name of the address sent in, along with the coordinate |
| CurrentEvacuationAreas | Retrieves the current evacuation areas in the province of BC |
| FindPersonsInEvacuationZones | Filters the list of people sent to the function with those that are in an active evacuation zone |
The solution requires a ADLS (HFS enabled storage account) on Azure. This storage account is used for:
- Storing the uploaded non-geocoded addresses and identifiers.
- Storing the geocoded addresses.
- Storing a simple CSV output of those who are currently in an evacuation zone.
The storage account has two containers: one called upload, one called reports.
Data must be uploaded to the path /data/upload/addresses.csv.
The addresses csv file format must have three columns:
| Column | Description |
|---|---|
| Identifier | The identifier of the address. This could be the name of a person. |
| Group | The group for this address, could be used for reporting on. |
| Address | A single string address. Note: this should be in quotes, as there may be commas in the address. |
The deployment works in two stages.
- Geocoding the addresses.
- Checking if the addresses are in any evacuation zone.
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ │ │ │ │ │
│ ADLS │ │ LA │ │ FunctionApp │
│ │ │ │ │ │
└───────┬───────┘ └───────┬───────┘ └───────┬───────┘
│ │ │
│ │ │
├────────────Read Addresses───────────▶│ │
│ │ │
│ ├──────────GeoCode Addresses──────────▶│
│ │ │
│ │ │
│ │ │
│ │◀────────────Read Response────────────┤
│ │ │
│◀──────Write GeoCoded Addresses───────┤ │
│ │ │
│ │ │
│ │ │
│ │ │
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ │ │ │ │ │
│ ADLS │ │ LA │ │ FunctionApp │
│ │ │ │ │ │
└───────┬───────┘ └───────┬───────┘ └───────┬───────┘
│ │ │
│ │ │
│ │ │
│ │ │
├─────────Read GeoCoded Points────────▶│ │
│ │ │
│ │ │
│ ├───────────Check Geo Points──────────▶│
│ │ │
│ │ │
│ │ │
│ │ │
│ │◀──────Points in Evacuation Zones─────┤
│ │ │
│ │ │
│◀────────Write Evacuation Zones───────┤ │
│ │ │
│ │ │
│ │ │
│ │ │
▼ ▼ ▼
The deployment of the solution is handled mostly via a BICEP template in this repo.
az login
#optionally select the subscription
#az account set --subscription <name>
az deployment group create --template-file ./deployment.bicep --resource-group '<resoucegroupname>' --parameters companyident=<companyident> environment=test --confirm-with-what-ifThere are a few things we need to do post bicep deploment.
- Set the AzureMapsApiKey app setting inside the function app of the azure maps account. Note: this should be saved in a keyvault in production.
- Create two filesystems on the ADLS container: data, and reports.