An address point represents a geographic location that has been assigned an address by the local address authority (i.e., county or municipality) but does not necessarily receive mail from the US Postal Service (USPS). Address points may include several pieces of information about the structure or location that’s being mapped, such as:[WHOLE_ADDRESS] the full address (i.e., the USPS mailing address, if the address is for a physical location [rather than a PO box]);the type of unit [UNIT_TYPE] and unit [UNIT];the city or zip community [POST_COMM] and ZIP code POST_CODE;the vacancy status (occupied, vacant, meter) [OccupiedUseStatus]; andthe date that the address point was created [DATE_CREATED] and last edited [DATE_MODIFIED].These data were originally created for Public Safety e911 response in 2001 through field survey by county staff and is mapping grade. Today it is used throughout the County and by the public to conduct business and assist in decision making. This feature service is updated daily from its source ArcGIS Enterprise feature class. Source data within an Enterprise Geodatabase is accessed by County and City of Rock Hill staff through ArcGIS Server and Portal. When edited, business rules are enforced by BCS theAddresser software. York County has an Address Manual used by staff and stakeholders to ensure quality and standards are adhered to during maintenance and use.These data are shared through open data and available for download. York County addresses are included in the National Address Database (USDOT NAD). The NAD is consumed by Google as highlighted in their Maps Content Partners 2022 November Newsletter. York County is one of 13 counties added in 2022. Access the NAD through the ArcGIS Online Living Atlas.As of October 2022, the schema of these data are compatible with NG911. Previous schema remains as of January 2023 with intent to remove fields tentatively planned for 2024. Review the schema field mapping document (PDF) to gain a better understanding of field mapping used to transition these data to NG911 standards.

Road segments within this layer represent centerlines of public and private (not gated) roadways. Road segments define left (_L) and right (_R) side attributes and address ranges along the segment. Additional attribute information may include:The full street name ST_DIR_NAM;the city or zip community [POSTCOMM_L]; The ZIP code POSTCODE_L; The jurisdiction (Incorporated Municipality) the segment is within [INCMUNI_L];The functional classification [F_CLASS] used; (ex: Interstate, Major Collector, Minor Arterial, Local)The route number [RT_NUM] containing a county road or highway number;The road maintenance provider or construction status [ST_OWNER];Fields used in routing [MPH, ONEWAY, _ELEV, _IM] and; the date that the road segment was created [DATE_CREATED] and last edited [DATE_MODIFIED].This information is was originally compiled from orthophotography in 2001 for use in Public Safety e911 response. Today it is used throughout the County and by the public to conduct business and assist in decision making.County and City staff update records daily or as needed (such as through subdivision plan review and approval using georeferenced CAD files provided by land developers). The road centerlines support address geocoding, analysis, routing and mapping.The centerline represents the geographic location on the roadway between both shoulders (physical center), which often, but not always coincides with the center painted line dividing bi-directional travel lanes. Roadway centerline data plays an important role in transportation management and planning, while also being the basis for all other roadway-related data products.This feature service is updated daily from its source ArcGIS Enterprise feature class. Source data within an Enterprise Geodatabase is accessed by County and City of Rock Hill staff through ArcGIS Server and Portal. When edited, business rules are enforced by BCS theAddresser software. York County has an Address Manual used by staff and stakeholders to ensure quality and standards are adhered to during maintenance and use.For additional information about county maintained roadways, review the County Road Inventory data or search for data through One Map. County staff maintain the relationship between streets and the County Road Inventory through the RT_NUM field. The street ownership [ST_OWNER] designation serves as a source to determine the maintenance provider by municipal public works agencies who actively manage the road assets. SCDOT roadways can be confirmed by reviewing data within their lookup application or their source data within our One Map application.Railroads are contained within the streets feature class to enable cross street lookup (geodcoding), a requirement for e911 dispatchers.Street segments outside the county are present for cartographic and Public Safety dispatch of nearest vehicle (routing) purposes. These can be filtered out and removedAddressing data (streets and addresses) are used to update the US Census Bureau Tiger data in support of the decennial census. As of October 2022, the schema of these data are compatible with NG911. Previous schema remains as of January 2023 with intent to remove fields tentatively planned for 2024. Review the schema field mapping document (PDF) to gain a better understanding of field mapping used to transition these data to NG911 standards. Continuing NG911 compliance projects include splitting the centerline as they cross the city limit. To assist York County, South Carolina in the maintenance of the data, please provide any information concerning discovered errors, omissions, or other discrepancies found in the data. Data Owner: County IT/GIS, Addressing Staff and City of Rock Hill.Access the file geodatabase source data in SC State Plane coordinate system

Meeting minutes from January 9, 2023 where these boundaries were approved can be found here.Town staff has been working with the South Carolina Revenue and Fiscal Affairs office (SCRFA) to study and plan for the redistricting of the Town Council’s wards based upon the results of the 2020 Decennial Census. SCRFA first developed a Redistricting Benchmark Report, which staff presented to Council on March 14, 2022. The report outlines the current demographics of the existing Council ward geographies and discusses the path forward to developing a new ward map. After receiving input, staff reached back out to SCRFA to begin the process of developing a draft map for public review. The draft map is attached. The map was developed utilizing the following traditional redistricting principles:Wards will be drawn contiguously, so that all parts of the district or ward are connected to each other. Wards will be drawn to minimize the division of voting precincts. Wards will be geographically compact to the extent practicable, such that nearby areas of population are not bypassed for a more distant population. Wards will be drawn to comply with other applicable court decisions and federal and state laws. Wards will be drawn, when feasible, with respect to existing districts and communities of interests, which will require input from Council and the citizens.Wards will be drawn to give careful consideration to minority districts for compliance with Section 2 criteria of the Voting Rights Act Wards will be drawn to a deviation range of 5%The adoption process follows the normal ordinance adoption process, which requires two readings and one public hearing. The public hearing is tentatively set for Council’s first meeting in January.

On April 3, 2023, after consulting with addressing staff to evaluate workflow and processes related to annexations, we determined that this zip code layer was never intended to be a true representation of postal service zip code. Instead, this layer represents the MSAG community. During an annexation, as a street is consumed by a city jurisdiction boundary, its MSAG equivalent range receives a new ESN and Community designation. With MSAG, the ESN + Community designation are intended to be the components relating back to a GIS street centerline segment. Decades ago when the PSAP call routing was first established, this layer was established to aid in assigning the community value placed on MSAG street segment equivalents.As of April 2023, the street and address layers have a zip code and zip community value assigned. These are based on the MSAG zip code layer maintained by York county, which were developed from postal service zip code route delivery areas decades ago, but are now maintained only for MSAG community assignment. At some point, possibly once York County migrates to NG911 in 2024-2025 and MSAG becomes obsolete, we may need to update our MSAG zip code values to reflect the true postal service route delivery boundary.Access the file geodatabase source data in SC State Plane coordinate system

The primary use is for e911 public safety dispatch, if a call comes in the dispatcher can review this layer as a guide to look up and then call the provider to have electricity turned off. In January 2022, electric companies (York Electric and Rock Hill) provided indication of service by parcel (presence of an electric meter). The Duke Energy parcels were selected from those unassigned by the other providers, but within the service area regions they provided May 2022. This layer was last updated June 8, 2022 using the more accurate data provided by Duke Energy. Fields were reworked in 2022. There is now a secondary provider attribute that can be populated to suggest the alternative provider for a region, when the area is unknown. This was provided based on the region, for example, if near Rock Hill, the providers might be CRH / YEC / DUKE, if elsewhere, YEC/DUKE are the probable providers. The only exception is the lower left corner near the Broad River, which is Lockhart Power.There may be a small number of properties that are served by multiple service providers, however these are unknown. YEC suggests these are large properties and maybe no more than 3.Annexations in the City of Rock Hill with empty lots become Rock Hill customers. If Rock Hill annexes Duke Energy customers, they remain with Duke Energy. Providers don't appear to communicate between each other about their areas of service. Service areas don’t appear to be regulated.Future updates should take place yearly or at every two years based on the amount of growth.Future updates could focus on areas unknown or may use a different methodology.A note about the Duke Energy Service Area:Duke Energy's Service Area in York County was derived by buffering all of the primary and secondary distribution conductors by 300ft. That buffer was then used to select parcels that intersect with the buffer. Lastly, those selected parcels were dissolved into a single polygon layer and a single record. This process was generated on 5/25/2022. The data product was reviewed internally and released. The information product provided by Duke Energy is not presented in this data, instead it was used to select parcels within the areas provided and assign those as being served by the provider.++++Description last updated 6/8/22++++Access the file geodatabase source data in SC State Plane coordinate system

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

Hydrants are part of the water systems maintained by various entities in York County. They are primarily serviced by the fire agency within the jurisdiction the hydrant is found in. The hydrants are provided to 911 dispatchers for use during an emergency, to relay nearest and best available to vehicles while on route to call. Apps and web maps:Hydrant Search, report for each hydrant, report by districtWeb map for Hydrant SearchFire hydrants within the County jurisdiction are inspected and maintained by York County Fire staff. Access to maintain hydrants in cities by City staff has been granted in previous years (using map service functionality, users are restricted from editing hydrants they did not create). At end of year, for ISO to use during their review, a report by district is obtained. This report is available for each district through the hydrants app. Having inspection reports yearly results in max points. Typically, once all hydrants in a district have been inspected in a year, the report is printed and stored for ISO to reference. County Fire staff also capture a shapefile of the hydrants yearly, from the open data site.630 INSPECTION AND FIRE FLOW TESTING OF HYDRANTS:A. Inspection (HI):Inspection of hydrants should be in accordance with AWWA manual M17, Installation, Field Testing, and Maintenance of Fire Hydrants. The frequency of inspection is the average time interval between the 3 most recent inspections.Assign points for frequency of inspection (FI) according to the following:Frequency of Inspection (FI) Points1 year 302 years 203 years 104 years 55 years or more No creditAccess the file geodatabase source data in SC State Plane coordinate systemUpdate History:3/6/24 - first draft

Data acquired from the City of Rock Hill (June 2020). The City of Rock Hill studied all of the creeks upstream of the FEMA zones to a drainage area of 0.1Sq. miles.ESP & Associates defined the flood prone areas (100 year) for Taylors and Wildcat.Keck & Wood defined the flood prone areas (100 year) for Manchester, Tools Fork, and Waterford.Data was compiled into one feature class by the City of Rock Hill City Engineer (DD) around 2016.Access the file geodatabase source data in SC State Plane coordinate system

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

To view this map and search for a road in context of an application, visit One Map, click on search roads or click here to access directly.Note: This AGOL View item has 11 fields hidden.(Replaces HFV)Access the file geodatabase source data in SC State Plane coordinate system

July 2023 - Esri now hosts this as a Living Atlas layer. This 146MG copy of the data can be decommissioned.+++This layer represents the NHD Flowline, its a copy downloaded from the USGS NHD, however it is unknown when this copy was made or last updated (likely well before 2017 since there is no last edit date.) A copy is hosted in support of Planning Department related business processes (Stormwater, Environmental Compliance). The source could be updated from USGS through this link. Since this data product is owned by the USGS, this item should be used only when their resource is unavailable. Web maps should reference these resources, NHD Plus High Resolution, from this URL resource, the metadata describes it as:The USGS NHDPlus High Resolution service, NHDPlus_HR, a part of The National Map, is a comprehensive set of digital spatial data comprising a nationally seamless network of stream reaches, elevation-based catchment areas, flow surfaces, and value-added attributes that enhance stream network navigation, analysis, and data display. NHDPlus High Resolution (NHDPlus HR) is a scalable geospatial hydrography framework built from the high resolution National Hydrography Dataset, nationally complete Watershed Boundary Dataset, and 3D Elevation Program (3DEP) ? arc-second (10 meter ground spacing) digital elevation model data. The National Map download client allows free downloads of public domain NHDPlus HR data in Esri File Geodatabase format. For additional information on the NHDPlus HR, go to https://nhd.usgs.gov.There is a cached, updated yearly NHD dataset found at this URL.FCode defines the symbology, the codes can be found at this resource.Access the file geodatabase source data in SC State Plane coordinate system

This item view references FloodZone layer and displays 100 and 500 year flood boundary categories.The S_Fld_Haz_Ar table contains information about the flood hazards within the study area. A spatial file with locational information also corresponds with this data table. These zones are used by the federal Emergency Management Agency (FEMA) to designate the Special Flood Hazard Area (SFHA) and for insurance rating purposes. These data are the flood hazard areas that are or will be depicted on the Flood Insurance Rate Map (FIRM). A spatial file with locational information also corresponds with this data table. Source DFIRM: S_FLD_HAZ_ARThis layer was download from the FEMA Flood Map Service Center (latest study effective date of 5/16/2017)To download, use the following; State: SC, County: York County, Community: [select any]Direct Link to download source (working as of 10/10/2022)Access the file geodatabase source data in SC State Plane coordinate system

** THIS IS NOT THE MOST CURRENT FLOOD HAZARD MAP **This data has been replaced by the Flood Hazard Zone Areas (DFIRM 2017) [or more recent]This layer contains information about the flood hazards within the study area, specifically the floodway, defined by an attribute filter. These zones are used by the Federal Emergency Management Agency (FEMA) to designate the Special Flood Hazard Area (SFHA) and for insurance rating purposes. These data are the regulatory flood hazard areas that are or will be depicted on the Flood Insurance Rate Map (FIRM). The spatial elements representing flood zones are polygons. There is one polygon for each contiguous flood zone designated. Source DFIRM FC: S_FLD_HAZ_ARThis layer was download from the FEMA Flood Map Service Center (study effective date of 2008)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