Laserfiche WebLink
Document management portal powered by Laserfiche WebLink 9 © 1998-2015 Laserfiche. All rights reserved.
Open Space Advisory Board <br />Minutes <br /> February 12, 2020 <br />Page 2 of 4 <br /> <br />these were total sites, some of which were taken. David and Jessamine asked for and <br />received some clarification about the memorial bench program. <br /> G. Ember passed out the board contact list for the city. <br /> H. See further Staff Updates on page 5 of the meeting packet. <br /> <br />6. Board Updates <br /> None <br /> <br />7. Public Comments on Items Not on the Agenda <br />Kelly Bartell (563 West Cedar Place) came to the meeting because she wanted to hear about <br />the biodiversity study (Agenda Item VIII). She lives adjacent to North Open Space and doesn’t <br />see much biodiversity and wildlife there and she would like to see it increased. She added that <br />in the summer she hears lots of crickets and frogs and at some point in the summer it <br />suddenly “goes quiet,” and she finds that alarming. Helen commented that the board has <br />prioritized resource management and is very interested in good scientific practice of this <br />information. Ember clarified that on North Open Space all weed control is spot-spraying (single <br />plant) rather than broadcast spraying. Charles suggested the sudden silence could do with <br />ditches running dry. Nathan and Ember added that they didn’t know of any mosquito spraying <br />on the property and that it would always include notification, but said they’d look into it further. <br /> <br />8. Open Space Biodiversity Database. Presented by Steve Roels, Senior Natural Resource <br />Specialist (see page 9-14 of the meeting packet) <br />Steve is originally from Michigan. He has worked for a land trust doing conservation easement <br />work. He has his Master’s Degree from University of Kansas studying milkweeds and his PhD <br />from Michigan State where he focused on restoration ecology of birds in Panama. <br /> <br />He is currently working on a database to consolidate and format all existing records and <br />studies for the Louisville Open Space properties. He shared the basic structure of the <br />database and his process and he explained how a relational database makes the existing data <br />searchable, updatable, and much more valuable. <br /> <br />He gave a summary of what species are on our Open Space land and considered the data’s <br />context and sampling bias (both by location and by taxonomy). He also summarized the sort of <br />data and information he has already amassed. He also gave examples of how this database <br />can be used and the division plans for the future. One plan is the integration of citizen science <br />data into the database. He has already figured out how to upload citizen scientist data from <br />iNaturalist and eBird on City properties. Laura said she was very excited about this work. <br />Charles suggested an app called Seek. Steve will present to the public about citizen science in <br />the fall. Helen suggested a learning guide for the tools so citizens can learn to use it. Peter <br />asked if the database will be publically accessible, suggesting it could be popular for citizens <br />and valuable for stake holders. Steve pointed out that there could be implications for sensitive <br />species. Ember said there could be a summary-type document produced at the end of the <br />year. David commented that Steve collaborate with neighboring communities. He added that <br />he would be interested in having Steve’s input on our assessment/acquisition process. <br />Nathan asked if there are ways to do biodiversity surveys without trespassing on private land. <br />Steve suggested there were some ways to infer certain things about plant communities from <br />satellite imagery. Jessamine was hoping for another update from Steve in the fall. Helen <br />added that the database should be the new standard for any future contracting work. <br /> <br />9. Discussion Item: Discuss and Approve OSAB 2020 Goals (see pages 16-18 of the <br />Meeting Packet) <br />3