<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="44" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://sleepyhollow.localarchives.org/items/show/44?output=omeka-xml" accessDate="2026-09-19T08:36:35+00:00">
  <fileContainer>
    <file fileId="44">
      <src>https://sleepyhollow.localarchives.org/files/original/b726b246864a9d7781931d433bfef8e3.pdf</src>
      <authentication>7dc49ce019f84288f8ab8e19f94284e5</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="52">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="18532">
                  <text>VILLAGE OF SLEEPY HOLLOW
WATERFRONT ADVISORY COMMITTEE -APPROVED
March 2, 2005
The meeting was called to order by Richard Weiss, Chair at 8:10 p.m. The Chair noted that a
quorum was present.
Present:

Richard Weiss, Chairman
Doug Maass
Karin Adir
Ralph Gunderman
George Lence
Terence McGlynn

Absent:

Donald Stever

Also Present: Anthony DelVecchio (Recording Secretary)
Sean McCarthy (Village Architect, Village of Sleepy Hollow)
Dave Smith (Saccardi &amp; Schiff/Village Planner)
Announcements:
None.

Agenda:
1) Minutes of February 2005 meeting
2) Lighthouse Landing

1) Minutes of February 2005 meeting The minutes from the February 2005 meeting will be reviewed at the next meeting.

2) Lighthouse Landing The Chair referred to Dave Smith.
Dave Smith spoke about the sub-committee meetings. He discussed the recent traffic and
transportation meeting. He spoke about some of the parking issues.
The Chair asked if Beekman Avenue would be widened.
Dave Smith spoke about a few of the design options.
Jonathan Stein (Roseland) stated that some traffic options were discussed at the sub-committee
meeting because the options can help the Village’s existing traffic flow.

�Ralph Gunderman spoke about some of the traffic delay times that are listed in the DEIS.
Jonathan Stein stated that he is not prepared to discuss the traffic calculations listed in the DEIS
because the traffic consultant was not present.
There was an open discussion on the build and no-build statistics.
Mark Weingarten (Roseland’s zoning counsel) stated that the proposed traffic increase data
used to calculate the traffic growth rate in the Village was 2%/year.
Jonathan Stein stated that based on the data received from the Village’s and Roseland’s traffic
consultants, the Village’s traffic growth over the last 14 years has been only 2% in total. The
DEIS estimated a 20% growth over the next 10 years.
The Chair referred to the public for comments.
Jeffrey Anzavino (Scenic Hudson) summarized his letter (attached).
Victor Tafur (Riverkeeper) commended the Village on the thoroughness of its LWRP. He
noted three policies that apply to this application. They are policy 1(h), 21 (c) and 22 (a). He
stated that policy 1(h) discussed water-dependent uses and there are no water-dependent uses in
the DEIS. He referred to page 235 of the LWRP that discussed water-dependent recreational
uses.
There were no other public comments.
The Chair stated that the most effective way to proceed with this application was to review each
policy individually.

Policy 1 The Committee reviewed policies 1, 1(a), 1(b), 1(c), 1(d), 1(e), 1(f), 1(g), 1(h), 1(i), 1(j) and
1(k).
The Committee unanimously agreed that policies 1, 1(a), 1(f), 1(g), and 1(h) were applicable to
this application.
The Committee unanimously agreed that policies 1(b), 1(c), 1(d), 1(e), 1(i), 1(j), and 1(k) were
not applicable to this application.
The Chair spoke about the reference of water related and water dependent uses. He stated that
the proposed fishing pier is the only water-dependent use in the plan.
Jonathan Stein spoke about how the parcel’s recreational use was view comprehensively.
The Chair stated that he would like to see more water-dependent uses at the waterfront.
Doug Maass strongly agreed.
Jonathan Stein stated that the applicant would endorse other Village waterfront recreational
uses. He stated that the plan is only a draft. He stated that the Village should make
APPROVED - Waterfront Advisory Committee Meeting, March 2, 2005

2

�recommendations on potential uses and the applicant will respond.
Ralph Gunderman noted inconsistency with policy 1(h). He stated that the proposal is too
dense and does not keep with the existing character of the Village.
Jonathan Stein stated that the proposal is based on the linkage study and the RF district zoning
code. He stated that the analysis was done on the inner Village. He noted that the density of
the inner Village is 15.6 units/acre and the proposal is 15.5 units/acre. He also stated that the
density numbers do not include the large apartment buildings located in the inner Village.
Ralph Gunderman stated that he would like to see a reduction in the scaling and massing.
The Chair noted that although the exteriors are different, the buildings still give a massing
effect.
Jonathan Stein reviewed the overall plan. He stated that the building density proposed 36 acres
of the 94 acres to be saved for open space.
The Committee unanimously agreed that policies 1, 1(a), 1(f) and 1(g) were consistent with the
LWRP.
Ralph Gunderman stated that the applicant should create a shuttle to run up and down Beekman
Avenue.
The Committee unanimously agreed that policy 1(h) was not consistent with the LWRP.

Policy 2 The Committee reviewed policies 2 and 2(a).
The Committee unanimously agreed that policies 2 and 2(a) were applicable to this application.
The Committee unanimously agreed that policies 2 and 2(a) were not consistent with the
LWRP.
Jonathan Stein asked if the Committee approved of the fishing pier proposal.
The Committee agreed that the pier should not be eliminated but that the applicant should
provide more water-dependent recreational activities.

Policy 3 The Committee reviewed policy 3.
The Committee unanimously agreed that policy 3 was not applicable to this application.

Policy 4 The Committee reviewed policy 4.
The Committee unanimously agreed that policy 4 was not applicable to this application.

APPROVED - Waterfront Advisory Committee Meeting, March 2, 2005

3

�Policy 5 The Committee reviewed policies 5, 5(a) and 5(b).
The Committee unanimously agreed that policies 5 and 5(a) were applicable to this application.
The Committee unanimously agreed that policy 5(b) was not applicable to this application.
Ralph Gunderman thought that the proposal would benefit without the train station. He stated
that shuttles to the Tarrytown and Philipse Manor train stations would help.
Mark Weingarten stated that the proposed mixed-use is the least impacting use on traffic that
could be developed.
George Lence asked about the reference to “sufficient funding” for the train station.
Jonathan Stein spoke about possible public and private funding sources. He stated that efforts
to securing funding would proceed if Metro-North allows the train station to be built.
He stated that Metro-North has not made a decision regarding the train station as of yet.
George Lence asked when the development is expected to be fully occupied.
Jonathan Stein responded that they expect phased occupancy starting in 2007 and being fully
occupied by 2012.
George Lence asked about water impacts based on the Village’s current reservoir capacity.
Dave Smith spoke about the Westchester County requirement to increase the Village’s water
storage capacity. He stated that the Village must be able to accommodate its current users.
Jonathan Stein stated that the reservoir is only used for water storage.
The Committee unanimously agreed that policies 5 and 5(a) were not consistent with the
LWRP.
Doug Maass asked if there were any plans to increase the gas usage.
Jim Derito (Divney, Tung, Schwalbe) responded no.

Policy 6 The Committee reviewed policy 6.
The Committee unanimously agreed that policy 6 was not applicable to this application.

Policy 7 The Committee reviewed policies 7, 7(a), 7(b), 7(c), 7(d) and 7(e).
The Committee unanimously agreed that policies 7, 7(a), 7(c) and 7(e) were not applicable to
this application.
The Committee unanimously agreed that policies 7(b) and 7(d) were applicable to this
application.
APPROVED - Waterfront Advisory Committee Meeting, March 2, 2005

4

�The Committee unanimously agreed that policies 7(b) and 7(d) were consistent with the LWRP.

Policy 8 The Committee reviewed policies 8, 8(a) and 8(b).
The Committee unanimously agreed that policies 8 and 8(a) were applicable to this application.
The Committee unanimously agreed that policy 8(b) was not applicable to this application.
There was an open discussion on how decreasing the amount of impervious area would
decrease the amount of pollutants.
The Committee unanimously agreed that policies 8 and 8(a) were consistent with the LWRP.

Policy 9 The Committee reviewed policy 9.
The Committee unanimously agreed that policy 9 was applicable to this application.
The Committee unanimously agreed that based on policy 1(h) and other general discussions
regarding waterfront recreational uses, policy 9 was found to be consistent with the LWRP.
The Committee discussed the size and location of the proposed fishing pier.
Ralph Gunderman recommended that the pier be as capacious as possible.
There was an open discussion on the size of the proposed fishing pier.

Policy 10 The Committee reviewed policy 10.
The Committee unanimously agreed that policy 10 was not applicable to this application.

Policy 11 The Committee reviewed policy 11.
The Committee unanimously agreed that policy 11 was applicable to this application.
Doug Maass asked about the elevations of the proposed structures.
Jim Derito stated that there is a little differential between the Hudson River elevation and the
elevation of the proposed structures.
Doug Maass asked if basements are proposed.
Jim Derito responded no.
The Committee unanimously agreed that policy 11 was consistent with the LWRP.
APPROVED - Waterfront Advisory Committee Meeting, March 2, 2005

5

�Policy 12 The Committee reviewed policy 12.
The Committee unanimously agreed that policy 12 was not applicable to this application.
It was agreed by the Committee and the applicant that a special session would be held on March
15, 2005 at 7pm to continue the LWRP consistency review of this application.

George Lence made a motion to adjourn. Ralph Gunderman seconded. It was unanimous (6-0).

Adjourned at 10:32 PM.

APPROVED - Waterfront Advisory Committee Meeting, March 2, 2005

6

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="16">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4386">
                <text>Waterfront Advisory Committee Minutes-2005</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="266">
              <text>MINS_WATER_2005-03-02.pdf</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="267">
              <text>Waterfront Advisory Committee Minutes-2005</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="268">
              <text>2005</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="269">
              <text>Village of Sleepy Hollow All Rights Reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="270">
              <text>Text</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
