mirror of
https://github.com/DOI-DO/j40-cejst-2.git
synced 2025-02-23 10:04:18 -08:00
* Add spatial join method (#1871) Since we'll need to figure out the tracts for a large number of points in future tickets, add a utility to handle grabbing the tract geometries and adding tract data to a point dataset. * Add FUDS, also jupyter lab (#1871) * Add YAML configs for FUDS (#1871) * Allow input geoid to be optional (#1871) * Add FUDS ETL, tests, test-datae noteobook (#1871) This adds the ETL class for Formerly Used Defense Sites (FUDS). This is different from most other ETLs since these FUDS are not provided by tract, but instead by geographic point, so we need to assign FUDS to tracts and then do calculations from there. * Floats -> Ints, as I intended (#1871) * Floats -> Ints, as I intended (#1871) * Formatting fixes (#1871) * Add test false positive GEOIDs (#1871) * Add gdal binaries (#1871) * Refactor pandas code to be more idiomatic (#1871) Per Emma, the more pandas-y way of doing my counts is using np.where to add the values i need, then groupby and size. It is definitely more compact, and also I think more correct! * Update configs per Emma suggestions (#1871) * Type fixed! (#1871) * Remove spurious import from vscode (#1871) * Snapshot update after changing col name (#1871) * Move up GDAL (#1871) * Adjust geojson strategy (#1871) * Try running census separately first (#1871) * Fix import order (#1871) * Cleanup cache strategy (#1871) * Download census data from S3 instead of re-calculating (#1871) * Clarify pandas code per Emma (#1871) |
||
---|---|---|
.. | ||
closed_be_pr.yml | ||
closed_fe_pr.yml | ||
codeql-analysis.yml | ||
combine-tilefy.yml | ||
compile_mermaid.yml | ||
data-checks.yml | ||
deploy_be_staging.yml | ||
deploy_fe_main.yml | ||
deploy_fe_staging.yml | ||
e2e.yml | ||
generate-census.yml | ||
generate-score.yml | ||
main.yml | ||
markdown-link-check.yml | ||
README.md | ||
refresh-be-cdn.yml | ||
tribal-deploy.yml |
Justice40 Github Actions Workflows
This directory has the github actions workflows for the Justice40 Project.
This project is deployed on an AWS account managed by GeoPlatform.gov, and github actions is used to automate the data pipeline and all deployment steps.
The names of the Github Actions stages in the yaml files should describe what each step does, so it is best to refer there to understand the latest of what everything is doing.
To mitigate the risk of having this README quickly become outdated as the project evolves, avoid documenting anything application or data pipeline specific here. Instead, go back up to the top level project README and refer to the documentation on those components directly.