Loading...
HomeMy WebLinkAboutCC - Staff Response to Applicant's Response to Staff Report for 3-3 Charlene Way From:Linda Ritter Sent:Tuesday, February 24, 2026 12:05 PM To:William Veloso; Charlene Way Cc:Clerks Comment; Bill Parsons Subject:RE: 1725 Pine - MDA H-2025-0050 Staff Report William, Thank you for your response to the staff report. Below are staff’s responses to your questions: 1) Connectivity to N. Linder Road The staff analysis references that the parcel to the east has direct connection to N. Linder Road. Based on my understanding of the parcel configuration, the property to the east (Parcel #S1211417415) does not physically frontage N. Linder Road. Staff’s Response: The Staff Report stated there is no cross-access is proposed on the east side of the subject property connecting to N. Linder Road. The statement was not intended to imply that mean that the eastern parcel presently has direct access to Linder Road. Rather, staff’s position is that, with future redevelopment consistent with the area’s commercial future land use designation, cross-access connections would be required to ultimately provide connectivity to N. Linder Road. Hopefully, this clarification confirms that the eastern parcel does not currently have direct access to N. Linder Road. Any future connection would be contingent upon redevelopment of adjacent properties and the construction of required cross-access improvements. The only parcels on this block that appear to have frontage to Linder are 1625 W Pine Ave (Parcel #S1211417407) and 737 N Linder Rd (Parcel #S1211417307). Based on prior discussions with ACHD regarding access spacing and intersection proximity standards, it is my understanding that new commercial approaches along that limited frontage area would not meet current access management criteria. Additionally, the existing development pattern along Linder does not appear to provide a practical corridor for extending cross-access to the interior parcels. Staff’s Response: Depending on how this area redevelops, the access point could be relocated further south or restricted to certain turning movements. Any such modifications would require approval by ACHD through the redevelopment process. Removing the eastern connection on your parcel would limit the future connection potential. Even when considering potential future redevelopment or parcel consolidation scenarios, I have not been able to identify a physically feasible or access-compliant pathway that would allow the eastern parcel to obtain signalized access to Linder. Staff’s Response: No signalized access to Linder Road is being proposed for this area. The reference to a signalized intersection pertained only to the existing signal at Linder Road and Pine Avenue, and the statement in the Staff Report may have been misunderstood. 1 If I am misunderstanding the connectivity scenario referenced in the staff report, I would sincerely appreciate clarification. Much of the analysis appears to rely on preserving future access to Linder Road through the eastern parcel, and I would like to ensure I fully understand how that scenario is anticipated to function under the existing parcel configuration. Staff’s Response: Preserving cross-access is a requirement of the UDC and the current development agreement includes provisions to ensure such connectivity. Gaining access to Linder Road is warranted in order to avoid a dead-end condition to the west, particularly given that the western boundary abuts a residential zoning district. 2) Procedural Timing The report also indicates the request is premature due to the absence of a concurrent development proposal. My understanding was that a Development Agreement modification could be evaluated independently where it relates to long-term access planning and parcel configuration. Staff’s Response: Modifications to the Development Agreement can be considered independently; however, any request to remove or modify cross-access must be evaluated in the context of potential redevelopment of the subject property and, potentially, surrounding parcels, to fully understand traffic circulation in the area. Staff feels the proposed modification is premature without a clear understanding of how the property will develop, which may require coordination with neighboring property owners to explore potential future plans for the area. Alternatively, you may proceed with development and provide the cross-access stubs to the neighboring parcels to the east and west as required by the current Development Agreement. If the City’s position is that such modifications should only be considered concurrently with a specific site plan, I would appreciate clarification on that procedural expectation so that I can determine next steps appropriately. Staff’s Response: It is the staff’s position that without a valid development plan, the removal or modification of the cross-access provision from the DA is premature. My goal is to ensure that whatever access configuration is ultimately pursued aligns with the City’s long-term circulation objectives while also reflecting the physical realities of the surrounding parcel layout. Staff’s Response: See the responses above Please let me know if I can be of further assistance. Linda Ritter | Associate Planner City of Meridian | Community Development Dept. 33 E. Broadway Ave., Ste. 102, Meridian, Idaho 83642 Phone: 208-884-5533 | Direct: 208-489-0573 Built for Business, Designed for Living All e-mail messages sent to or received by City of Meridian e-mail accounts are subject to the Idaho law, in regards to both release and retention, and may be released upon request, unless exempt from disclosure by law. 2 From: William Veloso <velosoliam@gmail.com> Sent: Monday, February 23, 2026 12:23 PM To: Charlene Way <cway@meridiancity.org> Cc: Linda Ritter <lritter@meridiancity.org>; Clerks Comment <comment@meridiancity.org>; Bill Parsons <bparsons@meridiancity.org> Subject: Re: 1725 Pine - MDA H-2025-0050 Staff Report External Sender - Please use caution with links or attachments. Hi Linda, Thank you for forwarding the staff report. I appreciate the time that went into reviewing the application. After reading through it carefully, I had a few clarifying questions so that I can better understand the basis for the recommendation prior to the hearing. 1) Connectivity to N. Linder Road The staff analysis references that the parcel to the east has direct connection to N. Linder Road. Based on my understanding of the parcel configuration, the property to the east (Parcel #S1211417415) does not physically frontage N. Linder Road. The only parcels on this block that appear to have frontage to Linder are 1625 W Pine Ave (Parcel #S1211417407) and 737 N Linder Rd (Parcel #S1211417307). Based on prior discussions with ACHD regarding access spacing and intersection proximity standards, it is my understanding that new commercial approaches along that limited frontage area would not meet current access management criteria. Additionally, the existing development pattern along Linder does not appear to provide a practical corridor for extending cross-access to the interior parcels. Even when considering potential future redevelopment or parcel consolidation scenarios, I have not been able to identify a physically feasible or access-compliant pathway that would allow the eastern parcel to obtain signalized access to Linder. If I am misunderstanding the connectivity scenario referenced in the staff report, I would sincerely appreciate clarification. Much of the analysis appears to rely on preserving future access to Linder Road through the eastern parcel, and I would like to ensure I fully understand how that scenario is anticipated to function under the existing parcel configuration. 2) Procedural Timing The report also indicates the request is premature due to the absence of a concurrent development proposal. My understanding was that a Development Agreement modification could be evaluated independently where it relates to long-term access planning and parcel configuration. If the City’s position is that such modifications should only be considered concurrently with a specific site plan, I would appreciate clarification on that procedural expectation so that I can determine next steps appropriately. My goal is to ensure that whatever access configuration is ultimately pursued aligns with the City’s long-term circulation objectives while also reflecting the physical realities of the surrounding parcel layout. Thank you again for your time and guidance. 3 Best, William Veloso On Mon, Feb 23, 2026 at 9:15 AM Charlene Way <cway@meridiancity.org> wrote: Thank you Charlene Charlene Way, Assistant City Clerk 33 E. Broadway Suite 104 Meridian, ID 83642 Email: cway@meridiancity.org Phone: 208-888-4433 (Remote on Friday) From: Linda Ritter <lritter@meridiancity.org> Sent: Monday, February 23, 2026 9:13 AM To: Clerks Comment <comment@meridiancity.org>; Bill Parsons <bparsons@meridiancity.org>; William Veloso <velosoliam@gmail.com> Subject: 1725 Pine - MDA H-2025-0050 Staff Report Attached is the staff report for 1725 Pine - MDA. This item is scheduled to be on the Council agenda on March 3, 2026. The public hearing will be held at City Hall, 33 E. Broadway Avenue, beginning at 6:00 pm. You may attend in person or virtually via Zoom – the link/phone number to join the meeting is located at the top of the meeting agenda. Please call or e-mail with any questions. Please submit any written response you may have to the staff report to the City Clerk’s office (comment@meridiancity.org) and me as soon as possible. If you have a presentation you’d like to present at the public hearing, please send it to the City Clerk’s office no later than 12:00 pm the day of the hearing. 4 Linda Ritter | Associate Planner City of Meridian | Community Development Dept. 33 E. Broadway Ave., Ste. 102, Meridian, Idaho 83642 Phone: 208-884-5533 | Direct: 208-489-0573 Built for Business, Designed for Living All e-mail messages sent to or received by City of Meridian e-mail accounts are subject to the Idaho law, in regards to both release and retention, and may be released upon request, unless exempt from disclosure by law. 5