You can access a working version of this application here.
Each city and county in California is required to produce a General Plan, a document that outlines and commits local governments to long-term development goals. Planning laws in the State of California mandate that every General Plan address a common set of issues, including Land Use, Conservation, and Housing. However, such laws do not specify where in the General Plan such issues need to be addressed or the format of the Plan overall. Thus, while General Plans offer the most comprehensive blueprint for future visioning of cities and counties throughout California, the structure and format of the Plans vary considerably across cities and counties. This makes it difficult to readily compare planning approaches across the state, to comparatively evaluate progress towards planning goals, and to set benchmarks for policy success.
This project is developing a platform for readily querying and extracting snippets of information about issues such as planned housing across all General Plans. Currently, there are no states that have such a public database for querying General Plans state-wide. The platform is expected to become a key policy implementation and enforcement infrastructure for the California OPR, a resource for community developers in collaborative planning, and a valuable information source for community members and researchers.
The General Plan Database Mapping Tool provides access to the text of California city and county General Plans and enables users to identify the plans in which a queried phrase is referenced. Upon searching, the tool filters a map to the cities in CA with General Plans that reference the phrase, offering a geospatial representation of its use. The tool also links to the plans that reference the search phrase.
| Contributions | Name |
|---|---|
| 💻 🚇 📖 🤔 | Aniket Banginwar |
| 💻 🚇 🤔 | Dexter Antonio |
| 💻 📖 🤔 | Mirthala Lopez |
| 📆 🧑🏫 🚇 📖 🤔 | Lindsay Poirier |
| 💻 🚇 🤔 | Sujoy Ghosh |
| 💻 🚇 🤔 | Makena Dettman |
| 📆 🔬 🔣 🤔 | Catherine Brinkley |
(For a key to the contribution emoji or more info on this format, check out “All Contributors.”)
-
File an issue via this repo's issue queue.
-
Write code to fix issues or to create new features. When contributing code, please be sure to:
- Fork this repository, modify the code (changing only one thing at a time), and then issue a pull request for each change.
- Follow the project's coding style (using K&R-style indentation and bracketing, commenting above each feature, and using snake case for variables).
- Test your code locally before issuing a pull request.
- Clearly state the purpose of your change in the description field for each commit.
textsearch.py contains most of the code for searching the pdfs, creating the maps and tables, and displaying the maps and tables. uploader.py contains the code for uploading new pdfs, emailing the recipient of choice, and generating the searchable text document.
The data, including the shapefiles and population data for both the cities and counties are found in /static/data/. The code also looks for a folder named places inside /static/data/ which is where .pdfs and their corresponding .txt documents will be stored.
The .html templates are stored in /templates/. These templates contain references which are passed from textsearch.py. There are also dependencies on .css and .js code stored in /static/cssjs/css and /static/cssjs/js respectively. The images found on the site are stored in /static/images/.
Please follow the install guide on setting up a local version of the repository for testing and development.
Please see license file for details.
Aniket Banginwar, Dexter Antonio, Mirthala Lopez, Lindsay Poirier, Sujoy Ghosh, Makena Dettmann, & Catherine Brinkley. (2023, January 6). General Plan Database Mapping Tool (v3.0). Zenodo. https://doi.org/10.5281/zenodo.7508689
Contact [email protected]