My WebLink
|
Help
|
About
|
Sign Out
Home
EDA Packet 12.19.17
Hugo
>
Community Development
>
EDA
>
EDA Agenda/Packets
>
2017 EDA Packets
>
EDA Packet 12.19.17
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/7/2018 4:23:08 PM
Creation date
12/7/2018 3:03:50 PM
Metadata
Fields
Template:
Commissions
Meeting Date
12/19/2017
Document Type
Agenda/Packets
Commission Name
EDA
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
308
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Parkland <br />Using the standards identified in the 2008 plan and benchmarking <br />metrics from the National Parks and Recreation Association (NPRA), <br />shows that Hugo provides a significant amount of parkland, but that <br />the location of parkland does not necessarily serve residents in future <br />buildout of the City. <br />City Parks <br />According to NRPA standards, there should be one neighborhood park <br />per 5,000 people within 1/2 -'/4 mile of their home, and one community <br />park per 15,000 people within 2 miles of the residents. <br />Hugo today provides more parks per capita than the minimum <br />recommended number of parks for the total population of <br />Hugo, however, the parks are not necessarily located within the <br />recommended service areas. Hugo would need a total of 3.3 <br />neighborhood parks and 1.1 community parks to serve a population <br />of 16,900 (2020 population). If the population grows to 29,000 by <br />2040, the City will need a total of 5.8 neighborhood parks and 1.9 <br />community parks to meet the minimum NRPA standards for the entire <br />HUGO 2040 COMPREHENSIVE PLAN UPDATE <br />community. The City currently provides and manages 18 parks (13 <br />neighborhood parks and 5 community parks), not including open <br />space and regional parks. While the overall acreage of parkland, <br />exceeds the standards set by the NRPA, not all neighborhoods have <br />neighborhood or community parks within the recommended service <br />areas. As population increases in each neighborhood, the City should <br />acquire parkland in those neighborhoods to serve populations within <br />each neighborhood. <br />The 2030 Comprehensive Plan identified locational criteria and facility <br />needs for Community Parks. Since 2008, the City has acquired land <br />in locations that meet the locational criteria identified in the 2030 <br />Comprehensive Plan. A community park at Hanifl Fields with a multi- <br />purpose sports complex was constructed in 2011, the master planning <br />process for Lions Park in downtown has been completed, and the City <br />recently acquired land in Eastern Hugo for Irish Avenue Park. The <br />location of these parks meets the service area needs for the eastern <br />and southern parts of the City. However, the community is still lacking <br />a community park in the northwest corner of the City. Therefore, Map <br />xx — Neighborhood Service Areas, shows a Community Park Search <br />Area in the northwest corner of the City. It is the City's policy that each <br />neighborhood should have parks that serve residents to this standard <br />and that neighborhood and community parks may meet the service <br />area need of the population. Table 6.5 — Parks Servicing Neighborhood <br />Service Areas shows the minimum number of parks needed to serve <br />the population in each neighborhood. <br />As noted previously, the NRPA is moving away from the minimum <br />standards of service, as findings indicate that each City has unique <br />needs. Therefore, if more parkland than the minimum standards is <br />required to serve the population in each neighborhood, the City may <br />acquire land that to meet this need. <br />PARKS, TRAILS AND OPEN SPACE 138 <br />
The URL can be used to link to this page
Your browser does not support the video tag.