<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="2038" 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/2038?output=omeka-xml" accessDate="2026-09-19T10:25:52+00:00">
  <fileContainer>
    <file fileId="2038">
      <src>https://sleepyhollow.localarchives.org/files/original/3a0edf31d18122bb206b42dd8ccb3aa0.pdf</src>
      <authentication>13b4e939b1640c3ac26bd48dd2b1f30d</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="52">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="20525">
                  <text>RESOLUTION
Adopted at the September 19,2019 Meeting of the
Village of Sleepy Hojlow Planning Board
RESOLUTION:

SITE PLAN AMENDMENT APPROVAL

PROPOSED:

Edge on Hudson Phase 1 - Block I

LOCATION:

199 Beekman Avenue

TAX MAP
DESIGNATION:

Section 115.10-1-1 and 115.15-1-1

ZONING:

RF - Riverfront District

WHEREAS, the Planning Board of the Village of Sleepy Hollow (the Planning Board) has
reviewed an application for a site plan amendment (the Application) pursuant to the Village Zoning
Ordinance, Article X, Site Plan review, and to applicable laws and regulations considered pertinent
to the Application, which is for Phase 1 Block I of the redevelopment of the former North
Tarrytown General Motors Assembly Plant site located at 199 Beekman Avenue to be known as
Edge on Hudson (also known as the West Parcel and the South Parcel, collectively the "Site")
(the "Project"); and
WHEREAS, the Application was submitted by LL Parcel I LLC, the ("Applicant"); and
WHEREAS, the Applicant was granted a Site Plan Amendment Approval on or about
5/17/18; and
WHEREAS, the 5/17/18 Approval Resolution had certain conditions which required the
Applicant to provide to the Planning Board specific information including:
Condition #2 - Documentation sufficient in form and substance that the facade designs
for the proposed Block I are consistent with the representation made as part of the initial
Site Plan approval. The Planning Board requires that the Applicant submit to the
Planning Board the building exterior designs prior to the issuance of any Building Permit.
Condition #23 - Prior to the issuance of a building permit the Applicant shall provide to
the Planning Board a final landscape plan which shall address and mitigate any potential

Page 1 of 4

�visual impact of utilities, including but not limited to the provision of gas and electric
service.
WHEREAS, on 7/11/19 the Applicant has submitted to the Planning Board the
following materials:
Application package consisting of:
1.

Cover Letter from Diveny Tung Schwalbe

2.

Executed Planning Board Application Form

3.

EAF short form

4.

Coastal Assessment Form

5.

Zoning Compliance Form

6.

Owners of Record within 200' radius of Block I parcels

7.

Set of full size drawings (see list below).

8.

Site plan drawings last revised 9/18/19 less otherwise noted:
a.

Cover Sheet, Divney Tung Schwalbe (DTS);

b.

Phase 1 Approved Site Plan (SP-0.1), DTS;

c.

Phase 1 Amended Site Plan (SP-0.2), DTS;

d.

Block I Layout Plan (SP-1.0), DTS;

e.

Block I Grading &amp; Drainage Plan (SP-2.0), DTS;

f.

Block I Utility Plan (SP-3.0), DTS;

g.

Block I Landscaping Plan (SP-4.0), DTS;

h.

Block I Erosion and Sediment Control Plan (SP-7.0), DTS;

i.

Block I Erosion and Sediment Control Details (SP-7.1), DTS;

j-

Site Details (SP-8.1-SP-8.3), DTS; and

k.

Block I Lighting Photometric Plan (LP-1.0) DTS.

WHEREAS, at the 7/18/19 Planning Board meeting the Applicant requested and
received a six month extension to their site plan approval and provided a summary of the
modifications made to the plans;
WHEREAS, at the request of the Planning Board additional materials were
submitted to the Village on or about 8/8/19, including:
Page 2 of 4

�1.

Cover letter from DTS;

2.

Exterior Elevation Materials Graphics Figures 1-11

3.

Proposed Utility Screening Figures 12-14

4.

Response to comments raised by the Village Engineer in their
7/12/19 review memo.

WHEREAS, the Applicant appeared before the Planning Board at their 8/22/19
meeting to review the proposed exterior elevation materials, landscape treatment for
utilities and respond to comments raised by the Village Engineer; and
WHEREAS, on 9/5/19 the Applicant submitted to the Planning Board updated
exterior elevation materials graphics; and
WHEREAS, the Planning Board has also reviewed the following materials:
review memos dated 7/12/19, 8/15/19 and 9/18/19 from Dolph Rotfeld Engineering,
Division of AI Engineers, Inc., P.C. and memo dated 9/12/19 from Planning &amp;
Development Advisors; and
Applicant met with the Planning Board on 9/19/19 to review the proposed revised
exterior elevation materials exhibits; and
WHEREAS, pursuant to 6 NYCRR Part 617, the SEQRA regulations, the Planning
Board has made the following findings and caused, noted or conducted the following
activities:
1. Received a completed application and application fee;
2. Requested, received and considered comments from the Village Engineer, Village
Attorney, Village Planner and Building Inspector about the proposed project which
were provided in written form or discussed with the Board during the course of the
Planning Board meetings;
3. Requested, received and reviewed a short Environmental Assessment Form and
Coastal Assessment Form; and

Page 3 of 4

�NOW, THEREFORE, BE IT RESOLVED, that having reviewed the entire record as noted
above, in relation to the previously approved Special Permit, Riverfront Development Concept
Plan, and Phase 1 Block I Site Plan approval, the Planning Board acknowledges and accepts that
the exterior materials elevations as revised and the revised landscape treatments for proposed
utilities adequately satisfies conditions #2 and #23 as identified in the 5/17/18 Site Plan Approval
Resolution; and be it further
RESOLVED, all other conditions identified in the Village Board's 6/7/11 Special Permit
and the Planning Board's 5/17/18 Site Plan Approval shall remain in full force and effect; and be
it further
RESOLVED, that documentation, sufficient in form and substance, for the Village
Engineer to determine that the list of items outlined in their 9/18/19 correspondence have been
incorporated onto the site plan drawings.
PLANNING BOARD
VILLAGE OF SLEEPY HOLLOW

H &lt;S£pT 7*\\
Date

Page 4 of 4

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="160">
    <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="14863">
                <text>Planning Board Minutes &amp; Resolutions-2019</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="12639">
              <text>MINS_PLAN_2019-09-19_RES-EOH-Phase-I-Block-I-Site-Plan-Amend</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="12640">
              <text>Planning Board Minutes &amp; Resolutions-2019</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="12641">
              <text>2019</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="12642">
              <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="12643">
              <text>Text</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
