This dataset represents the APPROXIMATE delineations for the City of Charlottesville's boundary. This information is NOT to be construed or used as a "legal description". The boundary may be modified and updated as more up-to-date information is obtained. Boundaries are believed to be somewhat accurate, but accuracy is not guaranteed.

Detailed boundary from U.S. Census

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This file represents the City of Charlottesville's digital City boundary (City limits) layer in a closed polygon format.The information contained in this file is NOT to be construed or used as a "legal description.” Any errors or omissions should be reported to NDS for correction.

Only active parcels are included in this dataset. This layer shows the latest parcel boundaries and owner information recorded in the city's property records. Since some parcels have more than one owner (like condos), this dataset connects each parcel shape (GPIN) to all its owners (PIN).Neighborhood Development Services (NDS) assigns zoning and addresses, then shares this information with the City Assessor's Office to be added to the property records system (CAMA).This file is not a legal document for any parcel. Any mistakes or missing information can be directed to the Assessor's Office to have them corrected.

This dataset represents all real property parcels within the City of Charlottesville, Virginia that are owned by the City of Charlottesville or the City School Board. It includes detailed polygon geometry of parcel boundaries and joins authoritative ownership data from the parcel points layer to identify parcels currently held by the City. The data is filtered using a dynamic view that identifies ownership using common naming conventions found in city records. This includes ownership by the City of Charlottesville, City School Board, and other variations used in tax assessment and land records. Fields Included:OBJECTID: Internal database identifierGPIN: Geographic Parcel Identification NumberOWNER: Current owner name (e.g., "City of Charlottesville")SHAPE: Polygon geometry representing parcel boundaries Source & Processing Notes:Based on authoritative data from the City’s GIS parcel datasets (parcel_area and parcel_point)Ownership identified via dynamic SQL view matching typical City and School Board naming conventionsOWNER LIKE 'CITY OF CH''VILLE%'pt.OWNER LIKE 'CITY OF CHARLOTTESVILLE%'pt.OWNER LIKE 'CITY OF, CH''VILLE%'pt.OWNER LIKE 'CITY OF, CHARLOTTESVILLE%'pt.OWNER LIKE 'CITY, OF CHARLOTTESVILLE%'pt.OWNER LIKE 'SCHOOL BD-CITY OF CH''VILLE%'pt.OWNER LIKE 'SCHOOL BOARD%'pt.OWNER LIKE 'SCHOOL, BD-OF CH''VILLE%'pt.OWNER LIKE 'SCHOOL, BOARD OF%'Spatial joins ensure parcel geometry is directly linked to ownership point recordsUpdated regularly to reflect current ownership from tax and assessor records

Only active parcels are included in this data set. This layer represents the most recent parcel boundaries as recorded through deeds for the City. Real property zoning and addresses are assigned by Neighborhood Development Services and provided to City Assessor staff for entry into the CAMA system. The information contained in this file is NOT to be construed or used as a "legal description" of any parcel. Any perceived errors or omissions should be reported to the City Assessor's Office for correction.For more information see the "Parcel Area Details" datasetPlease refer to this Data Guide for details on how to access and join Real Estate data

This layer represents voting precinct boundaries within the City of Charlottesville.

This layer represents Elementary school attendance boundaries within the City of Charlottesville.

The 2019 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The cartographic boundary files include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this file are as of January 1, 2019, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

The dataset contains locations and attributes of Neighborhood Planning Areas provided by Neighborhood Development Services (NDS). These do not reflect precise neighborhood locations and do not necessarily include all commonly-used neighborhood designations. There is no formal set of standards that describes which neighborhoods are included in this dataset. Note that the City does not have official neighborhood boundaries.

Only active parcels are included in this data set. This layer represents the most recent parcel boundaries (and detail information) as recorded through deeds for the City. Since some parcels have multiple owners (e.g. Condos), this data set includes the one-to-many relationship between the parcel polygon (GPIN) and the individual parcel owner(s) (ParcelNumber). Real property zoning and addresses are assigned by Neighborhood Development Services and provided to City Assessor staff for entry into the CAMA system. The information contained in this file is NOT to be construed or used as a "legal description" of any parcel. Any perceived errors or omissions should be reported to the City Assessor's Office for correction.Please refer to this Data Guide for details on how to access and join Real Estate data

The physical location covered by an interagency, dispatch center for the effective coordination, mobilization and demobilization of emergency management resources. A dispatch center actively supports incidents within its boundaries and the resources assigned to those incidents.07/28/2025 - Updated email for USIDCIC from SM.FS.idcic@usda.gov to idcic@firenet.gov; edited by JHobson01/23/2025 - Updated email for USCAANCC to firenet email; edited by KJHansen6/27/2023 - Tabular changes only. Edits by JHobson, NPS. For Taos Interagency Dispatch Center, change Email from pdl_r3_Taos_Dispatch_Center@fs.fed.us to nmtdc@firenet.gov. For Santa Fe Interagency Dispatch Center, change Email from nmsfc01dispatch@fs.fed.us to nmsfc@firenet.gov.For Missoula Interagency Dispatch Center, change Email from sm.fs.mtmdc@firenet.gov to mtmdc@firenet.gov.Albuquerque Interagency Dispatch Center, change Email from nmabc01.dispatch@usda.gov to nmabc@firenet.gov. 3/31/2023 - 4/4/2023 - Tabular changes only. DispLocation and GACCUnitID updated using Unit IDx information current as of 4/3/2023. Edits by JKuenzi, USFS. Text changes to table include:For GACCUnitID, change USNWCC to USORNWC.For GACCUnitID, change USUTGBCC to USUTGBC.For USAZPHC, change DispLocation from Phoenix, AZ, to Mesa, AZ.For USORCOC, change DispLocation from Prineville,OR, to Redmond, OR.For USOREIC, change DispLocation from Eugene, OR, to Springfield, OR.For USPRCIC, change DispLocation from Boqueron, PR, to Palmer de Rio, PR.For USUTNUC, change DispLocation from Salt Lake City, UT, to Draper, UT.For USVAVIC, change DispLocation from Roanoke, VA, to Charlottesville, VA.For USWYTDC, change DispLocation from Moose, WY, to Bondurant, WY.3/23/2023-3/24/2023 - Tabular changes only. ContactPhone updated using Unit IDx information current as of 3/24/2023. Text changes per Official Unit IDs list "Unit Idx Name" field supplied by Kara Stringer (Combined Dispatch Centers 03222023.xlsx), co-lead for NWCG Unit ID Committee. Edits by JKuenzi, USFS. Changes include:GACCName from "Southwest Coordination Center" to "Southwest Area Coordination Center"GACCName from "Southern California Geographic Area Coordination Center" to "Southern California Coordination Center"DispUnitID from USCAMRNC to USCAMRCCDispName from "Angeles Emergency Communication Center" to "Angeles Communication Center"DispName from "Bitterroot Interagency Dispatch Center" to "Bitterroot Dispatch Center"DispName from "Blue Mountain Interagency Communication Center" to "Blue Mountains Interagency Dispatch Center"DispName from "Boise Dispatch Center" to "Boise Interagency Dispatch Center"DispName from "Coeur d'Alene Interagency Dispatch Center" to "Coeur d'Alene Dispatch Center"DispName from "Dillon Interagency Dispatch Center" to "Dillon Dispatch Center"DispName from "Florida Interagency Dispatch Center" to "Florida Interagency Coordination Center"DispName from "Fort Belknap Dispatch" to "Fort Belknap Agency Dispatch Center"DispName from "Grass Valley Emergency Comm Center" to 'Grass Valley Interagency Emergency Command Center"DispName from "Great Falls Interagency Dispatch Center" to "Great Falls Dispatch Center"DispName from "Howard Forest Command Center" to "Howard Forest Emergency Command Center"DispName from "Illinois Interagency Dispatch Center" to "Illinois Interagency Coordination Center"DispName from "Kern County Fire Department Emergency Communication Center" to "Kern County Emergency Command Center"DispName from "Las Vegas Interagency Communication Center" to "Las Vegas Interagency Dispatch Center"DispName from "Los Padres Communications Center" to "Los Padres Communication Center"DispName from "Madera-Mariposa-Merced Emergency Command Center" to "Madera-Mariposa-Merced Command Center"DispName from "Mat-Su/Southwest Area Forestry Dispatch" to "Mat-Su/Southwest Area Dispatch"DispName from "Mid-Atlantic Coordination Center" to "Mid-Atlantic Interagency Coordination Center"DispName from "Missouri-Iowa Interagency Fire Center to Missouri-Iowa Interagency Dispatch Center"DispName from "North Dakota Interagency Dispatch Center" to "North Dakota Dispatch Center"DispName from "Owens Valley Interagency Communications Center" to "Owens Valley Interagency Command Center"DispName from "Plumas Emergency Communications Center" to "Plumas Emergency Communication Center"DispName from "Rocky Boy's Dispatch" to "Rocky Boy's Agency Dispatch Center"DispName from "Roseburg Interagency Coordination Center" to "Roseburg Interagency Communication Center"DispName from "San Benito-Monterey Emergency Command Center" to "San Benito Monterey Emergency Command Center"DispName from "Santa Clara Command Center" to "Santa Clara Emergency Command Center'DispName from "South Central Interagency Dispatch Center" to "South Idaho Interagency Dispatch Center"DispName from "Tuolumne Calaveras Command Center" to "Tuolumne Calaveras Emergency Command Center"DispName from "Valdez-Copper River Area Forestry Dispatch" to "Valdez-Copper River Area Dispatch"DispName from 'Woodacre Emergency Command Center" to "Woodacre Headquarters Emergency Command Center"DispName from "Yakima Agency Dispatch Center" to "Yakama Agency Dispatch Center"DispName from "Yreka Interagency Dispatch Center" to "Yreka Interagency Command Center"DispName from "Uinta Basin Interagency Fire Center" to "Uintah Basin Interagency Fire Center"DispName from "Wisconsin Interagency Dispatch Center (federal) /Wisconsin State Dispatch Center (state)" to "Wisconsin Interagency Dispatch Center"DispName from "Michigan Interagency Dispatch Center (federal) /Michigan State Dispatch Center (state)" to "Michigan Interagency Dispatch Center"DispName from "Fresno-Sierra Emergency Command Center" to "Sierra Interagency Communication Center"DispName from "Perris Emergency Command Center" to "Riverside Emergency Command Center"DispName from "Red Bluff Emergency Command Center" to "Tehama Glenn Emergency Command Center"DispName from "Visalia Emergency Command Center" to "Tulare Emergency Command Center"DispName from "Orville Emergency Command Center" to "Butte Emergency Command Center"DispName from "Saint Helena Emergency Command Center" to "Lake Napa Command Center" 1/11/2023 - Tabular and geospatial changes. USMTBFAC (Blackfeet Reservation) merged into USMTGDC (Great Falls Interagency Dispatch Center). USMTBFAC remains as 4th Tier Dispatch. USMTFHA (Flathead Reservation) merged into USMTMDC (Missoula Interagency Dispatch Center). USMTFHA remains as 4th Tier Dispatch. Changes made by Kat Sorenson, R1 Asst Aircraft Coordinator, and Kara Stringer, IRWIN Business Lead. Edits by JKuenzi.1/10/2023 - Tabular and geospatial changes. Two islands on west edge of John Day Dispatch area (USORJDCC) absorbed into USORCOC Dispatch per direction from Kaleigh Johnson (Asst Ctr Mgr), Jada Altman (Central Oregon Center Mgr), and Jerry Messinger (Air Tactical Group Supervisor). Update made to Dispatch and Initial Attack Frequency Zone boundaries. Edits by JKuenzi,11/08/2022 - Tabular and geospatial changes. Update made to Dispatch and Initial Attack Frequency Zone boundaries between Miles City Interagency Dispatch Center (USMTMCC) and Billings Interagency Dispatch Center (USMTBDC), along Big Horn and Rosebud County line near Little Wolf Mountains, per Kat Sorenson, R1 Asst Aircraft Coordinator, and Kelsey Pluhar, DNRC Asst. Center Manager at Miles City Interagency Dispatch Center. Area in Big Horn County is dispatched by MTMCC. Edits by JKuenzi,09/06/2022-09/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada. Boundary modified between CAOVCC (Owens Valley Interagency Communications Center) and NVSFC (Sierra Front Interagency Dispatch Center), specifically between Queen Valley and Mono Valley. The team making the change is made up of Southern Calif (JTomaselli) and Great Basin (GDingman) GACCs, with input from Ian Mills and Lance Rosen (BLM). Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of Initial Attack Frequency Zone boundaries and GACC boundaries in the area described. Initial edits provided by Ian Mills and Daniel Yarborough. Final edits by JKuenzi, USFS.A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area. Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270. East through Bodie to the CA/NV state line. Follows the CA/NV State Line south to HWY CA 167/NV 359. East on NV359 to where the HWY intersects the corner of FS/BLM land. Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary.09/22/2022 - Tabular changes only. The DispLocation value of "Prineville, OR", was updated to "Redmond, OR", and the ContactPhone value was updated for Central Oregon Interagency Dispatch Ctr (USORCOC) per direction from Desraye Assali, Supervisory GIS Specialist in Region 6. The original correction had been made 9/30/2020, in the National Dispatch Office Location dataset, but had been missed in the National Dispatch Boundary dataset. Edits by JKuenzi, USFS.09/07/2022 - 09/08/2022 - Tabular and geospatial changes. Multiple boundaries modified in Northern Rockies GACC to bring lines closer in accordance with State boundaries. Information provided by Don Copple, State Fire Planning & Intelligence Program Manager for Montana Dept of Natural Resources & Conservation (DNRC), Kathy Pipkin, Northern Rockies GACC Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi, USFS. The following changes were made:Boundary changes made to the following: Bitterroot Interagency Dispatch Ctr (USMTBDC), Dillon Interagency Dispatch Ctr (USMTDDC), Flathead Dispatch (USMTFHA), Great Falls Interagency Dispatch Ctr