-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Case Enforcements as a DataSet object #18
Comments
This will be challenging because it involves two queries: one to associate facility IDs with enforcement action IDs and then another to pull up details of those enforcement actiosn |
We can use a linking table the same way we use EXP_PGM to link the facility IDs (ECHO EXPORTER) with program IDs (SDWA_IDS, RCRA_IDS,NPDES_IDS,AIR_IDS). There are several data sets associated with CASE ENFORCEMENTS. Do we need any others, or can we just start with CASE_ENFORCEMENTS? |
@shansen5 Good question! I think let's just start with CASE ENFORCEMENTS and CASE PENALTIES so that we can build as full a picture as possible of the US EPA enforcement actions that aren't already recorded in the program-specific tables. |
I added a few of the others to my request of Stonybrook. They seemed to me likely to be used. |
We should consider adding some of the tables described here, especially CASE ENFORCEMENTS, as a DataSet object for users to select when looking at program data.
https://echo.epa.gov/tools/data-downloads/icis-fec-download-summary
We had this in before but I think we were interpreting it incorrectly.
My understanding is that these tables sometimes duplicate, but also sometimes adds new information about enforcement actions taken by the US EPA rather than state agencies.
We already have ICIC FEC EPA INSPECTIONS
See some of the discussion here: edgi-govdata-archiving/Environmental_Enforcement_Watch#96 (comment)
The text was updated successfully, but these errors were encountered: