evacuation_history
Past evacuation orders and alerts in B.C. (since 2017)
Historical B.C. evacuation orders and alerts that have ended (All Clear), newest first, from the province's Historical Orders and Alerts layer on DataBC: event type (fire, flood, landslide, other), issuing agency, municipality and regional district, and the dates the alert and order started and the all clear. Filter by year, type, agency, municipality or regional district code. NOT current: for orders and alerts in force now use wildfire_evacuations. Order names are never returned, and event names and counts are withheld for records covering fewer than 10 homes or names that look like an address.
Cost: 3 units of your allowance (see Rate limits).
Parameters
from_year(integer, optional): min 2017, max 2100to_year(integer, optional): min 2017, max 2100type(Fire,Flood,Landslide,Other, optional)agency(string, optional): min length 1, max length 60municipality(string, optional): min length 1, max length 60regional_district(string, optional)limit(integer, optional): min 1, max 50, default20
REST
curl -X POST https://api.bcmcp.ca/v1/tools/evacuation_history \
-H "Authorization: Bearer $BCDATA_KEY" \
-H "Content-Type: application/json" \
-d '{}'MCP
Call the tool evacuation_history with these arguments. Over raw JSON-RPC:
curl -X POST https://api.bcmcp.ca/mcp \
-H "Authorization: Bearer $BCDATA_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"evacuation_history","arguments":{}}}'What comes back
Every answer is the same envelope, over REST and over MCP: available, data, citations, freshness and notes. See Citations and freshness.