WEBVTT

00:00:00.000 --> 00:00:08.800
 good morning we're going we are here at the mobility committee for the city of

00:00:08.800 --> 00:00:16.000
 dead and Wednesday September 27 2023 a 8m in the council work session room it

00:00:16.000 --> 00:00:21.280
 looks like we have a quorum present I will convene the meeting starting at 8

00:00:21.280 --> 00:00:29.120
 a.m. do we have any citizen comments on any of the agenda items okay so we'll

00:00:29.120 --> 00:00:37.760
 move on to number two items work excuse me individual consideration AMC 2 3

00:00:37.760 --> 00:00:45.120
 days 0 3 9 consider approval of the minutes for August 23rd 2023 we have a

00:00:45.120 --> 00:00:56.920
 motion for approval and I'll second and so all in favor the second one be we

00:00:56.920 --> 00:01:08.500
 will see in here MC 2 3 days 0 4 7 of a staff memorandum good morning Trevor

00:01:08.500 --> 00:01:12.320
 crane director of capital projects so I'll go through a couple of project

00:01:12.320 --> 00:01:18.520
 updates so bonnie bray road bonnie bray phase 3 of course was awarded the Sun

00:01:18.520 --> 00:01:22.960
 construction on August 16th those to proceed is anticipated to be issued on

00:01:22.960 --> 00:01:28.440
 October 16th 2023 and that project has a 30-month construction schedule so

00:01:28.440 --> 00:01:37.280
 bonnie bray 3 is from rose lawn drive to FM 1515 interstate 35 bonnie bray phase

00:01:37.280 --> 00:01:42.880
 6 that's from us 380 to us 77 we're on track to advertise for bids in quarter

00:01:42.880 --> 00:01:47.440
 4 of 2023 we've been working through comments with text dot over the probably

00:01:47.440 --> 00:01:51.040
 the last eight months we're really close to getting the state letter of authority

00:01:51.040 --> 00:01:57.480
 to move that project into bidding so right now the last date I saw was

00:01:57.480 --> 00:02:02.200
 November to have that ready to bid out once we get the state letter of

00:02:02.200 --> 00:02:06.000
 authority we'll kind of look at that project don't typically like to put

00:02:06.000 --> 00:02:10.680
 projects out to bid during December a lot of contractors kind of hanging up

00:02:10.680 --> 00:02:14.360
 during the holiday season so we'll look at that date want to make sure we get

00:02:14.360 --> 00:02:18.280
 good bids in on that so we may delay that bidding till early next year we'll

00:02:18.280 --> 00:02:25.240
 just take a look at it so okay Hickory Creek phase 3 update so we're

00:02:25.240 --> 00:02:29.960
 currently in active construction the contractor on that is Mario Sinicola and

00:02:29.960 --> 00:02:34.640
 sons has a two-year construction timeline so still estimated completion in

00:02:34.640 --> 00:02:42.400
 quarter one of 2025 and that is all I have on project updates any questions on

00:02:42.400 --> 00:02:51.000
 Bonnie Bray Hickory Creek phase 3 thank you

00:02:51.000 --> 00:03:10.320
 all righty so one of the requests that was made was to discuss the accidents or

00:03:10.320 --> 00:03:14.960
 data that we had received on downtown back-end parking along the Hickory

00:03:14.960 --> 00:03:20.080
 Grand Street project and so our staff worked with the police department to

00:03:20.080 --> 00:03:25.760
 look at those accidents that had occurred along East Hickory since

00:03:25.760 --> 00:03:30.480
 implementing that back-end parking between Locust and Bell Avenue there are

00:03:30.480 --> 00:03:36.920
 no specific parking related contributing factors which could be related to back

00:03:36.920 --> 00:03:41.480
 in parking specifically so when the reports are taken it's not saying this

00:03:41.480 --> 00:03:45.600
 accident occurred due to the fact that someone was trying to back in parking

00:03:45.600 --> 00:03:51.080
 but the table below which I'll show you right here shows the number of crashes

00:03:51.080 --> 00:03:55.480
 that have happened in that area but it cannot be attributed or specifically

00:03:55.480 --> 00:03:59.360
 related to the fact that it is back in parking it's just the number of crashes

00:03:59.360 --> 00:04:06.960
 that have happened within that roadway area so hopefully that answers some of

00:04:06.960 --> 00:04:10.880
 the questions that were asked and we have none for 2023 that have been

00:04:10.880 --> 00:04:17.760
 reported and then I guess in 2022 we had two you can see and when it was first

00:04:17.760 --> 00:04:24.840
 under implementation and it was brand-new 2015 2016 2017 you can see

00:04:24.840 --> 00:04:31.760
 there's five and then of course in 2019 six but as far as the actual reports

00:04:31.760 --> 00:04:35.680
 from the police department and they're not showing you can see that in the

00:04:35.680 --> 00:04:39.880
 report that there's no specific parking related contributing factor that says

00:04:39.880 --> 00:04:47.160
 the back-end parking caused whatever the accident was I don't know if you would

00:04:47.160 --> 00:04:53.000
 like to take his question take questions you have any questions they do on these

00:04:53.000 --> 00:04:57.620
 on these reports did it did it say in the incident report whether these were

00:04:57.620 --> 00:05:03.720
 vehicle and vehicle interactions vehicle and pedestrian did it mention when you

00:05:03.720 --> 00:05:07.640
 looked them up I mean the numbers are low so essentially we're looking at edge

00:05:07.640 --> 00:05:13.960
 cases regardless but I'm just curious and it was specific accident crash data so

00:05:13.960 --> 00:05:18.800
 those typically are a vehicular in the information we receive from the police

00:05:18.800 --> 00:05:21.480
 department but to be a hundred percent correct I'll have to check on that

00:05:21.480 --> 00:05:25.760
 information and get back to you I did not collect the data myself make sense

00:05:25.760 --> 00:05:30.560
 that no I think one of the reasons I was I was asking for the data is to

00:05:30.560 --> 00:05:36.520
 establish whether it was actually a problem and and it sounds like maybe in

00:05:36.520 --> 00:05:43.540
 2019 for whatever reason people are free from COVID and driving around or

00:05:43.540 --> 00:05:50.220
 something but but otherwise it looks like there it's pretty well an edge case

00:05:50.220 --> 00:05:55.360
 no matter whether it's vehicle and vehicle or vehicle and pedestrian unless

00:05:55.360 --> 00:05:59.200
 of course you guys come back and tell me oh well there's a bunch of vehicle and

00:05:59.200 --> 00:06:03.720
 pedestrian accidents that are not in the table and that's 20 or 30 or something

00:06:03.720 --> 00:06:11.680
 like that it sounds like regardless of sort of the cultural discomfort of back

00:06:11.680 --> 00:06:18.520
 in parking it's not a source of problem for the police is what I'm interpreting

00:06:18.520 --> 00:06:25.840
 that as okay and also I'm thinking that 2019 we were just going into COVID so

00:06:25.840 --> 00:06:29.960
 people were probably just kind of out of their minds at the time that's a very

00:06:29.960 --> 00:06:36.800
 high number six which regardless of if it's a was backed in or someone pulled

00:06:36.800 --> 00:06:41.660
 in so I think that we're we're addressing this because we're noticing

00:06:41.660 --> 00:06:48.120
 that more people are pulling in rather than backing in I'm not sure what they

00:06:48.120 --> 00:06:53.960
 enforcement level of that is do you have any idea whether or not the police

00:06:53.960 --> 00:07:03.040
 department is recognize that and is it forcing it more or and the individuals

00:07:03.040 --> 00:07:06.680
 who are pulling in instead of backing in that is not something the police

00:07:06.680 --> 00:07:11.720
 department is currently enforcing if there are individuals that are in that

00:07:11.720 --> 00:07:15.640
 area that are actually patrolling in that area and see something that's of

00:07:15.640 --> 00:07:19.720
 concern of course they're going to take care of the situation but as far as an

00:07:19.720 --> 00:07:23.240
 enforcement it's not something that they have individuals that are spending time

00:07:23.240 --> 00:07:26.960
 they're particularly focusing on the enforcement of whether folks are

00:07:26.960 --> 00:07:33.000
 actually pulling into the parking space or backing in do we do we still have

00:07:33.000 --> 00:07:39.400
 those what are those people called not the ambassadors but I think they work

00:07:39.400 --> 00:07:44.800
 for the police department and they would do parking my my understanding is is

00:07:44.800 --> 00:07:49.920
 that's not something that is currently ongoing okay that we do not have those

00:07:49.920 --> 00:07:55.320
 individuals that are currently it was a parking enforcement team essentially and

00:07:55.320 --> 00:07:59.960
 they did it all over downtown etc people waited you know some of those signs say

00:07:59.960 --> 00:08:04.280
 you can only park for two hours etc but my understanding is we don't have that

00:08:04.280 --> 00:08:08.600
 type of enforcement okay well I don't have any other questions or comments or

00:08:08.600 --> 00:08:15.000
 concerns all righty well let's move on to the future items for mobility so we

00:08:15.000 --> 00:08:18.440
 brought to you today the downtown back-end parking I'm gonna make a

00:08:18.440 --> 00:08:23.440
 statement my assumption is that was all vehicular if we happen to find that I'm

00:08:23.440 --> 00:08:28.320
 incorrect I'm gonna bring that item back to you and if not then I'm gonna request

00:08:28.320 --> 00:08:32.200
 that we remove that specific because we provided you the data and I'll get that

00:08:32.200 --> 00:08:39.080
 clarification the citywide downtown parking study we will bring back to you

00:08:39.080 --> 00:08:44.160
 as soon as that information is available ITS report I know you're very interested

00:08:44.160 --> 00:08:48.640
 in what's happening between loop 288 and the 380 connection and they're still

00:08:48.640 --> 00:08:52.360
 ongoing conversations we actually have a meeting next week with the consultant

00:08:52.360 --> 00:08:56.520
 and tech start it's not ready to bring forward to you yet as they're receiving

00:08:56.520 --> 00:08:59.700
 and still going through all the comments that were received from the public

00:08:59.700 --> 00:09:05.000
 meeting in late July but as soon as that is available I'm going to ask that they

00:09:05.000 --> 00:09:09.160
 bring that forward I also want to mention while we're on the ITS report

00:09:09.160 --> 00:09:13.840
 mr. pollster sends his regards for him not to be able to be here today to

00:09:13.840 --> 00:09:18.080
 actually make his presentation but the entire mobility report and that he

00:09:18.080 --> 00:09:24.200
 prepares will be in your Friday report this month this week and then the mapping

00:09:24.200 --> 00:09:28.640
 first sidewalk bike corridor staff is still working on all those GIS mapping

00:09:28.640 --> 00:09:32.160
 layers and as soon as we have that information where we feel like it's

00:09:32.160 --> 00:09:35.320
 ready to bring forward we're gonna bring that forward to you

00:09:35.320 --> 00:09:40.840
 Trevor gave you the update on Hickory Creek and Bonnie Bray Ryan Road we won't

00:09:40.840 --> 00:09:46.280
 bring anything forward until we're and the ending stages of Hickory Creek and

00:09:46.280 --> 00:09:50.940
 then Brett is still working through the text dot responses for the citywide

00:09:50.940 --> 00:09:54.640
 speed study so since we have that information so some of these are just

00:09:54.640 --> 00:10:00.200
 ongoing as we have the information so we don't lose their spot but currently not

00:10:00.200 --> 00:10:04.440
 additional information to report and so now we'd like to see if there's anything

00:10:04.440 --> 00:10:07.720
 else that you would like to bring forward for us to add to the agenda for

00:10:07.720 --> 00:10:14.680
 next month yeah real quick question it was it was dr.

00:10:14.680 --> 00:10:18.840
 Butts that that is taking over bikeped with dev services or engineering or

00:10:18.840 --> 00:10:23.320
 combo is that correct or I'm misunderstanding the role that position

00:10:23.320 --> 00:10:27.440
 has been moved to the transportation services group but all of the

00:10:27.440 --> 00:10:32.720
 transportation planning specific responsibilities has is still in the

00:10:32.720 --> 00:10:36.840
 process of being worked out okay all right and the reason I ask is

00:10:36.840 --> 00:10:44.720
 coming back to the the GIS layers do can do you have a list of the the

00:10:44.720 --> 00:10:48.720
 variables that you're gonna be putting into those layers that that should be

00:10:48.720 --> 00:10:53.680
 straightforward that we could get so I so I could see if I was wanting to ask

00:10:53.680 --> 00:10:58.740
 about additional variables to include in the layers or not so when you say

00:10:58.740 --> 00:11:02.120
 variables talk to me more about what you're asking because in the layer

00:11:02.120 --> 00:11:09.440
 specifically the GIS mapping part of what's happening is the roadways are

00:11:09.440 --> 00:11:15.240
 broken down into sections based on block and it is we're working on breaking them

00:11:15.240 --> 00:11:19.200
 down to where you actually have individual layers that are specific for

00:11:19.200 --> 00:11:23.440
 sidewalk on both sides of the roadway so it's a little bit more detailed to try

00:11:23.440 --> 00:11:27.420
 to break it down it looks at the asset from a GIS layer perspective as just

00:11:27.420 --> 00:11:30.840
 the roadways so now we're working on adding that layer to where it can be

00:11:30.840 --> 00:11:35.760
 specified with having its own identifier of the of the actual sidewalk along the

00:11:35.760 --> 00:11:40.040
 mapping system perfect that that's exactly you do this every week you

00:11:40.040 --> 00:11:45.440
 anticipate parts of my question are we separating this the sidewalk layers from

00:11:45.440 --> 00:11:50.080
 the street layers yeah and then the other things I was curious about I'll

00:11:50.080 --> 00:11:53.720
 just give you enough for instance of why I'm asking this question is are there

00:11:53.720 --> 00:12:01.040
 things like the these are certain timings or certain projected speedways

00:12:01.040 --> 00:12:09.360
 because I know some of the street data included vehicular speed limits but like

00:12:09.360 --> 00:12:15.680
 we you all also estimate the pedestrian traffic speeds at certain intersections

00:12:15.680 --> 00:12:21.260
 as well or the crossing times that came up in council Tuesday so what I guess

00:12:21.260 --> 00:12:28.120
 I'm curious what kinds of variables are in the you're projected because you don't

00:12:28.120 --> 00:12:32.960
 map every single nuance of data that you can mine out of the GIS that's it's too

00:12:32.960 --> 00:12:37.720
 much you you have typical variable sets so I guess what I'm asking is what's

00:12:37.720 --> 00:12:41.680
 your variable set that you're you're using in your your day-to-day business

00:12:41.680 --> 00:12:47.760
 and and if I could get that kind of understanding sure then it may be then

00:12:47.760 --> 00:12:50.500
 everything I'm interested is already there and then I just ask you what the

00:12:50.500 --> 00:12:57.400
 number is sure so specifically related to the GIS layer itself our goal is to

00:12:57.400 --> 00:13:02.680
 map every asset that we have every sidewalk that we have we'll also want to

00:13:02.680 --> 00:13:06.520
 work towards mapping every bike lane that's already within the system that

00:13:06.520 --> 00:13:12.120
 goal is to then be able to take those into a work order system that we

00:13:12.120 --> 00:13:17.000
 already have currently which we use as cardiograph to be able to say whether or

00:13:17.000 --> 00:13:21.600
 not there's any maintenance or repair that needs to be done to that system for

00:13:21.600 --> 00:13:25.800
 example there might be a crosswalk or there might be a bike lane that needs to

00:13:25.800 --> 00:13:31.360
 be updated so our goal is to actually tie that the GIS layer to the individual

00:13:31.360 --> 00:13:36.880
 asset so then we can develop work plans associated with God bless you works work

00:13:36.880 --> 00:13:40.200
 plans associated with the actual maintenance repair that needs to be

00:13:40.200 --> 00:13:45.400
 performed and I would say as far as signal timing and those things some of

00:13:45.400 --> 00:13:51.360
 the results of the bike pet audit are to we already have worksheets that we're

00:13:51.360 --> 00:13:55.080
 using and we already have a process that we're doing but then we're going to want

00:13:55.080 --> 00:13:59.920
 to be able to tie that information to that specific asset so our goal would be

00:13:59.920 --> 00:14:05.240
 is if we go and look at McKinney Street between you know whatever Bell and

00:14:05.240 --> 00:14:10.240
 whatever that we can say this is where a sidewalk is this is where a bike lane is

00:14:10.240 --> 00:14:14.120
 this is where there's the pedestrian and hybrid beacon crossing right here we've

00:14:14.120 --> 00:14:18.880
 maintained it every six months or once a year whatever the standard is associated

00:14:18.880 --> 00:14:23.360
 with that so we are working to try to develop the GIS layer to be able to give

00:14:23.360 --> 00:14:27.480
 the asset identifier information that will then help form our work plans

00:14:27.480 --> 00:14:34.680
 associated with that if that makes sense yes it does and and so I mean yeah no

00:14:34.680 --> 00:14:41.180
 just I won't reiterate just if we if I could get a list of the what you the

00:14:41.180 --> 00:14:49.840
 types of commonplace layers not what you're capable of but what you're you

00:14:49.840 --> 00:14:55.280
 just typically throw out then then I'd be interested in that and and and then

00:14:55.280 --> 00:15:00.440
 maybe note what you what you might put public in versus what you keep in house

00:15:00.440 --> 00:15:07.840
 okay so when we bring back the sidewalk by corridor information that is when

00:15:07.840 --> 00:15:12.880
 we'll go into detail as to here's the layers that were created etc so a lot of

00:15:12.880 --> 00:15:16.720
 that has already been mapped it's just now taking all those finite pieces and

00:15:16.720 --> 00:15:20.360
 putting them all together and that's why I don't want to ask questions if the

00:15:20.360 --> 00:15:24.080
 data I mean I don't mind asking questions but I don't want to ask for an

00:15:24.080 --> 00:15:28.080
 activity if you already have it sure all I have to do is say hey can I get a

00:15:28.080 --> 00:15:33.640
 paragraph report on that you know sure I don't want to put anybody out doing a

00:15:33.640 --> 00:15:37.880
 new thing that isn't a new thing no for sure no I completely understand and I

00:15:37.880 --> 00:15:41.920
 think that part of that mapping like I said when we bring that back is to

00:15:41.920 --> 00:15:47.960
 describe kind of what goes into without having a foundational GIS layer it's

00:15:47.960 --> 00:15:52.080
 hard to build and identify the asset and then it's hard to make a work plan

00:15:52.080 --> 00:15:54.960
 associated with that whether it be a maintenance or whether it be a

00:15:54.960 --> 00:15:59.480
 completely new reconstruction and then also mapping that with the mobility plan

00:15:59.480 --> 00:16:03.680
 and all the different multimodal elements of the mobility plan so I

00:16:03.680 --> 00:16:06.880
 understand where you're going and happy to bring that forward when we're ready

00:16:06.880 --> 00:16:18.440
 thank you yes sir anything else I know that there was some issues over in

00:16:18.440 --> 00:16:26.240
 southeast didn't in regards to Bradshaw Street in in East Prairie Street along

00:16:26.240 --> 00:16:34.840
 the way near the park in and I know that there was it had something to do with it

00:16:34.840 --> 00:16:43.520
 had rained in the complainants were concerned about not being able to get

00:16:43.520 --> 00:16:47.560
 out of the neighborhood I know that you all may have heard that Seth understands

00:16:47.560 --> 00:16:55.960
 that got immediate action on that but the question now becomes for me is are

00:16:55.960 --> 00:17:03.880
 the same people it's the same company during the entire area or do you all

00:17:03.880 --> 00:17:10.960
 use different contractors for different locations when we're updating the

00:17:10.960 --> 00:17:17.160
 streets one of the streets had a failure in it in it and somebody got stuck in

00:17:17.160 --> 00:17:22.120
 the mud in the other street sure and someone wasn't able to get out out of

00:17:22.120 --> 00:17:30.000
 the neighborhood or the regular route in their street so my question is because

00:17:30.000 --> 00:17:35.760
 we haven't had a a complainant you know of this nature from the other parts of

00:17:35.760 --> 00:17:43.920
 the community how did this happen and how did this happen in regards to is it

00:17:43.920 --> 00:17:49.720
 the same contractor or is it another contractor for that area so to get into

00:17:49.720 --> 00:17:52.960
 the specifics I think we'll need to bring that back as a future item I would

00:17:52.960 --> 00:17:57.400
 just say as a general statement those types of situations happen all over the

00:17:57.400 --> 00:18:01.120
 city you may just be more aware of the situation because it's directly in your

00:18:01.120 --> 00:18:07.360
 district and then I would say as far as contractors every single project either

00:18:07.360 --> 00:18:12.000
 goes through a Seymour process or a competitive still proposal process and

00:18:12.000 --> 00:18:18.040
 the general contractor can be different and is different throughout the city we

00:18:18.040 --> 00:18:22.280
 have lots of contractors working in the city so if you want specific information

00:18:22.280 --> 00:18:27.080
 about the southeast didn't bond program then we can have Trevor bring that

00:18:27.080 --> 00:18:32.340
 information back to you and and I would tell you that the concerns that you're

00:18:32.340 --> 00:18:36.120
 bringing to our attention or things that we were already aware of and on top of

00:18:36.120 --> 00:18:41.400
 and working to try to resolve but in general there are multiple contractors

00:18:41.400 --> 00:18:46.240
 working and they hire multiple subcontractors and some of the concerns

00:18:46.240 --> 00:18:50.000
 you're bringing forward those are all a part of our specifications with

00:18:50.000 --> 00:18:53.920
 warranties associated with work and that's why we put a two-year warranty on

00:18:53.920 --> 00:19:02.880
 all of our projects so and they oh how long two years and then this is my

00:19:02.880 --> 00:19:08.400
 kindergarten level question okay I'd recognize that they're bollards on

00:19:08.400 --> 00:19:13.720
 Oakland Street and I know that we use bollards on on other parts of the

00:19:13.720 --> 00:19:20.200
 streets on North you know on North Road but my question is and I wanted to say

00:19:20.200 --> 00:19:23.760
 it for this meeting so there may be other people that have this question my

00:19:23.760 --> 00:19:31.560
 question is is that if there's bollards on Oakland Street only on one side is it

00:19:31.560 --> 00:19:40.680
 expected for the cyclists to use that street going in either direction or if a

00:19:40.680 --> 00:19:45.600
 cyclist is says going north on Oakland Street and there are no bollards there

00:19:45.600 --> 00:19:53.280
 but the bollards are here for the riders on the south side how does

00:19:53.280 --> 00:19:57.480
 something like that work are they on the other bicyclists in the bollards on the

00:19:57.480 --> 00:20:03.760
 south side even if they're going north or does that play a role in how we put

00:20:03.760 --> 00:20:07.960
 bollards now if there wasn't any bollards and it was just a street with

00:20:07.960 --> 00:20:15.160
 just a line and you see bikes bike lane that wouldn't pique my interest but

00:20:15.160 --> 00:20:20.360
 because of the nature of this situation over on Oakland Street sure we're in the

00:20:20.360 --> 00:20:25.240
 Parkland we can bring back to you bike etiquette and what they're supposed to

00:20:25.240 --> 00:20:29.720
 be doing the short answer to your question is is if the bollards are there

00:20:29.720 --> 00:20:34.280
 they're supposed to be riding in it no matter which direction they're going and

00:20:34.280 --> 00:20:38.160
 we can't force people to do that but that's what they're supposed to be doing

00:20:38.160 --> 00:20:44.160
 and so that's the reason why there's that large bike lane so that it can be

00:20:44.160 --> 00:20:48.760
 multimodal whether you're walking or biking and it is for it to be used in

00:20:48.760 --> 00:20:58.080
 both directions it would seem to me that the necessary steps to take for that to

00:20:58.080 --> 00:21:04.120
 be a true situation for all for all locations is that those bollards would

00:21:04.120 --> 00:21:11.400
 be literally down the entire street but these bollards just start and then they

00:21:11.400 --> 00:21:21.080
 stop between Congress and Carroll so you know I just say just pique my interest I

00:21:21.080 --> 00:21:25.640
 drive through that way and and and that was just for me but I'm sure other folks

00:21:25.640 --> 00:21:30.360
 may be interested in that topic as well thank you for that sure we can bring

00:21:30.360 --> 00:21:33.680
 that back to you I know we've talked about Oakland before but we can kind of

00:21:33.680 --> 00:21:38.560
 show you the overall plan of that road specifically and how they are to

00:21:38.560 --> 00:21:46.240
 traverse and what really bike etiquette is in that area no problem also let's

00:21:46.240 --> 00:21:54.080
 bring back something for more street I just don't see any movement in regards to

00:21:54.080 --> 00:21:59.920
 slowing that street down I know you do know that there are reminders you know

00:21:59.920 --> 00:22:04.920
 you have those lighted reminders on the side of how fast you're going is and I

00:22:04.920 --> 00:22:09.800
 just want to know if that is all they're going to get there I have not heard any

00:22:09.800 --> 00:22:14.000
 additional complaints from there we used to hear about a lot of complaints at one

00:22:14.000 --> 00:22:19.880
 time but something's happening over there to keep them from not you know

00:22:19.880 --> 00:22:23.880
 calling me and saying hey these cars are still going too fast let's get an update

00:22:23.880 --> 00:22:30.240
 on whether or not that is helping out or are we still going to do anything

00:22:30.240 --> 00:22:37.680
 additional for Moore Street and I've been asked that by a resident yeah sure

00:22:37.680 --> 00:22:42.600
 we don't mind bringing that back at all we do have a project there as we brought

00:22:42.600 --> 00:22:47.960
 forward to not only the Sedna meeting and then also the southeastern area plan

00:22:47.960 --> 00:22:51.360
 brought forward and asked a lot of questions we had to have all of those

00:22:51.360 --> 00:22:54.840
 conversations and meetings and out like we reported in the southeastern meeting

00:22:54.840 --> 00:23:00.400
 we'll be bringing that back within about three to six months so that is a project

00:23:00.400 --> 00:23:07.840
 but we're happy to bring an update to you at the next meeting also on the

00:23:07.840 --> 00:23:15.160
 corner of Morris in Woodrow and it's still Woodrow yes we know that we're

00:23:15.160 --> 00:23:21.600
 getting a new apartment complex there so there's anticipation of more cars being

00:23:21.600 --> 00:23:28.680
 on that roadway and we could see right now that the roadway is full of cars as

00:23:28.680 --> 00:23:36.160
 it is it's growing is there any kind of anticipation of meeting the needs of the

00:23:36.160 --> 00:23:42.000
 folks that are trying to pull out on to Woodrow from Morris Street has there

00:23:42.000 --> 00:23:46.520
 been any conversation in that regard sure we can bring that line that is

00:23:46.520 --> 00:23:50.800
 slowing that area down so people can have time to pull out sure I think the

00:23:50.800 --> 00:23:54.800
 right side of going north is a little higher and they're coming up kind of

00:23:54.800 --> 00:24:01.360
 coming down a little slope in in so I like you all to take a look at that yes

00:24:01.360 --> 00:24:05.600
 we have that work came up in the southeastern also but we'll bring you

00:24:05.600 --> 00:24:10.680
 back a report of any plan or action that we do it's in concert with the more

00:24:10.680 --> 00:24:17.280
 street with it okay yes ma'am yes yeah I forgot one that I wanted to ask Becky

00:24:17.280 --> 00:24:23.080
 about and did I presume it was one of you or your team that responded to some

00:24:23.080 --> 00:24:31.720
 of the questions yesterday in council about you know the bike ped audit but I

00:24:31.720 --> 00:24:38.200
 know that that Paul submitted to council several questions from Susie room are

00:24:38.200 --> 00:24:43.560
 mm-hmm room war and and I wondered if you you and your team have had a chance to

00:24:43.560 --> 00:24:47.760
 review those and if if so whether you want to bring them back in mobility or

00:24:47.760 --> 00:24:53.160
 put it into a Friday staff if maybe staff could could address some of her

00:24:53.160 --> 00:25:00.180
 concerns sort of as a leading bike ped community advocate typically what we do

00:25:00.180 --> 00:25:04.320
 when we receive comments from Susie is sit down with her and go through her

00:25:04.320 --> 00:25:08.220
 comments and we didn't receive those till right before the council meeting

00:25:08.220 --> 00:25:11.400
 yesterday so we have not had a chance to even discuss or go through all of them

00:25:11.400 --> 00:25:17.200
 and but what we plan to do is sit down and go through her comments with her and

00:25:17.200 --> 00:25:22.200
 then because there were so many comments that were made I don't believe putting

00:25:22.200 --> 00:25:26.120
 it in a Friday report is going to be sufficient we'll probably put it in an

00:25:26.120 --> 00:25:29.760
 ISR which will be a part of the Friday report it would not just be a specific

00:25:29.760 --> 00:25:34.360
 blurb but that would be our anticipation and we will not have that ready for

00:25:34.360 --> 00:25:38.400
 Friday it'll probably be a week or so no yeah I didn't put a time limit on

00:25:38.400 --> 00:25:41.640
 because I knew some of them were more involved questions so yeah if you're

00:25:41.640 --> 00:25:49.000
 already on top of that then then great yes sir well I don't have any other

00:25:49.000 --> 00:25:54.240
 additional questions or any comments or concerns yes ma'am we did receive one

00:25:54.240 --> 00:25:59.000
 individuals request to speak so I'd like to give them an opportunity I know with

00:25:59.000 --> 00:26:02.840
 us starting right at 8 o'clock it makes it difficult to get in here and get your

00:26:02.840 --> 00:26:11.840
 comment card written down so I will minimize this and go ahead and let you

00:26:11.840 --> 00:26:24.280
 call that item okay we'll call Liam the cover you'll be you have three minutes

00:26:24.280 --> 00:26:32.120
 all right hello my name is Liam and I'm a member of Abundance Denton as you look

00:26:32.120 --> 00:26:35.960
 to future mobility committee items I'd like to submit an item for your

00:26:35.960 --> 00:26:40.400
 consideration as you already know DCTA has disinvested from Denton's fixed

00:26:40.400 --> 00:26:45.320
 route transit cutting a majority of the connect routes in 2021 GoZone has

00:26:45.320 --> 00:26:50.040
 proven an unreliable inefficient inexpensive option it cost DCTA more

00:26:50.040 --> 00:26:55.880
 pride given more pride than buses and has no way to decrease the cost and

00:26:55.880 --> 00:27:00.000
 still cannot reliably get people to and from work or to doctors appointments on

00:27:00.000 --> 00:27:05.000
 time one result of this disinvestment has been DCTA generating a sizable

00:27:05.000 --> 00:27:08.720
 stockpile of cash each year they cash out as a percentage of it to Denton to

00:27:08.720 --> 00:27:13.840
 be used for transit supportive projects with Denton's bus network and shambles

00:27:13.840 --> 00:27:19.200
 the most pressing transit supportive thing Denton can do with these this this

00:27:19.200 --> 00:27:28.400
 up 2024 years funds would be to do would can do with the fund is to do what UNT

00:27:28.400 --> 00:27:32.360
 does with their transportation funds is to buy bus routes currently on the east

00:27:32.360 --> 00:27:37.520
 side of town there has been many there there are many social services jobs

00:27:37.520 --> 00:27:42.800
 grocery stores and lots of multifamily mobile home parks which with more on the

00:27:42.800 --> 00:27:46.640
 way and only has a single meandering connect route which only runs every 43

00:27:46.640 --> 00:27:51.800
 minutes just till 6 p.m. with all the new development on the way it's the

00:27:51.800 --> 00:27:55.120
 city's best interest to provide high quality bus service in this area we

00:27:55.120 --> 00:28:00.320
 propose didn't buy two routes from DCTA for two years to run Monday through

00:28:00.320 --> 00:28:04.400
 Saturday 6 a.m. to 8 p.m. this time scale will give the routes time to

00:28:04.400 --> 00:28:08.800
 stabilize and then should work with DCTA to set a ridership target that is met

00:28:08.800 --> 00:28:15.480
 with a result in DCTA moving the routes over their budget over over to their

00:28:15.480 --> 00:28:20.680
 budget at the end of two years route also there is a white paper that was

00:28:20.680 --> 00:28:25.880
 emailed to you this morning that should be in there route 3b could be a companion

00:28:25.880 --> 00:28:29.920
 route to route 3 running every 43 minutes and taking the old route 3

00:28:29.920 --> 00:28:34.560
 straight to the end of McKinney and back this would provide approximately 20

00:28:34.560 --> 00:28:38.240
 minutes service too much of route 3 and renew service to Ashley Oaks Denton

00:28:38.240 --> 00:28:43.280
 Falls the shores and Ryan High route 2 would be running every 20 minutes along

00:28:43.280 --> 00:28:50.200
 loop 288 and from 380 to the mall this will provide a service to the mall the

00:28:50.200 --> 00:28:55.320
 288 shopping districts and thousands of existing incoming multifamily units this

00:28:55.320 --> 00:28:59.200
 would also be a generational investment in dens future to accessible climate

00:28:59.200 --> 00:29:02.680
 friendly future and won't need to pave paradise to meet our growing traffic

00:29:02.680 --> 00:29:10.840
 demands this would this also helps prevent more traffic getting onto certain

00:29:10.840 --> 00:29:16.560
 roads which is important to everybody thank you I yield the remainder of my

00:29:16.560 --> 00:29:21.660
 time thank you very much that's very important and very insightful and I just

00:29:21.660 --> 00:29:26.120
 happen to agree with everything that I've heard I'd appreciate that thank you

00:29:26.120 --> 00:29:30.120
 you can have a any questions yeah no I one of the things we can do with

00:29:30.120 --> 00:29:35.720
 citizens comments is ask for future agenda items so what I'm gonna do is ask

00:29:35.720 --> 00:29:40.920
 chair if you would I assume you got it if you didn't I and it's an email from

00:29:40.920 --> 00:29:47.000
 Christie I just hadn't looked at it that why don't we pass this off to staff and

00:29:47.000 --> 00:29:53.600
 ask them in some future agenda meeting to to evaluate pros and cons that they

00:29:53.600 --> 00:30:01.120
 see out of that kind of plan so that and then we can potentially move from there

00:30:01.120 --> 00:30:08.220
 maybe that's a mobility agenda item maybe that's an ISR but that'd be what I

00:30:08.220 --> 00:30:14.800
 would request is so that we can see staff's comments on the the potentials

00:30:14.800 --> 00:30:22.560
 of this plan and also just had in mind that we would ask our DCTA rep to give

00:30:22.560 --> 00:30:27.560
 us an update I'd like to see it at City Council meeting I know that they do come

00:30:27.560 --> 00:30:32.560
 to City Council meetings and give us an update I've been recognizing that they

00:30:32.560 --> 00:30:39.160
 were not coming to a mobility committee since they've gotten a new CEO not sure

00:30:39.160 --> 00:30:46.400
 how that turned out that way but we definitely still are very interested in

00:30:46.400 --> 00:30:52.200
 our transportation system on the east side we that's the most vulnerable

00:30:52.200 --> 00:30:57.440
 conditions and we even saw some of that data yesterday with through our auditor

00:30:57.440 --> 00:31:03.640
 auditor so yeah we're definitely gonna have to bring that back I don't know how

00:31:03.640 --> 00:31:09.240
 that's gonna look but I'd like to hear from our DCTA representative or someone

00:31:09.240 --> 00:31:15.920
 from DCTA sure and we have DCTA already on the agenda for the council work

00:31:15.920 --> 00:31:22.820
 session in November so what we'll do is happy to receive the letter and review

00:31:22.820 --> 00:31:27.080
 it see if there's anything that we need to bring forward prior to that with the

00:31:27.080 --> 00:31:31.960
 October meeting but that more than likely we will ask DCTA to address that

00:31:31.960 --> 00:31:36.720
 during their council meeting or in another form but they are coming forward

00:31:36.720 --> 00:31:41.560
 for their regular update in November okay that'll be great all right well

00:31:41.560 --> 00:31:44.560
 thank you very much Liam we appreciate you bringing that back to us thank you

00:31:44.560 --> 00:31:51.400
 for letting me speak so are there anything else that you wanted to bring

00:31:51.400 --> 00:32:02.760
 up are there any concluding items well I don't have you're okay I'm just curious

00:32:02.760 --> 00:32:07.640
 is anybody going to TML are there are there any no none of the engineering

00:32:07.640 --> 00:32:14.040
 staff are going to TML okay then then then council bird and I will bring back

00:32:14.040 --> 00:32:20.600
 even more annoying ideas from TML when we go about keeping up with the Joneses

00:32:20.600 --> 00:32:28.460
 in all the many extra layers of duty and FTE that we'll be asking you for and

00:32:28.460 --> 00:32:32.960
 unfortunately I won't be going to T T well I didn't know when I was gonna get

00:32:32.960 --> 00:32:36.200
 my hip replaced you know I was just kind of waiting on that and it was kind of

00:32:36.200 --> 00:32:38.960
 lingering around and I missed the deadlines and things like that I was

00:32:38.960 --> 00:32:41.960
 there wasn't on my mind so we'll have to depend on you to bring everything back

00:32:41.960 --> 00:32:46.360
 or appreciate it okay so if there's no concluding items will declare the

00:32:46.360 --> 00:32:55.960
 meeting over at 8 32 a.m. on Wednesday September 23rd thank you

