This data represents the graphic portrayal of land parcels and their spatial relationships throughout York County, South Carolina. Land parcel boundaries are also the basis for and define coincident boundaries for other layers, such as zoning, subdivisions, public safety response (ORI -Police, Fire, EMS) and Jurisdiction.Boundaries are established from a variety of sources including cadastral plats, subdivision plats, deeds, land contracts, right-of-way plats, and others. Each feature represents a parcel of land that is inventoried by a unique identifier, referred to as a “Tax Map Id” number. This dataset also includes multi-unit structures which have separate tax accounts for each unit, such as condominium units, represented as stacked polygon features. The parent parcel number [ParentTaxID] for the land parcel is distinguished from the child parcel [TaxMapID] for the condo unit. This data does not include mobile home data. Attributes include data stored within the Esri Fabric data model combined with those from the CAMA data. Examples of relevant attributes include:the [TaxMapID], [ParcelID] and [AprAccNum] can be used to uniquely identify each parcel. the [MailAddr1], [MailAddr2], [MailApt], [MailCity], [MailState], [MailZip] can be used as the full tax billing address for the owner.The [Owner1], [Owner2], [Owner3] describe the owner.the [YearBuilt] offers the oldest year a building was built on the property, reference this web map for info on potential lead pipes on premises;the area of the parcel in acres [GISSizeAC] as calculated from the parcel geometry and also the [deededAcres] from recorded documents, and ;the date that the parcel boundary was last edited [DATE_MODIFIED].How were parcels compiled? This layer was initially developed as an ink-on-mylar property maps maintained by the County from the early 1970's through around 2001.In the 1990s, the county procured services to convert parcels from source documents, however the product delivered in 2000 used a methodology which lost fidelity of source documents. Since then, county staff adhered to this same methodology in their daily work. Between 2001 and 2015 staff used an Esri topology to maintain parcel data in ArcMap. In 2015 the county migrated to Parcel Fabric (ArcMap) and then in 2021 to Pro (2.6/10.8.1 Enterprise) Parcel Fabric. In May of 2021 the county began outsourcing maintenance of parcel edits. This has worked well and was initiated in part to ensure a higher standard of editing practice was adhered to, but also to fulfil a shortage of skilled staff in the job market. County parcel mapping staff remain responsible for simple transactions (merge, split), compilation of materials to create vendor edit request task, and QC or review of vendor work. In Q4 2021, County Staff performed a needs assessment to review alignment issues between parcels and other layers and the internal business requirements for data alignment to parcels. They determined boundary layers must remain coincident with parcels, which are used in decision making by citizens and across many areas of government. Also, it was determined that our parcels had many errors from 20 years of edits in a non-Fabric data model and the previous editing practices. The county will be remapping parcels using ARP grant funding in the 2023-2024 timeframe. Upon delivery in 2024, data maintenance practices will ensure ongoing alignment with parcels.Year BuiltTo obtain the year built for structures on a property, use the 'Buildings' table available through our open data portal.Once you have downloaded the 'Buildings' table and this parcels layer, consider processing the building records in some way to join or perform a relate as there could be many buildings on one parcel, using the following fields:Parcel.AprAccNum = BuildingTable.PropertyID(Note: 98,227 parcels have 1 building, 647 parcels have 2 buildings, 272 have 3 or more)Data SchemaReview the Parcel schema document (PDF) to gain a better understand of the data fields. Access the file geodatabase source data in SC State Plane coordinate system

Access the file geodatabase source data in SC State Plane coordinate system

Adjacent county boundaries originally sourced from Esri data in the 2000s, but have been modified over time to best available data. Municipal boundaries are updated by York County staff when notified of annexations. Municipal boundaries may differ from parcel town tax code until CAMA records are updated.The county boundary may not yet reflect a surveyed boundary, the surveyed county boundary can be found here.This layer is maintained to be coincident with parcel and ORI (Police, Fire, EMS) boundaries. It is often used in court cases to resolve disputes over jurisdiction. As of February 2022, we have identified right of way discrepancies and need to review annexations for the last 5 to 20 years to ensure this layer reflects the intent of the documentation as approved by town councils.Access the file geodatabase source data in SC State Plane coordinate system

Note: When reviewing the comprehensive plan, add the layer 'Mixed Use Areas' to overlay on top of this. Also include layer Urban Services Boundary (USB, 2035).For more informationComprehensive Plan Update - 2022On March 6, 2023, the York County Council approved the update of York Forward. The process to develop an updated plan included a coordinated review of each goal and strategy with the Planning Commission. A series of community-wide open house meetings were held to define the purpose of each element, to recognize achievements made over the past five years, and to show proposed amendments. The effort resulted in a Plan that is relevant to current conditions, addressed changing needs of the community, and identified new key programs and partners to facilitate growth management initiatives. York Forward 2035 Comprehensive PlanFuture Land Use MapYork Forward 2035 - York County's Comprehensive PlanOn July 18, 2016, the York County Council approved the York Forward 2035 Comprehensive Plan. A Comprehensive Plan is best described as a guide to the County's future. It informs current and future decision makers where they are now, where they want to go, how they intend to get there, and who will help them along the way. The Comprehensive Plan provides the basis for York County's regulations and policies that guide its physical development. The plan establishes priorities for public action and direction for complementary private decisions.An important and overarching component of this planning effort was an inclusionary public engagement process. Understanding community values today ensures that this Plan, implemented in accordance with the recommendations, supports and advances those priorities over the long term. The effort was guided by an Advisory Committee appointed by County Council. Interviews with local stakeholders verified and supplemented the feedback received directly from citizens and property owners. Seven community meetings were held throughout the County to provide an opportunity to learn about the project, refine the goals and provide comments on the plan's components. Finally a project website was established as an additional opportunity for residents to access information and provide comments.The plan discusses opportunities and issues York County faces as it manages the rapid pace of growth while preserving the rural character of western area of York County. The Plan includes goals and strategies that address land use, economic development, housing, natural resources, cultural resources, community facilities and transportation. Access the file geodatabase source data in SC State Plane coordinate system

There are three Emergency Response Zone or ORI layers, Police or Law, Fire, and EMS used in unit recommendation when dispatching of emergency resources through a PSAP (Public Safety Answering Points, also known as 911 Call Centers) from a 911 call. Specific attributes dictate the order of emergency personnel to be sent as coded on run cards in a CAD software. The ORI layers were originally created between late 1990s and early 2000s.Police ORI includes attribute fields describing the responder or order of response, such as:During annexation, [PATBEAT] aids in determining the polygon to merge for a parcel, to better identify from/to attributes when populating the annexation tracking layer (web map).the CAD map uses the [BEAT_DESC] field for labeling (9/2023) and [] field for run cards.the date that the feature was created [DATE_CREATED] and last edited [DATE_MODIFIED].Through 2019, while using New World CAD system, Police ORI fields would be dissolved to produce 2 feature classes:the [BEAT_ID] and [BEAT_DESC] fields could be used to dissolve and produce a Police Beat Unit feature class.the [POL_ORI_ID] and [POL_ORI_DESC] can be dissolved to produce Police Station feature class.Annexations of parcels by municipalities are the most frequent business processes that require edits to be made. Occasionally, leadership reviews and reallocates resources over time as population growth or other factors necessitate rebalancing within a jurisdiction. At times, attributes are changed to improve specificity for an area to improve reporting (perhaps to evaluate call volume.)Polygons are edited to be contiguous (no gaps), encompass the road layer (always a polygon for the right-of-way), features do not overlap and remain coincident with parcel and jurisdiction boundaries. After migrating to the ArcGIS Parcel Fabric and evaluating layers that need to remain aligned during the maintenance of parcels, we established a need to better define maintenance practices. Between December 2021 and February 2022 the ORI layers and Jurisdiction boundary were aligned to parcels. Once parcel remapping completes in 2024, the layers will again be aligned to be coincident with parcels and there are plans to evaluate coincidence at each parcel edit to determine if an alignment edit is needed.Through 2019, while using New World CAD system, Fire ORI fields would be dissolved to produce 2 feature classes:the [Quad_DESC], [FIRQUAD] and [QUAD_ID] fields could be used to dissolve and produce a Fire Quadrants Unit feature class.the [FIRE_ORI_DESC] and [Fire_ORI_ID] can be dissolved to produce Fire Districts Station feature class.Through 2019, while using New World CAD system, EMS ORI fields would be dissolved to produce 2 feature classes:the [DISTRICT_DESC] and [DISTRICT_ID] fields could be used to dissolve and produce a EMS Districts Unit feature class.the [EMS_ORI_DESC] and [EMS_ORI_ID] can be dissolved to produce EMSStation feature class.Access the file geodatabase source data in SC State Plane coordinate system