Importing EPA Data
Used for importing EPA notification data. Two data providers are supported: EPA SEP NOTIFIED and EPA SEP SCRAPED.
CSV Format
The following headers must be present in the CSV file, even though some of them can be blank:
| Header | Type | Blank | Help |
|---|---|---|---|
| Notification report id | String | NO | Unique id given by EPA for each notification |
| Owner | String | NO | Name of the company, must exist in our db. This field will be ignored for EPA SEP SCRAPED |
| Longitude nad83 | Number | NO | Longitude in NAD83 coord system |
| Latitude nad83 | Number | NO | Latitude in NAD83 coord system |
| Detection date | Date | NO | ISO format |
| Notification date | Date | NO | ISO format |
| Detected rate g_hr | Decimal | NO | g/hr |
| Detected rate uncertainty g_hr | Decimal | NO | g/hr |
| Notifier name | String | YES | |
| Provider name | String | YES | |
| EPA identified site | String | NO | |
| Wind speed | Decimal | YES | m/s |
| Wind direction | Decimal | YES | degrees |
| Temperature | Decimal | YES | F (stored in °C) |
| Humidity | Decimal | YES | g/kg |
| Due Date | Date | YES | ISO format |
Notes:
- Owner column is required, but only for EPA SEP NOTIFIED data provider. For EPA SEP SCRAPED, owner column will be ignored. If owner is present, any company found in the file must exist in the platform, or the import script will fail.
- Any additional fields will be stored as extra data object.
Script Arguments
EPA script requires no additional arguments beyond the common ones (environment, api_key, data_path).
Additional argument:
--source- Source type:notifiedorscraped
Example
Example of calling the EPA script on dev environment:
bash
python -m importers.emissions.epa --environment dev --api_key {API_KEY_VALUE} --data_path {PATH_TO_FOLDER} --source notifiedOr for scraped data:
bash
python -m importers.emissions.epa --environment dev --api_key {API_KEY_VALUE} --data_path {PATH_TO_FOLDER} --source scraped