This dashboard is under review, please contact data.analytics@cincinnati-oh.gov if you have any questions regarding this dataset and dashboard. 
Neighborhood Operations Division (NOD), a division of the Department of Public Services (DPS) is responsible for maintaining a large portion of visible city-owned property.  Using the city's Greenspace Maintenance Plan, NOD cleans and maintains city green spaces, areas in the right-of-way (ROW), steps, public fences, bridge underpasses, guardrail buffers, alleys, walls, concrete islands and lots owned by or in the care of DPS (includes mowing, weed spraying, and litter pick-up).  Grass cutting occurs April through November: the Department provides a schedule listing the tentative dates for cleaning neighborhoods' green spaces and other related neighborhood cleanup projects.

While the Greenspace Maintenance Plan covers work that the City does to proactively maintain clean neighborhoods,  DPS also responds to citizen service requests (CSRs) for litter, tall grass/weeds, and dumping on both public and private property (for more information on private property cleaning, see Private Lot Abatement Program).  The above visualization shows all green space cleaning/abatement activity in response to CSRs.
How to use this dashboard:
The greenspace citizen service requests dashboard provides a high-level overview of all service requests created and closed. Users can filter projects based on:
1.     Neighborhood: Depending on what neighborhood is selected (Community Council or SNA Neighborhood) users can select particular neighborhoods by clicking on the drop-down menu on the top right side. By default all neighborhoods are selected.
2.     Year: Based on the calendar year when the service was first created and closed. To filter by year adjust the slider on the top left side. By default all years are selected.
Users can view Service Requests by Community Council or SNA Neighborhood by clicking on the upper left buttons to switch between neighborhoods. For an explanation on the differences between the two neighborhoods please read the definitions in the definition section down below.
Users can also interact with the by request or by neighborhood button to view individual or grouped service requests (by neighborhood).
To navigate to performance measures for closed service requests please click the arrow on the top right side of the dashboard. To return to service requests created click on the back arrow on the top left side of the dashboard.
Definitions:
Created: The number of SRs created between the start and end date.
Closed: The number of SRs that are closed that were created between the start and end date.
Open: The number of SRs that are currently open that were created between the start and end date.
Avg. Days Open (For Open SRs): For all SRs that were created between the start and end date and are currently open, the average number of days they have been open.
Avg. Days to Close: For all SRs that were created between the start and end date and are closed, the average number of days between the date created and date closed.
% Satisfied: The satisfaction rate for SRs that were created between the start and end date and are closed (Note: not every closed SR receives an email, they are randomly sent by the system).
Community Council: Nonprofit voluntary organizations that weigh in on city matters, but exist separately from the city government and follow different rules. Each neighborhood council has defined its own border which, in some cases, are not in agreement with other contiguous neighborhood boundaries resulting in areas of overlap within the layer. The City of Cincinnati does not intervene or mediate on these boundary discrepancies.
SNA (Statistical Neighborhood Approximations) Neighborhoods: Cincinnati neighborhoods based on the US Census Data and American Community Survey five-year estimates. The boundaries are redrawn every ten years following the Census.