bc_fire_incidents_history
B.C. historical wildfire incident locations (BC Wildfire Service)
Look up historical fire incidents from BC Wildfire Service's Fire Incident Locations - Historical layer on DataBC, read live: by year or range of years, cause, incident type, name or place description, fire number, minimum size, or distance from a point (nearest first). Returns fire number, year, name, place description, type, cause, response, ignition and out dates, size in hectares, fire centre and location. This layer lists every incident BC Wildfire recorded, so most rows are small: filter fire_type 'fire' for wildfires (the others are nuisance_fire, smoke_chase, duplicate, unknown, field_activity, field_activity_other, prescribed_fire, training, agency_assist, fuels_management, other_emergency, flood, landslide). A fire number can be given alone or as a label such as 2021-C10784. Not current-season fires (use wildfire_status) and no perimeters (use bc_fire_perimeters_history).
Cost: 3 units of your allowance (see Rate limits).
Parameters
year(integer, optional): min 1900, max 2100year_from(integer, optional): min 1900, max 2100year_to(integer, optional): min 1900, max 2100cause(lightning,person,unknown, optional)fire_type(fire,nuisance_fire,smoke_chase,duplicate,unknown,field_activity,field_activity_other,prescribed_fire,training,agency_assist,fuels_management,other_emergency,flood,landslide, optional)name(string, optional): min length 1, max length 60min_hectares(number, optional): min 0, max 10000000fire_number(string, optional): min length 1, max length 60lat(number, optional): min 47.5, max 61lon(number, optional): min -140, max -113radius_km(number, optional): min 0.5, max 200limit(integer, optional): min 1, max 50, default20
REST
curl -X POST https://api.bcmcp.ca/v1/tools/bc_fire_incidents_history \
-H "Authorization: Bearer $BCDATA_KEY" \
-H "Content-Type: application/json" \
-d '{}'MCP
Call the tool bc_fire_incidents_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":"bc_fire_incidents_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.