Quantcast

Trustees moving forward with paid parking lot for Lincklaen Street

— The new public parking lot at 22 Lincklaen St. will likely charge money for parking, the village board revealed at a special meeting last week.

The May 28 meeting was scheduled to close-out the year-end budget books, which included paying the village’s final bills for the 2012 fiscal year and transferring money between various accounts.

“The good news is we’ll begin the new fiscal year in a healthy place,” Mayor Kurt Wheeler said after the board had approved all the final fiscal moves.

Because the village budget is healthy and has higher-than-expected cash reserves, the village is now in a “financially-viable position” to move forward with the purchase of a parking lot pay station for the 22 Lincklaen St. lot, Wheeler said.

The board has been discussing for months whether or not the new 22-space parking lot next to the post office should be a paid or free lot, and, if it were to be a paid lot, how much it would cost the village to purchase a pay station and get it up and running.

At the board’s May 14 regular meeting, Trustee Peggy Van Arnam, who is on the parking committee and has been spearheading the Lincklaen lot project, said the best price she had found for a pay station was $14,700. At that meeting, Wheeler suggested the board wait to see the outcome of its May 28 budget close-out meeting to further discuss the option.

On May 28, Van Arnam said she felt after further research that leading a pay station was not a fiscally logical idea, and that the vendor for the pay station had reduced the price below the previous $14,700 number. She said if the village uses its own employees to install the station that would further lessen the cost. She asked the board to make a decision that night on whether or not to move forward with the pay station option, saying they would not have to actually spend the money until the project was ready.

0
Vote on this Story by clicking on the Icon

Comments

Use the comment form below to begin a discussion about this content.

Sign in to comment