WEBVTT

00:00:00.000 --> 00:00:02.600
 >>

00:00:02.600 --> 00:00:05.100
 Good morning and welcome to this meeting

00:00:05.100 --> 00:00:07.280
 of the mobility committee of the city of

00:00:07.280 --> 00:00:08.380
 Denton.

00:00:08.380 --> 00:00:11.180
 We have a quorum so we'll go ahead and get

00:00:11.180 --> 00:00:12.420
 started.

00:00:12.420 --> 00:00:14.280
 Items for individual consideration A,

00:00:14.280 --> 00:00:16.080
 first is considering approval of the

00:00:16.080 --> 00:00:17.460
 minutes of December 15.

00:00:17.460 --> 00:00:19.660
 I'll entertain a motion.

00:00:19.660 --> 00:00:22.160
 Why don't you go ahead and speak

00:00:22.160 --> 00:00:23.760
 rather than make a decision.

00:00:23.760 --> 00:00:25.420
 >> I move approval.

00:00:25.420 --> 00:00:28.220
 >>

00:00:28.260 --> 00:00:30.200
 We have a second?

00:00:30.200 --> 00:00:32.240
 >> I second.

00:00:32.240 --> 00:00:33.900
 >> Motion and seconded.

00:00:33.900 --> 00:00:35.440
 All in favor say aye.

00:00:35.440 --> 00:00:36.800
 >> Aye.

00:00:36.800 --> 00:00:38.000
 >>

00:00:38.000 --> 00:00:39.040
 Okay.

00:00:39.040 --> 00:00:39.980
 Minutes are approved.

00:00:39.980 --> 00:00:41.780
 Thank you.

00:00:41.780 --> 00:00:44.580
 Item B, receive a report and hold a

00:00:44.580 --> 00:00:46.780
 discussion regarding the city of Denton

00:00:46.780 --> 00:00:47.520
 transportation/mobility project status

00:00:47.520 --> 00:00:48.280
 report.

00:00:48.280 --> 00:00:50.720
 Go ahead.

00:00:57.060 --> 00:00:59.120
 >> Mayor Perotem, sir, Mr.

00:00:59.120 --> 00:01:01.660
 Poulter is going to be removed via Zoom

00:01:01.660 --> 00:01:04.300
 this morning so Logan is going to run the

00:01:04.300 --> 00:01:05.400
 slides for him.

00:01:05.400 --> 00:01:06.240
 >>

00:01:06.240 --> 00:01:07.160
 Morning, John.

00:01:07.160 --> 00:01:08.060
 >>

00:01:08.060 --> 00:01:09.140
 Morning, everybody.

00:01:09.140 --> 00:01:10.360
 My apologies.

00:01:10.360 --> 00:01:12.100
 I was in transit.

00:01:12.100 --> 00:01:14.580
 So I pulled over to make sure I was

00:01:14.580 --> 00:01:15.400
 completely safe.

00:01:15.400 --> 00:01:16.700
 >>

00:01:16.700 --> 00:01:17.380
 Construction?

00:01:17.380 --> 00:01:18.640
 >>

00:01:18.640 --> 00:01:20.140
 No, I'm good.

00:01:20.140 --> 00:01:21.680
 I'm safe.

00:01:21.680 --> 00:01:24.220
 So the first project we're going to

00:01:24.220 --> 00:01:26.980
 talk about is the plan for the city of

00:01:27.020 --> 00:01:28.080
 Denton.

00:01:28.080 --> 00:01:30.860
 If you can make it smaller for everybody to

00:01:30.860 --> 00:01:33.420
 see everything, that would be good.

00:01:33.420 --> 00:01:34.960
 Right there is perfect.

00:01:34.960 --> 00:01:36.100
 >> Okay.

00:01:36.100 --> 00:01:37.200
 >>

00:01:37.200 --> 00:01:40.540
 So right now, if you will roll down to the

00:01:40.540 --> 00:01:43.040
 next page, it's the text art report.

00:01:43.040 --> 00:01:45.600
 This project is anticipated to be -- we

00:01:45.600 --> 00:01:48.140
 were talking originally November, but if you

00:01:48.140 --> 00:01:51.100
 roll down to the next page, we're thinking

00:01:51.100 --> 00:01:54.040
 that it's probably -- what we're hearing now is

00:01:54.040 --> 00:01:55.340
 October instead of November.

00:01:55.380 --> 00:01:57.820
 And it's just because they're moving on the

00:01:57.820 --> 00:01:59.860
 concrete and asphalt paving for the

00:01:59.860 --> 00:02:02.560
 northbound lanes at a faster pace than they

00:02:02.560 --> 00:02:03.460
 anticipated.

00:02:03.460 --> 00:02:05.420
 So they're reporting internally to the

00:02:05.420 --> 00:02:08.320
 county that they think it will be October when

00:02:08.320 --> 00:02:10.260
 this project is substantially complete.

00:02:10.260 --> 00:02:11.660
 Next project.

00:02:11.660 --> 00:02:13.940
 So the 35E mayo project, the 35E

00:02:13.940 --> 00:02:16.860
 layout, we're going to talk about that in a

00:02:16.860 --> 00:02:18.400
 little bit more detail.

00:02:18.400 --> 00:02:21.000
 So we're going to talk about that in a

00:02:21.000 --> 00:02:22.580
 little bit more detail.

00:02:22.600 --> 00:02:25.740
 So the 35E mayo project, the --

00:02:25.740 --> 00:02:28.040
 >> Excuse me, John, I just want to encourage

00:02:28.040 --> 00:02:29.820
 councilmembers, since it's just frankly

00:02:29.820 --> 00:02:32.520
 difficult for me to tell what you're doing up

00:02:32.520 --> 00:02:35.360
 there, I'd say if you have a question, just go

00:02:35.360 --> 00:02:36.720
 ahead and speak up.

00:02:36.720 --> 00:02:38.760
 It can be a little more informal.

00:02:38.760 --> 00:02:41.200
 And I think on the recording, our voices

00:02:41.200 --> 00:02:43.760
 are distinct enough from each other that we'll

00:02:43.760 --> 00:02:44.960
 be able to follow.

00:02:44.960 --> 00:02:45.760
 Thanks.

00:02:45.760 --> 00:02:46.960
 Go ahead.

00:02:46.960 --> 00:02:50.300
 >> Okay, so the mayo project on 35, we're in

00:02:50.340 --> 00:02:53.100
 September of '23, and we are anticipating those

00:02:53.100 --> 00:02:56.200
 utilities to be completed by September of '23.

00:02:56.200 --> 00:02:58.680
 And as you scroll down, you'll see all the

00:02:58.680 --> 00:03:00.440
 utilities that we're working on.

00:03:00.440 --> 00:03:03.680
 And everybody seems to be confident that they'll

00:03:03.680 --> 00:03:05.480
 make that timeframe.

00:03:05.480 --> 00:03:09.760
 And again, as we get closer to that September

00:03:09.760 --> 00:03:13.720
 timeframe, we will be able to do a modification

00:03:13.720 --> 00:03:16.720
 and a 10-year plan to move the dollars from the

00:03:16.720 --> 00:03:20.240
 out year to the September '23 timeframe.

00:03:20.260 --> 00:03:24.240
 And this, again, does all of the work from Mayhill

00:03:24.240 --> 00:03:26.700
 through the brinker overpass and all the way to

00:03:26.700 --> 00:03:30.000
 the loop, loop 288, the frontage roads.

00:03:30.000 --> 00:03:31.940
 So it'll be permanent improvements on the

00:03:31.940 --> 00:03:33.280
 frontage roads.

00:03:33.280 --> 00:03:35.340
 So in the future, when we come back to do the

00:03:35.340 --> 00:03:38.680
 ultimate someday, it won't impact the frontage

00:03:38.680 --> 00:03:42.680
 roads at all.

00:03:42.680 --> 00:03:45.160
 Next slide with more questions.

00:03:45.160 --> 00:03:48.600
 The merge, we will have the right of way

00:03:48.620 --> 00:03:50.760
 completed this month.

00:03:50.760 --> 00:03:52.560
 There was one parcel left we had to get some

00:03:52.560 --> 00:03:55.560
 paperwork worked out on.

00:03:55.560 --> 00:03:59.580
 We've had our aesthetics meeting with TechStat

00:03:59.580 --> 00:04:02.580
 and the city related to getting those aesthetics

00:04:02.580 --> 00:04:06.380
 included in the plan set as they design the project.

00:04:06.380 --> 00:04:10.480
 So we're ahead of the curve on this section of '35.

00:04:10.480 --> 00:04:13.520
 And again, we've got August ready to let it to '23,

00:04:13.520 --> 00:04:17.320
 and the money is in that fiscal year of September '23.

00:04:17.360 --> 00:04:20.720
 So we're right on the number right there.

00:04:20.720 --> 00:04:23.600
 That's a $400 million project.

00:04:23.600 --> 00:04:25.960
 Next slide, unless there's questions.

00:04:25.960 --> 00:04:28.340
 And the utilities are the critical path item here,

00:04:28.340 --> 00:04:35.580
 but everybody's working together on it.

00:04:35.580 --> 00:04:40.020
 Okay, the interim job, it's essentially open to traffic.

00:04:40.020 --> 00:04:42.720
 If you'll scroll down to the TechStat report,

00:04:42.720 --> 00:04:44.880
 the reason we still have it as an active account is

00:04:44.920 --> 00:04:47.360
 they're still having to do some work at the 380

00:04:47.360 --> 00:04:50.980
 intersection to do some median striping and get

00:04:50.980 --> 00:04:52.720
 the signal conduit set up.

00:04:52.720 --> 00:04:59.760
 So once that striping and that signal adjustments are done,

00:04:59.760 --> 00:05:03.340
 TechStat will close this project out and we can put a

00:05:03.340 --> 00:05:06.100
 big green completed on it and move on to the next.

00:05:06.100 --> 00:05:09.680
 And I've driven it, a lot of people have drove it.

00:05:09.680 --> 00:05:12.380
 I feel like it is a safer section now.

00:05:12.400 --> 00:05:15.640
 And I think it was a plan that, I think Becky came up with it.

00:05:15.640 --> 00:05:19.380
 But good job all the way around for everybody.

00:05:19.380 --> 00:05:21.860
 >> If you hadn't said that, I was going to say it myself.

00:05:21.860 --> 00:05:25.420
 I also have the question, do we know, my experience also,

00:05:25.420 --> 00:05:28.620
 it doesn't seem to be backing up there now.

00:05:28.620 --> 00:05:31.620
 But do we know like objectively?

00:05:31.620 --> 00:05:37.040
 Now we have two people saying, it looks like it's working.

00:05:37.060 --> 00:05:42.340
 If we got any kind of other way to assess?

00:05:42.340 --> 00:05:46.880
 >> Yes sir, so if you drive like going northbound,

00:05:46.880 --> 00:05:49.840
 as you come around the merge into that situation,

00:05:49.840 --> 00:05:52.280
 you'll see that they put up a sign.

00:05:52.280 --> 00:05:56.960
 That's a yellow sign that says, congestion when flashing.

00:05:56.960 --> 00:06:02.020
 And I've checked with Travis and TechStat like two days ago.

00:06:02.020 --> 00:06:06.360
 And I've asked them, has that been triggered since the project

00:06:06.400 --> 00:06:08.160
 was opened and they said, no.

00:06:08.160 --> 00:06:13.200
 So it watches for congestion that was occurring before

00:06:13.200 --> 00:06:17.940
 and they warn you and it hasn't been needed to activate

00:06:17.940 --> 00:06:19.400
 since they opened the traffic.

00:06:19.400 --> 00:06:25.120
 >> Wow, that's a great answer, thank you.

00:06:25.120 --> 00:06:27.320
 >> Okay, I think I'm good on that one.

00:06:27.320 --> 00:06:29.420
 All right, so 35 North.

00:06:29.420 --> 00:06:34.260
 Again, we're in the right of acquisition process.

00:06:34.260 --> 00:06:35.620
 We're almost done with that.

00:06:35.660 --> 00:06:38.420
 It should be done by March of this year.

00:06:38.420 --> 00:06:42.760
 We roll into the utility relocations.

00:06:42.760 --> 00:06:46.000
 If you scroll down, you'll note that there are significant

00:06:46.000 --> 00:06:49.540
 utilities in this corridor as well that need to be worked on.

00:06:49.540 --> 00:06:55.280
 And we're looking at being ready to go by December of '23

00:06:55.280 --> 00:06:57.240
 from ready to let.

00:06:57.240 --> 00:07:01.380
 And this is a $800 million job.

00:07:01.420 --> 00:07:06.880
 So when it's ready to let, you may move one of the sections at

00:07:06.880 --> 00:07:09.720
 a time because there's three sections here and they want to

00:07:09.720 --> 00:07:12.320
 let them separately because if they go above a certain dollar

00:07:12.320 --> 00:07:17.240
 amount, they have to do a design build and they don't want to do

00:07:17.240 --> 00:07:18.640
 a design build.

00:07:18.640 --> 00:07:20.540
 But we're moving on this project.

00:07:20.540 --> 00:07:24.680
 It's on track.

00:07:24.680 --> 00:07:27.280
 And let me know if y'all can't hear me now.

00:07:27.280 --> 00:07:30.320
 I'll get closer but it will make my head look like a pumpkin.

00:07:30.340 --> 00:07:32.740
 You're audible to me.

00:07:32.740 --> 00:07:34.480
 Anyone else?

00:07:34.480 --> 00:07:35.920
 Any difficulties?

00:07:35.920 --> 00:07:38.320
 >> Yeah, John, we were having a little trouble hearing you from

00:07:38.320 --> 00:07:40.860
 time to time so if you could just speak into the mic as much

00:07:40.860 --> 00:07:42.300
 as you can, that would be great.

00:07:42.300 --> 00:07:44.660
 >> I don't even know where the mic is on my computer.

00:07:44.660 --> 00:07:47.560
 So I'll just face forward.

00:07:47.560 --> 00:07:50.240
 >> It's usually at the top of the screen.

00:07:50.240 --> 00:07:52.200
 >> Okay.

00:07:52.200 --> 00:07:55.480
 On the 3520 Frontage Roads, if you'll scroll down,

00:07:55.480 --> 00:07:57.580
 I think this is the one where we're having a little bit of

00:07:57.600 --> 00:08:02.040
 trouble with maybe, yeah.

00:08:02.040 --> 00:08:11.620
 So we were trying to finalize the contract with HNTB but since

00:08:11.620 --> 00:08:13.720
 we submitted this report to y'all,

00:08:13.720 --> 00:08:17.200
 TechStock notified us today or yesterday that they've

00:08:17.200 --> 00:08:19.860
 terminated the negotiations with HNTB because they couldn't get

00:08:19.860 --> 00:08:26.640
 to a number that both sides like so they are starting new

00:08:26.680 --> 00:08:31.400
 negotiations with a new firm and I'll send out the electric,

00:08:31.400 --> 00:08:34.940
 electronic version of this before y'all post it up on the

00:08:34.940 --> 00:08:37.540
 website to make sure it's the most current information but

00:08:37.540 --> 00:08:42.020
 they've terminated negotiations with HNTB so it'll be a little

00:08:42.020 --> 00:08:45.760
 bit of time before we get somebody to do the design work

00:08:45.760 --> 00:08:49.400
 on this project.

00:08:49.400 --> 00:08:51.220
 And that's pretty much it on that.

00:08:51.260 --> 00:08:57.300
 Next, we're going to move to questions.

00:08:57.300 --> 00:09:06.840
 All right, this is the US 380 section under construction.

00:09:06.840 --> 00:09:08.840
 Essentially, if you roll to the next report,

00:09:08.840 --> 00:09:10.880
 I mean to the next page.

00:09:19.860 --> 00:09:27.900
 They're fixing to switch over to the Phase 2 on this project

00:09:27.900 --> 00:09:32.300
 because they're getting faster on the improvements on Phase 1

00:09:32.300 --> 00:09:35.700
 than they were anticipating so they're moving into Phase 2

00:09:35.700 --> 00:09:39.240
 quicker than they anticipated and so for the entire length of

00:09:39.240 --> 00:09:43.880
 the project, they'll be working on the westbound side as well

00:09:43.920 --> 00:09:52.660
 as the eastbound and the same on this project with the next

00:09:52.660 --> 00:09:55.960
 contractor, the barricades are set.

00:09:55.960 --> 00:09:58.960
 If you roll to the text that report on the next page.

00:09:58.960 --> 00:10:06.940
 >> This one?

00:10:06.940 --> 00:10:12.080
 >> I think you went past it.

00:10:12.100 --> 00:10:14.340
 I think there's a page before that.

00:10:14.340 --> 00:10:15.720
 Yes, right here.

00:10:15.720 --> 00:10:21.020
 Oh, okay, yeah, so on mine we've got a construction report

00:10:21.020 --> 00:10:27.820
 now for 380, no, no, I apologize, it's the next page.

00:10:27.820 --> 00:10:32.100
 So on 380 east, the contractor is going to be working both in

00:10:32.100 --> 00:10:41.100
 Phase 1 and Phase 2, but the Phase 2 is the 10-foot sidewalk

00:10:41.140 --> 00:10:44.580
 and the temporary construction both on eastbound and westbound.

00:10:44.580 --> 00:10:47.740
 So they'll be working on both directions of the road,

00:10:47.740 --> 00:10:51.120
 but they're primarily doing the eastbound roadway improvements

00:10:51.120 --> 00:10:54.420
 and the westbound will be the pedestrian improvements.

00:10:54.420 --> 00:11:04.220
 So on the feasibility, we are waiting for crossroads and

00:11:04.220 --> 00:11:09.440
 little land to respond to text that essentially they in the

00:11:09.460 --> 00:11:14.700
 public hearing for the feasibility, they requested that

00:11:14.700 --> 00:11:18.400
 an economic impact study be done to the impact to those

00:11:18.400 --> 00:11:22.340
 communities for a loss of development along the corridor

00:11:22.340 --> 00:11:25.140
 that is being proposed.

00:11:25.140 --> 00:11:29.660
 But Denton County has met with both Little Elm and Crossroads

00:11:29.660 --> 00:11:34.160
 and told them that they would cooperate with those two

00:11:34.160 --> 00:11:38.960
 communities to find a new corridor for their economic

00:11:39.000 --> 00:11:43.640
 impact study, and so they need to communicate that to TxDOT

00:11:43.640 --> 00:11:46.440
 because we're conceding the point, the county is conceding

00:11:46.440 --> 00:11:48.940
 the point that it is an impact, so we don't need to do a study

00:11:48.940 --> 00:11:51.300
 to determine if there's an impact.

00:11:51.300 --> 00:11:54.680
 And so once they turn those statements in, TxDOT will close

00:11:54.680 --> 00:11:59.880
 out the feasibility study and we'll move into the environmental

00:11:59.880 --> 00:12:03.480
 phase of the blue section.

00:12:03.520 --> 00:12:11.600
 And just recently last Tuesday, Denton County hired Chico Cope

00:12:11.600 --> 00:12:15.700
 to begin the environmental clearance for the brown section

00:12:15.700 --> 00:12:21.740
 to add frontage roads to that section of 288.

00:12:21.740 --> 00:12:27.040
 Unless there's questions, that's all I got.

00:12:27.040 --> 00:12:31.820
 Okay, 288 West, this is the section further out.

00:12:31.840 --> 00:12:36.480
 Our design concept conference on February 11th, basically setting

00:12:36.480 --> 00:12:41.100
 up the parameters that which we will design the project by.

00:12:41.100 --> 00:12:44.620
 Took a while to get it set up, but Chico Cope got their

00:12:44.620 --> 00:12:48.640
 marching orders, and like I tell Becky from time to time

00:12:48.640 --> 00:12:52.260
 when we talk, the county's driving the boat on this,

00:12:52.260 --> 00:12:56.540
 but the number one stakeholder out there obviously is the city

00:12:56.540 --> 00:12:59.240
 because all of it's city and you've got a lot going on there,

00:12:59.280 --> 00:13:04.320
 so anything we do, we make sure that Becky, from the county

00:13:04.320 --> 00:13:06.480
 standpoint, that Becky and the city are included

00:13:06.480 --> 00:13:10.580
 in those conversations.

00:13:10.580 --> 00:13:18.800
 Next, okay, 1515, we had our kickoff for this one on February

00:13:18.800 --> 00:13:25.400
 15th, and basically we began preliminary design work for the

00:13:25.400 --> 00:13:27.940
 bridge layout, that's going to be the critical path item there

00:13:27.960 --> 00:13:32.300
 by Bonnie Bray and 35W, and essentially we went ahead and

00:13:32.300 --> 00:13:38.420
 started doing the design work in advance of our environmental

00:13:38.420 --> 00:13:41.720
 clearance because we're fairly confident that the technical

00:13:41.720 --> 00:13:44.520
 reports will be accepted and no major changes,

00:13:44.520 --> 00:13:48.320
 so we're trying to buy some time on this project by speeding up

00:13:48.320 --> 00:13:51.460
 the design before we get the re-eval done,

00:13:51.460 --> 00:13:55.260
 so I think we're good on this one.

00:13:55.260 --> 00:13:57.740
 Yeah, I think we're good.

00:13:57.760 --> 00:14:04.540
 We hired half-associates for this project at last Tuesday's

00:14:04.540 --> 00:14:08.720
 court, and we're working with them to get a scope and fee,

00:14:08.720 --> 00:14:11.780
 and as soon as we get them on contract, again,

00:14:11.780 --> 00:14:16.960
 this is primarily a city of Denton and Crum stakeholders,

00:14:16.960 --> 00:14:21.500
 and so we'll include, the county will include both entities in

00:14:21.500 --> 00:14:23.820
 the kickoff meetings to make sure that what we're doing is

00:14:23.820 --> 00:14:27.660
 what everybody wants us to do.

00:14:27.700 --> 00:14:30.660
 Next.

00:14:30.660 --> 00:14:34.500
 All right, so this one, unless you got questions,

00:14:34.500 --> 00:14:37.440
 you know, Becky, I think, is working with Travis,

00:14:37.440 --> 00:14:39.840
 and we've got some calculations done,

00:14:39.840 --> 00:14:43.320
 and we're just working through the best path forward on that,

00:14:43.320 --> 00:14:50.620
 and I don't know if Becky wants to add anything to that or not.

00:14:50.620 --> 00:14:52.620
 John, I believe you covered it.

00:14:52.660 --> 00:14:58.560
 City staff has met in the field with TxDOT to review the

00:14:58.560 --> 00:15:00.600
 construction that needs to happen on the roadway.

00:15:00.600 --> 00:15:03.000
 We're working through that collaboration.

00:15:03.000 --> 00:15:07.000
 Daniel Kramer is leading that charge from our Deputy Director

00:15:07.000 --> 00:15:09.280
 of Operations for Streets, Drainage, and Traffic,

00:15:09.280 --> 00:15:12.340
 so we're coordinating, really working through that process,

00:15:12.340 --> 00:15:16.380
 so we hope to have that resolved in the next few weeks,

00:15:16.380 --> 00:15:20.480
 but for sure, the on-the-ground visit has already taken place

00:15:20.520 --> 00:15:24.360
 based on the cores that were collected for that area.

00:15:24.360 --> 00:15:34.840
 Sorry, so what's the completion timing?

00:15:34.840 --> 00:15:37.540
 There's currently not a completion schedule.

00:15:37.540 --> 00:15:41.500
 What the process happened was TxDOT had to go out

00:15:41.500 --> 00:15:44.740
 and complete cores along this area and actually do pavement

00:15:44.740 --> 00:15:50.080
 cores to find out, you know, what was the actual surface

00:15:50.120 --> 00:15:55.180
 below the asphalt top, so they've done that.

00:15:55.180 --> 00:15:58.560
 They have presented that information to city staff,

00:15:58.560 --> 00:16:02.260
 and a walk-through was held week before last,

00:16:02.260 --> 00:16:04.260
 really to walk through that area,

00:16:04.260 --> 00:16:06.640
 look at the pavement markings on the ground.

00:16:06.640 --> 00:16:10.000
 Now city staff is evaluating that to make sure that we're

00:16:10.000 --> 00:16:13.580
 in alignment with the proposed construction that TxDOT is

00:16:13.580 --> 00:16:18.420
 proposing, being that it's not exactly a complete rebuild.

00:16:18.440 --> 00:16:23.020
 It's a different process that they're working through.

00:16:23.020 --> 00:16:26.460
 Once the agreement has been made between TxDOT and the city,

00:16:26.460 --> 00:16:31.460
 then TxDOT will move forward with the design of those plans

00:16:31.460 --> 00:16:34.860
 and then work through that construction timeframe.

00:16:34.860 --> 00:16:37.140
 So until those decisions are made,

00:16:37.140 --> 00:16:40.800
 city staff has not had that opportunity to set the timeframe.

00:16:40.800 --> 00:16:43.640
 It's going to be based on TxDOT's schedule.

00:16:43.680 --> 00:16:49.940
 Just to add to that a little bit, the path we're taking is a

00:16:49.940 --> 00:16:53.740
 maintenance path because Travis is going to be able to get out

00:16:53.740 --> 00:16:58.880
 there sooner and with the lesser degree of design work and if he

00:16:58.880 --> 00:17:02.020
 goes through his maintenance, and TxDOT has agreed to use

00:17:02.020 --> 00:17:04.320
 maintenance dollars to get this done.

00:17:04.320 --> 00:17:09.400
 So we were talking, you know, 18 months or so to get it to where

00:17:09.400 --> 00:17:10.400
 we can go to construction.

00:17:10.440 --> 00:17:14.140
 We're talking about several months now instead of,

00:17:14.140 --> 00:17:16.900
 you know, a year and a half.

00:17:16.900 --> 00:17:20.280
 >> To go, to get to the start of construction.

00:17:20.280 --> 00:17:23.820
 >> Correct, because the one thing that's happened since we

00:17:23.820 --> 00:17:30.120
 started this opportunity is that TxDOT's kind of shut the door

00:17:30.120 --> 00:17:34.320
 on any kind of turn back programs that reduce capacity.

00:17:34.320 --> 00:17:38.900
 We're not reducing capacity, but TxDOT knows that they have,

00:17:38.920 --> 00:17:40.800
 they're going to have to make these improvements whether or

00:17:40.800 --> 00:17:44.100
 not the city then takes these projects off system.

00:17:44.100 --> 00:17:48.300
 So they're less worried about the agreement between the city

00:17:48.300 --> 00:17:52.000
 and the state now and they just know they've got to get the

00:17:52.000 --> 00:17:53.880
 project done quick.

00:17:53.880 --> 00:17:56.580
 >> And Mayor Perot, just for context, we're only talking

00:17:56.580 --> 00:18:00.580
 about the portion that is south of Hickory where the recent

00:18:00.580 --> 00:18:04.520
 pack four phases one and two project was completed with the

00:18:04.560 --> 00:18:09.520
 water sewer and drainage in that area that's the specific area

00:18:09.520 --> 00:18:12.760
 that I'm referring to with the comments I just made.

00:18:12.760 --> 00:18:15.100
 >> Yeah, I appreciate that.

00:18:15.100 --> 00:18:17.760
 You know, and I totally hear that we don't have timing

00:18:17.760 --> 00:18:22.400
 because we haven't gotten to an agreement, you know, on exactly

00:18:22.400 --> 00:18:25.680
 the plan objectives and so on.

00:18:25.680 --> 00:18:28.540
 But can you know, can you just help us because we have to

00:18:28.540 --> 00:18:30.920
 respond to constituents?

00:18:30.940 --> 00:18:36.220
 Is it likely to be multiple years?

00:18:36.220 --> 00:18:39.220
 >> No, sir, I think that, I think with this type of work and

00:18:39.220 --> 00:18:42.900
 the fact that TxDOT is going to use their maintenance to do it,

00:18:42.900 --> 00:18:46.220
 that we could probably, because they're going to know what,

00:18:46.220 --> 00:18:49.060
 we're going to know what they think they want to do and we're

00:18:49.060 --> 00:18:52.840
 going to press them to do, you know, 30, 40% more than that

00:18:52.840 --> 00:18:55.040
 anyway, just our contingency.

00:18:55.040 --> 00:18:59.200
 And then we think by spring we can have these guys rolling

00:18:59.240 --> 00:19:05.620
 because the design for a rehab is far less difficult than the

00:19:05.620 --> 00:19:07.180
 design for a reconstruction.

00:19:07.180 --> 00:19:10.660
 >> Yeah, no, I get that as far as when to get started.

00:19:10.660 --> 00:19:15.020
 And then is that, from that point on, what's the sort of,

00:19:15.020 --> 00:19:17.720
 I'm sorry to, you know, be a bit of a problem.

00:19:17.720 --> 00:19:22.540
 What's the sort of range of plausible outcomes for,

00:19:22.540 --> 00:19:25.240
 you know, the end date?

00:19:25.240 --> 00:19:27.560
 >> This type of work would be like months, I think.

00:19:27.600 --> 00:19:33.480
 Not like a year, I think it would be done in a paving season.

00:19:33.480 --> 00:19:35.880
 >> Okay, that's helpful to understand, thank you.

00:19:35.880 --> 00:19:40.080
 >> And Mayor Pritz, we are going to be continuing to work with

00:19:40.080 --> 00:19:44.280
 TxDOT to make sure that we're all in alignment.

00:19:44.280 --> 00:19:47.620
 So part of the walkthrough process was to evaluate the

00:19:47.620 --> 00:19:52.420
 areas of which TxDOT anticipated needed to be repaired versus

00:19:52.420 --> 00:19:56.260
 the areas of which the city believed there were opportunities

00:19:56.300 --> 00:19:58.260
 to also make repairs on.

00:19:58.260 --> 00:20:00.600
 So that's a collaboration, making sure everyone's in

00:20:00.600 --> 00:20:03.700
 alignment and we're in agreement with the construction

00:20:03.700 --> 00:20:08.940
 that needs to happen, not only EGLE itself, but also Elm and

00:20:08.940 --> 00:20:12.520
 Locust, like I mentioned, to just south of Hickory.

00:20:12.520 --> 00:20:15.480
 And those agreements, once those are in alignment,

00:20:15.480 --> 00:20:19.320
 then we'll work forward with making sure that they have that

00:20:19.320 --> 00:20:22.760
 plan to actually execute that through their maintenance

00:20:22.760 --> 00:20:24.520
 program like John is referring to.

00:20:24.560 --> 00:20:28.500
 So we're still in the phase of making sure that we're all in

00:20:28.500 --> 00:20:32.160
 alignment based on the data that's been collected because

00:20:32.160 --> 00:20:35.300
 obviously, you know, there may be things that TxDOT didn't

00:20:35.300 --> 00:20:37.900
 necessarily think needed to be repaired, but the city does

00:20:37.900 --> 00:20:40.540
 think needs to be repaired, or vice versa.

00:20:40.540 --> 00:20:47.280
 So it's not a whole, you know, from beginning to end that every

00:20:47.280 --> 00:20:51.120
 single portion of those roadways are in agreement that need to be

00:20:51.160 --> 00:20:54.820
 completely repaired when I say that I mean completely rebuild.

00:20:54.820 --> 00:20:57.000
 So we're walking through that process with them.

00:20:57.000 --> 00:21:00.860
 >> Yeah, I understand.

00:21:00.860 --> 00:21:03.000
 You know, you get the gist of where I'm coming from, but it's

00:21:03.000 --> 00:21:07.640
 just really hard answering the people operating those

00:21:07.640 --> 00:21:10.700
 businesses along there.

00:21:10.700 --> 00:21:13.880
 Anybody else?

00:21:13.880 --> 00:21:18.420
 Okay.

00:21:18.420 --> 00:21:20.380
 >> I think the next- >> Councilmember Byrd, I believe,

00:21:20.420 --> 00:21:27.880
 is going to speak.

00:21:27.880 --> 00:21:32.920
 >> Okay, I have it, I have it.

00:21:32.920 --> 00:21:38.660
 I need for you all to go back to the slide that talks about the

00:21:38.660 --> 00:21:43.900
 380 corridor and the work being done up and around where the

00:21:43.940 --> 00:21:54.180
 frontage road is, where the 288 going north, and I do understand

00:21:54.180 --> 00:22:04.900
 that the work is proceeding on 380 and moving west, and I don't

00:22:04.900 --> 00:22:09.640
 understand, I don't have in my mindset about how long will that

00:22:09.660 --> 00:22:14.640
 particular portion take, is that the lit date that we see?

00:22:14.640 --> 00:22:16.980
 >> Are you talking about the blue section across the lake that

00:22:16.980 --> 00:22:18.840
 has ended the loop?

00:22:18.840 --> 00:22:25.640
 >> The 380 project and going up to 288 and looping around.

00:22:25.640 --> 00:22:28.080
 >> So you're talking about the feasibility, that slide right

00:22:28.080 --> 00:22:29.580
 there, yes.

00:22:29.580 --> 00:22:35.420
 >> That's it, yeah, 380 feasibility study, and I don't

00:22:35.460 --> 00:22:40.560
 see any dates or anything on there, but I am wanting to just

00:22:40.560 --> 00:22:47.140
 kind of get a ball figure idea of when will it finish up at the

00:22:47.140 --> 00:22:52.380
 288, 380 section, I mean, how long is this going to take?

00:22:52.380 --> 00:22:57.740
 >> Okay, so I think there is a project that's under construction

00:22:57.740 --> 00:23:03.380
 right now, if you'll move up the report to the, move up to the

00:23:03.420 --> 00:23:08.760
 2, 380s that are under construction, go for one more,

00:23:08.760 --> 00:23:11.800
 keep one more, yeah, so this right here ties in, this right

00:23:11.800 --> 00:23:15.700
 there ties into the loop with the interim improvements, and it

00:23:15.700 --> 00:23:19.400
 has a December 23 completion date, so all the work that we're

00:23:19.400 --> 00:23:24.940
 doing to add six lanes to 380 from the loop to 377, that work

00:23:24.940 --> 00:23:28.380
 will be done December of next year.

00:23:28.380 --> 00:23:31.520
 Now if you're talking about the eastern section, if you'll

00:23:31.540 --> 00:23:34.140
 scroll down, we have a completion date on that as

00:23:34.140 --> 00:23:38.520
 well, because we have the let date, so we're talking about

00:23:38.520 --> 00:23:43.960
 January 22, they said it would be 36 months, so you're talking

00:23:43.960 --> 00:23:51.740
 about January 25, 22, 23, 24, 25 for it to be complete, and

00:23:51.740 --> 00:23:55.540
 that's adding the six lanes and the raised median and all the

00:23:55.560 --> 00:24:01.540
 interchanges at Nabotel, Legacy, 423, and 720.

00:24:01.540 --> 00:24:11.580
 >> Okay, okay, and then on that 288 portion of that project--

00:24:11.580 --> 00:24:15.160
 >> Okay, the one that goes around the, that we just hired--

00:24:15.160 --> 00:24:18.320
 >> Yeah, the loop, yeah, the north loop, yeah.

00:24:18.320 --> 00:24:22.020
 >> Yeah, so if you'll go to the feasibility page--

00:24:22.020 --> 00:24:23.620
 >> Right there, that's it.

00:24:23.660 --> 00:24:26.760
 >> Okay, so Denton County hired Pacheco Cope to do the

00:24:26.760 --> 00:24:31.540
 environmental study to put frontage roads and turn that part

00:24:31.540 --> 00:24:36.180
 of the loop into a freeway so that the businesses can attach

00:24:36.180 --> 00:24:39.380
 to the frontage road and not directly to the main lanes, and

00:24:39.380 --> 00:24:44.720
 we will have those people on contract in the next 30 days,

00:24:44.720 --> 00:24:48.760
 and we are making, obviously, y'all are, from the county

00:24:48.760 --> 00:24:52.160
 standpoint, that's where a lot of pressure from the city is

00:24:52.180 --> 00:24:56.460
 getting, and so we'll make sure that we have PK very closely

00:24:56.460 --> 00:24:59.700
 aligned with Becky and your development services as we move

00:24:59.700 --> 00:25:02.000
 forward.

00:25:02.000 --> 00:25:05.640
 >> Are frontage roads built first before the main part of

00:25:05.640 --> 00:25:07.140
 the highway?

00:25:07.140 --> 00:25:09.800
 >> So right now you've got the main lanes out there on this

00:25:09.800 --> 00:25:12.900
 section of Loop 288.

00:25:12.900 --> 00:25:15.420
 There's places in the other parts of the county and other

00:25:15.420 --> 00:25:20.280
 parts of the region where frontage roads are first and then

00:25:20.320 --> 00:25:24.620
 the main lanes come in, like on the Dallas North Toll Road, or

00:25:24.620 --> 00:25:28.260
 it's like 35W where it's got main lanes and no frontage roads

00:25:28.260 --> 00:25:30.800
 or we're coming back putting frontage roads on them or the

00:25:30.800 --> 00:25:36.340
 loop, so it just depends on what people did back in the day.

00:25:36.340 --> 00:25:39.740
 We're just trying to fix what's not there, which in this case

00:25:39.740 --> 00:25:41.340
 is the frontage roads.

00:25:41.340 --> 00:25:43.600
 >> Okay, thank you so much, I appreciate that.

00:25:43.600 --> 00:25:47.580
 That gives me a better perspective of some

00:25:47.600 --> 00:25:50.720
 conversations that are being had with some developers and you

00:25:50.720 --> 00:25:53.240
 know, and just the growth more towards that way.

00:25:53.240 --> 00:25:57.480
 I have a question here that a constituent asked.

00:25:57.480 --> 00:25:59.080
 Is it okay if I ask this question?

00:25:59.080 --> 00:26:02.000
 I don't know where it belongs in the conversation, but while I

00:26:02.000 --> 00:26:03.460
 have the floor.

00:26:03.460 --> 00:26:10.660
 She said, "I did have a question for Raymond, though," you know,

00:26:10.660 --> 00:26:12.700
 I'm a teacher, I've got to throw my little commas and

00:26:12.700 --> 00:26:15.200
 everything in there, I'm sorry.

00:26:15.240 --> 00:26:19.780
 I did have a question for Raymond, though, if it could be

00:26:19.780 --> 00:26:24.120
 asked, and the question is, "Due to a portion of Bonnie Bray

00:26:24.120 --> 00:26:30.020
 being closed and number seven, I guess it's the bus route, is

00:26:30.020 --> 00:26:35.160
 rerouted, are the bus stops from Panhandle to University and

00:26:35.160 --> 00:26:38.600
 University going towards 35 being bypassed again, like they

00:26:38.600 --> 00:26:42.700
 were a few years ago," so this sounds like this is apparently a

00:26:42.720 --> 00:26:47.260
 DCTA question or city question.

00:26:47.260 --> 00:26:49.800
 I didn't know where to put that in the grand scheme of things

00:26:49.800 --> 00:26:51.040
 here.

00:26:51.040 --> 00:26:55.180
 >> Sure, Councilmember Bird, we will take that question and work

00:26:55.180 --> 00:26:59.540
 with Raymond to find out the exact locations that this

00:26:59.540 --> 00:27:04.380
 constituent is referring to and get that question clarified, so

00:27:04.380 --> 00:27:05.620
 that's not a problem.

00:27:05.620 --> 00:27:07.460
 >> Okay, thank you very much.

00:27:07.460 --> 00:27:08.480
 All right, my time is done.

00:27:08.520 --> 00:27:13.500
 That's one from McGuire, anything else?

00:27:13.500 --> 00:27:15.720
 You're ready to keep going?

00:27:15.720 --> 00:27:20.940
 >> I'd like to jump in, Logan, you read my mind with this slide

00:27:20.940 --> 00:27:24.440
 there, just to talk a little bit about Phase 2 on Elm and Locust

00:27:24.440 --> 00:27:27.480
 and just make you all aware of the conversations we're having.

00:27:27.480 --> 00:27:30.780
 We know there's a lot of complicated issues going on

00:27:30.780 --> 00:27:33.520
 here, obviously we have the water/wastewater project that

00:27:33.520 --> 00:27:35.940
 we're all hearing about, that part has been delayed for a

00:27:35.980 --> 00:27:38.420
 number of years, we have the funding, we're ready to roll,

00:27:38.420 --> 00:27:41.920
 we're just waiting on drainage issues and the road

00:27:41.920 --> 00:27:43.160
 construction there.

00:27:43.160 --> 00:27:46.060
 The drainage issues are significant, so we had a

00:27:46.060 --> 00:27:48.660
 conversation with John just on Friday about how can we work

00:27:48.660 --> 00:27:51.900
 with TechStock to look at funding for the drainage, where

00:27:51.900 --> 00:27:54.340
 are we going to find other funding for drainage, because the

00:27:54.340 --> 00:27:58.300
 drainage is kind of the linchpin to do a lot of the roadway and

00:27:58.300 --> 00:28:00.780
 the water/wastewater project, so I think this is something,

00:28:00.780 --> 00:28:02.580
 obviously when we have the turn back conversations and

00:28:02.580 --> 00:28:04.880
 everything else, that we're going to be talking about

00:28:04.900 --> 00:28:07.780
 frequently over the next few months, I'm sure, and just want

00:28:07.780 --> 00:28:10.520
 to let you all know that we are actively working on trying to

00:28:10.520 --> 00:28:12.880
 coincide all these things because they all fit together,

00:28:12.880 --> 00:28:16.580
 and the drainage piece really is kind of that first thing we

00:28:16.580 --> 00:28:21.160
 need to figure out as we move forward on those projects.

00:28:21.160 --> 00:28:22.300
 >> Thank you.

00:28:22.300 --> 00:28:33.100
 >> And the glossary of terms is the last page, so unless you

00:28:33.140 --> 00:28:36.080
 have questions, that's pretty much it for my side of the

00:28:36.080 --> 00:28:38.100
 story.

00:28:38.100 --> 00:28:41.780
 >> You're not going to read the glossary?

00:28:41.780 --> 00:28:45.980
 >> Only to put you to sleep.

00:28:45.980 --> 00:28:47.280
 >> Don't say that, we were up late last night.

00:28:47.280 --> 00:28:48.820
 That'd be a little too easy.

00:28:48.820 --> 00:28:49.860
 >> Sorry.

00:28:49.860 --> 00:28:52.020
 >> All right, well, thank you very much.

00:28:52.020 --> 00:28:55.000
 Any other questions?

00:28:55.000 --> 00:28:57.460
 Great, thanks, John.

00:28:57.460 --> 00:29:02.400
 We'll move on to item C, receive a report and hold a discussion

00:29:02.440 --> 00:29:06.980
 regarding the consideration of removing DCTA's wayside horn on

00:29:06.980 --> 00:29:09.000
 Shady Oaks Drive.

00:29:09.000 --> 00:29:13.480
 >> Okay, and I'll just stay up here because I'm giving the

00:29:13.480 --> 00:29:15.820
 presentation.

00:29:15.820 --> 00:29:18.660
 Good morning, hope everybody's doing well.

00:29:18.660 --> 00:29:20.680
 Let me share my screen.

00:29:20.680 --> 00:29:31.800
 All righty, so this is for the removal of the DCTA wayside horn

00:29:31.840 --> 00:29:34.240
 on Shady Oaks Drive.

00:29:34.240 --> 00:29:38.400
 A little background, in March of 2021, staff was contacted by a

00:29:38.400 --> 00:29:41.680
 resident concerned about the volume of the wayside horn at

00:29:41.680 --> 00:29:43.980
 the Shady Oaks Crossing.

00:29:43.980 --> 00:29:48.340
 This intersection is currently a quiet zone implemented by DCTA.

00:29:48.340 --> 00:29:54.820
 It is a quiet zone approved by the FRA.

00:29:54.820 --> 00:29:59.620
 This railroad line is maintained by DCTA for the A train, and

00:29:59.660 --> 00:30:03.200
 there are currently three DCTA wayside horns within city limits

00:30:03.200 --> 00:30:06.800
 at Sycamore, Shady Oaks, and Mayhill.

00:30:06.800 --> 00:30:14.380
 So we've been working with DCTA's consultant who also works

00:30:14.380 --> 00:30:19.440
 with the FRA on the feasibility of removing the wayside horn.

00:30:19.440 --> 00:30:22.380
 They confirmed that the wayside horn could be removed, but other

00:30:22.380 --> 00:30:25.380
 requirements would have to be met to maintain the FRA quiet

00:30:25.380 --> 00:30:27.860
 zone requirements.

00:30:27.880 --> 00:30:31.520
 So there's a few ways that you can maintain a quiet zone, and

00:30:31.520 --> 00:30:35.900
 you can implement putting in medians across so people can't

00:30:35.900 --> 00:30:42.800
 cross the intersection, but due to Curly Street and the Longhorn

00:30:42.800 --> 00:30:48.000
 business over here on the bottom part of the map, that is not

00:30:48.000 --> 00:30:51.240
 going to be a feasible solution.

00:30:51.240 --> 00:30:55.620
 So their recommendation is installing a four-quadrant gate.

00:30:55.640 --> 00:30:58.620
 Four-quadrant gate systems are gate at the crossing that

00:30:58.620 --> 00:31:02.920
 sufficiently blocks, fully block traffic, highway traffic,

00:31:02.920 --> 00:31:05.800
 goodness, from entering the crossing when the gates are

00:31:05.800 --> 00:31:09.220
 lowered, including at least one gate for each direction of

00:31:09.220 --> 00:31:11.500
 traffic on each approach.

00:31:11.500 --> 00:31:14.540
 So there are currently three intersections that have four

00:31:14.540 --> 00:31:17.940
 quadrant gates in the city limits, Morse Street, Duncan,

00:31:17.940 --> 00:31:20.340
 and Parker's Page Road.

00:31:20.340 --> 00:31:23.040
 And then you can see over here what the four-quadrant gate

00:31:23.080 --> 00:31:28.020
 looks like.

00:31:28.020 --> 00:31:31.480
 So the cost estimate for installing the two exits and

00:31:31.480 --> 00:31:36.260
 removing the existing horn is about $126,000.

00:31:36.260 --> 00:31:39.220
 This is an estimate and depends on material costs, including

00:31:39.220 --> 00:31:41.900
 design and project management costs.

00:31:41.900 --> 00:31:45.560
 If the mobility committee chooses to move forward, funding

00:31:45.560 --> 00:31:47.960
 considerations will be put during the budget

00:31:47.960 --> 00:31:51.100
 consideration process.

00:31:51.140 --> 00:31:55.680
 The timeline, so this will be once the wayside horn, or once

00:31:55.680 --> 00:31:59.180
 we start construction, you'll get a 60-day notice, construction

00:31:59.180 --> 00:32:03.580
 time, and then 20-day notice to establish that does not begin

00:32:03.580 --> 00:32:07.060
 until construction has completed.

00:32:07.060 --> 00:32:10.380
 So the next step is receive and address direction provided by

00:32:10.380 --> 00:32:11.820
 mobility committee.

00:32:11.820 --> 00:32:16.400
 So we're just looking for a recommendation from you guys on

00:32:16.400 --> 00:32:19.040
 how to proceed forward.

00:32:19.060 --> 00:32:21.460
 Just to clarify, this is just one resident who's

00:32:21.460 --> 00:32:25.200
 reached out to us.

00:32:25.200 --> 00:32:29.680
 >> I'm sorry, what did the resident say?

00:32:29.680 --> 00:32:32.680
 >> They're concerned, so they live close to the Shady Oaks

00:32:32.680 --> 00:32:37.840
 Drive Crossing, and they can hear the wayside horn, and it's

00:32:37.840 --> 00:32:41.460
 very loud, and they're wondering if we can remove it.

00:32:41.460 --> 00:32:43.480
 >> Oh, yeah, okay.

00:32:43.480 --> 00:32:46.020
 I'm sure you've heard from more than one resident over the years

00:32:46.020 --> 00:32:48.500
 on that.

00:32:48.520 --> 00:32:49.520
 >> We have not.

00:32:49.520 --> 00:32:52.760
 We have only heard from one, yes.

00:32:52.760 --> 00:32:57.200
 That has contacted us directly and has been in contact with CMO.

00:32:57.200 --> 00:33:02.580
 >> I can tell you that's like an applause line to talk about

00:33:02.580 --> 00:33:03.900
 getting rid of that.

00:33:03.900 --> 00:33:06.540
 I'll take questions and comments from other members,

00:33:06.540 --> 00:33:07.720
 and I've got it.

00:33:07.720 --> 00:33:09.620
 >> Vicki Burritt here.

00:33:09.620 --> 00:33:13.260
 You all have actually received two, for sure, because I'm also

00:33:13.260 --> 00:33:17.820
 one of those other people that have been affected by that horn,

00:33:17.860 --> 00:33:21.400
 and I don't live near that area, but I know that I can hear that

00:33:21.400 --> 00:33:26.500
 horn because it's a different sound, it's a different sound

00:33:26.500 --> 00:33:31.260
 from when the, you know, the regular train comes through.

00:33:31.260 --> 00:33:32.300
 >> Yes, ma'am.

00:33:32.300 --> 00:33:35.040
 >> And so if I'm standing in my backyard, and this has happened

00:33:35.040 --> 00:33:40.320
 to me several times, but because I don't live right there, but I

00:33:40.320 --> 00:33:45.180
 know if I can hear that horn from where I live, others are

00:33:45.220 --> 00:33:50.960
 just not, I don't think that they're just, or, you know, as

00:33:50.960 --> 00:33:53.900
 annoyed about it as this gentleman is apparently, but I

00:33:53.900 --> 00:33:57.800
 know that they're probably affected by it.

00:33:57.800 --> 00:34:01.440
 I've heard that horn before several times, so I also added

00:34:01.440 --> 00:34:08.280
 my name to the list of, you know, as a complainant.

00:34:08.280 --> 00:34:09.300
 >> Yes, ma'am.

00:34:09.300 --> 00:34:13.840
 >> So I would definitely like to, did you have any additional?

00:34:13.880 --> 00:34:16.720
 >> Oh, I mean, I just want to lend my support to what I think

00:34:16.720 --> 00:34:20.020
 you were about to say, which is you live pretty far from that.

00:34:20.020 --> 00:34:21.260
 >> I do, I live pretty far from there.

00:34:21.260 --> 00:34:22.960
 >> From that crossing, and if you can hear it, that's loud.

00:34:22.960 --> 00:34:23.980
 >> I can hear it.

00:34:23.980 --> 00:34:27.600
 1230 at night, I'm sitting on my back porch, and I said I can

00:34:27.600 --> 00:34:28.600
 hear that horn.

00:34:28.600 --> 00:34:29.960
 >> Yes, and if you're hearing the wayside horn at that hour,

00:34:29.960 --> 00:34:32.560
 it's because DCTA is doing maintenance on the railroad

00:34:32.560 --> 00:34:35.760
 track, and they're required to sound the horn for safety

00:34:35.760 --> 00:34:36.760
 reasons.

00:34:36.760 --> 00:34:38.000
 >> Right, I understand.

00:34:38.000 --> 00:34:42.440
 So I'd like to give direction for the city to move forward

00:34:42.480 --> 00:34:46.080
 with that project.

00:34:46.080 --> 00:34:50.420
 >> And I concur, I would also like to move forward with that.

00:34:50.420 --> 00:34:54.320
 >> So I have just a couple of questions.

00:34:54.320 --> 00:35:02.460
 How much would it cost to make the lane-changing, I forget the

00:35:02.460 --> 00:35:05.360
 exact terms in the backup, but, you know, one of the options was

00:35:05.360 --> 00:35:08.760
 doing this, another is, you know, there's a comment in the

00:35:08.760 --> 00:35:12.000
 presentation about the medians aren't adequate, but what would

00:35:12.040 --> 00:35:14.800
 it cost to do that, to make it so that you can't change lanes?

00:35:14.800 --> 00:35:18.780
 My understanding of the basic idea of the four gates so you

00:35:18.780 --> 00:35:23.220
 can't go in the wrong lane and get around the gate, but the

00:35:23.220 --> 00:35:27.020
 other way to accomplish that is with like a deep curb, is that

00:35:27.020 --> 00:35:28.120
 the general idea?

00:35:28.120 --> 00:35:32.160
 >> Yes, so you extend the median on both sides, but because of

00:35:32.160 --> 00:35:39.100
 the placement of, I believe it's curly, you're not able to do

00:35:39.100 --> 00:35:40.600
 that.

00:35:40.600 --> 00:35:41.460
 >> Oh, okay.

00:35:41.500 --> 00:35:45.160
 Yes, so curly street is too close to the intersection and you

00:35:45.160 --> 00:35:48.700
 have to maintain, I can't remember off the top of my head

00:35:48.700 --> 00:35:53.040
 what the length of the curb is, or of the median, and you have

00:35:53.040 --> 00:35:57.380
 to maintain that length to be FRA compliant, and because of

00:35:57.380 --> 00:35:59.880
 where curly street is, we can't meet that.

00:35:59.880 --> 00:36:00.980
 >> So it's a fiscal obstacle.

00:36:00.980 --> 00:36:07.720
 Okay, $126,000 is a lot of money, but it sounds like that's

00:36:07.720 --> 00:36:09.200
 the only option you have.

00:36:09.220 --> 00:36:12.000
 >> Yeah, I join the majority.

00:36:12.000 --> 00:36:13.120
 >> Okay.

00:36:13.120 --> 00:36:14.500
 >> All right, I think anything else?

00:36:14.500 --> 00:36:16.360
 We're good on, we're done with that item?

00:36:16.360 --> 00:36:19.500
 >> I would just point out this was Logan's first presentation,

00:36:19.500 --> 00:36:20.800
 so great job, Logan.

00:36:20.800 --> 00:36:22.800
 >> Oh, hey, congratulations.

00:36:22.800 --> 00:36:25.140
 >> Yay.

00:36:25.140 --> 00:36:32.280
 >> So just to clarify, so the gate on the north side of the

00:36:32.280 --> 00:36:36.020
 railroad tracks would be in between curly and the railroad

00:36:36.020 --> 00:36:39.020
 tracks, right?

00:36:39.060 --> 00:36:41.520
 >> I believe so.

00:36:41.520 --> 00:36:43.860
 >> Oh, yeah, one other question.

00:36:43.860 --> 00:36:48.360
 There's some discussion in the backup about the impact of

00:36:48.360 --> 00:36:50.360
 presence sensors.

00:36:50.360 --> 00:36:54.160
 Is it our plan to have presence sensors, or not, and it sounds

00:36:54.160 --> 00:36:57.840
 like it must serve some purpose, but it sounds like they actually

00:36:57.840 --> 00:37:03.540
 diminish safety, so that's what I'm asking.

00:37:03.540 --> 00:37:07.520
 >> Are you talking about the FRA quiet zone requirements page?

00:37:07.540 --> 00:37:10.820
 >> Yeah, yep.

00:37:10.820 --> 00:37:14.660
 >> I'm not sure that wasn't DCTA's consultant's

00:37:14.660 --> 00:37:21.120
 recommendation, so I will have to get back to you on that.

00:37:21.120 --> 00:37:25.260
 >> Okay, sounds like, you know, most of the actions would be the

00:37:25.260 --> 00:37:30.000
 same anyway to get the gates, but yeah, I'd like to understand.

00:37:30.000 --> 00:37:33.980
 >> Yeah, I believe they gave us the most feasible option, both

00:37:34.000 --> 00:37:39.280
 cost-wise and do-ability.

00:37:39.280 --> 00:37:41.880
 >> Great, thank you.

00:37:41.880 --> 00:37:47.580
 All right, I'll close that item and open item D, receive a report

00:37:47.580 --> 00:37:50.520
 and hold a discussion regarding the project schedules and

00:37:50.520 --> 00:37:53.960
 sequencing of construction associated with the different

00:37:53.960 --> 00:37:58.360
 phases of the I-35 widening and Bonnie Bray reconstruction

00:37:58.360 --> 00:38:00.400
 projects.

00:38:00.400 --> 00:38:03.540
 >> Good morning, my name is Kyle Pettigrew, I'm a program manager

00:38:03.580 --> 00:38:08.480
 with Capital Improvements and here to discuss the phasing

00:38:08.480 --> 00:38:13.580
 between I-35 and Bonnie Bray and adjacent projects.

00:38:13.620 --> 00:38:33.740
 Let me see, where's the share screen?

00:38:33.740 --> 00:38:35.800
 First we'll go through an overview of the adjacent

00:38:35.800 --> 00:38:38.260
 projects surrounding Bonnie Bray.

00:38:38.260 --> 00:38:41.200
 So this map is a little bit zoomed out just to capture all

00:38:41.240 --> 00:38:46.620
 of the projects, we do have it in an additional exhibit.

00:38:46.620 --> 00:38:51.620
 So we have the I-35 city utility relocations, these are the

00:38:51.620 --> 00:38:57.620
 relocations associated with TechStats expansion of I-35 from

00:38:57.620 --> 00:39:00.760
 Mayhill to Loop 288 and then from the east-west split up to

00:39:00.760 --> 00:39:02.400
 Milam Road.

00:39:02.400 --> 00:39:06.260
 The timeframe of these improvements is quarter three of

00:39:06.260 --> 00:39:09.940
 this year to quarter four of 2023.

00:39:09.960 --> 00:39:12.480
 We have the Denton Municipal electric construction of the

00:39:12.480 --> 00:39:14.500
 Hickory substation.

00:39:14.500 --> 00:39:17.240
 This is a new electrical substation, it's on the east

00:39:17.240 --> 00:39:21.120
 side of Bonnie Bray between West Oak and West Hickory.

00:39:21.120 --> 00:39:24.920
 So the substation construction is from quarter four this year

00:39:24.920 --> 00:39:28.920
 to quarter two of 2024 and they also have a small amount of

00:39:28.920 --> 00:39:32.320
 duck bank construction in that area, underground duck bank,

00:39:32.320 --> 00:39:36.100
 from quarter two to quarter four of 2024.

00:39:36.100 --> 00:39:39.560
 We have the TechStat widening of I-35, so that's the widening

00:39:39.600 --> 00:39:45.140
 and reconstruction that Mr. Polster reviewed earlier on I-35,

00:39:45.140 --> 00:39:48.840
 again Mayhill to Loop 288 and from the east-west split to

00:39:48.840 --> 00:39:50.340
 Milam Road.

00:39:50.340 --> 00:39:53.820
 So their projects are slated for quarter four of next year to

00:39:53.820 --> 00:39:57.760
 quarter four of 2027.

00:39:57.760 --> 00:40:00.420
 In looking at this phasing, we discussed it with TechStat

00:40:00.420 --> 00:40:04.700
 several times and we verified that traffic will not be

00:40:04.700 --> 00:40:08.340
 rerouted along city streets during this time period.

00:40:08.360 --> 00:40:12.340
 And TechStat is committed to maintaining their lane counts in

00:40:12.340 --> 00:40:14.700
 the construction area during construction.

00:40:14.700 --> 00:40:19.180
 So we have the quote of what they committed to below.

00:40:19.180 --> 00:40:25.320
 Here's the Bonnie Bray reconstruction.

00:40:25.320 --> 00:40:32.820
 So phase three, that's south of 35, that's the purple segment.

00:40:32.820 --> 00:40:36.820
 That one is fully funded through RTR and utility funds.

00:40:36.860 --> 00:40:43.100
 Phase four is the green segment from 35 to scripture.

00:40:43.100 --> 00:40:47.200
 Design and acquisitions on that are funded through 2014 bond

00:40:47.200 --> 00:40:48.640
 and RTR.

00:40:48.640 --> 00:40:53.040
 We're working with the 2022 county bond program for the

00:40:53.040 --> 00:40:56.620
 remainder of the construction funding.

00:40:56.620 --> 00:41:02.280
 This project is in the same area as the current north-south

00:41:02.280 --> 00:41:05.780
 Watermain phase three project.

00:41:05.820 --> 00:41:08.660
 That's the project on Bonnie Bray installing the water

00:41:08.660 --> 00:41:10.160
 transmission line.

00:41:10.160 --> 00:41:13.300
 So north-south water phase three includes temporary restoration

00:41:13.300 --> 00:41:16.860
 of the road surface for the south bond lanes where the water

00:41:16.860 --> 00:41:19.760
 line is being installed.

00:41:19.760 --> 00:41:22.900
 That's set to be completed by quarter two of this year and

00:41:22.900 --> 00:41:25.140
 we're exploring options to expand that temporary

00:41:25.140 --> 00:41:28.940
 restoration to the north bond lanes due to the condition that

00:41:28.940 --> 00:41:35.680
 they're in until this phase four, the full road reconstruction

00:41:35.720 --> 00:41:40.780
 is scheduled to begin in 2024.

00:41:40.780 --> 00:41:44.220
 Phase five is from scripture to US 380.

00:41:44.220 --> 00:41:46.820
 That's the outline in pink.

00:41:46.820 --> 00:41:53.500
 That is funded by 2019 bond funding.

00:41:53.500 --> 00:41:54.840
 That's utilized by phase six.

00:41:54.840 --> 00:41:57.800
 So as phase six is reimbursed by TechStat, that funding will be

00:41:57.800 --> 00:41:59.740
 used for phase five construction.

00:41:59.740 --> 00:42:03.980
 And then phase six is from US 380 to US 77.

00:42:04.020 --> 00:42:09.680
 That's the blue segment on the northern end of Bonnie Bray.

00:42:09.680 --> 00:42:12.680
 So that's funded through utilities and 2019 bond and that

00:42:12.680 --> 00:42:16.860
 is reimbursable by TechStat.

00:42:16.860 --> 00:42:20.820
 So here's an overall program schedule.

00:42:20.820 --> 00:42:27.060
 The top part of it includes the adjacent projects and the bottom

00:42:27.060 --> 00:42:30.540
 section includes the Bonnie Bray reconstruction.

00:42:30.540 --> 00:42:33.580
 So a few notes on this.

00:42:33.600 --> 00:42:36.740
 The Bonnie Bray program will overlap with these adjacent

00:42:36.740 --> 00:42:41.640
 construction projects until mid 2026 when Bonnie Bray is set

00:42:41.640 --> 00:42:44.080
 to be completed.

00:42:44.080 --> 00:42:47.960
 TechStat has committed to maintain their traffic pattern

00:42:47.960 --> 00:42:51.960
 and a high level traffic study suggests that the I-35

00:42:51.960 --> 00:42:56.800
 construction will not have a significant increase of traffic

00:42:56.800 --> 00:43:01.060
 on Bonnie Bray during that reconstruction.

00:43:01.100 --> 00:43:06.980
 So Bonnie Bray phase four, we are working with the county bond

00:43:06.980 --> 00:43:09.440
 to fund the construction portion.

00:43:09.440 --> 00:43:12.820
 And then the further note that that pork pavement quality due

00:43:12.820 --> 00:43:14.720
 to construction on the north-south water main phase

00:43:14.720 --> 00:43:20.860
 three, we're looking to remedy that through temporary surface

00:43:20.860 --> 00:43:24.420
 restoration that would be designed to last until phase

00:43:24.420 --> 00:43:29.460
 four of Bonnie Bray begins in 2024.

00:43:29.500 --> 00:43:33.300
 So then here's just a overall construction heat maps.

00:43:33.300 --> 00:43:37.040
 So on the left we have 2022.

00:43:37.040 --> 00:43:39.440
 Any line in blue is a City of Denton project.

00:43:39.440 --> 00:43:42.300
 Any line in red is a TechStat project.

00:43:42.300 --> 00:43:46.480
 So if you notice the blue lines, we have construction,

00:43:46.480 --> 00:43:50.540
 the utility relocations over at May Hill and right by the

00:43:50.540 --> 00:43:53.780
 east-west split of 35 beginning.

00:43:53.820 --> 00:43:59.820
 We have the north-south water finishing up their temporary

00:43:59.820 --> 00:44:03.600
 surface restoration and then phase six and phase three,

00:44:03.600 --> 00:44:07.100
 the far southern end and the far northern end of Bonnie Bray

00:44:07.100 --> 00:44:08.340
 beginning.

00:44:08.340 --> 00:44:14.840
 Next year we would have all of the utility relocations for

00:44:14.840 --> 00:44:17.980
 TechStat underway while phase six and phase three are fully

00:44:17.980 --> 00:44:21.320
 underway for Bonnie Bray.

00:44:21.340 --> 00:44:25.520
 2024 we would be done with the TechStat utility relocations,

00:44:25.520 --> 00:44:28.820
 but they would begin their work in red while we're finishing up

00:44:28.820 --> 00:44:34.020
 phase three and six and in the middle of phase four.

00:44:34.020 --> 00:44:39.660
 And then 2025 to '26 on the far right we have TechStats work

00:44:39.660 --> 00:44:42.700
 completing while Bonnie Bray is just finishing up phase five

00:44:42.700 --> 00:44:44.740
 in the middle.

00:44:44.740 --> 00:44:49.140
 Any questions on the coordination between the

00:44:49.140 --> 00:44:50.740
 projects?

00:44:50.780 --> 00:44:53.420
 >> Kyle, if I could just jump in real quick, just a little

00:44:53.420 --> 00:44:56.080
 context, I think, you know, we really looked at a number of

00:44:56.080 --> 00:44:58.480
 different options when we came up with this proposal.

00:44:58.480 --> 00:45:00.620
 We know that, I mean, and I think we tried to make it clear

00:45:00.620 --> 00:45:04.920
 on the map, 2024 is going to be kind of a nightmare, right?

00:45:04.920 --> 00:45:07.060
 I mean, we're going to hear a lot of comments.

00:45:07.060 --> 00:45:09.760
 We're going to have a significant public outreach push

00:45:09.760 --> 00:45:12.060
 to make sure everyone's aware of what's going on.

00:45:12.060 --> 00:45:16.100
 But we're going to be fully prepared for questions and

00:45:16.100 --> 00:45:17.940
 complaints and everything along with it.

00:45:17.980 --> 00:45:20.780
 We looked at maybe phasing out Bonnie Bray and kind of

00:45:20.780 --> 00:45:24.540
 extending the project, but really this was the best option

00:45:24.540 --> 00:45:27.880
 to kind of rip the bandaid off and just do everything we can.

00:45:27.880 --> 00:45:31.580
 So just a little context and all the work that went into this.

00:45:31.580 --> 00:45:34.560
 >> Yeah, I definitely appreciate that and, you know,

00:45:34.560 --> 00:45:37.720
 I think that this can be filed under growing pains.

00:45:37.720 --> 00:45:44.260
 It sounds like staff has done the best they can to design a

00:45:44.300 --> 00:45:48.140
 plan that will minimize those growing pains, but these are

00:45:48.140 --> 00:45:51.600
 just the types of situations that we run into when a city is

00:45:51.600 --> 00:45:54.180
 growing as fast as we are.

00:45:54.180 --> 00:45:57.280
 >> I would mention too that one of the big decision points when

00:45:57.280 --> 00:46:02.140
 staff, Kyle, myself, et cetera, worked with TxDOT and really

00:46:02.140 --> 00:46:05.160
 understood how they're going to construct.

00:46:05.160 --> 00:46:08.260
 Dallas District of TxDOT has a protocol that they follow.

00:46:08.260 --> 00:46:12.260
 Kyle mentioned it, where they do not lower the level of service.

00:46:12.300 --> 00:46:15.220
 So if there's three lanes out there today along 35,

00:46:15.220 --> 00:46:17.900
 there's going to be three lanes out there during construction.

00:46:17.900 --> 00:46:20.540
 And that really changes the way you think about that overall

00:46:20.540 --> 00:46:23.040
 construction in both of those areas with those roadways

00:46:23.040 --> 00:46:24.040
 and alignments.

00:46:24.040 --> 00:46:27.500
 So that was a very helpful tool when we had that conversation

00:46:27.500 --> 00:46:29.680
 with TxDOT really to bring that forward.

00:46:29.680 --> 00:46:32.940
 Not every district of TxDOT does that, but that is the

00:46:32.940 --> 00:46:34.980
 Dallas District's protocol.

00:46:34.980 --> 00:46:40.380
 >> Councilmember Byrd, any comments or questions?

00:46:40.420 --> 00:46:45.960
 I have a number of ma'am, but go ahead if you've got some.

00:46:45.960 --> 00:46:50.260
 >> So the Bonnie Bray phases, I don't know, I mean, it's

00:46:50.260 --> 00:46:52.960
 probably too late in the game to kind of bring this up, but,

00:46:52.960 --> 00:46:56.840
 you know, obviously they're numbered from south to north,

00:46:56.840 --> 00:46:59.800
 but they don't go in chronological order.

00:46:59.800 --> 00:47:04.540
 Is there perhaps some way we can more clearly communicate that to

00:47:04.540 --> 00:47:06.780
 the public, because that's going to be a little confusing, I

00:47:06.780 --> 00:47:10.280
 think, to the public that phase four is going to be the last one

00:47:10.320 --> 00:47:12.320
 to get done, not phase six.

00:47:12.320 --> 00:47:15.960
 >> You have a problem with phase six being before phase five,

00:47:15.960 --> 00:47:18.400
 basically being concurrent with phase three?

00:47:18.400 --> 00:47:20.320
 I don't understand why it's confusing about that.

00:47:20.320 --> 00:47:21.760
 >> I think that's a good point.

00:47:21.760 --> 00:47:23.160
 We can think about that, especially on the public

00:47:23.160 --> 00:47:24.160
 outreach.

00:47:24.160 --> 00:47:26.660
 I think the numbers really were derived from the bond program,

00:47:26.660 --> 00:47:28.640
 right, because we had the 2014 and we were looking at these

00:47:28.640 --> 00:47:31.680
 phases, the opportunity to have six go first with the external

00:47:31.680 --> 00:47:34.800
 funding really drove some of that, but I think that's a good

00:47:34.800 --> 00:47:37.180
 point, especially as we are outward focused on how we

00:47:37.180 --> 00:47:38.220
 message that.

00:47:41.220 --> 00:47:48.920
 >> I was talking with a constituent one day, and every

00:47:48.920 --> 00:47:51.920
 time I talk to someone, they're always talking about the roads,

00:47:51.920 --> 00:47:56.000
 and so I thought maybe we would design a program and call it

00:47:56.000 --> 00:48:00.760
 get mad, get mad again, then be happy.

00:48:00.760 --> 00:48:03.600
 So maybe that might be something that will help put all of this

00:48:03.600 --> 00:48:04.840
 in perspective.

00:48:04.840 --> 00:48:08.840
 We're already mad, we're going to get mad again, and then we'll

00:48:08.880 --> 00:48:10.840
 be happy someday.

00:48:10.840 --> 00:48:15.780
 My question does go to the Bonnie Bray.

00:48:15.780 --> 00:48:18.380
 It looks like it was coming along quite fine to me.

00:48:18.380 --> 00:48:23.120
 I drive down Bonnie Bray here and there, and it looks like,

00:48:23.120 --> 00:48:25.320
 you know, you can see the progress on it.

00:48:25.320 --> 00:48:28.360
 And from a layperson's perspective, it appears as though

00:48:28.360 --> 00:48:30.300
 it's starting to kind of wrap up.

00:48:30.300 --> 00:48:34.240
 But as we look here, it seems like there's quite a bit more to

00:48:34.240 --> 00:48:36.700
 go through with that project if we're looking at it.

00:48:36.740 --> 00:48:39.080
 Of course, from top to bottom.

00:48:39.080 --> 00:48:43.680
 So it appears to be okay, especially on the northern side

00:48:43.680 --> 00:48:47.040
 where we're wrapping it up and then closer to 35.

00:48:47.040 --> 00:48:48.720
 It looks like it's okay.

00:48:48.720 --> 00:48:53.460
 So it looks like we'll have to do some media work on teaching

00:48:53.460 --> 00:48:56.760
 and educating the public as to how it's going to go through.

00:48:56.760 --> 00:48:57.920
 >> Thank you.

00:48:57.920 --> 00:49:00.020
 >> Yep.

00:49:00.020 --> 00:49:05.560
 >> So I have, you know, some questions that, I don't know,

00:49:05.600 --> 00:49:10.240
 they may be stupid questions, but the premise, as it was

00:49:10.240 --> 00:49:14.980
 explained to me, I think by pre-TAM, who's on here now,

00:49:14.980 --> 00:49:19.980
 by somebody, was behind the whole effort to do Bonnie Bray

00:49:19.980 --> 00:49:24.020
 and why it's been so heavily funded by the state was precisely

00:49:24.020 --> 00:49:27.820
 because they wanted it to be an alternate route while so much

00:49:27.820 --> 00:49:29.580
 work was being done on 35.

00:49:29.580 --> 00:49:32.620
 Now, if, as, you know, to me, this is like the big headline,

00:49:32.620 --> 00:49:35.320
 but it's in the footnote, if they're going to keep the same

00:49:35.360 --> 00:49:40.660
 number of lanes going on 35 throughout construction,

00:49:40.660 --> 00:49:46.500
 so there really isn't a need for that, why are we doing it?

00:49:46.500 --> 00:49:51.000
 And before you answer, you know, and, or get over being

00:49:51.000 --> 00:49:57.380
 thunderstruck by the bluntness of that question, some of it

00:49:57.380 --> 00:50:01.760
 clearly has to do with the high school under construction.

00:50:01.780 --> 00:50:06.660
 How does the timing that we've been shown sync up with key

00:50:06.660 --> 00:50:07.860
 dates for that?

00:50:07.860 --> 00:50:10.800
 So those are my two questions to start with.

00:50:10.800 --> 00:50:15.660
 Why are we doing it if it's not, if the original purpose is not,

00:50:15.660 --> 00:50:17.100
 no longer needed?

00:50:17.100 --> 00:50:22.340
 And is the answer in part the high school and development

00:50:22.340 --> 00:50:24.840
 around that and how are we doing on that timing?

00:50:27.840 --> 00:50:32.440
 So as far as why we're doing it, the work that's planned is an

00:50:32.440 --> 00:50:37.880
 overall street reconstruction, which includes not just surface

00:50:37.880 --> 00:50:42.020
 restoration, it's total removal of the pavement, it's repair of

00:50:42.020 --> 00:50:45.920
 the subgrade and placing back brand new pavement.

00:50:45.920 --> 00:50:51.900
 And the reason for it, especially down towards 35, is

00:50:51.900 --> 00:50:55.400
 temporary repairs or surface repairs have a very short

00:50:55.440 --> 00:51:01.280
 lifespan, so we can resurface it, but with the traffic that it

00:51:01.280 --> 00:51:05.540
 sees, it will, it will need to be resurfaced again, you know,

00:51:05.540 --> 00:51:07.080
 within five years.

00:51:07.080 --> 00:51:10.660
 So with the overall reconstruction, that's a big

00:51:10.660 --> 00:51:11.660
 portion of it.

00:51:11.660 --> 00:51:17.060
 And then I believe as far as phase six with the, with the

00:51:17.060 --> 00:51:21.500
 connection with the high school, there's a, that with the state

00:51:21.540 --> 00:51:25.760
 funding and with the construction of the new high

00:51:25.760 --> 00:51:28.900
 school there, that was the decision that pushed phase six

00:51:28.900 --> 00:51:33.600
 to be constructed before the rest of the phase out of sequence.

00:51:33.600 --> 00:51:38.280
 If I could just jump in and try to answer your question, I think

00:51:38.280 --> 00:51:40.840
 to answer your question specifically, I don't, you know,

00:51:40.840 --> 00:51:44.680
 the push that Bonnie and Bray wasn't for the temporary time

00:51:44.680 --> 00:51:46.980
 while they're doing 35 construction, I think it was the

00:51:46.980 --> 00:51:51.220
 long term to have that alternate route long term, not just

00:51:51.260 --> 00:51:52.260
 during construction.

00:51:52.260 --> 00:51:57.040
 So I think that's a difference in framing the conversation.

00:51:57.040 --> 00:52:00.200
 >> And, okay, thank you for that.

00:52:00.200 --> 00:52:05.140
 And then, okay, now I get that the reason six was accelerated

00:52:05.140 --> 00:52:08.240
 so that it no longer makes sense to call it six was because of

00:52:08.240 --> 00:52:09.320
 the school.

00:52:09.320 --> 00:52:11.240
 So does that timing still work?

00:52:11.240 --> 00:52:14.220
 I mean, I'm saying that because I don't know exactly what the

00:52:14.220 --> 00:52:16.660
 timing needs are for the school.

00:52:16.660 --> 00:52:21.080
 So are we still meeting that objective?

00:52:21.120 --> 00:52:22.120
 >> I believe so.

00:52:22.120 --> 00:52:24.360
 There's current capacity up there, you know, with the

00:52:24.360 --> 00:52:26.920
 expansion of six starting this year.

00:52:26.920 --> 00:52:31.860
 I believe that's going according to the discussed schedule.

00:52:31.860 --> 00:52:35.500
 >> Could we, you know, maybe have a follow up note on that,

00:52:35.500 --> 00:52:39.340
 just to kind of confirm that that's still on target?

00:52:39.340 --> 00:52:40.880
 >> Yep.

00:52:40.880 --> 00:52:42.840
 >> Appreciate that.

00:52:42.840 --> 00:52:48.940
 And my last question is, I notice in the footnotes that it

00:52:48.980 --> 00:52:51.980
 says that when they have temporary closures, which may

00:52:51.980 --> 00:52:56.360
 occur due to demolition of bridges and a couple of other

00:52:56.360 --> 00:53:00.960
 conditions, they say it will not go on city streets.

00:53:00.960 --> 00:53:04.160
 It will use the TxDOT network.

00:53:04.160 --> 00:53:09.660
 That means not Monte Bray, Locust and Elm, right?

00:53:09.660 --> 00:53:12.900
 >> They, so whenever they have to do that, they'll submit a

00:53:12.900 --> 00:53:16.580
 plan, you know, the TxDOT network that they have to reroute

00:53:16.580 --> 00:53:18.440
 through has to be able to handle the capacity that they're

00:53:18.480 --> 00:53:19.480
 planning to reroute.

00:53:19.480 --> 00:53:21.320
 So they'll have to submit a plan.

00:53:21.320 --> 00:53:25.860
 I know Elm and Locust are logical because they're close,

00:53:25.860 --> 00:53:29.380
 but they might not be able to handle the capacity of traffic

00:53:29.380 --> 00:53:33.560
 that TxDOT is needing to move, so it may, you know,

00:53:33.560 --> 00:53:36.020
 be over towards Luke 288.

00:53:36.020 --> 00:53:38.460
 >> Okay, because that, yeah, my reaction was that that would be

00:53:38.460 --> 00:53:40.540
 sort of potentially disastrous.

00:53:40.540 --> 00:53:44.900
 So there are alternatives that would be considered.

00:53:44.900 --> 00:53:46.240
 Okay, good to know.

00:53:46.280 --> 00:53:49.940
 >> Mayor Pritam, to that question, we will confirm with

00:53:49.940 --> 00:53:52.040
 TxDOT that that's not their anticipation.

00:53:52.040 --> 00:53:55.540
 I haven't been aware or had any conversations that an alternate

00:53:55.540 --> 00:53:58.980
 route or an alternate location would be moving folks from 35

00:53:58.980 --> 00:54:01.020
 to Elm and Locust, nor has Kyle.

00:54:01.020 --> 00:54:05.160
 So we will confirm that, but that's not what we understood

00:54:05.160 --> 00:54:07.420
 from the information that we received or the conversations

00:54:07.420 --> 00:54:08.960
 that we've had with TxDOT.

00:54:08.960 --> 00:54:11.860
 They will look to have other locations that are TxDOT

00:54:11.900 --> 00:54:16.460
 structures to move folks to and from.

00:54:16.460 --> 00:54:19.200
 >> Yeah, it'd be great to hear what, you know, they think they

00:54:19.200 --> 00:54:23.780
 might be leaning toward.

00:54:23.780 --> 00:54:25.020
 That's all I have on this item.

00:54:25.020 --> 00:54:28.640
 Anyone else have anything else?

00:54:28.640 --> 00:54:29.780
 Okay, thank you.

00:54:29.780 --> 00:54:30.920
 >> Thank you.

00:54:30.920 --> 00:54:33.860
 >> So we'll move on to item E, staff report.

00:54:41.900 --> 00:54:44.400
 All righty, so the first thing we're going to start off with

00:54:44.400 --> 00:54:48.700
 today on the staff report is I'm going to ask Brett to come down

00:54:48.700 --> 00:54:50.200
 and introduce himself.

00:54:50.200 --> 00:54:53.140
 I'm happy to announce that we now have a new deputy city

00:54:53.140 --> 00:54:55.420
 engineer who started on Monday.

00:54:55.420 --> 00:54:58.020
 So I know you're all very excited, as you know, that our

00:54:58.020 --> 00:55:01.180
 department was much needing this position for a period of time.

00:55:01.180 --> 00:55:05.620
 And so we have a new deputy city engineer who started on Monday.

00:55:05.620 --> 00:55:08.120
 So I know you're all very excited, as you know, that our

00:55:08.120 --> 00:55:11.460
 department was much needing this position for a period of time.

00:55:11.500 --> 00:55:14.400
 And so we are going to have Brett come down and talk to us a

00:55:14.400 --> 00:55:17.240
 little bit about his background and give him an opportunity to

00:55:17.240 --> 00:55:21.440
 introduce himself.

00:55:21.440 --> 00:55:24.540
 >> Welcome, Brett.

00:55:24.540 --> 00:55:25.580
 >> Thank you.

00:55:25.580 --> 00:55:27.240
 My name is Brett Bourgeois.

00:55:27.240 --> 00:55:28.840
 I'm the new deputy city engineer.

00:55:28.840 --> 00:55:33.480
 And I come from California by way of Minnesota, have eight

00:55:33.480 --> 00:55:37.020
 years of experience of design experience in California, then

00:55:37.020 --> 00:55:40.120
 have about seven years of project manage experience.

00:55:40.160 --> 00:55:43.220
 Just recently five of it up in Minnesota, managing a light rail

00:55:43.220 --> 00:55:48.260
 project for Minneapolis and the city's areas and then just

00:55:48.260 --> 00:55:52.040
 relocated here about two weeks ago and started on Monday.

00:55:52.040 --> 00:55:55.000
 So I decided to be working here and getting to know everybody

00:55:55.000 --> 00:55:57.500
 and being part of the city.

00:55:57.500 --> 00:56:02.520
 >> We are really glad to have you and I believe you've picked

00:56:02.520 --> 00:56:04.040
 a really nice place to live.

00:56:04.040 --> 00:56:05.640
 >> Yes, I'm liking it a lot.

00:56:05.640 --> 00:56:06.640
 It's very nice.

00:56:06.640 --> 00:56:09.520
 It's nice to be able to cold, nice to be able to go outside

00:56:09.560 --> 00:56:12.860
 year-round and enjoying everything that Fenton and

00:56:12.860 --> 00:56:14.820
 Texas has to offer.

00:56:14.820 --> 00:56:16.400
 >> Excellent.

00:56:16.400 --> 00:56:19.420
 >> There's certainly no shortage of work for you.

00:56:19.420 --> 00:56:20.100
 >> I know there is.

00:56:20.100 --> 00:56:21.660
 Thank you.

00:56:21.660 --> 00:56:23.600
 >> Thank you, Brett.

00:56:23.600 --> 00:56:24.600
 All righty.

00:56:24.600 --> 00:56:27.040
 So we'll move on to the staff report.

00:56:36.580 --> 00:56:44.120
 Let me play a little bit of -- all righty.

00:56:44.120 --> 00:56:47.360
 So first thing that we did, obviously, was introduce Brett.

00:56:47.360 --> 00:56:49.900
 The second item that is currently on our report is to

00:56:49.900 --> 00:56:53.160
 talk about the speeding concerns along Dallas Drive.

00:56:53.160 --> 00:56:58.700
 I had some several Friday reports that we have put out,

00:56:58.700 --> 00:57:02.200
 obviously, that y'all get a copy of and that backup information.

00:57:02.200 --> 00:57:06.140
 You can see that there was a Friday report in October and

00:57:06.180 --> 00:57:09.620
 then, of course, another one later in October and then

00:57:09.620 --> 00:57:11.780
 another one that happened in November.

00:57:11.780 --> 00:57:15.180
 And so just wanted to kind of bring up, and I'll go back to

00:57:15.180 --> 00:57:17.920
 the very top, just to kind of talk through our action plan and

00:57:17.920 --> 00:57:20.400
 our next steps.

00:57:20.400 --> 00:57:24.960
 So, you know, during the last meeting that we had in December,

00:57:24.960 --> 00:57:27.460
 you know, there was a request to talk about the speeding concerns

00:57:27.460 --> 00:57:28.800
 along Dallas Drive.

00:57:28.800 --> 00:57:32.900
 Reminder, Dallas Drive is a TxDOT roadway, but the following

00:57:32.900 --> 00:57:35.840
 Friday report items really were the steps that staff has taken

00:57:35.880 --> 00:57:39.180
 forward to prepare that information for all of you to

00:57:39.180 --> 00:57:41.080
 address those speeding concerns.

00:57:41.080 --> 00:57:43.980
 We've been in contact with the police department and we have

00:57:43.980 --> 00:57:46.880
 regular meetings with them to really talk about what the speed

00:57:46.880 --> 00:57:49.560
 studies show, what the information is that's collected

00:57:49.560 --> 00:57:53.700
 and discuss what additional measures could happen or occur

00:57:53.700 --> 00:57:57.120
 to help with those speeding concerns.

00:57:57.120 --> 00:58:00.660
 I will tell you that Nathan, I know I've mentioned this before,

00:58:00.660 --> 00:58:03.740
 is leading the citywide speed study effort and this roadway

00:58:03.760 --> 00:58:06.800
 has been added as a part of that and we think that will give us a

00:58:06.800 --> 00:58:10.340
 good idea based on the data collected and he has a number of

00:58:10.340 --> 00:58:12.540
 collection points along this roadway.

00:58:12.540 --> 00:58:15.980
 And so we are anticipating, based on that information coming

00:58:15.980 --> 00:58:19.420
 back, then looking at the speed limit of this particular roadway

00:58:19.420 --> 00:58:22.620
 to see if any modifications need to be made in coordination with

00:58:22.620 --> 00:58:24.920
 TxDOT.

00:58:24.920 --> 00:58:27.760
 Until that, obviously, I know we've talked about the date for

00:58:27.760 --> 00:58:31.400
 that to be completed and then come to share that with council.

00:58:31.420 --> 00:58:33.860
 And of course, mobility committee would be late August,

00:58:33.860 --> 00:58:37.740
 early September and so when we do bring that forward,

00:58:37.740 --> 00:58:40.500
 we'll talk about if there's modifications that need to be

00:58:40.500 --> 00:58:42.540
 made in this area.

00:58:42.540 --> 00:58:47.940
 For now, I guess I should mention of course PD will

00:58:47.940 --> 00:58:51.780
 continue to enforce the concerns and I know a lot of the concerns

00:58:51.780 --> 00:58:54.680
 that have been mentioned, just recently we've had that

00:58:54.680 --> 00:58:59.160
 conversation even last week with PD and they put some additional

00:58:59.180 --> 00:59:02.760
 measures out there to look in those areas where folks are

00:59:02.760 --> 00:59:09.300
 exiting 35 at a higher rate of speed and then of course it goes

00:59:09.300 --> 00:59:14.100
 down to 45 immediately to 35 and then in some areas all the way

00:59:14.100 --> 00:59:16.700
 to 30 as you come through town.

00:59:16.700 --> 00:59:20.240
 I myself have received a speeding violation on that roadway

00:59:20.240 --> 00:59:24.140
 about 20 years ago so I understand the concerns and know

00:59:24.140 --> 00:59:27.820
 how hard it is at many times to, you know,

00:59:27.860 --> 00:59:29.920
 obviously take your foot off the gas.

00:59:29.920 --> 00:59:34.420
 And you have to stop blaming yourself.

00:59:34.420 --> 00:59:39.060
 That feedback sign on Bell headed northbound like just

00:59:39.060 --> 00:59:41.540
 north of Dallas Drive is that gets me every time,

00:59:41.540 --> 00:59:43.340
 every single time I go past that sign,

00:59:43.340 --> 00:59:45.040
 I go, oh my gosh, I'm speeding.

00:59:45.040 --> 00:59:49.240
 Right, it's definitely hard to realize so just I wanted to

00:59:49.240 --> 00:59:52.440
 mention that just simply because obviously we understand the

00:59:52.440 --> 00:59:55.240
 concerns, we're working to address those.

00:59:55.240 --> 00:59:57.540
 We know that we're going to continue to hear concerns in

00:59:57.580 --> 01:00:00.980
 this area, want to take that time to put this as a part of

01:00:00.980 --> 01:00:03.120
 the speed study to see if there's additional improvements

01:00:03.120 --> 01:00:04.180
 that can be made.

01:00:04.180 --> 01:00:08.560
 Also understand that as 35 changes in that area and some of

01:00:08.560 --> 01:00:12.100
 those intersection connections change in that area,

01:00:12.100 --> 01:00:15.900
 it'll also change some of those exit and on ramps.

01:00:15.900 --> 01:00:19.000
 Same, you know, same thing happens as you're trying to

01:00:19.000 --> 01:00:22.440
 leave Dallas Drive to enter 35 in that left lane configuration.

01:00:22.440 --> 01:00:25.600
 I know we also get concerns about that too so just wanted to

01:00:25.640 --> 01:00:27.920
 bring that forward.

01:00:27.920 --> 01:00:30.120
 Talk about the next item.

01:00:30.120 --> 01:00:33.420
 The next item we discussed on our last meeting was the

01:00:33.420 --> 01:00:37.320
 intersection of Parkway Street and then Locust and Elm.

01:00:37.320 --> 01:00:42.660
 I know we mentioned that of course James in the back.

01:00:42.660 --> 01:00:45.260
 James is up there, yes he is, there he is.

01:00:45.260 --> 01:00:48.100
 So James and his staff, I think I mentioned this to you last

01:00:48.100 --> 01:00:50.460
 time, I mean literally on a Thursday night we're out there

01:00:50.460 --> 01:00:54.100
 working to get speed, I mean sorry, stop signs deployed.

01:00:54.140 --> 01:01:00.140
 Obviously as you're traveling southbound on Elm they now have

01:01:00.140 --> 01:01:02.780
 that red flashing light that notifies you of the stop sign

01:01:02.780 --> 01:01:06.380
 in that area and Nathan along with James,

01:01:06.380 --> 01:01:09.420
 those groups have worked together really to talk about

01:01:09.420 --> 01:01:10.560
 what our next steps are.

01:01:10.560 --> 01:01:13.300
 Staff has determined that a roadway diet in this area would

01:01:13.300 --> 01:01:17.820
 be feasible so we're going to be looking at taking Parkway to one

01:01:17.820 --> 01:01:21.200
 lane in each direction with some bike lane that will really take

01:01:21.240 --> 01:01:25.040
 us all the way around to the park to Schmitz I believe is the

01:01:25.040 --> 01:01:29.540
 name of that roadway so really helping with that repurposing of

01:01:29.540 --> 01:01:33.580
 that roadway which will also slow down some of the traffic in

01:01:33.580 --> 01:01:36.740
 that area so just wanted to bring that up.

01:01:36.740 --> 01:01:40.180
 These will be intersection enhancements and really pavement

01:01:40.180 --> 01:01:45.520
 markings and signage so no roadway changes per se besides

01:01:45.520 --> 01:01:49.960
 those frivolous extra things like the markings and the signs

01:01:50.000 --> 01:01:53.400
 so I wanted to bring that up to you.

01:01:53.400 --> 01:01:54.560
 >> Excuse me Becky.

01:01:54.560 --> 01:01:55.640
 >> Yes sir.

01:01:55.640 --> 01:02:01.380
 >> Do you happen to know what is the crash history when it was

01:02:01.380 --> 01:02:06.340
 signalized and then at the various sort of treatments that

01:02:06.340 --> 01:02:10.780
 it's had since at those intersections?

01:02:10.780 --> 01:02:12.680
 >> I do not have that data.

01:02:12.680 --> 01:02:15.480
 I can obviously collect that data.

01:02:15.480 --> 01:02:19.480
 When I became aware of the situation of course the signals

01:02:19.520 --> 01:02:24.120
 were already removed and it was non-signalized and it was just

01:02:24.120 --> 01:02:27.360
 that stop obviously at Parkway as Almond Locust had that full

01:02:27.360 --> 01:02:32.800
 through traffic pattern but with those additional stop signs

01:02:32.800 --> 01:02:35.680
 you know obviously we're still seeing some crashes but I can

01:02:35.680 --> 01:02:42.340
 collect that data based on what recollection and what's in the

01:02:42.340 --> 01:02:46.020
 system from the police department without an issue.

01:02:46.040 --> 01:02:49.980
 >> Yeah, if it's not too difficult I think it would be

01:02:49.980 --> 01:02:53.180
 just good to know what we're aiming for and whether what

01:02:53.180 --> 01:02:56.060
 we're doing is being effective or not.

01:02:56.060 --> 01:02:58.520
 >> Sure and I would just mention and I know I mentioned this

01:02:58.520 --> 01:03:02.300
 again last night you know folks have to get used to the new

01:03:02.300 --> 01:03:05.340
 patterns that's the reason for the flash on the stop sign you

01:03:05.340 --> 01:03:09.900
 know many folks travel that area every single day and it may

01:03:09.900 --> 01:03:13.340
 take them some time to make that muscle memory of that

01:03:13.380 --> 01:03:17.140
 intersection in that area so keep in mind that we have seen

01:03:17.140 --> 01:03:21.880
 some crashes just as we traverse between the transfer of no stop

01:03:21.880 --> 01:03:25.260
 signs as an all-way stop from just a two-way stop so you know

01:03:25.260 --> 01:03:29.360
 we will see some of those types of crashes but we'll work with

01:03:29.360 --> 01:03:32.100
 PD to collect that actual data.

01:03:32.100 --> 01:03:35.840
 I will have to go back and have that data performed just to see

01:03:35.840 --> 01:03:38.940
 when the signal was there and what happened, why it was

01:03:38.940 --> 01:03:42.100
 removed and then work through that process but we can bring

01:03:42.140 --> 01:03:45.080
 that back as an update at next month with that additional

01:03:45.080 --> 01:03:46.600
 information for you.

01:03:46.600 --> 01:03:49.280
 >> I think that'd be great you know and so my expectation would

01:03:49.280 --> 01:03:54.020
 be you know shortly after you make any change there are

01:03:54.020 --> 01:03:57.960
 incidents and then they should go away right.

01:03:57.960 --> 01:04:00.320
 >> Yes, sir that would be our hope.

01:04:00.320 --> 01:04:03.360
 >> Yeah okay that'd be interesting to see thank you.

01:04:03.360 --> 01:04:06.500
 >> No problem sir so the next item that was mentioned at the

01:04:06.500 --> 01:04:09.100
 last meeting just to follow up was the read at the Roodell

01:04:09.140 --> 01:04:12.760
 Street widening concerns obviously in the Friday report

01:04:12.760 --> 01:04:15.840
 on January 14 there was really an update of that didn't basic

01:04:15.840 --> 01:04:18.600
 services center proposal.

01:04:18.600 --> 01:04:22.720
 I wanted to just highlight that one of the focus areas was the

01:04:22.720 --> 01:04:26.480
 Fulton property which was located on Roodell Street and

01:04:26.480 --> 01:04:29.180
 that obviously we're still in preliminary plans of Roodell

01:04:29.180 --> 01:04:33.480
 Street extension and we're working through that 30% design

01:04:33.480 --> 01:04:35.900
 which is completed in that area but working through that final

01:04:35.920 --> 01:04:39.660
 funding before we would move forward with that project really

01:04:39.660 --> 01:04:42.440
 just that that's on hold at this time as we work through those

01:04:42.440 --> 01:04:45.200
 next steps I know there were questions about that particular

01:04:45.200 --> 01:04:49.280
 area and how Roodell and Mingo intersection would traverse

01:04:49.280 --> 01:04:52.200
 through that piece of property so just wanted to refer you back

01:04:52.200 --> 01:04:54.380
 to that Friday report.

01:04:54.380 --> 01:05:01.580
 >> Well if any the question you know that I was present for me

01:05:01.580 --> 01:05:05.360
 was to have a reconcile really just to get a shared point of

01:05:05.380 --> 01:05:12.720
 view from staff between your department and development on

01:05:12.720 --> 01:05:16.160
 whether that project is critically needed or not and

01:05:16.160 --> 01:05:23.000
 I was hearing from Jane who was referenced here that supposedly

01:05:23.000 --> 01:05:28.080
 Ron Mangida has said oh yeah that's not a problem at all so

01:05:28.080 --> 01:05:31.020
 you know a very different point of view so what I'm really

01:05:31.040 --> 01:05:36.880
 looking for was the consensus staff you on the on how

01:05:36.880 --> 01:05:40.320
 compelling the need is for the widening project.

01:05:40.320 --> 01:05:43.760
 >> Yes, sir and I have gone back and discuss with development

01:05:43.760 --> 01:05:45.320
 services and planning department.

01:05:45.320 --> 01:05:47.460
 I'm not sure that the information you received is

01:05:47.460 --> 01:05:51.860
 actually the information that was conveyed and it is a planned

01:05:51.860 --> 01:05:56.200
 capital project that's a part of the overall a CIP and it's a

01:05:56.200 --> 01:06:00.340
 bond project that was put through with the bond program

01:06:00.380 --> 01:06:04.980
 in 2014 and it is anticipated that definitely that's an area

01:06:04.980 --> 01:06:07.980
 in an intersection that needs to be improved at Rue Dell and

01:06:07.980 --> 01:06:11.420
 Mingo and then connect back into the existing roadway

01:06:11.420 --> 01:06:14.120
 infrastructure and that is the location that was currently

01:06:14.120 --> 01:06:19.220
 selected of course if you know council just makes a decision

01:06:19.220 --> 01:06:22.660
 that they no longer believe that that's the the right approach

01:06:22.660 --> 01:06:25.900
 and of course staff will take that information back and

01:06:25.900 --> 01:06:30.100
 receive that determination but I do not believe that the way

01:06:30.140 --> 01:06:33.400
 that that information was conveyed to you was the actual

01:06:33.400 --> 01:06:36.880
 correct way that it was conveyed and it is shown on our mobility

01:06:36.880 --> 01:06:41.180
 plan and it is a approved project to the 29 or 2014 bond

01:06:41.180 --> 01:06:42.520
 program.

01:06:42.520 --> 01:06:45.980
 >> So at some point will there be a discussion of council

01:06:45.980 --> 01:06:50.560
 about the original rationale why it was on the plan and what

01:06:50.560 --> 01:06:54.360
 alternatives would be if we didn't do that or you know I

01:06:54.400 --> 01:07:00.900
 just there's always conflicting needs and we have to weigh how

01:07:00.900 --> 01:07:05.600
 compelling each is right so.

01:07:05.600 --> 01:07:08.380
 >> Sure, yes, sir, I would anticipate that that type of

01:07:08.380 --> 01:07:10.840
 conversation would come up during the tiny home village

01:07:10.840 --> 01:07:14.660
 conversation. I believe that scheduled for council and I'm

01:07:14.660 --> 01:07:18.280
 going off memory for late March.

01:07:18.280 --> 01:07:21.320
 >> So we'll hear the transportation aspect of that at

01:07:21.320 --> 01:07:22.660
 that time whatever that is.

01:07:22.700 --> 01:07:25.460
 >> Yes, there and there will be representatives, I'm sure from

01:07:25.460 --> 01:07:28.700
 all different departments discussing impacts or concerns

01:07:28.700 --> 01:07:32.240
 questions, etc. As those were all listed as a part of that

01:07:32.240 --> 01:07:36.440
 overall RFI you know that was submitted and work through the

01:07:36.440 --> 01:07:39.780
 process so my anticipation is those types of questions would

01:07:39.780 --> 01:07:42.720
 come up during that conversation.

01:07:42.720 --> 01:07:47.820
 >> I'm just just a note we're scheduled to discuss the RFI on

01:07:47.820 --> 01:07:52.080
 April 19th April 19th OK, I'm sorry I was going purely on

01:07:52.120 --> 01:07:55.620
 memory so I appreciate that.

01:07:55.620 --> 01:07:58.800
 I know originally it might have been in March and was moved or

01:07:58.800 --> 01:08:03.100
 okay, so thank you councilmember McGuire I try to keep those

01:08:03.100 --> 01:08:05.640
 dates in my head, but I can't remember everything so I

01:08:05.640 --> 01:08:07.140
 appreciate that.

01:08:07.140 --> 01:08:12.580
 >> Are we too much to keep in your head and how you do it.

01:08:12.580 --> 01:08:16.220
 >> All righty so let's go back to the last part of the staff

01:08:16.240 --> 01:08:22.780
 report which let me see and then I'll share.

01:08:22.780 --> 01:08:26.660
 So that was actually the last item we had on the staff report

01:08:26.660 --> 01:08:34.120
 and so let me go to the second exhibit I'm going to be pulling

01:08:34.120 --> 01:08:40.060
 that up for you and let me share that just so we can.

01:08:40.060 --> 01:08:44.700
 All righty minimize that sorry there's a lot of different

01:08:44.740 --> 01:08:47.800
 screens open, so I'm trying my best to share so I apologize

01:08:47.800 --> 01:08:51.720
 Sir, I know it's it's hard when you're remote to to make sure

01:08:51.720 --> 01:08:55.580
 you're seeing everything so so good.

01:08:55.580 --> 01:08:58.460
 I wanted to make sure so this is our overall staff report that

01:08:58.460 --> 01:09:01.960
 we've really worked through the process on the first item was

01:09:01.960 --> 01:09:05.520
 the construction sequence for Bonnie Bray and plan that plan

01:09:05.520 --> 01:09:07.460
 timing at 35 widening.

01:09:07.460 --> 01:09:11.900
 I do believe that we have you know produce that information

01:09:11.940 --> 01:09:14.740
 for you call me that presentation today there may be a

01:09:14.740 --> 01:09:17.780
 few follow-up questions and what I would recommend is with

01:09:17.780 --> 01:09:20.140
 those follow-up questions we just have that apart as a staff

01:09:20.140 --> 01:09:24.340
 report next month. If you're in concurrence of that.

01:09:24.340 --> 01:09:29.080
 >> I find that me other members any everybody not OK with that

01:09:29.080 --> 01:09:34.180
 they're shaking their heads and giving you a thumbs up so OK.

01:09:34.180 --> 01:09:37.520
 >> As I could not possibly see that yes, Sir, I know I've been

01:09:37.520 --> 01:09:40.660
 on your side presenting and it is definitely difficult to see

01:09:40.700 --> 01:09:45.940
 the Dias or on the paisley Street Roodell intersection

01:09:45.940 --> 01:09:50.240
 questions. You know I think what we would bring back for you is

01:09:50.240 --> 01:09:53.000
 that actual

01:09:53.000 --> 01:09:56.240
 information you requested with the crash data just have that as

01:09:56.240 --> 01:09:59.380
 a part of that staff report.

01:09:59.380 --> 01:10:03.360
 As the I'm sorry that that's specifically related to the item

01:10:03.360 --> 01:10:06.460
 that we just talked about which was Roodell so I'd like to

01:10:06.480 --> 01:10:11.620
 remove that simply because I'm.

01:10:11.620 --> 01:10:13.660
 Well, you know.

01:10:13.660 --> 01:10:17.100
 >> It's because we have a different item so councilmember

01:10:17.100 --> 01:10:20.040
 bird that's the I'm sorry I saw Roodell and I immediately went

01:10:20.040 --> 01:10:23.140
 to that project that's listed for that later in the so my

01:10:23.140 --> 01:10:26.740
 apologies that paisley Street Roodell Street intersection that

01:10:26.740 --> 01:10:30.220
 was the curb project you asked us about that we gave that

01:10:30.220 --> 01:10:33.040
 report on in November.

01:10:33.040 --> 01:10:36.020
 As 17th so we would like to request to remove that unless

01:10:36.060 --> 01:10:42.120
 you have additional questions.

01:10:42.120 --> 01:10:48.760
 >> Your Mike's not on.

01:10:48.760 --> 01:10:58.080
 >> Your Mike's not on councilmember bird.

01:10:58.080 --> 01:11:01.940
 >> They're very difficult today to get.

01:11:01.980 --> 01:11:06.440
 >> They're probably overused from last night.

01:11:06.440 --> 01:11:12.260
 >> I'm sorry paisley Street in Roodell intersection curves.

01:11:12.260 --> 01:11:16.200
 I don't see where they did that could be closed nothing's been

01:11:16.200 --> 01:11:18.060
 done in that area.

01:11:18.060 --> 01:11:21.140
 >> Well, what we were asking is to remove it from the staff

01:11:21.140 --> 01:11:23.660
 agenda because it was something that we discussed with you if

01:11:23.660 --> 01:11:26.740
 you feel like we still need to do some additional information

01:11:26.740 --> 01:11:29.500
 on it and we understood the concerns were working through

01:11:29.540 --> 01:11:32.400
 that with other capital projects that are in that area if

01:11:32.400 --> 01:11:34.440
 there's something that you're asking additional for us to

01:11:34.440 --> 01:11:37.840
 bring back other than what was put in the November a 17th

01:11:37.840 --> 01:11:40.140
 report that we wanted to make sure we brought that back to

01:11:40.140 --> 01:11:42.280
 you if not we'd like to remove it from.

01:11:42.280 --> 01:11:46.480
 >> Yeah, I I just needed some clarification should as to you

01:11:46.480 --> 01:11:51.760
 know why it's being moved so yeah sure yes, yes, ma'am.

01:11:51.760 --> 01:11:54.000
 >> All righty we will remove that from the agenda of course

01:11:54.000 --> 01:11:56.300
 that there's additional questions we're happy to answer

01:11:56.340 --> 01:12:00.260
 those all right now moving on to item number 3 which was the

01:12:00.260 --> 01:12:04.980
 Parkway locust intersection. Mayor protein, I understand

01:12:04.980 --> 01:12:07.540
 you'd like to see some crash data when it was signalized when

01:12:07.540 --> 01:12:10.240
 it was not signalized and then that current condition with

01:12:10.240 --> 01:12:14.220
 some time frames and we'll have to give us how long it's been

01:12:14.220 --> 01:12:17.420
 with the this the 4 way stop condition always stop condition

01:12:17.420 --> 01:12:20.460
 so we will bring that one back to you with that additional

01:12:20.460 --> 01:12:25.460
 crash data. So the the 4th item the speeding concerns along

01:12:25.500 --> 01:12:30.060
 Dallas dry were requesting also to remove that item as it's a

01:12:30.060 --> 01:12:32.440
 part of the citywide speed study and will be further

01:12:32.440 --> 01:12:36.340
 discussed during that August to September time frame.

01:12:36.340 --> 01:12:41.300
 >> Objections.

01:12:41.300 --> 01:12:44.520
 >> And then the final item is the redel Street widening

01:12:44.520 --> 01:12:47.240
 concerns we also are requesting to remove that one from the

01:12:47.240 --> 01:12:51.220
 agenda being that it will be a part of the April 19th tiny home

01:12:51.260 --> 01:12:55.860
 discussion at that time as that's one of the the possible

01:12:55.860 --> 01:12:58.020
 locations and we'll discuss that roadway project at that

01:12:58.020 --> 01:13:00.300
 time.

01:13:00.300 --> 01:13:04.700
 >> Objections I actually kind of do have an objection, I think

01:13:04.700 --> 01:13:10.500
 that we need to have some information.

01:13:10.500 --> 01:13:14.700
 Some more information about that before the April 19th, okay,

01:13:14.700 --> 01:13:18.440
 sure what time information are you requesting I just you know,

01:13:18.480 --> 01:13:23.180
 maybe not not for this committee necessarily, but if you can

01:13:23.180 --> 01:13:26.280
 include in a Friday report prior to April 19th something

01:13:26.280 --> 01:13:32.220
 about you know what what the history of of that project is as

01:13:32.220 --> 01:13:36.900
 far as the bond funding and the design phase that move forward

01:13:36.900 --> 01:13:41.100
 and and where we're at now and you know visuals of what what

01:13:41.100 --> 01:13:44.540
 the proposed alignment is sure just so we can have that

01:13:44.580 --> 01:13:49.520
 information going into the April 19th conversation because

01:13:49.520 --> 01:13:52.420
 you know full disclosure, I I suspect we may need to find a

01:13:52.420 --> 01:13:55.620
 different location for that project but and and so we need

01:13:55.620 --> 01:13:58.680
 to be prepared to have that conversation on April 19th.

01:13:58.680 --> 01:14:01.120
 >> Sure that absolutely we can do that so we'll remove it from

01:14:01.120 --> 01:14:03.460
 this agenda and then we'll include it in a future Friday

01:14:03.460 --> 01:14:06.520
 report and we already have the majority of that information

01:14:06.520 --> 01:14:09.700
 prepared so that's that'll be very simple.

01:14:09.700 --> 01:14:11.640
 >> And I don't know if it's a you know sort of asking too

01:14:11.660 --> 01:14:14.800
 much around the scope or you know, it's just chill till the

01:14:14.800 --> 01:14:21.420
 19th, but the the part I'm most curious about curious about is

01:14:21.420 --> 01:14:28.260
 not so as much the status of the funding planning, but the

01:14:28.260 --> 01:14:33.120
 rationale for the project what what was compelling about it

01:14:33.120 --> 01:14:36.560
 and and what the alternatives.

01:14:36.600 --> 01:14:41.840
 >> Are yet if if any are needed, but like I said that may be

01:14:41.840 --> 01:14:47.500
 coming April 19th, but if you want to you know share any of

01:14:47.500 --> 01:14:51.840
 that least the historical aspect why I was compelling.

01:14:51.840 --> 01:14:55.080
 You know that would be interesting to me.

01:14:55.080 --> 01:14:58.340
 >> But you know I I we certainly will and there's there really

01:14:58.340 --> 01:15:00.380
 is a lot of history to it right because it was part of the

01:15:00.380 --> 01:15:03.580
 2014 bond program we've had funding issues it's been it

01:15:03.620 --> 01:15:07.560
 hasn't been a priority obviously in previous iterations so we

01:15:07.560 --> 01:15:09.760
 have a lot of history so I think we can walk it all the way

01:15:09.760 --> 01:15:12.600
 forward even in more detail of here's here's a rationale when

01:15:12.600 --> 01:15:15.200
 it was approved in 2014 here's been the considerations up to

01:15:15.200 --> 01:15:18.740
 this point and where we stand today, so I think that's a

01:15:18.740 --> 01:15:21.180
 perfectly good exercise for us.

01:15:21.180 --> 01:15:22.880
 >> Okay great.

01:15:22.880 --> 01:15:25.380
 >> I think I'll explain that why behind what you're asking

01:15:25.380 --> 01:15:27.280
 mayor pritam so.

01:15:27.280 --> 01:15:30.540
 >> Super yes, sir. So you're about to ask if people have

01:15:30.580 --> 01:15:34.120
 other items would like to introduce I am good guess,

01:15:34.120 --> 01:15:39.020
 yes, sir, yes, yes, sir, so are there any other items that

01:15:39.020 --> 01:15:41.260
 mobility committee has that they'd like to bring forward for

01:15:41.260 --> 01:15:44.900
 us to discuss at the future meeting.

01:15:44.900 --> 01:15:50.900
 >> It would be there would you would dear would yeah, sure if

01:15:50.900 --> 01:15:54.100
 we could have a conversation about that in the future there

01:15:54.140 --> 01:16:01.140
 would kings row. You know in light of the complications

01:16:01.140 --> 01:16:04.480
 that we're going to be encountering soon.

01:16:04.480 --> 01:16:06.380
 >> That's not a problem.

01:16:06.380 --> 01:16:08.680
 >> And I you know, I think having that discussion prior to

01:16:08.680 --> 01:16:11.220
 that small area plan prioritization will be good too

01:16:11.220 --> 01:16:13.020
 in advance of them.

01:16:13.020 --> 01:16:15.860
 >> Yeah, great.

01:16:15.860 --> 01:16:18.060
 >> Anything else anyone else.

01:16:18.100 --> 01:16:26.300
 >> I just want to make sure that I'm on the right track.

01:16:26.300 --> 01:16:32.040
 >> And also the through through lanes are through

01:16:32.040 --> 01:16:35.620
 neighborhood, the Southeast neighborhood.

01:16:35.620 --> 01:16:39.420
 They were having issues in regards to trucks coming

01:16:39.420 --> 01:16:43.720
 through to get over to business that are over on Duncan Street.

01:16:43.720 --> 01:16:47.360
 Yes, ma'am and they're missing that turn and they're going

01:16:47.400 --> 01:16:50.960
 to have to go back and look for that turn to get over there.

01:16:50.960 --> 01:16:53.940
 So I guess we'll need some kind of update on that.

01:16:53.940 --> 01:16:56.600
 >> Sure we can do that and we have made some modifications in

01:16:56.600 --> 01:16:59.600
 that area, but if we're still receiving the same complaints.

01:16:59.600 --> 01:17:03.420
 We will work with Daniel Kramer screw. So yes, ma'am okay.

01:17:03.420 --> 01:17:08.480
 >> Also I know for sure that a sign needs to be replaced or

01:17:08.480 --> 01:17:12.520
 cleansed. When you make when you're coming up on Dallas

01:17:12.520 --> 01:17:15.720
 Drive and you're going north on Dallas Drive. You make that

01:17:15.760 --> 01:17:21.360
 left turn into Duncan Street and then there's a sign on the

01:17:21.360 --> 01:17:26.240
 side of the road that says Duncan Street and then it says

01:17:26.240 --> 01:17:33.200
 Shady Oaks, Shady Oaks. No way down. And then there's a sign

01:17:33.200 --> 01:17:36.640
 that says Duncan Street right there for you know visitors to

01:17:36.640 --> 01:17:40.040
 make that left turn into Duncan Street. It's just corroded.

01:17:40.040 --> 01:17:43.180
 I don't know. You can't see it. And so maybe that might be

01:17:43.220 --> 01:17:47.080
 when appears to be fairly small where maybe our drivers could

01:17:47.080 --> 01:17:50.420
 actually look to see where Duncan Street is. It might be

01:17:50.420 --> 01:17:51.500
 very helpful.

01:17:51.500 --> 01:17:54.860
 >> Sure, James is here today. I know he's listening. So

01:17:54.860 --> 01:17:57.560
 definitely will will look into that item. That's not a problem.

01:17:57.560 --> 01:18:00.360
 >> All right. Thank you. That's the only thing I have.

01:18:00.360 --> 01:18:05.640
 >> Mayor, kind of a follow on you know, Councilmember Byrd has

01:18:05.640 --> 01:18:09.080
 asked over the months, you know, but different specific

01:18:09.100 --> 01:18:13.240
 streets in Southeast Deton. But then we have this 2 minute

01:18:13.240 --> 01:18:18.760
 pitch from the mayor about how do we look at Southeast Deton

01:18:18.760 --> 01:18:25.000
 speed. And I just that got approved and I'm just curious

01:18:25.000 --> 01:18:28.460
 to know what does that entail then? Is that something

01:18:28.460 --> 01:18:33.060
 different? I mean, is that different from the citywide

01:18:33.060 --> 01:18:37.840
 speed study? What would the next steps be on that?

01:18:37.880 --> 01:18:39.900
 >> Sure, we're currently working through that process

01:18:39.900 --> 01:18:43.980
 with the public works team streets operations, Daniel

01:18:43.980 --> 01:18:47.880
 Kramer and Ethan Cox, general manager, really coordinating

01:18:47.880 --> 01:18:51.060
 that effort. We also want to make mention of those roadways

01:18:51.060 --> 01:18:54.520
 that are going to be a part of the citywide speed study. So

01:18:54.520 --> 01:18:57.220
 that we have that recollection and knowledge to share with

01:18:57.220 --> 01:19:00.120
 y'all of the information that we're going to be collecting in

01:19:00.120 --> 01:19:04.140
 that area. But that is something that's being worked on

01:19:04.140 --> 01:19:06.700
 through that process. So it's something we will have to bring

01:19:06.740 --> 01:19:10.400
 back to you when we're ready. We're not quite ready yet with

01:19:10.400 --> 01:19:13.140
 that level of detail and level of information. We could

01:19:13.140 --> 01:19:15.680
 possibly be ready for the next mobility committee meeting. And

01:19:15.680 --> 01:19:19.880
 if so, we'll bring that forward as an individual item. If not,

01:19:19.880 --> 01:19:22.680
 it would be at one of the following meetings after that

01:19:22.680 --> 01:19:24.060
 timeframe.

01:19:24.060 --> 01:19:26.780
 >> Okay, great. Just so we get, you know, whatever degree of

01:19:26.780 --> 01:19:30.960
 update you're prepared to give, you know, when we get together.

01:19:30.960 --> 01:19:33.300
 >> Yes, sir.

01:19:33.320 --> 01:19:37.340
 >> That's all I've got. So unless there's anything else,

01:19:37.340 --> 01:19:41.000
 last call. We'll go to concluding items. You could

01:19:41.000 --> 01:19:44.240
 make whatever your last thing is that you just thought of a

01:19:44.240 --> 01:19:46.780
 concluding item. Anyone?

01:19:46.780 --> 01:19:49.880
 >> Nothing.

01:19:49.880 --> 01:19:52.880
 >> All right. Thank you, everyone. And Billy, thank you

01:19:52.880 --> 01:19:56.580
 very much for accommodating me being remote.

01:19:56.580 --> 01:19:58.880
 >> Absolutely, sir. Have a nice day.

01:19:58.880 --> 01:19:59.720
 >> Have a good week.

01:19:59.720 --> 01:20:01.160
 >> Bye-bye.

