Reference boundaries of Cleveland neighborhoods, which also referred to in some contexts as "Statistical Planning Areas" or SPAs.The City of Cleveland's neighborhoods were updated last in 2012 and include 34 neighborhoods:Bellaire-PuritasBroadway-Slavic VillageBrooklyn CentreBuckeye-Shaker SquareBuckeye-WoodhillCentralClark-FultonCollinwood-NottinghamCudellCuyahoga ValleyDetroit ShorewayDowntownEdgewaterEuclid-GreenFairfaxGlenvilleGoodrich-Kirtland PkHopkinsHoughJeffersonKamm'sKinsmanLee-HarvardLee-SevilleMount PleasantNorth Shore CollinwoodOhio CityOld BrooklynSt.Clair-SuperiorStockyardsTremontUnion-MilesUniversityWest BoulevardData GlossarySPA - SPA numeric idSPANM - Neighborhood nameSQ_MILES - Area in square milesUpdate FrequencyMaintained and managed in an enterprise geodatabase. Updated if neighborhood information changes.ContactCleveland GIS

TO VIEW AND DOWNLOAD THE ACTUAL DATA, CLICK ON ONE OF THE LAYERS BELOWPolygon layer containing American Community Survey (ACS) 5-Year Estimate data for the most recent vintage. 5 year estimates are a rolling average of data from the past five years. The current vintage is for 2018-2022. Data is filtered for Cuyahoga County, OH, and additional calculations are performed to determine the city each census tract lies within. Therefore, this dataset is filterable for the city of Cleveland and its surrounding suburbs. To learn more about each of these datasets, click on one of datasets under "Layers". This dataset powers the City Census Viewer.This dataset is ported from the ArcGIS Living Atlas.Data GlossaryClick here, then click on "Fields" to view documentation. Use the "Layers" drop down to view documentation for different tables.Update FrequencyThis dataset is updated annually in December when the new ACS vintage is released.ContactsSamuel Martinez, Urban Analytics and Innovationsmartinez2@clevelandohio.gov

TO VIEW AND DOWNLOAD THE ACTUAL DATA, CLICK ON ONE OF THE LAYERS BELOWThis was created in late 2021 using the Census Bureau's redistricting PL 914 171 dataset. The block-level data is the official release of Census results which comes in a text format that requires processing via R or other statistical software. City Planning (Dro Sohrabian) ran analysis of the Census results by aggregating by city neighborhoods and comparing to 2010 results so the City and others can understand how the City's demographics changed from 2010 to 2020.DocumentationClick here, then click on "Fields" to view documentation.Update FrequencyNeverThis dataset is featured on the following app(s):Census 2020 in Cleveland Story MapTransit Oriented Development in ClevelandContactsCleveland City Planning Commission, Zoning & Technology

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. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

U.S. Census Block GroupsThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), displays Census block groups in the 50 states, the District of Columbia, and Puerto Rico. Per the USCB, "Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas".Block Group 2 - Census Tract 010400 (Santa Fe, NM area)Data version: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Census Block Groups) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 70 (Series Information for Block Group State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (U.S. Census Block Groups - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: What are census blocks?For feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

Boundary layer of the service area for City of Cleveland Water. Cleveland Water service area contains all of Cuyahoga county and some areas in surrounding counties. The surrounding counties are: Geauga, Medina, Portage and Summit.Data GlossaryClick here, then click on "Fields" to view documentation.Update FrequencyMaintained and managed regularly by Cleveland GISContactCleveland GIS

Working with several partners, including the Cleveland Metroparks and the Chagrin River Watershed Partners, the Cuyahoga County Planning Commission (CCPC) developed a predictive series of buffer areas - areas to be preserved for protection - around various types of water features highlighted in the map. The methods utilized are patterned on well-established modeling approaches and use a particular feature's drainage area to delineate its buffer or active stream area.The maps show buffered water areas, by feature, as determined by the CCPC:Lake Erie Shore: 300 feet bufferNavigable River (Cuyahoga): 300-foot bufferNavigable River (Chagrin, Rocky): 120-foot bufferStream Bank (Larger Watershed): 120-foot bufferStream Bank (Smaller Watershed): 75-foot bufferPonds, Lakes, Other Water bodies: 120-foot bufferWetland (National Wetland Inventory): 120-footWetland (Soil and Water Inventory): 120-footSmall Stream Centerline: 25 foot bufferWhen viewing these modeled buffer areas on the map, users can click within any given buffer area and "View Details" to see the reasoning behind that particular buffer area size.Note: These riparian buffers were generated only for above-ground water features and exclude culverted portions streamsVintage:2024Data Sources: Cuyahoga County Planning Commission, Cleveland Metroparks, Chagrin River Watershed PartnersCoverage: Cuyahoga CountyUpdate Frequency: Not Regularly UpdatedLast Update: August, 2024

The Redcar and Cleveland Web Mapping Service (WMS) displays geographically maintained or monitored areas in the borough of Redcar and Cleveland. Numerous layers have been created for the map display and represent the extents of certain environmental, historical and regulated areas managed by Redcar and Cleveland Borough Council

Data from City of Cleveland Public Safety's Computer-aided Dispatch (CAD) system on calls for Cleveland Division of Fire service. Includes information on call time, priority, type, and location.Data starts with calls from 2021 onwards. The data provided is the latest available information and is updated regularly as statistics change.Disposition Type refers to the first disposition code, which is the code determined by Division of Fire after arrival on scene.Map points show approximate locations of Fire calls for service, including 911 calls. Locations are adjusted to the nearest road, and full addresses are not provided to protect individual privacy.Update FrequencyDaily around 8:30AM EasternRelated data item(s):Fire Calls for Service DatasetFire Calls for Service DashboardContactsCity of Cleveland, Division of FireInstructionsZoom into an area of the city you are interested in.Search for an address to zoom to that location.Filter by call date or call disposition type.Use the map layers tool to add wards or neighborhoods to the map.Use the advanced query tool to view calls within a certain distance of a point or area.

Crime incidents starting with incidents reported in 2016. Note: crimes that occurred before 2016 are included if the date reported was in 2016 or later. The data provided is the latest available information and is updated regularly as statistics change. For access to comprehensive reports, kindly submit a public record request by clicking here. This dataset is featured in the following app(s):Cleveland Division of Police Crime DashboardCrime Incidents MapThe City strives to provide the highest-quality information on this platform. The content on this website is provided as a public service, on an ‘as is’ basis. The City makes no warranty, representation, or guarantee of any type as to the content, accuracy, timeliness, completeness, or fitness for any particular purpose or use of any public data provided on this portal; nor shall any such warranty be implied, including, without limitation, the implied warranties of merchantability and fitness for a particular purpose. The City assumes no liability by making data available to the public or other departments. Update FrequencyDaily around 8AM ESTContactsCity of Cleveland, Division of PoliceData GlossaryColumn | DescriptionPrimaryKey | Unique identifier of the incident.CaseNumber | Identifier to reference the case linked to the incident. Multiple incidents can have the same CaseNumber.District | Police District of occurrence selected by the reporting OfficerUCRdesc | Uniformed Crime Report Offense DescriptionYearReported | The year the crime was reportedTimeGroup | Time Grouping for Statistical comparisonReportedDate | The Date the Crime was reportedMonth1 | The Month the Crime OccurredDay1 | The Day of the Month that the Crime OccurredTimeBlock | Crime Time of Day Group, between 0-6=Night,6-11=Morning,11-19=Day,19-24=Early NightDOWname | The Day of the Week the Crime Took placeDOW | The Day of the Week the Crime Took placeHourofDay | The Hour of the Day that the Crime Took PlaceDaysAgo | The amount of days ago that the crime took placeOffenseDate | The Date the Crime occurredStatute | The Criminal Statute Selected by the Reporting OfficerCity | The City of the Crime used for the RMS systemZip | The Zip of the CrimeAddress_Public | The address of the incident. The final digits of the house numbers are redacted to preserve anonymity.WARD | The ward in which the incident occurred.CENSUS_TRACT | The name of the census tract in which the incident occurred.CENSUS_TRACT_GEOID | The GEOID of the census tract.CENSUS_BLOCK_GROUP | The census block group in which the incident occurred.CENSUS_BG_GEOID | The GEOID of the census block group.CENSUS_BLOCK | The census block in which the incident occurred.CENSUS_BLOCK_GEOID | The GEOID of the census block in which the incident occurred.LAT | The latitude of the incident, snapped to the nearest street.LON | The longitude of the incident, snapped to the nearest street.

Data from City of Cleveland Public Safety's Computer-aided Dispatch (CAD) system on calls for Cleveland Division of Police service. Includes information on call time, priority, type, and location.Data starts with calls from 2021 onwards. The data provided is the latest available information and is updated regularly as statistics change.Call times are shown in your local time zone, but are converted to UTC when you download the data.Map points show approximate locations of police calls for service, including 911 calls. Locations are adjusted to the nearest road, and full addresses are not provided to protect individual privacy. Update FrequencyDaily by 8:30 AM EasternThis dataset is featured in the following app(s):Police Calls for Service DashboardPolice Calls for Service Map ViewerContactsCity of Cleveland, Division of PoliceFor more information, visit the City's Police webpage.Data GlossaryColumn | Descriptioncall_datetime | Timestamp for when call was placedcensus_block | The census block where service was neededcensus_tract | The census tract where service was neededdispo_descriptions | Disposition codes related to a specific calleid | ID for the datasetfirst_dispo_eng | The first disposition code related to a specific calllatitude | Latitude where service was needed, snapped to the nearest streetlongitude | Longitude where service was needed, snapped to the nearest streetpolice_district | Police district where service was neededpriority | The priority level of the call, typically between 1 and 5, 1 being highest priority and 5 being lowestsub_eng | Typically "1M" or "2M" which identifies if it was a 1-man or 2-man dispatchtyp_eng | Type or category of callward | Ward where service was neededzip | The zip code where service was needed

1.1 In May 2018, Redcar & Cleveland Borough Council adopted the Redcar & Cleveland Local Plan. This plan sets out the visions and overall development strategy for the borough (outside of the North York Moors National Park) and how it will be achieved over the plan period until 2032. It forms part of the statutory development plan for the borough and is used to direct decisions on planning applications and to provide a spatial planning framework for the many plans and strategies prepared by the Council.1.2 The Local Plan replaces the Local Development Framework, including the adopted Core Strategy and Development Policies Development Plan Documents (DPDs) and the Saved Policies of the Redcar & Cleveland Local Plan (1999). 2. Adopted Policies Map2.1 Policies Maps provide a geographic illustration of the policies within the adopted development plan. The previous Proposals Map for the borough had been prepared to represent the policies of the Core Strategy and Development Policies DPDs and was adopted in September 2007.2.2 The Proposals Map has now been replaced by the Local Plan Policies Map (May 2018) in order to reflect the adoption of the Redcar & Cleveland Local Plan (May 2018) and the Joint Tees Valley Minerals and Waste Development Plan Documents (Sep 2011).2.3 The Policies Map illustrates the site specific policies, allocations and designations of the adopted development plan and relates to the area of the borough that lies outside of the North York Moors National Park. Further details about the Policies Map and the development plan can be found at www.redcar-cleveland.gov.uk 3. Disclaimers3.1 Contains Ordnance Survey data © Crown Copyright and database rights 2018 (100019983).3.2 The information shown on the Local Plan Policies Map is accurate to the best of the knowledge of Redcar & Cleveland Borough Council at the time of publication.

3.3 Some parts of the borough fall within consultation zones for the Health and Safety Executive, the Civil Aviation Authority and the Environment Agency. Please note that these zones are not shown on the Policies Map. For further details regarding these zones, please contact Development Services or the relevant agency directly.

The Department of Public Works Division of Street Maintenance's leaf pick-up program focuses on high-generation areas, defined as areas with the highest concentration of city-owned tree lawn trees, potentially causing hazardous conditions or flooding.Leaves collected from high-generation areas will be transported to an approved leaf compost site, diverting 2,000 tons of leaf material from the waste stream.The division will systematically deploy sweepers, leaf machines, end loaders and leaf blowers in these areas over the course of the program. High-generation areas have been vetted by streets supervisors in partnership with Urban Forestry, the Cuyahoga County Tree Canopy and the Mayor’s Office of Sustainability. Leaf pick-up signage will be posted one week in advance of service being provided to allow residents in that area time to move collected leaves to the tree lawn. Signage will also be posted in neighborhoods to remind residents not to park on the street on leaf collection days. Residents are reminded never to rake leaves into the street, where they may clog sewers, create hazards for traffic and cyclists, and affect snow and ice control. Residents in all areas of the city may bag leaves and place bagged leaves out with their trash on their regular waste collection day. Residents who bag leaves may set out 20 leaf bags with their trash for the duration of leaf collection season. Based on volume and weather conditions on collection day, residents’ trash may be picked up first, followed by bagged leaves. Residents may also opt to ‘leave the leaves’ or turn them into mulch by mowing over leaves and chopping them into small pieces to use in their home gardens and landscapes. Update FrequencyStaticContactsCity of Cleveland, Dept. of Public Works, Division of Streets

This layer shows demographic context for senior well-being work. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. The layer is symbolized to show the percentage of population aged 65 and up (senior population). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B01001, B09021, B17020, B18101, B23027, B25072, B25093, B27010, B28005, C27001B-IData downloaded from: Census Bureau's API for American Community Survey Date of API call: December 7, 2023The United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2022 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.