EJScreen’s Environmental Justice Analysis Multisite Tool (EJAM) is a resource provided by the United States Environmental Protection Agency (US EPA). It lets you easily and quickly see demographic and environmental information aggregated within and across hundreds or thousands of places, all at the same time.
- EJAM powers EJScreen’s Multisite Tool, for providing public access to multisite reports. The EJScreen Multisite Tool can be reached from the EJScreen website or EJScreen Mapping application.
- EPA staff who are authenticated on the Agency’s internal network (by VPN or within the office) have access to a version of the web app that is configured specifically for staff use.
EJAM is also available to analysts and developers as an R Package written in the R programming language, with source code on GitHub. When used in RStudio, the EJAM package provides functions to help analysts work with block group data, points, and polygons, to very quickly aggregate and compare large numbers of locations.
Note that installing the R package also allows one to use EJAM as a
local web app, if the shiny app is launched locally on a user’s own
computer. The EJScreen Multisite Tool configuration is available via
run_app(isPublic=T) and the version for staff use is available via
run_app(isPublic=F)
Effective August 8, 2016, the OMB Mandate: M-16-21; Federal Source Code Policy: Achieving Efficiency, Transparency, and Innovation through Reusable and Open Source Software applies to new custom-developed code created or procured by EPA consistent with the scope and applicability requirements of Office of Management and Budget’s (OMB’s) Federal Source Code Policy. In general, it states that all new custom-developed code by Federal Agencies should be made available and reusable as open-source code.
The EPA specific implementation of OMB Mandate M-16-21 is addressed in the System Life Cycle Management Procedure. EPA has chosen to use GitHub as its version control system as well as its inventory of open-source code projects. EPA uses GitHub to inventory its custom-developed, open-source code and generate the necessary metadata file that is then posted to code.gov for broad reuse in compliance with OMB Mandate M-16-21.
If you have any questions or want to read more, check out the EPA Open Source Project Repo and EPA’s Interim Open Source Code Guidance.
We encourage analysts and developers to test the EJAM R package and the EJAM shiny app, and provide feedback, or to share code, and we welcome your suggestions or contributions.
By submitting a pull request or issue, you are agreeing to comply with a waiver of copyright interest.
This software/application has been approved for release by the U.S. Environmental Protection Agency (USEPA). Although the software has been subjected to rigorous review, the USEPA reserves the right to update the software as needed pursuant to further analysis and review. No warranty, expressed or implied, is made by the USEPA or the U.S. Government as to the functionality of the software and related material nor shall the fact of release constitute any such warranty. Furthermore, the software is released on condition that neither the USEPA nor the U.S. Government shall be held liable for any damages resulting from its authorized or unauthorized use.
The United States Environmental Protection Agency (EPA) GitHub project code is provided on an “as is” basis and the user assumes responsibility for its use. EPA has relinquished control of the information and no longer has responsibility to protect the integrity, confidentiality, or availability of the information. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by EPA.
The EPA seal and logo shall not be used in any manner to imply endorsement of any commercial product or activity by EPA or the United States Government.
If you have questions or comments, please contact the EJScreen team in EPA’s OEJECR, and for technical questions contact Mark Corrales ([email protected]).