Skip to content
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

[Data Source Request]: Unregulated Contaminant Monitoring Rule 3 (2013-2015) #15

Open
kzollove opened this issue Jul 20, 2023 · 2 comments

Comments

@kzollove
Copy link
Collaborator

Organization

EPA

Organization Subset

EPA UCMR

Data Source Name

ucmr-3-occurrence-data

Version

No response

Geometry Type

No response

Download Method

direct download

Download file type

txt

Download File Name

UCMR3_All.txt

Download URL

https://www.epa.gov/sites/default/files/2017-02/ucmr-3-occurrence-data.zip

Documentation URL

https://www.epa.gov/sites/default/files/2017-02/documents/ucmr3-data-summary-january-2017.pdf

@kzollove
Copy link
Collaborator Author

This is an interesting case.

In the zip file that is downloaded, there is the main data file (listed above), as well as a file with zipcodes related to site ids UCMR3_ZipCodes.txt

These files will need to be merged. Will attr_spec be up to this challenge? I don't think so...

This either necessitates another *_spec (etl_spec) that handles this specific situation, or geom_spec should be repurposed as data_spec (the spec that handles data_sources). Within a data_spec there could be {geom: "..."} that functions the same way as the geom_spec

@kzollove kzollove changed the title [Data Source Request]: [Data Source Request]: Unregulated Contaminant Monitoring Rule 3 (2013-2015) Jul 20, 2023
@tibbben
Copy link
Collaborator

tibbben commented Jul 20, 2023

yep, the SVI data is similar in some ways (one file name for zip file, another for shape file inside the zip. Also the data I am using for local temperature and NDVI in Miami-Dade has several files(data layers) in one zip file. I think we can handle this, but it will require a few more custom fields/etl functions. With that said, if we think carefully, we should be abole to handle any number of similar cases ... we can chat if you want.

@kzollove kzollove transferred this issue from OHDSI/GIS Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 💡 Idea
Development

No branches or pull requests

2 participants