Schema, domains, and file structure for Vermont's zoning database, aligned with the Vermont Zoning GIS Data Standard
This page documents the fields and allowed values in the Vermont Zoning Atlas. Where a field has an equivalent in the Vermont Zoning GIS Data Standard (Version 2.0, adopted November 12, 2025, revised March 11, 2026), the atlas uses the VCGI field name and domain values (full standard: files.vcgi.vermont.gov/other/standards-guidelines/zoning/zoning-standard.html), so the data can be combined with the statewide zoning dataset maintained by the RPCs and the State. The remaining fields follow the National Zoning Atlas methodology and capture detail the VCGI standard does not cover, such as setbacks, parking, and ADU rules.
25 of the 113 fields follow the VCGI standard. They are marked VCGI in the schema below.
Data has been broken into smaller files for ease in editing. In "data/RPC" all the zoning files are split out by Regional Planning Commission (RPC). These GeoJSONs can be explored in the abbreviated viewer on the homepage of this site or downloaded for further analysis. The RPC field in each file uses the VCGI code listed under Domains.
There is also a state-wide single file, "data/State of Vermont"; this is not the preferred way to update the files but rather for analysis.
If you are interested in viewing the legal PDFs downloaded as part of this process, explore "data/Town_Bylaw_Text" and the downloaded maps from town websites here: "data/Town_Zoning_Maps"
The machine-readable version of the schema on this page is analysis/canonical_fields.csv.
This effort is a collection of teams which includes volunteers, interns, and students. This was done over a year period from 2023-2024 and during this time updates to the zoning codes have already made some of this data inaccurate. It is likely that this data will only be updated once a year at most so this data can be out of date. It is also possible that the regulation from the State of Vermont may not be reflected in town zoning just due to the time it takes to update and comply with legislation and the very limited capacity many of these towns have to complete that work.
The dataset contains 113 fields covering district identification, housing treatment, dimensional standards (setbacks, lot size, height, parking), and housing-specific regulations. Fields that follow the VCGI standard use VCGI's names; the remaining fields use a prefix system: F1F = single-family, F2F = 2-unit, F3F = 3-unit, F4F = 4+ unit, ADU = accessory dwelling unit, PRD = planned residential development, PUD = planned unit development. Renamed fields show their previous name.
The atlas records 4+ unit housing as one category, while VCGI separates 4-unit and 5+ unit housing. The 4+ value is written to both VCGI fields (for example UT4 and UT5) and marked VCGI · from 4+.
| Field | Alias | Type | Description | Domain Values | Standard |
|---|---|---|---|---|---|
| District Identification | |||||
| OBJECT_ID | OBJECT ID | numerical | Unique sequential integer identifier assigned to each zoning district feature across all municipalities. | – | |
| COUNTYwas County | County | text | County per the VT Geographic Area Names and Codes Standard. | – | VCGI |
| RPC | Regional Planning Commission | text | Unique identifier of the Regional Planning Commission per the VT Geographic Area Names and Codes Standard (2-character code). | AC, BC, CC, CV, LC, MA, NV, NW, RR, TR, WR | VCGI |
| JXTNwas Municipal_Name | Jurisdiction | text | Name of town, city or incorporated village per the VT Geographic Area Names and Codes Standard. | – | VCGI |
| GEOIDwas GEO_ID | GEOID | text | Unique identifier of the town, city, or incorporated village per the VT Geographic Area Names and Codes Standard. Currently the Census GEOID; VCGI plans a combined town/village code (TVGEOID). | – | VCGI |
| DIST_NAMEwas District_Name | District Name | text | Full zoning district name as defined in the municipal zoning bylaw. | – | VCGI |
| ABBRDISTNMwas Abbreviated_District_Name | District Abbreviation | text | Abbreviated district name as used in maps and tables. | – | VCGI |
| District_Type | District Type | text | Classification of the district by its primary land use character (e.g., Primarily Residential, Nonresidential, Mixed with Residential, Overlay). | Primarily Residential, Nonresidential, Mixed with Residential, Overlay | |
| Bylaw_Date | Bylaw Date | text | Date of the zoning bylaw document from which data was collected. | – | |
| Elderly_Housing_District | Elderly Housing District | text | Indicates whether the district is designated specifically for elderly housing. | Yes, No | |
| District_Mapped | District Mapped | text | Indicates whether the zoning district has a corresponding mapped geographic boundary. | Yes, No | |
| OVERwas Overlay_District | Overlay | text | Overlay. Indicates whether this record is an overlay district layered on top of a base district. | Yes, No | VCGI |
| Base_Density | Base Density | numerical | Maximum residential density allowed in the district as a baseline, expressed in units per acre. | – | |
| FIPS6 | FIPS6 | numerical | Vermont six-digit FIPS place code identifying the municipality within the state. | – | |
| GIS_ID | GIS ID | text | Identifier used in the source GIS system, typically combining municipality name and district name. | – | |
| Last_Update | Last Update | text | Date the record was last updated in the source dataset. | – | |
| Shape_Length | Shape Length | numerical | Perimeter length of the zoning district polygon in decimal degrees. | – | |
| Shape_Area | Shape Area | numerical | Area of the zoning district polygon in decimal degrees squared. | – | |
| 1-Unit Housing (Single-Family) | |||||
| UT1was F1F_Allowance | 1-Unit Treatment | text | 1-Unit Treatment: how the bylaw treats 1-unit (single-family) residential structures. | AP, CU, SP, PR | VCGI |
| F1F_Front_Setback | F1F Front Setback | numerical | Minimum required setback from the front lot line for single-family structures, in feet. | – | |
| F1F_Side_Setback | F1F Side Setback | numerical | Minimum required setback from each side lot line for single-family structures, in feet. | – | |
| F1F_Rear_Setback | F1F Rear Setback | numerical | Minimum required setback from the rear lot line for single-family structures, in feet. | – | |
| F1F_Frontage | F1F Frontage | numerical | Minimum required road frontage for a single-family lot, in feet. | – | |
| F1F_Max_Height | F1F Max Height | numerical | Maximum allowed height for single-family structures, in feet. | – | |
| F1F_Max_Stories | F1F Max Stories | numerical | Maximum number of stories allowed for single-family structures. | – | |
| MIN_LOT_1Uwas F1F_Min_Lot_Size | 1-UNIT MIN LOT | numerical | 1-Unit Min. Lot, in acres. | – | VCGI |
| F1F_Max_Lot_Building_Coverage | F1F Max Lot Building Coverage | numerical | Maximum percentage of the lot that may be covered by a building footprint for single-family use. | – | |
| F1F_Max_Lot_Impervious_Coverage | F1F Max Lot Impervious Coverage | numerical | Maximum percentage of the lot that may be covered by impervious surfaces for single-family use. | – | |
| F1F_Min_Parking_Spaces | F1F Min Parking Spaces | numerical | Minimum number of off-street parking spaces required per single-family unit. | – | |
| F1F_Elderly_Housing_Only | F1F Elderly Housing Only | text | Indicates whether single-family housing in this district is restricted to elderly occupants only. | Yes, No | |
| F1F_Affordable_Housing_Only | F1F Affordable Housing Only | text | Indicates whether single-family housing in this district is restricted to affordable housing only. | Yes, No | |
| F1F_Max_Density | F1F Max Density | numerical | Maximum density allowed for single-family housing, in units per acre. | – | |
| 2-Unit Housing | |||||
| UT2was F2F_Allowance | 2-Unit Treatment | text | 2-Unit Treatment: how the bylaw treats 2-unit residential structures. | AP, CU, SP, PR | VCGI |
| F2F_Front_Setback | F2F Front Setback | numerical | Minimum required setback from the front lot line for 2-unit structures, in feet. | – | |
| F2F_Side_Setback | F2F Side Setback | numerical | Minimum required setback from each side lot line for 2-unit structures, in feet. | – | |
| F2F_Rear_Setback | F2F Rear Setback | numerical | Minimum required setback from the rear lot line for 2-unit structures, in feet. | – | |
| F2F_Frontage | F2F Frontage | numerical | Minimum required road frontage for a 2-unit residential lot, in feet. | – | |
| MAX_DEN_2Uwas F2F_Max_Density | 2-UNIT MAX DENSITY | numerical | 2-Unit Max. Density, in dwelling units per acre. | – | VCGI |
| F2F_Max_Height | F2F Max Height | numerical | Maximum allowed height for 2-unit structures, in feet. | – | |
| F2F_Max_Stories | F2F Max Stories | numerical | Maximum number of stories allowed for 2-unit structures. | – | |
| MIN_LOT_2Uwas F2F_Min_Lot_Size | 2-UNIT MIN LOT | numerical | 2-Unit Min. Lot, in acres. | – | VCGI |
| F2F_Max_Lot_Building_Coverage | F2F Max Lot Building Coverage | numerical | Maximum percentage of the lot that may be covered by a building footprint for 2-unit use. | – | |
| F2F_Max_Lot_Impervious_Coverage | F2F Max Lot Impervious Coverage | numerical | Maximum percentage of the lot covered by impervious surfaces for 2-unit use. | – | |
| F2F_Min_Parking_Spaces_per_1BR | F2F Min Parking Spaces per 1BR | numerical | Minimum off-street parking spaces required per 1-bedroom unit in a 2-unit building. | – | |
| F2F_Min_Parking_Spaces_per_mult_BR | F2F Min Parking Spaces per mult BR | numerical | Minimum off-street parking spaces required per multi-bedroom unit in a 2-unit building. | – | |
| F2F_Elderly_Housing_Only | F2F Elderly Housing Only | text | Indicates whether 2-unit housing in this district is restricted to elderly occupants only. | Yes, No | |
| F2F_Affordable_Housing_Only | F2F Affordable Housing Only | text | Indicates whether 2-unit housing in this district is restricted to affordable housing only. | Yes, No | |
| 3-Unit Housing | |||||
| UT3was F3F_Allowance | 3-Unit Treatment | text | 3-Unit Treatment: how the bylaw treats 3-unit residential structures. | AP, CU, SP, PR | VCGI |
| F3F_Front_Setback | F3F Front Setback | numerical | Minimum required setback from the front lot line for 3-unit structures, in feet. | – | |
| F3F_Side_Setback | F3F Side Setback | numerical | Minimum required setback from each side lot line for 3-unit structures, in feet. | – | |
| F3F_Rear_Setback | F3F Rear Setback | numerical | Minimum required setback from the rear lot line for 3-unit structures, in feet. | – | |
| F3F_Frontage | F3F Frontage | numerical | Minimum required road frontage for 3-unit residential use, in feet. | – | |
| MAX_DEN_3Uwas F3F_Max_Density | 3-UNIT MAX DENSITY | numerical | 3-Unit Max. Density, in dwelling units per acre. | – | VCGI |
| F3F_Max_Height | F3F Max Height | numerical | Maximum allowed height for 3-unit structures, in feet. | – | |
| F3F_Max_Stories | F3F Max Stories | numerical | Maximum number of stories allowed for 3-unit structures. | – | |
| MIN_LOT_3Uwas F3F_Min_Lot_Size | 3-UNIT MIN LOT | numerical | 3-Unit Min. Lot, in acres. | – | VCGI |
| F3F_Max_Lot_Building_Coverage | F3F Max Lot Building Coverage | numerical | Maximum percentage of the lot covered by building footprint for 3-unit use. | – | |
| F3F_Max_Lot_Impervious_Coverage | F3F Max Lot Impervious Coverage | numerical | Maximum percentage of the lot covered by impervious surfaces for 3-unit use. | – | |
| F3F_Min_Parking_Spaces_per_1BR | F3F Min Parking Spaces per 1BR | numerical | Minimum off-street parking spaces per 1-bedroom unit in a 3-unit building. | – | |
| F3F_Min_Parking_Spaces_per_mult_BR | F3F Min Parking Spaces per mult BR | numerical | Minimum off-street parking spaces per multi-bedroom unit in a 3-unit building. | – | |
| F3F_Affordable_Housing_Only | F3F Affordable Housing Only | text | Indicates whether 3-unit housing in this district is restricted to affordable housing only. | Yes, No | |
| F3F_Proximity_to_Public_Transit_Required | F3F Proximity to Public Transit Required | text | Indicates whether 3-unit housing requires proximity to public transit service. | Yes, No | |
| F3F_Connection_to_Sewage/Water_Required | F3F Connection to Sewage/Water Required | text | Indicates whether 3-unit housing requires connection to public sewer or water systems. | Yes, No | |
| F3F_Elderly_Housing_Only | F3F Elderly Housing Only | text | Indicates whether 3-unit housing in this district is restricted to elderly occupants only. | Yes, No | |
| 4+ Unit Housing | |||||
| UT4was F4F_Allowance | 4-Unit Treatment | text | 4-Unit Treatment. Collected as a single 4+ unit value, so UT4 and UT5 are equal. | AP, CU, SP, PR | VCGI · from 4+ |
| UT5was F4F_Allowance | 5+Unit Treatment | text | 5+Unit Treatment. Collected as a single 4+ unit value, so UT4 and UT5 are equal. | AP, CU, SP, PR | VCGI · from 4+ |
| F4F_Front_Setback | F4F Front Setback | numerical | Minimum required setback from the front lot line for 4+ unit structures, in feet. | – | |
| F4F_Side_Setback | F4F Side Setback | numerical | Minimum required setback from each side lot line for 4+ unit structures, in feet. | – | |
| F4F_Rear_Setback | F4F Rear Setback | numerical | Minimum required setback from the rear lot line for 4+ unit structures, in feet. | – | |
| F4F_Frontage | F4F Frontage | numerical | Minimum required road frontage for 4+ unit multifamily use, in feet. | – | |
| MAX_DEN_4Uwas F4F_Max_Density | 4-UNIT MAX DENSITY | numerical | 4-Unit Max. Density, in dwelling units per acre. Collected as a single 4+ unit value, so MAX_DEN_4U and MAX_DEN_5U are equal. | – | VCGI · from 4+ |
| MAX_DEN_5Uwas F4F_Max_Density | 5+UNIT MAX DENSITY | numerical | 5+Unit Max. Density, in dwelling units per acre. Collected as a single 4+ unit value, so MAX_DEN_4U and MAX_DEN_5U are equal. | – | VCGI · from 4+ |
| F4F_Max_Height | F4F Max Height | numerical | Maximum allowed height for 4+ unit multifamily structures, in feet. | – | |
| F4F_Max_Stories | F4F Max Stories | numerical | Maximum number of stories allowed for 4+ unit multifamily structures. | – | |
| MIN_LOT_4Uwas F4F_Min_Lot_Size | 4-UNIT MIN LOT | numerical | 4-Unit Min. Lot, in acres. Collected as a single 4+ unit value, so MIN_LOT_4U and MIN_LOT_5U are equal. | – | VCGI · from 4+ |
| MIN_LOT_5Uwas F4F_Min_Lot_Size | 5+UNIT MIN LOT | numerical | 5+Unit Min. Lot, in acres. Collected as a single 4+ unit value, so MIN_LOT_4U and MIN_LOT_5U are equal. | – | VCGI · from 4+ |
| F4F_Max_Lot_Building_Coverage | F4F Max Lot Building Coverage | numerical | Maximum percentage of the lot covered by building footprint for 4+ unit use. | – | |
| F4F_Max_Lot_Impervious_Coverage | F4F Max Lot Impervious Coverage | numerical | Maximum percentage of the lot covered by impervious surfaces for 4+ unit use. | – | |
| F4F_Min_Parking_Spaces_per_1BR | F4F Min Parking Spaces per 1BR | numerical | Minimum off-street parking spaces per 1-bedroom unit in a 4+ unit building. | – | |
| F4F_Min_Parking_Spaces_per_mult_BR | F4F Min Parking Spaces per mult BR | numerical | Minimum off-street parking spaces per multi-bedroom unit in a 4+ unit building. | – | |
| F4F_Elderly_Housing_Only | F4F Elderly Housing Only | text | Indicates whether 4+ unit housing in this district is restricted to elderly occupants only. | Yes, No | |
| F4F_Affordable_Housing_Only | F4F Affordable Housing Only | text | Indicates whether 4+ unit housing in this district is restricted to affordable housing only. | Yes, No | |
| F4F_Proximity_to_Public_Transit_Required | F4F Proximity to Public Transit Required | text | Indicates whether 4+ unit housing requires proximity to public transit service. | Yes, No | |
| F4F_Connection_to_Sewage/Water_Required | F4F Connection to Sewage/Water Required | text | Indicates whether 4+ unit housing requires connection to public sewer or water systems. | Yes, No | |
| Accessory Dwelling Units (ADU) | |||||
| ADUDPwas ADU_Allowance | Accessory Dwelling Unit Treatment | text | Accessory Dwelling Unit Treatment. | AP, CU, SP, PR | VCGI |
| ADU_Elderly_Housing_Only | ADU Elderly Housing Only | text | Indicates whether ADUs in this district are restricted to elderly occupants only. | Yes, No | |
| ADU_Max_Size_as_Percent_of_Primary_Strcture | ADU Max Size as Percent of Primary Strcture | mixed | Maximum allowed size of an ADU as a percentage of the primary structure's floor area; may contain 'No' where no limit applies. | – | |
| ADU_Max_Size_in_sq_ft | ADU Max Size in sq ft | numerical | Maximum allowed floor area of an ADU in square feet. | – | |
| ADU_Min_Lot_Size | ADU Min Lot Size | numerical | Minimum lot size required for a property to include an ADU, in acres. | – | |
| ADU_Max_Bedrooms | ADU Max Bedrooms | numerical | Maximum number of bedrooms allowed in an ADU. | – | |
| ADU_Min_Parking_Spaces | ADU Min Parking Spaces | numerical | Minimum off-street parking spaces required for an ADU. | – | |
| ADU_Owner_Occupancy_Required | ADU Owner Occupancy Required | text | Indicates whether the property owner must occupy either the primary structure or the ADU. | Yes, No | |
| ADU_Renter_Occupancy_Prohibited | ADU Renter Occupancy Prohibited | text | Indicates whether renting the ADU to non-family members is prohibited. | Yes, No | |
| ADU_Employee_or_Family_Occupancy_Required | ADU Employee or Family Occupancy Required | text | Indicates whether the ADU must be occupied by an employee or family member of the property owner. | Yes, No | |
| ADU_Restricted_to_Primary_Structure | ADU Restricted to Primary Structure | text | Indicates whether the ADU must be contained within or attached to the primary structure rather than built as a detached unit. | Yes, No | |
| Affordable Housing | |||||
| Affordable_Housing_Allowance | Affordable Housing Allowance | text | Whether affordable housing developments are permitted in the district as a distinct use category. | Permitted, Prohibited, Allowed/Conditional, Public Hearing | |
| Affordable_Housing_District | Affordable Housing District | text | Indicates whether the district is specifically designated for affordable housing development. | Yes, No | |
| Affordable_Housing_Elderly_Only | Affordable Housing Elderly Only | text | Indicates whether affordable housing in this district is restricted to elderly residents only. | Yes, No | |
| Affordable_Housing_Min_Lot_Size | Affordable Housing Min Lot Size | numerical | Minimum lot size required for affordable housing development, in acres. | – | |
| Affordable_Housing_Max_Density | Affordable Housing Max Density | numerical | Maximum density allowed for affordable housing, in units per acre. | – | |
| Affordable_Housing_Min_Parking_Spaces_per_mult_BR | Affordable Housing Min Parking Spaces per mult BR | numerical | Minimum off-street parking spaces per multi-bedroom affordable housing unit. | – | |
| Affordable_Housing_Max_Units_per_Building | Affordable Housing Max Units per Building | numerical | Maximum number of units allowed per affordable housing building. | – | |
| Affordable_Housing_Min_Parking_Spaces_per_1BR | Affordable Housing Min Parking Spaces per 1BR | numerical | Minimum off-street parking spaces per 1-bedroom affordable housing unit. | – | |
| Planned Residential Development (PRD) | |||||
| PRDDPwas PRD_Allowance | Planned Residential Development Treatment | text | Planned Residential Development Treatment. | AP, CU, SP, PR | VCGI |
| PRD_Max_Density | PRD Max Density | numerical | Maximum density allowed for a planned residential development, in units per acre. | – | |
| PRD_Max_Units | PRD Max Units | numerical | Maximum total number of units allowed in a planned residential development. | – | |
| PRD_Min_Lot_Size | PRD Min Lot Size | numerical | Minimum lot size required to develop a planned residential development, in acres. | – | |
| PRD_MHPwas PRD_Mobile_or_Manufactured_Home_Park | Mobile or Manufactured Home Park Allowed | text | Mobile or Manufactured Home Park allowed in a PRD. VCGI expects a treatment code; this dataset records Yes/No. | Yes, No | VCGI name only |
| Planned Unit Development (PUD) | |||||
| PUD_Allowance | PUD Allowance | text | Whether planned unit developments (PUDs) are permitted in the district. | Yes, No | |
| PUD_Required_with_Subdivision | PUD Required with Subdivision | text | Indicates whether PUD approval is required when subdividing land in this district. | Yes, No | |
| PUD_Requires_Land_Conservation | PUD Requires Land Conservation | text | Indicates whether PUD approval requires setting aside land for conservation. | Yes, No | |
| PUD_Threshold_Number | PUD Threshold Number | numerical | Minimum number of units or lots that triggers PUD requirements in the district. | – | |
| Additional Information | |||||
| NOTEwas Notes | Note | text | Notes. Free-text context about the district's regulations or data collection. | – | VCGI |
The domain values below apply to the following fields: UT1, UT2, UT3, UT4, UT5, ADUDP, PRDDP. Counts are districts in the statewide file (1,760 districts).
| Code | Description | UT1 | UT2 | UT3 | UT4 | UT5 | ADUDP | PRDDP |
|---|---|---|---|---|---|---|---|---|
| AP | Administrative Permit. Converted from Permitted. | 903 | 745 | 231 | 89 | 89 | 32 | 0 |
| CU | Conditional Use. Converted from Public Hearing. | 135 | 223 | 574 | 700 | 700 | 128 | 577 |
| SP | Site Plan. No values converted yet (see Allowed/Conditional). | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| PR | Prohibited. Converted from Prohibited. | 346 | 469 | 742 | 758 | 758 | 278 | 343 |
Some National Zoning Atlas values have no single VCGI code and are kept as collected until each district is reviewed against its bylaw:
| Value | Meaning | UT1 | UT2 | UT3 | UT4 | UT5 | ADUDP | PRDDP |
|---|---|---|---|---|---|---|---|---|
| Allowed/Conditional | Allowed without a public hearing: either an administrative permit (AP) or site plan review (SP). Needs bylaw review to split. | 233 | 183 | 81 | 81 | 81 | 1,122 | 193 |
| Not Mentioned | The bylaw does not address this use. | 0 | 0 | 0 | 0 | 0 | 158 | 615 |
| Overlay | Treatment is set by an overlay district. | 0 | 0 | 0 | 0 | 0 | 29 | 11 |
| (blank) | No value recorded. | 143 | 140 | 132 | 132 | 132 | 13 | 21 |
2-character codes from the Vermont Geographic Area Names and Codes Standard, as listed in the VCGI zoning standard.
The atlas classifies districts with the National Zoning Atlas categories below. This is a different classification from VCGI's DIST_TYPE list (Downtown, Village Center, Forest, and so on). See VCGI Fields Not Yet Collected.
| Value | Description | Districts |
|---|---|---|
| Primarily Residential | Residential uses are the main allowed uses. | 501 |
| Mixed with Residential | Residential and nonresidential uses are both allowed. | 804 |
| Nonresidential | Residential uses are generally not allowed. | 337 |
| Overlay | Overlay district layered on top of base districts. | 109 |
Census GEOID for the town, city, or incorporated village. VCGI expects to add a combined town/village code (TVGEOID) to the Names and Codes standard; GEOID will be updated to that code once it is published.
These VCGI fields have no equivalent in the atlas yet. Where a related atlas field exists, it is noted.
| VCGI Field | Alias | Status in the Atlas |
|---|---|---|
| DIST_TYPE | District Type | Our District_Type uses the 4 National Zoning Atlas categories (Primarily Residential, Mixed with Residential, Nonresidential, Overlay), not VCGI's land-use list. Needs district-by-district classification. |
| DTYPNONRES | District Type Non-residential | Partly covered by District_Type = Nonresidential. |
| RES_ALLOW | Residential Allowed | Can be derived: Yes when any of UT1–UT5 is not PR. |
| ADUS | Accessory Dwelling Unit Size | Related to ADU_Max_Size_in_sq_ft and ADU_Max_Size_as_Percent_of_Primary_Strcture, which record limits rather than a treatment. |
| AFFDHR | Affordable Housing Requirement | Not collected. Affordable_Housing_* fields record allowances, not requirements. |
| AFFDHINC | Affordable Housing Incentive | Not collected. Affordable_Housing_Max_Density may indicate a density bonus. |
| BYLAW_EFF | Bylaw Effective | Bylaw_Date is the date data was collected, not the bylaw effective date. Effective dates are in the bylaw PDF file names (..._eff11272007.pdf). |
| MINLOT1_NT | 1-UNIT MIN LOT NOTES | Not collected. Lot-size caveats are in NOTE. |
| MINLOT2_NT | 2-UNIT MIN LOT NOTES | Not collected. Lot-size caveats are in NOTE. |
| MINLOT3_NT | 3-UNIT MIN LOT NOTES | Not collected. Lot-size caveats are in NOTE. |
| MINLOT4_NT | 4-UNIT MIN LOT NOTES | Not collected. Lot-size caveats are in NOTE. |
| MINLOT5_NT | 5+UNIT MIN LOT NOTES | Not collected. Lot-size caveats are in NOTE. |
| DATE_RPC | Date from RPC | Last_Update is related but records the source GIS update date. |
These values could not be converted to the VCGI standard automatically and need review against the municipal bylaws. District counts are from the statewide file (1,760 districts).
| # | Item | Fields | Districts | What's Needed |
|---|---|---|---|---|
| 1 | Split Allowed/Conditional into AP or SP | UT1–UT5, ADUDP, PRDDP | 1,172 | Allowed/Conditional covers both an administrative permit (AP) and site plan review (SP). Check each district's bylaw and record AP or SP. |
| 2 | Resolve Not Mentioned and Overlay treatments | ADUDP, PRDDP | 679 | VCGI has no code for these. Decide how to record them, for example PR when the bylaw is silent, or the overlay district's treatment. |
| 3 | Record mobile home park treatment | PRD_MHP | 1,472 | VCGI expects a treatment code (AP, CU, SP, PR); the atlas records Yes/No. Re-review bylaws to record how mobile or manufactured home parks are permitted. |
| 4 | Classify districts with VCGI district types | DIST_TYPE (new) | 1,760 | Assign each district one of VCGI's 18 district types (Downtown, Village Center, Rural Residential, and so on). District_Type keeps the National Zoning Atlas categories and cannot be converted automatically. |
| 5 | Add bylaw effective dates | BYLAW_EFF (new) | 1,760 | Bylaw_Date is the data collection date, so it was not renamed. Effective dates are in the bylaw PDF file names in data/Town_Bylaw_Text and could be filled from there. |
The map on the homepage colors districts by the treatment of the selected housing type (UT1–UT4). Overlay districts (OVER = Yes) are not drawn.
| Treatment | HEX # | Color |
|---|---|---|
| AP | #27AE60 | |
| CU, Allowed/Conditional | #F39C12 | |
| PR | #E74C3C | |
| No data | #95A5A6 |
| Date | Notes |
|---|---|
| October 29, 2026 | Aligned matching fields with the Vermont Zoning GIS Data Standard v2.0 (March 11, 2026 revision): 21 fields renamed to VCGI names, 3 VCGI 5+ unit fields added from the 4+ unit values, RPC values converted to VCGI codes, and Permitted / Public Hearing / Prohibited converted to AP / CU / PR. |
| February 26, 2026 | Canonical 110-field schema established across all RPC and statewide files. |