WEBVTT

00:00:00.000 --> 00:00:13.200
 Good morning, we are here at the City of Denton Mobility Committee at 8 a.m. in the council

00:00:13.200 --> 00:00:15.560
 work session room.

00:00:15.560 --> 00:00:19.160
 Do we have any citizen comments on the agenda item?

00:00:19.160 --> 00:00:20.400
 Does anybody have?

00:00:20.400 --> 00:00:23.240
 It doesn't seem to be there.

00:00:23.240 --> 00:00:27.520
 So we'll move on to items for individual consideration.

00:00:27.520 --> 00:00:37.160
 House 1, MC 23-018, consider approval of the minutes May 24th.

00:00:37.160 --> 00:00:45.200
 Since you are newly on the board, the committee here, we don't have the quorum to approve

00:00:45.200 --> 00:00:53.040
 the minutes from May 24th, so we would need another person here.

00:00:53.040 --> 00:00:55.000
 So we're going to move on from there.

00:00:55.000 --> 00:00:56.000
 Yes, sir?

00:00:56.000 --> 00:01:02.920
 Councilor McGee and I can't verify the minutes, so is there a process where only one committee

00:01:02.920 --> 00:01:05.320
 member can verify the minutes?

00:01:05.320 --> 00:01:12.320
 I think it's a quorum issue here, so two people are a quorum, so he's not here.

00:01:12.320 --> 00:01:18.440
 So I will, just for expediency, even though I will, if you will attest to the minutes,

00:01:18.440 --> 00:01:21.000
 then I will move approval of the minutes.

00:01:21.000 --> 00:01:22.960
 I can attest to the minutes.

00:01:22.960 --> 00:01:29.680
 And I will accept your as a statement of fact and move approval of the minutes.

00:01:29.680 --> 00:01:31.800
 Well, that's great.

00:01:31.800 --> 00:01:33.320
 So yes.

00:01:33.320 --> 00:01:35.320
 So all in favor?

00:01:35.320 --> 00:01:36.320
 Aye.

00:01:36.320 --> 00:01:37.320
 Aye.

00:01:37.320 --> 00:01:38.320
 All right, there you go.

00:01:38.320 --> 00:01:39.920
 Thank you.

00:01:39.920 --> 00:01:47.640
 Moving on to MC 23-19, Receive a report and hold a discussion regarding the City of Denton

00:01:47.640 --> 00:01:51.520
 Transportation Mobility Project Status Report.

00:01:51.520 --> 00:01:58.480
 Yes, ma'am, and today we have Barry Heard with ITS here to present the information for

00:01:58.480 --> 00:01:59.480
 us.

00:01:59.480 --> 00:02:01.440
 He has the packet ready.

00:02:01.440 --> 00:02:03.440
 Good morning.

00:02:03.440 --> 00:02:05.680
 Good morning.

00:02:05.680 --> 00:02:06.680
 Present.

00:02:06.680 --> 00:02:07.680
 Present.

00:02:07.680 --> 00:02:08.680
 Present.

00:02:08.680 --> 00:02:11.680
 There it is.

00:02:11.680 --> 00:02:12.680
 Present.

00:02:12.680 --> 00:02:13.680
 Thanks.

00:02:13.680 --> 00:02:14.680
 All right.

00:02:14.680 --> 00:02:15.680
 I'm Barry Heard.

00:02:15.680 --> 00:02:19.040
 I'm here to present the Mobility Report.

00:02:19.040 --> 00:02:27.360
 These are the projects we have, starting out with number one, FM 2181.

00:02:27.360 --> 00:02:33.640
 When I started -- when I retired with TechStat in 2016, this project was just getting started.

00:02:33.640 --> 00:02:38.280
 And we don't have this on our reports very often that we say completed, but this has

00:02:38.280 --> 00:02:48.200
 been a project that's taken a few years and very glad to say that it's completed, FM 2181.

00:02:48.200 --> 00:03:02.200
 I-35 North, this is split up into four separate projects, and there's 115 parcels for acquisition

00:03:02.200 --> 00:03:09.600
 on the 74 CSJ, 113 of those parcels are in possession and two in negotiations.

00:03:09.600 --> 00:03:19.240
 We're working to expedite the design, resubmittal at the end of July 2023.

00:03:19.240 --> 00:03:21.600
 That's with AT&T.

00:03:21.600 --> 00:03:25.760
 These utilities are finalizing all across the city of Denton.

00:03:25.760 --> 00:03:32.220
 We're expecting to have that agreement later this month.

00:03:32.220 --> 00:03:34.260
 And everybody else is just finishing up.

00:03:34.260 --> 00:03:42.720
 The interchange letting, the important thing to note here is the letting is April 2024

00:03:42.720 --> 00:03:46.440
 with completed plans in December of 2023.

00:03:46.440 --> 00:03:51.200
 Right now those plans are under 95% review.

00:03:51.200 --> 00:04:01.720
 And the city of Denton is working with TWU on the medallion.

00:04:01.720 --> 00:04:05.600
 And those utilities are expected to be completed in August.

00:04:05.600 --> 00:04:14.300
 So this project is $466 million, it's a very big project.

00:04:14.300 --> 00:04:18.720
 Here's the utilities, they're just finishing up also.

00:04:18.720 --> 00:04:26.340
 Next project, I-35E at May Hill, $116 million project scheduled to let, ready to let in

00:04:26.340 --> 00:04:45.560
 February 2024 with a June 25 let date, 35W frontage roads, 60% plan review is going to

00:04:45.560 --> 00:04:53.240
 be submitted later this week, 100% plan scheduled for December of 2023.

00:04:53.240 --> 00:05:00.080
 And currently, ready to let is December 24.

00:05:00.080 --> 00:05:05.880
 And we expect right away acquisition to be complete in September.

00:05:05.880 --> 00:05:22.720
 380, US 380, US 377, this project's under construction, $20 million project with Regal

00:05:22.720 --> 00:05:31.800
 doing the construction, they're working on the medians and the sidewalks, mainly on the

00:05:31.800 --> 00:05:36.040
 west end of the project currently.

00:05:36.040 --> 00:05:48.480
 Loop 288 West frontage roads, this project is expecting 100% plans in February 2024.

00:05:48.480 --> 00:05:56.300
 And again, this is another submittal, a 60% submittal that is planned at the end of July

00:05:56.300 --> 00:06:00.680
 in the next few weeks, or the next few days actually.

00:06:00.680 --> 00:06:15.280
 CPMY is a consultant and there was a TCP traffic control plan conference held last week.

00:06:15.280 --> 00:06:23.360
 Loop 288 East and the US 380 connector, this is a project we're actually having a public

00:06:23.360 --> 00:06:29.840
 meeting tomorrow night here in Denton.

00:06:29.840 --> 00:06:40.080
 It's a, the current estimated cost is approximately $650 million.

00:06:40.080 --> 00:06:49.780
 Bonnie Bray segment seven, this is an extension of the project that was just previously connecting

00:06:49.780 --> 00:06:53.360
 Bonnie Bray to the loop.

00:06:53.360 --> 00:07:07.520
 FM 1515 airport road, estimated construction costs approximately 34 million, 100% plans

00:07:07.520 --> 00:07:18.800
 are scheduled for May of 2024 with a ready to let date of June 2025.

00:07:18.800 --> 00:07:24.360
 Right now, almost all the right of way is acquired and once that's done, the utilities

00:07:24.360 --> 00:07:30.400
 will, utility relocations will start.

00:07:30.400 --> 00:07:41.040
 FM 1173, this is mainly from, in crumb from 156 to I-35.

00:07:41.040 --> 00:07:47.520
 It's an estimated construction cost of 88 million, 100% plans in March 2024 with a ready

00:07:47.520 --> 00:07:50.800
 to let of February 2025.

00:07:50.800 --> 00:07:58.000
 Currently, there are 41 parcels on the right of way parcels.

00:07:58.000 --> 00:08:07.560
 One parcel parcels are in eminent domain and 34 in possession.

00:08:07.560 --> 00:08:17.400
 The outer loop, this is a project that has recently started within the past six months.

00:08:17.400 --> 00:08:28.280
 It's a $1.5 billion project and this goes from State Highway 289 in Collin County to

00:08:28.280 --> 00:08:39.880
 I-35 north of Dent.

00:08:39.880 --> 00:08:52.080
 Noman Locust, this is the turn back with the City of Denton from, with TxDOT and once this

00:08:52.080 --> 00:09:10.160
 is approved, the city will provide a resolution to complete the process.

00:09:10.160 --> 00:09:12.160
 That's one thing I was going to mention on the outer loop.

00:09:12.160 --> 00:09:19.680
 The public meeting was held earlier in June and the comment period closed on June 22nd.

00:09:19.680 --> 00:09:26.000
 Have you all gotten a chance to review those comments yet?

00:09:26.000 --> 00:09:27.920
 They're in the process of reviewing those right now.

00:09:27.920 --> 00:09:36.120
 Once they're reviewed, all the responses will be posted online to the Denton County website

00:09:36.120 --> 00:09:38.120
 as well as TxDOT.

00:09:38.120 --> 00:09:44.320
 TxDOT has a link, Keep It Moving Dallas, and that link goes right to the county website

00:09:44.320 --> 00:09:50.160
 and those will be posted there.

00:09:50.160 --> 00:09:54.200
 I have a question about Bonnie Bray.

00:09:54.200 --> 00:10:04.360
 Let me go back down here.

00:10:04.360 --> 00:10:11.240
 That yellow part that we're looking at there, is the yellow part that's going north and

00:10:11.240 --> 00:10:16.200
 south, is that a new road or is that just an improved road right there?

00:10:16.200 --> 00:10:22.840
 Because it seemed like I thought that Bonnie Bray just went directly straight.

00:10:22.840 --> 00:10:24.120
 It is a new road.

00:10:24.120 --> 00:10:30.640
 Right, so currently there is a connection that goes underneath the loop off of 77.

00:10:30.640 --> 00:10:34.560
 It's further to the west where Barry's Parcer is.

00:10:34.560 --> 00:10:38.800
 And that roadway will no longer be the connection.

00:10:38.800 --> 00:10:45.400
 So what we're working with UNT as it impacts their property, and then also with the Loop

00:10:45.400 --> 00:10:52.080
 288 frontage road project that they're having the public hearing on Thursday, this has been

00:10:52.080 --> 00:10:53.280
 added as a portion.

00:10:53.280 --> 00:11:00.780
 So if you recall, Bonnie Bray Phase 6 will come from the south and basically make a perpendicular

00:11:00.780 --> 00:11:02.480
 angle at 77.

00:11:02.480 --> 00:11:08.600
 So this would be the connection piece between Bonnie Bray Phase 6 to the new loop project.

00:11:08.600 --> 00:11:12.040
 And so we've been coordinating with access.

00:11:12.040 --> 00:11:18.440
 We did not want to have this area be stranded and not have access to it.

00:11:18.440 --> 00:11:22.800
 The portion that Barry was showing you that's further to that west, that roadway continues

00:11:22.800 --> 00:11:26.560
 north and there are folks that receive access from that area.

00:11:26.560 --> 00:11:31.120
 So we've coordinated with transportation planning and then of course development services team

00:11:31.120 --> 00:11:35.040
 and our team just to make sure that there's still access to the frontage roads and that

00:11:35.040 --> 00:11:36.640
 you can continue north.

00:11:36.640 --> 00:11:41.820
 So there will continue to be a lot of coordination with UNT as they're looking at their master

00:11:41.820 --> 00:11:43.880
 plan in that area.

00:11:43.880 --> 00:11:49.360
 That portion that you see north of the loop that kind of sticks out a little bit, that's

00:11:49.360 --> 00:11:52.080
 a graphical representation.

00:11:52.080 --> 00:11:57.640
 That's not currently really in the works to make a new roadway go north in that area.

00:11:57.640 --> 00:12:03.440
 Currently what we're proposing and working with is to tie, there'll be a frontage road

00:12:03.440 --> 00:12:07.360
 along that area, tie that frontage road back to the existing Bonnie Bray that's to the

00:12:07.360 --> 00:12:09.320
 west of that location.

00:12:09.320 --> 00:12:12.800
 Because there will no longer be that U-turn turn around underneath.

00:12:12.800 --> 00:12:15.040
 But it'll go roughly from right here to right here.

00:12:15.040 --> 00:12:23.120
 That's correct Barry, thank you.

00:12:23.120 --> 00:12:31.780
 Also that north loop 288 to 35, they're right there.

00:12:31.780 --> 00:12:37.800
 That whole space right there is going to be frontage roads first, do you all build the

00:12:37.800 --> 00:12:42.400
 frontage roads first or do you all work?

00:12:42.400 --> 00:12:47.840
 We don't have the traffic control plan, this is just in the schematic phase but that will

00:12:47.840 --> 00:12:48.840
 be one way to do it.

00:12:48.840 --> 00:12:51.760
 Yeah, let's build the frontage roads first while all the traffic's on the main lanes

00:12:51.760 --> 00:12:52.760
 and go from there.

00:12:52.760 --> 00:12:55.360
 However, that's not been finalized.

00:12:55.360 --> 00:12:59.360
 But this is different than, so it's different than the loop 288 west.

00:12:59.360 --> 00:13:04.200
 So what is a little bit confusing is on the loop 288 west project, they are specifically

00:13:04.200 --> 00:13:07.880
 building the frontage roads first and then we'll come back at a later date.

00:13:07.880 --> 00:13:11.780
 It's based then over time, yes.

00:13:11.780 --> 00:13:16.680
 This project, and you'll see this tomorrow night, has an ultimate cross section, three

00:13:16.680 --> 00:13:20.040
 lanes each direction with frontage roads.

00:13:20.040 --> 00:13:24.920
 And so the way that it's constructed or the manner of which Barry's just mentioning, that

00:13:24.920 --> 00:13:29.440
 will come through as a part of the traffic control from the design engineer as to what

00:13:29.440 --> 00:13:31.320
 makes sense to construct first.

00:13:31.320 --> 00:13:35.400
 Many times, they do construct the frontage roads first, get traffic flowing on that,

00:13:35.400 --> 00:13:37.620
 then go back and work towards the center.

00:13:37.620 --> 00:13:40.920
 But those decisions have not been made because it's in schematic phase.

00:13:40.920 --> 00:13:44.800
 Several years out still on that determination.

00:13:44.800 --> 00:13:49.920
 Well I was just, keep thinking in mind of the developers that...

00:13:49.920 --> 00:13:50.920
 Providing access.

00:13:50.920 --> 00:13:52.720
 Yeah, for what they're doing, so...

00:13:52.720 --> 00:13:57.760
 We're gonna work closely with the city, we already have been on the access on this project,

00:13:57.760 --> 00:14:01.600
 so we will continue that throughout the project development.

00:14:01.600 --> 00:14:05.360
 The schematic environmental and the plans.

00:14:05.360 --> 00:14:11.120
 Just wanna comment on 380, I've been traveling up and down that way here lately for some

00:14:11.120 --> 00:14:16.240
 reason and just recognizing the good work that's being done and...

00:14:16.240 --> 00:14:19.880
 They make good progress here the last few months.

00:14:19.880 --> 00:14:20.880
 I'll pass that along.

00:14:20.880 --> 00:14:22.600
 Yeah, be sure and pass that along.

00:14:22.600 --> 00:14:23.600
 Definitely I will.

00:14:23.600 --> 00:14:24.600
 The work is not...

00:14:24.600 --> 00:14:25.720
 They're not working in vain.

00:14:25.720 --> 00:14:26.720
 Exactly.

00:14:26.720 --> 00:14:29.120
 It's definitely helping, so thank you for that.

00:14:29.120 --> 00:14:30.600
 You have any questions?

00:14:30.600 --> 00:14:37.840
 Yeah, I had similar questions and seems like your order was to run through yours, I appreciate

00:14:37.840 --> 00:14:38.840
 you letting me...

00:14:38.840 --> 00:14:40.400
 Can we go back to the Bonnie Bray?

00:14:40.400 --> 00:14:44.480
 I'll have Bonnie Bray's 288 and Outer Loop questions.

00:14:44.480 --> 00:14:51.240
 On that one, just to clarify a little, we're not...

00:14:51.240 --> 00:14:54.240
 The graphical extension is just that.

00:14:54.240 --> 00:15:02.920
 We're not anticipating jogging back to the left and hooking back in to North 77 at this

00:15:02.920 --> 00:15:06.280
 time up to Sanger and whatnot.

00:15:06.280 --> 00:15:09.280
 At this time, no.

00:15:09.280 --> 00:15:10.280
 Okay.

00:15:10.280 --> 00:15:17.640
 We don't have currently the growth in that area to make those improvements.

00:15:17.640 --> 00:15:23.040
 This is a, like I said, a graphical representation as the project moves forward and progresses

00:15:23.040 --> 00:15:24.040
 forward.

00:15:24.040 --> 00:15:29.080
 There may be a situation where along with the mobility plan, there might need to be

00:15:29.080 --> 00:15:35.280
 an additional roadway or improvements to existing old Bonnie Bray, air quotes.

00:15:35.280 --> 00:15:36.360
 At this time, no.

00:15:36.360 --> 00:15:41.720
 What we're proposing or what we've been working with Texton and their design engineer on is

00:15:41.720 --> 00:15:44.800
 actually just having a frontage road connection between...

00:15:44.800 --> 00:15:47.800
 Right there.

00:15:47.800 --> 00:15:48.800
 Correct.

00:15:48.800 --> 00:15:55.960
 Can I ask what is the impetus to move it 200 yards to the east?

00:15:55.960 --> 00:16:05.000
 That's based on a request from UNT as well as working with the city.

00:16:05.000 --> 00:16:09.160
 This intersection is close to the 77 intersection now.

00:16:09.160 --> 00:16:17.280
 This provides for a greater development as well as when this comes in at a 90 degree

00:16:17.280 --> 00:16:19.160
 angle at 77.

00:16:19.160 --> 00:16:25.600
 This makes this connection much more safer, much better, yes.

00:16:25.600 --> 00:16:31.240
 We are anticipating traffic control at 77 and Bonnie Bray.

00:16:31.240 --> 00:16:36.560
 There will be a traffic signal at that location.

00:16:36.560 --> 00:16:39.680
 It doesn't face six and right at 77.

00:16:39.680 --> 00:16:44.660
 It does end at 77.

00:16:44.660 --> 00:16:52.880
 Our anticipation is that folks could use Bonnie Bray all the way even from where Bonnie Bray

00:16:52.880 --> 00:16:59.920
 hits 35 down near the Textot office, use Bonnie Bray all the way north to get on the loop

00:16:59.920 --> 00:17:05.120
 or you could come up all the way 35 and then get on the loop.

00:17:05.120 --> 00:17:06.880
 It's just another access point.

00:17:06.880 --> 00:17:13.000
 Are you pulling out the old Bonnie Bray in that segment?

00:17:13.000 --> 00:17:14.000
 Yes.

00:17:14.000 --> 00:17:15.000
 This part?

00:17:15.000 --> 00:17:16.000
 Yes.

00:17:16.000 --> 00:17:17.000
 Yes.

00:17:17.000 --> 00:17:18.000
 Condemned and returned to grass?

00:17:18.000 --> 00:17:24.360
 Are you talking about the existing portion that's to the west?

00:17:24.360 --> 00:17:25.800
 That will know...

00:17:25.800 --> 00:17:26.800
 We're working through.

00:17:26.800 --> 00:17:32.560
 We've asked to keep the connection to 77, so the driveway connection, the roadway connection

00:17:32.560 --> 00:17:38.280
 to 77, that will be something we work through as a design process, but our anticipation

00:17:38.280 --> 00:17:42.080
 is that that roadway cross section will no longer be there.

00:17:42.080 --> 00:17:46.480
 The right of way will be there, but it'll no longer make the connection to go underneath

00:17:46.480 --> 00:17:47.680
 the loop.

00:17:47.680 --> 00:17:53.080
 Whether the pavement stays, whether that becomes a way that's a dead end or a cul-de-sac so

00:17:53.080 --> 00:17:56.840
 folks could develop on either side, those determinations have not been made.

00:17:56.840 --> 00:17:57.840
 That's one thing.

00:17:57.840 --> 00:18:01.280
 It'll work itself out over time, I think.

00:18:01.280 --> 00:18:08.600
 Yes, but putting a positive plan on that is always better than being reactive.

00:18:08.600 --> 00:18:09.600
 Yes.

00:18:09.600 --> 00:18:12.600
 I just don't think we're quite there yet.

00:18:12.600 --> 00:18:20.560
 If we could go to the 288 East and 380.

00:18:20.560 --> 00:18:31.320
 For those segments, are we widening those interchanges at Locust and Sherman, or that

00:18:31.320 --> 00:18:33.880
 you're just indicating intersections?

00:18:33.880 --> 00:18:40.360
 No, they will be reconstructed at the interchanges, yes.

00:18:40.360 --> 00:18:49.360
 Okay, so my concern at Sherman is we just reconstructed those interchanges, and so we're

00:18:49.360 --> 00:18:52.240
 reconstructing them?

00:18:52.240 --> 00:18:56.200
 We're tying in to what's there as well as making improvements, so anything that can

00:18:56.200 --> 00:19:03.080
 be saved will be saved, but we ultimately want to make the intersection fit the project.

00:19:03.080 --> 00:19:05.680
 Keep in mind, too, this will not all be at grade.

00:19:05.680 --> 00:19:09.760
 There will be some elevation to this, so some of it will be bridge connections, some of

00:19:09.760 --> 00:19:15.120
 it will be overpass, some of it will be braided ramps, those types of things.

00:19:15.120 --> 00:19:19.280
 Not everything will be at grade, and it's in a very preliminary state at this point,

00:19:19.280 --> 00:19:24.360
 so when you see the overall schematic, it's more of here's the cross section that will

00:19:24.360 --> 00:19:29.520
 fit within the right of way that's anticipated, and those details will be worked out through

00:19:29.520 --> 00:19:31.120
 the design phase.

00:19:31.120 --> 00:19:34.600
 Schematic phase is really more of a graphical representation.

00:19:34.600 --> 00:19:41.000
 Until you get to 30% design and really even 60% design, 65 is what they call plans adequate,

00:19:41.000 --> 00:19:44.920
 a lot of those details will not be worked out, and it could be up to a year from now.

00:19:44.920 --> 00:19:51.080
 We're expecting the environmental clearance in July 2025, so that's two years from now,

00:19:51.080 --> 00:19:57.040
 then start the detailed design, so yes, approximately one year before the 60% schematic would be

00:19:57.040 --> 00:20:04.200
 finalized, and that's when we set the right of way footprint from there.

00:20:04.200 --> 00:20:12.200
 Given that, and given the sort of nebulous nature and the incomplete design process,

00:20:12.200 --> 00:20:16.360
 the next part of this question is going to allude to what was in the paper and what you

00:20:16.360 --> 00:20:22.360
 and I have discussed before separately, and that is the amount of right of way and the

00:20:22.360 --> 00:20:29.520
 residential parcels, some of the retail and DASD parcels right along those segments.

00:20:29.520 --> 00:20:36.560
 Do we have sufficient right of way, or we're going to have to domain in the domain things?

00:20:36.560 --> 00:20:42.720
 Right now it's just currently, this is all a textile project, but right now it's currently

00:20:42.720 --> 00:20:47.880
 very schematic in nature, so they're looking at is the roadway cross section 110 feet,

00:20:47.880 --> 00:20:53.840
 is it 135, is it 300 feet, but what they have done is brought to us different examples of

00:20:53.840 --> 00:20:58.080
 areas where there's one area if you drive throughout that corridor, homes are built

00:20:58.080 --> 00:20:59.920
 very close to the edge.

00:20:59.920 --> 00:21:05.200
 So what they've done is a modified cross section to actually allow for the roadway section

00:21:05.200 --> 00:21:12.840
 to be more narrow in that area so that there won't be the impact to the homes in those

00:21:12.840 --> 00:21:13.840
 areas.

00:21:13.840 --> 00:21:16.840
 So those are things that they will evaluate through design is are there things that they

00:21:16.840 --> 00:21:23.720
 can do to make the lanes more narrow or not have as much median between the frontage road

00:21:23.720 --> 00:21:25.700
 and the main lanes.

00:21:25.700 --> 00:21:30.160
 So they're evaluating all those things and they've already submitted to us an actual

00:21:30.160 --> 00:21:34.040
 cross section to evaluate that's narrow in that area.

00:21:34.040 --> 00:21:38.040
 Our goal with this project is to have not only the main lanes and the frontage road,

00:21:38.040 --> 00:21:41.480
 but also a side path throughout this entire area.

00:21:41.480 --> 00:21:48.520
 Keep in mind there's large transmission poles also in this area and large water line transmission,

00:21:48.520 --> 00:21:51.000
 and so all of those conversations are happening.

00:21:51.000 --> 00:21:56.600
 We've actually taken their overview of their schematic and put the water and wastewater

00:21:56.600 --> 00:22:01.180
 infrastructure and DME infrastructure on those drawings and started having some of those

00:22:01.180 --> 00:22:07.760
 very preliminary conversations of this is going to be a very hot area for the city because

00:22:07.760 --> 00:22:09.360
 we can't have this impact.

00:22:09.360 --> 00:22:13.640
 We've already told them you can't construct during these timeframes because we have water

00:22:13.640 --> 00:22:15.520
 supply concerns.

00:22:15.520 --> 00:22:18.400
 So those conversations are already- Utility point is very important on this

00:22:18.400 --> 00:22:19.400
 project.

00:22:19.400 --> 00:22:22.380
 So we've been having those conversations.

00:22:22.380 --> 00:22:26.080
 It'll be up to TxDOT once they look at the final right away cross section, but they're

00:22:26.080 --> 00:22:30.000
 very cognizant of the fact that there are homes in these areas.

00:22:30.000 --> 00:22:34.880
 And you'll see it when you look at the schematic, and we're happy to point that out and show

00:22:34.880 --> 00:22:39.720
 those things to you where the cross section, and when I say the cross section, the roadway

00:22:39.720 --> 00:22:45.160
 cross section, where it's actually been narrowed instead of the ultimate to make sure that

00:22:45.160 --> 00:22:50.000
 it is looking into the homes that are on the south and the north side of that roadway.

00:22:50.000 --> 00:23:00.040
 Okay, and then you and I and Scott had this conversation before about the extension, the

00:23:00.040 --> 00:23:10.720
 on-ramp from 380 on to 288 on the east, starting around Mayhill-ish, no, it's east of Mayhill.

00:23:10.720 --> 00:23:14.280
 So is that alignment firmed since we discussed-

00:23:14.280 --> 00:23:15.280
 No.

00:23:15.280 --> 00:23:20.080
 ... at least at the time, where the development on the 288-

00:23:20.080 --> 00:23:21.880
 Right.

00:23:21.880 --> 00:23:28.560
 Originally there was a connection farther to the west, and then that's what I was saying

00:23:28.560 --> 00:23:32.160
 a little bit earlier, is we're working through the development with the city.

00:23:32.160 --> 00:23:38.440
 So this alignment that you see here is in a feasibility portion, so it's a little farther

00:23:38.440 --> 00:23:44.320
 back than the schematic and environmental on the main part of the loop.

00:23:44.320 --> 00:23:47.840
 There's really a difference.

00:23:47.840 --> 00:23:52.720
 It's going to go through more evaluation still, and that's what's going to be presented tomorrow

00:23:52.720 --> 00:23:53.720
 night also.

00:23:53.720 --> 00:23:58.000
 Yeah, and I would just add to that that there are still both alignments.

00:23:58.000 --> 00:23:59.600
 One was the schematic version of the alignment.

00:23:59.600 --> 00:24:00.600
 It's still there, yes.

00:24:00.600 --> 00:24:07.120
 And then this is the revised version as an alternate location, and the purpose of tomorrow's

00:24:07.120 --> 00:24:12.440
 meeting is to receive feedback to understand kind of what the community feels as far as-

00:24:12.440 --> 00:24:16.480
 And the individuals who are present, they also have that opportunity for public comment

00:24:16.480 --> 00:24:23.200
 to say this is an impact versus this is an impact, but both of those routes are still

00:24:23.200 --> 00:24:30.760
 going to be a part of the evaluation process throughout the entire public meeting in that

00:24:30.760 --> 00:24:32.960
 phase, and they'll give a timeframe.

00:24:32.960 --> 00:24:38.480
 And you'll see both of those on the schematic, so it's very hard to understand, and it also

00:24:38.480 --> 00:24:47.200
 is a process many times that obviously residents, council, et cetera, they're trying to understand,

00:24:47.200 --> 00:24:49.000
 okay, well, when is this going to happen?

00:24:49.000 --> 00:24:50.000
 What's the impact?

00:24:50.000 --> 00:24:52.320
 How is this impacting the development community?

00:24:52.320 --> 00:24:53.640
 How is this impacting my home?

00:24:53.640 --> 00:24:56.240
 I currently live there, et cetera.

00:24:56.240 --> 00:24:59.120
 That's why both of the schematics exist.

00:24:59.120 --> 00:25:05.120
 I will also tell you that we meet monthly with Barry, the design firm who's actually

00:25:05.120 --> 00:25:11.480
 working on this for the county, TextDOT, UNT's present, and have a meeting to actually go

00:25:11.480 --> 00:25:16.320
 through with development services team and transportation planning, and review every

00:25:16.320 --> 00:25:20.880
 single development that's come along that entire cross-section, so we can be letting

00:25:20.880 --> 00:25:25.640
 them know, hey, we've just received this development application, hey, we're working on this capital

00:25:25.640 --> 00:25:26.640
 project.

00:25:26.640 --> 00:25:31.360
 So we're doing monthly check-ins at the schematic phase, even though it's very preliminary,

00:25:31.360 --> 00:25:35.040
 just so they're aware of the types of development we're seeing and where those locations are.

00:25:35.040 --> 00:25:41.040
 Those are separate from our regular meetings, which are hour, two-hour long meetings every

00:25:41.040 --> 00:25:42.040
 month.

00:25:42.040 --> 00:25:46.880
 I appreciate you all doing that because there's so much development coming in there, and building

00:25:46.880 --> 00:25:51.560
 something new and then eminent domain it like a year later is really foolish.

00:25:51.560 --> 00:25:56.880
 That's where the other alignment came from as far as the feasibility.

00:25:56.880 --> 00:25:59.860
 My last question is on the outer loop.

00:25:59.860 --> 00:26:08.360
 When I was at the meeting, it seemed like it was the light blue path, but there's none

00:26:08.360 --> 00:26:13.840
 of the potential paths on here.

00:26:13.840 --> 00:26:16.440
 Has that firmed up since the last meeting?

00:26:16.440 --> 00:26:18.960
 We're still going under the comments.

00:26:18.960 --> 00:26:25.920
 If I remember, I want to say there was 167 different alignments or variations of alignments

00:26:25.920 --> 00:26:31.720
 throughout this corridor, and they're still going through the comments, working with the

00:26:31.720 --> 00:26:34.480
 Corps of Engineers along FM428.

00:26:34.480 --> 00:26:41.720
 So I would say it's going to be several months more before there's even narrowed down to

00:26:41.720 --> 00:26:43.200
 several alignments.

00:26:43.200 --> 00:26:44.200
 Okay.

00:26:44.200 --> 00:26:53.160
 Yeah, and I'd just add, Barry, that the design firm for this project also, we've been meeting

00:26:53.160 --> 00:26:57.040
 with on a fairly regular basis, not monthly.

00:26:57.040 --> 00:27:01.840
 We do meet with them this week on Thursday, and their goal is similar, to ask what capital

00:27:01.840 --> 00:27:03.760
 projects we have in the area.

00:27:03.760 --> 00:27:10.600
 Trevor's team has projects going up 35 to the Milam Road area as a part of the 35 project,

00:27:10.600 --> 00:27:15.180
 but also to find out from our team what are the developments we see in the area, and then

00:27:15.180 --> 00:27:20.240
 I want the development services team to have the opportunity to explain some of the Northeast

00:27:20.240 --> 00:27:21.960
 area plan that they're working on.

00:27:21.960 --> 00:27:27.840
 So we're meeting with them, actually tomorrow, to talk about what the city's doing in those

00:27:27.840 --> 00:27:30.000
 areas and the impacts.

00:27:30.000 --> 00:27:33.800
 We're working to have that open dialogue, so like I mentioned on the previous, is they

00:27:33.800 --> 00:27:39.000
 understand here are the things that are happening within the city of Denton that either could

00:27:39.000 --> 00:27:44.120
 or could not make an impact on what their plans are, what their proposal.

00:27:44.120 --> 00:27:50.720
 At this current time, they're still kind of showing that green, I call it the blob, because

00:27:50.720 --> 00:27:53.360
 there is not an alignment that has been selected.

00:27:53.360 --> 00:27:57.760
 As Barry mentioned, they're going through a number of comments that have been received,

00:27:57.760 --> 00:28:02.900
 and typically they will get it down to a couple of fixed alignments and then have another

00:28:02.900 --> 00:28:03.900
 public conversation.

00:28:03.900 --> 00:28:10.200
 Well, as you know from all these community meetings and the comments that everybody's

00:28:10.200 --> 00:28:16.520
 gotten from the public, there's a lot of, the concern is too strong, but a lot of focus,

00:28:16.520 --> 00:28:22.680
 a lot of interest in North Denton and South Sanger populations on exactly where this is

00:28:22.680 --> 00:28:26.680
 going through, where it's punching through Aubrey and all that.

00:28:26.680 --> 00:28:29.800
 There's a lot of, there's a laser focus on this.

00:28:29.800 --> 00:28:35.640
 Same meetings that Becky had mentioned with all the cities, Aubrey, Salina, Krugerville,

00:28:35.640 --> 00:28:46.320
 Pilot Point, Sanger, Salina, this is part of a regional project also that goes through

00:28:46.320 --> 00:28:50.520
 Collin County, Rockwell County, Kauffman County, all the way down to I-20, which will eventually

00:28:50.520 --> 00:28:54.200
 go through Ellis to 45, I-45.

00:28:54.200 --> 00:28:55.200
 Yeah.

00:28:55.200 --> 00:29:01.600
 It's hard to understand also because we're looking at it specifically within our county

00:29:01.600 --> 00:29:06.480
 or our impacted area, but this roadway is actually shown on the 20-45 mobility plan

00:29:06.480 --> 00:29:12.720
 that NETCOG has and so that's a part of their overall adopted plan for the entire Metroplex

00:29:12.720 --> 00:29:16.880
 and that's the impact he's talking about is it's five or six counties that it actually

00:29:16.880 --> 00:29:20.000
 will go through at some point.

00:29:20.000 --> 00:29:22.920
 I think that's all my questions, I appreciate you.

00:29:22.920 --> 00:29:29.940
 Well, while we were discussing that, I was thinking about that big monstrosity down in

00:29:29.940 --> 00:29:38.000
 Houston where they were having to push out and put additional roads out and Highway 6.

00:29:38.000 --> 00:29:45.960
 I lived maybe about 10 miles from 610 and to see just everything going south and I thought

00:29:45.960 --> 00:29:53.040
 Richmond used to be far away and Katy used to be far away, but I'm appreciating all of

00:29:53.040 --> 00:29:54.040
 this.

00:29:54.040 --> 00:29:59.360
 Aubrey, I'm envisioning a big highway coming through Aubrey, so that'll be interesting

00:29:59.360 --> 00:30:00.360
 to see.

00:30:00.360 --> 00:30:01.360
 There's a lot of planning going in.

00:30:01.360 --> 00:30:06.280
 Fortunately, we're working with the developers through that area.

00:30:06.280 --> 00:30:13.000
 The growth, the projected growth, it's hard to believe how much projected growth that's

00:30:13.000 --> 00:30:15.160
 coming to the area for sure.

00:30:15.160 --> 00:30:17.680
 Well, I don't have any other questions.

00:30:17.680 --> 00:30:18.680
 Thank you so much.

00:30:18.680 --> 00:30:19.680
 I appreciate your time.

00:30:19.680 --> 00:30:20.680
 Thank you, Barry.

00:30:20.680 --> 00:30:21.680
 Okay, thank you.

00:30:21.680 --> 00:30:47.920
 So we'll move on to MC 23-026, receive a report, hold a discussion and give staff direction

00:30:47.920 --> 00:30:54.480
 regarding moving the Mobility Committee meeting time from 10 to 8.

00:30:54.480 --> 00:30:56.160
 All right.

00:30:56.160 --> 00:30:57.280
 Yes, ma'am.

00:30:57.280 --> 00:30:58.840
 So we just wanted to bring this forward.

00:30:58.840 --> 00:31:04.360
 I know there was discussion about changing that as a part of some of the council meeting

00:31:04.360 --> 00:31:07.880
 that happened and then also with the new committee members.

00:31:07.880 --> 00:31:14.140
 So we have the schedule provided for you also to show the meetings that would be left.

00:31:14.140 --> 00:31:18.920
 So we would obviously have August, September, October, November, December.

00:31:18.920 --> 00:31:26.680
 Our plan is to meet the fourth Wednesday of the month except for December because that

00:31:26.680 --> 00:31:32.320
 would be during the Christmas holiday or in between, I should say, Christmas and New Year's

00:31:32.320 --> 00:31:33.720
 holidays.

00:31:33.720 --> 00:31:40.040
 So we're just asking for a direction to formally move the meeting from 10 a.m. to 8 a.m. on

00:31:40.040 --> 00:31:42.360
 that fourth Wednesday of the month.

00:31:42.360 --> 00:31:48.920
 Okay, do you have any questions, any discussion?

00:31:48.920 --> 00:31:55.640
 My understanding is where the timeframe was moving to accommodate members' schedules.

00:31:55.640 --> 00:31:59.800
 So I think that that member isn't here.

00:31:59.800 --> 00:32:00.800
 I don't know if it was here.

00:32:00.800 --> 00:32:06.260
 Was it the last member that was here that's no longer on this committee or?

00:32:06.260 --> 00:32:09.760
 Councilor McGee's schedule?

00:32:09.760 --> 00:32:15.400
 My understanding is Councilmember McGee would like to meet you at 8 a.m. so that he could

00:32:15.400 --> 00:32:19.320
 be able to attend as a part of being a part of this committee, not a previous member of

00:32:19.320 --> 00:32:20.320
 the committee.

00:32:20.320 --> 00:32:21.320
 Okay.

00:32:21.320 --> 00:32:22.320
 Okay, good.

00:32:22.320 --> 00:32:25.160
 Well, I don't have a problem with the timeframe of the schedule.

00:32:25.160 --> 00:32:26.160
 I don't either.

00:32:26.160 --> 00:32:27.160
 I'm here.

00:32:27.160 --> 00:32:28.160
 All right.

00:32:28.160 --> 00:32:30.720
 Well, I'll move that we accept the new timeframe.

00:32:30.720 --> 00:32:31.720
 Second.

00:32:31.720 --> 00:32:32.720
 Second.

00:32:32.720 --> 00:32:33.720
 All in favor?

00:32:33.720 --> 00:32:34.720
 Aye.

00:32:34.720 --> 00:32:35.720
 Aye.

00:32:35.720 --> 00:32:36.720
 All right.

00:32:36.720 --> 00:32:37.720
 Thank you.

00:32:37.720 --> 00:32:38.720
 That was pretty simple.

00:32:38.720 --> 00:32:44.720
 I'll move down to MC 23-021, staff memorandum.

00:32:44.720 --> 00:32:45.720
 Awesome.

00:32:45.720 --> 00:32:51.160
 So Trevor is going to present the first couple of items of Bonnie Bray and Hickory, and then

00:32:51.160 --> 00:32:57.120
 Brett has an entire couple of pages of items that were brought up as agenda items.

00:32:57.120 --> 00:33:01.280
 And then we'll close out with any future items that you have.

00:33:01.280 --> 00:33:03.600
 So Trevor, we'll turn it over to you.

00:33:03.600 --> 00:33:04.600
 Sure.

00:33:04.600 --> 00:33:05.600
 So good morning.

00:33:05.600 --> 00:33:06.600
 Trevor Crane, Director of Capital Projects.

00:33:06.600 --> 00:33:09.720
 So I'm going to go through the first couple, and then as Becky said, I'll turn it over

00:33:09.720 --> 00:33:13.660
 to Brett to go through the last couple.

00:33:13.660 --> 00:33:16.520
 So the first update we have is Bonnie Bray.

00:33:16.520 --> 00:33:21.960
 So Bonnie Bray Phase 3, we advertised that for bid in April.

00:33:21.960 --> 00:33:27.240
 You should see that construction contract coming to you in August, August 15th.

00:33:27.240 --> 00:33:32.440
 And then we anticipate construction beginning in Q3 of this year, pending that approval

00:33:32.440 --> 00:33:34.760
 of that contract.

00:33:34.760 --> 00:33:40.120
 Bonnie Bray Phase 6, we're on track to advertise for bid in Quarter 3 of this year.

00:33:40.120 --> 00:33:45.800
 We're working through a couple of final right-of-way issues, and then we've gotten -- we're just

00:33:45.800 --> 00:33:49.520
 waiting on the letter of approval from TxDOT.

00:33:49.520 --> 00:33:52.640
 So move -- or the state letter of authority to move forward with that.

00:33:52.640 --> 00:33:57.400
 So both of those projects are really close, and I'm sure to have those under construction

00:33:57.400 --> 00:33:59.600
 this year.

00:33:59.600 --> 00:34:03.680
 Both of those projects have an approximate two-year construction timeline and are anticipated

00:34:03.680 --> 00:34:08.680
 to be completed in Quarter 3 of 2025.

00:34:08.680 --> 00:34:14.200
 And then moving on to Hickory Creek Road Phase 3, that project's moving forward, not much

00:34:14.200 --> 00:34:16.600
 to update there.

00:34:16.600 --> 00:34:21.920
 We are estimating completion in Quarter 1 of 2025, and then the last time we talked

00:34:21.920 --> 00:34:28.080
 about there was a -- some county roadway construction going on that has been completed, and so we're

00:34:28.080 --> 00:34:31.920
 moving forward with our schedule.

00:34:31.920 --> 00:34:36.680
 And then, did y'all have any questions on those two, or you want to do those at the

00:34:36.680 --> 00:34:37.680
 end, Becky?

00:34:37.680 --> 00:34:38.680
 >> No, I'm fine.

00:34:38.680 --> 00:34:39.680
 Go ahead and ask questions.

00:34:39.680 --> 00:34:40.680
 >> Okay.

00:34:40.680 --> 00:34:41.680
 >> I have a -- I don't know.

00:34:41.680 --> 00:34:44.680
 This is a kindergarten-level question.

00:34:44.680 --> 00:34:46.560
 >> That's okay.

00:34:46.560 --> 00:34:49.720
 >> I know we talk about Phase 3 and Phase 6.

00:34:49.720 --> 00:34:53.560
 Have we done Phase 4 and 5, or what is that?

00:34:53.560 --> 00:34:59.480
 >> So Phase 4 was actually broken into two projects, 4A and 4B.

00:34:59.480 --> 00:35:00.840
 4A was the roundabout.

00:35:00.840 --> 00:35:03.360
 So that project has been completed.

00:35:03.360 --> 00:35:10.400
 4B is from -- is from I-35 to the roundabout going north.

00:35:10.400 --> 00:35:14.680
 That project is currently under design, we're at about 90%.

00:35:14.680 --> 00:35:19.140
 And then Phase 5 is from the roundabout north to 380.

00:35:19.140 --> 00:35:22.920
 That project is under design as well, about 30%.

00:35:22.920 --> 00:35:29.200
 Both of those projects we submitted as a part of the 2023 county trip funding, and that

00:35:29.200 --> 00:35:31.120
 funding was approved.

00:35:31.120 --> 00:35:34.040
 So we're moving forward with those designs right now.

00:35:34.040 --> 00:35:39.160
 We don't -- I don't really want to push those too fast, since we're about to have a portion

00:35:39.160 --> 00:35:44.020
 south of that under construction on Bonnebray and Bonnebray 6 on the north side.

00:35:44.020 --> 00:35:48.640
 So we're trying to kind of stagger out that construction so I don't have that whole corridor

00:35:48.640 --> 00:35:50.640
 under construction at the same time.

00:35:50.640 --> 00:35:55.880
 >> I was pretty basically concerned about the new population that's coming up.

00:35:55.880 --> 00:36:02.960
 I know that they're starting to build town homes and over on that Phase 5 area.

00:36:02.960 --> 00:36:03.960
 >> Yes, ma'am.

00:36:03.960 --> 00:36:07.680
 >> So we'll wait until -- it looks like we can wait until they all get settled in and

00:36:07.680 --> 00:36:09.160
 then start working on the road.

00:36:09.160 --> 00:36:10.160
 >> Right.

00:36:10.160 --> 00:36:11.680
 >> That's just kind of like a common sense type thing.

00:36:11.680 --> 00:36:15.080
 >> Yeah, as Becky said, we coordinate with all of those developers, developments as they

00:36:15.080 --> 00:36:18.960
 come in so they understand where the road's going and what type of right of way we need

00:36:18.960 --> 00:36:22.600
 and those types of things so that we're not kind of stepping on each other's toes and

00:36:22.600 --> 00:36:23.600
 those types of things.

00:36:23.600 --> 00:36:24.600
 >> Okay.

00:36:24.600 --> 00:36:25.600
 All right, do you have any other questions?

00:36:25.600 --> 00:36:30.880
 >> I do and it's one that you spurred.

00:36:30.880 --> 00:36:38.520
 For our -- any of our bridges, our roadways near riparian areas, in our pre-development,

00:36:38.520 --> 00:36:44.160
 is it the practice for our development that we have to do cultural resource management,

00:36:44.160 --> 00:36:47.320
 CRM work along those areas?

00:36:47.320 --> 00:36:49.040
 >> Sure.

00:36:49.040 --> 00:36:54.960
 So all of those projects are run through really kind of the whole gambit of all that stuff.

00:36:54.960 --> 00:37:01.280
 So we have our own -- I don't know what Christy's called, but the resource management and the

00:37:01.280 --> 00:37:03.800
 riparian buffers and all those types of things.

00:37:03.800 --> 00:37:05.980
 So they're reviewing all those plans.

00:37:05.980 --> 00:37:10.120
 They're making sure that, you know, we're not disturbing any ESAs or anything like that.

00:37:10.120 --> 00:37:13.160
 So we've had to do mitigation on other projects.

00:37:13.160 --> 00:37:16.720
 We've had to shut down projects to do archeological and those types of things.

00:37:16.720 --> 00:37:21.360
 So all of these projects are being run through -- run through the appropriate people to make

00:37:21.360 --> 00:37:23.840
 sure that we're checking all those boxes.

00:37:23.840 --> 00:37:27.840
 >> Okay, and I -- this is just more of a general question.

00:37:27.840 --> 00:37:31.920
 But because we're a government entity, we're still -- I mean, I know at the state level

00:37:31.920 --> 00:37:38.400
 you're required to do archeology and CRM work, but for funded projects, I didn't know at

00:37:38.400 --> 00:37:42.440
 the city level if we are also required to do that on our projects.

00:37:42.440 --> 00:37:44.260
 >> I think only when necessary.

00:37:44.260 --> 00:37:51.080
 So depending on where the project is, if it's in a specific location that I guess has been

00:37:51.080 --> 00:37:59.200
 slated or identified as possibly having that, then we have to do those -- we do those exploratory

00:37:59.200 --> 00:38:04.840
 and if we find something, then of course we have to continue down that path.

00:38:04.840 --> 00:38:13.040
 >> But a survey is not necessarily always part of the project generally?

00:38:13.040 --> 00:38:15.040
 >> I would say yes.

00:38:15.040 --> 00:38:16.040
 >> Okay.

00:38:16.040 --> 00:38:17.480
 That's all my questions.

00:38:17.480 --> 00:38:18.480
 >> Okay.

00:38:18.480 --> 00:38:19.480
 Perfect.

00:38:19.480 --> 00:38:22.800
 So thank you to our deputy engineer to do the next part.

00:38:22.800 --> 00:38:23.800
 Thank you.

00:38:23.800 --> 00:38:24.800
 >> All right.

00:38:24.800 --> 00:38:25.800
 Thank you.

00:38:25.800 --> 00:38:26.800
 >> All right.

00:38:26.800 --> 00:38:27.800
 Good morning.

00:38:27.800 --> 00:38:36.120
 I'm Brett Bourgeois, the deputy city engineer, and I'm here to discuss the -- you guys had

00:38:36.120 --> 00:38:39.600
 a question on the bollards that we have around the city.

00:38:39.600 --> 00:38:43.800
 So we actually have about 400 different bollard projects that we've deployed on the city,

00:38:43.800 --> 00:38:47.080
 and I'll kind of just go through each one individually and so we can kind of talk about

00:38:47.080 --> 00:38:48.080
 each one.

00:38:48.080 --> 00:38:51.420
 So the first one we're trying to talk about is the one on Old North.

00:38:51.420 --> 00:38:56.680
 That project came up from community complaints regarding speeding and kind of a confusing

00:38:56.680 --> 00:39:01.400
 roadway section where we have very wide shoulders and two drive lanes.

00:39:01.400 --> 00:39:06.200
 It's kind of a shared shoulder type of situation, so it can be parking, it can be pedestrian,

00:39:06.200 --> 00:39:10.360
 it's kind of this multi-use shoulder configuration.

00:39:10.360 --> 00:39:12.080
 So we got a lot of complaints regarding speeding.

00:39:12.080 --> 00:39:17.000
 We've had some pictures and videos of vehicles driving in the shoulder as a drive lane.

00:39:17.000 --> 00:39:19.360
 So it's kind of a confusing situation there.

00:39:19.360 --> 00:39:20.720
 So we did have community meetings.

00:39:20.720 --> 00:39:22.600
 We did put out different signage.

00:39:22.600 --> 00:39:25.920
 We tried to address the speeding with the signage.

00:39:25.920 --> 00:39:26.920
 Those were not working.

00:39:26.920 --> 00:39:28.120
 So we did have the community meeting.

00:39:28.120 --> 00:39:32.440
 We asked, you know, community feedback as to what that road characteristic they want

00:39:32.440 --> 00:39:33.440
 it to look like.

00:39:33.440 --> 00:39:34.440
 Do they want sidewalks?

00:39:34.440 --> 00:39:35.440
 Do they want bike lanes?

00:39:35.440 --> 00:39:36.440
 Do they want parking?

00:39:36.440 --> 00:39:38.320
 Do they want -- what do they want?

00:39:38.320 --> 00:39:42.040
 They kind of wanted everything, so it kind of really made a challenging situation for

00:39:42.040 --> 00:39:44.000
 us to come up with a solution.

00:39:44.000 --> 00:39:48.640
 So we came up with something kind of unique where we did a test section to try to visually

00:39:48.640 --> 00:39:53.920
 narrow the roadway intersections to get vehicles to slow down, but still provide the multi-use

00:39:53.920 --> 00:39:56.600
 functionality of that shared shoulder.

00:39:56.600 --> 00:39:58.680
 So we did a test section out there for a few months.

00:39:58.680 --> 00:40:02.040
 We studied the speeding behaviors through that test section.

00:40:02.040 --> 00:40:06.320
 We noticed the test section had a reduction in speed, but sections outside that had an

00:40:06.320 --> 00:40:10.600
 increase in speed, so we figured that's because vehicles were making up lost time for having

00:40:10.600 --> 00:40:12.160
 to slow down.

00:40:12.160 --> 00:40:15.580
 So that gave us kind of the green light to go ahead, let's put the bollards out along

00:40:15.580 --> 00:40:19.000
 the whole roadway, and let's, you know, observe it and follow it.

00:40:19.000 --> 00:40:20.800
 So we've been doing that.

00:40:20.800 --> 00:40:23.400
 We have seen a moderate reduction in speed.

00:40:23.400 --> 00:40:27.280
 It's kind of been hit and miss throughout the area, but we are continuing to monitor

00:40:27.280 --> 00:40:29.000
 it.

00:40:29.000 --> 00:40:32.160
 We did receive some complaints early on in the project.

00:40:32.160 --> 00:40:36.960
 One of the ones, I got a phone call from a resident in the neighborhood, very frustrated,

00:40:36.960 --> 00:40:40.560
 she doesn't understand the reason for it, she goes, it's not a bike lane, it's not a

00:40:40.560 --> 00:40:41.560
 parking lane.

00:40:41.560 --> 00:40:44.560
 So what this is doing, all it does is make the intersections narrower and slow people

00:40:44.560 --> 00:40:45.560
 slow down.

00:40:45.560 --> 00:40:47.460
 It's like that's exactly what we're trying to do.

00:40:47.460 --> 00:40:50.880
 That was the whole goal of the project.

00:40:50.880 --> 00:40:52.680
 So far it seems to be working.

00:40:52.680 --> 00:40:54.280
 We'll continue to watch it.

00:40:54.280 --> 00:40:59.160
 It's another tool in our toolbox to see if it can be used on other roadways.

00:40:59.160 --> 00:41:05.800
 Every roadway is kind of a different situation, so we evaluate each one as necessary.

00:41:05.800 --> 00:41:10.840
 The other one is over here on Parkway, outside here, we have the new on-street trail that

00:41:10.840 --> 00:41:12.320
 we put in.

00:41:12.320 --> 00:41:18.160
 So this was a project that was actually conceived, I want to say in 2019, by previous staff.

00:41:18.160 --> 00:41:24.040
 It got lost in the shuffle during COVID, became a lower priority, and then in 2022 we decided

00:41:24.040 --> 00:41:26.440
 to revive this project.

00:41:26.440 --> 00:41:31.240
 We looked at reconfiguring it different than what was originally conceived and come up

00:41:31.240 --> 00:41:32.860
 with a different solution.

00:41:32.860 --> 00:41:39.160
 And so when we looked at the roadway section, there was a sidewalk connectivity we have,

00:41:39.160 --> 00:41:43.680
 and the north side of Parkway there was very little sidewalk, and the south side had a

00:41:43.680 --> 00:41:45.240
 pretty significant amount of sidewalk.

00:41:45.240 --> 00:41:51.400
 So the decision was made to reconfigure the on-street trail to push it to the north side

00:41:51.400 --> 00:41:52.900
 of the roadway.

00:41:52.900 --> 00:41:55.520
 We held a community meeting, nobody attended.

00:41:55.520 --> 00:41:59.880
 We had two questions via email that we responded to, so we made a video and posted it online

00:41:59.880 --> 00:42:04.400
 about what the project's going to be and the thoughts and the ideas behind it.

00:42:04.400 --> 00:42:07.600
 And then we kicked that design off.

00:42:07.600 --> 00:42:12.240
 We had to reshuffle some staff, so the design kind of lagged a little bit, but we got the

00:42:12.240 --> 00:42:14.580
 design completed in the fall.

00:42:14.580 --> 00:42:19.120
 We held another community meeting over the winter months prior to construction.

00:42:19.120 --> 00:42:21.800
 We had a fairly significant turnout for that community meeting.

00:42:21.800 --> 00:42:26.360
 We had a bike dent and advocacy group attended the meeting, and they brought a lot of members

00:42:26.360 --> 00:42:30.700
 and they were very supportive of the project and excited to see it get installed.

00:42:30.700 --> 00:42:31.920
 We did get it installed.

00:42:31.920 --> 00:42:37.200
 The initial response was confusing at first because it was in the middle of construction,

00:42:37.200 --> 00:42:40.200
 so people didn't know how to function it yet or how to use it.

00:42:40.200 --> 00:42:45.240
 So all the construction's completed, all the punchless items are done, the ramps are completed,

00:42:45.240 --> 00:42:46.520
 the striping's all completed.

00:42:46.520 --> 00:42:52.520
 So we haven't had any complaints since the project was completed, it was just the in-construction

00:42:52.520 --> 00:42:54.080
 confusion we had.

00:42:54.080 --> 00:42:57.660
 And then we also noticed that there was some issues with vehicles and drivers not knowing

00:42:57.660 --> 00:42:59.600
 how to drive that roadway now.

00:42:59.600 --> 00:43:02.000
 We had people parking in the bike lane.

00:43:02.000 --> 00:43:05.320
 We had construction vehicles staging in the bike lane.

00:43:05.320 --> 00:43:11.720
 So it took some time for the community to learn how this roadway functions.

00:43:11.720 --> 00:43:13.900
 So far we haven't had any complaints on it.

00:43:13.900 --> 00:43:16.680
 We do see people using it because it's right outside our office.

00:43:16.680 --> 00:43:20.920
 We've had members of the Traffic Safety Commission be appreciative of it because they use it

00:43:20.920 --> 00:43:22.860
 also and they have noticed it.

00:43:22.860 --> 00:43:25.160
 So so far it's been a very successful project.

00:43:25.160 --> 00:43:30.200
 We'll continue to monitor it and look at ways to improve our overall network connectivity

00:43:30.200 --> 00:43:33.120
 for bike ped facilities around the city.

00:43:33.120 --> 00:43:37.160
 So that also supports the 10 minute walk initiative to Quaker Town Park.

00:43:37.160 --> 00:43:40.800
 So it provides a lot of benefits.

00:43:40.800 --> 00:43:44.960
 The other two, so the other ones talk about is West Hickory Street.

00:43:44.960 --> 00:43:49.280
 That's the main bike lanes down there by UNT.

00:43:49.280 --> 00:43:55.000
 So originally this project was part of the 2012-2014 bond and the project was originally

00:43:55.000 --> 00:43:58.880
 scoped as just a remove and replace the roadway.

00:43:58.880 --> 00:44:02.280
 And so when they started the first part of the project over on the east side or the west

00:44:02.280 --> 00:44:08.040
 side of Denton coming from I think Bonnie Bray or yeah, Bonnie Bray areas going west

00:44:08.040 --> 00:44:11.760
 or going east, it was just remove the road, replace the road.

00:44:11.760 --> 00:44:16.360
 But we had community feedback during construction like why are we not adding bike ped facilities?

00:44:16.360 --> 00:44:20.520
 So the decision was made to add those bike ped facilities, add the bollards and add the

00:44:20.520 --> 00:44:22.040
 bike dedicated bike lane.

00:44:22.040 --> 00:44:26.040
 It was a little bit challenging because it wasn't initially designed that way and we

00:44:26.040 --> 00:44:30.000
 didn't have the right of way necessary to make it a continuous path on the east on the

00:44:30.000 --> 00:44:31.960
 west side of the project.

00:44:31.960 --> 00:44:34.360
 The project was cut into two halves.

00:44:34.360 --> 00:44:41.360
 The second half kicked off continuing that bike lane from Welch, Welch Street was the

00:44:41.360 --> 00:44:42.360
 cutoff point.

00:44:42.360 --> 00:44:43.360
 Yeah.

00:44:43.360 --> 00:44:46.440
 So from Welch Street all the way to Carroll, the bike lane was designed as part of it to

00:44:46.440 --> 00:44:48.040
 make it continuous.

00:44:48.040 --> 00:44:51.280
 So they actually did a pretty good job of trying to fit this into the field.

00:44:51.280 --> 00:44:55.240
 It wasn't initially scoped that way or designed that way, but we did get it all in.

00:44:55.240 --> 00:44:59.320
 It seems to be a very successful project, especially down there in the UNT area with

00:44:59.320 --> 00:45:00.880
 a lot of pedestrians.

00:45:00.880 --> 00:45:07.000
 Unfortunately, we don't have pre-numbers or pre-analysis of what it was used before

00:45:07.000 --> 00:45:08.000
 to where it is now.

00:45:08.000 --> 00:45:14.640
 So we can't really just talk about the effectiveness of it other than just observations and empirical

00:45:14.640 --> 00:45:15.640
 data.

00:45:15.640 --> 00:45:20.160
 So we don't have anything where to compare previous conditions to existing conditions.

00:45:20.160 --> 00:45:23.720
 And then the other one is on Hinkle Drive and that was kind of a similar situation where

00:45:23.720 --> 00:45:28.560
 it was part of the 2012, 2014 bond and it was actually a drainage project.

00:45:28.560 --> 00:45:31.320
 And the goal was to put the roadway back the way it was.

00:45:31.320 --> 00:45:34.040
 But the community said, "Hey, why don't you add another bike lane here?"

00:45:34.040 --> 00:45:36.840
 And it provides connectivity up to North Lakes Park.

00:45:36.840 --> 00:45:42.080
 It provides connectivity up to Windsor Street, which is a fairly good bike ped corridor with

00:45:42.080 --> 00:45:43.960
 a lot of facilities on it.

00:45:43.960 --> 00:45:48.220
 And it also connects to the shopping center down off of 380 and Hinkle.

00:45:48.220 --> 00:45:54.740
 So the decision was made to add the bike lane on that project during construction again.

00:45:54.740 --> 00:46:00.160
 We actually had the right-of-way width, the road width, so we shifted parking to one side

00:46:00.160 --> 00:46:04.040
 and put bike lane on the east side of Hinkle.

00:46:04.040 --> 00:46:08.280
 And so again, that was kind of an infield change decision during construction.

00:46:08.280 --> 00:46:12.680
 So that was, again, wasn't designed or intended that way, but we made it work and was able

00:46:12.680 --> 00:46:15.200
 to incorporate that now.

00:46:15.200 --> 00:46:18.220
 Lessons learned from those two projects is that we always look at bike ped facilities

00:46:18.220 --> 00:46:19.840
 now whenever we do a project.

00:46:19.840 --> 00:46:25.680
 So these are ones that were historic, were originally scoped and funded.

00:46:25.680 --> 00:46:30.040
 Not to include those, but we were able to accommodate them, and everything we do going

00:46:30.040 --> 00:46:34.100
 forward is including bike ped facilities.

00:46:34.100 --> 00:46:36.640
 And then...

00:46:36.640 --> 00:46:38.920
 Are you saying bike ped facilities?

00:46:38.920 --> 00:46:39.920
 Yes.

00:46:39.920 --> 00:46:40.920
 Oh, okay.

00:46:40.920 --> 00:46:47.520
 Yes, that could be a side path, on-street trail, bike lanes, including some form of

00:46:47.520 --> 00:46:52.080
 multimodal access besides just vehicles.

00:46:52.080 --> 00:46:58.400
 And then to give an update on the hiring of our senior planner, bicycle pedestrian ADA

00:46:58.400 --> 00:47:01.960
 coordinator position, we've had a pool of candidates.

00:47:01.960 --> 00:47:03.920
 We've conducted many interviews.

00:47:03.920 --> 00:47:09.400
 We've actually extended two offers to two different candidates, both declined for reasons

00:47:09.400 --> 00:47:10.800
 outside of our control.

00:47:10.800 --> 00:47:15.440
 One had actually both personal reasons as to why they declined.

00:47:15.440 --> 00:47:18.320
 So unfortunately, we haven't been able to fill that role.

00:47:18.320 --> 00:47:24.280
 During that time, we've decided to pull down the application to revise the job description,

00:47:24.280 --> 00:47:25.280
 to repost it.

00:47:25.280 --> 00:47:28.820
 And we're looking at the different organization structure and who's going to report to and

00:47:28.820 --> 00:47:34.920
 how the city is going to function, and we're going to repost that position and fill that.

00:47:34.920 --> 00:47:35.920
 Any other questions?

00:47:35.920 --> 00:47:36.920
 Any questions?

00:47:36.920 --> 00:47:47.840
 Yes, I have a question, are there any bike pit connecting to one another at all right

00:47:47.840 --> 00:47:48.840
 now?

00:47:48.840 --> 00:47:52.360
 Or is everything just, it looks like there's things just this here and over here and over

00:47:52.360 --> 00:47:53.360
 here and over there.

00:47:53.360 --> 00:47:58.000
 Does anything connect to another path at all yet?

00:47:58.000 --> 00:48:03.560
 So in terms of the dedicated baller projects, none of those are actually connected right

00:48:03.560 --> 00:48:07.560
 now, but they do connect to other bike ped facilities.

00:48:07.560 --> 00:48:13.880
 So for example, is we're working on a project that we have funded through DCTA trip funding

00:48:13.880 --> 00:48:18.680
 to improve sidewalks along Carroll, which will provide the connection from West Hickory

00:48:18.680 --> 00:48:21.200
 along Carroll to the Parkway area.

00:48:21.200 --> 00:48:25.680
 So it's not going to be a ballered bike ped project, but it's going to be improved sidewalks

00:48:25.680 --> 00:48:26.680
 along there.

00:48:26.680 --> 00:48:31.440
 So when we look at the overall network connectivity, we don't just look at the ballered bike lanes,

00:48:31.440 --> 00:48:37.280
 we look at the side paths, the sidewalks, the on-street bike trails, the shared lanes

00:48:37.280 --> 00:48:40.920
 to make sure we have a network of different facilities.

00:48:40.920 --> 00:48:45.160
 They might not all look the same, but it's a way that people can navigate the city either

00:48:45.160 --> 00:48:50.400
 by bicycle or walking.

00:48:50.400 --> 00:49:01.200
 Do you all have a priority list for what's going to be next?

00:49:01.200 --> 00:49:02.620
 How do you all work that?

00:49:02.620 --> 00:49:06.920
 Do you just wait until somebody calls in with a complaint or?

00:49:06.920 --> 00:49:07.920
 No.

00:49:07.920 --> 00:49:13.040
 So we do have a sidewalk work plan, which we did outlining the condition of all the

00:49:13.040 --> 00:49:17.320
 sidewalks and the bicycle pedestrian facilities throughout the city.

00:49:17.320 --> 00:49:20.960
 So we have areas that we know are deficient and areas that we know are in pretty good

00:49:20.960 --> 00:49:21.960
 condition.

00:49:21.960 --> 00:49:25.000
 And then we look at the areas that we have gaps that we don't have anything.

00:49:25.000 --> 00:49:30.400
 And so these projects are much more cost effective if we bundle them with roadway projects because

00:49:30.400 --> 00:49:34.520
 you're mobilizing construction equipment, having to do check down a roadway a lot of

00:49:34.520 --> 00:49:35.520
 times.

00:49:35.520 --> 00:49:41.400
 So we try to bundle our projects with roadway projects and to get more bang for our buck.

00:49:41.400 --> 00:49:47.120
 So we can come in and build new side paths, new sidewalks, new bike trails at the same

00:49:47.120 --> 00:49:49.600
 time that we're reconstructing our roadway.

00:49:49.600 --> 00:49:53.600
 And so every project that we look at from a roadway is, okay, we need to add bike ped

00:49:53.600 --> 00:49:54.600
 facilities here.

00:49:54.600 --> 00:49:57.240
 Does it need to be a side path on which side of the road?

00:49:57.240 --> 00:50:00.080
 Does it need to be a bike lane on what side of the road?

00:50:00.080 --> 00:50:03.560
 How's that going to connect to our existing infrastructure?

00:50:03.560 --> 00:50:08.760
 Sometimes what we do is that we also fund through like the DCTA trip funding where we

00:50:08.760 --> 00:50:11.600
 look at, okay, what is our bike ped connectivity?

00:50:11.600 --> 00:50:13.200
 What are projects that can improve that?

00:50:13.200 --> 00:50:16.180
 We submit those projects to DCTA.

00:50:16.180 --> 00:50:18.160
 We've won many of them.

00:50:18.160 --> 00:50:22.640
 We are working through those and designing construction on a lot of those right now.

00:50:22.640 --> 00:50:24.800
 So we have some on loop 288 that we're doing.

00:50:24.800 --> 00:50:28.160
 We have the one at Carroll Boulevard that we're designing.

00:50:28.160 --> 00:50:32.720
 We're filling in those gaps as best we can.

00:50:32.720 --> 00:50:38.280
 We do have a goal for the overall bike ped network.

00:50:38.280 --> 00:50:44.440
 We want to make a continuous, think of us like a wheel, like a north-south connectivity

00:50:44.440 --> 00:50:48.560
 from downtown through the city and east-west connectivity and then build out from there.

00:50:48.560 --> 00:50:49.680
 Oh, that sounds cool.

00:50:49.680 --> 00:50:51.360
 So we're working towards that.

00:50:51.360 --> 00:50:56.560
 That's part of all these projects are eventually going to build out to a complete network.

00:50:56.560 --> 00:51:01.720
 It's just we're trying to take advantage of tacking onto other projects and other bigger

00:51:01.720 --> 00:51:06.800
 projects where our contribution is smaller to the overall project scope versus having

00:51:06.800 --> 00:51:09.720
 to pay a higher mobilization costs, all the other kind of things.

00:51:09.720 --> 00:51:10.720
 All right.

00:51:10.720 --> 00:51:11.720
 Thank you so much.

00:51:11.720 --> 00:51:16.600
 I wanted to also mention that the mobility plan and ADA transition plan is also being

00:51:16.600 --> 00:51:18.760
 evaluated throughout all of these projects.

00:51:18.760 --> 00:51:27.620
 So we're looking at where their specific projects that were either listed in that massive list

00:51:27.620 --> 00:51:34.440
 of projects for the ADA transition plan or on the mobility plan because we have a map

00:51:34.440 --> 00:51:37.000
 specifically to bicycle or pedestrian.

00:51:37.000 --> 00:51:38.160
 Those are all evaluations.

00:51:38.160 --> 00:51:42.040
 So we have that as a part of our planning phase when we go through projects.

00:51:42.040 --> 00:51:45.960
 As Brett mentioned though, right now we're seeing a lot of success with adding them to

00:51:45.960 --> 00:51:52.560
 existing projects and then also allocating funding with those DCTA trip projects.

00:51:52.560 --> 00:51:58.040
 I asked Trevor to come up really quickly so that he could talk about the PPI index, which

00:51:58.040 --> 00:51:59.980
 is the scoring we use for sidewalks.

00:51:59.980 --> 00:52:02.160
 So I thought that would be something he could explain.

00:52:02.160 --> 00:52:07.240
 And as you talked about a work plan, that's kind of how we actually facilitate the order

00:52:07.240 --> 00:52:09.800
 of which the projects are moved forward.

00:52:09.800 --> 00:52:10.800
 Right.

00:52:10.800 --> 00:52:14.620
 So as you can imagine, we get a lot of requests for sidewalks and those types of things.

00:52:14.620 --> 00:52:20.080
 So we wanted to be able to put some data behind and have some data-driven decisions as far

00:52:20.080 --> 00:52:25.520
 as where we spend that money that we get instead of just kind of being reactive and going out

00:52:25.520 --> 00:52:27.000
 and fixing this spot and this spot.

00:52:27.000 --> 00:52:33.380
 So what we did is we worked with a consultant to create what we call a PPI score.

00:52:33.380 --> 00:52:39.960
 And what it does is it takes into account proximity to, let's say, a school or a DCTA

00:52:39.960 --> 00:52:47.760
 bus stop, or I think there's seven different criteria where we find what they call like

00:52:47.760 --> 00:52:50.680
 a goat path, where people are walking where there's no path.

00:52:50.680 --> 00:52:55.280
 So all those things are rated, there's all these scores, and then we give each of those

00:52:55.280 --> 00:53:00.040
 sidewalks a rating, how many of those criteria they meet, and then depending on how many

00:53:00.040 --> 00:53:04.020
 they meet, that brings it up or down that sidewalk work plan.

00:53:04.020 --> 00:53:09.400
 So that's really how we try to prioritize those sidewalks so that we're making those

00:53:09.400 --> 00:53:17.320
 data-driven decisions, trying to address the areas that need to be addressed first that

00:53:17.320 --> 00:53:18.320
 show the highest need.

00:53:18.320 --> 00:53:19.320
 Okay.

00:53:19.320 --> 00:53:20.320
 Thank you.

00:53:20.320 --> 00:53:21.320
 Yes, ma'am.

00:53:21.320 --> 00:53:22.320
 All right.

00:53:22.320 --> 00:53:23.320
 Go ahead.

00:53:23.320 --> 00:53:24.320
 So many questions.

00:53:24.320 --> 00:53:25.320
 So many questions.

00:53:25.320 --> 00:53:26.320
 Especially for Brett.

00:53:26.320 --> 00:53:27.320
 Yes.

00:53:27.320 --> 00:53:28.320
 Yes.

00:53:28.320 --> 00:53:31.320
 Let me start with the last first.

00:53:31.320 --> 00:53:34.000
 I'm glad that you two brought up the PPI index.

00:53:34.000 --> 00:53:38.120
 I was going to bring it up, so I appreciate that.

00:53:38.120 --> 00:53:44.480
 Before the destination planning, the desire path planning that's going on that correlates

00:53:44.480 --> 00:53:50.160
 with the PPI, is that in one of our GIS layers, or do we have it as a static map that we can

00:53:50.160 --> 00:53:56.600
 get out to the public where we can say, "Yes, here's the bike ped map you're already familiar

00:53:56.600 --> 00:54:03.160
 with, but here's sort of our prioritization based on PPI that we can get out so people

00:54:03.160 --> 00:54:08.440
 can start changing their behavior in advance of the mobility plan rolling out?"

00:54:08.440 --> 00:54:09.440
 Yes.

00:54:09.440 --> 00:54:14.880
 So we do have a sidewalk work plan story map, which goes to GIS connected, showing all the

00:54:14.880 --> 00:54:18.480
 sidewalks what the rankings are in terms of the PPI score.

00:54:18.480 --> 00:54:23.040
 And then the one thing that we are working on is updating that map as projects are completed.

00:54:23.040 --> 00:54:26.440
 We actually just got a GIS technician not too long ago, so we're getting through and

00:54:26.440 --> 00:54:30.880
 getting all the past projects completed that we've done onto that story map, onto that

00:54:30.880 --> 00:54:32.120
 GIS layer.

00:54:32.120 --> 00:54:38.040
 And as we do projects, we'll make sure we update them or revise that map as necessary.

00:54:38.040 --> 00:54:45.360
 I think the other thing I would add is there are several different, I guess, pieces of

00:54:45.360 --> 00:54:47.880
 data or data sets.

00:54:47.880 --> 00:54:52.680
 And so you have the mobility plan, and it has kind of a plan, a pie in the sky, "Hey,

00:54:52.680 --> 00:54:54.120
 this is our dream."

00:54:54.120 --> 00:54:57.320
 And then you have a sidewalk work plan that says, "This is the areas of which we think

00:54:57.320 --> 00:54:59.180
 we need to have projects."

00:54:59.180 --> 00:55:02.880
 And then you have the projects that are being planned through the capital program.

00:55:02.880 --> 00:55:07.640
 You have the projects that Ethan's team is doing from a maintenance and operation standpoint.

00:55:07.640 --> 00:55:08.920
 You have existing sidewalk.

00:55:08.920 --> 00:55:09.920
 You have gaps.

00:55:09.920 --> 00:55:15.040
 We have developers that were saying, "No, you can't develop without building a sidewalk."

00:55:15.040 --> 00:55:17.900
 There's a lot of competing things that are happening all at once.

00:55:17.900 --> 00:55:23.680
 So with Ryan Drumgold, our GIS technician, he has actually been taking all that data

00:55:23.680 --> 00:55:26.320
 and putting it into one GIS layer.

00:55:26.320 --> 00:55:31.520
 I think to your point, kind of after we're all confident and we're working through kind

00:55:31.520 --> 00:55:38.120
 of that QA/QC right now, and a lot of this is due to the filing having an individual

00:55:38.120 --> 00:55:43.480
 has the ability to make this thing happen, one, so we're very happy to have that staff,

00:55:43.480 --> 00:55:47.560
 but two, you know, seeing the big picture and pulling all these different documentations

00:55:47.560 --> 00:55:53.400
 together, you know, working through the bicycle and pedestrian safety audit, also being able

00:55:53.400 --> 00:55:55.560
 to explain and kind of talk through that story.

00:55:55.560 --> 00:56:00.840
 I think the next step for us would be, and maybe I'm maybe reading into more of what

00:56:00.840 --> 00:56:05.840
 you're saying than I should be, but I think maybe the next area where I'd like to really

00:56:05.840 --> 00:56:11.320
 focus is, as Brett was mentioning, as those projects are completed, having that more as

00:56:11.320 --> 00:56:16.400
 an outward-facing, "Hey, I'm bike-ditting or I'm a part of the bicycle community.

00:56:16.400 --> 00:56:17.680
 Here's a route I can take."

00:56:17.680 --> 00:56:21.120
 So our goal would be if you're on the south side of town, how do you get to the north

00:56:21.120 --> 00:56:28.240
 side of the town, east to the west, or I get off the DCTA A train down by Hickory Street,

00:56:28.240 --> 00:56:32.320
 kind of more on the, I guess, middle part of town, but I want to get to UNT or I want

00:56:32.320 --> 00:56:36.840
 to get to TWU, can I click on a map, click on a layer, and it show me the network so

00:56:36.840 --> 00:56:39.800
 I know what is the existing network that I could use?

00:56:39.800 --> 00:56:41.360
 So I think that would be our next step.

00:56:41.360 --> 00:56:42.360
 That is where it was going.

00:56:42.360 --> 00:56:43.360
 Okay.

00:56:43.360 --> 00:56:44.360
 Well, I was reading your mind.

00:56:44.360 --> 00:56:45.360
 Very ambitious.

00:56:45.360 --> 00:56:52.560
 No, and I think it's just, I mean, so that there's pent-up demand and people want to

00:56:52.560 --> 00:57:00.520
 be able to, well, a section of our community wants to be able to make better use of any

00:57:00.520 --> 00:57:06.960
 lessening of the density on the roadways is going to be good for many departments.

00:57:06.960 --> 00:57:16.760
 For the Old North, full disclosure, I am the community feedback that they were referencing.

00:57:16.760 --> 00:57:23.800
 I'm not the only one, but I was the funnel for lots of people along the Old North corridor,

00:57:23.800 --> 00:57:34.520
 and I did send in the pictures, but a couple of questions on that regard in, I know one

00:57:34.520 --> 00:57:39.000
 of the things that, before Nathan left, that we were talking about is alternative striping

00:57:39.000 --> 00:57:45.620
 plans that would augment some of what you found with the bollards.

00:57:45.620 --> 00:57:51.320
 Is that sort of down the road a bit while we wait on this new position, or we're moving

00:57:51.320 --> 00:57:57.920
 ahead with concepts about alternative striping, like one bike lane, one park lane, or, you

00:57:57.920 --> 00:58:02.200
 know, he mentioned a lot of things, so this is, I understand it's not a concrete thing.

00:58:02.200 --> 00:58:03.200
 Yeah.

00:58:03.200 --> 00:58:09.400
 So, when we looked at the layout for Old North, we did evaluate, you know, different alternatives

00:58:09.400 --> 00:58:13.880
 in terms of at least conceptually how would it look to put a different bike lane or put

00:58:13.880 --> 00:58:15.160
 a parking.

00:58:15.160 --> 00:58:19.720
 The feedback we got was pretty much consistent, that everybody wanted parking on both sides,

00:58:19.720 --> 00:58:23.800
 they wanted bike lanes on both sides, they wanted sidewalks on both sides, and we couldn't

00:58:23.800 --> 00:58:30.360
 really make all that happen without taking right of way to add sidewalks, so the first

00:58:30.360 --> 00:58:35.640
 step was to put the bollards at the intersections to try to reduce the traffic speed and to

00:58:35.640 --> 00:58:40.200
 provide a physical barrier to prevent vehicles from driving in that lane as a drive lane,

00:58:40.200 --> 00:58:41.200
 essentially.

00:58:41.200 --> 00:58:44.000
 We haven't gone to the next step yet in looking at the striping.

00:58:44.000 --> 00:58:47.320
 We're evaluating how the performance of the bollards are.

00:58:47.320 --> 00:58:50.400
 Once we do get the bike ped coordinated around, we will definitely go back and look at that

00:58:50.400 --> 00:58:54.760
 situation and work with our transportation planning department in terms of what else

00:58:54.760 --> 00:58:55.760
 can be done.

00:58:55.760 --> 00:59:00.480
 We actually did just hire a transportation engineer again, so he'll help out in that

00:59:00.480 --> 00:59:05.160
 process of looking at alternatives for that roadway as well.

00:59:05.160 --> 00:59:10.000
 I appreciate that, and so some feedback I got from the community is they've noticed

00:59:10.000 --> 00:59:15.600
 the speed dropping anecdotally because they're not out there with radars, but it does seem

00:59:15.600 --> 00:59:21.240
 like they're positive to me about that.

00:59:21.240 --> 00:59:25.400
 One of the things, and I've mentioned this to Trevor, I don't know, half a dozen times,

00:59:25.400 --> 00:59:29.880
 they don't like the look of them.

00:59:29.880 --> 00:59:30.880
 I know.

00:59:30.880 --> 00:59:37.960
 I don't know what we have in the way of different visual options.

00:59:37.960 --> 00:59:40.720
 They do have to be a safety-related item.

00:59:40.720 --> 00:59:41.720
 They do need to be reflective.

00:59:41.720 --> 00:59:43.520
 They do need to be visible.

00:59:43.520 --> 00:59:46.960
 If we make them blend in too much, then obviously people, they're not going to function.

00:59:46.960 --> 00:59:54.560
 People are not going to see them, so we are kind of limited on those aspects of it.

00:59:54.560 --> 00:59:59.320
 We can look into other options or other alternatives and see what else is available.

00:59:59.320 --> 01:00:03.880
 We'd have to do some research on that and see what other options are available in terms

01:00:03.880 --> 01:00:04.880
 of colorations.

01:00:04.880 --> 01:00:08.520
 I mean, I don't know, white and yellow and orange are kind of the standard colors because

01:00:08.520 --> 01:00:10.600
 they provide high contrast and high visibility.

01:00:10.600 --> 01:00:16.080
 You don't like my pinwheels that I taped to the ones outside my yard?

01:00:16.080 --> 01:00:23.320
 I shouldn't admit that on video tape.

01:00:23.320 --> 01:00:27.240
 The next question, well, not question, comment.

01:00:27.240 --> 01:00:33.320
 Like you, I got a lot of positive, not early on positive feedback, but later positive feedback

01:00:33.320 --> 01:00:35.960
 on the parkway striping.

01:00:35.960 --> 01:00:40.760
 Just lots of people stopped me and said they're really stoked and happy about that.

01:00:40.760 --> 01:00:44.280
 I don't know what sort of feedback you all have been getting, but I'm adding to that

01:00:44.280 --> 01:00:49.480
 that it's filtering up to counsel that they like that.

01:00:49.480 --> 01:00:55.040
 We take it, usually we only hear complaints, so we don't get a lot of positive feedback.

01:00:55.040 --> 01:01:00.120
 When we see complaints significantly drop off, we're assuming that the functionality

01:01:00.120 --> 01:01:04.280
 is good and people like it, so we take that as a good sign that people are adapting to

01:01:04.280 --> 01:01:08.800
 it and enjoying the facilities.

01:01:08.800 --> 01:01:20.360
 Let's see, let's skip that one because that's just an extra comment.

01:01:20.360 --> 01:01:28.260
 The question I had was about the bike lane right away and pathing there near the roundabout

01:01:28.260 --> 01:01:30.000
 in Hinkle.

01:01:30.000 --> 01:01:36.040
 All that is resolved with the neighbor in the tree that had to come out and all that

01:01:36.040 --> 01:01:37.320
 settled down.

01:01:37.320 --> 01:01:40.680
 I haven't honestly driven through the roundabout in a while.

01:01:40.680 --> 01:01:41.880
 Yes, that's all been taken care of.

01:01:41.880 --> 01:01:47.480
 The tree was removed, the sidewalk's been installed and that's been done, I don't know,

01:01:47.480 --> 01:01:52.440
 Danny, six months, eight, a couple of months, so two years, okay, so it's been longer than

01:01:52.440 --> 01:01:53.440
 I thought.

01:01:53.440 --> 01:01:54.440
 I don't remember.

01:01:54.440 --> 01:01:55.440
 Apparently I haven't driven down Hinkle in a while.

01:01:55.440 --> 01:01:56.440
 It's been two years.

01:01:56.440 --> 01:01:57.440
 Or my time here.

01:01:57.440 --> 01:01:58.440
 Or I didn't pay attention.

01:01:58.440 --> 01:01:59.440
 I have gone to the movie theater.

01:01:59.440 --> 01:02:04.440
 I drive up and down Windsor and Hinkle, so I have gone to the movie theater, so I have

01:02:04.440 --> 01:02:07.600
 driven it, but I guess I didn't pay attention.

01:02:07.600 --> 01:02:09.080
 James is keeping us honest this morning.

01:02:09.080 --> 01:02:10.080
 I don't remember either.

01:02:10.080 --> 01:02:14.600
 I do remember it coming to council, but I don't remember the timeframe, so thank you, James.

01:02:14.600 --> 01:02:17.600
 That's fair and now I'm embarrassed.

01:02:17.600 --> 01:02:18.600
 Me too.

01:02:18.600 --> 01:02:20.200
 Time is not our friend.

01:02:20.200 --> 01:02:30.160
 On the bike ped coordinator, I know you there at the end, you mentioned that there might

01:02:30.160 --> 01:02:36.400
 be some restructuring or Brett mentioned that there might be some restructuring of the org

01:02:36.400 --> 01:02:44.400
 chart a little bit, but so do we have any, I don't recall you mentioning a timeframe

01:02:44.400 --> 01:02:51.240
 for when that was happening and the only reason I bring this up at all is I know that Nathan

01:02:51.240 --> 01:02:58.240
 had started a lot of positively received activities, you know, positive inside the department,

01:02:58.240 --> 01:03:05.520
 positive in the community and I want to make sure that we maintain the momentum that Nathan

01:03:05.520 --> 01:03:13.360
 developed and that we don't sort of lose that as we restructure, so you know, it's more

01:03:13.360 --> 01:03:17.440
 of a please more comment than anything else.

01:03:17.440 --> 01:03:18.440
 Sure.

01:03:18.440 --> 01:03:20.120
 Nathan did an excellent job.

01:03:20.120 --> 01:03:21.960
 We were very sad to see him go.

01:03:21.960 --> 01:03:28.580
 He did write an entire document of all of the things that he saw, positive, negative.

01:03:28.580 --> 01:03:31.940
 We have all of his information projects.

01:03:31.940 --> 01:03:37.680
 We coordinate heavily with transportation planning and as those things are rolled out

01:03:37.680 --> 01:03:41.960
 through the city manager's office of any modifications that they'll be making organizationally,

01:03:41.960 --> 01:03:48.160
 positions, et cetera, I know that those will be things that you'll be made aware of, but

01:03:48.160 --> 01:03:54.260
 we don't anticipate slowing down the momentum, only to grow with the additional staff if

01:03:54.260 --> 01:03:57.880
 that is what moves forward.

01:03:57.880 --> 01:04:02.800
 So I think the good thing is that there are still several of us here that worked with

01:04:02.800 --> 01:04:07.680
 Nathan and as those opportunities, whether that's a new individual, et cetera, we'll

01:04:07.680 --> 01:04:12.200
 still continue working through those things, so definitely want to keep moving that in

01:04:12.200 --> 01:04:17.220
 the right direction and keep that momentum and I think a lot of these ideas and things

01:04:17.220 --> 01:04:23.560
 that have been worked on, Brett mentioned several of them today, you have to keep in

01:04:23.560 --> 01:04:29.720
 mind one of the things is not only have we adopted the mobility plan, the comp plan,

01:04:29.720 --> 01:04:34.080
 the parks trials master plan, the other thing is is TechStats now made it standard on their

01:04:34.080 --> 01:04:39.720
 projects as of November of 2021 that they're going to allow for sidewalks and side paths,

01:04:39.720 --> 01:04:41.320
 so that's not even something standard.

01:04:41.320 --> 01:04:44.360
 So it's an entire mind frame shift.

01:04:44.360 --> 01:04:47.800
 You'll see projects still being constructed today that are not taking those things into

01:04:47.800 --> 01:04:54.000
 consideration because they were designed six years ago, five years ago, or they're using

01:04:54.000 --> 01:04:58.800
 federal funding and you can't make modifications to the plans at the state that they're in,

01:04:58.800 --> 01:05:03.080
 but you'll see where our entire team, that is just a part of our checklist.

01:05:03.080 --> 01:05:04.720
 How are we doing BikePed?

01:05:04.720 --> 01:05:07.360
 How are we doing the multimodal approach?

01:05:07.360 --> 01:05:12.160
 So it's definitely something that has kind of changed the way we think and then we're

01:05:12.160 --> 01:05:17.280
 also making those things similarly happen with TechStat and with the county.

01:05:17.280 --> 01:05:23.600
 So I don't know how this committee works if we put items on the matrix, so I'll revisit

01:05:23.600 --> 01:05:28.840
 this at the end if that's how this committee works, but yes, we're about to go through

01:05:28.840 --> 01:05:29.840
 that.

01:05:29.840 --> 01:05:36.040
 Then I will just put a placeholder for, since we're talking about sidewalks, to discuss

01:05:36.040 --> 01:05:43.540
 a side path from the shelter to 380 on the matrix if that's not already in the works.

01:05:43.540 --> 01:05:46.540
 So I'll hold that for later.

01:05:46.540 --> 01:05:48.560
 So I think, Brett, that's all you have, correct?

01:05:48.560 --> 01:05:52.280
 I just have one more question, I'm sorry, and I'm just thinking about it.

01:05:52.280 --> 01:06:00.160
 I'm thinking about a developer had noted that the sidewalks within the development is five

01:06:00.160 --> 01:06:09.480
 feet wide, and outside the development there was a request to do 10 feet wide.

01:06:09.480 --> 01:06:15.120
 And is that something, is this what you're talking about, that the state has changed

01:06:15.120 --> 01:06:20.400
 its course about how wide sidewalks should be as part of a development?

01:06:20.400 --> 01:06:26.220
 So the state will not be doing typical projects along developments because their corridors

01:06:26.220 --> 01:06:32.440
 are mainly larger roadways, where that conversation comes in many times is, there is existing

01:06:32.440 --> 01:06:37.360
 sidewalk that's been put in place, but we have city standard details and specifications

01:06:37.360 --> 01:06:42.760
 that dictate what should be constructed in what areas based on the mobility plan.

01:06:42.760 --> 01:06:47.560
 So you may see a five foot sidewalk that's connecting to a 10 foot side path because

01:06:47.560 --> 01:06:52.960
 the city has plans and a future date to change that five foot sidewalk to a 10 foot side

01:06:52.960 --> 01:06:53.960
 path.

01:06:53.960 --> 01:06:58.760
 So we will ask the developers to build things according to our code and criteria that match

01:06:58.760 --> 01:07:04.960
 our overall master plans, whether it be the mobility plan, the comprehensive plan, knowing

01:07:04.960 --> 01:07:10.240
 that at some later date there may be a modification made to that existing five foot sidewalk.

01:07:10.240 --> 01:07:15.240
 So we're having people build to the plan or the standard.

01:07:15.240 --> 01:07:20.900
 In most cases, there are some that are not, but in most cases that would be in conjunction

01:07:20.900 --> 01:07:26.760
 with the criteria manuals, specifications, and standard details.

01:07:26.760 --> 01:07:27.760
 Thank you very much.

01:07:27.760 --> 01:07:28.760
 Thank you.

01:07:28.760 --> 01:07:29.760
 All righty.

01:07:29.760 --> 01:07:30.760
 Moving on.

01:07:30.760 --> 01:07:37.760
 Exhibit two.

01:07:37.760 --> 01:07:40.120
 All righty.

01:07:40.120 --> 01:07:43.460
 So go through the matrix really quickly.

01:07:43.460 --> 01:07:48.720
 So deployment of bicycle bollards, we're asking to remove that.

01:07:48.720 --> 01:07:53.680
 That item we brought to you today, along with the status of the hiring of the bicycle and

01:07:53.680 --> 01:07:56.560
 pedestrian ADA coordinator.

01:07:56.560 --> 01:07:57.720
 That's a long title.

01:07:57.720 --> 01:08:01.000
 So we're asking to remove both of those.

01:08:01.000 --> 01:08:05.800
 And then of course, Bonnie Bray and Hickory Creek Road phase three, Trevor will continue

01:08:05.800 --> 01:08:09.900
 to bring those updates to you monthly.

01:08:09.900 --> 01:08:14.820
 This is more for you, Mayor Pro Tembeck, is that Ryan Road, we leave this on here kind

01:08:14.820 --> 01:08:16.720
 of as a future agenda item.

01:08:16.720 --> 01:08:20.800
 I think you're very aware that we're going to hold on doing Ryan Road until Hickory Creek

01:08:20.800 --> 01:08:26.160
 is completed, because that is the major east-west corridor.

01:08:26.160 --> 01:08:33.660
 And then lastly, the TxDOT response for the citywide speed study speed limit changes.

01:08:33.660 --> 01:08:36.920
 Brett has had some conversations recently with TxDOT.

01:08:36.920 --> 01:08:43.500
 They've asked us for graphical representations of some of the corridors, but we're waiting

01:08:43.500 --> 01:08:45.600
 on their overall feedback.

01:08:45.600 --> 01:08:50.560
 And those are specific to those TxDOT roadways that were a part of the speed study.

01:08:50.560 --> 01:08:56.000
 So once we received that back, they had given us kind of a six to eight month time frame.

01:08:56.000 --> 01:09:01.060
 And then they've also asked for some additional data recently, but have not given us a final

01:09:01.060 --> 01:09:03.500
 time frame when they anticipate being completed with that.

01:09:03.500 --> 01:09:05.360
 But when that is completed, we will bring that forward.

01:09:05.360 --> 01:09:12.340
 So we leave it on here so that we don't forget one and two, we bring it back to you.

01:09:12.340 --> 01:09:19.480
 So the only other thing that I was going to mention, it's not really a future staff report

01:09:19.480 --> 01:09:27.760
 item specifically, but we will want to bring forward at the next meeting the chair, vice

01:09:27.760 --> 01:09:28.760
 chair.

01:09:28.760 --> 01:09:33.240
 And so we will be bringing that forward to you.

01:09:33.240 --> 01:09:36.720
 And I think that that is everything that I have.

01:09:36.720 --> 01:09:41.120
 So if you agree with removing those two, we'll remove those.

01:09:41.120 --> 01:09:44.440
 And then, of course, we'd love to hear anything else that you'd like to see at the next meeting.

01:09:44.440 --> 01:09:45.440
 Okay.

01:09:45.440 --> 01:09:47.240
 What do you think about removing those two?

01:09:47.240 --> 01:09:49.500
 Are you satisfied with it?

01:09:49.500 --> 01:09:54.600
 It sounds like you are, I mean, we can always bring things back if we have concerns or point

01:09:54.600 --> 01:09:55.600
 issues.

01:09:55.600 --> 01:09:57.040
 So absolutely.

01:09:57.040 --> 01:10:01.320
 How it kind of works, just so you understand is, is we use this time frame for you to bring

01:10:01.320 --> 01:10:05.020
 forward anything you'd like for us to report on the next month.

01:10:05.020 --> 01:10:08.600
 And then if we've reported on it, we request to remove it if it's something that we want

01:10:08.600 --> 01:10:12.620
 to bring to you monthly, we'll continue to bring to you monthly.

01:10:12.620 --> 01:10:16.400
 And then if there's things that come up kind of in between the two meeting timeframes, we

01:10:16.400 --> 01:10:20.920
 ask that you bring that forward when we have this meeting so that we can make sure because

01:10:20.920 --> 01:10:23.080
 if it's not on posting, we can't really talk about it.

01:10:23.080 --> 01:10:25.240
 So we want to make sure that it's on the agenda item.

01:10:25.240 --> 01:10:26.880
 The same doesn't get us.

01:10:26.880 --> 01:10:27.880
 Yes, sir.

01:10:27.880 --> 01:10:28.880
 He's tough.

01:10:28.880 --> 01:10:31.760
 I believe that we're in agreement to remove one and two.

01:10:31.760 --> 01:10:32.760
 Wonderful.

01:10:32.760 --> 01:10:33.760
 Thank you very much.

01:10:33.760 --> 01:10:39.720
 And for have just a couple of questions about a few streets here.

01:10:39.720 --> 01:10:41.360
 The first one is Oakland Street.

01:10:41.360 --> 01:10:48.240
 I know that we talked about bollards and bike paths and, and all of that, but that street,

01:10:48.240 --> 01:10:55.260
 I like to know where it is in terms of an overlay or replacement or I mean, it's a really

01:10:55.260 --> 01:10:56.520
 rough street right there.

01:10:56.520 --> 01:10:57.520
 Absolutely.

01:10:57.520 --> 01:10:59.120
 All the way around to Locust Street.

01:10:59.120 --> 01:11:01.040
 Yes, we have lots of plans for that.

01:11:01.040 --> 01:11:04.800
 So we can definitely bring you back and I really love that.

01:11:04.800 --> 01:11:14.000
 And then I am also understanding that there is another multifamily development that is

01:11:14.000 --> 01:11:22.240
 in the works to come up over on Spencer at that Walmart and on the other side of that

01:11:22.240 --> 01:11:28.120
 luxury apartment complex across the street from the senior Villa.

01:11:28.120 --> 01:11:38.720
 But the question is, is, will this new structure, will it affect the roadway in some kind of

01:11:38.720 --> 01:11:39.720
 way?

01:11:39.720 --> 01:11:46.240
 Will there be, will we put this road on some type of list to be done?

01:11:46.240 --> 01:11:47.240
 Things to do list.

01:11:47.240 --> 01:11:48.240
 Okay.

01:11:48.240 --> 01:11:54.240
 So specifically Spencer Road between between a 28 Mayhill and Mayhill.

01:11:54.240 --> 01:11:55.240
 Okay.

01:11:55.240 --> 01:11:56.240
 Sure.

01:11:56.240 --> 01:11:58.040
 We can bring that forward because there's going to be more traffic on that road.

01:11:58.040 --> 01:12:06.400
 And then a car apartment complex come up also, you know, one street that really just kind

01:12:06.400 --> 01:12:12.400
 of perplexes me is Windsor because there's like Windsor Road is four or five different

01:12:12.400 --> 01:12:13.680
 streets.

01:12:13.680 --> 01:12:19.520
 You know, it's just, and some have the pipe bike paid, but when we get to the park, it's

01:12:19.520 --> 01:12:22.520
 just down to those two lanes.

01:12:22.520 --> 01:12:27.080
 Is there any, is there something going on with that right now?

01:12:27.080 --> 01:12:29.520
 I do, I just need to add that to the list.

01:12:29.520 --> 01:12:33.040
 So there are projects happening along Windsor also.

01:12:33.040 --> 01:12:38.120
 So we're happy to bring that back to you so we can explain kind of the West Gate Windsor

01:12:38.120 --> 01:12:43.720
 and that project also as it coordinates with Bonnie Bray face six.

01:12:43.720 --> 01:12:47.680
 And then of course the fire station right there that's a part of the bond program.

01:12:47.680 --> 01:12:51.680
 So we can bring forward kind of an overall update of Windsor and kind of talk to you

01:12:51.680 --> 01:12:52.880
 about future planning.

01:12:52.880 --> 01:12:57.460
 I know Brett talked about Hinkle to Windsor, but you're talking kind of from that area

01:12:57.460 --> 01:13:01.840
 all the way due West to 35 and the improvements on 35.

01:13:01.840 --> 01:13:03.380
 We can bring that back.

01:13:03.380 --> 01:13:05.520
 That's not what's going on there.

01:13:05.520 --> 01:13:19.320
 And also I'm not sure if this is in the loop as well, but I've always been, not loop, but

01:13:19.320 --> 01:13:23.840
 downtown backing in parking.

01:13:23.840 --> 01:13:27.900
 Can you all bring us some conversation in that regard?

01:13:27.900 --> 01:13:33.600
 I particularly don't care for it, but I just want to know what the community is thinking

01:13:33.600 --> 01:13:36.200
 about the backing in.

01:13:36.200 --> 01:13:42.120
 I know it hadn't always been that way and then there was a request to make it that way.

01:13:42.120 --> 01:13:48.720
 And so I'm curious now as to what the feedback is from that now that we have new community

01:13:48.720 --> 01:13:52.320
 members, more people have moved in.

01:13:52.320 --> 01:13:56.800
 I'm noticing people are actually pulling in more than backing in here lately.

01:13:56.800 --> 01:14:01.320
 So I like to have that on our radar as well.

01:14:01.320 --> 01:14:02.620
 Sure we can absolutely do that.

01:14:02.620 --> 01:14:08.360
 We just gave that update to Traffic Safety Commission.

01:14:08.360 --> 01:14:10.800
 Yeah it'll be fun to hear.

01:14:10.800 --> 01:14:16.640
 I should go review that update from Traffic Safety.

01:14:16.640 --> 01:14:23.760
 I buy the rationale for the backing in parking, but I know that now there's literally like

01:14:23.760 --> 01:14:32.560
 75,000 people in both camps who love or hate the backing in parking.

01:14:32.560 --> 01:14:33.560
 So I won't cover that.

01:14:33.560 --> 01:14:41.840
 A couple of things that I wanted to bring up are, well we discussed a lot of them today

01:14:41.840 --> 01:14:44.880
 that were sort of my top of mind issues with Brett.

01:14:44.880 --> 01:14:47.200
 I appreciate it was very timely.

01:14:47.200 --> 01:14:49.760
 I'm going to give you credit for doing that on purpose with new membership.

01:14:49.760 --> 01:14:55.240
 Even if it was not planned, if it was already in the cycle, I'm going to say no, you guys

01:14:55.240 --> 01:15:00.380
 are forward thinking and proactive so you're going to get credit for that.

01:15:00.380 --> 01:15:04.920
 The ones that I was interested in, I know that you're engaged in a citywide parking

01:15:04.920 --> 01:15:09.520
 study because I've been talking with Scott about that and the reason I bring this up

01:15:09.520 --> 01:15:16.680
 is there's both downtown parking and citywide parking and I bring this up because I've been

01:15:16.680 --> 01:15:27.600
 in discussions with the Oak Street historical community and they're very interested in being

01:15:27.600 --> 01:15:37.120
 a pilot for future whatever we design as a parking standard because of their ongoing

01:15:37.120 --> 01:15:46.560
 concerns with competition, with student parking for UNT.

01:15:46.560 --> 01:15:51.600
 So I'd love to hear some updates from, I've heard some of the development updates, I'd

01:15:51.600 --> 01:15:55.920
 love to hear some of the mobility and engineering updates for the citywide parking and the downtown

01:15:55.920 --> 01:16:02.240
 parking and then I guess this isn't an item for, well it might become an item for next

01:16:02.240 --> 01:16:03.640
 time.

01:16:03.640 --> 01:16:13.560
 Wherever we get to on the bond meeting, particularly I guess the big ones will be Rudel and Mingo,

01:16:13.560 --> 01:16:19.240
 however that shakes out after the August 1st meeting, we'll probably need to have an update

01:16:19.240 --> 01:16:26.440
 on how that changes forward planning going after that depending on where we go.

01:16:26.440 --> 01:16:31.120
 So if the timing is right and it aligns with the August meeting, great, sounds like it

01:16:31.120 --> 01:16:36.120
 might because we're going to meet at the beginning of the month so we should, hopefully that's

01:16:36.120 --> 01:16:42.080
 enough weeks for you to prepare for the end of the month, if not then subsequent month

01:16:42.080 --> 01:16:47.880
 about how that impacts forward planning in the Rudel and Mingo corridor and how that

01:16:47.880 --> 01:16:50.360
 changes things, whatever we decide.

01:16:50.360 --> 01:16:54.800
 So I'm purposely leaving that nebulous but I'm going to ask for it regardless of whatever

01:16:54.800 --> 01:16:55.800
 the state is.

01:16:55.800 --> 01:17:01.800
 Sure, yeah we can definitely bring that to you after the meeting on the 1st and depending

01:17:01.800 --> 01:17:05.360
 on which way it goes, what our anticipations will be.

01:17:05.360 --> 01:17:12.720
 Alrighty, so I have seven different things to talk about.

01:17:12.720 --> 01:17:18.840
 One of the things that I would like to bring forward to you as a staff report update and

01:17:18.840 --> 01:17:23.960
 I don't anticipate that it will be August but one of the things that's on my radar is

01:17:23.960 --> 01:17:29.200
 kind of what we talked about with the mapping and showing you kind of that overall sidewalk

01:17:29.200 --> 01:17:34.680
 and bicycle corridor, just actually visually showing it to you and allowing Ryan that opportunity

01:17:34.680 --> 01:17:41.360
 to present that and kind of walk through some of those ideas just so you can see.

01:17:41.360 --> 01:17:45.400
 I think it makes a lot of sense to be able to show you kind of those GIS layers and then

01:17:45.400 --> 01:17:50.560
 I think one of the things I'd like to do is kind of make it a goal that we talk about

01:17:50.560 --> 01:17:56.720
 kind of that outward facing, we focus a lot on developers, capital, those types of plans

01:17:56.720 --> 01:18:01.200
 of how are we coordinating and planning for the future and making sure we're coordinating

01:18:01.200 --> 01:18:06.700
 with developers but I do think it's very important to make sure that those who are using the

01:18:06.700 --> 01:18:12.240
 different pieces of infrastructure have that opportunity also and we have done things like

01:18:12.240 --> 01:18:17.320
 that with Waze in the past so kind of thinking in those terms of if I go on my smartphone

01:18:17.320 --> 01:18:22.000
 and press walk or bike, how does that populate to show me this is the route and that's kind

01:18:22.000 --> 01:18:23.160
 of where my head is with that.

01:18:23.160 --> 01:18:27.000
 I don't know if that's kind of what you're thinking Mayor Breton but something I'm going

01:18:27.000 --> 01:18:28.000
 to.

01:18:28.000 --> 01:18:32.660
 Any education, outreach and training forward facing to the public, awesome, more the merrier.

01:18:32.660 --> 01:18:35.840
 So that's kind of where I'm headed with that but I'm not thinking that we're going to

01:18:35.840 --> 01:18:40.440
 be ready for that in August but I do think that that's something that I'd like to bring

01:18:40.440 --> 01:18:42.920
 back definitely before the end of the year.

01:18:42.920 --> 01:18:48.320
 All righty, well that's everything that I have.

01:18:48.320 --> 01:18:49.520
 We appreciate it.

01:18:49.520 --> 01:18:53.640
 Will, are there any concluding items, Dr. Beck?

01:18:53.640 --> 01:18:59.640
 I will just say thank you for bringing me up to speed on some of these items.

01:18:59.640 --> 01:19:00.640
 I appreciate that.

01:19:00.640 --> 01:19:03.400
 Give me a couple of meetings and I'll be right there with you.

01:19:03.400 --> 01:19:10.360
 I try to be, I try to do my homework so I appreciate everybody's indulgence while we

01:19:10.360 --> 01:19:13.600
 do the change.

01:19:13.600 --> 01:19:18.800
 Well we will declare that this meeting is over at 9.19.

01:19:18.800 --> 01:19:20.760
 Awesome, thank you.