firecares / data

Keeps track of sources and issues related to data in FireCARES.

Data

Keeps track of sources and issues related to data in FireCARES.

• NFIRS: National Fire Incident Reporting System
• USFA: US Fire Administration

see terms for additional information regarding terminology used in FireCARES

IPython/Jupyter notebook setup

Database connections

firecares/nfirs/parcels should be connections defined in your .pg_service.conf, pointed at the respective databases.

Docker

1. docker-compose up

Python

We'd recommend creating a virtualenv to contain your python libraries specific to this project.

Install the necessary python dependencies via:

pip install -r requirements.txt

Next, run ipython notebook to start a notebook session, from here you'll be able to navigate to the notebook you'd like to open via your browser.

data's Issues

Harvest Arlington hydrants.

From here: http://gis.arlingtonva.us/arlgis/rest/services/public_fs/Public_FS_Fire/FeatureServer/0.

Load 2018 parcels

Research: Station placement score

Add 2013 data to the NFIRS database.

• Append the 2013 incident data the the NFIRS database with data from 2002-2012.
• Update the building fires table using this: https://github.com/FireCARES/data/blob/master/sources/nfirs/scripts/building_fires.sql.
• Upload PostGRES dump of the entire NFIRS database to S3.

Add stateco_fips code for harvested datasets.

Once this is complete: FireCARES/harvester#13 add the stateco_fips to the documents already harvested.