<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="2255" 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/2255?output=omeka-xml" accessDate="2026-09-19T10:31:34+00:00">
  <fileContainer>
    <file fileId="2255">
      <src>https://sleepyhollow.localarchives.org/files/original/420a9c4f927653c7a579e33c6faa89c3.pdf</src>
      <authentication>bb24711427aaa43639a0383612b641aa</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="52">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="20742">
                  <text>/// 4*
A regular meeting of the Planning Board was held on Thursday, December 18, 1997 at
8:00 PM in Village Hall, 28 Beekman Avenue, Sleepy Hollow, New York.
Present:

Donald Stever, Chairman
David Perlmutter
Joanne Becker
Betsy Sawyer-Gaylin
Nicholas Cicchetti
Don Caetano
Edward McCarthy

Also Present:

James Margotta, Building Inspector

Absent:

Janet Gandolfo, Village Attorney

Donald Stever called the meeting to order.
SFV Design -Corner Beekman Avenue &amp; Clinton Street
Chairman Stever commented that this is a preliminary hearing and general discussion of
the proposed multi-family residence before it goes before the Zoning Board.
Sam Viera, Architect for this project presented plans for the proposed eight unit family
dwelling.
James Margotta commented that the Board has already been given the coastal assessment
form for this project. He also stated that a lot that has been dedicated before now, you are
allowed a minimum of a ten foot front yard set back providing other buildings are set back
no more than ten feet.
Ms Gaylin commented that the building should be fronting on Beekman Avenue.
Discussion ensued on the set back and whether parking spaces should be under the
building rather than outside. Discussion also ensued on reducing eight units to six which
would allow for more room for parking. Mr. Viera commented that he would still need to
provide twelve parking spaces and that underground parking would not coincide with the
rest of the area. Also, underground parking would present a need for columns.
Chairman Stever commented that he was not suggesting an underground garage but
suggested four individual sub-grade spaces. Storage areas are a big problem in these types
of buildings, therefore he has the basement slated for storage and laundry facilities which
the state code requires be provided.
Donald Stever made a motion to declare the Planning Board as lead agency for SEQRA
purposes, seconded by David Perlmutter and earned.

�More discussion ensued on the parking and it was suggested that some spaces he
underneath and others outside on the Clinton Street side. Discussion ensued on where the
air conditioners should be installed and it was suggested that they be placed on the south
side towards the parking lot area.
Chairman Stever commented that he and Betsy Sawyer-Gaylin will be a sub-committee to
discuss with Antonio Rodrigues and his attorney his request for the reinstatement of the
resolution for the Philipse Plaza project.
There being no further business, David Perlmutter moved, seconded by Edward McCarthy
to adjourn the meeting, motion carried.
Respectfully submitted,

Angela Everett
Recording Secretary

�VILLAGE OF SLEEPY HOLLOW
PLANNING BOARD
Donald W. Stever
Chairman

January 13,1998
VIA FACSIMILE
Samuel Vieira R.A.
SFV Design
15Neperan Road
Tarrytown, NY 10591
Re: Application of John Cabeca
Beekman Avenue and Clinton Street
Dear Mr. Vieira:
Because of the fact that neither the Village Attorney nor the Planning Consultant
was in attendance at the December 18 meeting, the Planning Board was able only to provide
an informal set of comments on your client's site plan. It is important that your client
understand that the Planning Board has neither approved the site plan, nor indicated an
intent to approve it, and that the Planning Board is not bound, in exercising its discretion
with respect to the site plan, by area variances granted by the Zoning Board of Appeals. At
the December 18 meeting, Planning Board members expressed concern about or
commented on a number of elements of the plan, including the orientation of the building
(what is front and what is back), the number of units, the number of parking spaces and
their location and the percentage of the lot that will be covered by asphalt (suggestions were
made for reducing the number of units and parking spaces and locating four of them
beneath the building), and the location of the air conditioning compressors.
The Planning Board is in the process of evaluating the procedures followed by
applicants who require variances in order to develop property in accordance with a proposed
site plan. You may wish to consider coming back to the Planning Board for a more
extensive evaluation of the site plan, and obtain input from the Village's planning consultant,
before proceeding with your application to the ZBA
Very truly yours,

til

Chaiifman, Planning Board
Cc: Robert Anello, Chairman, ZBA

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="138">
    <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="14841">
                <text>Planning Board Minutes &amp; Resolutions-1997</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="13873">
              <text>MINS_PLAN_1997-12-18</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="13874">
              <text>Planning Board Minutes &amp; Resolutions-1997</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="13875">
              <text>1997</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
