|
Lexington Home Page
|
Help
|
About
|
Browse
Search
2015-10-26-GCC-min
Breadcrumb Navigation:
TownOfLexington-Public
>
WEB PUBLISHED-PUBLIC DOCUMENTS
>
MINUTES-REPORTS-COMMITTEES ARCHIVE
>
Greenways Corridor Committee-GCC
>
Minutes
>
2011-2019
>
2015
>
2015-10-26-GCC-min
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/2/2019 6:18:17 PM
Creation date
12/1/2015 1:56:07 PM
Metadata
Fields
Template:
Archives
Keywords or Subject
Minutes - GCC - Greenways Corridor Committee
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
2
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
Keith had a large map with potential future routes mapped out. We discussed <br />naming procedure and agreed to continue with letters, labelling routes chronologi- <br />cally as opposed to geographically (i.e. routes will not necessarily be alphabetically <br />contiguous). <br />New Business: <br />Discussion of moving meeting location to new Community Center ended in a deci- <br />sion to remain at Hadley DPW location <br />Regarding the East Lexington Corridor Improvement Project, we agreed to take <br />the basic position that any changes/upgrades should take bicyclists and pedestri- <br />ans into consideration and make travel safer for them as well as safer for cars. <br />Keith will draft a letter and circulate for edits. <br />Next Meeting <br />: November 23, 2015, 4:30-6:00pm, DPW Training Room <br />Future meeting dates: December 14 <br />Future Agenda Items: <br />- <br />Certification of ACROSS Lexington Completion program update - Gil Benghiat <br />- <br />Easement/Town Access Project <br />- <br />Expenditure of FY16 monies - Keith <br />Respectfully Submitted by <br />Alexandra Dohan, Secretary <br />
The URL can be used to link to this page
Your browser does not support the video tag.