> For the complete documentation index, see [llms.txt](https://metropolitan-area-planning-counc.gitbook.io/zoning-atlas-appendix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metropolitan-area-planning-counc.gitbook.io/zoning-atlas-appendix/master.md). # Introduction The Zoning Atlas consists of spatial data and associated tabular data for the base zoning districts and the overlay districts of the 101 municipalities in the MAPC region. This dataset is a unique resource for planners, researchers, and advocates interested in land use, development patterns, and development opportunities across the region. This technical appendix contains a summary of the Zoning Atlas data sources and, particular to base zoning districts, a discussion of our approach to the interpretation of bylaws and ordinances, a summary of the field structure of the tabular data, and an overview of each major field group in the tabular data. A complete data dictionary for the Zoning Atlas can be accessed at the link below. {% content-ref url="/pages/-MOl1R\_YiYmueOA3Fbd\_" %} [Data Dictionary](/zoning-atlas-appendix/data-dictionary.md) {% endcontent-ref %} The Zoning Atlas was assembled over nine years and will always be a work in progress. Its first release in December 2020 is a foundational dataset that will be updated and improved over time and with the contributions of municipal staff and other stakeholders. Municipal zoning boundaries and codes are living documents, and it is our intention that the Zoning Atlas will evolve as municipalities update their zoning. ### ### ### ### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://metropolitan-area-planning-counc.gitbook.io/zoning-atlas-appendix/master.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.