TODAY IS FRIDAY, JANUARY 9, 2026. APPEALS AND VARIANCE HEARING. I AM THE HEARING OFFICER, TIM PACK. FIRST ITEM ON THE AGENDA IS THE APPROVAL OF THE MINUTES FROM OUR SEPTEMBER 23, 2025 MEETING. I HAVE REVIEWED THOSE MINUTES. I APPROVE THOSE MINUTES. Next item on our agenda is the 12-12640 South Relation Street appeal filed by the Ayers. Did I say that right? Ayer. Ayer. I apologize. By the Ayers. Okay. Are we ready to proceed? We're ready. Okay. Well, it's your appeal. I invite you to the podium. make your presentation. I have reviewed all the materials. I might have some questions for you. Is that what you were doing? That's what I was trying to do. Whatever you're more comfortable with. I understand. And if there's something you want me to look at, all the materials are, I have a screen here, whatever is up there. Great. We can put anything up. Great. So understanding that, if you, as I go through this, if there's anything that you have questions on, please feel free to stop me and we can discuss and open it up further. We address the city's appeal response and the zoning administrator's interpretation based on the existing records. The points below are rebuttal explaining why the city's reasoning cannot be sustained under Draper's Code and Utah Administrative Law Review. As stated in the city's error appeal response in Section 3A, quote, the appellant must show that the zoning administrator's interpretation was arbitrary and capricious, which means a failure to meet the substantial evidence standard. To demonstrate that the administrator's interpretation was arbitrary and capricious, failure to meet substantial evidence standard or stated differently, lacking a rational basis, and failing to consider relevant factors, and is the legal standard used to challenge administrative agency actions, I will be presenting three points. I will summarize these three points up front and then discuss more in detail as follows. Point one, Title 17 subdivision standards. The city's theory assumes the 2000 Baker's Coast subdivision approval converted this parcel from an interior lot into a corner lot when June Circle was approved. If that conversion occurred, it could not lawfully have occurred while bypassing Title 17's mandatory corner lot and developability standards. The subdivision approval as implemented did not satisfy those standards and should not have been approved in its current form. Therefore, the parcel's lawful classification should remain interior lot status unless and until the city identifies a code mechanism that lawfully converts it while satisfying Title 17's mandatory standards. Point two, uniform application. Utah administrative law requires consistent application of land use standards. The city attempts to exclude consideration of similarly situated properties to avoid scrutiny of how Draper applies corner lot rules in practice. Inconsistent application cannot be insulated from review by simply narrowing what the interpretation discusses. Point three. City conduct shows no settled, quote, corner lot since 2000 designation. If the parcel has been a corner lot since 2000, the city's position would have been clear and consistently communicated during our due diligence process prior to purchasing this property. Instead, the record reflects clear uncertainty, internal disagreement, and the need for an interpretation. Had the parcel been identified and treated as a corner lot with dual front setbacks, appellants would not have purchased it. The requested relief here is given the city's interpretation was arbitrary and capricious, we are requesting that the corner lot determination not be sustained and that the parcel be treated and recorded as an interior lot with interior lot setbacks. That is 30 feet front on Relation Street, 12 foot side yards, and 20 foot rear. And that the city's classification be reflected consistently in city records and aligned with county records so the property can be reasonably improved. Under DCMC section 9-5-180D4, the question is whether the interpretation is supported by substantial evidence and whether it correctly applies the code's plain meaning when the code is read as a coherent whole, not in isolated fragments. The appellants agree the only issue on appeal here today is whether the parcel was correctly classified as a corner lot under Draper City Code. Appellants do not appeal the determination that the parcel and structure are legally non-conforming. This is a code interpretation appeal, not a dispute over physical facts. To discuss section 3A of the city's air appeal response under DCMC section 9-5-180D4, the hearing officer decides this appeal based upon the record only and determines whether, one, the record contains substantial evidence for essential findings, and two, the zoning administrator correctly interpreted and applied the land use regulations. In its response to our appeal, the city cites Outfront Media LLC versus Salt Lake City Corporation, 2017, Utah, 74, paragraph 12. There, the Utah Supreme Court distinguishes two separate bases for reversal. One, a decision is illegal if it rests on an incorrect interpretation or application of the law. And two, a decision is arbitrary and capricious if it is not supported by substantial evidence. Accordingly, this appeal focuses on A, whether the interpretation correctly applies Draper's Code when read as a whole, our first point, and B, Whether the city's asserted corner lot rule can be supported by the record and applied consistently, our second point. Before turning to our substance, I would like to note a concern with the city's presentation in the appeal response. The city's written response was dismissive and at times condescending, implying our position barely merits consideration. To be clear, we did not create this dispute. We came here because the city itself created uncertainty, changed its position, and then asserted after the fact that the issue was supposedly clear all along, that this property has been a corner lot since 2000. This matters because it highlights a problem with the city's argument. The city cannot credibly claim the issue has been settled for decades while the city's own process reflects uncertainty and reinterpretation. That is our third point. We also note that the city's references in their appeal response to dictionary definitions and quote geometry do not resolve the legal question at hand. For clarity, we do not dispute the parcel physically abuts the June Circle corridor, the ordinary meaning of the word abut, or the geometric relationship between June Circle and Relations Street. The issue is whether abutment alone compels corner lot classification when Draper's Code is read as a whole, including the subdivision standards in Title 17. I will now expand upon our three points. Our first point regards Title 17 consequences of the city's 2000 conversion theory that, quote, when June Circle was established in the Platte, the subject property became a corner lot, end quote. The city argues that the Bakers Cove subdivision plot, quote, excludes the subject parcel and therefore cannot serve as the baseline for corner lot status. Appellants agree that the plot did not directly reclassify this parcel. Can I stop you right there? Can we put the plot up? That might help me. The subdivision plot itself. Let me. You have it in the folder? Okay. Where's the plot map? When you talk about the platen, is this what you're referring to? Yes, correct. That's what they cited in their response to our interpretation. Okay, continue. Okay. appellants agreed that the plat did not reclassify the parcel however the relevance of the 2000 approval arises from the city's own asserted theory that quote when june circle was established in the plat the subject property became a corner lot it is that asserted consequence not the plat's direct applicability that is at issue under the city's theory The 2000 Bakers Co. subdivision approval is treated as having converted the subject parcel from an interior lot into a corner lot, thereby triggering corner lot consequences that must be evaluated under Title 17. If approval of the subdivision in 2000 converted the subject parcel from an interior lot into a corner lot, then that subdivision approval necessarily imposed new dimensional new dimensional and developability consequences on the parcel. Under the Draper City Code, such a conversion could not lawfully occur without satisfying the mandatory standards applicable to corner lots. Title 17 expressly requires that one, residential corner lots be platted wider to accommodate increased setbacks. That's found in the DCMC section 17-5-020F And two, subdivision approvals result in lots that are developable and capable of reasonable improvement. That same section in paragraph A. The Bakers Cove subdivision approval did not widen the parcel. It did not reconfigure it, and it did not ensure that it remained developable if treated as a corner lot. If the city's current position is accepted, the subdivision approval created a non-conforming impractical and undevelopable corner lot condition an outcome title 17 does not permit in that circumstance the appropriate conclusion is not that the parcel must now be treated as a corner lot by operation of law rather the city's theory exposes a fundamental defect if the 2000 subdivision approval produced a result that converted the subject parcel into a corner lot then the subdivision should not have been approved in that form without complying with Title 17's mandatory corner lot and developability standards, including preserving the subject parcel as a conforming interior lot through an appropriate access configuration. The City identifies no provision of the code that permits an automatic conversion of a parcel's classification while bypassing those requirements. Accordingly, the assertion that the parcel quote became a corner lot when June Circle was approved does not resolve the appeal. It underscores the problem. Either the subdivision approval failed to comply with Title 17 at the time it was granted, or the parcel was never lawfully converted into a corner lot. In either case, the city's current interpretation cannot be sustained. The city cannot rely on the 2000 action to impose new corner lot consequences today while simultaneously avoiding the governing standards by asserting that, quote, what's done is done. Either the conversion was lawful under the code or it cannot be used now. The city has suggested in their rebuttal to our appeal that the parcel is developed simply because a structure exists upon it. This, however, misunderstands the purpose of Title 17 and legal nonconformity protections. Title 17 does not exist merely to allow a lot to remain occupied indefinitely. It exists to ensure that lots remain capable of reasonable improvement over time. A rule that deems a parcel developable solely because an aging structure happens to sit on it effectively freezes the property in time treating the existence of an old structure as a reason to deny any reasonable improvement and preventing reconstruction, modernization, or reasonable redevelopment without any change in zoning, platting, or physical conditions. That is precisely what nonconformity protections are designed to prevent. Draper City Code does not authorize interpretations that lock a parcel into its existing condition and strip it of meaningful redevelopment potential decades after plat approval. If the city's interpretation leaves the parcel usable only so long as the current structure remains untouched, that is not developable within the meaning of Title 17. It is a regulatory dead end, and the interpretation still cannot be sustained. Additionally, the city has also claimed the word abutment for reasons of their interpretation. Can you speak in the mic? Okay, so you raised chapter 17-5-020 subsection F, corner lots. Is it your position that when this Baker's Cove subdivision was platted, the city made a determination on whether your property was a corner lot or not? So that is what the city itself has asserted in its appeal response, that because this was platted and at the time that it was platted, our lot automatically converted into a corner lot. That's the entire basis of their argument. Okay. So before the – I don't want to use terminology that – The right-of-way, the path, the road, which is now June Circle. Before it was platted, it was something else, right? It was land. It was just land. There was no right-of-way? Correct. Okay. And by – your position is the result of this plat was to – is it your position that it automatically converted it to a corner lot? That is what the city has stated. That is not what we argued. That was the basis for their interpretation. Okay. They are the ones that provided this plat in their interpretation response. Okay. And so to quickly summarize your position of why it's not a corner lot based on the Baker's Cove plat. Because there was never anything done to lawfully convert it from the interior lot to a corner lot. Okay. The city has provided no mechanism to show how it converted from an interior lot to a corner lot. And when the plat was established, there was no review done as to the implication or consequences upon our lot status at the time. And I understand the city's position is that there was no formal determination that your lot was a corner lot. as of the time of the Baker's Cove plot. But because of the Baker's Cove plot, it had the effect of turning your lot into a corner lot. Is that your understanding of the city's position? Correct. Do I have that correct? That's what they have stated. Okay. Continue, sorry. Great, no problem. Thank you for your questions. The city has suggested also in their rebuttal to our appeal, oh, excuse me, Additionally, the city has also claimed the word abutment as reasoning for their interpretation. Abutment is conceded by the appellants. The question is whether abutment alone compels corner lot classification without reconciling the result with Title 17's mandatory standards. The city's argument rests almost entirely upon the one word of abutment. The city says that because our parcel abuts June Circle And because June Circle meets the broad definition of a street, the parcel must automatically be a corner lot. That reasoning is flawed because abutment alone has never been sufficient to determine lot classification under Draper City Code. If abutment alone were enough, then the city would be required to classify a wide range of parcels as corner lots simply because they touch or border something labeled a right-of-way. This would include parcels of private access easements, utility corridors, paper streets, flag lot access lanes, shared private drives, and rights of way that provide no frontage, addressing, or access to the parcel itself. Draper has never applied its code that way. The issue is not whether the word abut can be read broadly in a dictionary as the city has stated. The issue is whether the city can read that word so broadly that it nullifies other mandatory provisions in the code. An interpretation that turns abutment into a universal trigger for corner lot status creates internal conflict within the ordinance and cannot be sustained under Utah law. Abutment may be a necessary condition for corner lot. but it has never been a sufficient one. And treating it as sufficient creates results the code was designed to prevent, which leads us into our second point of uniform application. Excuse me. I will next address our second point of uniform application or arbitrary or capricious action. Utah administrative law requires consistent application of land use standards. The city's effort to exclude similarly situated properties by arguing that they were not cited in the interpretation would improperly insulate inconsistent application from appellate review. The city objects to the appellant's discussion of similarly situated properties on the grounds that those properties were not cited in the zoning administrator's interpretation and therefore must be excluded under DCMC section 9-5-180 . The appellants do not dispute record only review and do not offer the comparables as new factual evidence regarding the subject parcel. Rather, the comparables are cited for a legally permissible purpose to evaluate whether the city's stated interpretation can be lawfully and uniformly applied. Appellants agree on the governing rule. This is a record-based appeal under DCMC 9-5-180. We are not asking the hearing officer to accept new testimony, make new factual findings, or consider facts that were unavailable to the zoning administrator. but the city's position goes further than the code allows. The restriction in 9-5-180 limits new facts, not legal argument. An appellant is permitted, indeed required, to explain why an interpretation based on the existing record misapplies the code or produces an unlawful result. Nothing in our appeal changes the underlying facts. The parcel boundaries have not changed. The recorded plat has not changed. June Circle has not changed. The zoning code has not changed. The only thing that changed was the city's interpretation. What the city labels as quote new evidence is simply our explanation of why their interpretation on its face fails to properly apply Draper City Code as a whole. That is legal analysis, not factual supplementation. Let me stop you there. I understand your position between new evidence versus legal argument. If you're bringing in a comparable, showing me a map, isn't that new evidence? In other words, can you make the legal argument without showing me the actual evidence? Just one moment, please. And a question to the city. I'm inclined to let them present their case. I mean, it's in their submission. And then I'll reserve ruling of whether I consider it and whether I consider it part of the record. Correct. Is that... Even... And I'm... Is that acceptable? Fine with me, yeah. Okay. So I'm not going to restrict in what you present today. In my written ruling, I may say you presented something. I'm going to accept it, admit it, or not. Right. Does that make sense? Yes. Okay. So in response to that, even if you disregard and exclude the disputed evidence that we've supported or the excluding articles, excuse me, that we've submitted, This finding still fails on its face because it still fails to reconcile title nine with title seventeen. The city's position in excluding these facts in the administrative interpretation would effectively limit appellate review to only those facts and comparisons the zoning administrator themselves elected to discuss. thereby insulating inconsistencies from review by omission. If accepted, the narrower a zoning administrator writes an interpretation, the narrower the scope of appeal, regardless of whether the city applies the same ordinance differently elsewhere. Here, the city's interpretation asserts that adjacency to a right of way constitutes, quote, a street, and that, quote, When June Circle was established in the Platte, the subject property became a corner lot. The appellant's references to similarly situated properties test the legal consequence of that interpretation. Whether Draper City has in practice treated right of way adjacency as automatically creating corner lot status and impose dual 30 foot front setbacks on other properties elsewhere. The record reflects that Draper City has not applied the rule in that manner to other recent approvals, including projects currently under construction. An interpretation that appears to be applied flexibly in the context of larger development approvals, but rigidly when applied to an individual homeowner, raises a serious concern of unequal application, even absent any suggest of intention. Such an outcome underscores why abutment alone cannot be dispositive and why the code must be applied uniformly to materially similar parcels regardless of the applicant. In the appeal application, appellants identified multiple recently approved residential parcels that, under the city's own definition of street, similarly abut more than one right-of-way. These examples are not offered to challenge those approvals or indeed to introduce new facts, but to test the City's interpretation for internal consistency. Under the interpretation advanced here, each of those parcels would be required to carry dual 30-foot front setbacks as cornered lots. The record reflects that they were not treated that way, yet were still approved for construction. This contrast illustrates that the city has not, in practice, applied abutment alone as an automatic trigger for corner lot classification, reinforcing that the city's interpretation at issue reflects a novel and overly rigid application rather than the code's settled meaning. Consideration of similarly situated properties for purposes of evaluating arbitrariness does not constitute new testimony or new information about the subject parcel and falls within the hearing officer's responsibility to determine whether the interpretation reflects a lawful and consistent application of the code. Stated plainly, if Draper applies corner lot rules differently to materially similar circumstances, then the asserted rule is not being applied consistently and cannot be sustained as non-arbitrary as ruled by the Utah Supreme Court in the city's own referenced case of Outfront Media LLC v. Salt Lake City Corporation, 2017 Utah, 74 paragraph 12. The third and last point we will present today regards the City's conduct in reflecting that there has been no settled, quote, corner lot since 2000 designation. Appellants acknowledge reasonable reliance is not determinative under DCMC Section 9-5-180 and do not offer it as an independent basis for reversal. It is relevant context for the city's claim that the parcel has been a corner lot since 2000. The city asserts that one, the parcel became a corner lot when June Circle was approved in 2000. Two, the issue was not ambiguous. And three, the remedy should have been pursued by a predecessor decades ago. But if this had been truly settled for 24 years, the city would have consistently communicated corner lot setbacks and there would have been no internal uncertainty, and there would have been no need for a formal interpretation now. The record, however, reflects the opposite. During pre-purchase due diligence, appellants architect and contractor both contacted the city to confirm buildability and setbacks. On August 28th, appellants received a written message from the contractor relaying the setbacks provided to him by the city, stating, quote, Here are a few things I got for you on that lot. Total square foot of lot is 10,890 square feet. The front setback is 30 feet, rear setback is 20 feet, and the sides are 12 feet. Those setbacks correspond to an interior lot, not a corner lot. If the parcel were a settled corner lot, the city would have described dual front setbacks along both Relation Street and June Circle to the architect and contractor, quoting directly from the city's air appeal response. Section 4A, the city's response, quote, frontage does not determine whether a property is defined as a corner lot. Plats do not identify corner lots. The city does not create corner lots or intend to do so. Corner lots are created when properties abut two intersecting streets in the manner described by the code SUPRA. When June Circle was established in the plat, the subject property became a corner lot. And two, section 4C, the city's own response, quote, the zoning administrator's interpretation does not clarify an unresolved ambiguity. The subject property became a corner lot when June Circle was approved. Over the nearly two and a half decades that have intervened, this is the first time either the appellant or the appellant's predecessor in interest has asked for an interpretation, end quote. During due diligence, before committing substantial architectural fees, Appellant Jenna Ayer, myself, contacted the city to confirm the lot status in writing, specifically noting the property's relationship to Relation Street and June Circle. If the corner lot status were settled, as the city claims in their rebuttal that I read above, it would have been readily ascertainable and communicated. Instead, city staff and its director expressly expressed uncertainty and directed me to file an administrative interpretation in order to receive a formal answer. Upon doing so, and in numerous conversations with the city planning and their director, it was revealed that internal views diverged between city planning officials and the city attorney, and three different stated deadlines in providing a ruling response to me were missed. In fact, it took the city over a month to settle upon a decision as to whether the parcel was an interior or corner lot. That sequence is inconsistent with the city's quote clear since 2000 narrative, and it supports our third point. The city's own conduct shows the designation was not treated as settled in practice. The city's indecision has caused concrete financial harm. appellants incurred substantial due diligence costs prior to purchase, have carried the capital costs of a vacant property for months, experienced delays in architectural and construction planning, and now face additional costs and time associated with this appeal. More fundamentally, had the parcel been identified as a corner lot during due diligence, appellants would not have purchased it. If the city's interpretation is sustained and the parcel is finalized as corner lot, The severely constrained building envelope will prevent reasonable modern residential development and materially diminish the property's value, resulting in further financial harm. In conclusion, under DCMC section 9-5-180D4, the record does not sustain the zoning administrator's corner lot determination. THE INTERPRETATION DOES NOT CORRECTLY INTERPRET AND APPLY DRAPER CITY CODE WHEN READ AS A WHOLE. IT TREATS ABUTMENT AS DISPOSITIVE. IT ISOLATES TITLE 9 DEFINITIONS FROM TITLE 17'S MANDATORY SUBDIVISION STANDARDS GOVERNING CORNER LOCK CONFIGURATION AND DEVELOPABILITY. and it yields a result that effectively freezes the parcel in its existing condition rather than preserving its ability to be reasonably improved consistent with legal nonconformity protections. It also assigns decisive consequences to the 2000 Baker's Cove action without identifying any code provision authorizing an automatic conversion to a corner lot while bypassing Title 17's requirements. and it advances a restrictive rule that cannot be applied coherently or uniformly in practice. Accordingly, appellants respectfully request that the hearing officer not sustain the corner lot determination and instead confirm that the subject parcel is properly classified and recorded by the city and consistently in county records as an interior lot subject to interior lot setbacks, which are a single 30 foot YARD SETBACK FROM RELATIONS STREET, TWO 12-FOOT SIDE YARDS, AND A 20-FOOT REAR SETBACK SO THAT THIS PROPERTY CAN BE REASONABLY IMPROVED. THANK YOU. A FEW FOLLOW-UP QUESTIONS. SO IF WE'RE JUST LOOKING AT THE definition of corner lot in a vacuum, right? I read the definition as, so a lot are parcel abutting two intersecting or intercepting streets. So one of the issues is, is June Circle a street, right? The definition of street seems to be very broad. Do you dispute that June Circle is a street? Can you speak in the mic? No, not based on the code. From what the code reads, it's saying that it is a street. So according to the code, it's a street. And the intersecting streets of Relation Street and June Circle are less than 135 degrees. Correct. And I don't want to Essentially, your argument is that the city effectively changed an interior lot to a corner lot and effectively made it a non-compliant, the home a non-compliant structure and the lot a non-compliant lot when they recorded the Baker's Cove play. Is that correct? Do you agree with that? That is what the city has argued in their response. Do you agree with that? Like that's essentially what – well, I understand. You don't think it's a corner lot, but that's – okay. The city has not provided any mandatory – MECHANISMS BY WHICH LOT CLASSIFICATIONS CAN CHANGE. THERE'S BEEN NO PLAT RECONFIGURATION, THERE'S BEEN NO SUBDIVISION APPROVALS BECAUSE THEY THEMSELVES ARGUE THAT THIS DOES NOT APPLY TO OUR LOT, THAT OUR LOT WAS EXCLUDED, AND YET THEY INCOHERENTLY THEN ARGUE IT AS THE BASIS FOR THEIR INTERPRETATION. THERE IS NO ZONING ACTION AND THERE'S BEEN NO VARIANCE RULING. THEREBY THERE HAS BEEN NOTHING PROVIDED THAT SHOWS US HOW THIS WAS LEGALLY TRANSFORMED FROM AN INTERIOR LOT INTO A CORNER LOT, MEANING IT NEVER WAS. AND I DON'T EXPECT YOU TO BE AN EXPERT ON THE CITY CODE, BUT IS THERE A MECHANISM UNDER THE CITY CODE WHERE A LOT IS FORMALLY DESIGNATED AS AN INTERIOR LOT OR A CORNER LOT? WE HAVE BOTH DONE SUBSTANTIAL RESEARCH AND CAN FIND NONE. But you're aware that the city made a determination that it was a corner lot is the zoning administrator's recommendation or opinion. That was quoted to me by Todd Draper that on his suggestion that I submit an administrative interpretation because it was unclear to them as to how that lot was classified and that had never been classified within their jurisdiction. Okay. You'll have a chance to listen to the city. You have a chance to respond. Thank you. You like to stay there? I can turn turn this way. Let me ask a couple questions before you get started, certainly. So I asked the question. When the Bakers Cove Platte subdivision was approved and recorded. Is the city's position that that event had the effect of changing the status of the property from an interior lot to a corner lot. That's right. Okay. And... To go back to the question that you asked, if there's a legal mechanism, it would be impractical to create a legal mechanism for changing interior lots into corner lots, other than having the definition of our code apply as its plain language, Otherwise, the city would be bogged down with going through every single lot and parcel in the city regularly, trying to reclassify and follow through with a procedural mechanism to convert it. So that's the reason why it's not. There's no mechanism within the Draper City Municipal Code to change a corner lot or an interior lot to a corner lot. It's just not practical. It either is or it isn't. What's that? It either is or it isn't, and a lot can change over time. That's right. It's by definition a corner lot if there are two streets intersecting or intercepting, that's the way our code reads, that abut the lot or parcel with a degree of angle of 135 degrees or less. Okay. So here's kind of where I'm... What's giving me pause is... So the... The chapter 17... Subdivision requirements for subdivision 175020 lots. Subsection F talks about corner lots. Corner lots for residential use should be platted 10 feet wider than interior lots in order to facilitate conformance with the required street setback requirements of the zoning ordinance. Now, I understand that when you're plotting a subdivision, right, this applies to the lots within that subdivision, not to lots outside of that subdivision. But what happens when the effect of recording this plat had the effect of transforming an interior lot to a corner lot, which doesn't comply with that requirement, if it was part of the subdivision? Yeah, so response to that is several fold. First, Title 17, It's not considered within the zoning administrator's jurisdiction to hear matters of Title 17. It's matters of Title IX. Title 17 wasn't raised in the original request for the zoning administrator's interpretation. And so for that reason, I would object to any kind of inclusion of discussion of Title 17 in the same vein that it's new evidence. However, to address the issue of Title 17, Title 17 is... required of the city as an engineering standard. Title 17 addresses our engineering standards. Our engineering department looks at PLATs and makes sure that they comply with what's in our engineering standards under Title 17 and then can only, because the way that Title 17 reads, can only apply those standards to the property that's included within the PLAT. They have to not consider property outside of the plat when they look at those standards. The owner of the parcel in question at the time that June Circle was created by this plat specifically left this parcel out. They owned that parcel as well as all of the others that are in the Baker's Cove plat. And so they specifically excluded their parcel. For what reason, I'm not sure. But assuming that in 2000, Title 17 read then as it does now, that's another problem that I have with applying Title 17 here is because we're applying Title 17 as it's amended today to conditions that were in effect in 26 years ago, 25 years ago, which... The code might have read differently. There's no basis for us to know what the code read in 2000 other than if we go and look it up and that the code as it read in 2000 hasn't been brought forward as a basis for saying that the city's action was illegal then beyond that statute of limitations would have run on that claim by now. And. And so let's just assume for argument's sake that. We can use our code to apply to an action that happened in 2000, knowing that the subdivider was the owner of the appellant's property and the subdivider was the owner of all of the property within the plat. We can only assume that they did this fully aware of what was going to happen to the property that the appellants are, that's the subject property today. and that they were fully aware of the legal consequences, or if they weren't, at the very least, they had every opportunity to become informed of those consequences before they submitted the plat, and they did it anyway. Okay. I've read your submission, but if you want to respond to some stuff, go ahead. So the city's argument is, it goes to a plain language argument. The Ludma requires that that jurisdictions read the plain language of their own code and of Ludma and apply that. If we look at the definition of corner lot, the definition of corner lot reads that it's a lot or a parcel that abuts two streets with an intersecting or intercepting angle of 135 degrees or less and so. While in the brief I I mentioned Geometry and math. I understand it seems a little bit glib. It was mostly a bigot myself for being bad at math. But yeah, I'm bad at math, but I can see that it's less than 135 degrees just by eyeballing it. But then I had our GIS department draw a 135 degree angle and superimpose it on the map to show that it's less than 135 degrees. Because our plain language argument is. is there is there a parcel there does the property of the parcel about two streets do those streets intersect or intercept at an angle of less than 135 degrees if so it's by definition a corner lot and if the corner lot and if it's a corner lot then it has to meet the corner lot setbacks june circle is a street that is evidence here zoom in here let me zoom in here this is the plat we have this here listed as a right-of-way easement and then we have june circle here it says one two six three five south street and then in parenthesis in brackets there private and if we look at the definition of do we have the code up here jen now i'll pull it up do you agree that was It was not any type of street prior to the recording of the plat? Prior to recording of the plat, it wasn't a street. It was part of either the parcel in question or the neighbor's parcel, which would have meant that at that time, it was an interior lot. No argument for me that in 2000, before the plat was recorded and before the June Circle was created, that would have been an interior lot. But as soon as June Circle was created, Now there are two streets. And this may not have been the definition in 2000 either. I'll concede that. But as soon as we changed our ordinance to define a corner lot as one with two streets that abut the property, my argument is that's when it becomes a corner lot. And if not... If there's some argument for a legal non-conforming use, that would be another zoning administrator's interpretation. So if the appellants want to come back and argue, well, in 2000, the code didn't say that this was what a corner lot was when the plat was approved, then we can look at the definition of what a corner lot was back in 2000, and then we can make a determination of whether there's a legal non-conforming use that's continued to this day. That may or may not mean that the subject property is redevelopable, because with legal nonconforming uses and legal nonconforming statuses, those can change based off of redevelopment. But the city's argument is the plain language argument, which has been required by Utah law as recently as within the context of Land Use Development Management Act, Northern Monticello Alliance versus San Juan County, which was in 22 or 23. That's still good law. As for the argument that the city has failed to enforce or failed to look at other lots and apply the same standards, that doesn't necessarily make the decision today arbitrary and capricious. Arbitrary and capricious means that WE CAN'T MEET THE SUBSTANTIAL EVIDENCE STANDARD. AND BASED OFF OF THE INFORMATION THAT'S INCLUDED IN THE ZONING ADMINISTRATOR'S REPORT, THE SUBSTANTIAL EVIDENCE STANDARD CAN BE MET BECAUSE THE SUBSTANTIAL EVIDENCE IS, LET'S SEE, I HAVE IT WRITTEN DOWN HERE. I ALWAYS GET THIS WRONG. I CAN'T RECITE IT OFF THE TOP OF MY HEAD. THE QUANTUM AND QUALITY OF RELEVANT EVIDENCE THAT IS ADEQUATE TO CONVINCE A REASONABLE MIND TO SUPPORT A CONCLUSION. AND SO I THINK THAT WE CAN MEET THE SUBSTANTIAL EVIDENCE STANDARD. IT'S NOT A VERY HIGH BAR. that if there's enough evidence there to convince a reasonable mind to meet the same conclusion that this is a corner lot, I think that we can say that we've met our substantial evidence standard and it's not arbitrary and capricious. Whether we've enforced our corner lot standard and our corner lot setbacks against other properties in the city previously actually has no bearing on whether we can do so now. There's a case called, well, there's a couple of cases. The earliest case that I could find goes back to 1976, and it's Karchner v. Salt Lake County, where the court said that a municipality's failure to enforce an ordinance does not preclude it from enforcing an ordinance now. Failure to enforce previously doesn't mean that you can't enforce it now. And that was upheld as recently as 2023 by Burmese v. Summit County. If we've failed to designate a lot or a parcel as a corner lot and treat it as a lot or a parcel that's a corner lot in the past, that doesn't necessarily make our decision to identify this as a corner lot now, arbitrary and capricious. And we are obligated to follow our own ordinance. So when we get asked for zoning administrator interpretation, what we need to do is we need to look at our own ordinance read it in the plain language meaning of the ordinance and then apply our ordinance so that we can come out with predictable conclusions other than that my my contention is under the plain language meaning of the term corner lot and the plain language meaning of street this is a corner lot and the zoning administrator's decision was not incorrect in terms of calling it a corner lot, and it should be upheld. Do you have any other questions? No, I don't. Okay. You have an opportunity to respond. Let me ask, how much time do you think you need? Is it more than five minutes? I'd like to take a quick break. Yes. Can we take a five-minute break? Sure. Great. Thanks. Sure. Take your time. Okay, I think we're ready. Okay. I think we'd first like to start by asking why we are not looking at any of the comparable properties that have not been treated as corner lots. So I'll say this. I'm not going to restrict your presentation in any way. there is an ordinance which restricts what I can consider. And so after I re-review that ordinance and look at the evidence, I may ultimately say, well, I agree with you. This is argument. This is legal argument. It's not new facts, not new evidence. Or I may not. And then in my written ruling, I can't consider that. So you're going to reserve that for after you're reviewing. Right. So I'm not going to restrict. And I understand. I will also say this, though. sometimes cities, counties, aren't consistent in their enforcement of their own code. And that is usually not a basis for having the city deviate from its own code in a different instance. Understood. But anyway, I'm not going to restrict what you present. Okay, thank you. Excuse me. I am still recovering or in the midst of a very bad cold. Okay. We'd first like to address Title 17 in the issue that the city has discussed. It is not, in fact, new evidence. Yes. TITLE 17 IS NOT, IN FACT, NEW EVIDENCE, AS HE IS CLAIMING. IT WAS CITED IN THE ORIGINAL REQUEST FOR THE ZONING ADMINISTRATOR'S INTERPRETATION, AND IT WAS REFERENCED IN THE CITY'S OWN INTERPRETATION. THIS WAS ORIGINALLY FILING LIST TITLE 9, TITLE 17, AND THIS WAS THE INTERPRETATION WHERE THEY DISCUSSED THE CONCEPT OF TITLE 17. I'VE SEEN THE REFERENCES IN TITLE 17. CAN I CLARIFY SOMETHING REAL QUICK? So the objection is not about it being new evidence. The objection to Title 17 is that it's outside the scope of the authority giving to the appeals and variance hearing officer in Title 95040 or 180 or 170. I can't remember where it is. But it's not inside. It's not for the appeals and variance hearing officer to consider. The appeals and variance hearing officers... TITLES OF DRAPER CITY MUNICIPAL CODE TO CONSIDER ARE EXCLUSIVELY WITHIN TITLE 9. AND IF IT'S AN APPEAL FROM A ZONING ADMINISTRATOR'S DECISION, A ZONING ADMINISTRATOR'S DECISION TO HEAR ITEMS COMES EXCLUSIVELY IN TITLE 9 AS WELL. SO TITLE 17 IS OUTSIDE THE JURISDICTION OF BOTH ADMINISTRATIVE BODIES UNDER THE DRAPER CITY MUNICIPAL CODE. SO AND I'M HESITANT TO MAKE A FINAL RULING ON SOMETHING LIKE THIS, BUT MY UNDERSTANDING Big picture, the question before me is really, the question is simple, the answer is more difficult. Is the property a corner lot? Basically, I think that's the only question I'm deciding. And that's an issue under Title IX. The city has cited Title XVII. So I'm going to let you argue and how that applies or relates to Title IX and how this is a corner lot. Sure, great. We argue that Title XVII is not optional when the city relies on the 2000 approval, and the city cannot have it both ways. It cannot argue that the parcel became a corner lot because of this subdivision, this Baker Cove approval. and then disclaim the standards that govern the legal consequences of that approval. That's the fundamental flaw here. If the city's theory is correct, then the 2000 action imposed new dimensional and developability consequences. Title 17 expressly requires that corner lots be platted wider and that subdivision approvals result in lots capable of reasonable improvement, and none of that occurred here. So the city can't argue and rely upon the Baker's plot subdivision subdivision here and the baker's cope approval and then deny it here in today the city identifies no code provision allowing an automatic conversion that has bypassing those requirements title 17 matters because the city's own theory relies on the action as the event that allegedly converted the parcel into a corner lot If that action imposed new corner lot consequences, then those consequences must comply with the standards that govern subdivision outcomes, including developability and corner lot configuration. We are not challenging or reopening the Baker's Cove approval. We are only responding to the city's reliance on it for their interpretation. If the city invokes the action to impose new legal consequences today, it must accept the standards that accompany that action. It must. Otherwise, they cannot use the conversion to justify their response. The city also addressed the other properties. We are not asking you to adjudicate other approvals. The references are offered solely to test the city's interpretation for internal consistencies. An interpretation that is applied differently to materially similar parcels raises a concern of administrability and uniform application under the code. That is arbitrary. The Code defines a corner lot as a parcel that abuts two intersecting streets. That is what the City is relying upon. That is what we agree with. The subject property does abut Relation Street and June Circle. This definition is unambiguous. No further analysis is required. Plats do not create or eliminate corner lots. Corner lot status arises by operation of the Code when streets are established. When June Circle was approved in 2000, the subject property abutted two streets and became a corner lot at that time. This is what the city's main statement argument is saying. The city asks you, however, to stop at a single definition and ignore the entire rest of the code. The code must be read as a coherent whole. A definition cannot be applied in a way that nullifies mandatory standards elsewhere. If abutment alone automatically converts a parcel into a corner lot, then that conversion must still comply with the standards governing corner lots, standards the city itself has adopted. If the hearing officer determines that Title 17 is irrelevant to our case, If the hearing officer also decides that the factual circumstances of the adjacent properties that we have submitted is also irrelevant, even if both of these are entirely set aside and the only thing you look at is Title IX, the city's interpretation still fails under Title IX alone. Under Title IX, the city must still identify a lawful mechanism by which this parcel's classification changed. To be clear, that lawful mechanism is a subdivision approval, a zoning action, a variance ruling. Any of these are lawful mechanisms. Otherwise, the city can willy-nilly go in and lay down pavement and change classifications of lots at will. That is what the code expressly prevents and protects against. The city must still identify a lawful mechanism by which this parcel's classification changed. Title IX defines terms, but it does not authorize automatic reclassification of lots without an implementing action or standard. Even without Title XVII, the city has already determined the parcel is legally non-conforming. That status exists to prevent later interpretations from imposing new restrictions that eliminate reasonable redevelopment. The interpretation does exactly that. I'll just add one last comment, which is why are we here? We asked the city before we bought the lot if it was what the setbacks were. And they told us it was an interior lot. They gave us interior lot setbacks. If they had have told us it was a corner lot from the very beginning, we wouldn't have bought the property. We wouldn't be sitting here. Now we're trying to develop this property. We're going to take a very aged old home. We've lived in Draper for 13 plus years. We love it here. We're going to take a very aged old home and redo it and improve. a property within Draper City and increased Draper's tax base. I'm not sure what the issue is now, but if this was a corner lot with dual setbacks, why didn't they tell us that before we bought the property? Why didn't they tell? Because none of us would be sitting here. And that old property can just sit as is forever here in Draper City, rather than having somebody come through and improve it. So at this point, if it is deemed a corner lot, it's going to be impossible to develop on a 20-foot envelope. And we'll probably, I don't know what we'll do at that point, but it definitely will decrease the value of that property. Okay, I'd just like to close again by emphasizing that this interpretation fails on every level. It fails on Title IX alone, it fails on Title XVII, and it fails on arbitrary and capricious action by the city. For purposes of DCMC section 95180 subsection D4, appellants have clearly met our burden. The zoning administrator's interpretation is not supported by substantial evidence for its essential legal conclusion, and it does not reflect a correct interpretation and application of the land use regulations when read as a whole. The interpretation treats abutment alone as dispositive. It isolates Title IX definitions from the broader ordinance, and it fails to reconcile that reading with mandatory Title XVII requirements governing corner lot configuration, developability, and legal nonconformity. In doing so, it assigns decisive legal consequences to the 2000 Baker's Cove action without analyzing whether those consequences were lawful then or can be imposed now. It produces a result that defeats the code's express protections for reasonable improvement and it applies the most restrictive possible interpretation in a manner the city itself has not uniformly applied. Even setting aside any contested exhibits, these defects are apparent on the face of the interpretation and the existing administrative record. Because the interpretation's essential legal conclusion does not follow from the evidence cited and is incorrect under a proper, PLAIN MEANING ANALYSIS OF DRAPER CITY CODE, THE APPEALENTS RESPECTFULLY REQUEST THAT THE APPEALS AND VARIANCE HEARING OFFICER REVERSE THE CORNER LOT DETERMINATION AND CONFIRM THAT THE SUBJECT PARCEL IS PROPERLY CLASSIFIED AS AN INTERIOR LOT SUBJECT TO A SINGLE FRONT YARD SETBACK FROM RELATION STREET. THANK YOU. SO YOU MENTIONED A FEW TIMES TITLE 17 AND HOW WE CAN'T JUST LOOK AT TITLE 9. When we look at Title 17, I know we've looked at the definition of corner lots, right, and that has specific setbacks. Is there any other provision or section of Title 17 other than that definition that you've been referring to? I don't believe so. Okay. This is an interesting issue. I mean, you've... I'm not making a ruling right now on the issue of a written ruling, and I haven't made up my mind yet. But I would say, you know, cities, counties, they change their land use code all the time. They change setback requirements. They change lot width requirements. they create all by themselves nonconforming lots, nonconforming structures. It happens, right? And they have, in general, the right to do that, right? And cities and counties usually have mechanisms to sort of account for that, account for those. They create inconsistencies and irregularities, right? And there are also ordinances that account for that. There's the nonconforming... structure ordinance, non-conforming use ordinance, non-conforming lot ordinance, there's variances, right? So sometimes these things happen, but there's sometimes ways to still achieve your goals regardless of whether there's a determination this is a corner lot or not. So today it's simply, is this a corner lot, I think. And I would say don't let that discourage you from continuing to do what you want to do with your property. Okay? Anything else from anybody? Okay. I don't think we have anything from the city. Did we make appearances, proper appearances? Not really. Should we do that now? Yeah, let's do that. Okay. I made my appearance. I'm Tim Pack, the hearing officer. starting with, can you state your names for the record? Jenna Ayer. Michael Ayer. Okay. And I'm Spencer Duchesne, Assistant City Attorney for the City, and I actually did make an appearance without him being asked at the beginning. I remembered. Jennifer Dostromski, Community Development Director. Todd Draper, Planning Manager. Todd Taylor, Planner. Corey Stout, Executive Assistant. Okay, great. I'm going to close the hearing. Thank you very much. I'll issue a ruling sometime next week.