WEBVTT

00:00:00.000 --> 00:00:15.460
 Good morning, and we are here for a joint meeting of the City Council on Planning and

00:00:15.460 --> 00:00:16.880
 Zoning Commission.

00:00:16.880 --> 00:00:20.560
 It is Monday, February 14th, Happy Valentine's Day.

00:00:20.560 --> 00:00:22.200
 It is 10 a.m.

00:00:22.200 --> 00:00:28.320
 We do have a quorum, so I'll call the meeting to order and then turn it over to the P&Z

00:00:28.320 --> 00:00:29.320
 chair.

00:00:29.320 --> 00:00:30.840
 Thank you, Mayor.

00:00:30.840 --> 00:00:35.040
 Yes, good morning, everyone, and Happy Valentine's Day.

00:00:35.040 --> 00:00:38.680
 With the quorum present with the Commission, I will call the Commission to order at 10

00:00:38.680 --> 00:00:39.680
 a.m.

00:00:39.680 --> 00:00:40.680
 Great.

00:00:40.680 --> 00:00:44.160
 And so we have one thing, one item on our agenda, and we'll follow the same kind of

00:00:44.160 --> 00:00:45.160
 format.

00:00:45.160 --> 00:00:46.160
 Well, we'll reverse the format.

00:00:46.160 --> 00:00:53.720
 What I'll do is kind of defer to P&Z for questions first, and then we'll follow that

00:00:53.720 --> 00:00:58.580
 up at each break or each point of questions.

00:00:58.580 --> 00:01:05.360
 So the first item today is, and our only item, is item A, ID 22036, Receive Report and Hold

00:01:05.360 --> 00:01:11.640
 Discussion, Give Staff Direction, regarding the Denton 2040 Comprehensive Plan update and

00:01:11.640 --> 00:01:23.600
 the Draft 2022 Mobility Plan for the City of Denton.

00:01:23.600 --> 00:01:24.600
 Good morning.

00:01:24.600 --> 00:01:25.600
 Happy Valentine's Day.

00:01:25.600 --> 00:01:26.600
 Morning.

00:01:26.600 --> 00:01:27.600
 Becky Devaney.

00:01:27.600 --> 00:01:31.080
 I think I know most all of you.

00:01:31.080 --> 00:01:34.240
 Thank you for, number one, coming together today.

00:01:34.240 --> 00:01:38.320
 This is a very exciting time for our entire staff.

00:01:38.320 --> 00:01:42.360
 I don't know that I've ever been in this type of scenario before where Planning and Zoning

00:01:42.360 --> 00:01:47.640
 and City Council is all together, but what a great opportunity for us to share some of

00:01:47.640 --> 00:01:52.800
 the updates and comments we've received from both of you and really work through those.

00:01:52.800 --> 00:01:59.200
 So with that, I am going to get started.

00:01:59.200 --> 00:02:12.600
 I'm going to share my screen and start this slideshow.

00:02:12.600 --> 00:02:17.680
 There's always too many things on the screen.

00:02:17.680 --> 00:02:25.600
 Alrighty, so myself, Nathan George, and Pritam Deshmukh have worked together on this Draft

00:02:25.600 --> 00:02:28.520
 2022 Mobility Plan update.

00:02:28.520 --> 00:02:33.460
 Like I mentioned, I know in the meetings last week, both Tuesday and Wednesday, we received

00:02:33.460 --> 00:02:34.820
 a number of comments.

00:02:34.820 --> 00:02:36.960
 We thank you so much for your comments.

00:02:36.960 --> 00:02:38.760
 I know you all know this.

00:02:38.760 --> 00:02:46.440
 I know the comment and time to give comments has been happening for a number of years.

00:02:46.440 --> 00:02:50.360
 I just want to remind you, there have been presentations dating back on the Mobility

00:02:50.360 --> 00:02:56.200
 Plan all the way to 2019, so we've had lots of opportunities to come before Council and

00:02:56.200 --> 00:02:57.200
 Planning and Zoning.

00:02:57.200 --> 00:03:02.200
 I know there's been several presentations being that that was, in some cases, the more

00:03:02.200 --> 00:03:03.200
 virtual world.

00:03:03.200 --> 00:03:07.760
 I know today we're doing that hybrid world, but I don't believe that we would be moving

00:03:07.760 --> 00:03:13.200
 forward in this process unless we had that input that we received from all of you.

00:03:13.200 --> 00:03:18.040
 I know Eric has had a lot of questions, Commissioner Pruitt, we definitely appreciate that.

00:03:18.040 --> 00:03:21.960
 I know there's been lots of questions from you, Councilmember Davis, and from each and

00:03:21.960 --> 00:03:26.120
 every one of you that have given us this opportunity to come before you today.

00:03:26.120 --> 00:03:30.840
 So I just want to move forward and talk to you a little bit about our overview.

00:03:30.840 --> 00:03:37.600
 We're going to go through goal number one, safety first, previously goal number seven.

00:03:37.600 --> 00:03:39.080
 Talk about some focus areas.

00:03:39.080 --> 00:03:44.360
 We had a lot of comments that we had last presentation talking about some of those focus

00:03:44.360 --> 00:03:49.240
 areas we wanted to look in at, and I'm thankful that you brought those up because staff did

00:03:49.240 --> 00:03:53.400
 have that opportunity to go back and do a deeper dive and have made some modifications

00:03:53.400 --> 00:03:55.000
 based on some of the comments we received.

00:03:55.000 --> 00:03:57.880
 So I want to take the time to highlight those for you.

00:03:57.880 --> 00:04:03.080
 I want to show you an example at the very end of a project that uses a more phased approach

00:04:03.080 --> 00:04:07.920
 for construction just to kind of help everyone understand the overall goal, and then talk

00:04:07.920 --> 00:04:10.760
 about some next steps.

00:04:10.760 --> 00:04:18.880
 So in your backup, I know you received this as an ISR on Friday in your Friday report,

00:04:18.880 --> 00:04:22.720
 and I know Planning and Zoning was also receiving a copy of it.

00:04:22.720 --> 00:04:27.640
 So the first thing we heard from everyone was really to change, obviously, goal number

00:04:27.640 --> 00:04:28.820
 seven to number one.

00:04:28.820 --> 00:04:30.840
 I think we've all got that.

00:04:30.840 --> 00:04:38.120
 But then work forward to have the language be more proactive, and I use the word aggressive,

00:04:38.120 --> 00:04:39.880
 but I don't think that that's a negative term.

00:04:39.880 --> 00:04:43.040
 I think it's the right term to use.

00:04:43.040 --> 00:04:50.080
 And so we've worked through changing the order of which some of those strategies are aligned.

00:04:50.080 --> 00:04:56.680
 We've also worked through updating objective number 1A and making that not have so much

00:04:56.680 --> 00:05:02.000
 detail, but then make sure that everyone understands that safety is the number one priority for

00:05:02.000 --> 00:05:06.440
 planning, designing, and maintaining the roadway infrastructure and the entire transportation

00:05:06.440 --> 00:05:07.440
 network.

00:05:07.440 --> 00:05:12.040
 I'll highlight a couple of more on strategy 1.1.

00:05:12.040 --> 00:05:17.120
 And we really did talk about Ditten's highest priority is protection of human life over

00:05:17.120 --> 00:05:21.680
 other aspects involved in that planning and design operation.

00:05:21.680 --> 00:05:23.800
 Strategy 1.2, we also changed.

00:05:23.800 --> 00:05:25.240
 It said manage.

00:05:25.240 --> 00:05:31.880
 We changed that word to design, evaluate, operate, and enforce safe speeds.

00:05:31.880 --> 00:05:34.640
 And there are a few others that we worked through.

00:05:34.640 --> 00:05:40.000
 I will tell you, 1.4, we also worked through that acknowledge vulnerability of non-auto

00:05:40.000 --> 00:05:45.940
 users and enhance safety through planning, design, evaluation, and operation of the transportation

00:05:45.940 --> 00:05:47.520
 network.

00:05:47.520 --> 00:05:49.960
 Not going to read every single one of these for you.

00:05:49.960 --> 00:05:54.000
 Just wanted you to see the changes that we've made to the language.

00:05:54.000 --> 00:05:59.120
 If there's additional comments you have or additional changes that you might recommend,

00:05:59.120 --> 00:06:01.840
 obviously, we'd like to hear those.

00:06:01.840 --> 00:06:08.040
 But really wanted to take to heart what you told us and what your recommendations were

00:06:08.040 --> 00:06:12.640
 and express that we did have that opportunity to go back and look and hope that we've met

00:06:12.640 --> 00:06:18.120
 the mark with addressing some of those comments we received.

00:06:18.120 --> 00:06:22.880
 I'm going to move off the specific goal because the next comments we received were in regards

00:06:22.880 --> 00:06:25.240
 to looking at focus areas.

00:06:25.240 --> 00:06:29.160
 As I mentioned, we're going to talk about three different focus areas.

00:06:29.160 --> 00:06:31.640
 Northeast Denton is interesting.

00:06:31.640 --> 00:06:37.920
 Took the time to take the land use map and put that behind the actual mobility plan.

00:06:37.920 --> 00:06:42.600
 I think it helps share the story a little bit better of what's going on in this area.

00:06:42.600 --> 00:06:47.920
 As you can see, quite a bit of the land is within the ETJ.

00:06:47.920 --> 00:06:50.200
 You can also see the city limits.

00:06:50.200 --> 00:06:54.100
 Of course, there's large waterway structures through this area.

00:06:54.100 --> 00:06:57.840
 I want to point out one thing that's really important, and we're going to deeper dive

00:06:57.840 --> 00:07:03.880
 into this area through the series of slides, but one thing I really want to point out is

00:07:03.880 --> 00:07:10.800
 if you look at it, the black road that you see here, the black road you see here, the

00:07:10.800 --> 00:07:18.460
 black road you see here, and then, of course, Loop 288 that comes down to 380, which I hope

00:07:18.460 --> 00:07:23.920
 that I'm on the right area, there I am because I can't see because there's this beautiful

00:07:23.920 --> 00:07:27.520
 little thing telling me about Zoom in my way.

00:07:27.520 --> 00:07:35.240
 This 380 area here that then connects to Loop 288, and then also FM 2164.

00:07:35.240 --> 00:07:37.120
 All of those are textile roadways.

00:07:37.120 --> 00:07:42.640
 All of those are roadways that really, as we work through this entire process, we wanted

00:07:42.640 --> 00:07:47.180
 to make sure that you understand there's not a whole lot of input or say that the city

00:07:47.180 --> 00:07:51.500
 has minus one, and I'll show you the difference that's happened on that roadway.

00:07:51.500 --> 00:07:53.040
 Just wanted to highlight that area.

00:07:53.040 --> 00:08:05.120
 I'm going to move on to, and I guess, I'm sorry, I just pressed the next button.

00:08:05.120 --> 00:08:06.360
 From there, you can see.

00:08:06.360 --> 00:08:10.760
 Now we've taken that opportunity to make those all very dark.

00:08:10.760 --> 00:08:15.620
 Like I mentioned, the 2164, 380, FM 428.

00:08:15.620 --> 00:08:20.900
 This was the integrated corridor, you see Loop 288, you see 380, and then of course

00:08:20.900 --> 00:08:27.480
 that connective piece that's to be constructed by TechStop between 380 and Loop 288.

00:08:27.480 --> 00:08:30.640
 Let's move on and go to the next area.

00:08:30.640 --> 00:08:34.620
 The reason why I wanted to share this with you is so that you could see.

00:08:34.620 --> 00:08:41.200
 The original adopted currently, 2015 mobility plan, has a lot of different roadway networks

00:08:41.200 --> 00:08:43.000
 and it's shaped a little bit differently.

00:08:43.000 --> 00:08:47.040
 The schematics and the graphics that you see are quite different.

00:08:47.040 --> 00:08:52.040
 If you look at the current draft mobility plan that you can see, Cooper Creek was one

00:08:52.040 --> 00:08:58.960
 of the roadways that had some questions about it, along with Hartley Field Road, and then

00:08:58.960 --> 00:09:00.720
 also Collins Road.

00:09:00.720 --> 00:09:06.280
 Also, this integrated corridor did not exist in that time of the 2015 mobility plan.

00:09:06.280 --> 00:09:08.000
 For me, I'm very visual.

00:09:08.000 --> 00:09:11.360
 It helps me very much to see these two compared side by side.

00:09:11.360 --> 00:09:15.600
 I hope that helps you also, but you can see the drastic changes that have been made from

00:09:15.600 --> 00:09:20.580
 the 2015 to the 2022 draft mobility plan.

00:09:20.580 --> 00:09:26.480
 I next want to walk through and show you that we appreciate your comments, and the reason

00:09:26.480 --> 00:09:30.840
 why I wanted to show this to you all side by side is after staff went back and reviewed

00:09:30.840 --> 00:09:36.000
 and had a lot of conversations and talked about really what is the purpose of Cooper

00:09:36.000 --> 00:09:40.980
 Creek Road, what is the purpose of Collins Road, and let's talk about that integrated

00:09:40.980 --> 00:09:41.980
 corridor.

00:09:41.980 --> 00:09:44.800
 We went back to our friends at TxDOT and said, "Tell us a little more.

00:09:44.800 --> 00:09:46.220
 Let's talk about this."

00:09:46.220 --> 00:09:49.840
 This has been going through a feasibility study for a period of time.

00:09:49.840 --> 00:09:54.120
 What I present before you today are the changes that our staff would like to make for the

00:09:54.120 --> 00:09:58.440
 revised draft 2022 mobility plan.

00:09:58.440 --> 00:09:59.440
 That's a mouthful.

00:09:59.440 --> 00:10:03.880
 As you can tell, of course, all these TxDOT roadways still exist, right?

00:10:03.880 --> 00:10:11.880
 The outer loop still exists, 2164 still exists, Loop 288, 380, the connective tissue between

00:10:11.880 --> 00:10:14.360
 380 and Loop 288.

00:10:14.360 --> 00:10:16.600
 All of those are still TxDOT roadways.

00:10:16.600 --> 00:10:18.020
 Same with 428.

00:10:18.020 --> 00:10:20.440
 We all know that's the roadway that we all take to Aubrey.

00:10:20.440 --> 00:10:25.960
 I'll be taking at 5 o'clock today to go watch my son play baseball in Aubrey.

00:10:25.960 --> 00:10:29.840
 What I will tell you is what we've learned, and I'm going to first highlight the road

00:10:29.840 --> 00:10:32.040
 that we've highlighted in red.

00:10:32.040 --> 00:10:35.000
 TxDOT is no longer considering the integrated corridor.

00:10:35.000 --> 00:10:37.120
 I know I've mentioned this a few times.

00:10:37.120 --> 00:10:41.400
 They're focusing in on the outer loop, which is this roadway you see here, and then, of

00:10:41.400 --> 00:10:44.800
 course, 380, which is this roadway you see here.

00:10:44.800 --> 00:10:48.840
 The improvements that TxDOT is going to make in this area based on their traffic studies

00:10:48.840 --> 00:10:53.720
 and the way that we understand it today is to connect this outer loop piece, which I

00:10:53.720 --> 00:10:58.160
 showed you in the previous presentation, how that aligned directly with the roadway that

00:10:58.160 --> 00:11:00.880
 is connected to Collin County.

00:11:00.880 --> 00:11:07.420
 And then, of course, 380, TxDOT is looking at making altercations to 380 as they anticipate

00:11:07.420 --> 00:11:11.760
 up to 80,000 additional cars going through this area.

00:11:11.760 --> 00:11:15.640
 I've been told it's comparable to the size of Richardson that they're anticipating with

00:11:15.640 --> 00:11:18.160
 the growth to be along 380.

00:11:18.160 --> 00:11:21.960
 So the modifications that TxDOT will make are to that outer loop and that integrated

00:11:21.960 --> 00:11:24.800
 corridor -- I'm sorry, the 380.

00:11:24.800 --> 00:11:28.040
 This gives us the opportunity on the integrated corridor to look at it through a little bit

00:11:28.040 --> 00:11:32.120
 different lens, because now it'll be a definition and a conversation between the county and

00:11:32.120 --> 00:11:33.360
 the city.

00:11:33.360 --> 00:11:36.920
 So staff went back and looked at it, reviewed it with our partners at the county and our

00:11:36.920 --> 00:11:41.160
 partners at TxDOT, and believe that the best thing to do at this time is to change that

00:11:41.160 --> 00:11:46.200
 roadway classification from that interstate freeway that we previously showed to make

00:11:46.200 --> 00:11:48.400
 that a primary arterial.

00:11:48.400 --> 00:11:51.640
 Keep in mind, that's still 135 feet of rideway.

00:11:51.640 --> 00:11:53.520
 It's still a six-lane roadway.

00:11:53.520 --> 00:11:59.640
 I will show you an example of 135-foot rideway that was actually built to a smaller cross-section

00:11:59.640 --> 00:12:00.640
 here later.

00:12:00.640 --> 00:12:02.820
 I'm at the end of the presentation.

00:12:02.820 --> 00:12:07.120
 But the primary arterial in this area obviously is still schematic in nature, but it does

00:12:07.120 --> 00:12:11.480
 change it from that freeway classification to that arterial.

00:12:11.480 --> 00:12:14.840
 The next roadway I want to highlight is Cooper Creek Road.

00:12:14.840 --> 00:12:20.160
 After staff went back and evaluated, looked at the areas of which was in the ETJ, the

00:12:20.160 --> 00:12:25.160
 areas where they were within the city limits, and also the cross-section looking at where

00:12:25.160 --> 00:12:29.480
 it would be crossing creeks, et cetera, and the alignment.

00:12:29.480 --> 00:12:33.720
 Staff feels like it's the best thing to make that instead of a primary arterial.

00:12:33.720 --> 00:12:37.640
 As you can see, the recommendation would be to a secondary arterial cross-section, which

00:12:37.640 --> 00:12:40.400
 is 110-foot rideway.

00:12:40.400 --> 00:12:45.880
 It still provides that connectivity from 380 all the way due north.

00:12:45.880 --> 00:12:52.280
 We obviously know we have 2164 and we have FM428 that are also getting to those areas

00:12:52.280 --> 00:13:00.240
 outside of town, but we felt like it was best to lower that based on the data and the evaluation

00:13:00.240 --> 00:13:02.200
 that we performed.

00:13:02.200 --> 00:13:07.800
 And finally, as you can see, Harleyfield Road we have as that secondary arterial, but the

00:13:07.800 --> 00:13:10.600
 other change that we made was to Collins.

00:13:10.600 --> 00:13:15.760
 And on Collins, we felt like really based on the land use in that area, the location

00:13:15.760 --> 00:13:22.320
 that it is, that it was best to evaluate that and change that from being a collector, I'm

00:13:22.320 --> 00:13:25.880
 sorry, bringing a secondary arterial to being a collector.

00:13:25.880 --> 00:13:30.500
 So those are the three major changes that staff has evaluated based on the comments

00:13:30.500 --> 00:13:38.240
 we received to revise and send these comments back for our consultant to make those modifications

00:13:38.240 --> 00:13:40.280
 to the mobility plan.

00:13:40.280 --> 00:13:48.560
 So just to re-highlight, Cooper Creek Road from a primary arterial to a secondary arterial,

00:13:48.560 --> 00:13:56.160
 Collins Road from a right here showing a secondary arterial to a collector, and then of course

00:13:56.160 --> 00:14:01.200
 the integrated corridor no longer being a freeway, being a primary arterial.

00:14:01.200 --> 00:14:06.680
 So we felt like with the comments that we received and the data that we did, the evaluation

00:14:06.680 --> 00:14:11.120
 we did looking at, like I mentioned, the ETJ, the city limits, and the growth patterns in

00:14:11.120 --> 00:14:16.360
 this area, and those connective pieces between the TxDOT roadways, that that would be the

00:14:16.360 --> 00:14:19.600
 best way to move forward.

00:14:19.600 --> 00:14:26.360
 So I'm going to go from Northeast Denton, and as you can see, same thing again.

00:14:26.360 --> 00:14:30.360
 Look at all of the TxDOT roadway network that's in that area.

00:14:30.360 --> 00:14:34.740
 I think you've heard me say this before, but when I started with City of Denton in 2001,

00:14:34.740 --> 00:14:38.800
 the first time I was here, we had seven TxDOT roadways that go through the city.

00:14:38.800 --> 00:14:45.240
 We now have six, being that McKinney is now a city roadway, but, you know, Denton is unique

00:14:45.240 --> 00:14:51.560
 in the fact that it has so many roadways that are TxDOT that actually go through the city.

00:14:51.560 --> 00:14:53.000
 All righty.

00:14:53.000 --> 00:14:57.400
 So the next focus area we wanted to look at is Southeast Denton.

00:14:57.400 --> 00:15:00.720
 Same type of conversation, really looking at the focus areas.

00:15:00.720 --> 00:15:06.880
 I know there's a lot of conversations about Morris Street, Woodrow, Shady Oaks, really

00:15:06.880 --> 00:15:12.920
 in that area, and the purpose of this map is really to focus in on the fact that the

00:15:12.920 --> 00:15:17.300
 majority of the roadways in this area are already classified.

00:15:17.300 --> 00:15:19.880
 They're already shown to what their status is.

00:15:19.880 --> 00:15:22.040
 They're not proposed roadways.

00:15:22.040 --> 00:15:28.180
 I will tell you, they may not be functioning or constructed to their current classification,

00:15:28.180 --> 00:15:36.080
 but that's where staff would evaluate a roadway like Morris, see that it's shown as a collector,

00:15:36.080 --> 00:15:40.060
 and look at if there's modifications that need to be made to that cross section to make

00:15:40.060 --> 00:15:47.680
 it more of an alignment with what a typical collector cross section would be.

00:15:47.680 --> 00:15:51.080
 So just wanted to take that opportunity to show there's not a lot of proposed roadways

00:15:51.080 --> 00:15:52.940
 in Southeast Denton.

00:15:52.940 --> 00:15:58.320
 You know, the majority of them are roadways minus Dutchess, that's an extension from loop

00:15:58.320 --> 00:15:59.320
 288.

00:15:59.320 --> 00:16:06.480
 The majority of those roadways are already existing and currently in their configuration.

00:16:06.480 --> 00:16:10.300
 Moving on, wanted to focus in on Southwest Denton.

00:16:10.300 --> 00:16:14.400
 As you are probably familiar with, this is the Hunter Cole development.

00:16:14.400 --> 00:16:20.760
 Really what I want to hone in on here is just to mention to you that staff has ongoing conversations.

00:16:20.760 --> 00:16:26.420
 We meet with Hunter on Mondays and Coles on Thursdays every other week.

00:16:26.420 --> 00:16:29.460
 We have constant conversation with those teams.

00:16:29.460 --> 00:16:34.640
 We're evaluating a lot of the roadways that they are bringing forward to us and looking

00:16:34.640 --> 00:16:39.600
 at different changes that they're anticipating being made or that they recommend.

00:16:39.600 --> 00:16:44.020
 But keep in mind, this is a master plan community that already has an agreement that's gone

00:16:44.020 --> 00:16:45.020
 through the city.

00:16:45.020 --> 00:16:49.480
 And so there are roadway networks that have to be constructed as a part of those agreements

00:16:49.480 --> 00:16:51.320
 and a part of those processes.

00:16:51.320 --> 00:16:55.480
 So anything that they bring forward that they want to make a modification on, we have to

00:16:55.480 --> 00:16:59.840
 have that data to support it, including that traffic study information.

00:16:59.840 --> 00:17:05.100
 I will mention to you two roadways that you see highlighted in red that are being removed.

00:17:05.100 --> 00:17:09.160
 Obviously, this connection piece was an existing connection.

00:17:09.160 --> 00:17:16.080
 When this new roadway is built right here, this is Underwood and 2449.

00:17:16.080 --> 00:17:21.260
 So when you see this little connection piece, it did not make sense to keep that anymore.

00:17:21.260 --> 00:17:25.080
 So we will be eliminating that because now the roadway will head north.

00:17:25.080 --> 00:17:29.160
 The other roadway is this roadway that you see that abuts basically Robeson Ranch that

00:17:29.160 --> 00:17:34.620
 separates Hunter, I'm sorry, the Hunter Ranch from Robeson Ranch.

00:17:34.620 --> 00:17:40.200
 That was a roadway that staff was already removing from the overall documents.

00:17:40.200 --> 00:17:45.920
 So just wanted to highlight that those two roadways are being removed.

00:17:45.920 --> 00:17:49.620
 So this is the project I promised you at the end that I would show you.

00:17:49.620 --> 00:17:53.260
 This is really a phased approach to construction of arterials.

00:17:53.260 --> 00:17:57.000
 For those of you who don't know, this is Mayhill Road.

00:17:57.000 --> 00:18:01.320
 And so really what I wanted to focus in on, it dedicated the ultimate right of way.

00:18:01.320 --> 00:18:06.560
 For those of you who have driven it, you know what a beautiful roadway it is.

00:18:06.560 --> 00:18:10.560
 Of course, I'm always going to say construction is beautiful because I love it.

00:18:10.560 --> 00:18:16.040
 But, you know, we constructed that required sized facility that was based on the current

00:18:16.040 --> 00:18:17.640
 capacity, right?

00:18:17.640 --> 00:18:21.360
 So it is an ultimate cross section of a primary arterial.

00:18:21.360 --> 00:18:26.640
 But as it's functioning today, it's constructed to that secondary arterial.

00:18:26.640 --> 00:18:30.440
 And when we have that opportunity and when the opportunity exists based on the traffic

00:18:30.440 --> 00:18:36.040
 demands and the needs in the area and the traffic studies that are created, then we

00:18:36.040 --> 00:18:39.180
 have that opportunity to widen towards the median.

00:18:39.180 --> 00:18:41.940
 So additional right of way won't be required.

00:18:41.940 --> 00:18:45.920
 It still will be the 135 foot for the most part.

00:18:45.920 --> 00:18:49.900
 There may be some additional right of way, of course, sometimes that are needed at intersections.

00:18:49.900 --> 00:18:54.720
 But what I wanted to show you is we have that opportunity with the medians to actually restripe

00:18:54.720 --> 00:19:00.960
 and make this a three lane in each direction, six lane primary arterial at the time that's

00:19:00.960 --> 00:19:01.960
 necessary.

00:19:01.960 --> 00:19:04.460
 So I thought this was a really good case study.

00:19:04.460 --> 00:19:10.320
 And I appreciate our team really working to develop this and show it for you to show you.

00:19:10.320 --> 00:19:12.920
 You can dedicate the ultimate right of way.

00:19:12.920 --> 00:19:17.960
 You can have that line on the map that says eventually at some time down the road, this

00:19:17.960 --> 00:19:22.340
 is going to be a primary arterial and you can have the data to support that it only

00:19:22.340 --> 00:19:25.260
 needs to be a secondary arterial at this time.

00:19:25.260 --> 00:19:31.280
 So just wanted to show you a real life situation that's happening to date.

00:19:31.280 --> 00:19:36.660
 So next steps, obviously, you know, it's critical that we work to a step to adopt the mobility

00:19:36.660 --> 00:19:40.960
 plan so that we can work forward with doing those roadway impact fees.

00:19:40.960 --> 00:19:44.840
 And we currently have that slated to bring back to you in the springtime.

00:19:44.840 --> 00:19:48.920
 The Vision Zero framework, that's something we're working with Pre-Tim on.

00:19:48.920 --> 00:19:54.160
 And he's taking the lead on that between transportation planning and our engineering team.

00:19:54.160 --> 00:19:58.420
 And we plan on bringing that back in the May, June timeframe.

00:19:58.420 --> 00:20:02.560
 And then, of course, that citywide speed study, Nathan is leading that effort.

00:20:02.560 --> 00:20:06.720
 And that's something that you will finally see come forward to you towards late summer,

00:20:06.720 --> 00:20:08.700
 so August, September timeframe.

00:20:08.700 --> 00:20:12.460
 So just explaining to you that I know a lot of the conversations we've had have been related

00:20:12.460 --> 00:20:18.100
 to speed, Vision Zero, and ultimately knowing that in order to adopt the mobility plan and

00:20:18.100 --> 00:20:22.400
 move forward, then the next steps will be really working through these three different

00:20:22.400 --> 00:20:27.160
 big task items that our teams are working through.

00:20:27.160 --> 00:20:30.480
 And with that, I will end the presentation.

00:20:30.480 --> 00:20:35.680
 And there were several of us that are here and can answer any questions that you might

00:20:35.680 --> 00:20:36.680
 have.

00:20:36.680 --> 00:20:37.960
 And I appreciate the time.

00:20:37.960 --> 00:20:43.120
 I do want to just mention to you that we're still obviously wanting to take any comments

00:20:43.120 --> 00:20:44.320
 or questions that you have.

00:20:44.320 --> 00:20:49.040
 That's what we're here for, is to listen to you, try to understand what your requests

00:20:49.040 --> 00:20:54.860
 are, what your concerns are, and work through that process to get the mobility plan adopted.

00:20:54.860 --> 00:20:59.720
 So I appreciate so much you taking that opportunity to join each other together on Valentine's

00:20:59.720 --> 00:21:03.000
 Day, and for us to take this time to have this meeting.

00:21:03.000 --> 00:21:05.960
 So Mayor, I'll turn it over to you, sir.

00:21:05.960 --> 00:21:07.040
 No, thank you very much.

00:21:07.040 --> 00:21:14.960
 And so just as I turn it over to PNZ commissioners, I would just ask that we give, maximize the

00:21:14.960 --> 00:21:18.840
 time we have with staff here, and give direction.

00:21:18.840 --> 00:21:27.480
 State an issue, state a suggestion as change, suggested change, adjustment, etc., etc.,

00:21:27.480 --> 00:21:33.720
 so that everyone at the dais and online can understand what you're proposing, and react

00:21:33.720 --> 00:21:40.760
 to that, and try to drive toward consensus to then, again, move us towards adopting this.

00:21:40.760 --> 00:21:46.960
 So again, if we can set aside some of the narratives for right now, and focus on giving

00:21:46.960 --> 00:21:52.000
 staff direction while they're here, and then we can get into those things later, or in

00:21:52.000 --> 00:21:53.560
 a different way.

00:21:53.560 --> 00:21:58.520
 But while we have staff here, I'd love to get direction kind of pared down, and give

00:21:58.520 --> 00:22:03.880
 them next steps so that they can make adjustments, and bring it to us for a vote.

00:22:03.880 --> 00:22:05.380
 Commissioner Nellis?

00:22:05.380 --> 00:22:06.380
 Thank you, Mayor.

00:22:06.380 --> 00:22:11.840
 Becky, thank you to you and your team, as always, for working so hard on this.

00:22:11.840 --> 00:22:21.000
 Any questions for staff at this time?

00:22:21.000 --> 00:22:22.000
 Commissioner Pruitt?

00:22:22.000 --> 00:22:24.000
 Thank you, Chair.

00:22:24.000 --> 00:22:30.680
 Some of these buttons work a little different than others.

00:22:30.680 --> 00:22:37.080
 Just real briefly, is there any proposed change to that roadway classifications table within

00:22:37.080 --> 00:22:41.920
 the mobility plan at this time from staff?

00:22:41.920 --> 00:22:44.720
 Could you give me a little bit more information?

00:22:44.720 --> 00:22:49.360
 It's that table that describes the function of different roadway classifications, their

00:22:49.360 --> 00:22:52.360
 proposed width, their speed, that sort of thing.

00:22:52.360 --> 00:22:55.440
 Sure, the blue one that has the white text.

00:22:55.440 --> 00:23:00.760
 So like I mentioned during planning and zoning, we are not gonna recommend changing that chart.

00:23:00.760 --> 00:23:04.080
 What we are going to recommend is adding some additional, and I appreciate you bringing

00:23:04.080 --> 00:23:09.520
 that up to me, adding some additional verbiage to explain that these are parameters of which

00:23:09.520 --> 00:23:15.280
 typical designs are done, but that the actual traffic studies and actual design parameters

00:23:15.280 --> 00:23:20.040
 are going to be put on that design engineer and have city staff input really through the

00:23:20.040 --> 00:23:22.440
 evaluation process of those roadways.

00:23:22.440 --> 00:23:27.400
 So those are really just kind of the bumpers, you know, kind of the standards that align

00:23:27.400 --> 00:23:32.060
 with those standard details, but definitely going to add some verbiage at the end really

00:23:32.060 --> 00:23:34.540
 to explain that that's the purpose of it.

00:23:34.540 --> 00:23:43.720
 So it's not seen as thou shalt do X and B, so cookie cutter, if that will help with the

00:23:43.720 --> 00:23:44.720
 concerns.

00:23:44.720 --> 00:23:45.720
 Yeah, I think that does.

00:23:45.720 --> 00:23:49.320
 I just, it was a very big departure from the similar chart that was shared with council

00:23:49.320 --> 00:23:57.800
 at work session back in early 2020 that really kind of showed the difference of those roadway

00:23:57.800 --> 00:24:01.560
 classification uses from a rural to a suburban to an urban context.

00:24:01.560 --> 00:24:04.720
 So I wanted to make sure that that was going to be incorporated.

00:24:04.720 --> 00:24:05.720
 Thank you.

00:24:05.720 --> 00:24:06.720
 Absolutely sir.

00:24:06.720 --> 00:24:07.720
 Thank you.

00:24:07.720 --> 00:24:08.720
 Commissioner Anderson.

00:24:08.720 --> 00:24:09.720
 Thank you chair.

00:24:09.720 --> 00:24:10.720
 Good afternoon city council.

00:24:10.720 --> 00:24:22.600
 I did have a question about Hartley Field Road through many of our PNZ meetings with

00:24:22.600 --> 00:24:27.480
 the development that's going on to the west of Hartley Field.

00:24:27.480 --> 00:24:32.920
 Many residents have come in front of us and sent us emails about not wanting to connect

00:24:32.920 --> 00:24:35.720
 Hartley Field Road and make it a major thoroughfare.

00:24:35.720 --> 00:24:39.400
 But did I hear correctly that that is what the cities want to do because the developer

00:24:39.400 --> 00:24:44.520
 said they didn't have any plans in developing or connecting their neighborhood into Hartley

00:24:44.520 --> 00:24:45.520
 Field.

00:24:45.520 --> 00:24:51.600
 The current plan of the mobility plan is to show that roadway as a secondary arterial,

00:24:51.600 --> 00:24:58.480
 which would be 110 foot wide cross section that could be built to a two lane each direction

00:24:58.480 --> 00:25:01.040
 or four lane total roadway.

00:25:01.040 --> 00:25:04.920
 That obviously would be something that as that development comes through that staff

00:25:04.920 --> 00:25:11.480
 will be evaluating and having those conversations based on the traffic demands in that area.

00:25:11.480 --> 00:25:17.600
 Could they not, could the city not look at building that road just behind Hartley Field

00:25:17.600 --> 00:25:18.600
 just to the north of it?

00:25:18.600 --> 00:25:21.840
 Because that's what many residents said because that neighborhood has already developed.

00:25:21.840 --> 00:25:24.720
 It's a rural development.

00:25:24.720 --> 00:25:29.720
 Kids are playing out in the streets and they don't want major traffic flow through their

00:25:29.720 --> 00:25:30.720
 neighborhood.

00:25:30.720 --> 00:25:32.720
 I mean, many of them spoke about that.

00:25:32.720 --> 00:25:33.720
 Sure.

00:25:33.720 --> 00:25:38.360
 Staff has that opportunity to evaluate the actual alignment of that roadway and where

00:25:38.360 --> 00:25:43.000
 that actually will be located at the time that those developments come through.

00:25:43.000 --> 00:25:47.900
 So if that is just a little bit north, I know there was a little bit of a gap in between

00:25:47.900 --> 00:25:50.600
 the existing homes.

00:25:50.600 --> 00:25:54.840
 If I'm remembering correctly what you're referring to, sir, there was a gap between where the

00:25:54.840 --> 00:25:58.840
 existing homes were, where Hartley Field Road was, and then the development to the north

00:25:58.840 --> 00:25:59.920
 of that location.

00:25:59.920 --> 00:26:06.440
 So where that actual alignment goes for that roadway specifically, it's currently aligned

00:26:06.440 --> 00:26:10.360
 in the existing roadway network that is in that area.

00:26:10.360 --> 00:26:16.860
 That's a typical situation is to align an actual roadway with the existing line that's

00:26:16.860 --> 00:26:21.800
 on the ground, but based on when that development comes through, we do have that opportunity

00:26:21.800 --> 00:26:27.440
 to be flexible to move that roadway either north or south to align with what makes sense

00:26:27.440 --> 00:26:29.020
 for that overall development.

00:26:29.020 --> 00:26:33.360
 At this point, it's a schematic that shows that yes, there is a need for a secondary

00:26:33.360 --> 00:26:36.720
 arterial in that area, if that makes sense.

00:26:36.720 --> 00:26:37.720
 It does.

00:26:37.720 --> 00:26:38.720
 Thank you.

00:26:38.720 --> 00:26:44.720
 But I just want, I don't know if y'all have heard all the people, all the people's comments

00:26:44.720 --> 00:26:48.880
 that live in Hartley Field, but they are not wanting a major thoroughfare through their

00:26:48.880 --> 00:26:49.880
 neighborhood.

00:26:49.880 --> 00:26:50.880
 I'm just letting that be on record.

00:26:50.880 --> 00:26:51.880
 Absolutely, sir.

00:26:51.880 --> 00:26:53.080
 I appreciate that comment.

00:26:53.080 --> 00:26:57.640
 If we need to make any adjustments based on those comments received, we will definitely

00:26:57.640 --> 00:27:02.600
 look into that and make sure that if there's anything that needs to be adjusted, whether

00:27:02.600 --> 00:27:06.040
 that's moving that roadway a little bit north, that we'll evaluate that.

00:27:06.040 --> 00:27:09.320
 As I mentioned, it's just following that current alignment of that roadway in the area.

00:27:09.320 --> 00:27:11.920
 So I appreciate you bringing that up.

00:27:11.920 --> 00:27:16.760
 And thank you, thank you, the city for y'all's hard work on this.

00:27:16.760 --> 00:27:19.280
 Yes, sir.

00:27:19.280 --> 00:27:25.880
 Any other questions from commissioners?

00:27:25.880 --> 00:27:26.880
 I do not see any, Mayor.

00:27:26.880 --> 00:27:28.480
 I'm going to turn that back to you.

00:27:28.480 --> 00:27:29.480
 All right.

00:27:29.480 --> 00:27:33.920
 And yeah, so council members, direction from council.

00:27:33.920 --> 00:27:41.280
 Council Member Guara, then Mayor Proctor Meltzer.

00:27:41.280 --> 00:27:42.280
 Thank you, Mayor.

00:27:42.280 --> 00:27:47.760
 And just so you know, I think Council Member Beck and I were both using the screen to get

00:27:47.760 --> 00:27:48.760
 in the queue.

00:27:48.760 --> 00:27:55.720
 But first, I feel like I owe you and your staff, especially Pritam, an apology.

00:27:55.720 --> 00:27:57.320
 I was speaking a little bit off the cuff.

00:27:57.320 --> 00:28:00.640
 I was kind of distracted at our last work session.

00:28:00.640 --> 00:28:07.080
 And although I think that, you know, I still sort of hold the, I still do hold the concerns

00:28:07.080 --> 00:28:08.680
 that I expressed.

00:28:08.680 --> 00:28:16.280
 I also recognize that given the timeline, it's not realistic to expect you to respond

00:28:16.280 --> 00:28:21.400
 to everything that I said at our last work session before we need to pass a mobility

00:28:21.400 --> 00:28:23.160
 plan.

00:28:23.160 --> 00:28:27.800
 So I, you know, I apologize for kind of throwing that out there so flippantly.

00:28:27.800 --> 00:28:32.360
 And I recognize that this is a living document that's going to continue to evolve.

00:28:32.360 --> 00:28:37.840
 And I hope that as it continues to evolve, it will move closer to what I think is that

00:28:37.840 --> 00:28:46.080
 community vision of, you know, moving a little bit farther away from the suburban, late 20th

00:28:46.080 --> 00:28:49.720
 century, hierarchical roadway design.

00:28:49.720 --> 00:28:55.000
 I do think that, I mean, I see that you've taken those comments seriously in the changes

00:28:55.000 --> 00:28:57.640
 that you've made to Cooper Creek Road.

00:28:57.640 --> 00:29:03.520
 So thank you for taking a look at that and seeing what you can do to address those concerns

00:29:03.520 --> 00:29:07.040
 in a very short timeframe.

00:29:07.040 --> 00:29:14.380
 I sort of intuited that you were taking that phased approach to arterials and dedicating

00:29:14.380 --> 00:29:16.600
 more right of way that was needed.

00:29:16.600 --> 00:29:19.600
 It seems like you're also taking that approach on Hickory Creek Road.

00:29:19.600 --> 00:29:22.000
 Would you say that that's true?

00:29:22.000 --> 00:29:26.760
 In some situations, we are looking at doing that, yes.

00:29:26.760 --> 00:29:27.920
 Okay.

00:29:27.920 --> 00:29:35.800
 What kind of impact does, do those wide medians have on pedestrian access or pedestrian crossings

00:29:35.800 --> 00:29:36.800
 on those roads?

00:29:36.800 --> 00:29:38.040
 Can you speak to that a little bit?

00:29:38.040 --> 00:29:39.040
 Sure.

00:29:39.040 --> 00:29:40.040
 I'd be happy to.

00:29:40.040 --> 00:29:44.600
 Nathan, would you like to speak to that?

00:29:44.600 --> 00:29:48.160
 I will let the expert speak to it.

00:29:48.160 --> 00:29:54.560
 Thanks, Nathan George, also with Capital Projects Engineering.

00:29:54.560 --> 00:30:01.600
 Wide medians, so I'll say first that when I look at safety and intersection design,

00:30:01.600 --> 00:30:07.240
 I'm looking at the goal that I would have as a compact intersection.

00:30:07.240 --> 00:30:11.560
 When I say that, I mean a lot of times when we have wide medians, it does create a challenge

00:30:11.560 --> 00:30:13.680
 for a pedestrian cross street.

00:30:13.680 --> 00:30:16.200
 The wider the intersection, the longer the crossing time.

00:30:16.200 --> 00:30:20.140
 The longer the crossing time, the more impact that has on operations of the signal.

00:30:20.140 --> 00:30:26.920
 So it's sort of a challenge for us as our traffic operations division who runs the timing

00:30:26.920 --> 00:30:30.080
 on the signals to allow adequate time.

00:30:30.080 --> 00:30:34.200
 So the wider the intersection, the more challenge it is to balance the needs of vehicles versus

00:30:34.200 --> 00:30:36.360
 the needs of pedestrians.

00:30:36.360 --> 00:30:39.040
 Those wide medians can be beneficial in a way.

00:30:39.040 --> 00:30:43.440
 We want to have some space for refuge and it helps lower turning speeds.

00:30:43.440 --> 00:30:49.240
 Medians tend to discourage drivers from cutting the corner, like if you have just a painted

00:30:49.240 --> 00:30:50.440
 turn lane or something like that.

00:30:50.440 --> 00:30:54.400
 So they might actually drive a little bit faster and a little bit more recklessly.

00:30:54.400 --> 00:30:59.080
 So there are some benefits, but it's really a trade off at each specific location.

00:30:59.080 --> 00:31:02.680
 And I would tend to prefer not having wide medians.

00:31:02.680 --> 00:31:09.960
 So there's that four lane to six lane and the carving up of that space for future needs

00:31:09.960 --> 00:31:12.800
 from a vehicular standpoint.

00:31:12.800 --> 00:31:20.080
 And I think to your points across the board, what we really need to focus on is adapting

00:31:20.080 --> 00:31:23.120
 our design standards to more of a complete streets approach.

00:31:23.120 --> 00:31:28.440
 Narrow lanes, that helps us make the intersections more compact, shorten up those crossings.

00:31:28.440 --> 00:31:32.400
 People still maybe want to have those medians, but perhaps a little bit narrower.

00:31:32.400 --> 00:31:36.440
 But it's really about trying to use different design variables to make the intersection

00:31:36.440 --> 00:31:38.760
 more compact and that will make it safer.

00:31:38.760 --> 00:31:39.760
 Thanks.

00:31:39.760 --> 00:31:42.680
 So I hear that it's kind of a trade off.

00:31:42.680 --> 00:31:50.640
 Are there opportunities maybe for altering the design of those medians to make them safe?

00:31:50.640 --> 00:31:57.400
 You used the word refuge, a safer place for pedestrians to stand and wait?

00:31:57.400 --> 00:31:59.000
 Are there opportunities there?

00:31:59.000 --> 00:32:00.000
 Yes.

00:32:00.000 --> 00:32:04.520
 So when we design an intersection, if there's a place of refuge, we call that a pass through

00:32:04.520 --> 00:32:06.400
 median or a refuge median.

00:32:06.400 --> 00:32:09.960
 So it's basically the crosswalk would go through the median.

00:32:09.960 --> 00:32:12.000
 And that does provide a little bit of a safety enhancement.

00:32:12.000 --> 00:32:16.440
 Typically, you want to have a little median in front of the crosswalk and that forces

00:32:16.440 --> 00:32:18.760
 cars to turn a little bit more slowly.

00:32:18.760 --> 00:32:22.880
 So depending on the design of the roadway, there are certainly opportunities to use that

00:32:22.880 --> 00:32:27.000
 median as a safety feature and then maybe put some additional elements.

00:32:27.000 --> 00:32:31.760
 The other challenge I'll point to is that if the intersection is very large, you may

00:32:31.760 --> 00:32:36.760
 have to put some signal equipment in the median to make sure that if somebody were to get

00:32:36.760 --> 00:32:40.960
 stranded in the median, they'd have the ability to call the signal.

00:32:40.960 --> 00:32:44.500
 So it would give them a walk if they're in the median.

00:32:44.500 --> 00:32:49.200
 So that's another consideration to take that tends to prefer not having those really wide

00:32:49.200 --> 00:32:51.920
 medians but more of a narrow median.

00:32:51.920 --> 00:32:53.320
 Okay, great.

00:32:53.320 --> 00:32:54.800
 So thank you so much.

00:32:54.800 --> 00:33:01.320
 I think my direction then is as broad as my direction always is, is that moving forward,

00:33:01.320 --> 00:33:07.360
 I would love to see staff kind of balancing those concerns of acquiring right of way but

00:33:07.360 --> 00:33:13.560
 also wanting to make it accessible to pedestrians and other folks who are not driving.

00:33:13.560 --> 00:33:14.560
 Thanks.

00:33:14.560 --> 00:33:15.560
 Okay.

00:33:15.560 --> 00:33:18.020
 And so the screen's not working.

00:33:18.020 --> 00:33:23.160
 I don't think they signed in, so I'm not seeing the buttons.

00:33:23.160 --> 00:33:27.600
 So, just, you'll have to indicate by raising your hand.

00:33:27.600 --> 00:33:31.080
 And so I have Mayor Pro Tem and then we'll come back to Councilmember Beck.

00:33:31.080 --> 00:33:33.560
 Mayor, you'll have to have them raise their hand.

00:33:33.560 --> 00:33:36.480
 I think it was difficult for them to get the screen set up for everybody.

00:33:36.480 --> 00:33:38.040
 So if they'll just raise their hand.

00:33:38.040 --> 00:33:39.040
 Right.

00:33:39.040 --> 00:33:40.040
 Yeah.

00:33:40.040 --> 00:33:42.520
 No, I didn't even realize anyone was logged in to use that feature.

00:33:42.520 --> 00:33:43.520
 So we're good.

00:33:43.520 --> 00:33:44.520
 Mayor Pro Tem Elter.

00:33:44.520 --> 00:33:45.520
 Yeah.

00:33:45.520 --> 00:33:46.520
 Thank you, Mayor.

00:33:46.520 --> 00:33:56.160
 First of all, thank you, Becky, you know, for giving us the drill down and I was particularly

00:33:56.160 --> 00:34:03.920
 interested in doing that so we could see how mobility is integrated with future land use

00:34:03.920 --> 00:34:11.760
 map and mostly with respect to the Northeast and Southwest, as far as whether they line

00:34:11.760 --> 00:34:17.480
 up and agree in terms of the planned intensity of development.

00:34:17.480 --> 00:34:20.200
 And I didn't really get that, so I'm hoping you can help a little bit.

00:34:20.200 --> 00:34:27.920
 What I got out of your discussion on the Northeast was that in a relook, you've sort of downgraded

00:34:27.920 --> 00:34:37.480
 the planned sort of intensity of the roadways, but first of all, are they still being expanded

00:34:37.480 --> 00:34:41.880
 from where they are and how does that tie in?

00:34:41.880 --> 00:34:43.360
 Let's just take Northeast.

00:34:43.360 --> 00:34:50.000
 How does that tie in to what the future land use map says about the intensity of development

00:34:50.000 --> 00:34:51.500
 there?

00:34:51.500 --> 00:34:55.280
 So if you're specifically talking about Northeast, you know, that's the reason why I wanted to

00:34:55.280 --> 00:35:00.520
 show you all of the ETJ and all of the text that roadway network in that area.

00:35:00.520 --> 00:35:04.640
 And you know, explain to you where the city limits is, because if you look at that area,

00:35:04.640 --> 00:35:10.400
 the majority of the roadways in the far corner of that map really are roadways that we're

00:35:10.400 --> 00:35:15.600
 showing on our map to align with what the county thoroughfare plan would show and then

00:35:15.600 --> 00:35:18.200
 also with those connective tissues to TxDOT.

00:35:18.200 --> 00:35:23.840
 You know, a lot of that area is really going to be areas of which are going to grow in

00:35:23.840 --> 00:35:29.040
 the future, and we want to make sure we're in alignment with those future growths.

00:35:29.040 --> 00:35:33.280
 But I would just mention that specifically in the northeastern section, the majority

00:35:33.280 --> 00:35:37.000
 of that is really not within the city of Denton city limits.

00:35:37.000 --> 00:35:42.320
 So we do feel like based on the land use map in that area, what we currently know, this

00:35:42.320 --> 00:35:46.880
 is the reason why you see the mobility plan come back at least at a minimum every five

00:35:46.880 --> 00:35:53.800
 years because land will change, land uses will change, growth will happen.

00:35:53.800 --> 00:35:59.240
 And when those types of things happen, we want that opportunity to reassess the roadway

00:35:59.240 --> 00:36:00.240
 network in that area.

00:36:00.240 --> 00:36:04.280
 And so the reason why you see us changing those classifications of those roadways are

00:36:04.280 --> 00:36:09.960
 based on current situations and current data that we know in those areas, downgrading the

00:36:09.960 --> 00:36:14.480
 classifications of those roadways, or getting in alignment with those changes in the plan

00:36:14.480 --> 00:36:20.000
 that TxDOT has made from those integrated corridor, outer loop, et cetera.

00:36:20.000 --> 00:36:25.720
 Specifically in the southwest portion of town, those are decisions that have previously been

00:36:25.720 --> 00:36:28.600
 made through that master plan community that's gone through council.

00:36:28.600 --> 00:36:36.400
 - If I can interrupt a little bit, Becky, and with respect to southwest, my concern

00:36:36.400 --> 00:36:44.200
 was you mostly focused on the coal hunter part, which is, frankly, it hasn't come up

00:36:44.200 --> 00:36:51.760
 as much since those communities were planned, but the discussions that I've heard at council

00:36:51.760 --> 00:36:58.280
 were more about, again, kind of in the lower right part of that focus area.

00:36:58.280 --> 00:37:06.240
 Does the planned roadway expansion match the expected intensity of development?

00:37:06.240 --> 00:37:11.120
 'Cause those are both northeast and southwestern areas where you repeatedly hear an interest

00:37:11.120 --> 00:37:18.200
 in preserving rural fringe, and the concern is, does a mobility plan line up with that?

00:37:18.200 --> 00:37:26.920
 So is that really in the future land use map, or, you know, and as far as any amount of

00:37:26.920 --> 00:37:31.440
 rural character in either of those areas, and is that what the mobility plan says?

00:37:31.440 --> 00:37:34.840
 That really, to me, is the key question on both those quadrants.

00:37:34.840 --> 00:37:42.800
 I mean, you hear it over and over that hardly feel, you know, those are still contributing

00:37:42.800 --> 00:37:44.480
 rural areas.

00:37:44.480 --> 00:37:49.120
 - And feel free to answer, finish your last, it got truncated a bit, so if there's anything

00:37:49.120 --> 00:37:54.920
 else to pick up from where you were, where that, you know, just feel free to complete

00:37:54.920 --> 00:37:57.520
 your thought, and then the additional questions.

00:37:57.520 --> 00:37:58.520
 - No, thank you.

00:37:58.520 --> 00:37:59.520
 I appreciate that.

00:37:59.520 --> 00:38:03.440
 You know, I was just gonna mention that the southwestern area, the majority of that is

00:38:03.440 --> 00:38:07.920
 a part of that Hunter-Coal, and those decisions have been made through those developer agreements.

00:38:07.920 --> 00:38:12.640
 I will tell you that staff has evaluated based on the comments that we've received from Hunter

00:38:12.640 --> 00:38:17.720
 and Coal, and looked at if there's anything that needs to be modified in those areas.

00:38:17.720 --> 00:38:25.760
 But I would say, in general, our goal is to be in alignment with the land use map.

00:38:25.760 --> 00:38:32.440
 We've looked at the mobility based on not only the land use map, multiple occasions,

00:38:32.440 --> 00:38:39.080
 but then also really looking at some of those ETJ areas and seeing, you know, where those

00:38:39.080 --> 00:38:43.040
 areas are that where the staff does have the opportunity to make the changes and not.

00:38:43.040 --> 00:38:48.240
 Keep in mind, you know, in those ETJ areas, those are where the possibilities of those

00:38:48.240 --> 00:38:54.280
 muds come in, and, you know, those decisions will be made through those efforts with collaboration

00:38:54.280 --> 00:38:55.280
 with the county.

00:38:55.280 --> 00:39:00.680
 And so, you know, I would say that to the best of our ability, if you see a particular

00:39:00.680 --> 00:39:05.360
 area that's still concerning you, or a particular area that you'd like for us to look at to,

00:39:05.360 --> 00:39:10.640
 or even get with you and discuss, we'd be more than happy to do so.

00:39:10.640 --> 00:39:17.960
 So I feel comfortable with the information that's being shared, and I also understand,

00:39:17.960 --> 00:39:24.760
 like I mentioned, that this is something that gets updated, you know, as even Councilmember

00:39:24.760 --> 00:39:27.560
 McGuire mentioned, you know, it's a living document.

00:39:27.560 --> 00:39:33.120
 It's a schematic in nature type document, and our goal is to, as the land use changes

00:39:33.120 --> 00:39:38.880
 or growth happens, to continuously making modifications to the document.

00:39:38.880 --> 00:39:43.060
 But sorry, I'd be happy if there's a particular area that you're concerned about to sit down

00:39:43.060 --> 00:39:45.160
 with you and go over that area.

00:39:45.160 --> 00:39:51.080
 Well, I mean, we'll see if others have the same, you know, interest.

00:39:51.080 --> 00:39:53.560
 I mean, I think this is that opportunity.

00:39:53.560 --> 00:39:55.800
 You know, you're focusing on those areas, which is great.

00:39:55.800 --> 00:40:01.200
 You know, I really just want to hear clearly how much intensity is of development.

00:40:01.200 --> 00:40:07.280
 I mean, it's not just on you, you know, Becky, it's kind of jointly what's the look between

00:40:07.280 --> 00:40:09.080
 development and you.

00:40:09.080 --> 00:40:11.400
 How intense is the development that's expected?

00:40:11.400 --> 00:40:12.880
 Does that line up with the road?

00:40:12.880 --> 00:40:13.880
 Sure.

00:40:13.880 --> 00:40:14.880
 And I'm going to let...

00:40:14.880 --> 00:40:15.880
 Oh, go ahead, David.

00:40:15.880 --> 00:40:16.880
 I'm sorry.

00:40:16.880 --> 00:40:17.880
 I just saw you hop on the screen.

00:40:17.880 --> 00:40:22.580
 I was going to let Tina also talk a little bit about the comp plan in alignment with

00:40:22.580 --> 00:40:26.080
 the land use map and then also the mobility plan.

00:40:26.080 --> 00:40:27.080
 Sure.

00:40:27.080 --> 00:40:30.320
 And Tina will be able to better articulate this, I'm sure.

00:40:30.320 --> 00:40:34.720
 But just in advance of Tina addressing the question, I think the point that Becky made

00:40:34.720 --> 00:40:39.080
 on the muds, especially in the northeast, as we're looking at those textile roadways

00:40:39.080 --> 00:40:44.800
 coming through and really kind of narrowing in on Cooper Creek and Collins, you know,

00:40:44.800 --> 00:40:48.680
 downgraded those, trying to really take that fresh look.

00:40:48.680 --> 00:40:50.320
 What do we really need right now?

00:40:50.320 --> 00:40:52.800
 What do we need over the next number of years?

00:40:52.800 --> 00:40:53.800
 But we just don't have control.

00:40:53.800 --> 00:40:55.880
 So we had the land use considerations for sure.

00:40:55.880 --> 00:40:57.680
 We had the textile considerations for sure.

00:40:57.680 --> 00:41:01.200
 But we just don't have that same level of control in those muds.

00:41:01.200 --> 00:41:03.360
 And they're coming in that ETJ section right there.

00:41:03.360 --> 00:41:06.200
 So that's just going to place demands on those roadways.

00:41:06.200 --> 00:41:09.760
 But I'll hand it over to Tina.

00:41:09.760 --> 00:41:10.760
 Thank you, David.

00:41:10.760 --> 00:41:13.200
 And Tina Fergens, Deputy Director of Development Services and Planning Director.

00:41:13.200 --> 00:41:17.200
 And just along those same lines, I was going to say it a little bit different way, but

00:41:17.200 --> 00:41:21.920
 the challenge that we have, Mayor Pro Tem, is we're trying to balance the land use development

00:41:21.920 --> 00:41:23.760
 that we know that is happening within that area.

00:41:23.760 --> 00:41:27.720
 I mean, we see the growth pressures right now in the northeast quadrant of the city.

00:41:27.720 --> 00:41:29.520
 So we're trying to balance that.

00:41:29.520 --> 00:41:32.280
 We're also trying to balance that with the direction that we receive from council, which

00:41:32.280 --> 00:41:36.580
 is our desire to try to keep the character rural, agricultural, and nature.

00:41:36.580 --> 00:41:38.840
 But we know that our hands are tied to some extent.

00:41:38.840 --> 00:41:44.160
 We had this conversation a lot last week with respect to the development within the ETJ.

00:41:44.160 --> 00:41:48.360
 And when it comes to the ETJ, as you know, if we receive subdivision plots that comply

00:41:48.360 --> 00:41:52.200
 with all of the remaining of our development standards, that we're obligated to approve

00:41:52.200 --> 00:41:53.200
 them.

00:41:53.200 --> 00:41:57.360
 We also have the challenge with the muds, as David also spoke to, and that could potentially

00:41:57.360 --> 00:41:58.540
 form in that area.

00:41:58.540 --> 00:42:04.160
 So if we do not plan for some sort of roadway infrastructure right now, then we're really

00:42:04.160 --> 00:42:06.960
 setting ourselves up for bigger challenges later on.

00:42:06.960 --> 00:42:09.160
 And we're trying to find the balance, right?

00:42:09.160 --> 00:42:11.820
 So our team has further evaluated that area.

00:42:11.820 --> 00:42:16.120
 We feel comfortable downgrading the north-south roadway down to the secondary arterial down

00:42:16.120 --> 00:42:18.080
 from the primary.

00:42:18.080 --> 00:42:22.680
 That's a little bit lesser right of way, as Becky illustrated.

00:42:22.680 --> 00:42:25.920
 We try to design our roadways based upon the context of the development that's occurring

00:42:25.920 --> 00:42:27.180
 within the area.

00:42:27.180 --> 00:42:30.960
 But we have to be careful that if we limit ourselves too much right now, then we could

00:42:30.960 --> 00:42:34.360
 potentially be setting ourselves up in future councils and planning and zoning commissions

00:42:34.360 --> 00:42:38.840
 up with a lot greater challenge, because it's going to be difficult to try and go in and

00:42:38.840 --> 00:42:41.660
 acquire additional right of way as those properties develop.

00:42:41.660 --> 00:42:47.120
 So we're trying to look in our crystal ball and see what is the best decision that we

00:42:47.120 --> 00:42:48.120
 can make right now.

00:42:48.120 --> 00:42:52.040
 As Becky pointed out, we do have the ability to reevaluate the comprehensive plan and the

00:42:52.040 --> 00:42:55.000
 mobility plan every five to 10 years.

00:42:55.000 --> 00:42:59.000
 In this particular area, I know we've talked about doing area plans also, because we really

00:42:59.000 --> 00:43:03.460
 see the future being in an area plan will allow for a little bit deeper dive analysis,

00:43:03.460 --> 00:43:07.360
 so that hopefully we can look to see do we need to make any refinements to any land use

00:43:07.360 --> 00:43:12.120
 assumptions as well as address the roadway network based upon those land use assumptions

00:43:12.120 --> 00:43:13.120
 as well.

00:43:13.120 --> 00:43:16.960
 So it may not be the answer that you want to hear, Mayor Pro Tem Meltzer, but right

00:43:16.960 --> 00:43:20.520
 now we're trying to do the best we can to balance the needs for the area based upon

00:43:20.520 --> 00:43:21.520
 what we do know.

00:43:21.520 --> 00:43:25.160
 It actually, you know, it is the answer that I'm looking for.

00:43:25.160 --> 00:43:29.760
 I appreciate it that, you know, just a clear statement of what exactly is it we're trying

00:43:29.760 --> 00:43:30.760
 to accommodate.

00:43:30.760 --> 00:43:37.640
 So it's muds that we can't control that will add intensity up there.

00:43:37.640 --> 00:43:48.040
 And I appreciate your similar thoughts about expected land use intensity and how that matches

00:43:48.040 --> 00:43:54.200
 or doesn't match, you know, the roads in the Southwest, not talking about and I'm not talking

00:43:54.200 --> 00:43:58.240
 so much about Cole Hunter, but the area that you keep hearing about, you know, around Hickory

00:43:58.240 --> 00:43:59.240
 Creek.

00:43:59.240 --> 00:44:03.480
 Well, and I would say the Southwest area is a little bit easier for us to be able to analyze

00:44:03.480 --> 00:44:07.640
 and evaluate because the existing zoning is in place there, particularly with the Cole

00:44:07.640 --> 00:44:10.680
 Ranch and the Hunter ranches that are there, because all of that has already been titled.

00:44:10.680 --> 00:44:12.760
 So we know what we're receiving there.

00:44:12.760 --> 00:44:16.280
 Northeast area a little bit different because we have so much ETJ in that area.

00:44:16.280 --> 00:44:20.440
 And so we're trying to balance what we see is happening in that area with what we know

00:44:20.440 --> 00:44:23.560
 and how can we plan smart for the future in that area?

00:44:23.560 --> 00:44:24.560
 Okay.

00:44:24.560 --> 00:44:25.560
 Councilman Brett.

00:44:25.560 --> 00:44:26.560
 Thank you.

00:44:26.560 --> 00:44:27.560
 Thank you.

00:44:27.560 --> 00:44:28.560
 Thank you.

00:44:28.560 --> 00:44:29.560
 Thank you.

00:44:29.560 --> 00:44:30.560
 Mr. Mayor.

00:44:30.560 --> 00:44:31.560
 I have let's follow up.

00:44:31.560 --> 00:44:36.780
 I'll take my questions out of work as I want to follow on from that thought train.

00:44:36.780 --> 00:44:43.720
 So particular areas that I want to ask questions about sort of the alignments of potential

00:44:43.720 --> 00:44:50.440
 right of ways and issues like that are this area that we just discussed, the 377 and the

00:44:50.440 --> 00:44:56.080
 35W corridor, it looks like from the future land use map, the density is a little higher.

00:44:56.080 --> 00:45:03.120
 But when you go to the thoroughfare plan, the road network proposed, especially as you

00:45:03.120 --> 00:45:07.880
 get south of Dania and Rose Lawn and stuff is sparser.

00:45:07.880 --> 00:45:13.960
 And so it's a question, does that mobility alignment align with the more intense use towards

00:45:13.960 --> 00:45:16.720
 the southern border in that corridor?

00:45:16.720 --> 00:45:21.460
 So that's just east of Hunter Call.

00:45:21.460 --> 00:45:26.200
 But not all of it's part of Hunter Call, a lot of it's in independent development.

00:45:26.200 --> 00:45:34.160
 So my question is, does the mobility alignment align with more intense future land use?

00:45:34.160 --> 00:45:35.600
 And that really is a question.

00:45:35.600 --> 00:45:39.160
 If it's sufficient, it's sufficient, but it just seemed like when you look at the rest

00:45:39.160 --> 00:45:47.280
 of the areas where there's more density, the networks, like you just go east of there into

00:45:47.280 --> 00:45:53.120
 the sort of due south, that's, you can see the, oh yeah, here we're adding roads, we're

00:45:53.120 --> 00:45:57.040
 widening roads, blah, blah, blah, along 1830 and stuff.

00:45:57.040 --> 00:46:02.800
 But just in that corridor, just south of Rose Lawn between 377 and 35, it looked like the,

00:46:02.800 --> 00:46:07.200
 I wasn't seeing the alignment of the orange with the thoroughfare map.

00:46:07.200 --> 00:46:12.980
 And so maybe you can help me understand that.

00:46:12.980 --> 00:46:15.600
 And then I have a similar question for along 28.

00:46:15.600 --> 00:46:16.600
 Okay.

00:46:16.600 --> 00:46:19.800
 So yes, what we have shown on the mobility plan and what we have shown on the conference

00:46:19.800 --> 00:46:21.980
 of plan, we believe are in alignment with each other.

00:46:21.980 --> 00:46:25.200
 So knowing what some of the existing development patterns that are happening down there in

00:46:25.200 --> 00:46:29.080
 the southern portion of town, also take into consideration the existing entitlements in

00:46:29.080 --> 00:46:30.080
 that area.

00:46:30.080 --> 00:46:34.600
 And we've matched that up to be appropriate between the mobility plan and the conference

00:46:34.600 --> 00:46:35.600
 of plan.

00:46:35.600 --> 00:46:36.600
 All right.

00:46:36.600 --> 00:46:37.960
 Well, I hope you're right.

00:46:37.960 --> 00:46:44.040
 I mean, one of the things that we're seeing in particular regions is choke points where

00:46:44.040 --> 00:46:49.080
 we have insufficient roadways and too many single entrances.

00:46:49.080 --> 00:46:53.700
 And I know we don't really do that anymore, but I think to the extent that we can avoid

00:46:53.700 --> 00:46:57.000
 creating choke points in the future, I would sure like to do that.

00:46:57.000 --> 00:47:01.960
 Well, if you ask my team, what's the one soapbox I stand on a regular basis is the access,

00:47:01.960 --> 00:47:02.960
 right?

00:47:02.960 --> 00:47:06.240
 And trying to ensure that we have, that we're trying to minimize those choke points and

00:47:06.240 --> 00:47:07.960
 be able to get access into development.

00:47:07.960 --> 00:47:12.600
 You know, part of the challenge that we have in our community, and this is no different

00:47:12.600 --> 00:47:15.640
 in Denton compared to other communities that are experiencing growth.

00:47:15.640 --> 00:47:19.360
 When you have, and our challenge is also coupled by the fact with all the text out roadways

00:47:19.360 --> 00:47:21.840
 we have, because some of them don't have frontage roads on them, right?

00:47:21.840 --> 00:47:25.240
 So they limit our ability for any further movement and connectivity.

00:47:25.240 --> 00:47:29.920
 But what you find is that in communities that are still experiencing growth and development,

00:47:29.920 --> 00:47:33.840
 what you have is that the infrastructure gets constructed and gets phased in.

00:47:33.840 --> 00:47:36.920
 I mean, if we had unlimited amounts of money, we could go out and build all these roadways

00:47:36.920 --> 00:47:41.440
 first and do some things that I've seen Frisco where they've built six lanes divided arterials

00:47:41.440 --> 00:47:44.040
 in areas that just have farmland on either side.

00:47:44.040 --> 00:47:47.200
 But we're not in that position here in Denton to be able to go out and build all these roadways,

00:47:47.200 --> 00:47:48.200
 right?

00:47:48.200 --> 00:47:51.600
 And so we rely upon the development community in order to be able to assist us in developing

00:47:51.600 --> 00:47:52.600
 our roadways.

00:47:52.600 --> 00:47:55.560
 Our roadway network, unfortunately, is going to be phased approach.

00:47:55.560 --> 00:47:59.200
 Becky's team does a great job with their capital projects and planning that they have and trying

00:47:59.200 --> 00:48:01.240
 to do improvements where we can.

00:48:01.240 --> 00:48:03.600
 But we are going to have some pain points.

00:48:03.600 --> 00:48:06.640
 And that's going to be as areas continue to experience some development, we're going to

00:48:06.640 --> 00:48:09.960
 have to partner with the developers to be able to get our roadways constructed in relation

00:48:09.960 --> 00:48:10.960
 to that.

00:48:10.960 --> 00:48:12.400
 And I had a similar question.

00:48:12.400 --> 00:48:13.400
 Thank you.

00:48:13.400 --> 00:48:14.400
 I appreciate that.

00:48:14.400 --> 00:48:16.360
 And a similar question.

00:48:16.360 --> 00:48:23.440
 If we compare the bikeped plan to the thoroughfare plan along 28 near the new shelter, this is

00:48:23.440 --> 00:48:29.840
 something that I remember Commissioner Smith and I asking about access south along 288

00:48:29.840 --> 00:48:33.080
 to get to those services as opposed to going into the network.

00:48:33.080 --> 00:48:36.480
 It looks like the thoroughfare map is along Audre.

00:48:36.480 --> 00:48:44.920
 And so I guess, do we have sufficient south bikeped access?

00:48:44.920 --> 00:48:52.360
 I see the bike plan has us going sort of in and out of Audre near the shelter.

00:48:52.360 --> 00:48:59.900
 But nothing between the shelter and McKinney, and yet there's services up and down in there.

00:48:59.900 --> 00:49:03.440
 So I guess, is that a place that we've overlooked?

00:49:03.440 --> 00:49:09.320
 Or do we have a plan in mind and I can just rest comfortably?

00:49:09.320 --> 00:49:14.040
 From a pedestrian perspective, the answer is we have put in a sidewalk project in our

00:49:14.040 --> 00:49:17.240
 trip, proposed trip project application for this year.

00:49:17.240 --> 00:49:21.640
 So that will address our pedestrian accessibility.

00:49:21.640 --> 00:49:28.120
 From a bicycle perspective, we will need to add some lines to the map, I would say.

00:49:28.120 --> 00:49:29.440
 Loop 288 has not been addressed.

00:49:29.440 --> 00:49:34.240
 That's going to be a real challenge because Loop 288, we're in the process of putting

00:49:34.240 --> 00:49:41.400
 in sidewalks and then to recommend putting in bicycle accommodations as well is a higher

00:49:41.400 --> 00:49:43.140
 level recommendation.

00:49:43.140 --> 00:49:47.960
 So ideally we would make those accommodations as we deliver new projects, but if their sidewalk

00:49:47.960 --> 00:49:54.920
 projects are not combined bikeped, that would then not address that need, if you will.

00:49:54.920 --> 00:50:01.880
 And yes, the north-south activity, we have kind of the bike lanes a little bit west of

00:50:01.880 --> 00:50:08.920
 there, but we don't have any tandem access along Loop 288 proposed currently.

00:50:08.920 --> 00:50:19.100
 My one micro-direction would be for then that I would ask staff to focus on that because

00:50:19.100 --> 00:50:24.320
 we see pedestrian access up and down that green swath to go from Serve Denton and other

00:50:24.320 --> 00:50:27.840
 services that are in the courthouse, blah, blah, blah.

00:50:27.840 --> 00:50:34.000
 There's lots of little services in there that are used and I'd love to see us make sure

00:50:34.000 --> 00:50:36.120
 that that is not a gap.

00:50:36.120 --> 00:50:41.960
 It may not be a gap, but I would like maybe some, to just make sure if that's something

00:50:41.960 --> 00:50:42.960
 we can clean up.

00:50:42.960 --> 00:50:46.760
 Yeah, I'll say if I could just offer, Mayhill Road is just off the map that I have in front

00:50:46.760 --> 00:50:52.080
 of me, but that's our primary north-south bike and pedestrian access, so that provides

00:50:52.080 --> 00:50:55.080
 our what I would call our priority north-south access.

00:50:55.080 --> 00:51:00.220
 We have a number of east-west branches that come off of that facility, so that will be

00:51:00.220 --> 00:51:05.440
 sort of our highest order facility in the nearby area.

00:51:05.440 --> 00:51:08.480
 The trip application will address the missing sidewalks.

00:51:08.480 --> 00:51:15.560
 I actually took a photo on that corridor as one of my primary missing sidewalk areas in

00:51:15.560 --> 00:51:16.560
 the city.

00:51:16.560 --> 00:51:18.000
 It's one of the areas that really needs to be addressed.

00:51:18.000 --> 00:51:23.000
 It is a textile roadway, of course, so we're going in and filling in the gaps that were

00:51:23.000 --> 00:51:28.720
 left by the roadway project, but it is a priority to make sure it's pedestrian accessible and

00:51:28.720 --> 00:51:35.080
 we'll be focusing on making sure bicycle users know that Mayhill is going to be their priority

00:51:35.080 --> 00:51:38.600
 facility, at least in the near term, until we can build out more of a network elsewhere.

00:51:38.600 --> 00:51:44.560
 Yeah, and I understand that in the future Mayhill will be more, and as we grow it'll

00:51:44.560 --> 00:51:46.960
 expand and we have the control of Mayhill.

00:51:46.960 --> 00:51:51.920
 And I hear that we're hitting all these text-dot, Becky said this at the beginning of her presentation,

00:51:51.920 --> 00:51:58.160
 that our ability to do things on text-dot roads is challenging, remains a barrier.

00:51:58.160 --> 00:51:59.960
 I get that.

00:51:59.960 --> 00:52:06.220
 We do know that just as you know better than anyone in this room that people will just

00:52:06.220 --> 00:52:11.400
 walk across the grass to make a path, people will walk and people are going to do what

00:52:11.400 --> 00:52:16.720
 they're going to do and I think we have to build in what they're going to do near and

00:52:16.720 --> 00:52:17.720
 long term.

00:52:17.720 --> 00:52:21.080
 So I guess that's only sort of a micro-direction.

00:52:21.080 --> 00:52:27.120
 It just feels like a gap, but I ask that maybe we give a little attention to that.

00:52:27.120 --> 00:52:32.080
 And then real quick, two more sort of conceptual questions and this might be, this next one

00:52:32.080 --> 00:52:39.520
 might be Becky or Preetan, and it seems like if we're now prioritizing safety as in our

00:52:39.520 --> 00:52:46.400
 flat hierarchy we're giving number one a little boost on priority in terms of our mobility

00:52:46.400 --> 00:52:53.200
 planning and safety and its potential that our roadway network speeds, you heard a lot

00:52:53.200 --> 00:52:58.600
 of in the council at least, I don't know about P&Z, asking for those speeds to be where possible

00:52:58.600 --> 00:53:03.280
 minimums rather than averages or maximums.

00:53:03.280 --> 00:53:07.320
 If that's the case and you still want to have flow, this actually goes back to Councilor

00:53:07.320 --> 00:53:13.760
 McGuire's question, don't we need, I understand the concept of having a hierarchical network,

00:53:13.760 --> 00:53:19.700
 and that's completely valid, right, but doesn't it need to mean that it's a hierarchical network

00:53:19.700 --> 00:53:23.240
 of collectors, especially if we're lowering the speeds.

00:53:23.240 --> 00:53:27.520
 If you want to keep up the flow, then we need a couple more collectors so that our collectors

00:53:27.520 --> 00:53:34.960
 are not as widely spaced apart so that the flow is maintained at the lower speeds.

00:53:34.960 --> 00:53:38.680
 And so that really is just a, that's a hundred thousand foot view, I mean that's a question

00:53:38.680 --> 00:53:44.460
 of do we have sufficient flexibility to add additional collector capacity into our hierarchical

00:53:44.460 --> 00:53:45.460
 network?

00:53:45.460 --> 00:53:49.240
 Absolutely, and those are the things that we do when developments come through is evaluate

00:53:49.240 --> 00:53:51.960
 if a collector's needed based on their traffic study.

00:53:51.960 --> 00:53:55.600
 In many areas, all the collectors may not be shown.

00:53:55.600 --> 00:53:59.080
 We'd love to add additional collectors all over the map, but we want to wait and see

00:53:59.080 --> 00:54:03.600
 how those areas develop and then add those collectors as needed.

00:54:03.600 --> 00:54:10.360
 Cool, and then similarly, not similarly, but related to the textile problem I mentioned

00:54:10.360 --> 00:54:16.080
 a second ago, is there, is there something that the city needs to do to update our approach

00:54:16.080 --> 00:54:21.360
 to getting these text dot, is there, not our thumb on the scale, but is there, is there

00:54:21.360 --> 00:54:30.240
 ways that we should anticipate interacting with text dot to facilitate some of the needs

00:54:30.240 --> 00:54:36.440
 that you, the citizens, you and your team identify, development team identifies, but

00:54:36.440 --> 00:54:39.880
 we're unable to approach in the same way that we do our own roads.

00:54:39.880 --> 00:54:44.160
 Is there something we need to be doing to facilitate that text dot interaction?

00:54:44.160 --> 00:54:50.320
 So loop 288 was constructed in 2004, 2005, 2006 timeframe.

00:54:50.320 --> 00:54:54.840
 At that time, text dot did not have as a part of their design criteria to have sidewalks

00:54:54.840 --> 00:54:58.480
 as a part of their overall construction of their projects.

00:54:58.480 --> 00:55:02.880
 That is, that whole philosophy has drastically changed.

00:55:02.880 --> 00:55:09.880
 As you see, if you drive down 2499, 2181, all of those roadway networks will have sidewalks.

00:55:09.880 --> 00:55:15.120
 Where Nathan is working and he can tell you this himself, we have conversations with text

00:55:15.120 --> 00:55:21.360
 dot on a very regular basis, is working on the projects that have not began construction

00:55:21.360 --> 00:55:29.520
 yet to add those additional pedestrian areas or add the side path type situations where

00:55:29.520 --> 00:55:33.920
 they do allow for the bicycle traffic.

00:55:33.920 --> 00:55:37.760
 Specifically on loop 288, it's been a very big concern of mine that the junction is way

00:55:37.760 --> 00:55:44.600
 north and the Serve Denton is way south and there's not traffic lights in between.

00:55:44.600 --> 00:55:47.800
 There's only a traffic light located at McKinney.

00:55:47.800 --> 00:55:52.120
 That's the reason why when Nathan was working on the DCTA trip, I said let's look to fill

00:55:52.120 --> 00:55:57.400
 in the gaps and get folks an opportunity to walk all the way down, cross this crosswalk

00:55:57.400 --> 00:56:02.440
 at McKinney and walk back up to Serve Denton because I realize we need to provide that

00:56:02.440 --> 00:56:03.440
 safe path.

00:56:03.440 --> 00:56:08.200
 So there's things we're doing and looking at doing as a part of projects such as the

00:56:08.200 --> 00:56:09.960
 DCTA trip.

00:56:09.960 --> 00:56:12.960
 There's conversations we're constantly having with text dot.

00:56:12.960 --> 00:56:16.240
 When they provide us a schematic, we're looking at that overall cross section.

00:56:16.240 --> 00:56:19.080
 We're seeing if there's modifications that can be made.

00:56:19.080 --> 00:56:21.920
 And this is what I've been talking about from the very beginning.

00:56:21.920 --> 00:56:24.560
 We always focus in on the thoroughfare map, right?

00:56:24.560 --> 00:56:27.080
 We always want to see where the roads are going to go.

00:56:27.080 --> 00:56:31.080
 We always focus in on those lines, what those classifications are.

00:56:31.080 --> 00:56:36.400
 So we have, in my mind, been able to have the opportunity by having Nathan on board

00:56:36.400 --> 00:56:42.200
 with his expertise to take that to the next level, to make it the true multimodal document

00:56:42.200 --> 00:56:46.480
 that our team is really working for, allowing for those sidewalks and allowing for those

00:56:46.480 --> 00:56:48.240
 bike paths.

00:56:48.240 --> 00:56:52.720
 But I would say as far as the collaboration with text dot, they hear us loud and clear.

00:56:52.720 --> 00:56:56.680
 Nathan's had multiple conversations and I feel comfortable with the direction that we're

00:56:56.680 --> 00:56:58.560
 headed.

00:56:58.560 --> 00:57:03.720
 And I will tell you, there will be some projects that are already far enough down the road

00:57:03.720 --> 00:57:07.920
 where we're making modifications or requesting modifications.

00:57:07.920 --> 00:57:12.120
 There are things that happen from a text dot perspective with environmental clearance,

00:57:12.120 --> 00:57:13.120
 et cetera.

00:57:13.120 --> 00:57:16.880
 But anywhere we can make those changes, I'll give you an example.

00:57:16.880 --> 00:57:24.040
 The 35 widening at Oak Street, Nathan and several other folks worked along with Gary

00:57:24.040 --> 00:57:29.520
 Packin with Parks, obviously, worked to try to make some modifications so that folks will

00:57:29.520 --> 00:57:35.440
 be able to go along Oak under 35 from the hospital network along to the west side of

00:57:35.440 --> 00:57:41.160
 town and making those modifications so that we had safe passages through there.

00:57:41.160 --> 00:57:44.480
 It's a little bit change in philosophy, but definitely something that we're already having

00:57:44.480 --> 00:57:47.840
 those conversations with text dot regularly when we have new roadways that are coming

00:57:47.840 --> 00:57:48.840
 through.

00:57:48.840 --> 00:57:49.840
 All right.

00:57:49.840 --> 00:57:50.840
 Thank you.

00:57:50.840 --> 00:57:51.840
 Yes, sir.

00:57:51.840 --> 00:57:55.120
 Councilmember Davis.

00:57:55.120 --> 00:57:59.180
 Thank you, Mayor.

00:57:59.180 --> 00:58:00.180
 Excuse me.

00:58:00.180 --> 00:58:03.320
 I just want to weigh in quickly to say my direction is I'm very pleased with the changes

00:58:03.320 --> 00:58:04.320
 that you've made.

00:58:04.320 --> 00:58:05.680
 I think they're very responsive.

00:58:05.680 --> 00:58:08.680
 You know, we're, we're laypeople.

00:58:08.680 --> 00:58:09.680
 Most of us.

00:58:09.680 --> 00:58:13.840
 I can't think of any of us that have advanced degrees in engineering or career experience

00:58:13.840 --> 00:58:19.440
 in planning roadway networks, much less designing cross-sections for each of the myriad situations

00:58:19.440 --> 00:58:26.780
 that a roadway will encounter on the I like the phased approach a lot.

00:58:26.780 --> 00:58:27.780
 It's not perfect.

00:58:27.780 --> 00:58:28.780
 Nothing is perfect.

00:58:28.780 --> 00:58:32.460
 Like Tina said, if we could had all the money in the world, we could play Sim City and plan

00:58:32.460 --> 00:58:34.640
 things out perfectly.

00:58:34.640 --> 00:58:38.880
 But planning ahead with that phased approach, I like that our standard cross-section for

00:58:38.880 --> 00:58:43.780
 that size of facility includes side paths, substantial side paths.

00:58:43.780 --> 00:58:51.760
 I like that we're taking that holistic approach, even when we're doing 139 foot right away.

00:58:51.760 --> 00:58:55.400
 We're planning ahead and taking that holistic approach.

00:58:55.400 --> 00:58:58.960
 And then I like the downgrades that you've done in the Hartley Field Northeast Denton

00:58:58.960 --> 00:59:04.960
 area because the thing that's been very helpful for me to understand through our conversations

00:59:04.960 --> 00:59:11.280
 is that when I think primary arterial, I think Carroll Boulevard, I think driveways, I think

00:59:11.280 --> 00:59:16.360
 businesses, I think a million cars coming in from all directions.

00:59:16.360 --> 00:59:21.200
 But I've needed to change my thinking about some of the larger facilities we're talking

00:59:21.200 --> 00:59:26.000
 about in this area and think of it more like 380 west of Jacksboro.

00:59:26.000 --> 00:59:31.040
 In Denton, we may not want any kind of development along those big, bigger roads.

00:59:31.040 --> 00:59:36.240
 In Denton, we may want big one-acre lots because that's what our flume says.

00:59:36.240 --> 00:59:41.280
 But over in Salina and Krugerville and Aubrey, they're going to be building houses and muds.

00:59:41.280 --> 00:59:45.000
 And over in Crum and Sanger, they're going to be building houses and muds.

00:59:45.000 --> 00:59:50.060
 And if we don't move those folks across our nice, open, rural fringe, then they're going

00:59:50.060 --> 00:59:55.040
 to come down into the city or they're going to go north up into the new Super Warsham

00:59:55.040 --> 00:59:59.440
 Road or the Super 428 that TxDOT is going to build.

00:59:59.440 --> 01:00:05.020
 And those facilities aren't going to come from TxDOT nearly so soon as the facilities

01:00:05.020 --> 01:00:08.720
 that developers may build as we approve them in the city.

01:00:08.720 --> 01:00:14.480
 So I really appreciate you helping me reorient my thinking to moving people, not just around

01:00:14.480 --> 01:00:19.160
 in those areas and not just the developments we have control over, but across our borders,

01:00:19.160 --> 01:00:24.440
 across the city, and keeping them off of 380 and keeping them off of 428 and just moving

01:00:24.440 --> 01:00:25.440
 them through.

01:00:25.440 --> 01:00:26.440
 Thank you.

01:00:26.440 --> 01:00:27.440
 Yes, sir.

01:00:27.440 --> 01:00:28.440
 Okay.

01:00:28.440 --> 01:00:29.440
 Vicki, one quick question.

01:00:29.440 --> 01:00:35.760
 Obviously, it's come up a lot, and I looked at the map and understand the border between

01:00:35.760 --> 01:00:40.200
 the ETGA is right at Hartley Field Road, right?

01:00:40.200 --> 01:00:43.720
 So who controls that road?

01:00:43.720 --> 01:00:44.720
 The border is right on it.

01:00:44.720 --> 01:00:47.780
 I just don't know how to read the map and for those following along.

01:00:47.780 --> 01:00:51.960
 And I will have to tell you, I'll have to go back and look at exactly what is in the

01:00:51.960 --> 01:00:53.680
 city and what is in the county.

01:00:53.680 --> 01:00:59.600
 From my recollection, the last time this came up, to Commissioner Anderson's comments that

01:00:59.600 --> 01:01:03.520
 he made, I believe there's portions that are in the city and the county, but I would have

01:01:03.520 --> 01:01:09.440
 to actually look specifically at that to tell you where the stops and start points are.

01:01:09.440 --> 01:01:12.560
 But my recollection is that it falls in both jurisdictions, sir.

01:01:12.560 --> 01:01:13.560
 Right.

01:01:13.560 --> 01:01:14.560
 Okay.

01:01:14.560 --> 01:01:15.560
 Thank you.

01:01:15.560 --> 01:01:18.440
 Council Member Burke.

01:01:18.440 --> 01:01:21.040
 Thank you, Mr. Mayor, for the opportunity to speak.

01:01:21.040 --> 01:01:28.440
 Becky DeVine, you all are doing a terrific job, and I'm so pleased at the learning that

01:01:28.440 --> 01:01:30.920
 I'm getting with all of this.

01:01:30.920 --> 01:01:36.880
 One of the things I did want to highlight, and I wanted the folks out there to know,

01:01:36.880 --> 01:01:44.680
 is that the thing that's staying with me right now is that we have to rely on the development

01:01:44.680 --> 01:01:51.960
 to the partnerships with the developers to plan these roads, have extensive conversation

01:01:51.960 --> 01:01:57.400
 with someone that didn't know, at one point I didn't know, that you have to have the development

01:01:57.400 --> 01:02:00.280
 in to get the roads.

01:02:00.280 --> 01:02:05.120
 We always seem to want to think that the roads are going to come first, you know, why didn't

01:02:05.120 --> 01:02:06.120
 they plan the roads?

01:02:06.120 --> 01:02:07.780
 Why didn't they plan the roads?

01:02:07.780 --> 01:02:09.800
 But the development has to be there.

01:02:09.800 --> 01:02:14.320
 So you know, from the educational perspective, you know, that's something that we have to

01:02:14.320 --> 01:02:20.160
 understand as citizens, is that the money is not there, the funding is not there until

01:02:20.160 --> 01:02:24.960
 the development comes in, and then we work and plan around that development.

01:02:24.960 --> 01:02:26.520
 Did I say that right?

01:02:26.520 --> 01:02:28.480
 Okay, good.

01:02:28.480 --> 01:02:36.600
 The other thing is, this is probably my personal issue that I have with roads coming up.

01:02:36.600 --> 01:02:45.920
 I don't always agree and understand how we choose to put the plants and the trees and

01:02:45.920 --> 01:02:54.800
 all of that in these medians, and taking care of those plants and trees to grow, and I know

01:02:54.800 --> 01:03:00.680
 it's a beautification thing, but the primary thing for me sometimes is the lighting.

01:03:00.680 --> 01:03:06.280
 I don't understand how there's a lot of lights here and then there's no lights here and then

01:03:06.280 --> 01:03:09.040
 there's some lights there and these different kind of lights.

01:03:09.040 --> 01:03:16.560
 How does that all work for, you know, lay people like me that will drive down 380, we'll

01:03:16.560 --> 01:03:22.120
 use 380 as an example, get up here to Texas Women's University and go all the way out

01:03:22.120 --> 01:03:27.400
 to 288, and there's not a light anywhere to be seen, and it's always, we have to depend

01:03:27.400 --> 01:03:33.120
 on those developments to get, you know, some lighting on the roads, and then we go out

01:03:33.120 --> 01:03:37.160
 and then there's an overabundance of lights.

01:03:37.160 --> 01:03:40.040
 How does, who's working on that?

01:03:40.040 --> 01:03:41.640
 Who has a say in that?

01:03:41.640 --> 01:03:47.520
 How can I complain to everybody in town if there's not enough lights here?

01:03:47.520 --> 01:03:52.320
 You are making me have more gray hairs, I always, we speak, no, I'm kidding.

01:03:52.320 --> 01:03:57.160
 The light is a component that comes within the design parameter, so, you know, really

01:03:57.160 --> 01:04:02.160
 this planning focus is really more of a planning level document, but when these become from

01:04:02.160 --> 01:04:09.080
 planning level documents into physical designs, it's part of the process that we look at and

01:04:09.080 --> 01:04:12.880
 review to see if lighting is something that is needing to be evaluated.

01:04:12.880 --> 01:04:17.440
 Now many of the roadways, in the roadway example that you gave, 380, we do have a bond project

01:04:17.440 --> 01:04:20.280
 to do lighting along 380 that we're working through.

01:04:20.280 --> 01:04:25.600
 It's just a future project that's a few years out in the queue, but I would tell you that

01:04:25.600 --> 01:04:30.560
 that's something that we have to coordinate with TxDOT, and just really a high level,

01:04:30.560 --> 01:04:36.080
 the way that that works is through a photometric study to actually look and see what types

01:04:36.080 --> 01:04:40.080
 of lights need to be installed where we have streetlight criteria, just like you hear me

01:04:40.080 --> 01:04:45.560
 talk about the transportation criteria, and DME is responsible for that streetlight criteria,

01:04:45.560 --> 01:04:51.000
 but we work very closely with them on streetlights as our team is the one who really works through

01:04:51.000 --> 01:04:55.640
 that process to add streetlights as necessary when we're developing a road.

01:04:55.640 --> 01:05:00.520
 I'll say my word, our goal is to use our holistic approach to make sure we're looking at where

01:05:00.520 --> 01:05:07.960
 that water, sewer, drainage, roadway, sidewalk, bicycle, streetlight, etc., when we design

01:05:07.960 --> 01:05:08.960
 a roadway.

01:05:08.960 --> 01:05:12.480
 That's a new focus, that's a new thought process, that's something that we're working through

01:05:12.480 --> 01:05:13.640
 the process.

01:05:13.640 --> 01:05:18.200
 Many of the projects you see going on today, we're working to incorporate them if we can,

01:05:18.200 --> 01:05:22.200
 but many of those are projects that have already, the decisions have been made, so my goal is

01:05:22.200 --> 01:05:26.460
 for us to start seeing that shift as we work through new projects as we move forward.

01:05:26.460 --> 01:05:30.840
 Great example is the 2019 bond program on the residential streets.

01:05:30.840 --> 01:05:33.000
 Thank you.

01:05:33.000 --> 01:05:37.280
 Commissioner Anderson has been waiting, so I'll let you.

01:05:37.280 --> 01:05:39.760
 I appreciate that, Mayor, thank you.

01:05:39.760 --> 01:05:44.280
 Commissioner Anderson, I will give the floor to you.

01:05:44.280 --> 01:05:49.040
 Thank you, Chair.

01:05:49.040 --> 01:05:53.260
 I do have a quick question, if I understood this correctly, are we really considering

01:05:53.260 --> 01:06:00.080
 putting bike lanes on loop 288?

01:06:00.080 --> 01:06:04.760
 I can have Nathan answer that, but what we are looking at is ways to incorporate and

01:06:04.760 --> 01:06:10.160
 add bike lanes as necessary or as the need exists.

01:06:10.160 --> 01:06:13.500
 That's a textile roadway, so that would be something that we would have to coordinate

01:06:13.500 --> 01:06:15.200
 with them as a decision.

01:06:15.200 --> 01:06:19.320
 I think to Nathan's point is it's something that we're currently evaluating and working

01:06:19.320 --> 01:06:25.760
 through the process of having sidewalks along 288 for connective tissue from the junction

01:06:25.760 --> 01:06:32.040
 all the way down and across, but bike lanes are something that would be addressed, not

01:06:32.040 --> 01:06:34.960
 specifically on the roadway itself.

01:06:34.960 --> 01:06:40.160
 If that's the concern, it would be where could those be constructed and how could those sidewalks

01:06:40.160 --> 01:06:45.480
 change to side path to situations where bicycles would be able to be used those, but I'll let

01:06:45.480 --> 01:06:49.600
 Nathan see if I missed anything and if he wants to add anything.

01:06:49.600 --> 01:06:51.560
 Thanks for the question.

01:06:51.560 --> 01:06:58.800
 Just to clarify our approach, or I guess I'll call it our philosophy, last year TxDOT adopted

01:06:58.800 --> 01:07:02.960
 a new bicycle accommodation policy that on major thoroughfares, on their major roads,

01:07:02.960 --> 01:07:07.120
 which is pretty much everything they have, that they would provide side paths to accommodate

01:07:07.120 --> 01:07:09.360
 bicycles to pedestrian activity.

01:07:09.360 --> 01:07:14.820
 We're going to follow suit in general for all of our designs, so on a major road like

01:07:14.820 --> 01:07:20.880
 at Loop 288 or any major road that we would call our thoroughfares collector or arterial,

01:07:20.880 --> 01:07:24.840
 we will not have on street bike facilities unless they're separated or protected in some

01:07:24.840 --> 01:07:29.000
 way, which is just an acknowledgement that anybody who's out riding on those streets

01:07:29.000 --> 01:07:33.280
 in general, if we want to appeal to a broader audience, they need to have that feeling of

01:07:33.280 --> 01:07:38.000
 safety and comfort and that'll be more like Hickory Street if I can point to an example

01:07:38.000 --> 01:07:42.600
 here in the city where we have those bollards separating traffic or as traffic gets higher

01:07:42.600 --> 01:07:47.960
 speed or higher volume, maybe something more robust to separate folks from traffic or we're

01:07:47.960 --> 01:07:53.200
 putting them into a high quality roadside facility like we're building on McKinney or

01:07:53.200 --> 01:08:00.600
 you might see on other streets around town.

01:08:00.600 --> 01:08:01.600
 Commissioner Anderson, you're muted.

01:08:01.600 --> 01:08:03.720
 Can you hear me now?

01:08:03.720 --> 01:08:04.720
 Yes.

01:08:04.720 --> 01:08:05.720
 Yes.

01:08:05.720 --> 01:08:06.720
 Okay.

01:08:06.720 --> 01:08:12.580
 Thank you again for that answer, but my concern is if you put it on Loop 288, I mean we already

01:08:12.580 --> 01:08:18.280
 have people trying to cross Loop 288, McKinney Street that had a pass, unfortunately had

01:08:18.280 --> 01:08:23.720
 fatality accidents there and I thought that if we put bike paths on Loop 288, that's just

01:08:23.720 --> 01:08:28.160
 asking for more trouble, but it's good to hear that you're putting it off the road,

01:08:28.160 --> 01:08:30.200
 not on the road.

01:08:30.200 --> 01:08:31.200
 Correct.

01:08:31.200 --> 01:08:32.200
 Yeah.

01:08:32.200 --> 01:08:36.200
 And I will also point out there were some mapping issues based on some changes that

01:08:36.200 --> 01:08:39.480
 were made that we still have some corrections to make to the maps that you'll see in the

01:08:39.480 --> 01:08:44.800
 final document that we'll be working on with the consultant, but if there's any lack of

01:08:44.800 --> 01:08:49.080
 clarity in what you see on the maps, if it says bike lane, that will be corrected before

01:08:49.080 --> 01:08:52.280
 the final version is adopted or put forward for adoption.

01:08:52.280 --> 01:08:53.280
 Thanks.

01:08:53.280 --> 01:08:54.280
 Okay.

01:08:54.280 --> 01:08:57.280
 Again, thank you guys for your hard work.

01:08:57.280 --> 01:08:58.280
 Thanks.

01:08:58.280 --> 01:08:59.280
 Thank you, Nathan.

01:08:59.280 --> 01:09:06.040
 Is there any other commissioners with questions?

01:09:06.040 --> 01:09:07.840
 If I could just say just a minute.

01:09:07.840 --> 01:09:08.840
 Sure.

01:09:08.840 --> 01:09:15.080
 Just to concur with Council Member Davis and I think some others on the downgrading of

01:09:15.080 --> 01:09:22.040
 those roads, I think that's spot on in that area and what you always hear me talk about

01:09:22.040 --> 01:09:27.600
 and I will talk about when we talk about the comp plan is small area plans and I've been

01:09:27.600 --> 01:09:34.320
 wanting one for that area for so long and I think if we can focus on that, it will spell

01:09:34.320 --> 01:09:38.880
 out further what that mobility in that area is going to be.

01:09:38.880 --> 01:09:39.880
 So thank you.

01:09:39.880 --> 01:09:40.880
 Yes, ma'am.

01:09:40.880 --> 01:09:41.880
 Thank you.

01:09:41.880 --> 01:09:42.880
 Okay.

01:09:42.880 --> 01:09:43.880
 Any other Council Members?

01:09:43.880 --> 01:09:44.880
 Mayor Proctor Meltzer?

01:09:44.880 --> 01:09:52.040
 Yeah, I may be the lone voice, but you know, I might as well say it.

01:09:52.040 --> 01:09:58.520
 Regarding the Northeast, this is by way of direction, if we're not building for growth

01:09:58.520 --> 01:10:04.800
 that we project in areas that we control, but I'm not that compelled by the idea that

01:10:04.800 --> 01:10:10.880
 we should facilitate and pave the way for muds that we don't control, so I appreciate

01:10:10.880 --> 01:10:21.240
 the downgrading, but I would say if we're not building for our needs, I'd do less and

01:10:21.240 --> 01:10:29.360
 send those rations to Southeast where we're already behind the definitions that we think

01:10:29.360 --> 01:10:37.160
 are already needed for the community that's already there, so that may just be me, but

01:10:37.160 --> 01:10:38.160
 that's me.

01:10:38.160 --> 01:10:39.160
 Councilmember Aguilar?

01:10:39.160 --> 01:10:40.160
 Thank you.

01:10:40.160 --> 01:10:47.920
 I was just a little bit concerned about the conversation around the junction and folks

01:10:47.920 --> 01:10:51.440
 who might need to get from the junction to Serve Denton on foot.

01:10:51.440 --> 01:10:56.440
 It's almost a mile from the junction to get all the way down to McKinney and then cross

01:10:56.440 --> 01:11:01.560
 and then almost half a mile back up north to Serve Denton.

01:11:01.560 --> 01:11:09.360
 That's a big burden, a place on pedestrians, and I'm seeing that, what is that, prominence

01:11:09.360 --> 01:11:14.480
 parkway there is just north of the junction, and that's going to be extended, it looks

01:11:14.480 --> 01:11:15.480
 like.

01:11:15.480 --> 01:11:22.160
 Are there any plans to signalize that intersection at prominence, or is that like fully a text

01:11:22.160 --> 01:11:25.720
 dot decision, which intersections get signalized along 288?

01:11:25.720 --> 01:11:27.780
 No, the signal has to meet warrant.

01:11:27.780 --> 01:11:32.160
 We do know there will be a time that that signal actually will be one that will be installed

01:11:32.160 --> 01:11:37.400
 to your point, then they would go north and across and down.

01:11:37.400 --> 01:11:44.300
 It's a fairly similar trek, but definitely a different way to cross.

01:11:44.300 --> 01:11:48.920
 It's a lot shorter if you could go north, I mean it's like a mile shorter if you can

01:11:48.920 --> 01:11:49.920
 go north.

01:11:49.920 --> 01:11:50.920
 No, I appreciate that.

01:11:50.920 --> 01:11:56.720
 I'm currently with the way that we've evaluated it because there is not a signalized intersection

01:11:56.720 --> 01:12:01.560
 there, and there is not current funding to work through that process to have that signalized

01:12:01.560 --> 01:12:02.560
 intersection.

01:12:02.560 --> 01:12:06.720
 Also, that roadway is something that's being developed as a part of that development in

01:12:06.720 --> 01:12:08.160
 that area.

01:12:08.160 --> 01:12:13.000
 When that signal is installed, and it already does meet warrants in that area, then that

01:12:13.000 --> 01:12:18.240
 would be the improvements that would look to be made is from the junction to the north

01:12:18.240 --> 01:12:22.040
 to connect to that Audre, although the roadway now makes a little bit different connection

01:12:22.040 --> 01:12:28.080
 in that area, or proposed connection, and then go across to prominence and down.

01:12:28.080 --> 01:12:32.060
 In that area, there's already some sidewalk that's constructed, so it would be filling

01:12:32.060 --> 01:12:37.160
 in some of those gaps, another sidewalk in front of FEMA, maybe some sidewalk in front

01:12:37.160 --> 01:12:41.720
 of the former DPS building, but then we would look to be filling in gaps in some of those

01:12:41.720 --> 01:12:46.600
 areas to make sure that they had a clear path to get from point A to point B, but I'm going

01:12:46.600 --> 01:12:52.720
 off memory, so that usually doesn't serve me well, but did work on the construction

01:12:52.720 --> 01:12:58.560
 of loop 288 back in 2004, so I do have some knowledge of that area.

01:12:58.560 --> 01:13:02.540
 That definitely would be something that's evaluated at that time, and I will tell you

01:13:02.540 --> 01:13:09.480
 that we've already had those conversations to talk about getting folks from the junction

01:13:09.480 --> 01:13:13.040
 to serve Denton in the most expeditious manner.

01:13:13.040 --> 01:13:17.440
 Currently, the way that we're proposing is, like I mentioned before, but definitely when

01:13:17.440 --> 01:13:23.280
 that signal comes there, I know another topic that's been brought up is the pedestrian hybrid

01:13:23.280 --> 01:13:28.840
 beacons to allow folks to move across the roadway, and TxDOT will not allow those roadways

01:13:28.840 --> 01:13:34.160
 on their roadway network, so we will have to have a signalized intersection to allow

01:13:34.160 --> 01:13:38.560
 for that safe passage from the western side of the roadway to the eastern side of the

01:13:38.560 --> 01:13:39.560
 roadway.

01:13:39.560 --> 01:13:40.560
 Okay, good.

01:13:40.560 --> 01:13:41.560
 I'm glad to hear that there is going to be a signal.

01:13:41.560 --> 01:13:44.480
 I'm real disappointed to hear that TxDOT is not allowing hawk beacons.

01:13:44.480 --> 01:13:45.480
 I didn't realize that.

01:13:45.480 --> 01:13:52.360
 Do you have a sense of what the timeline is for, yeah, that Audra prominence intersection

01:13:52.360 --> 01:13:56.120
 becoming signalized with the development that's happening there?

01:13:56.120 --> 01:13:57.120
 I do not.

01:13:57.120 --> 01:13:59.120
 I will have to get back to you on that.

01:13:59.120 --> 01:14:03.800
 That will be something I'll have to coordinate with Tina and their team based on what's happening

01:14:03.800 --> 01:14:08.520
 in that area, and we can evaluate that, but I don't have that timing in my mind.

01:14:08.520 --> 01:14:09.520
 That's fine.

01:14:09.520 --> 01:14:10.520
 That's fine.

01:14:10.520 --> 01:14:11.520
 Thank you.

01:14:11.520 --> 01:14:20.920
 But just to pick up there, I think it is noteworthy, though, to point out currently people leave

01:14:20.920 --> 01:14:27.880
 Monsignor King and have to walk all the way to the square to go to our Daily Bread, and

01:14:27.880 --> 01:14:34.720
 so we're condensing that quite a bit, and also I think I'll take staff, and this is

01:14:34.720 --> 01:14:38.840
 not your department, but other departments' direction, on ways to bridge that, because

01:14:38.840 --> 01:14:43.360
 I'm not optimistic that anything's going to happen from TxDOT anytime soon, but I think

01:14:43.360 --> 01:14:52.560
 the great thing is we do contribute a huge amount to DCTA, and there's buses that can

01:14:52.560 --> 01:14:57.360
 just make loops there, and then we obviously served it and it works well with us and the

01:14:57.360 --> 01:15:04.400
 community, and we could then bus over, provide offices, food pantry coordination, and we

01:15:04.400 --> 01:15:12.240
 can handle all that in-house with other departments without having to be subject to TxDOT's timing,

01:15:12.240 --> 01:15:15.100
 their ability to meet our needs, that sort of thing.

01:15:15.100 --> 01:15:20.560
 So one, it's a much shorter walk, and two, safety is a priority, and I think it's key

01:15:20.560 --> 01:15:26.840
 that we can use the buses to manage that, we can use pooling of resources, offices,

01:15:26.840 --> 01:15:32.480
 that sort of thing, to bring served it into the junction if we have to in the interim.

01:15:32.480 --> 01:15:37.800
 So I think that's something that is immediately, when we open, we'll have a solve for that,

01:15:37.800 --> 01:15:44.200
 and we'll have a great plan in place, and I think that's critical.

01:15:44.200 --> 01:15:45.720
 I think that's all I have.

01:15:45.720 --> 01:15:48.920
 Council Member Bett.

01:15:48.920 --> 01:15:56.920
 I really applaud the Mayor's reminder about how important the bus is, and I think, I know

01:15:56.920 --> 01:16:02.560
 all the staff is trying to incorporate mass transit, so I really appreciate the Mayor

01:16:02.560 --> 01:16:07.920
 reminding us about the needs and the way the city can use the DCTA and the mass transit.

01:16:07.920 --> 01:16:13.840
 In terms of a couple of micro-directions that I'd like to emphasize, I concur with Mayor

01:16:13.840 --> 01:16:20.520
 Pro Tem that I don't know that we need to be pre-building out road networks for MUDs

01:16:20.520 --> 01:16:26.840
 and other areas, just being mindful of our mobility plan, so I would like to prioritize

01:16:26.840 --> 01:16:35.840
 our land and mobility use in advance of the mobility planning for future MUDs and let

01:16:35.840 --> 01:16:41.840
 them carry more of that burden if they're not going to participate immediately.

01:16:41.840 --> 01:16:50.920
 If you don't want to buy in NX and build in Denton, then that's one of the cons of putting

01:16:50.920 --> 01:16:54.600
 your MUD out in the county.

01:16:54.600 --> 01:16:59.040
 So don't expect us to necessarily prioritize you if that's what you're going to do.

01:16:59.040 --> 01:17:00.800
 So I agree with that.

01:17:00.800 --> 01:17:06.480
 And then the last sort of micro-direction, I'd like to just remind us as we're laying

01:17:06.480 --> 01:17:10.960
 out the precise alignments of a lot of our mobility planning, and I know you guys do

01:17:10.960 --> 01:17:20.840
 this, but to really be mindful of bridges that run over riparian areas and creeks, especially

01:17:20.840 --> 01:17:27.400
 in northeast Denton, and just to a large degree, Hunter Cole and there along Hickory Creek

01:17:27.400 --> 01:17:32.840
 and down through South Denton, as we hit those corridors, we're seeing the impacts of not

01:17:32.840 --> 01:17:38.200
 properly building bridges because we're having that emergency bridge rebuild down there in

01:17:38.200 --> 01:17:44.080
 that southwest section right now where there's accidents and accidents and accidents.

01:17:44.080 --> 01:17:56.320
 But let's just make sure and really, really be mindful of those sustainable sections that

01:17:56.320 --> 01:17:58.080
 are environmentally friendly as well.

01:17:58.080 --> 01:18:00.840
 So I'm just encouraging us on that one.

01:18:00.840 --> 01:18:01.840
 Yes, sir.

01:18:01.840 --> 01:18:02.840
 Thank you.

01:18:02.840 --> 01:18:03.840
 Okay.

01:18:03.840 --> 01:18:04.840
 Any other questions?

01:18:04.840 --> 01:18:07.680
 Mayor, if I could just jump in real quick, and just to address Mayor Portia-Milter and

01:18:07.680 --> 01:18:11.760
 Councilmember Beck's points about kind of building those roads for the MUDs in the northeast

01:18:11.760 --> 01:18:15.800
 because it's a really interesting discussion and something we had internally as we talked

01:18:15.800 --> 01:18:18.240
 about downgrading those roads.

01:18:18.240 --> 01:18:23.200
 I think an important thing to consider as well is by having them even at that downgraded

01:18:23.200 --> 01:18:27.600
 stage on the mobility plan, we can then have them in the impact fee studies means we can

01:18:27.600 --> 01:18:32.600
 have those future developments pay for those roads as opposed to waiting.

01:18:32.600 --> 01:18:37.160
 If we wait and then the need's there, we lose that funding capability, and you might be

01:18:37.160 --> 01:18:39.560
 possibly asking the entire community to pay for those.

01:18:39.560 --> 01:18:44.760
 So that's a reason to keep them on the mobility plan even at that downgraded stage.

01:18:44.760 --> 01:18:51.160
 Just obviously it's a trade-off, right, and I get the hesitation there, but that's some

01:18:51.160 --> 01:18:53.960
 of the thought process that went into that.

01:18:53.960 --> 01:18:54.960
 Okay.

01:18:54.960 --> 01:18:55.960
 Thank you, David.

01:18:55.960 --> 01:18:56.960
 Thank you.

01:18:56.960 --> 01:18:57.960
 Anyone else on council?

01:18:57.960 --> 01:18:58.960
 Any other questions?

01:18:58.960 --> 01:19:04.880
 Seeing none.

01:19:04.880 --> 01:19:11.080
 Any further questions on the commission?

01:19:11.080 --> 01:19:15.520
 If not, then do you have any additional presentations?

01:19:15.520 --> 01:19:20.160
 Obviously you have notes on the requested thoughts, changes, that sort of thing.

01:19:20.160 --> 01:19:21.560
 Anything else from staff's perspective?

01:19:21.560 --> 01:19:22.560
 No, sir.

01:19:22.560 --> 01:19:23.560
 Not for my item.

01:19:23.560 --> 01:19:25.440
 I'll turn it over to Ms. Fergens.

01:19:25.440 --> 01:19:26.440
 Okay.

01:19:26.440 --> 01:19:27.440
 Great.

01:19:27.440 --> 01:19:35.400
 I think we'll take a, it's 11.19, so let's take a 15-minute break.

01:19:35.400 --> 01:19:38.440
 We'll be back at 11.35.

01:19:38.440 --> 01:19:43.440
 I was going to say lunch will be here at 11.30.

01:19:43.440 --> 01:19:44.440
 Perfect.

01:19:44.440 --> 01:19:47.960
 So then let's stretch that a bit.

01:19:47.960 --> 01:19:56.440
 So let's come back at 11.50, and so in between time, if you have questions or other follow-ups,

01:19:56.440 --> 01:20:00.640
 you can grab staff, talk to them, and then, but we'll be back at 11.50 at bring back lunch

01:20:00.640 --> 01:20:03.200
 or finish lunch, whatever's your preference.

01:20:03.200 --> 01:20:04.200
 Thank you.

01:20:04.200 --> 01:20:05.200
 Thank you, sir.

01:20:05.200 --> 01:20:19.000
 We will adjourn now at 11.20.

01:20:19.000 --> 01:20:20.000
 And good morning.

01:20:20.000 --> 01:20:22.840
 It'll be afternoon in one minute.

01:20:22.840 --> 01:20:32.360
 We are back, and we are to the second portion of our meeting, but want to just give a heads

01:20:32.360 --> 01:20:33.360
 up at the end.

01:20:33.360 --> 01:20:39.280
 I'm going to ask and make sure from a council perspective that we're all clear on the questions

01:20:39.280 --> 01:20:47.920
 we've provided and ask that we can find consensus to give staff approval to skip another presentation

01:20:47.920 --> 01:20:54.400
 tomorrow so that they can prepare for next week's hearing with the consultant and get

01:20:54.400 --> 01:20:55.680
 them kind of closed out.

01:20:55.680 --> 01:20:59.960
 So at the end of this meeting, just to give you a heads up to be thinking about that,

01:20:59.960 --> 01:21:06.520
 what else can we speak to to clear that out so that they can have a workday tomorrow versus

01:21:06.520 --> 01:21:11.160
 presenting the same information again in preparation for next week's meeting?

01:21:11.160 --> 01:21:18.680
 So that being said, I'll turn it over to oh, and then so it's what's 12.

01:21:18.680 --> 01:21:19.680
 We're back.

01:21:19.680 --> 01:21:20.920
 And so I'll let you call.

01:21:20.920 --> 01:21:21.920
 Thank you, Mayor.

01:21:21.920 --> 01:21:25.400
 I will call reconvene the commission meeting at 12 noon.

01:21:25.400 --> 01:21:26.400
 Great.

01:21:26.400 --> 01:21:27.400
 All right.

01:21:27.400 --> 01:21:28.400
 Thank you, Mayor.

01:21:28.400 --> 01:21:29.400
 Thank you, Chairman Ellis.

01:21:29.400 --> 01:21:34.960
 So I'm happy to be here again to talk about the Conference of Plan, and we're hopefully

01:21:34.960 --> 01:21:39.240
 narrowing down our conversations as we move towards finalizing the document.

01:21:39.240 --> 01:21:42.520
 So with me, I have Ed Boyk with Matrix Design Group.

01:21:42.520 --> 01:21:44.800
 So he and I are going to be doing a tag team presentation.

01:21:44.800 --> 01:21:48.960
 In fact, majority of it will probably be Ed, but and then also I have Ron Mangito on my

01:21:48.960 --> 01:21:53.440
 team as well to assist with any questions that we have following up.

01:21:53.440 --> 01:21:59.720
 What I would like to do is before we get into the more in-depth in our presentation, I thought

01:21:59.720 --> 01:22:02.360
 I'd start with the calendar slide first.

01:22:02.360 --> 01:22:04.080
 We typically wrap up with that.

01:22:04.080 --> 01:22:08.080
 But as you all know, we've had quite a bit of discussion and just wanted to put this

01:22:08.080 --> 01:22:11.000
 on the forefront for your consideration.

01:22:11.000 --> 01:22:14.280
 As we're moving into what I would like to think hopefully is the home stretch with respect

01:22:14.280 --> 01:22:17.440
 to this particular project as well as the mobility plan.

01:22:17.440 --> 01:22:21.760
 So obviously right now we're on February 14th and we had some great discussion earlier and

01:22:21.760 --> 01:22:25.440
 our purpose this afternoon of our presentation is going to recap what we've heard from the

01:22:25.440 --> 01:22:27.760
 City Council and the Planning and Zoning Commission.

01:22:27.760 --> 01:22:32.000
 I believe we have consensus on pretty much everything that we presented in a path forward.

01:22:32.000 --> 01:22:35.320
 And so Ed's going to go through all of that recap of what we've heard from both of these

01:22:35.320 --> 01:22:37.300
 groups combined.

01:22:37.300 --> 01:22:42.520
 And then with that, we do have teed up tomorrow afternoon with Council in the event we needed

01:22:42.520 --> 01:22:44.620
 to have one last discussion.

01:22:44.620 --> 01:22:49.640
 Hopefully with the information that we share with you today, that that will not be necessary.

01:22:49.640 --> 01:22:53.200
 But if we missed something during our recap, then please let us know after Ed's had an

01:22:53.200 --> 01:22:55.200
 opportunity to present the slides.

01:22:55.200 --> 01:22:59.600
 But really we're liking to focus on our next steps then after this week is for our public

01:22:59.600 --> 01:23:00.960
 hearing phase.

01:23:00.960 --> 01:23:03.080
 So moving into adoption.

01:23:03.080 --> 01:23:07.360
 So next Wednesday, February 23rd is when we anticipate having the public hearing with the

01:23:07.360 --> 01:23:08.800
 Planning and Zoning Commission.

01:23:08.800 --> 01:23:12.160
 If the Planning and Zoning Commission is able to offer a recommendation on the comprehensive

01:23:12.160 --> 01:23:18.720
 plan, then we would move forward to the City Council meeting on March 1st for your final

01:23:18.720 --> 01:23:21.280
 action and adoption associated with the plan.

01:23:21.280 --> 01:23:25.960
 Not only the comprehensive plan, but hopefully the mobility plan along with that.

01:23:25.960 --> 01:23:30.040
 We added a couple of additional days to the calendar that might look of interest to you.

01:23:30.040 --> 01:23:34.280
 So you've heard us say many times of the whole area plans discussion, how we've had area

01:23:34.280 --> 01:23:38.520
 plans teed up for right after we get the comprehensive plan adopted.

01:23:38.520 --> 01:23:42.080
 So right now we have that slated for March 9th with the Planning and Zoning Commission.

01:23:42.080 --> 01:23:46.640
 This is where we'll enter into that conversation about prioritizing areas that we believe should

01:23:46.640 --> 01:23:49.240
 benefit from area plans.

01:23:49.240 --> 01:23:52.480
 And then once the Planning and Zoning Commission's had an opportunity to have that conversation,

01:23:52.480 --> 01:23:56.760
 then we'll bring forth their recommendations to the City Council for your consideration

01:23:56.760 --> 01:24:03.320
 on April 5th, not 15th, the 5th, so we can get your direction.

01:24:03.320 --> 01:24:07.280
 Because that will also be important as we move into budget preparation, because some

01:24:07.280 --> 01:24:11.760
 of this will need some financial assistance to go along with completing the area plans.

01:24:11.760 --> 01:24:16.040
 But with that, unless there's any questions regarding the calendar, I'd like to turn it

01:24:16.040 --> 01:24:20.080
 over then to Ed Boyk, and he'll start with this presentation.

01:24:20.080 --> 01:24:25.200
 And I would like to tee up just his comments that he's going to make as a result of some

01:24:25.200 --> 01:24:29.120
 additional comments or questions that we received from Mayor Pro Tem Meltzer over the weekend.

01:24:29.120 --> 01:24:33.960
 So Ed, if you're there, I'll turn it over to you.

01:24:33.960 --> 01:24:34.960
 Thank you, Tina.

01:24:34.960 --> 01:24:39.560
 Ed Boyk with Matrix Design Group, Mayor, Chair of the Planning and Zoning Commission.

01:24:39.560 --> 01:24:44.160
 I'm happy to be here and present these last hopefully items for the work session for this

01:24:44.160 --> 01:24:46.120
 comprehensive plan update.

01:24:46.120 --> 01:24:50.320
 And as Tina had noted, we did receive some comments just over the weekend regarding the

01:24:50.320 --> 01:24:54.400
 same sustainability and how that relates to the comprehensive plan.

01:24:54.400 --> 01:24:57.560
 And we wanted to reiterate that it's a major theme of the comprehensive plan.

01:24:57.560 --> 01:25:02.080
 It's one of the four main elements that's retained in the comprehensive plan update,

01:25:02.080 --> 01:25:06.120
 referenced probably eight times or more in the conservation and environmental element

01:25:06.120 --> 01:25:07.120
 alone.

01:25:07.120 --> 01:25:12.520
 But not only that, the sustainability aspects are touched on throughout the plan, whether

01:25:12.520 --> 01:25:18.300
 environmental, energy, transportation, land use, parks, recreation, open space, and quality

01:25:18.300 --> 01:25:19.300
 of life.

01:25:19.300 --> 01:25:27.720
 So it is a major theme, the sustainability framework, the 2020 update is specifically

01:25:27.720 --> 01:25:29.720
 referred to and identified as well.

01:25:29.720 --> 01:25:36.520
 So again, just to reiterate, it is an important aspect of this plan and is a guiding influence

01:25:36.520 --> 01:25:40.440
 as this plan has been prepared and updated.

01:25:40.440 --> 01:25:46.640
 So moving on to the recap of what we heard on the slide, we just want to make sure that

01:25:46.640 --> 01:25:51.080
 we illustrate that we're hearing what the council and the commission have told us and

01:25:51.080 --> 01:25:52.080
 we're responding to it.

01:25:52.080 --> 01:25:54.360
 So I'm just going to run through these briefly.

01:25:54.360 --> 01:25:56.600
 We confirmed that the vision statement was good.

01:25:56.600 --> 01:26:01.200
 There was no additional comments that reflects the vision of the community and the council

01:26:01.200 --> 01:26:02.840
 and the commission.

01:26:02.840 --> 01:26:07.280
 We heard that option two was preferred for the future land use map.

01:26:07.280 --> 01:26:11.160
 And I have a slide coming up that'll show that, that shows a little bit more clarity

01:26:11.160 --> 01:26:17.560
 about the authority within the ETJ and those MUDs that are either through an approved process

01:26:17.560 --> 01:26:22.600
 or pending, moving through a process, the preferred pattern of land preservation.

01:26:22.600 --> 01:26:23.600
 That plan was confirmed.

01:26:23.600 --> 01:26:26.980
 We're going to place that in the plan and I'll talk about that in a future slide.

01:26:26.980 --> 01:26:29.600
 A little bit detail about the future land use map.

01:26:29.600 --> 01:26:33.560
 There's really no additional changes that was confirmed by the commission.

01:26:33.560 --> 01:26:38.100
 But importantly, we'll show that relationship between the future land use plan and some

01:26:38.100 --> 01:26:42.200
 other plans that are within the document such as the preferred pattern of growth in the

01:26:42.200 --> 01:26:43.520
 focus area plans.

01:26:43.520 --> 01:26:45.880
 Implementation, we got some good comments on that.

01:26:45.880 --> 01:26:52.080
 We'll talk about that in the slide as well as Tina alluded to, leading towards area plans

01:26:52.080 --> 01:26:57.440
 and then the actions in the implementation table such as infill and redevelopment activities,

01:26:57.440 --> 01:26:58.880
 how we can move forward with that.

01:26:58.880 --> 01:27:05.880
 So I'm going to move on to the next slide and recap the comments we heard regarding

01:27:05.880 --> 01:27:07.880
 the implementation.

01:27:07.880 --> 01:27:12.440
 Planned planning and zoning commission are both very interested in making sure that this

01:27:12.440 --> 01:27:14.640
 plan was not just one that sat on a shelf.

01:27:14.640 --> 01:27:21.580
 Something that could be acted upon and move forward so that these actions move forward

01:27:21.580 --> 01:27:26.480
 as they should on an ongoing, short-term, mid-term or long-term basis.

01:27:26.480 --> 01:27:28.920
 The plan already has accommodations built into it.

01:27:28.920 --> 01:27:32.880
 There's a series of principles that are found in Chapter 10 to identify how the plan relates

01:27:32.880 --> 01:27:37.960
 to other plans and policies, how it's to be used, how you should find conformance between

01:27:37.960 --> 01:27:40.360
 the land use plan and the zoning map and so on.

01:27:40.360 --> 01:27:43.840
 But principle five is the one that's very important because it talks about the city

01:27:43.840 --> 01:27:49.240
 preparing and monitoring and evaluation report and using metrics as appropriate to measure

01:27:49.240 --> 01:27:50.780
 that progress of the plan.

01:27:50.780 --> 01:27:55.320
 This will give the city staff an opportunity to work with the planning and zoning commission

01:27:55.320 --> 01:28:02.060
 to work together to actively implement, monitor, assess and then report forward to the city

01:28:02.060 --> 01:28:05.020
 council the performance of this comprehensive plan.

01:28:05.020 --> 01:28:10.920
 So we're happy to make sure that it's widely known and then transparent that there are

01:28:10.920 --> 01:28:15.620
 mechanisms built in place to take care of the measurement and the continued success

01:28:15.620 --> 01:28:18.040
 of this plan.

01:28:18.040 --> 01:28:21.540
 As I mentioned earlier, there was two different options for the future land use map presented

01:28:21.540 --> 01:28:24.600
 to the city council and to the commission.

01:28:24.600 --> 01:28:28.040
 Option one on the left was the original staff recommendation, but hearing the comments from

01:28:28.040 --> 01:28:35.000
 both bodies, it made it very clear that option two was the preferred way to illustrate those

01:28:35.000 --> 01:28:39.880
 municipal utility districts within the ETJs in Denton.

01:28:39.880 --> 01:28:45.600
 Specifically, low density residential land use is illustrated for those LUDs that have

01:28:45.600 --> 01:28:49.960
 been through an approval process or through a state legislative process and are moving

01:28:49.960 --> 01:28:52.600
 forward for development.

01:28:52.600 --> 01:28:56.480
 The ones which are outlined in pink are the ones that are conceptual.

01:28:56.480 --> 01:28:57.880
 Denton's aware of them.

01:28:57.880 --> 01:29:01.960
 They exist to some capacity, but they haven't moved through a formal approval review or

01:29:01.960 --> 01:29:04.240
 state legislative process at this point.

01:29:04.240 --> 01:29:08.840
 However, in the effort of transparency, they're illustrated on the future map so that the

01:29:08.840 --> 01:29:14.040
 community and others that may use this may understand that while the long-term vision

01:29:14.040 --> 01:29:20.440
 for Denton is to have these preferred preservation land uses, the rural and agricultural land

01:29:20.440 --> 01:29:25.560
 uses throughout the ETJ, there are opportunities and possible situations where that could change

01:29:25.560 --> 01:29:33.400
 depending if those LUDs, which Denton has limited authority for regulating, move forward.

01:29:33.400 --> 01:29:37.960
 In conjunction with the future land use plan is the preferred land preservation plan.

01:29:37.960 --> 01:29:42.500
 No changes are provided between what you've seen last time at the work session and this

01:29:42.500 --> 01:29:47.840
 one, but we are going to include, based on your recommendation, the preferred land preservation

01:29:47.840 --> 01:29:49.800
 plan within the comprehensive plan.

01:29:49.800 --> 01:29:54.320
 It'll be right behind the future land use plan so that there's a clear understanding

01:29:54.320 --> 01:29:59.340
 of the relationship between the future land use plan and this preferred land preservation

01:29:59.340 --> 01:30:03.280
 plan and how they work with each other.

01:30:03.280 --> 01:30:07.100
 Some additional actions will be included in the plan.

01:30:07.100 --> 01:30:15.460
 These will be actions to add some clarification for policies, codes, implementation, consistency

01:30:15.460 --> 01:30:19.760
 between plans, and will be implemented as appropriate to make sure that these different

01:30:19.760 --> 01:30:24.920
 topics such as wildlife corridors, green space, connectivity, parks and trails, etc., tree

01:30:24.920 --> 01:30:31.520
 canopy greater than 30 percent, all of these different things are important to the community,

01:30:31.520 --> 01:30:36.160
 are clearly identified in the action table and the implementation, and will be moved

01:30:36.160 --> 01:30:43.000
 forward and acted upon in the appropriate timeframes as per the comprehensive plan.

01:30:43.000 --> 01:30:48.000
 So the final additional items, again, further evaluation is going to be conducted at this

01:30:48.000 --> 01:30:53.240
 meeting to discuss the mobility plan and its relationship to the future land use plan.

01:30:53.240 --> 01:30:57.520
 As I noted before, that preferred land preservation plan will be inserted into the comprehensive

01:30:57.520 --> 01:30:59.880
 plan based on the comments that we have received.

01:30:59.880 --> 01:31:04.000
 There'll be actions will be enhanced as appropriate to make sure that it's very clear about how

01:31:04.000 --> 01:31:07.280
 that preferred land preservation plan is to be used.

01:31:07.280 --> 01:31:11.080
 And then as I noted before, the implementation metrics is another piece that we wanted to

01:31:11.080 --> 01:31:16.240
 make sure was very clear that they will be prepared by staff, the metrics, they will

01:31:16.240 --> 01:31:20.840
 be updated and reviewed by the Planning and Zoning Commission and provided to the council

01:31:20.840 --> 01:31:22.120
 annually.

01:31:22.120 --> 01:31:27.280
 And that is something that's already in the plan and helps to make sure this plan is not

01:31:27.280 --> 01:31:30.080
 just that plan that sits on a shelf.

01:31:30.080 --> 01:31:34.920
 The last several slides that I have, I'll flip between them just because the future

01:31:34.920 --> 01:31:39.920
 land use plan and the plans that follow have a relationship to each other.

01:31:39.920 --> 01:31:45.120
 First, the future land use plan as a general high level sets the overall tone for the land

01:31:45.120 --> 01:31:47.220
 use policy for the community.

01:31:47.220 --> 01:31:51.600
 It's coordinated with existing plans, including the parks plan, the mobility plan, as we discussed

01:31:51.600 --> 01:31:59.440
 earlier today, as well as it reflects in the more refined detail on planning that has taken

01:31:59.440 --> 01:32:06.520
 place for, say, the master plan communities, as well as showing those muds either approved

01:32:06.520 --> 01:32:11.480
 or not approved, but potentially moving forward through the process.

01:32:11.480 --> 01:32:15.680
 But because this is a high level general plan, it works in concert with plans such as the

01:32:15.680 --> 01:32:19.880
 preferred growth scenario plan, which is a little different than the future land use

01:32:19.880 --> 01:32:26.520
 plan because this is a plan that helps to identify where those potentially more intense

01:32:26.520 --> 01:32:33.200
 functions could occur, like more employment uses or more community building or mixed use

01:32:33.200 --> 01:32:35.280
 or intense development.

01:32:35.280 --> 01:32:39.840
 The circles that were illustrated on there are not boundaries, they're kind of generalized

01:32:39.840 --> 01:32:45.160
 areas that illustrate that these are these focus areas of downtown Denton that would

01:32:45.160 --> 01:32:50.620
 have more intensity at the core and then potentially moderate out to a lower density on the outside

01:32:50.620 --> 01:32:57.000
 so that those low density residential neighborhoods surrounding downtown are not necessarily overtaken

01:32:57.000 --> 01:33:00.880
 and then become something that is not the vision of the community, but it just establishes

01:33:00.880 --> 01:33:02.720
 that this is a focus point.

01:33:02.720 --> 01:33:09.160
 A couple have been added to this map, in particular, a couple of brown circles around the master

01:33:09.160 --> 01:33:15.280
 plan communities to identify that these preferred growth scenario areas are areas where the

01:33:15.280 --> 01:33:22.120
 city expects to see growth occur on the periphery, new areas, the green field areas, as well

01:33:22.120 --> 01:33:26.200
 as the rest of this map is identifying those areas within the community where there could

01:33:26.200 --> 01:33:28.480
 be more redevelopment or infill development.

01:33:28.480 --> 01:33:35.280
 So it illustrates that balance of growth between those new master planned areas and those existing

01:33:35.280 --> 01:33:41.160
 areas that can be enhanced and refined and provide a diversity of housing types and diversity

01:33:41.160 --> 01:33:43.440
 of living arrangements for the community.

01:33:43.440 --> 01:33:50.880
 The purple, as noted before, is expanded through the area near the west side of I-35 and 288

01:33:50.880 --> 01:33:54.760
 as well as on the northeast corner of that intersection as well.

01:33:54.760 --> 01:34:00.040
 This is that area that was identified on the future land use map as a light industrial.

01:34:00.040 --> 01:34:04.400
 It's really one of the employment focus areas in the community and it supports and complements

01:34:04.400 --> 01:34:09.960
 the employment areas that are around or will be growing around the Denton Airport into

01:34:09.960 --> 01:34:12.920
 the future, as you can see on this map.

01:34:12.920 --> 01:34:18.720
 So moving on to a little bit more focused, appropriately named the Focused Areas Concept

01:34:18.720 --> 01:34:19.720
 Plan.

01:34:19.720 --> 01:34:24.880
 This is a focused look at those areas in the community that are either existing today as

01:34:24.880 --> 01:34:31.120
 those special or unique areas in Denton that should be focused on for additional planning

01:34:31.120 --> 01:34:32.120
 and refinement.

01:34:32.120 --> 01:34:36.980
 This has been something that was developed through the 2030 plan process and reaffirmed

01:34:36.980 --> 01:34:39.280
 through the 2040 process.

01:34:39.280 --> 01:34:42.840
 Since the last time you saw this, we also, well actually during the last time you saw

01:34:42.840 --> 01:34:49.120
 it, there was identification of area planning areas that potentially could be pursued in

01:34:49.120 --> 01:34:54.820
 the northeast part of Denton, southeast of downtown as well as that employment focus

01:34:54.820 --> 01:34:57.560
 area at I-35 and 288.

01:34:57.560 --> 01:35:04.160
 So among that, all these different circular dashed areas illustrate those focus areas

01:35:04.160 --> 01:35:07.640
 or areas where the area planning could be focused.

01:35:07.640 --> 01:35:11.520
 Not saying that these are the only ones, but those are the ones that were identified through

01:35:11.520 --> 01:35:14.240
 the various community outreach process.

01:35:14.240 --> 01:35:16.840
 The highlighted roadways are those corridor focus areas.

01:35:16.840 --> 01:35:21.520
 So these could be areas that are those gateways or windows into the community that help to

01:35:21.520 --> 01:35:29.680
 define the character of Denton and those could benefit from area or corridor planning that

01:35:29.680 --> 01:35:37.660
 focus in on design or architecture or whatever to help brand the community and illustrate

01:35:37.660 --> 01:35:43.200
 what Denton is to those that may be driving by or through the community or visiting the

01:35:43.200 --> 01:35:47.780
 community for tourist purposes or work or living in the area.

01:35:47.780 --> 01:35:53.320
 Those area plan areas that are identified through those circular dashed areas, I mean

01:35:53.320 --> 01:35:58.560
 they could be things that identify design and character and architecture and land use.

01:35:58.560 --> 01:36:03.000
 It could support mixed use, it could support a single use, but it could be a variety of

01:36:03.000 --> 01:36:04.280
 different things.

01:36:04.280 --> 01:36:09.440
 But the important thing is that these three maps together work together to tell the story

01:36:09.440 --> 01:36:15.100
 about how Denton should move forward from a general land use perspective to identifying

01:36:15.100 --> 01:36:22.800
 those areas where more intense growth or future growth is intended or envisioned in regards

01:36:22.800 --> 01:36:29.440
 to preservation and balanced efforts of growth between new and within the community.

01:36:29.440 --> 01:36:34.240
 And then those focus areas to say if we are going to focus growth or have those intense

01:36:34.240 --> 01:36:39.600
 areas of growth, we need to think about ways that we can plan them appropriately to ensure

01:36:39.600 --> 01:36:44.960
 that they reflect the values of the community, the vision of the community, and the character

01:36:44.960 --> 01:36:49.760
 of Denton that is extremely unique so they can continue to be that way far into the future

01:36:49.760 --> 01:36:52.400
 through the year 2040.

01:36:52.400 --> 01:36:57.360
 So with that, I wanted to just go over the next steps that we're looking for at this

01:36:57.360 --> 01:36:58.560
 point.

01:36:58.560 --> 01:37:02.240
 As noted earlier, there could be an additional city council work session tomorrow.

01:37:02.240 --> 01:37:04.080
 I know that's up for discussion.

01:37:04.080 --> 01:37:09.260
 If there is any discussion that's needed, that will be available.

01:37:09.260 --> 01:37:13.440
 In the meantime, staff and Matrix will work together to edit the comprehensive plan and

01:37:13.440 --> 01:37:18.840
 refine it to make that final version of it and have it ready to go for the public hearing

01:37:18.840 --> 01:37:23.720
 process which will follow starting on the 23rd with the planning and zoning commission

01:37:23.720 --> 01:37:28.120
 and resolving with the city council on March 1st.

01:37:28.120 --> 01:37:38.680
 And this is the first steps to allowing for that more detailed discussion into prioritizing

01:37:38.680 --> 01:37:44.320
 those implementation tasks such as the area plans which Tina had alluded to, or not even

01:37:44.320 --> 01:37:49.880
 alluded to but specifically mentioned, starting on March 9th and then continuing on April

01:37:49.880 --> 01:37:51.360
 5th with the city council.

01:37:51.360 --> 01:37:56.640
 So with that, I'd be happy to answer any questions or take or receive any comments you might

01:37:56.640 --> 01:37:57.640
 have.

01:37:57.640 --> 01:38:00.920
 And I'll also turn this back over to Tina if she has anything to add at this point.

01:38:00.920 --> 01:38:01.920
 So thank you.

01:38:01.920 --> 01:38:02.920
 >> Thank you, Ed.

01:38:02.920 --> 01:38:03.920
 >> Okay.

01:38:03.920 --> 01:38:04.920
 Thank you.

01:38:04.920 --> 01:38:11.200
 Commissioner Reynolds.

01:38:11.200 --> 01:38:12.520
 >> Thank you, Mayor.

01:38:12.520 --> 01:38:24.120
 Commissioners, any questions at this moment for staff or Ed?

01:38:24.120 --> 01:38:26.800
 I don't see any at this time, so I'll turn it back to you.

01:38:26.800 --> 01:38:27.800
 >> Great.

01:38:27.800 --> 01:38:28.800
 Thank you.

01:38:28.800 --> 01:38:29.800
 Council, direction for staff.

01:38:29.800 --> 01:38:30.800
 Anyone?

01:38:30.800 --> 01:38:31.800
 Seeing none.

01:38:31.800 --> 01:38:39.200
 Councilor Betz?

01:38:39.200 --> 01:38:51.560
 >> This is small and probably niggly, but why on the preferred growth map, we're kind

01:38:51.560 --> 01:38:55.240
 of using -- this is so small and I feel silly for saying it.

01:38:55.240 --> 01:38:57.520
 >> I was going to say now are we policy level or are we getting into the weeds?

01:38:57.520 --> 01:38:58.520
 >> No, no.

01:38:58.520 --> 01:38:59.520
 It's for this document.

01:38:59.520 --> 01:39:00.520
 No weeds at all.

01:39:00.520 --> 01:39:01.520
 >> Okay.

01:39:01.520 --> 01:39:08.280
 So the question I have is consistency in presentation for the public-facing documentation, and it

01:39:08.280 --> 01:39:19.780
 seems like our focus map is different than the rest of our mapping layouts, and I've

01:39:19.780 --> 01:39:26.000
 actually -- what brought this up is questions from citizens, like, I don't understand this

01:39:26.000 --> 01:39:30.040
 sort of blur and style doing the map.

01:39:30.040 --> 01:39:38.600
 And so let me say it might do us -- it might be beneficial to make those mapping stylings

01:39:38.600 --> 01:39:43.880
 consistent throughout the document to avoid citizen questions.

01:39:43.880 --> 01:39:48.800
 >> Is it particularly -- you mentioned the preferred growth theory map or the concept

01:39:48.800 --> 01:39:49.800
 map?

01:39:49.800 --> 01:39:50.800
 >> Let me get to the right.

01:39:50.800 --> 01:39:57.720
 Well, the preferred growth, I think, where we had the purple bars for industrial and

01:39:57.720 --> 01:40:03.440
 shopping and I just was getting a lot of -- the stylings of it -- no, I wasn't getting a lot.

01:40:03.440 --> 01:40:07.400
 I've got a couple questions, so I thought I would bring it up since there was no substantial

01:40:07.400 --> 01:40:08.400
 questions.

01:40:08.400 --> 01:40:14.400
 And that is just in terms of education, outreach, and community engagement, maybe if there's

01:40:14.400 --> 01:40:20.300
 an opportunity to make those maps more consistent, I don't want to belabor this point just visually

01:40:20.300 --> 01:40:25.040
 so that as they flip between the different maps, they understand they're looking at the

01:40:25.040 --> 01:40:28.240
 same map over and over and over, displaying different things, and they know they're looking

01:40:28.240 --> 01:40:29.240
 at Denton.

01:40:29.240 --> 01:40:34.520
 But it just -- this is one of those things where I just think we could avoid questions

01:40:34.520 --> 01:40:37.240
 to staff if we make them a little more consistent.

01:40:37.240 --> 01:40:42.840
 >> Well, and I know we have on that preferred growth scenario map, I know we were making

01:40:42.840 --> 01:40:46.280
 a quick adjustment to the map as a result of direction we received from council.

01:40:46.280 --> 01:40:49.760
 And so we know we need to go back and clean up some of the editing.

01:40:49.760 --> 01:40:53.560
 So if the concern was, well, how come the edges on this purple area are a little more

01:40:53.560 --> 01:40:59.800
 fuzzy and shady compared to the area on the northwest quadrant, or at I-35 and 2A?

01:40:59.800 --> 01:41:02.280
 We know we can do a little mapping cleanup there.

01:41:02.280 --> 01:41:06.240
 Those were some crude edits as a result of direction that we've gotten both from PNZ

01:41:06.240 --> 01:41:10.860
 and council to try and move along our conversation so that we know we have some cleanup that

01:41:10.860 --> 01:41:12.520
 needs to be done.

01:41:12.520 --> 01:41:16.560
 If the question, though, that you're receiving from the public, though, is the interrelationship

01:41:16.560 --> 01:41:20.180
 between the maps, then -- so one of the challenges you have is the public's not then reading

01:41:20.180 --> 01:41:25.200
 the words that are in the document also and seeing these maps in the context of the document.

01:41:25.200 --> 01:41:29.400
 So that's where that additional explanation is within the comprehensive plan that explains

01:41:29.400 --> 01:41:31.920
 the relationships amongst the maps.

01:41:31.920 --> 01:41:33.120
 Also we're here as a resource.

01:41:33.120 --> 01:41:35.600
 We continue to be a resource for educating the public.

01:41:35.600 --> 01:41:39.760
 So if folks have questions, whether they're residents or property owners, they're looking

01:41:39.760 --> 01:41:43.080
 to invest within the community, whatever the case is, that's where we as staff also serve

01:41:43.080 --> 01:41:48.360
 as an educator in what the maps are trying to convey and what the document is saying.

01:41:48.360 --> 01:41:52.720
 So I think it's all there, but if they're just looking at these maps individually as

01:41:52.720 --> 01:41:56.320
 what you're getting in your presentations, then they're missing the context of how they're

01:41:56.320 --> 01:41:57.320
 presented.

01:41:57.320 --> 01:42:02.440
 And I will say, just as a comment to that, that there's a common phrase in lots of documentation

01:42:02.440 --> 01:42:08.000
 literature of RTFM, and I'm not going to say what the F stands for.

01:42:08.000 --> 01:42:15.680
 And I'll leave it to people to Google that, the safety of the privacy of their own homes.

01:42:15.680 --> 01:42:19.520
 When it is, people simply look at the pictures and they don't follow the narratives.

01:42:19.520 --> 01:42:20.520
 And so just be aware.

01:42:20.520 --> 01:42:23.760
 I'm just trying to save us some future question time is all.

01:42:23.760 --> 01:42:24.760
 Okay.

01:42:24.760 --> 01:42:25.760
 Thank you.

01:42:25.760 --> 01:42:26.760
 Okay.

01:42:26.760 --> 01:42:27.760
 Any other questions?

01:42:27.760 --> 01:42:28.760
 Okay.

01:42:28.760 --> 01:42:29.760
 Seeing none.

01:42:29.760 --> 01:42:30.760
 Commissioner, one more time.

01:42:30.760 --> 01:42:31.760
 Oh, you've got mayor.

01:42:31.760 --> 01:42:32.760
 Oh, mayor for Tim Meltzer.

01:42:32.760 --> 01:42:33.760
 Yeah.

01:42:33.760 --> 01:42:34.760
 Thank you.

01:42:34.760 --> 01:42:35.760
 Actually, not a question.

01:42:35.760 --> 01:42:50.600
 Just a gratitude, I feel like you've really listened, and I think the plan is being improved

01:42:50.600 --> 01:42:51.600
 through the dialogue.

01:42:51.600 --> 01:42:52.600
 So just thank you.

01:42:52.600 --> 01:42:53.600
 You're welcome.

01:42:53.600 --> 01:42:54.600
 Thank you.

01:42:54.600 --> 01:42:55.600
 Okay.

01:42:55.600 --> 01:42:59.520
 Councilmember Boer.

01:42:59.520 --> 01:43:05.600
 I think that this is, you know, very responsive to the feedback that we've all given.

01:43:05.600 --> 01:43:11.320
 And in light of how responsive you all have been, I would feel comfortable skipping tomorrow's

01:43:11.320 --> 01:43:16.920
 work session and just seeing this again at the public hearing.

01:43:16.920 --> 01:43:18.120
 Okay.

01:43:18.120 --> 01:43:20.000
 Thank you for that.

01:43:20.000 --> 01:43:24.680
 Seeing no other request to speak, making sure I'm not missing anyone.

01:43:24.680 --> 01:43:25.680
 Okay.

01:43:25.680 --> 01:43:26.680
 Let me check.

01:43:26.680 --> 01:43:27.680
 You good?

01:43:27.680 --> 01:43:28.680
 Yeah.

01:43:28.680 --> 01:43:29.680
 Commissioner, any questions?

01:43:29.680 --> 01:43:30.680
 Okay.

01:43:30.680 --> 01:43:31.680
 I don't see any.

01:43:31.680 --> 01:43:32.680
 Yeah.

01:43:32.680 --> 01:43:35.400
 I'll just say, you know, thank you again for all the hard work.

01:43:35.400 --> 01:43:39.200
 That collaborative effort needed and welcome change to the comp plan.

01:43:39.200 --> 01:43:42.360
 So yeah, it's exciting to be able to move this forward.

01:43:42.360 --> 01:43:43.360
 Thank you.

01:43:43.360 --> 01:43:44.360
 Yeah.

01:43:44.360 --> 01:43:48.680
 And I'll say I appreciate Ed pointing it out and staff pointing it out as well, that annual

01:43:48.680 --> 01:43:52.560
 look at it from a planning zoning perspective, really good.

01:43:52.560 --> 01:43:58.160
 You know, that'll be good to make sure it's active and matches what we've been seeing.

01:43:58.160 --> 01:44:00.580
 And forgive me if I've missed it.

01:44:00.580 --> 01:44:05.360
 Is there anything we can do with respect to, did you have a chance to look into the loophole

01:44:05.360 --> 01:44:12.320
 component with respect to zonings that, you know, kind of a one-offs to help us identify

01:44:12.320 --> 01:44:13.320
 those?

01:44:13.320 --> 01:44:14.320
 Right.

01:44:14.320 --> 01:44:18.080
 So we have an action item within the comprehensive plan that speaks to evaluating the zoning

01:44:18.080 --> 01:44:24.240
 for consistency with the comprehensive plan so that we can continue to look for those.

01:44:24.240 --> 01:44:28.240
 And I think in the instance that you're speaking to, Haley was kind enough to give me a little

01:44:28.240 --> 01:44:32.360
 background information on that, that I think the particular land use in question was actually

01:44:32.360 --> 01:44:36.920
 allowed by right in that particular district, but what I would say is that if the zoning

01:44:36.920 --> 01:44:41.280
 district that's in place is inconsistent with our comprehensive plan recommendations, then

01:44:41.280 --> 01:44:43.360
 there's an opportunity for us to go back and take a look at that.

01:44:43.360 --> 01:44:47.880
 But that goes back to that overarching action item that speaks to periodically evaluating

01:44:47.880 --> 01:44:50.600
 our zoning to make sure it's consistent with the comprehensive plan.

01:44:50.600 --> 01:44:51.600
 Got it.

01:44:51.600 --> 01:44:52.600
 Okay.

01:44:52.600 --> 01:44:53.600
 Yeah.

01:44:53.600 --> 01:44:54.600
 Okay.

01:44:54.600 --> 01:44:55.600
 Great.

01:44:55.600 --> 01:44:56.600
 Thank you for that.

01:44:56.600 --> 01:44:57.600
 Okay.

01:44:57.600 --> 01:45:04.840
 If there's anyone that is against giving staff a workday tomorrow to finalize this for public

01:45:04.840 --> 01:45:07.760
 hearing, then you'd need to say so.

01:45:07.760 --> 01:45:12.560
 Otherwise, I'm going to assume we don't need to hear the same presentation tomorrow.

01:45:12.560 --> 01:45:14.760
 See none?

01:45:14.760 --> 01:45:16.060
 Great.

01:45:16.060 --> 01:45:18.040
 So that's the direction on both of those.

01:45:18.040 --> 01:45:21.920
 So thank you all very much for your help.

01:45:21.920 --> 01:45:23.920
 Do we have anything else?

01:45:23.920 --> 01:45:24.920
 That's all we had on the agenda.

01:45:24.920 --> 01:45:25.920
 So unless you have anything else-

01:45:25.920 --> 01:45:26.920
 No, that's it, Mayor.

01:45:26.920 --> 01:45:30.520
 I'm sorry?

01:45:30.520 --> 01:45:31.520
 That's all that's on the agenda.

01:45:31.520 --> 01:45:32.520
 Good.

01:45:32.520 --> 01:45:33.520
 We finished it for today.

01:45:33.520 --> 01:45:34.520
 Good.

01:45:34.520 --> 01:45:35.520
 Good.

01:45:35.520 --> 01:45:36.520
 Ed, you do great work.

01:45:36.520 --> 01:45:37.520
 I'm going to give you...

01:45:37.520 --> 01:45:42.760
 No, I appreciate your team being responsive, the additional meetings, that sort of thing.

01:45:42.760 --> 01:45:44.720
 So spinning up and scaling.

01:45:44.720 --> 01:45:46.920
 So thank you very much for that.

01:45:46.920 --> 01:45:49.960
 So then, Commissioner Ellis, anything?

01:45:49.960 --> 01:45:50.960
 It's been...

01:45:50.960 --> 01:45:51.960
 Thank you.

01:45:51.960 --> 01:45:52.960
 Commissioner Ellis, I used to serve on P&Z together.

01:45:52.960 --> 01:45:54.920
 So this is nostalgic for you.

01:45:54.920 --> 01:45:55.920
 It is.

01:45:55.920 --> 01:45:58.000
 It makes me feel comfortable being next to her.

01:45:58.000 --> 01:46:00.200
 But anything else you want to add before we...

01:46:00.200 --> 01:46:05.480
 No, I think the only thing that I would like to add is, well, this is the first joint session

01:46:05.480 --> 01:46:10.400
 in my five-plus years on P&Z that we've had.

01:46:10.400 --> 01:46:15.520
 I would have liked to have seen this at the beginning of maybe after we heard it one time

01:46:15.520 --> 01:46:20.400
 versus at the end when we've had already so much discussion back and forth.

01:46:20.400 --> 01:46:26.120
 I think we could have been super productive, even more so, at the very beginning of this

01:46:26.120 --> 01:46:29.720
 type of plan.

01:46:29.720 --> 01:46:30.800
 So I'll just say that.

01:46:30.800 --> 01:46:35.680
 But thrilled to be here and, yes, wonderful to be sitting on the dais with you once again.

01:46:35.680 --> 01:46:36.680
 Oh, me too.

01:46:36.680 --> 01:46:37.680
 Thank you.

01:46:37.680 --> 01:46:38.680
 Yeah.

01:46:38.680 --> 01:46:39.680
 Thank you.

01:46:39.680 --> 01:46:40.680
 Okay.

01:46:40.680 --> 01:46:41.680
 Councilman Betts?

01:46:41.680 --> 01:46:45.320
 Yeah, just because Commissioner Ellis brought that up, if in future planning sessions with

01:46:45.320 --> 01:46:52.880
 the future council, if we could do that, that's just a beautiful comment because a lot of these

01:46:52.880 --> 01:46:57.840
 concerns we had were early on and could have been addressed and not how did this go back

01:46:57.840 --> 01:46:58.840
 and forth.

01:46:58.840 --> 01:47:02.240
 And then I think that really would have been helpful to have a beginning middle and then

01:47:02.240 --> 01:47:03.240
 a finalizer.

01:47:03.240 --> 01:47:04.760
 And I love that.

01:47:04.760 --> 01:47:05.760
 Thank you, Commissioner Ellis.

01:47:05.760 --> 01:47:06.760
 It was a great comment.

01:47:06.760 --> 01:47:08.840
 Well, I'm glad you all are finding this to be receptive.

01:47:08.840 --> 01:47:13.560
 I've utilized this strategy, if you will, or opportunity to get the groups together on

01:47:13.560 --> 01:47:17.000
 some other projects and it typically proved very beneficial in those.

01:47:17.000 --> 01:47:21.520
 So I appreciate you all being receptive to the opportunity to have this joint meeting

01:47:21.520 --> 01:47:26.440
 and where it really can be beneficial is especially if we don't have agreement on certain areas.

01:47:26.440 --> 01:47:29.120
 So I felt like our discussion day was very productive.

01:47:29.120 --> 01:47:33.240
 And so I appreciate you all entertaining this approach, especially as we're moving into

01:47:33.240 --> 01:47:35.160
 the final stretch on this project.

01:47:35.160 --> 01:47:39.040
 But your comments are duly noted and happy to bring you guys together more often on some

01:47:39.040 --> 01:47:40.280
 other projects in the future.

01:47:40.280 --> 01:47:41.280
 Got it.

01:47:41.280 --> 01:47:42.280
 Okay.

01:47:42.280 --> 01:47:45.760
 So I'll let you I think I'll let you close and then I'll close this.

01:47:45.760 --> 01:47:46.760
 That sounds good.

01:47:46.760 --> 01:47:50.260
 I will adjourn the commission at 1227 p.m.

01:47:50.260 --> 01:47:51.260
 Okay.

01:47:51.260 --> 01:47:56.520
 And I'll conclude the council work session at 1227 as well.

01:47:56.520 --> 01:47:58.560
 And we'll be back tomorrow.

01:47:58.560 --> 01:47:59.960
 Commissioner Ellis, feel free to come join us.

01:47:59.960 --> 01:48:00.960
 We start at three.

01:48:00.960 --> 01:48:01.960
 You can hang out.

01:48:01.960 --> 01:48:02.960
 All right.

01:48:02.960 --> 01:48:03.960
 Thank you all very much.

01:48:03.960 --> 01:48:04.960
 Thank you.

01:48:04.960 --> 01:48:05.960
 Thank you, Ed.