WEBVTT

00:00:00.000 --> 00:00:09.660
 All right, well, we are here at the Mobility Committee of the City of Denton, Wednesday,

00:00:09.660 --> 00:00:15.920
 January 29th, starting at 10 a.m. We're in the council work session room.

00:00:15.920 --> 00:00:23.000
 It looks like we have a quorum, and so we're going to convene at this regular meeting.

00:00:23.000 --> 00:00:27.600
 Item number one, citizens' comment on agenda items, do we have any kind of citizens' comments

00:00:27.600 --> 00:00:28.600
 or anything?

00:00:28.600 --> 00:00:31.040
 Okay, so we'll move on, no citizens' comment.

00:00:31.040 --> 00:00:40.560
 Move on to item number two, for individual consideration, AMC 25-001, consider approval

00:00:40.560 --> 00:00:43.360
 of the minutes of December the 18th, 2024.

00:00:43.360 --> 00:00:45.360
 How can we get a motion?

00:00:45.360 --> 00:00:48.400
 I move approval of the minutes as submitted.

00:00:48.400 --> 00:00:49.400
 I'll second.

00:00:49.400 --> 00:00:52.000
 All right, are there any decisions?

00:00:52.000 --> 00:00:58.840
 Let's see, everybody's in approval of that, and it stands.

00:00:58.840 --> 00:01:05.300
 So we'll move on to B, AMC 25-002, receive a report and hold a discussion regarding the

00:01:05.300 --> 00:01:09.280
 City of Denton Transportation Mobility Project status report.

00:01:09.280 --> 00:01:10.280
 John.

00:01:10.280 --> 00:01:11.280
 John Poster.

00:01:11.280 --> 00:01:12.280
 Good morning.

00:01:12.280 --> 00:01:13.280
 Good morning.

00:01:13.280 --> 00:01:14.280
 This is John Poster.

00:01:14.280 --> 00:01:15.280
 John Poster, Innovative Transportation Solutions.

00:01:15.280 --> 00:01:24.140
 So we'll go over the meeting, the report today, we've got some updates to give you.

00:01:24.140 --> 00:01:25.920
 Oh, may I interject here?

00:01:25.920 --> 00:01:26.920
 Absolutely.

00:01:26.920 --> 00:01:30.800
 Just remind the community, we're not having these reports every month, they're coming

00:01:30.800 --> 00:01:32.400
 on a quarterly basis now.

00:01:32.400 --> 00:01:33.880
 Is that right?

00:01:33.880 --> 00:01:34.880
 Yes.

00:01:34.880 --> 00:01:37.680
 I show up whenever you tell me to.

00:01:37.680 --> 00:01:38.680
 Okay.

00:01:38.680 --> 00:01:42.120
 Okay, so I'm going to get down a little bit smaller, I think.

00:01:42.120 --> 00:01:43.680
 So we'll just start here.

00:01:43.680 --> 00:01:47.120
 35 North has multiple sections.

00:01:47.120 --> 00:01:52.520
 The thing to note on this today is that the 074, I don't know why that's there.

00:01:52.520 --> 00:01:56.640
 How do you get rid of that?

00:01:56.640 --> 00:01:58.160
 Well, I'll move it up.

00:01:58.160 --> 00:02:06.440
 074 project, which is his yellow job, TechStat is going to be breaking that up into multiple

00:02:06.440 --> 00:02:07.440
 plan sets.

00:02:07.440 --> 00:02:09.440
 It should say that right down here.

00:02:09.440 --> 00:02:11.080
 These are the utilities.

00:02:11.080 --> 00:02:18.200
 So it'll be broken into three different projects, because 074 is over the dollar amount that

00:02:18.200 --> 00:02:19.200
 they like to bid.

00:02:19.200 --> 00:02:23.280
 So they're going to be breaking 074 into three different projects and starting from

00:02:23.280 --> 00:02:28.680
 basically 77, where the merge job ends and start moving north.

00:02:28.680 --> 00:02:34.840
 And so that will delay our ready to let date because of the breakout of the plans for 074

00:02:34.840 --> 00:02:41.000
 to January 26, which is basically four months later than what it was originally.

00:02:41.000 --> 00:02:46.120
 We were in like September 25, which is still in the same fiscal year because their fiscal

00:02:46.120 --> 00:02:48.760
 year started in September and goes through August.

00:02:48.760 --> 00:02:54.000
 So they didn't move it out of that 26 fiscal year.

00:02:54.000 --> 00:02:59.000
 They just moved it from September to January so they can break those projects into three

00:02:59.000 --> 00:03:00.000
 sets.

00:03:00.000 --> 00:03:03.000
 It shouldn't impact anything that y'all are going to see.

00:03:03.000 --> 00:03:04.480
 Go ahead.

00:03:04.480 --> 00:03:08.440
 I had a question.

00:03:08.440 --> 00:03:13.760
 I think you just answered the question, it shouldn't impact, but my question was going

00:03:13.760 --> 00:03:18.080
 to be, is that going to slow down any of the other projects?

00:03:18.080 --> 00:03:23.960
 So if you look at 074, it's $495 million, and anything over 150 has to go through a

00:03:23.960 --> 00:03:25.880
 value engineering.

00:03:25.880 --> 00:03:29.880
 And what's happening is when they get to projects that have these higher dollar amounts, they

00:03:29.880 --> 00:03:34.240
 get fewer bidders, and they don't get as much competition.

00:03:34.240 --> 00:03:39.360
 So when they break them up into smaller projects, they open it up for additional bidders, and

00:03:39.360 --> 00:03:40.360
 they get better prices.

00:03:40.360 --> 00:03:44.520
 Yeah, because I kind of noticed that it was always the same companies on these large--

00:03:44.520 --> 00:03:47.880
 Well, it's always going to be the same companies because there's only so many companies that

00:03:47.880 --> 00:03:48.880
 can do it.

00:03:48.880 --> 00:03:49.880
 Right.

00:03:49.880 --> 00:03:52.440
 For example, on the next project you're going to look at, that was a $555 million project.

00:03:52.440 --> 00:03:57.720
 Text, I got two bidders on that because it was that big, and they said we're not doing

00:03:57.720 --> 00:03:58.720
 that anymore.

00:03:58.720 --> 00:04:00.720
 So they're going to break up these big jobs into smaller ones.

00:04:00.720 --> 00:04:01.720
 Oh, okay.

00:04:01.720 --> 00:04:02.720
 That's interesting.

00:04:02.720 --> 00:04:03.720
 We have a question here.

00:04:03.720 --> 00:04:10.120
 This is a follow-on from Cher's question, and that is that four-month delay is going

00:04:10.120 --> 00:04:12.000
 to be a four-month delay for everything.

00:04:12.000 --> 00:04:14.600
 We're going to expect all the other layouts to--

00:04:14.600 --> 00:04:18.480
 Yeah, so are you doing utility relocations regardless because the utilities are clearing

00:04:18.480 --> 00:04:20.840
 the whole 074 section.

00:04:20.840 --> 00:04:24.600
 How textile lets it is irrelevant to the utility coordination.

00:04:24.600 --> 00:04:29.320
 So those utilities are still moving, and those are-- we're going to be having the plants

00:04:29.320 --> 00:04:31.600
 done during that time that the utilities are relocating.

00:04:31.600 --> 00:04:32.600
 Okay.

00:04:32.600 --> 00:04:33.600
 Okay.

00:04:33.600 --> 00:04:36.920
 So they'll just have a break between each project section.

00:04:36.920 --> 00:04:41.440
 If they're going to do the whole utility coordination, they're going to start south to north.

00:04:41.440 --> 00:04:45.840
 That way, when the south starts, they're already cleared from that section, and we'll just

00:04:45.840 --> 00:04:48.860
 move forward on them as we go north.

00:04:48.860 --> 00:04:51.000
 So utilities are still being moved during that same time.

00:04:51.000 --> 00:04:52.480
 We're not just waiting for the plans.

00:04:52.480 --> 00:04:54.480
 We've still got utilities to move.

00:04:54.480 --> 00:04:55.480
 Yeah.

00:04:55.480 --> 00:04:56.480
 Appreciate that.

00:04:56.480 --> 00:04:57.480
 Thank you.

00:04:57.480 --> 00:04:58.480
 It gets worse.

00:04:58.480 --> 00:05:03.760
 Okay, so those are all the utilities that need to be moved.

00:05:03.760 --> 00:05:07.400
 So the merge, the key right here is it says January 25.

00:05:07.400 --> 00:05:15.640
 This project actually went under-- fully under the knife contractually January 13th.

00:05:15.640 --> 00:05:19.200
 There's still a slight delay because there's a couple of utilities that won't be out of

00:05:19.200 --> 00:05:27.340
 the way until February, but by come summer, this project will be fully engulfed in construction

00:05:27.340 --> 00:05:29.880
 trauma.

00:05:29.880 --> 00:05:30.880
 And it's 56 months.

00:05:30.880 --> 00:05:31.880
 Trauma from your mama.

00:05:31.880 --> 00:05:32.880
 Yeah.

00:05:32.880 --> 00:05:34.880
 I'm not sure I like John's adjectives.

00:05:34.880 --> 00:05:37.480
 Well, you'll see in a second why I'm telling you that.

00:05:37.480 --> 00:05:40.520
 56 months doesn't sound like four and a half years, does it?

00:05:40.520 --> 00:05:41.520
 No.

00:05:41.520 --> 00:05:42.520
 Oh my gosh.

00:05:42.520 --> 00:05:43.520
 It feels more like seven.

00:05:43.520 --> 00:05:44.520
 It's like marriage years.

00:05:44.520 --> 00:05:45.520
 They always seem longer.

00:05:45.520 --> 00:05:46.520
 Marriage years.

00:05:46.520 --> 00:05:47.520
 Doggy.

00:05:47.520 --> 00:05:48.520
 Don't touch that.

00:05:48.520 --> 00:05:51.520
 Gotta go through it to get to it.

00:05:51.520 --> 00:05:52.720
 Hope our watch not watching.

00:05:52.720 --> 00:05:54.640
 So here's why I'm saying this.

00:05:54.640 --> 00:05:55.640
 Mayhill.

00:05:55.640 --> 00:06:02.200
 This is a $139 million job and it takes not just Mayhill, but it does the northbound frontage

00:06:02.200 --> 00:06:05.480
 road all the way to 288 and the bypass is a brinker.

00:06:05.480 --> 00:06:10.080
 So that whole area is going to be under the knife and it lets in June.

00:06:10.080 --> 00:06:15.200
 So by the time the merge is fully engulfed, by the end of the year, you won't be able

00:06:15.200 --> 00:06:18.680
 to escape southward because this will start.

00:06:18.680 --> 00:06:22.160
 And if you're trying to get across the lake going into Louisville, you're going to hit

00:06:22.160 --> 00:06:30.480
 Main Street and we just let the 121 corporate drive this month and that's another 56-month

00:06:30.480 --> 00:06:31.480
 project.

00:06:31.480 --> 00:06:36.600
 So everywhere you go on 35 in Denton County is going to look like we did during the 2012

00:06:36.600 --> 00:06:40.640
 to 2014 timeframe.

00:06:40.640 --> 00:06:47.160
 Well I will say that the Mayhill project has just been great.

00:06:47.160 --> 00:06:48.560
 Absolutely.

00:06:48.560 --> 00:06:54.560
 I have had some concerns and a little pushback about the not being able to make that right

00:06:54.560 --> 00:07:01.380
 turn going over into, you know, and so you know it's just a growing pain.

00:07:01.380 --> 00:07:05.920
 I go there almost every day, twice a day, and I'm fine with it because and that you

00:07:05.920 --> 00:07:09.740
 wouldn't have gotten the money from COG if you hadn't gotten rid of that grade.

00:07:09.740 --> 00:07:13.080
 Well you know and it's just a matter of just getting used to it.

00:07:13.080 --> 00:07:14.080
 Absolutely.

00:07:14.080 --> 00:07:15.080
 Just getting used to it.

00:07:15.080 --> 00:07:20.880
 And I'm communicating that with my constituents over there that have been, you know, upset

00:07:20.880 --> 00:07:21.880
 about it.

00:07:21.880 --> 00:07:22.960
 I don't know the other words.

00:07:22.960 --> 00:07:25.040
 So we can't get out of town is what you're telling.

00:07:25.040 --> 00:07:26.720
 We have to either go to McKinney or Decatur.

00:07:26.720 --> 00:07:30.360
 And you're not going to be able, if we're successful on 35W, you're not going to be

00:07:30.360 --> 00:07:32.320
 able to go down 35W either.

00:07:32.320 --> 00:07:33.320
 Wow.

00:07:33.320 --> 00:07:36.320
 Okay, well it's our turn.

00:07:36.320 --> 00:07:39.600
 I know we're being glib and we're laughing about the upcoming pain.

00:07:39.600 --> 00:07:40.600
 I'm not.

00:07:40.600 --> 00:07:52.320
 My real question is certainly flow is included in forecast planning and not just when the

00:07:52.320 --> 00:07:58.000
 legislature releases the budget so that tech stock can do the projects.

00:07:58.000 --> 00:08:03.120
 So how are we, because we're, at least the three council people, if not the other two

00:08:03.120 --> 00:08:10.680
 mobility commissioners, are going to hear on a weekly, if not daily basis about how

00:08:10.680 --> 00:08:13.760
 they can't move around Denton and the Metroplex?

00:08:13.760 --> 00:08:14.760
 Two points.

00:08:14.760 --> 00:08:16.960
 So help us provide feedback to that.

00:08:16.960 --> 00:08:23.920
 Two points is we know that because of the emerge, the 35W, the frontage roads, May Hill,

00:08:23.920 --> 00:08:30.520
 and then all the trauma in Louisville, that we will have a heightened POI process and

00:08:30.520 --> 00:08:32.120
 we will do more outreach.

00:08:32.120 --> 00:08:38.280
 So similar to what we've done on the design builds project where part of the contract

00:08:38.280 --> 00:08:43.000
 will include public involvement where they go out and outreach and we'll have business

00:08:43.000 --> 00:08:47.040
 outreaches on what's going to impact you in that time frame, how the traffic is going

00:08:47.040 --> 00:08:48.040
 to change.

00:08:48.040 --> 00:08:51.360
 It's a little bit more static and a little bit more predictable because this is a design

00:08:51.360 --> 00:08:56.200
 bid build, which means that all the traffic control has to be approved prior to being

00:08:56.200 --> 00:09:00.440
 implemented, which on a design build, it's called dynamic traffic control, which means

00:09:00.440 --> 00:09:05.080
 they can change it daily if they want, which is why they can get done faster.

00:09:05.080 --> 00:09:10.960
 So we have a, we've been working with the district to bring in a higher level of public

00:09:10.960 --> 00:09:16.440
 involvement where we do geo-fencing around these folks and then send the information

00:09:16.440 --> 00:09:23.400
 out to people and we'll put up a public information website where they can go on and give us their

00:09:23.400 --> 00:09:28.600
 emails and we can send them out daily updates on what's going to happen today and just try

00:09:28.600 --> 00:09:32.360
 to get the information out to them as best we can and keep them informed.

00:09:32.360 --> 00:09:38.280
 Second is we build the roads when the money comes and the money never comes slowly, it

00:09:38.280 --> 00:09:45.300
 comes all at once or it doesn't come at all and this has happened multiple times and we

00:09:45.300 --> 00:09:47.760
 just, we build the roads when we get the money.

00:09:47.760 --> 00:09:52.960
 So there was a period of time, 10 years ago, 15 years ago, where every road in Flower Mound,

00:09:52.960 --> 00:09:59.840
 Allen Village, Bartonville, Double Oak was under the knife and we're talking 30/40, 24/99,

00:09:59.840 --> 00:10:06.840
 three sections of 24/99, two sections of 407 and you just couldn't get out and for seven

00:10:06.840 --> 00:10:07.840
 years it was horrible.

00:10:07.840 --> 00:10:12.560
 There was, at one point, and I do not suggest doing this, where the town of Flower Mound

00:10:12.560 --> 00:10:18.560
 put a sign up at the corner of 407 and 24/99, said if you don't like the way this project's

00:10:18.560 --> 00:10:23.240
 going, call this number and it was Buzz Ellsworth's cell phone number and he was the area engineer

00:10:23.240 --> 00:10:26.240
 so that didn't go over well.

00:10:26.240 --> 00:10:31.400
 I don't think we'll do that to him.

00:10:31.400 --> 00:10:34.200
 So they don't, they don't chime it.

00:10:34.200 --> 00:10:36.520
 These projects are like a racehorse, right?

00:10:36.520 --> 00:10:40.520
 You get seven horses in the block, you don't know who's going to fit across the finish

00:10:40.520 --> 00:10:46.000
 line first, but as they go across the line, they're in the money, you fund them.

00:10:46.000 --> 00:10:51.800
 So the way we did it, these are all going to hit at the same time and they'll all be

00:10:51.800 --> 00:10:53.760
 built at the same time.

00:10:53.760 --> 00:10:55.960
 I appreciate that.

00:10:55.960 --> 00:11:01.160
 I'm going to request that you, when we have these quarterly mobility meetings, but to

00:11:01.160 --> 00:11:08.720
 the extent that staff and/or you, whichever is appropriate, can help us, help you spread

00:11:08.720 --> 00:11:14.620
 the message, it's going to relieve pain on us as we relieve the pain of the citizens.

00:11:14.620 --> 00:11:20.480
 So what we do is, off cycle from meeting with y'all, we still meet with staff monthly and

00:11:20.480 --> 00:11:24.640
 that includes Tech Start district and Ridaway and all those folks.

00:11:24.640 --> 00:11:30.240
 So we're just not getting to the point where we need to flesh out the public involvement

00:11:30.240 --> 00:11:31.240
 side of it.

00:11:31.240 --> 00:11:34.040
 When we're doing the same thing in Rockwell County, they're doing I-30 through, all through

00:11:34.040 --> 00:11:35.040
 Rockwell County.

00:11:35.040 --> 00:11:39.180
 Well Rockwell County's never experienced what they're going through now, which is a full-on

00:11:39.180 --> 00:11:44.940
 interstate reconstruction and they go to Dallas and Dallas is under construction.

00:11:44.940 --> 00:11:52.600
 So we had a high level of public involvement system set up between the Dallas district,

00:11:52.600 --> 00:11:57.960
 the contractor, the county, and the city PIO offices and they meet every two weeks and

00:11:57.960 --> 00:12:04.600
 they've created an email chain where they get out the word, they put it on their PSA

00:12:04.600 --> 00:12:09.080
 saying, "If you want information on this project, send us your email and we'll send out these

00:12:09.080 --> 00:12:11.120
 daily reports."

00:12:11.120 --> 00:12:12.600
 And so it seemed to help.

00:12:12.600 --> 00:12:13.600
 Let me get that out again.

00:12:13.600 --> 00:12:14.600
 No, I appreciate that.

00:12:14.600 --> 00:12:15.600
 It seemed to help.

00:12:15.600 --> 00:12:17.440
 That feedback will help keep tempers down.

00:12:17.440 --> 00:12:18.440
 Yeah.

00:12:18.440 --> 00:12:22.560
 And what are we going to see in 56 months?

00:12:22.560 --> 00:12:25.920
 What are the improvements?

00:12:25.920 --> 00:12:26.920
 Okay.

00:12:26.920 --> 00:12:31.440
 So on the merge, you're going to go from the three lanes that you have, it goes down to

00:12:31.440 --> 00:12:36.200
 two as you're going north, it'll be six lanes all the way through, but from the merge to

00:12:36.200 --> 00:12:42.400
 380, we'll be building the future toll manage lanes in their future existence.

00:12:42.400 --> 00:12:48.760
 So if you know anything about 407 at 35E, that bridge, that's the ultimate bridge and

00:12:48.760 --> 00:12:52.120
 there's that big pavement out in the middle that nobody's using, those will be the toll

00:12:52.120 --> 00:12:53.120
 manage lanes.

00:12:53.120 --> 00:12:58.280
 So we're adding the additional lane in each direction, we're adding two lanes for the

00:12:58.280 --> 00:12:59.280
 ramping.

00:12:59.280 --> 00:13:05.280
 So what happens when you come from 35W to 35, 35 is you go from two lanes to one and

00:13:05.280 --> 00:13:09.200
 then that one lane merges at the same time the frontage road's coming on, and then all

00:13:09.200 --> 00:13:13.640
 those people try to get on the freeway and then off, there'll be braided ramps between

00:13:13.640 --> 00:13:18.080
 the merge and 380, so you can get on and off at the same location.

00:13:18.080 --> 00:13:21.920
 So your exit ramp will be at grade, your on ramp will be over.

00:13:21.920 --> 00:13:27.520
 It's just like if you go down towards Western Center Boulevard on 35W, just north Fort Worth,

00:13:27.520 --> 00:13:28.520
 those are braided ramps.

00:13:28.520 --> 00:13:32.080
 So they're on and off at the same location, they'll happen on both sides, which should

00:13:32.080 --> 00:13:38.680
 reduce the conflict, and then we're going to get through 380 and go all the way to 288,

00:13:38.680 --> 00:13:44.800
 almost 77, and that way you'll be able to flow through.

00:13:44.800 --> 00:13:50.320
 No modification 35W into 35?

00:13:50.320 --> 00:13:56.800
 Yes, that's exactly what we're doing, is that ramping that will come from 35W will have

00:13:56.800 --> 00:14:00.240
 two lanes that go into sort of lane balancing.

00:14:00.240 --> 00:14:05.480
 So you'll still only have 3 lanes, but you'll have 2 lanes of 35W being able to merge into

00:14:05.480 --> 00:14:13.000
 35, because we'll also be taking the on ramp traffic that conflicts right there, a separate

00:14:13.000 --> 00:14:14.000
 structure.

00:14:14.000 --> 00:14:15.000
 I can send you a schematic.

00:14:15.000 --> 00:14:20.360
 It'll go up and over the exit ramp, and then it'll have its own entrance into the main

00:14:20.360 --> 00:14:21.360
 lanes.

00:14:21.360 --> 00:14:22.360
 I would sure like to see that.

00:14:22.360 --> 00:14:23.360
 It's not a problem.

00:14:23.360 --> 00:14:24.360
 Yeah, I would love to have that schematic too.

00:14:24.360 --> 00:14:25.360
 It's not a problem.

00:14:25.360 --> 00:14:28.560
 Will it include the airport road that's going to be here in a slide or two?

00:14:28.560 --> 00:14:34.400
 It will include the access on 1515, it won't include 1515, that's a separate project which

00:14:34.400 --> 00:14:35.400
 you'll see.

00:14:35.400 --> 00:14:38.520
 But where 1515 merges in, it'll include that?

00:14:38.520 --> 00:14:41.040
 Absolutely, we're doing that with the 35 merge job.

00:14:41.040 --> 00:14:45.960
 And so we won't have that left turn at Bonnie Bray anymore?

00:14:45.960 --> 00:14:51.480
 I don't have the schematic memorized, but I can check it, but yes, it was to improve

00:14:51.480 --> 00:14:52.480
 connectivity.

00:14:52.480 --> 00:15:06.560
 Okay, what about the guy on 1515 that wants to go south on 35W, and I don't mean to be

00:15:06.560 --> 00:15:07.560
 skipping ahead.

00:15:07.560 --> 00:15:08.560
 It's okay.

00:15:08.560 --> 00:15:14.880
 That's why they give you this roller ball thing on the, so I don't know if you can see

00:15:14.880 --> 00:15:20.880
 that and I don't know if I can see it, but it ties, it's supposed to be able to tie in

00:15:20.880 --> 00:15:25.160
 so you can come straight across and go right on to Bonnie Bray, similar to what you're

00:15:25.160 --> 00:15:27.880
 doing now, but changing the grade.

00:15:27.880 --> 00:15:32.480
 So it won't impact your access, you'll still have to do the same thing, but we'll go give

00:15:32.480 --> 00:15:35.680
 you the whole schematic for that because I think we did make some improvements to Bonnie

00:15:35.680 --> 00:15:39.420
 Bray, access to the 35 merge in that area as well.

00:15:39.420 --> 00:15:43.760
 So it's been a long time since it's been cleared, I just got to go back and send it to you and

00:15:43.760 --> 00:15:44.760
 let's look at it.

00:15:44.760 --> 00:15:46.760
 We'll get it to Scott and company.

00:15:46.760 --> 00:15:50.800
 That's just a complicated, it's complicated for me and I'm familiar with it.

00:15:50.800 --> 00:15:53.760
 I can't imagine what it must be like for a newcomer.

00:15:53.760 --> 00:15:54.760
 Right.

00:15:54.760 --> 00:15:58.800
 Okay, guys, we need to move on, we just have about another 10 minutes so we can get through

00:15:58.800 --> 00:15:59.800
 the rest of them.

00:15:59.800 --> 00:16:02.140
 Thank you all for that was good.

00:16:02.140 --> 00:16:03.140
 Thank you.

00:16:03.140 --> 00:16:09.000
 Okay, so I think where I was, so we talked about mail, it's going to start in earnest

00:16:09.000 --> 00:16:14.760
 in June and by the end of the year, it'll be fully engulfed as well.

00:16:14.760 --> 00:16:20.200
 Your frontage roads, we are right now, we have 213 million text, Dallas has submitted

00:16:20.200 --> 00:16:25.800
 the remainder of the funding, the Delta, the 200 million or so.

00:16:25.800 --> 00:16:30.980
 They're trying to get that through category 12 funds, which are commissioned.

00:16:30.980 --> 00:16:36.400
 So then go ahead and do the whole 416 million dollar project right now.

00:16:36.400 --> 00:16:41.800
 If they don't succeed, we have at the top project that we first talked to you about

00:16:41.800 --> 00:16:52.400
 the 35 North, we are using this project, the 084 and 116, 084 is in Denton County 116 is

00:16:52.400 --> 00:16:59.920
 in Cook County, but we're using the money in 084, which is 116 million dollars to cover

00:16:59.920 --> 00:17:05.020
 cost overruns or change orders for projects in Denton County.

00:17:05.020 --> 00:17:10.920
 So we're because that part far north where less we lose interest quick, we'll make commission

00:17:10.920 --> 00:17:12.040
 and pay for it.

00:17:12.040 --> 00:17:17.840
 So what we're going to do is if they don't get, if we don't know, if we'll know by August

00:17:17.840 --> 00:17:26.520
 if they got the money in the 26 UTP and as a March 26 ready to let date, so that won't

00:17:26.520 --> 00:17:27.520
 hurt us.

00:17:27.520 --> 00:17:30.640
 If they didn't get the funding, then we're going to take some of that money and we're

00:17:30.640 --> 00:17:37.580
 going to add back in all red because it's not in that plan set right now and apparently

00:17:37.580 --> 00:17:42.520
 developments breaking out all around all red, so we'll put that back into the plans, but

00:17:42.520 --> 00:17:48.040
 we don't want to use our money or the allocated if the commission picks it up.

00:17:48.040 --> 00:17:52.360
 If they don't, then we will, but we're here to tell you that regardless of how it happens,

00:17:52.360 --> 00:17:56.680
 we're putting all red back in to this job.

00:17:56.680 --> 00:18:09.640
 Okay, I have a question for Scott in regards to the new home development out there.

00:18:09.640 --> 00:18:14.520
 These new frontage roads and all of this construction, is that going to be bumping up against each

00:18:14.520 --> 00:18:17.920
 other or does that have anything to do with this?

00:18:17.920 --> 00:18:20.200
 It complements the development that's going to be occurring.

00:18:20.200 --> 00:18:24.680
 Okay, so this is going to happen before the development will get started or they will

00:18:24.680 --> 00:18:25.680
 all be working.

00:18:25.680 --> 00:18:30.800
 It'll be in concert, so the single-family homes won't be impacted by this.

00:18:30.800 --> 00:18:35.680
 Some of the commercial may be, but it's all a benefit and the sooner it happens, the better

00:18:35.680 --> 00:18:38.600
 off for that corner of Robeson 35.

00:18:38.600 --> 00:18:39.600
 Okay, great.

00:18:39.600 --> 00:18:46.280
 On this job, we have all the three parcels acquired, and the three parcels that we don't

00:18:46.280 --> 00:18:53.040
 have acquired are in eminent domain, so everybody knows where the right-of-way is and are being

00:18:53.040 --> 00:18:55.320
 purchased one way or the other.

00:18:55.320 --> 00:19:00.440
 All the developments that are going on in this area are going based on the fact that

00:19:00.440 --> 00:19:04.160
 the right-of-way has been acquired already for this project or they know what needs to

00:19:04.160 --> 00:19:07.080
 be done, and so they're developing accordingly.

00:19:07.080 --> 00:19:08.840
 Okay, thank you.

00:19:08.840 --> 00:19:12.560
 Anybody else have any questions on this one?

00:19:12.560 --> 00:19:13.560
 All right.

00:19:13.560 --> 00:19:18.520
 So, Luke 28 Frontage Roads, basically we're tinkering with the plan set because we're

00:19:18.520 --> 00:19:28.000
 on hold on the right-of-way because TechStot Austin cut the Dallas District's budget, and

00:19:28.000 --> 00:19:35.280
 they reduced it from like $700 million to $300 million, and TechStot Dallas already

00:19:35.280 --> 00:19:40.760
 had about $150 million of projects in eminent domain, and they told them with a penalty

00:19:40.760 --> 00:19:45.320
 of death not to go with their budget, so the Dallas District just put a full stop on right-of-way

00:19:45.320 --> 00:19:52.040
 acquisition until September until they get all these EDs dealt with so they know how

00:19:52.040 --> 00:19:57.640
 much money they have left moving forward, so it's not a big deal because all those projects

00:19:57.640 --> 00:20:00.720
 I just talked to you about that are going to construction, those all have the right-of-way

00:20:00.720 --> 00:20:12.080
 acquired already, but it impacts Luke 28, 1171, 377, 1385, 2931, but not the ones I just

00:20:12.080 --> 00:20:13.080
 talked about.

00:20:13.080 --> 00:20:15.760
 That's disappointing.

00:20:15.760 --> 00:20:16.760
 We're gonna get it fixed.

00:20:16.760 --> 00:20:19.760
 Anybody have any questions about that one?

00:20:19.760 --> 00:20:20.760
 All right.

00:20:20.760 --> 00:20:21.760
 We'll move on.

00:20:21.760 --> 00:20:22.760
 Thank you.

00:20:22.760 --> 00:20:23.760
 So, this is just the Luke 28.

00:20:23.760 --> 00:20:25.640
 We're working on this, the environmental clearance.

00:20:25.640 --> 00:20:32.200
 We're expecting to have a tentative public, see, why does it do that?

00:20:32.200 --> 00:20:36.600
 Public hearing in April, which means that it drives the schedule.

00:20:36.600 --> 00:20:40.120
 Once we do April, we think we're for sure by the end of the year we'll have an environment

00:20:40.120 --> 00:20:43.280
 cleared once it's cleared, it's protected.

00:20:43.280 --> 00:20:51.960
 We don't have to worry about anybody trying to build something on it.

00:20:51.960 --> 00:20:58.800
 We just repaired the sidewalks at the 380 and 288 intersection and a little bit past,

00:20:58.800 --> 00:21:02.860
 right, as part of that whole prior completed project.

00:21:02.860 --> 00:21:08.120
 For this, because of the bypass and the way we have to construct it with the raised grade

00:21:08.120 --> 00:21:12.240
 and everything, are we tearing it out and putting it back in?

00:21:12.240 --> 00:21:13.240
 Is that what's gonna happen?

00:21:13.240 --> 00:21:14.920
 Are you talking about this area right here?

00:21:14.920 --> 00:21:17.640
 What's on 380, the segment on 380?

00:21:17.640 --> 00:21:24.560
 So what's happening is the bypass will be the main lanes going up to 288.

00:21:24.560 --> 00:21:28.560
 The frontage road system will be bifurcated from the main lanes and you'll still want

00:21:28.560 --> 00:21:33.920
 to come to this intersection to go north or south if you need to hit something in this

00:21:33.920 --> 00:21:34.920
 area.

00:21:34.920 --> 00:21:36.920
 So this will stay exactly the way it is.

00:21:36.920 --> 00:21:43.200
 So this project does not anticipate impacting anything in that intersection as is.

00:21:43.200 --> 00:21:47.520
 It's just gonna be the frontage road, the bifurcated frontage road system for the main

00:21:47.520 --> 00:21:49.640
 lanes that go cross country.

00:21:49.640 --> 00:21:50.640
 Okay.

00:21:50.640 --> 00:21:54.840
 I just thought it was just curious because the interface right there and I didn't know

00:21:54.840 --> 00:21:56.320
 if they'd be...

00:21:56.320 --> 00:22:03.200
 That's why we're cutting cross country because there was no way to make a direct connection

00:22:03.200 --> 00:22:09.260
 that close to the intersection on that acute angle.

00:22:09.260 --> 00:22:10.260
 Yeah.

00:22:10.260 --> 00:22:11.260
 I appreciate that.

00:22:11.260 --> 00:22:12.260
 Thank you.

00:22:12.260 --> 00:22:19.600
 Sort of building on what Brian said, I think what he's kind of saying is right there where

00:22:19.600 --> 00:22:25.520
 if somebody's heading westbound on US 380 and then they hit the new roadway or building,

00:22:25.520 --> 00:22:26.880
 yes, right there.

00:22:26.880 --> 00:22:31.920
 So right now there's a pedestrian path between May Hill and the Greenbelt on the north side

00:22:31.920 --> 00:22:34.840
 or it's a bike path and then there's a sidewalk on the south side.

00:22:34.840 --> 00:22:40.080
 So I think what he's asking and what I'm also interested in is will there be either uninterrupted

00:22:40.080 --> 00:22:45.640
 access on the north side for somebody traveling on the side path on the north side along US

00:22:45.640 --> 00:22:51.040
 380 or if there's a detour, is it gonna be super minor or kind of how is that gonna interact?

00:22:51.040 --> 00:22:55.000
 I'll get you the schematic to show you exactly, but we have to accommodate the 10 foot shared

00:22:55.000 --> 00:23:00.680
 use path, whether it's making it go around and under the footing of the bridge or we

00:23:00.680 --> 00:23:05.640
 have the bridge go over it soon enough to minimize impact, but we have to accommodate

00:23:05.640 --> 00:23:06.640
 that.

00:23:06.640 --> 00:23:07.640
 Sure.

00:23:07.640 --> 00:23:08.640
 That's a federal requirement.

00:23:08.640 --> 00:23:10.280
 I think amount of detour is what I'm more interested in.

00:23:10.280 --> 00:23:13.120
 Well, if people like to walk, if they got to walk a little bit farther, I mean, isn't

00:23:13.120 --> 00:23:14.120
 that better for you?

00:23:14.120 --> 00:23:15.120
 Anyway.

00:23:15.120 --> 00:23:16.120
 Well, if it's four or five miles on the road.

00:23:16.120 --> 00:23:17.120
 I don't walk, so I don't know for sure.

00:23:17.120 --> 00:23:18.120
 Yeah, I'd appreciate the schematic of how that's gonna interact.

00:23:18.120 --> 00:23:31.400
 I've got a prenup that precludes elected office.

00:23:31.400 --> 00:23:33.960
 My wife made me sign it.

00:23:33.960 --> 00:23:39.280
 So I'll get the schematic check and show you what it does, but yeah, we have to accommodate

00:23:39.280 --> 00:23:43.100
 the pedestrian amenities.

00:23:43.100 --> 00:23:45.200
 This is just a part of that job.

00:23:45.200 --> 00:23:52.240
 1515, it's basically gonna be ready to let in December, we still gotta come up with 69

00:23:52.240 --> 00:23:53.240
 million bucks.

00:23:53.240 --> 00:23:57.320
 The good news about this project is the district that headquarters isn't running out of money

00:23:57.320 --> 00:24:08.640
 per se on construction, because the 26, 27 biennium will be the second highest construction

00:24:08.640 --> 00:24:11.300
 budget in the history.

00:24:11.300 --> 00:24:14.440
 It's the right away in consultant budgets that are being impacted.

00:24:14.440 --> 00:24:19.360
 So this one's got the right of the acquired, the environmental is done, utilities are moving.

00:24:19.360 --> 00:24:26.520
 So there is a good chance that once we get this ready to let that it will rise to the

00:24:26.520 --> 00:24:34.480
 top for, because this also is one of those things that your previous elected officials

00:24:34.480 --> 00:24:38.880
 have made a tentative commitment to take this off system once it's built.

00:24:38.880 --> 00:24:43.600
 So it would stop being 1515 and just go back to airport road that way you can control it

00:24:43.600 --> 00:24:45.360
 a little bit better.

00:24:45.360 --> 00:24:52.720
 But you'd get a brand new six lane divided concrete, you know, 30 year road.

00:24:52.720 --> 00:25:02.480
 The narrow blue line, oh, I'm sorry, that's indicating in the project.

00:25:02.480 --> 00:25:09.080
 I'm concerned, I'm on 1515 and I want to go to Fort Worth, how do I do that?

00:25:09.080 --> 00:25:12.440
 Well, you go up and you see right, I don't have to show you, I'm gonna show you, it's

00:25:12.440 --> 00:25:13.440
 right there.

00:25:13.440 --> 00:25:17.480
 So you come up, you make that turn and you run the frontage road and you get on somewhere

00:25:17.480 --> 00:25:18.480
 down here.

00:25:18.480 --> 00:25:19.960
 So there's gonna be a way?

00:25:19.960 --> 00:25:20.960
 Absolutely.

00:25:20.960 --> 00:25:23.200
 Because there's not a way now.

00:25:23.200 --> 00:25:24.200
 Well there is a way.

00:25:24.200 --> 00:25:25.200
 It's just the other way around.

00:25:25.200 --> 00:25:26.200
 You got to go.

00:25:26.200 --> 00:25:27.200
 You got to go around.

00:25:27.200 --> 00:25:28.200
 Yeah.

00:25:28.200 --> 00:25:29.200
 Well, I mean, literally, there's a way.

00:25:29.200 --> 00:25:30.200
 It's just not a good way.

00:25:30.200 --> 00:25:31.200
 Right.

00:25:31.200 --> 00:25:34.200
 Well, I don't have an answer to that.

00:25:34.200 --> 00:25:38.800
 No, no answer, don't try.

00:25:38.800 --> 00:25:44.520
 Okay, we have a question over here.

00:25:44.520 --> 00:25:45.520
 Just a quick clarification.

00:25:45.520 --> 00:25:49.040
 So when you say a 30 year road, you're just referring to the idea that this road would

00:25:49.040 --> 00:25:52.480
 have an expected lifespan of 30 years after initial construction?

00:25:52.480 --> 00:25:56.720
 The state builds a road that has, I don't know what y'all's design standards are, but

00:25:56.720 --> 00:26:02.480
 when the state builds a foreign to market, it's supposed to carry 56,000 pounds plus.

00:26:02.480 --> 00:26:08.520
 And so they'll have six, eight inches of subgrade, four or five inches, Trevor could probably

00:26:08.520 --> 00:26:12.920
 give it very clearly, sometimes as much as 10 inches being on the soil of an asphalt

00:26:12.920 --> 00:26:13.920
 base.

00:26:13.920 --> 00:26:18.440
 And then they'll put 10, 12 inches of concrete that's continuously enforced with rebar.

00:26:18.440 --> 00:26:24.280
 So it's not the kind of road that a city builds, it's a state facility and they don't like

00:26:24.280 --> 00:26:26.320
 to go back and repair them.

00:26:26.320 --> 00:26:30.200
 So they build them for a long life cycle.

00:26:30.200 --> 00:26:32.840
 All right, thank you.

00:26:32.840 --> 00:26:37.880
 It's the pavement design that makes them last.

00:26:37.880 --> 00:26:44.240
 1173, I mean, again, we've got the right of way already acquired, so this one isn't impacted

00:26:44.240 --> 00:26:45.600
 by anything but money.

00:26:45.600 --> 00:26:50.640
 Again, we think that by the time we get this ready to let with the fact that they still

00:26:50.640 --> 00:26:54.480
 have construction money, we'll have a good chance of getting this road funded during

00:26:54.480 --> 00:26:56.680
 that 26, 27 UTP period.

00:26:56.680 --> 00:27:03.120
 Outer loop, does anybody want to talk about the outer loop, nothing's really going on?

00:27:03.120 --> 00:27:10.280
 We had our series of stakeholder meetings back in October and November, and we are analyzing

00:27:10.280 --> 00:27:11.280
 those comments.

00:27:11.280 --> 00:27:15.560
 And then once we get them back, LJ will come back to the county and the state, show them

00:27:15.560 --> 00:27:20.580
 the comments, and then we'll come back to you all and show you what we heard.

00:27:20.580 --> 00:27:26.800
 And then there's a test on the acronym, it's open book.

00:27:26.800 --> 00:27:28.120
 I was looking forward to a test.

00:27:28.120 --> 00:27:34.920
 We had those ABCD subjects, and I know that the implication of your statement a second

00:27:34.920 --> 00:27:41.200
 ago was we're waiting to figure out what the final alignments of A versus B and C versus

00:27:41.200 --> 00:27:49.880
 D. You sense which way they're leaning, whether it's Rector or Ganzer or any of the others.

00:27:49.880 --> 00:27:53.800
 I can tell you, the technically preferred, I got a second question.

00:27:53.800 --> 00:27:58.280
 The technically preferred alternative is the alternative that ends at Milam.

00:27:58.280 --> 00:28:00.040
 That's the technically preferred.

00:28:00.040 --> 00:28:04.160
 But since this is an EIS, an environmental impact statement, which is the highest level,

00:28:04.160 --> 00:28:10.040
 we have to take two viable alternatives all the way through the EIS process.

00:28:10.040 --> 00:28:17.480
 So even though we don't think Rector is technically preferred, we have to go through it because

00:28:17.480 --> 00:28:24.440
 there may be an environmental reason why Rector is more viable than Milam.

00:28:24.440 --> 00:28:27.440
 So on an environmental assessment, I call these others.

00:28:27.440 --> 00:28:30.840
 What you do is you find out which is the technically preferred, you try to get it also to be the

00:28:30.840 --> 00:28:31.840
 locally preferred.

00:28:31.840 --> 00:28:35.100
 And if you get an alignment that's locally and technically preferred, then that's the

00:28:35.100 --> 00:28:36.100
 only one you clear.

00:28:36.100 --> 00:28:40.080
 And the rest of them you dismiss because of random reasons, whether it's environmental

00:28:40.080 --> 00:28:42.620
 or local government, opposition.

00:28:42.620 --> 00:28:45.680
 But in an EIS, you got to take two through the entire process.

00:28:45.680 --> 00:28:48.280
 Okay.

00:28:48.280 --> 00:28:54.640
 So we started at 78 alignments, and we got them down to four.

00:28:54.640 --> 00:28:57.280
 So I appreciate the filtering that's gone on.

00:28:57.280 --> 00:29:02.640
 And well, I mean, it's just obvious, like, you know, Rector affects Sanger and Milam

00:29:02.640 --> 00:29:03.640
 affects us.

00:29:03.640 --> 00:29:10.720
 Well, your thoroughfare plan shows the outer loop on Milam, which is part of the environmental

00:29:10.720 --> 00:29:13.560
 process is called community cohesion.

00:29:13.560 --> 00:29:19.520
 So to the extent possible, we had to try to follow your thoroughfare plan.

00:29:19.520 --> 00:29:24.680
 So the county thoroughfare plan, city thoroughfare plan, city Aubrey's thoroughfare plan, pilot

00:29:24.680 --> 00:29:31.560
 points, Salinas, Collin counties, all points to the technically preferred alignment.

00:29:31.560 --> 00:29:36.400
 But just because it's there doesn't mean we can't have to, we don't have to look at, and

00:29:36.400 --> 00:29:39.960
 there's actually three alternatives, two viable and then the no build.

00:29:39.960 --> 00:29:44.080
 And the no build is if you get through all the process, it's either too environmentally

00:29:44.080 --> 00:29:51.920
 impactive, or it doesn't fulfill the purpose and need of the document that was you set

00:29:51.920 --> 00:29:54.920
 as the need at the very beginning of the process.

00:29:54.920 --> 00:29:55.920
 Sure.

00:29:55.920 --> 00:30:00.280
 And then my second question was, and we have that lockdown section from the core at the

00:30:00.280 --> 00:30:06.080
 trestle bridge, but there was some confusion in our last meeting, I've had some more discussions

00:30:06.080 --> 00:30:11.680
 with various state stakeholders where I'm not clear, so I'm hoping maybe you can clear.

00:30:11.680 --> 00:30:16.600
 I thought THC didn't like us to move the trestle bridge and there'd been some discussion about

00:30:16.600 --> 00:30:22.400
 moving the trestle bridge to allow for better right of way development there over that fixed

00:30:22.400 --> 00:30:23.400
 segment.

00:30:23.400 --> 00:30:24.400
 Do we have any clarity on that?

00:30:24.400 --> 00:30:29.240
 So yes, we've got two approaches.

00:30:29.240 --> 00:30:38.020
 One is propose a deck scenario that stays within the core of engineers footprint and

00:30:38.020 --> 00:30:41.400
 doesn't impact the trestle bridge.

00:30:41.400 --> 00:30:47.040
 Get the project cleared, be able to move forward with the rest of the project, come back after

00:30:47.040 --> 00:30:51.880
 it's cleared and go fight the fight with the core, because you can beat the core of engineers,

00:30:51.880 --> 00:30:54.440
 it just takes time and money.

00:30:54.440 --> 00:31:01.320
 But if we want to get the rest of the corridor fixed, we may end up just surrendering the

00:31:01.320 --> 00:31:08.080
 fight now, staying within the footprint, clearing all of it, and then come back and do a separate

00:31:08.080 --> 00:31:10.440
 environmental document for that area.

00:31:10.440 --> 00:31:17.840
 Now the core of engineers will let you go to a wider footprint, and they are less interested

00:31:17.840 --> 00:31:27.060
 in that trestle bridge than the Texas Parks and Wildlife guys are, and the core supersedes.

00:31:27.060 --> 00:31:32.320
 So we're going to try to accommodate it, but what we can't do is have a two billion dollar

00:31:32.320 --> 00:31:39.800
 road that's supposed to be a part of a five county outer loop restricted for future growth

00:31:39.800 --> 00:31:44.760
 for a half a mile where there's no development.

00:31:44.760 --> 00:31:48.280
 And what happens is to stack it, you put the frontage roads on the bottom and the main

00:31:48.280 --> 00:31:54.520
 lanes on top, if at any point there's an accident under, and there's a fire, the whole thing

00:31:54.520 --> 00:31:55.620
 shut down.

00:31:55.620 --> 00:32:07.920
 So it doesn't have, what is it, redundancy, and it doesn't have future operability if

00:32:07.920 --> 00:32:08.920
 we do that.

00:32:08.920 --> 00:32:10.280
 So that's one.

00:32:10.280 --> 00:32:16.180
 The second is, Congress has given us 50 million dollars to do that crossing.

00:32:16.180 --> 00:32:23.900
 And so part of that is we're also partnering with the core of engineers to do that storm

00:32:23.900 --> 00:32:30.400
 water, transportation storm water initiative, where everywhere this road, this 23 mile dam

00:32:30.400 --> 00:32:37.360
 impacts any kind of waterway, we're going to go and buy flood rights north of that,

00:32:37.360 --> 00:32:43.760
 and we are going to impound the water, and not impound it like slowly release it down

00:32:43.760 --> 00:32:44.760
 the river.

00:32:44.760 --> 00:32:50.800
 We're going to impound it, make it an aesthetic situation, and then use those impounded waters

00:32:50.800 --> 00:32:56.000
 to find a way to do best management practices to push the water down into the aquifer to

00:32:56.000 --> 00:32:57.280
 recharge the aquifer.

00:32:57.280 --> 00:33:00.120
 And so the core wants that too.

00:33:00.120 --> 00:33:05.240
 So we figure at some point the core is going to agree to what we want to do because we're

00:33:05.240 --> 00:33:08.600
 giving them something they want and it's just going to cost us a lot of money.

00:33:08.600 --> 00:33:13.620
 And right now we don't have any of the money other than the 50 million for fixing the problem

00:33:13.620 --> 00:33:14.880
 at the crossing.

00:33:14.880 --> 00:33:22.560
 So we're going to pan that out, and if we think that we can't get it vetted soon, we'll

00:33:22.560 --> 00:33:30.720
 dip, do the deck, clear the project, and then come back and give us time to do the right

00:33:30.720 --> 00:33:31.720
 thing there.

00:33:31.720 --> 00:33:36.200
 I appreciate that, something else, and this will be like, I'm just going to whisper in

00:33:36.200 --> 00:33:43.960
 the ears of local staff, I know that parks is responsible for some of the leases from

00:33:43.960 --> 00:33:44.960
 the core.

00:33:44.960 --> 00:33:50.280
 So the city of Denton leases some of it to Texas Parks and Wildlife, and Texas Parks

00:33:50.280 --> 00:33:54.200
 and Wildlife leases some of that core land for the Green Belt directly.

00:33:54.200 --> 00:34:01.320
 And so I don't know how that mixture of leases back to Texas Parks and Wildlife now affects

00:34:01.320 --> 00:34:06.960
 TxDOT and this whole process, so at some point, if there's some clarity, I would love to have

00:34:06.960 --> 00:34:07.960
 some clarity.

00:34:07.960 --> 00:34:12.840
 So we have to honor any contracts that the core has in that area.

00:34:12.840 --> 00:34:19.720
 So like when we were widening 2499 across the lake, or when we did Lake Lewisville-Towbridge,

00:34:19.720 --> 00:34:25.100
 there were parks in those areas that Highland Village or Little Lamb or Lakewood Village

00:34:25.100 --> 00:34:28.080
 had, and they had rights, right?

00:34:28.080 --> 00:34:34.260
 And then there's that yacht club north of the Lake Lewisville-Towbridge, they had rights,

00:34:34.260 --> 00:34:38.800
 so that's why you had that big arch in the middle of the lake, so that those guys didn't

00:34:38.800 --> 00:34:44.520
 have to lower their mast to go under the, so we just spent $50 million on that.

00:34:44.520 --> 00:34:49.180
 I just paid them to cut the mast off.

00:34:49.180 --> 00:34:53.260
 So all the contracts that are currently out there, we have to honor.

00:34:53.260 --> 00:34:56.560
 So that's part of the cost.

00:34:56.560 --> 00:35:00.360
 The core language is surrender early and pay what they ask.

00:35:00.360 --> 00:35:01.360
 So that's what we're going to do.

00:35:01.360 --> 00:35:02.360
 >> All right, I appreciate it.

00:35:02.360 --> 00:35:03.360
 Thanks, John.

00:35:03.360 --> 00:35:04.360
 >> Okay.

00:35:04.360 --> 00:35:05.360
 >> And that's it.

00:35:05.360 --> 00:35:09.220
 >> All right, well, Ben, I have just been full of game one knowledge today.

00:35:09.220 --> 00:35:12.160
 Thank you very much for your services, and we appreciate you coming through.

00:35:12.160 --> 00:35:13.700
 >> It's all going to change like in two weeks.

00:35:13.700 --> 00:35:14.700
 I just don't know how.

00:35:14.700 --> 00:35:15.700
 >> Okay.

00:35:15.700 --> 00:35:18.400
 Well, we'll look forward to seeing you in a few months.

00:35:18.400 --> 00:35:19.400
 >> Thank you.

00:35:19.400 --> 00:35:26.360
 >> We're going to move on to items D. We are going to skip C. It has been pulled.

00:35:26.360 --> 00:35:39.240
 But we're going to go ahead and go to D. MC 25-004, staff memorandum, the 2019 bond program,

00:35:39.240 --> 00:35:57.000
 UPRR agreement, Bush Creek.

00:35:57.000 --> 00:35:58.840
 >> Trevor Crane, director of capital projects.

00:35:58.840 --> 00:36:02.480
 These came up from some questions that were brought up last time.

00:36:02.480 --> 00:36:04.380
 Staff provided response to those.

00:36:04.380 --> 00:36:09.040
 So really, just if you all have any additional questions that we can answer at this time,

00:36:09.040 --> 00:36:12.600
 myself and some other staff are here.

00:36:12.600 --> 00:36:16.400
 >> Well, I'm just pleased to see that Janie Street is part of a project now.

00:36:16.400 --> 00:36:17.400
 >> Yes, ma'am.

00:36:17.400 --> 00:36:22.320
 >> And they're going to be happy about that in that neighborhood.

00:36:22.320 --> 00:36:23.320
 Anybody else have any questions?

00:36:23.320 --> 00:36:24.320
 Let's start down.

00:36:24.320 --> 00:36:27.640
 Okay, let's start down here this time.

00:36:27.640 --> 00:36:32.760
 >> So when it comes to hawk beacons and other crosswalks, I just had some questions about

00:36:32.760 --> 00:36:39.120
 the city's approach to determining where those should be installed.

00:36:39.120 --> 00:36:43.720
 Is this engineer's best judgment is kind of the approach that we take or are we looking

00:36:43.720 --> 00:36:45.800
 at warrants for these?

00:36:45.800 --> 00:36:50.800
 >> Good morning, chair and commissioners, Chandra with transportation services.

00:36:50.800 --> 00:36:56.960
 So when we consider pedestrian hybrid beacons, it's a combination of a number of crosses

00:36:56.960 --> 00:37:03.880
 at pedestrians or bikes that crossing their roadway, and there is no set metrics.

00:37:03.880 --> 00:37:10.880
 Like Tony, Tony is a rule of thumb when Tony pedestrians cross in one peak hour.

00:37:10.880 --> 00:37:13.600
 That is one consideration.

00:37:13.600 --> 00:37:18.440
 In absence of pedestrians, but if there is any fatalities or near misses or if there

00:37:18.440 --> 00:37:22.640
 is serious injuries in a location, that is a factor as well.

00:37:22.640 --> 00:37:29.880
 And also we need to consider the cost of building these on roadways which would be $150,000

00:37:29.880 --> 00:37:35.480
 to $200,000 per location.

00:37:35.480 --> 00:37:40.320
 >> So you said 20 crossings in a peak hour.

00:37:40.320 --> 00:37:43.560
 I guess how do you just determine the study area for that, right?

00:37:43.560 --> 00:37:55.080
 So there's like the parking lot kind of opposite east side on the south side of Oak Street.

00:37:55.080 --> 00:38:00.560
 If I'm crossing at like one end of that parking lot on the east end of that parking lot and

00:38:00.560 --> 00:38:03.880
 then somebody else is crossing on the south end of that parking lot and somebody is crossing

00:38:03.880 --> 00:38:07.840
 at that Austin street intersection, does that all get grouped into one crossing area?

00:38:07.840 --> 00:38:08.840
 >> Yes.

00:38:08.840 --> 00:38:14.320
 When there is a request comes in, we usually go and count and make observations and make

00:38:14.320 --> 00:38:18.280
 the determination if it's needed to be funneled into all into one crossing.

00:38:18.280 --> 00:38:19.280
 >> Okay.

00:38:19.280 --> 00:38:20.280
 Thank you.

00:38:20.280 --> 00:38:21.280
 >> Okay.

00:38:21.280 --> 00:38:22.280
 Yes, sir.

00:38:22.280 --> 00:38:23.680
 >> I'm just going to pick it immediately from there.

00:38:23.680 --> 00:38:29.480
 So it's all intersection and mid-block crossings that count to the 20?

00:38:29.480 --> 00:38:33.720
 >> It's mostly -- it's -- PHBs are used at mid-block crossings.

00:38:33.720 --> 00:38:34.720
 >> Right.

00:38:34.720 --> 00:38:38.920
 >> But in terms of volume and the reason -- I'll put context on my question.

00:38:38.920 --> 00:38:52.260
 If you are having people jaywalk, then they're crossing against the guidance of the layout.

00:38:52.260 --> 00:38:54.560
 So how do you determine that?

00:38:54.560 --> 00:38:59.640
 Because if you had a controlled crossing, they would cross it there.

00:38:59.640 --> 00:39:04.920
 So the flow is obviously directing them away from the region, but their desire flow is

00:39:04.920 --> 00:39:06.680
 to the mid-block crossing.

00:39:06.680 --> 00:39:12.200
 So how do we determine 20 -- and I know you're not being hard and fast on the 20, but how

00:39:12.200 --> 00:39:17.000
 do we determine that volume of need is, I guess, my question.

00:39:17.000 --> 00:39:21.520
 >> So if there is a crossing, we only consider max of 300 feet.

00:39:21.520 --> 00:39:26.420
 Beyond 300 feet, even if you provide an intersection with signals, people would be just not cross

00:39:26.420 --> 00:39:30.240
 it there, they would cross wherever they feel convenient.

00:39:30.240 --> 00:39:35.240
 So anything that is within the 300 feet is where we consider -- if you provide one, they

00:39:35.240 --> 00:39:39.640
 will be utilizing that crossing.

00:39:39.640 --> 00:39:43.840
 >> Okay.

00:39:43.840 --> 00:39:50.920
 Do we have a current plan for when we're going to put PHBs and how we're going to deploy

00:39:50.920 --> 00:39:58.360
 them across the city and then sort of secondarily have a citizen request those in the best way

00:39:58.360 --> 00:39:59.360
 possible?

00:39:59.360 --> 00:40:04.960
 >> So there are not only PHBs, there are other like RRPs or even LED lights that we could

00:40:04.960 --> 00:40:05.960
 consider.

00:40:05.960 --> 00:40:11.060
 Based on the request, we make the judgment because it's not only we plan, we need to

00:40:11.060 --> 00:40:15.240
 have funds to implement those.

00:40:15.240 --> 00:40:21.200
 So it's a combination of need and whether we have the funds to build those.

00:40:21.200 --> 00:40:26.280
 >> But I guess I meant that more in terms of what's our current anticipated rollout

00:40:26.280 --> 00:40:27.280
 of PHBs?

00:40:27.280 --> 00:40:30.720
 >> We are studying four locations right now.

00:40:30.720 --> 00:40:38.560
 McKinney Street at Jenin, McKinney at Mack Park, and there are other two locations across

00:40:38.560 --> 00:40:45.920
 South Lake Park, so there is one other location, so we are evaluating it, and based on funds

00:40:45.920 --> 00:40:49.920
 available, we would be able to build it.

00:40:49.920 --> 00:40:54.240
 >> And is there a preferred way -- like I know like obviously Anderson's is very interested

00:40:54.240 --> 00:41:01.480
 in PHB, and there's been various requests for PHBs along 288, especially near the shelter

00:41:01.480 --> 00:41:03.880
 and Serve Denton and things like that.

00:41:03.880 --> 00:41:11.720
 So how -- I mean, you don't have to necessarily answer today unless it's a short answer, but

00:41:11.720 --> 00:41:19.880
 there is desire in the community for additional PHBs around, you know, high-trafficked, high-volume

00:41:19.880 --> 00:41:24.440
 variant, and a way of requesting that would be really great.

00:41:24.440 --> 00:41:25.440
 >> Sure.

00:41:25.440 --> 00:41:27.600
 It's either Engage Renton or you could send it to us.

00:41:27.600 --> 00:41:31.240
 We will evaluate and make the determination.

00:41:31.240 --> 00:41:34.160
 >> Hi, Chandra.

00:41:34.160 --> 00:41:39.760
 So you sort of hit on it, and so did committee member Bray.

00:41:39.760 --> 00:41:41.960
 We said 20 pedestrians at peak hour.

00:41:41.960 --> 00:41:43.720
 Is this a should or a shall?

00:41:43.720 --> 00:41:44.720
 You said guideline.

00:41:44.720 --> 00:41:45.720
 >> Yeah.

00:41:45.720 --> 00:41:48.720
 It's neither.

00:41:48.720 --> 00:41:53.720
 Tech Start uses the rule of thumb as a minimum Tony, but if there is an accident prone and

00:41:53.720 --> 00:42:01.120
 there is no Tony process, then we could -- it gives more authority for the traffic engineer

00:42:01.120 --> 00:42:02.120
 to make the call.

00:42:02.120 --> 00:42:03.120
 >> Okay.

00:42:03.120 --> 00:42:04.120
 So just a guideline.

00:42:04.120 --> 00:42:05.120
 >> Yeah.

00:42:05.120 --> 00:42:08.480
 >> And then to make sure I got this right, you said the general cost is 150 to 250?

00:42:08.480 --> 00:42:09.680
 Was that the upper level?

00:42:09.680 --> 00:42:14.280
 >> It ranges, say, if you're building on a two-lane roadway, the steel equipment, you

00:42:14.280 --> 00:42:19.000
 don't need a longer mast arms, but if you're building across a six-lane facility, the cost

00:42:19.000 --> 00:42:20.000
 would go up.

00:42:20.000 --> 00:42:21.000
 >> Was it 250?

00:42:21.000 --> 00:42:22.000
 Was that the upper --

00:42:22.000 --> 00:42:23.000
 >> 250, yeah, max.

00:42:23.000 --> 00:42:27.480
 >> And then how does that compare to the cost of a typical intersection signal?

00:42:27.480 --> 00:42:32.120
 >> Like signal, lately we are getting quote around $700,000 to $800,000 per location.

00:42:32.120 --> 00:42:33.120
 >> All right.

00:42:33.120 --> 00:42:34.120
 That's all I had.

00:42:34.120 --> 00:42:35.120
 Thank you.

00:42:35.120 --> 00:42:36.120
 >> Sure.

00:42:36.120 --> 00:42:37.120
 >> Okay.

00:42:37.120 --> 00:42:38.120
 We have one more question here.

00:42:38.120 --> 00:42:39.120
 >> You said four PHBs are pending.

00:42:39.120 --> 00:42:40.120
 Two McKinney, one on Tuesday.

00:42:40.120 --> 00:42:41.120
 What was the fourth one?

00:42:41.120 --> 00:42:48.920
 >> We have -- I have -- I don't have the location, but I can find out and let you know.

00:42:48.920 --> 00:42:49.920
 >> Okay.

00:42:49.920 --> 00:42:50.920
 >> But yes, evaluate it.

00:42:50.920 --> 00:42:51.920
 >> That's why I didn't hear it.

00:42:51.920 --> 00:42:52.920
 Okay.

00:42:52.920 --> 00:42:53.920
 >> McKinney is disciplining it.

00:42:53.920 --> 00:42:54.920
 Yes.

00:42:54.920 --> 00:42:57.200
 >> I just want to provide one point of clarity.

00:42:57.200 --> 00:43:00.520
 When Chandra is speaking, he's speaking to city-controlled streets.

00:43:00.520 --> 00:43:05.240
 Keep in mind, tech-stock-controlled roadways, their standards are much stricter.

00:43:05.240 --> 00:43:08.960
 And the second piece to that is that we're limited on funding.

00:43:08.960 --> 00:43:13.560
 So again, he's doing a lot of evaluation, but it's not as if we're going to be putting

00:43:13.560 --> 00:43:14.560
 these everywhere.

00:43:14.560 --> 00:43:15.560
 So just --

00:43:15.560 --> 00:43:20.560
 >> Sounds like we're going to have to meet another bond.

00:43:20.560 --> 00:43:21.640
 Yes.

00:43:21.640 --> 00:43:27.160
 >> Just in terms of things that go beyond kind of a standard zebra crossing, I would

00:43:27.160 --> 00:43:30.960
 -- I was driving down Newton at Moore Street by Rivera today, and I noticed -- and I don't

00:43:30.960 --> 00:43:34.560
 know if this is intentional or if this is just a quirk of the way that the road is settled,

00:43:34.560 --> 00:43:38.240
 but there is a slightly actually elevated crosswalk there.

00:43:38.240 --> 00:43:42.400
 So I thought that was great, and I'm always open to seeing more of those around town.

00:43:42.400 --> 00:43:43.400
 >> Sure.

00:43:43.400 --> 00:43:46.480
 I haven't seen it, but I will take a look at it and circle back.

00:43:46.480 --> 00:43:47.480
 >> Elevated crosswalk.

00:43:47.480 --> 00:43:50.600
 >> I'd be happy to show you after the meeting on collapse.

00:43:50.600 --> 00:43:51.600
 >> Okay.

00:43:51.600 --> 00:43:52.600
 >> Okay.

00:43:52.600 --> 00:43:53.600
 >> I have one more question on the next item.

00:43:53.600 --> 00:43:54.760
 >> Oh, okay.

00:43:54.760 --> 00:43:59.160
 >> The next item, the UPR agreement.

00:43:59.160 --> 00:44:00.160
 Rush Creek crossing.

00:44:00.160 --> 00:44:04.400
 Can you scroll that up a little bit?

00:44:04.400 --> 00:44:05.400
 That right there.

00:44:05.400 --> 00:44:06.400
 Yes.

00:44:06.400 --> 00:44:07.400
 You had a question?

00:44:07.400 --> 00:44:08.400
 >> Yeah.

00:44:08.400 --> 00:44:14.120
 No, I know generally we're looking for a 90-degree crossing in crossings in general as a principle,

00:44:14.120 --> 00:44:23.320
 but given the layout of Bonnie Brade Parvin, that region, like I'm having trouble visualizing

00:44:23.320 --> 00:44:28.200
 what we're intending to do, especially in light of the other Bonnie Brade projects.

00:44:28.200 --> 00:44:34.280
 So could some sort of alignment clarity, could you kind of describe or somebody describe what

00:44:34.280 --> 00:44:36.520
 we're talking about in that region?

00:44:36.520 --> 00:44:37.520
 >> Sure.

00:44:37.520 --> 00:44:41.800
 Currently, Bonnie Brake terminates at US 377.

00:44:41.800 --> 00:44:45.960
 It's at an angle, and it's an unsafe crossing so far.

00:44:45.960 --> 00:44:51.520
 And there is another crossing to the south of that at Johnson that hits at 377.

00:44:51.520 --> 00:44:54.800
 So this project is based on our mobility plan.

00:44:54.800 --> 00:45:00.600
 Rush Creek hits at 377, it right now terminates, but it will extend all the way on the western

00:45:00.600 --> 00:45:07.240
 side of 377 to go to 35, turns into Aldred, based on our mobility plan.

00:45:07.240 --> 00:45:12.800
 So with this project, what we are trying to do is close Bonnie Brake crossing and Johnson

00:45:12.800 --> 00:45:18.920
 crossing, that's UPR guidelines, to trade two crossings to get one new crossing.

00:45:18.920 --> 00:45:27.400
 And this new crossing will provide six lanes with the quiet zone, traffic light, and preemption,

00:45:27.400 --> 00:45:33.040
 which is a much more safer crossing than Johnson or at Bonnie Brake.

00:45:33.040 --> 00:45:34.040
 >> Nice.

00:45:34.040 --> 00:45:35.240
 >> Yes, sir?

00:45:35.240 --> 00:45:40.760
 >> And just to tag on to that, so the south side of Sagebrook, the right of way has been

00:45:40.760 --> 00:45:45.960
 acquired, this plan has been in the works for years.

00:45:45.960 --> 00:45:54.280
 So the Bonnie Brake crossing will close and it will go through that south of the Sagebrook

00:45:54.280 --> 00:45:55.280
 subdivision.

00:45:55.280 --> 00:45:56.280
 We can provide you with that.

00:45:56.280 --> 00:45:57.280
 >> I was going to say, do we have an alignment?

00:45:57.280 --> 00:45:58.280
 >> We do.

00:45:58.280 --> 00:46:02.520
 >> Because I think 99% of my questions would be answered if I could visualize the alignment.

00:46:02.520 --> 00:46:05.400
 >> It's much simpler, it's much cleaner, so absolutely we'll provide that.

00:46:05.400 --> 00:46:06.400
 >> Perfect.

00:46:06.400 --> 00:46:07.400
 >> That would be great.

00:46:07.400 --> 00:46:10.880
 And when you provide that to him, just provide it to all of us on the committee.

00:46:10.880 --> 00:46:11.880
 >> Absolutely.

00:46:11.880 --> 00:46:12.880
 >> Thank you.

00:46:12.880 --> 00:46:13.880
 Yes?

00:46:13.880 --> 00:46:18.160
 >> I have to follow what he said that a lot of visuals would help me as well.

00:46:18.160 --> 00:46:22.080
 When I first read this, I was completely in the wrong location, but I think I understand

00:46:22.080 --> 00:46:23.440
 where we are now.

00:46:23.440 --> 00:46:30.520
 So my question is on the Brushy Creek, Hickory Creek, is that part of our Hickory Creek widening

00:46:30.520 --> 00:46:32.880
 project, the bond funded project?

00:46:32.880 --> 00:46:33.880
 I just want to confirm that.

00:46:33.880 --> 00:46:36.520
 >> It's on the eastern side, yes.

00:46:36.520 --> 00:46:45.860
 The Hickory Creek terminates at bond 377, that is in the -- yeah, 1830.

00:46:45.860 --> 00:46:51.040
 >> And then, so at the new crossing, and I do know this rule of to create a new crossing,

00:46:51.040 --> 00:46:52.640
 we are required to close two.

00:46:52.640 --> 00:46:53.640
 >> That's right.

00:46:53.640 --> 00:46:58.240
 >> On the new crossing, so we said it would be six lanes, as part of the 2019 Hickory

00:46:58.240 --> 00:47:02.320
 Creek widening bond project, there was bike/ped infrastructure.

00:47:02.320 --> 00:47:08.880
 So my question is, at the crossing, will the quad gates also block the bike/ped infrastructure?

00:47:08.880 --> 00:47:09.880
 >> No.

00:47:09.880 --> 00:47:13.560
 >> Just to give a more active, hey, you should stop?

00:47:13.560 --> 00:47:20.680
 >> It's only for the vehicles right now, because quad gates are optional for pedestrians, and

00:47:20.680 --> 00:47:29.280
 cost would be exponentially high, but as far as railways, it's optional, they give it justification

00:47:29.280 --> 00:47:34.960
 based on what we recommend, but usually on pedestrians, we provide the Z gates, they

00:47:34.960 --> 00:47:40.360
 kind of navigate like a maze and hit perpendicularly to the tracks.

00:47:40.360 --> 00:47:45.200
 >> So I know road width is going to impact it, but I have seen in other cities where

00:47:45.200 --> 00:47:49.720
 a single gate could block both, so you didn't buy an extra gate, you just had a gate that

00:47:49.720 --> 00:47:54.000
 could block both, and a lot of folks do struggle with the Z gates, because it's really for

00:47:54.000 --> 00:47:58.000
 pedestrians, not bikes, so people with cargo bikes, bike trailers, they really struggle

00:47:58.000 --> 00:48:03.280
 to navigate that, so on the DCTA rail trail, a lot of people just go around them, because

00:48:03.280 --> 00:48:09.840
 it's hard to navigate, so if we can do something that's more friendly to more people, that

00:48:09.840 --> 00:48:12.800
 would be ideal, especially if it's one of those options where we don't have to add an

00:48:12.800 --> 00:48:16.240
 additional gate, because I know those are expensive, but I know there's an option in

00:48:16.240 --> 00:48:20.800
 some cases, depending on the road width and things like that, to possibly have the same

00:48:20.800 --> 00:48:28.560
 arm block bike path and the car lanes, potentially. >> It depends, we can evaluate it, but when

00:48:28.560 --> 00:48:35.680
 you go to like a six-lane facility, already the arm lengths has to go span across three

00:48:35.680 --> 00:48:42.600
 lanes, there is a sag, but when you incorporate pedestrian elements, the gates have to be

00:48:42.600 --> 00:48:47.800
 even more longer, but since it's a new roadway, new location, we could evaluate it.

00:48:47.800 --> 00:48:51.600
 >> That would be ideal if we can figure out a way to make that happen.

00:48:51.600 --> 00:48:59.320
 >> I think that's a reasonable ask. It seems logical. Okay, anybody else on this topic?

00:48:59.320 --> 00:49:02.880
 All right, well, Dean, thank you very much, we appreciate it. All right, we're going to

00:49:02.880 --> 00:49:10.640
 move down to EMC 25-005, receive a report, hold a discussion, and give staff direction

00:49:10.640 --> 00:49:18.240
 regarding future meeting topics. Also, I'm going to read this so I don't forget this,

00:49:18.240 --> 00:49:23.320
 agenda information sheet and future items matrix. I never get a chance to look up to

00:49:23.320 --> 00:49:28.480
 see that it's actually there, so yeah. So here we are.

00:49:28.480 --> 00:49:32.800
 >> Sure, so Trevor Crane, Director of Capital Projects, again, I'll run through these rather

00:49:32.800 --> 00:49:38.480
 quickly. So the 2019 bond program, Janie Street, we provided that update, we'd like to request

00:49:38.480 --> 00:49:46.560
 to remove that. The next couple will be updates that we'll provide when they're completed.

00:49:46.560 --> 00:49:52.140
 So citywide parking study, collision reduction statistics, concerns for bicyclists and pedestrian

00:49:52.140 --> 00:49:57.320
 safety on north and south Austin, and then growing the Bice Bus program, those are all

00:49:57.320 --> 00:50:02.440
 being worked on now, and once we get those completed, we'll provide those. Next is the

00:50:02.440 --> 00:50:08.520
 hawk best practices, so that was provided today. We did give some additional questions,

00:50:08.520 --> 00:50:16.200
 so we'll probably need to leave that one on there just to finish that one out. Increasing

00:50:16.200 --> 00:50:24.040
 wrapped equipment, box locations, that was provided in November 20th to 2024, so I would

00:50:24.040 --> 00:50:27.240
 request that we remove that one, unless there's additional-

00:50:27.240 --> 00:50:28.640
 >> We have a project.

00:50:28.640 --> 00:50:29.640
 >> It's coming back. Oh, sorry.

00:50:29.640 --> 00:50:30.640
 >> Oh, it's going to come back.

00:50:30.640 --> 00:50:35.640
 >> It's going to come back. Thank you, Jasmine. McKinney Crosswalk, we'll provide an update

00:50:35.640 --> 00:50:36.800
 when that one is available.

00:50:36.800 --> 00:50:42.360
 >> Now, can I verify that that's the Crosswalk near Janie Street by the-

00:50:42.360 --> 00:50:45.720
 >> I'm not sure which one it is. We'll go back and check the notes and make sure that

00:50:45.720 --> 00:50:46.720
 we have-

00:50:46.720 --> 00:50:49.080
 >> I know that's the one that I requested, and so I'm not sure if anybody else has-

00:50:49.080 --> 00:50:50.080
 >> It's probably it, but let me verify.

00:50:50.080 --> 00:50:51.080
 >> Okay.

00:50:51.080 --> 00:50:56.760
 >> And then we have our quarterly transportation mobility project status that'll come back

00:50:56.760 --> 00:51:02.240
 next quarter. Quarterly construction report and trip report that'll be coming back as

00:51:02.240 --> 00:51:08.960
 well as our transportation services report. Those are all on a quarterly update schedule.

00:51:08.960 --> 00:51:13.040
 Quiet zone realignment for Mingo and Riddell, that's being worked on along with our side

00:51:13.040 --> 00:51:18.720
 path and trail access, that was also being worked on as well. And then traffic calming

00:51:18.720 --> 00:51:25.280
 measures was provided, and that one's coming back as well. Jasmine's nodding her head at

00:51:25.280 --> 00:51:26.280
 me.

00:51:26.280 --> 00:51:32.000
 >> I think now we can take anything additional that y'all would like to add to the future

00:51:32.000 --> 00:51:33.000
 items list.

00:51:33.000 --> 00:51:42.120
 >> I know that I am going to or going to have some conversation about Moore Street. Would

00:51:42.120 --> 00:51:49.120
 this be included on this list, or is this already off this list, but we know that it's

00:51:49.120 --> 00:51:50.120
 coming.

00:51:50.120 --> 00:51:53.520
 >> Sure. So that meeting on Moore's is tomorrow, and we'll go through that project with you.

00:51:53.520 --> 00:51:54.520
 >> It comes on the meeting.

00:51:54.520 --> 00:51:55.520
 >> Yes, ma'am.

00:51:55.520 --> 00:52:01.320
 >> All right. I'll look at my calendar. I think that was the only thing in my -- oh,

00:52:01.320 --> 00:52:11.080
 you know what? I would like for you all to add Spencer Road -- no, Spencer? Yeah, Spencer.

00:52:11.080 --> 00:52:13.920
 Between 288 and May Hill.

00:52:13.920 --> 00:52:14.920
 >> Okay.

00:52:14.920 --> 00:52:20.760
 >> It's just the numbers are increasing on that road. And we had initially had a complaint

00:52:20.760 --> 00:52:25.480
 from the senior citizens that live on that road, that community there. They're concerned

00:52:25.480 --> 00:52:30.120
 about increased back and forth because of the new apartment complex.

00:52:30.120 --> 00:52:33.160
 >> Okay. So an evaluation of widening that road?

00:52:33.160 --> 00:52:36.880
 >> Yes. Kind of looking at the evaluation. As a matter of fact, and this is kind of personal,

00:52:36.880 --> 00:52:42.320
 I want to say this real quick, I was coming out from Walmart and coming back behind the

00:52:42.320 --> 00:52:45.400
 buildings. You know how you can kind of go behind those buildings? And I was making a

00:52:45.400 --> 00:52:50.560
 right turn there, just kind of evaluate the area, and just right to the right at that right

00:52:50.560 --> 00:52:56.000
 turn, there's a really deep kind of gully type thing. I was going to put it on engaged in,

00:52:56.000 --> 00:53:01.360
 but I just never did do it. So I'll just ask you all to please evaluate that area as you're

00:53:01.360 --> 00:53:02.360
 doing that.

00:53:02.360 --> 00:53:03.860
 >> Yes, ma'am.

00:53:03.860 --> 00:53:10.760
 >> The other thing that I may -- what are we doing on -- I know Moore Street -- no,

00:53:10.760 --> 00:53:17.720
 yeah, Moore Street turns into -- I don't know, but it's got a crossover 288.

00:53:17.720 --> 00:53:21.720
 >> What's that? Say it again?

00:53:21.720 --> 00:53:23.720
 >> Sadie Shores.

00:53:23.720 --> 00:53:29.800
 >> Sadie Shores. And I saw some work being done over in that area.

00:53:29.800 --> 00:53:30.800
 >> Okay.

00:53:30.800 --> 00:53:38.240
 >> By maybe about a -- by Kimberly, kind of up in there. And I didn't recognize what was

00:53:38.240 --> 00:53:39.720
 going on. Were you all looking at that?

00:53:39.720 --> 00:53:41.880
 >> Yeah. Take a look at it. Yes, ma'am.

00:53:41.880 --> 00:53:47.160
 >> And I think that's all that I had. I'm going to start on this scene. Go ahead. Yeah.

00:53:47.160 --> 00:53:55.840
 >> So what I'd like to try to discuss is with all the construction we've got going around,

00:53:55.840 --> 00:54:00.840
 sometimes if you're walking or biking, you'll hit a dead end, like sidewalk close, something

00:54:00.840 --> 00:54:07.560
 like that, and there's no detour provided or suggestion on how to proceed. In some cases,

00:54:07.560 --> 00:54:11.540
 like on Carroll, something with fewer pedestrian crossings, you don't know the sidewalk is

00:54:11.540 --> 00:54:17.880
 closed until you're, you know, 15 minutes away from the closest legal crossing. So it

00:54:17.880 --> 00:54:22.880
 tends to encourage people to cross at unsafe locations and that kind of thing. So maybe

00:54:22.880 --> 00:54:28.500
 this is a discussion at some point. I'm kind of curious if there's any additional policies

00:54:28.500 --> 00:54:33.600
 we need to add to do things like giving advanced warnings of sidewalk closures before you hit

00:54:33.600 --> 00:54:39.480
 the closure. And also what our process is for -- I know for -- is it temporary traffic

00:54:39.480 --> 00:54:46.160
 controls, is that the phrase I'm looking for here? If there's a pedestrian or bicycle infrastructure

00:54:46.160 --> 00:54:51.920
 at that location and that's blocked, we're supposed to provide some sort of detour unless,

00:54:51.920 --> 00:54:58.220
 you know, there's certain reasons to not. So I'd be curious to sort of hear how we go

00:54:58.220 --> 00:55:03.560
 about creating the detours and how we decide maybe that we're not going to. So like an

00:55:03.560 --> 00:55:09.920
 example right now is Hickory Street, pretty close to Welch. The bike lane ends. There's

00:55:09.920 --> 00:55:15.280
 no detour. So especially when you've got an inexperienced bicyclist, having them merge

00:55:15.280 --> 00:55:19.600
 kind of suddenly with car traffic kind of creates confusion and potential for collision.

00:55:19.600 --> 00:55:24.280
 So I'm just kind of interested to hear our procedure for temporary traffic controls when

00:55:24.280 --> 00:55:28.600
 we're going to close or block a sidewalk or a bike facility.

00:55:28.600 --> 00:55:32.720
 Sure. So let me ask one clarification question because I think you may have brought up two

00:55:32.720 --> 00:55:38.040
 separate items. So one is when there's construction. So that's kind of one item. And you hit that

00:55:38.040 --> 00:55:42.200
 perfectly. Typically, they should be providing those advanced warning signs. So if you're

00:55:42.200 --> 00:55:46.480
 not seeing those, let us know. And then secondly, when you talked about Hickory, it sounds like

00:55:46.480 --> 00:55:51.640
 that was a permanent bike lane that just ends. Or is it due to construction?

00:55:51.640 --> 00:55:54.920
 So Welch is under construction and some of the construction is sort of bleeding into

00:55:54.920 --> 00:55:59.480
 the bike lane. So the pedestrian crossing and the bike lane right there are closed.

00:55:59.480 --> 00:56:00.480
 Gotcha. Okay.

00:56:00.480 --> 00:56:07.120
 So let me give you like a detour on that side. So that's just a specific example. Yeah. So

00:56:07.120 --> 00:56:12.160
 also like I know there's requirements of how far in advance you warn people of detours

00:56:12.160 --> 00:56:16.480
 and things like that. So looking at, especially when there's a sidewalk closure, whether it's

00:56:16.480 --> 00:56:22.280
 a road construction or out on Mayhill one time, it was blocked for like a city facility.

00:56:22.280 --> 00:56:27.680
 Just do we need to add something to policy to give more advanced warning at the nearest

00:56:27.680 --> 00:56:31.840
 legal crossing so people know ahead of time? Sure. It's going to be closed across here.

00:56:31.840 --> 00:56:35.080
 Yeah. I think that's going to be more of an enforcement issue, but we'll definitely provide

00:56:35.080 --> 00:56:41.540
 something. Okay. Thank you.

00:56:41.540 --> 00:56:47.560
 Yeah. I just want to put a pin in these because I'm not sure if it's a continuing item or

00:56:47.560 --> 00:56:52.960
 not from the PHP. So I'd love to see that guidance brought forward. But then for call

00:56:52.960 --> 00:56:58.160
 buttons in general, you know, we had the disabled gentlemen in the middle of the night at Rudel

00:56:58.160 --> 00:57:05.040
 at university with a, you know, urban pacification button rather than an actual call button.

00:57:05.040 --> 00:57:12.400
 Unfortunately, this gentleman, and I don't mean to be glib, but had to play Frogger and

00:57:12.400 --> 00:57:19.840
 that unfortunately lost his life. And so I guess my question is how often, and I don't

00:57:19.840 --> 00:57:24.640
 want the answer here because this is for future matrix items, but if we could get some clarity

00:57:24.640 --> 00:57:35.360
 on how often we audit our PCBs and you know, when, especially on these arterials and larger,

00:57:35.360 --> 00:57:40.520
 when, you know, what's our frequency of that? I don't want our pedestrians hitting the button

00:57:40.520 --> 00:57:47.000
 and having to take their lives into their hands, especially for disabled folks, especially

00:57:47.000 --> 00:57:52.040
 on the arterials and universities perennial. I mean, like I've come to this committee and

00:57:52.040 --> 00:57:58.240
 counsel many times for Rudel and Nottingham Old North. These are sort of constant issues

00:57:58.240 --> 00:58:03.840
 and it's not, it's because the neighborhoods span either side of a major, you know, strode

00:58:03.840 --> 00:58:12.460
 that we had here in our town. And so I'd like some clarity, some updating in a future item

00:58:12.460 --> 00:58:20.080
 on frequency of maintenance of those PCBs and where we stand on that so that I can go

00:58:20.080 --> 00:58:26.360
 back to the public and say that this was broken or, you know, that, yeah, no, we only do that

00:58:26.360 --> 00:58:32.000
 every three years or every five years or, and we don't know the status of our PCBs.

00:58:32.000 --> 00:58:37.400
 And I just, I mean, that's a huge spectrum. I just like to know where Denton is somewhere

00:58:37.400 --> 00:58:45.080
 in the middle of that. Sure. Absolutely. Okay. DCTA is having a long-term planning meeting

00:58:45.080 --> 00:58:50.000
 this weekend, and I believe that they may be discussing the addition of one or two routes.

00:58:50.000 --> 00:58:56.840
 At their previous meeting, they also discussed merging some UNT routes, recombining, reconfiguring

00:58:56.840 --> 00:59:03.140
 some things. So just maybe not next month, but at some point, I'd like to hear something

00:59:03.140 --> 00:59:09.760
 about how those will impact the city and what we might be able to do to support those creation

00:59:09.760 --> 00:59:13.360
 of the routes, right? If they're putting a stop here on university, can we, you know,

00:59:13.360 --> 00:59:19.960
 build a sidewalk bump out or, you know, those sorts of things. Sounds good. And with that

00:59:19.960 --> 00:59:26.880
 being said, do we know when the next time we're going to have DCTA to come in front

00:59:26.880 --> 00:59:33.120
 of City Council? Or can we get a brief something from our representative to come and speak

00:59:33.120 --> 00:59:40.720
 to us, to the Mobility Committee in this regard? Just have them in front of us in some kind

00:59:40.720 --> 00:59:46.880
 of way. Do we have any idea of when we're going to be seeing them again? No, we can

00:59:46.880 --> 00:59:51.640
 look at that and get back to you on what that might look like. We're attending the strategic

00:59:51.640 --> 00:59:56.560
 planning session, so we'll provide that feedback. Okay. And maybe we'll just do it in a report

00:59:56.560 --> 01:00:02.880
 form. Maybe we'll do an ISR type thing or, okay, because we still do have a representative.

01:00:02.880 --> 01:00:09.120
 Yes, absolutely. Yep. Which I haven't actually seen in the last couple of years. Yeah, and

01:00:09.120 --> 01:00:14.640
 they've been going to council, but I'll visit with Cassie on it. Please do. Thank you. Sure,

01:00:14.640 --> 01:00:20.520
 we'll stay connected. And were you talking about maybe some cross, that's what they're

01:00:20.520 --> 01:00:27.200
 going to be talking about, the strategic, you mentioned something about the buses not

01:00:27.200 --> 01:00:38.440
 crossing one another or other? UNT has, I want to say around 10 or 11 routes right now.

01:00:38.440 --> 01:00:42.800
 They're looking at just merging some of those because there's repetition of this bus follows

01:00:42.800 --> 01:00:46.960
 this route, and then this second bus follows pretty much the same route, but with some

01:00:46.960 --> 01:00:52.680
 divergences. Okay. And then also just like if they're adding a bus route somewhere, do

01:00:52.680 --> 01:00:56.840
 we need to add a crosswalk? Do we need to add a hawk beacon to support that bus route?

01:00:56.840 --> 01:01:02.600
 Things like that. Oh, okay. Also, if you all have an opportunity to add considerations

01:01:02.600 --> 01:01:09.920
 for downtown, I know that we have a great downtown plan, and I'm not real, I am not

01:01:09.920 --> 01:01:18.040
 me. I'm not real clear on how we're going to run our bus system through that space,

01:01:18.040 --> 01:01:25.280
 if it at all. So that'll be part of the strategic conversation. Yes. Yes, sir. Because you all

01:01:25.280 --> 01:01:34.280
 brought up that topic and because we delayed the autonomous vehicle item, I think it would

01:01:34.280 --> 01:01:42.320
 be beneficial to staff to know that, at least myself, I'm going to have questions about

01:01:42.320 --> 01:01:51.000
 how the DCTA scheduling interacts with something we would schedule if we do an autonomous vehicle.

01:01:51.000 --> 01:01:56.640
 And so staff might as well be aware of that and sort of talk about that integration when

01:01:56.640 --> 01:02:01.040
 we eventually bring that item back. I don't know when that's going to come back. It'll

01:02:01.040 --> 01:02:08.360
 probably be another year. So there was some funding reductions unrelated to the new presidency

01:02:08.360 --> 01:02:14.440
 that occurred last week, and so we're just going to wait for another year. We have been

01:02:14.440 --> 01:02:19.440
 in constant communication with DCTA, so we're going to continue to work with them and work

01:02:19.440 --> 01:02:24.040
 with them on routes. Again, why it is that we can provide some of the information from

01:02:24.040 --> 01:02:30.200
 the strategic planning session to this group via an ISR or something. I think DCTA will

01:02:30.200 --> 01:02:34.320
 really just report out to council, so you'll get that briefing from the representative

01:02:34.320 --> 01:02:40.520
 directly at council rather than through this body, but we'll be certain to provide something

01:02:40.520 --> 01:02:44.840
 related to kind of that planning. But just important to note that staff does meet with

01:02:44.840 --> 01:02:52.520
 DCTA bi-weekly, so we're in constant communication. That's unfortunate because the last time we

01:02:52.520 --> 01:02:59.340
 saw the TERS, they talked about this was coming before you in a week, so apparently the funding

01:02:59.340 --> 01:03:07.080
 changed from when Vicki and I saw it a week ago to this meeting, so that's very unfortunate.

01:03:07.080 --> 01:03:17.880
 The timing feels coincidental, but okay. So they reduced that. It's a very competitive

01:03:17.880 --> 01:03:25.680
 process. DCTA wasn't completely prepared for this, so we were almost a little bit ahead

01:03:25.680 --> 01:03:29.920
 of DCTA, so this will work much more in a collaborative way anyhow that we have a little

01:03:29.920 --> 01:03:34.320
 better timing to get through the strategic planning process and then be able to put together

01:03:34.320 --> 01:03:41.120
 a packet together to work on this. So we'll be looking at submitting in the fall or start

01:03:41.120 --> 01:03:50.000
 the process in the fall for the early '26 awards. Thank you. Okay. Anything else? Future

01:03:50.000 --> 01:04:00.300
 items on the future items matrix. Oh, yes. Okay. I understand that we need to vote on

01:04:00.300 --> 01:04:15.880
 the removal. The update. Okay, remove. Okay. So I'll need to get a motion. Also move. Second.

01:04:15.880 --> 01:04:24.720
 Okay. All right. All in favor. Thank you. And with that being said, their concluding

01:04:24.720 --> 01:04:49.520
 meeting is February next meeting. Oh, next meeting. 2626. Yes. I just want to say shout

01:04:49.520 --> 01:04:54.640
 out to staff for the vision zero kickoff meeting is stakeholder meeting. Was that two weeks

01:04:54.640 --> 01:05:01.000
 ago, something January 15th. Yeah. So I'm really happy that the city's continuing with

01:05:01.000 --> 01:05:06.160
 trying to reduce traffic fatalities and serious injuries and great kickoff meeting to everybody

01:05:06.160 --> 01:05:12.080
 that was there and or helped plan it or implement it. Yes, yes, yes. I had that in the back

01:05:12.080 --> 01:05:16.860
 of my mind to say, but I'm glad you said it. Anything else? Well, I don't have anything.

01:05:16.860 --> 01:05:23.420
 So we are going to conclude this meeting at 1105 a.m. this morning. Everyone, please have

01:05:23.420 --> 01:05:27.040
 a great rest of the day and the great rest of your life.

