A tool to identify disadvantaged communities due to environmental, socioeconomic and health burdens.
Find a file
Shelby Switzer 819f3ff478
Update etl constants to use score field_names and put strings around tract IDs in downloadable CSV (#985)
* Update etl constants to use score field_names

Put strings around tract IDs in downloadable CSV

No need to modify the xls file creation because the string type is
preserved and interpreted correctly in Excel already.

One note is that this does cause the ID in the CSV to be have quotes
around it, which might be annoying. Maybe we don't want this behavior?

* Update based on PR feedback and lint needs

* Change field we're using in downloadable

This reverts the downloadable csv field list to use
MEDIAN_INCOME_AS_PERCENT_OF_STATE_FIELD instead of
MEDIAN_INCOME_AS_PERCENT_OF_AMI_FIELD in order to get the test to pass.
The point of this PR is a refactor (and a small change to the CSV
quotations), not to change the output. That will be a different PR
later.

Co-authored-by: Shelby Switzer <shelby.switzer@cms.hhs.gov>
2021-12-06 13:17:17 -05:00
.github Update combine-tilefy.yml 2021-11-30 15:03:07 -05:00
client [Draft] Adds Nominatum search behind a feature flag (#935) 2021-12-03 07:56:15 -08:00
data Update etl constants to use score field_names and put strings around tract IDs in downloadable CSV (#985) 2021-12-06 13:17:17 -05:00
docs Add orientation deck to docs (#863) 2021-11-05 13:21:26 -04:00
infrastructure Bump ansi-regex in /infrastructure/functions/detect-changes-for-worker (#733) 2021-09-22 13:50:20 -04:00
.adr-dir almost finished 2021-04-22 12:40:56 -04:00
.gitignore Data Unit Tests (#509) 2021-09-10 14:17:34 -04:00
CODE_OF_CONDUCT-es.md Add translations for repo documents (#281) 2021-07-01 13:48:03 -04:00
CODE_OF_CONDUCT.md Add translations for repo documents (#281) 2021-07-01 13:48:03 -04:00
COMMUNITY_GUIDELINES.md Add community guidelines (#83) 2021-06-18 09:18:48 -04:00
CONTRIBUTING-es.md Add translations for repo documents (#281) 2021-07-01 13:48:03 -04:00
CONTRIBUTING.md Add translations for repo documents (#281) 2021-07-01 13:48:03 -04:00
docker-compose.yml Attempt to merge Lighthouse Fix branch from Nat (#758) 2021-10-04 08:43:33 -07:00
INSTALLATION-es.md Update data documentation and some data steps (#407) 2021-07-29 10:28:52 -04:00
INSTALLATION.md Update data documentation and some data steps (#407) 2021-07-29 10:28:52 -04:00
LICENSE-es.md Add translations for repo documents (#281) 2021-07-01 13:48:03 -04:00
LICENSE.md Add translations for repo documents (#281) 2021-07-01 13:48:03 -04:00
MAINTAINERS-es.md Update CODEOWNERS (#705) 2021-09-17 10:07:12 -04:00
MAINTAINERS.md Update CODEOWNERS (#705) 2021-09-17 10:07:12 -04:00
package-lock.json Zoom button styling does not match spec // General custom controls fix (#357) 2021-07-15 10:28:51 -04:00
package.json Zoom button styling does not match spec // General custom controls fix (#357) 2021-07-15 10:28:51 -04:00
README-es.md Update README-es.md 2021-07-01 17:56:46 -07:00
README.md Update README.md (#868) 2021-11-16 10:03:32 -05:00

Justice40 Tool

CC0 License

¡Lea esto en español!

Welcome to the Justice40 Open Source Community! This repo contains the code, processes, and documentation for the data and tech powering the Justice40 Climate and Economic Justice Screening Tool (CEJST).

Background

The Justice40 initiative and screening tool were announced in an Executive Order in January 2021, with the goal to launch an MVP of the tool by July 27, 2021. This tool will include interactive maps and an initial draft scorecard which federal agencies can use to prioritize historically overburdened and underserved communities for benefits in their programs.

Please see our Open Source Community Orientation deck for more information on the Justice40 initiative, our team, this project, and ways to participate.

Core team

The core Justice40 team building this tool is a small group of designers, developers, and product managers from the US Digital Service in partnership with the Council on Environmental Quality (CEQ).

An up-to-date list of core team members can be found in MAINTAINERS.md. The engineering members of the core team who maintain the code in this repo are listed in .github/CODEOWNERS.

Community

The Justice40 team is taking a community-first and open source approach to the product development of this tool. We believe government software should be made in the open and be built and licensed such that anyone can take the code, run it themselves without paying money to third parties or using proprietary software, and use it as they will.

We know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in data science or technology, or who have experience in climate, economic,or environmental justice work. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.

We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents in multiple languages, and offer support to our community members of a wide variety of background and skillsets, directly or in the form of group chats and training. If you have ideas for how we can improve or add to our capacity building efforts and methods for welcoming folks into our community, please let use know in the Google Group or email us at justice40open@usds.gov.

Community Guidelines

Principles and guidelines for participating in our open source community are available here. Please read them before joining or starting a conversation in this repo or one of the channels listed below.

Community Chats

We host open source community chats every third Monday of the month at 5-6pm ET. You can find information about the agenda and how to participate in our Google Group.

Community members are welcome to share updates or propose topics for discussion in community chats. Please do so in the Google Group.

Google Group

Our Google Group is open to anyone to join and share their knowledge or experiences, as well as to ask questions of the core Justice40 team or the wider community.

The core team uses the group to post updates on the program and tech/data issues, and to share the agenda and call for community participation in the community chat.

Curious about whether to ask a question here as a Github issue or in the Google Group? The general rule of thumb is that issues are for actionable topics related to the tool or data itself (e.g. questions about a specific data set in use, or suggestion for a new tool feature), and the Google Group is for more general topics or questions. If you can't decide, use the google group and we'll discuss there before moving to Github if appropriate!

Contributing

Contributions are always welcome! We encourage contributions in the form of discussion on issues in this repo and pull requests of documentation and code.

See CONTRIBUTING.md for ways to get started.

Installation

The installation is a typical gatsby install and the details can be found in INSTALLATION.md

Glossary

Confused about a term? Heard an acronym and have no idea what it stands for? Check out our glossary!

Feedback

If you have any feedback or questions, please reach out to us at justice40open@usds.gov.