My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Hearings Official Decision
>
OnTrack
>
Z
>
2015
>
Z 15-5
>
Hearings Official Decision
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2015 4:00:31 PM
Creation date
9/24/2015 12:03:42 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
Z
File Year
15
File Sequence Number
5
Application Name
LAUREL RIDGE
Document Type
Hearings Official Decision
Document_Date
9/24/2015
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
9
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
The applicant produced a metes and bounds description of the property. No one appears to take <br />issue with that description. The applicant then superimposed the subject property, using the <br />metes and bounds description, on to a same scale version of the 2004 Metro Plan. Because the <br />2004 Metro Plan is generalized, the decision of where to place the subject property when <br />superimposing it on the 2004 Metro Plan requires the use of referents to properly line up the two <br />maps. The applicant used Eat 30th Avenue and the north arrow to align the two maps. An <br />enlarged version of the applicant's proposed boundary is depicted in Exhibit M. <br />LHVC does not agree with the method the applicant used to superimpose the map of the <br />property on to the scaled version of the 2004 Metro Plan. LHVC produced maps showing much <br />more POS designated land by using a version of the Metro Plan diagram obtained from LCOG <br />that are depicted in Exhibits 1-5 to their letter of September 2, 2015. LHVC also uses tax lots for <br />other properties, city limits, and additional streets to generate what it argues are more accurate <br />maps than the applicant. LHVC materials were prepared in part by a certified engineering <br />geologist, and the arguments are compelling. In fact, if the question were where the boundary is <br />most likely located using any available information, I would likely agree with LHVC. In <br />determining the boundary, however, we are all bound by the 2004 Metro Plan diagram. As staff's <br />September 2, 2015 memorandum explains, LHVC used maps generated by LCOG from a digital <br />version that is different from the 2004 Metro Plan. Even though that digitized version is likely <br />more accurate than the 2004 Metro Plan, even LCOG acknowledges that only the 2004 Metro <br />Plan is the official version of the diagram. Furthermore, city limits and tax lots are not depicted <br />on the 2004 Metro Plan diagram. So even though LHVC's maps may be theoretically more <br />accurate, they are not more accurate for determining the boundary by using the 2004 Metro Plan <br />diagram. <br />LHVC also takes issue with how the applicant aligned East 30th Avenue with the subject <br />property. According to LHVC, aligning the location of East 30th Avenue on the map of the <br />property with East 30th Avenue on the 2004 Metro Plan diagram results in the two depictions of <br />East 30th Avenue diverging from each other, particularly the farther you get from the property. <br />LHVC attempted to align East 30th Avenue differently to show more POS plan designation for <br />the property. The 2004 Metro Plan diagram is a generalized map. When it is scaled up to match <br />metes and bounds descriptions of individual parcels there will almost always be discrepancies. <br />No matter where you align East 30th Avenue, the farther you get away from the alignment the <br />Hearings Official Decision (Z 15-5) Page 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.