Mapping cities, counties, states, and countries that are enacting emergency tenant protections due to the COVID-19 pandemic, and where housing justice actions are taking place.
Data sourcing and maintenance is being provided by the Anti-Eviction Mapping Project.
DISCLAIMER: This data is by no means perfect or exhaustive of all emergency tenant protection policies. It has been crowdsourced and is maintained by a team of dedicated volunteers. If you notice something missing or incorrect in the data, please reach out to us to let us know so we may update it accordingly! The AEMP recognizes that we are mapping Indigenous lands that have been stolen, colonized, divided, and renamed. We have depicted colonial and nation-states geographies because tenant protection legislation exists within these borders. Our goal is to pay our respect to the original stewards of the land by using Indigenous names, whenever a third-part service that we depend on allows us to implement this modification.
Getting this project running locally requires that:
-
You are comfortable running programs on the CLI such as the Terminal program on MacOS.
-
You have installed NodeJS >=
v10.13and NPM >=6.4(NPM should automatically be installed with NodeJS). Older versions of any of these may or may not work.
After installing Node.js and cloning the repo, navigate to the root of the project directory and run npm i to install all dependencies. Now you are ready to get started. See the next section for the commands used in development.
This project was bootstrapped with Create React App, which provides the following commands. See package.json for all commands.
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
When embedding this website with an <iframe>, the settings of the map can be configured with URL hash values. The available params are as follows:
/#lat=<float>&lng=<float>&z=<integer>&states=<boolean>&cities=<boolean>&counties=<boolean>&rentstrike=<boolean>
To add translations:
- Copy the file
src/locale/en.json - Rename the file to using the IETF language tag standard followed by
.json. For example:de.json - Replace the existing text with the translated text.
- Do not change the keys. For example
{"do-not-change": "This text should be changed"}
Optional: implement the translation If you're comfortable with javascript, you can also add the language to the i18n configuration.
- Add the language code to the value of
languagesin the filesrc/utils/constants.js. For example:const languages = ['en', 'pt-BR', 'es-MX'] - Add the following to the file
src/locale/index.js, substitutingdefor the language code you are working with:
// In imports
import de from './de.json'
// Inside of the exported object
de: {
translation: de,
},- To validate that you have all the correct keys in your language file:
- Add your locale to the test file,
locale/locale.test.js, by importing at the top of the file, and adding it to thetranslationsobject. - Run
npm run test. If there are any missing or extra keys, you will see an error which informs you which key and language is the issue.
- To check that your new language works, run the development environment, and add
?lang=<your-lang>to the url. Make sure that all the expected text is displayed as expected.
Thank you for contributing!