WEBVTT 00:00:02.114 --> 00:00:15.530 - So this is May 29th for the Bloomington Monroe County MPO Policy Committee meeting. So I'd like to call 00:00:15.530 --> 00:00:29.074 - the meeting to order and introductions and I'll begin to my right. As proxy for director of public works 00:00:29.074 --> 00:00:30.622 - Adam Wason. 00:00:32.258 --> 00:00:41.716 - Good morning, Becky Packer in dot Sam Tobin hockstatt Citizens Advisory Committee Scott Ferris Monroe 00:00:41.716 --> 00:00:51.174 - County Planning Commission Andrew Seabor serving as proxy for Mayor Thompson Lisa Ridge Monroe County 00:00:51.174 --> 00:01:00.446 - Highway Director Hopi Stossburg Bloomington Common Council And I believe we do not have any members 00:01:00.834 --> 00:01:10.571 - Uh, committee members online and moving on approval of agenda for mate 29, 2026 motion to approve. We 00:01:10.571 --> 00:01:20.403 - have a motion and a second. I believe we can just do an overall. We don't need to do a roll call vote. 00:01:20.403 --> 00:01:29.854 - So all those in favor for approving the agenda for mate 29, 2026, please do so by saying aye. Aye. 00:01:30.690 --> 00:01:39.300 - any nays? Seeing none. Motion carries. Um, moving on to approval of minutes from April 24th, 2026. I 00:01:39.300 --> 00:01:48.336 - have a motion. Uh, also there, I want to make note for everybody present that there was a revised version 00:01:48.336 --> 00:01:55.838 - of the minutes that were I believe published yesterday. That right, Katie? Okay. And so 00:01:56.162 --> 00:02:01.607 - What we're voting on is that revised version for those folks who, if you took a look to make sure you 00:02:01.607 --> 00:02:06.999 - know what you're voting on? I can't quite hear you. If you could speak more into the mic, that would 00:02:06.999 --> 00:02:12.552 - be great. I'm sorry? I can't quite hear you. If you could speak more into the mic, that would be great. 00:02:12.552 --> 00:02:18.317 - I'll repeat what I said then. How's that? Better. Much better. All right. So there really were two versions 00:02:18.317 --> 00:02:24.350 - of the minutes that were revised, I believe, yesterday by the MPO staff. What it added was a reflection that the 00:02:24.834 --> 00:02:32.748 - County Attorney Schilling was present at the meeting and actually made comments. That was the only additions 00:02:32.748 --> 00:02:40.371 - that were added to the minutes and that's what we're voting on. Correct. Correct. OK. So I have a motion 00:02:40.371 --> 00:02:47.776 - to approve those minutes. We have a motion and a second. Any board comments any public comment seeing 00:02:47.776 --> 00:02:54.238 - none. All those in favor of proving the minutes from April 24th do so by saying aye aye. 00:02:54.914 --> 00:03:05.011 - Any opposed Motion carries Communications from fair or from chair or vice chair. I don't have any comments 00:03:05.011 --> 00:03:14.448 - today And neither does our vice chair Communications from officers and or committees tech committee 00:03:14.448 --> 00:03:21.054 - Yes, the MPO technical advisory committee met this past Wednesday and 00:03:21.570 --> 00:03:29.513 - Also considered the items that are on today's agenda and recommended approval. Thank you. Thank you. 00:03:29.513 --> 00:03:37.378 - And citizens similarly the citizens advisory committee met on Wednesday and also considered the tip 00:03:37.378 --> 00:03:45.950 - amendments and recommended them for approval by this committee. Thank you. Moving on reports from MPO staff. 00:03:54.658 --> 00:04:01.341 - There is a news release from the Indiana Department of Transportation regarding single-lane closure 00:04:01.341 --> 00:04:08.225 - planned on Interstate 69, Green and Monroe counties. This falls within the urbanized area. The Indiana 00:04:08.225 --> 00:04:14.908 - Department of Transportation will be conducting geotechnical repairs along the corridor. This is an 00:04:14.908 --> 00:04:20.990 - area prone to landslide. I think this has happened at least two to three times previously. 00:04:21.890 --> 00:04:32.734 - The soils are very unstable. They've done a number of things before but it needs work again. So the 00:04:32.734 --> 00:04:43.903 - single enclosure will will occur as noted in the Press release. Does anybody have any questions? Okay, 00:04:43.903 --> 00:04:51.710 - if not, I'll move on to the next item item 6.2 2026 city of Bloomington 00:04:52.290 --> 00:05:00.126 - ADA transition plan. This is the draft the draft comment period is already closed City of Bloomington 00:05:00.126 --> 00:05:07.962 - will finalize the ADA transition plan and it will be published in July The reason this is included in 00:05:07.962 --> 00:05:15.952 - the packet is because the MPO is housed and has meetings within the city of Bloomington this is to show 00:05:15.952 --> 00:05:20.254 - that we are in compliance with all the ADA criteria and 00:05:20.546 --> 00:05:29.764 - This will the final document will be transmitted to the Indiana Department of Transportation Federal 00:05:29.764 --> 00:05:39.074 - Highway Administration and Federal Transit Administration in July Any questions anybody on this? Okay 00:05:39.074 --> 00:05:49.022 - item six point three this is a memorandum prepared on Bloomington trance's proposed service improvements and 00:05:49.218 --> 00:05:57.318 - and the public hearing notice, which was external to us. I attended all three of the public meetings. 00:05:57.318 --> 00:06:05.259 - First one was at Ivy Tech State College. Second and third ones were at the downtown transfer center 00:06:05.259 --> 00:06:13.279 - for Bloomington Transit. All three public hearings were very well attended. At least 10 to 20 people 00:06:13.279 --> 00:06:15.582 - at each one of the meetings. 00:06:15.938 --> 00:06:23.967 - That involves a consolidation of route 3 what was previously known as route 3 and route 13 into a new 00:06:23.967 --> 00:06:32.153 - route of route 16 the reason we attended and the reason we're Making you aware of this is the fact that 00:06:32.153 --> 00:06:40.103 - this route was outside of the normal service area of Bloomington transit. It's outside of the city's 00:06:40.103 --> 00:06:45.534 - corporate limits into Monroe County and Bloomington transit operates 00:06:45.762 --> 00:06:55.471 - In this area and operates this route with supplemental support from the county Nero County Council through 00:06:55.471 --> 00:07:04.907 - an interlocal agreement The new route Hits all the marks. They've looked at seven different alternative 00:07:04.907 --> 00:07:14.071 - Combinations before they struck this one make sure that it ensures Access to Ivy Tech State College. 00:07:14.071 --> 00:07:15.614 - It's also serves 00:07:16.226 --> 00:07:23.752 - Cook Medical and serves another former Baxter pharmaceutical out in that area. There are no rides that 00:07:23.752 --> 00:07:31.278 - they are aware of that are coming from trip generation, trip distribution to any one of those two, but 00:07:31.278 --> 00:07:38.730 - to Ivy Tech State College there is. This thing also includes major shopping destinations such as Game 00:07:38.730 --> 00:07:46.110 - Art Sam's Club. I'm trying to think of Rural King and others in the area. The route will take effect 00:07:46.658 --> 00:07:56.430 - In July, I believe it is. There's also a push here too by Bloomington Transit with the unveiling of 00:07:56.430 --> 00:08:06.299 - micro transit. So anyone who feels like they're outside of this current route can also ask for micro 00:08:06.299 --> 00:08:15.582 - transit service. It's been an extension of service hours Monday through Friday, six to 10 p.m. 00:08:15.938 --> 00:08:27.425 - Saturday 8 10 to 6 10 Departs every 30 minutes Departs the Transit Center at 10 and 40 on the hour three 00:08:27.425 --> 00:08:38.802 - buses on route 16 at all times and the bus will stop at each each Every 30 minutes. There's also Sunday 00:08:38.802 --> 00:08:45.694 - service available From 8 10 a.m. To 10 p.m. The previous route 00:08:45.826 --> 00:08:54.161 - Route 3 and Route 13, it had low ridership for the last 12 months. The ridership sometimes was only 00:08:54.161 --> 00:09:02.580 - a single rider or perhaps zero riders. So therefore, with this development of combination of the new 00:09:02.580 --> 00:09:11.582 - route, they hope to boost the ridership substantially with a particular emphasis on Ivy Tech State College. 00:09:14.498 --> 00:09:27.266 - It starts June 1st. I'm sorry Bloomington Transit Board Doug's not here Bloomington Transit Board already 00:09:27.266 --> 00:09:39.311 - voted to approve this Questions anyone Moving to the next item go ahead. Oh, that's right Six point 00:09:39.311 --> 00:09:43.166 - four on page 60 of the contract 00:09:43.330 --> 00:09:51.678 - This is a memo notifying you of a change to the tip that staff made since the last meeting. Some changes 00:09:51.678 --> 00:09:59.945 - to the tip don't require committee review. This particular change, there were two changes, one transit, 00:09:59.945 --> 00:10:08.134 - one non-transit. This change for transit was to the EV mobile chargers project. They were changing the 00:10:08.134 --> 00:10:09.406 - funding source. 00:10:10.466 --> 00:10:19.020 - They also increased the federal amount. So I believe this was a chunk of change that was flexed to them 00:10:19.020 --> 00:10:27.245 - from the MPO in the past and they're applying it to this project and they're trying to use up those 00:10:27.245 --> 00:10:35.552 - flex funds before September. So they increase the federal total. They also had to therefore increase 00:10:35.552 --> 00:10:39.582 - the local share and of course the project total. 00:10:41.058 --> 00:10:50.093 - You can see it went from 350,000 to 453,000 All transit projects that get federal funding from FTA have 00:10:50.093 --> 00:10:58.867 - to be in our tip and do get reviewed by the committees But this was this was just a modification The 00:10:58.867 --> 00:11:07.988 - next memo is for a non-transit update to the tip this was for Monroe County's Dillman Road bridge number 00:11:07.988 --> 00:11:10.334 - 83 replacement project and 00:11:11.266 --> 00:11:19.834 - Due to environmental impacts they will be moving the bridge program funds they're receiving from the 00:11:19.834 --> 00:11:28.403 - state and also their local match funds for the right of way phase from fiscal year 26 to 27. And you 00:11:28.403 --> 00:11:35.614 - can see that change reflected here. There was no change in amounts just fiscal year. 00:11:41.890 --> 00:11:48.785 - Any questions. Happy has a question. Hey you said in the memo that these are considered administrative 00:11:48.785 --> 00:11:55.679 - modifications and so they don't require approval. Can I feel like we've had similar sort of like small 00:11:55.679 --> 00:12:02.373 - changes before that did require approval. So can you like just explain a little bit more about what 00:12:02.373 --> 00:12:06.590 - classifies as an administrative modification and what doesn't. 00:12:06.818 --> 00:12:15.288 - Yeah, good question. That information is not in our tip right now, but it will be in the next one. And 00:12:15.288 --> 00:12:23.593 - actually, we'll be bringing this topic to your July policy committee meeting. So there will be a lot 00:12:23.593 --> 00:12:32.063 - more detail then. But essentially, per federal law, significant changes to the tip have to be reviewed 00:12:32.063 --> 00:12:33.790 - by local committees. 00:12:33.922 --> 00:12:42.894 - But insignificant changes don't and so examples of significant changes would be like an increase in 00:12:42.894 --> 00:12:52.046 - project funding above a certain percentage or the addition of a new project to the tip and then a lot 00:12:52.046 --> 00:12:58.686 - there's a lot of gray area there too, but there is what in dot requires a 00:12:59.170 --> 00:13:06.246 - For their amendments or modifications. So essentially they have their own public review process they 00:13:06.246 --> 00:13:13.252 - consider certain things to be amendments and versus modifications and that depends on how long they 00:13:13.252 --> 00:13:20.679 - put something out for public review or whether whether they need to do public review and then essentially 00:13:20.679 --> 00:13:27.895 - we have the same powers here to To kind of decide what we consider an amendment or modification beyond 00:13:27.895 --> 00:13:29.086 - those big ticket 00:13:29.378 --> 00:13:40.371 - threshold items that are very clear in the federal law. And so that's we. Yeah. We plan to talk more 00:13:40.371 --> 00:13:51.690 - about that to you next next meeting. Yeah. Okay. Thank you. Item six point six pack. Okay. Please refer 00:13:51.690 --> 00:13:55.390 - to your packet here. We've got a. 00:13:56.194 --> 00:14:04.904 - Memorandum from the Indiana Department of Transportation, the Office of Traffic Safety. These are changes 00:14:04.904 --> 00:14:13.286 - to the injury severity determination method for crash data analysis in the state of Indiana. State of 00:14:13.286 --> 00:14:21.750 - Indiana has had a, well, it's had a evolving definition of what is a suspected serious injury and what 00:14:21.750 --> 00:14:25.694 - is a serious injury. This methodology is proven 00:14:26.114 --> 00:14:35.418 - somewhat unstable in terms of the actuality of the injuries over the last period of time. The Office 00:14:35.418 --> 00:14:45.091 - of Traffic Safety is therefore rolling out a brand new methodology which is consistent with 21, 22 other 00:14:45.091 --> 00:14:50.526 - states within the United States of the national standards. 00:14:50.978 --> 00:15:01.380 - This also coincides with the rollout. I have a new software package called Ashtoware safety which brings 00:15:01.380 --> 00:15:11.584 - the state into an alignment with 22 20 yeah 21 22 other states the Better lines with the national best 00:15:11.584 --> 00:15:19.806 - practices also for how injury severity is determined And if you look in the packet 00:15:20.034 --> 00:15:29.471 - You'll note that 26, sorry, just a second. We'll go through this. The crash severity level will be changed 00:15:29.471 --> 00:15:38.290 - within the Ares data reporting form filled out by the officers at the scene of the crashes. And the 00:15:38.290 --> 00:15:43.582 - new crash severity level will add in eight different items. 00:15:43.906 --> 00:15:52.570 - called a crush injury, a fracture, dislocation, internal paralysis, severe bleeding, severe burn, severed 00:15:52.570 --> 00:16:00.744 - or unconscious states. Both incapacitating and non-incapacitating injury crashes will be counted as 00:16:00.744 --> 00:16:08.918 - suspected serious injury crashes depending on the nature of the most severe injury. Whether someone 00:16:08.918 --> 00:16:13.822 - is transported to the hospital or not will not be relevant. 00:16:14.082 --> 00:16:22.569 - previous or current definition is that they're transported to the hospital. It's considered a suspected 00:16:22.569 --> 00:16:30.810 - serious injury. Also, there will be an injury scale, the rollout of a new injury scale for the state 00:16:30.810 --> 00:16:39.297 - of Indiana called the CABO standard, K-A-B-C-O standard. K will stand for fatality. A will be suspected 00:16:39.297 --> 00:16:44.030 - serious injury. B will be a non-suspected serious injury. 00:16:44.706 --> 00:16:53.326 - C will be a minor injury, O will be a property damage type crash. There's also detailed documentation 00:16:53.326 --> 00:17:01.861 - in here about how errors will be handled. Also, the state of Indiana is adopting a brand new updated 00:17:01.861 --> 00:17:10.481 - crash cost for highway safety analysis. This consists of the same process used by the Federal Highway 00:17:10.481 --> 00:17:14.622 - Administration, where the costs of a fatality or 00:17:14.850 --> 00:17:24.386 - and serious injuries are all based on economic crash unit costs, $20.24 in comprehensive unit costs 00:17:24.386 --> 00:17:33.922 - of using $20.24. I won't go into any other of the detail on this because it's fairly technical, but 00:17:33.922 --> 00:17:39.358 - I'll be happy to answer any questions that you may have. 00:17:44.482 --> 00:17:52.583 - question. Yes. So and I'm sure there's an obvious answer here. This will not be retroactively applied 00:17:52.583 --> 00:18:00.604 - to any of the crash data that were reported in the past correct. It's from this whenever this is put 00:18:00.604 --> 00:18:09.023 - in place from that point forward. I know we plan to update the crash dashboard. Well we don't I shouldn't 00:18:09.023 --> 00:18:13.470 - say that we're talking about what our approach will be. 00:18:13.602 --> 00:18:21.902 - given these new this new information. So we may be updating the crash dashboard to reflect this process 00:18:21.902 --> 00:18:30.123 - although we'll only be able to go back to 2022. So we'll probably have to let go of if we want to keep 00:18:30.123 --> 00:18:38.104 - everything in the same with the same analysis we'll probably have to let go of 2019 to 2022 data so 00:18:38.104 --> 00:18:42.494 - that everything is using the same methodology but well 00:18:42.690 --> 00:18:52.909 - To be yeah to to be determined. We'll have to figure that out by October 1st. Thank you. Yeah. In terms 00:18:52.909 --> 00:19:02.932 - of modification to the record is that the responsibility of the responding officers then to follow up 00:19:02.932 --> 00:19:11.678 - to potentially modify the record in terms of injury severity. Well in terms of fatality. 00:19:12.322 --> 00:19:19.201 - Well, yeah, just I mean it's how to how to handle errors and then it gave some examples in terms of 00:19:19.201 --> 00:19:26.218 - You know a minor bruise that might Elevate or a fracture dislocation that might be clarified in terms 00:19:26.218 --> 00:19:33.235 - of what exactly you know a minor broken nose Which is different than like a leg broken in four places 00:19:33.235 --> 00:19:40.734 - and so I'm just trying to figure out who like where the responsibility would lay to make that correction and 00:19:41.954 --> 00:19:49.807 - Correction lies with the officer Okay state of Indiana and ourselves Aren't able to alter those records, 00:19:49.807 --> 00:19:57.511 - right? I mean we could categorize them We as in Indiana Department of Transportation Office of traffic 00:19:57.511 --> 00:20:05.064 - safety and ourselves could subsequently categorize them differently but for changing the record know 00:20:05.064 --> 00:20:11.646 - that responsibilities exclusively with the officer completing the the report itself and 00:20:12.034 --> 00:20:19.551 - And in fairness to the officers under time constraints I mean to appear at the accident to complete 00:20:19.551 --> 00:20:27.444 - the report Sometimes the reports aren't completed till several days after the crash You know preliminary 00:20:27.444 --> 00:20:34.961 - information is is placed down and then comes after that Katie can tell you that we wait until 35 We 00:20:34.961 --> 00:20:41.726 - wait a period for the fatalities to make sure that the fatalities are accurately recorded 00:20:42.306 --> 00:20:49.677 - The state defines a fatality is a death that occurs within 30 days of the accident and so that's why 00:20:49.677 --> 00:20:56.976 - we wait Two and a half months or so after the quarter to pull the crash data to give time for Those 00:20:56.976 --> 00:21:04.347 - updates to the the crash entries are to the crash reports But regarding this paragraph here the crap 00:21:04.347 --> 00:21:11.646 - about the crash narratives I think some I think some my guess is that some there will still be some 00:21:12.578 --> 00:21:21.191 - you know, cleaning up of data that will occur at the Transportation Safety Office at NDOT. If they have 00:21:21.191 --> 00:21:30.218 - access to do that, I think they will with their new system. And so they reference here that crash narratives 00:21:30.218 --> 00:21:38.831 - will be an important part of verifying things. So they have talked about using AI to help with cleaning 00:21:38.831 --> 00:21:42.558 - up data. Don't know if that will happen, but 00:21:42.882 --> 00:21:50.027 - At the very least there will will be able to review data We have there's a lot of people here who still 00:21:50.027 --> 00:21:57.103 - have access to crash reports and the narratives and we can still We can still review the data to clean 00:21:57.103 --> 00:22:03.973 - it up. We can well, we'll probably be able to submit that Submit those changes then to end up which 00:22:03.973 --> 00:22:10.980 - would be great because currently we we do clean it up We don't we don't currently modify injuries and 00:22:10.980 --> 00:22:12.766 - change those fields we we 00:22:13.154 --> 00:22:20.603 - We mainly just clean up location right now. But in the future, if there is something, a narrative that 00:22:20.603 --> 00:22:27.980 - seems to go against the injury classification, we'll be able to submit that request to INDOT and then 00:22:27.980 --> 00:22:35.357 - have them change that at the source of the data, which is much preferable to changing it locally here 00:22:35.357 --> 00:22:42.878 - and then them having a different data set. So a lot will depend on the rollout of the new software too. 00:22:43.330 --> 00:22:51.301 - And and kind of as a follow-up will the public have access to these crash reports? So like will the 00:22:51.301 --> 00:22:59.273 - public be able to like like go online somewhere with with a crash and see that it was you know an a 00:22:59.273 --> 00:23:07.324 - level crash or That kind of thing Do you know that I mean there are privacy constraints on all of us 00:23:07.324 --> 00:23:11.230 - so only in terms of the location time of day and 00:23:12.034 --> 00:23:18.711 - What I would call the generalized information will be there. Yes, but no personal information will be 00:23:18.711 --> 00:23:25.323 - available to anybody from the public No, right, but you could go on say some kind of map and go. Oh, 00:23:25.323 --> 00:23:31.869 - there's you know, there was this crash on this date Involving two vehicles and it was and and there 00:23:31.869 --> 00:23:37.630 - was an a crash that had a that kind of level of severity Yeah, the the ash aware safety 00:23:37.730 --> 00:23:45.704 - data will have that available once the data has been uploaded and posted through the software. The only 00:23:45.704 --> 00:23:53.831 - other thing I want to add is Katie mentioned it has an AI component to the software. We call it we gently 00:23:53.831 --> 00:24:01.958 - call it a learning software in that it will take time probably at least a year or perhaps slightly longer 00:24:01.958 --> 00:24:06.942 - where it will correct some of the reports where the location was 00:24:07.170 --> 00:24:15.817 - was made referencing everything will be done by GPS GIS to locate and then in identifying consistent 00:24:15.817 --> 00:24:24.379 - errors that learning component will hopefully standardize all of the crashes so that we have a much 00:24:24.379 --> 00:24:33.282 - better we Department Transportation Office of Traffic Safety and ourselves will have a much better idea 00:24:33.282 --> 00:24:35.166 - of where when why how 00:24:35.810 --> 00:24:43.993 - Then also the engineering departments will have a better Better opportunity to apply the appropriate 00:24:43.993 --> 00:24:52.581 - corrective crash countermeasure Does that Yeah, I think it does do you know what kind of lag time they'll 00:24:52.581 --> 00:25:01.169 - be on that site I mean this is kind of up to the state right in terms of when they get something uploaded 00:25:01.169 --> 00:25:04.734 - I guess it's like so if an accident happens 00:25:05.026 --> 00:25:13.871 - Say today, how long might it be before? At least a month at least a month simply because of the fatality 00:25:13.871 --> 00:25:23.054 - issue And sometimes longer than that depending on the lag the new software will accelerate that considerably 00:25:23.054 --> 00:25:31.478 - Okay, and then we will be partnering with the office of traffic safety on the crash software itself 00:25:31.478 --> 00:25:34.174 - Beta testing will begin shortly 00:25:35.074 --> 00:25:42.688 - Shortly meaning in the next few weeks and then full implementation software began October 1st which 00:25:42.688 --> 00:25:50.378 - coincides with the beginning of the state federal fiscal year. Okay. Thank you. Yeah. Well we'll all 00:25:50.378 --> 00:25:54.718 - be learning from this process. Any additional questions. 00:26:04.546 --> 00:26:16.681 - Item 6.8 on page 71 of the combined packet. This is a 2025 brief overview of the crashes, mostly fatalities 00:26:16.681 --> 00:26:28.141 - and serious injury numbers for 2025. GIS, the city GIS team is working on getting that data up on the 00:26:28.141 --> 00:26:33.310 - dashboard right now, but it's been cleaned up 00:26:33.474 --> 00:26:43.352 - They just have a couple more steps. And so this total crashes of 3,662 that does include crashes that 00:26:43.352 --> 00:26:53.036 - took place on both private and public property. So keep in mind that the local public agencies when 00:26:53.036 --> 00:27:02.526 - they do their analysis, typically just look at the crashes that occur in the public right of way. 00:27:03.042 --> 00:27:11.378 - Something of note, which we hope to kind of track this number and look at the numbers in the past as 00:27:11.378 --> 00:27:19.963 - well in the future, but 10 out of 14 occurred within the MPOs metropolitan planning area, which is like 00:27:19.963 --> 00:27:28.216 - our jurisdiction of control. And then 43 out of 62 of the serious injuries occurred within the MPA. 00:27:28.216 --> 00:27:31.518 - And we can, we'll update these numbers. 00:27:32.002 --> 00:27:41.372 - Uh, in the future, once, once we, uh, once the serious injury, um, adjustments are made this fall. Fatal 00:27:41.372 --> 00:27:50.564 - crashes. We had 14 in 2025, although one occurred in a public, in a parking garage. So not on a public 00:27:50.564 --> 00:27:59.667 - road. Uh, one metric I don't have, I don't have on here, which, which the citizens advisory committee 00:27:59.667 --> 00:28:01.630 - pointed out, which is 00:28:02.210 --> 00:28:11.354 - You know which crashes how many crashes occurred on state road versus local roads. And so that's something 00:28:11.354 --> 00:28:19.899 - I'll add to this later. Two of the fatal crashes had two crashes each or sorry two deaths each. And 00:28:19.899 --> 00:28:21.950 - then we had a total of. 00:28:27.874 --> 00:28:38.059 - 13 of those crashes of those 14 crashes were vehicle two vehicles one involved a vehicle or a motor 00:28:38.059 --> 00:28:48.447 - vehicle and a pedestrian and zero involved bikes And keep in mind that scooters are not Separated out 00:28:48.447 --> 00:28:56.798 - from this so they typically fall within the bicycle category Next is just a short 00:28:57.442 --> 00:29:06.296 - brief descriptions of each of the fatal crashes and where they occurred. Of course, you'll be able to 00:29:06.296 --> 00:29:15.063 - see the locations better on the dashboard in the future. And the most common manner of collision was 00:29:15.063 --> 00:29:23.917 - a head-on, at least as reported, was a head-on crash. And both of the crashes with the two fatalities 00:29:23.917 --> 00:29:25.566 - each were head-on. 00:29:30.306 --> 00:29:39.985 - Serious injuries. You can see that over time serious injuries have declined and that looks really good. 00:29:39.985 --> 00:29:49.478 - And it's both due to local efforts to make things more safe and also possibly skewed a little bit due 00:29:49.478 --> 00:29:57.854 - to software changes at the state level and different interpretations of serious injuries. 00:29:58.242 --> 00:30:08.496 - And so it'll be interesting to see how these numbers change once that different methodology is applied. 00:30:08.496 --> 00:30:18.355 - The most common primary factor of the serious injury crashes that was noted was failure to yield to 00:30:18.355 --> 00:30:21.214 - right of way. Any questions? 00:30:24.930 --> 00:30:33.020 - Thank you. I really appreciate you putting this together, by the way. And I have a couple of questions. 00:30:33.020 --> 00:30:40.877 - So first of all, you don't have any bike versus pedestrian categories on here. And I know that there 00:30:40.877 --> 00:30:48.967 - was at least one of those on the beeline. And I can't quite remember when it was. I know it wasn't last 00:30:48.967 --> 00:30:53.790 - year. But is that something that can somehow get added? Well, 00:30:54.146 --> 00:31:05.426 - We use the areas data which is police crash reports which implies at least one motor vehicle was involved. 00:31:05.426 --> 00:31:16.074 - So that would have been labeled as some some other sort of incident report. I'm not sure how the BPD 00:31:16.074 --> 00:31:23.454 - would do it but that I don't think that would that shows up at all on 00:31:23.682 --> 00:31:32.030 - Okay, so maybe it's Like it could in theory show up, but it's all about how how it's coded Yeah, I would 00:31:32.030 --> 00:31:39.981 - certainly show up as a police report But it may not come to Aries the Aries software at all because 00:31:39.981 --> 00:31:48.568 - it's not considered like a crash Okay, because it didn't have a car. Yeah, and then similarly like electric 00:31:48.568 --> 00:31:52.702 - bicycles is that Separated out in any way right now 00:31:53.378 --> 00:32:03.108 - Not very well or consistently. At this time, no, they would just be labeled as as bicycles, most likely. 00:32:03.108 --> 00:32:12.745 - OK. And there are categories. There are some categories for for those different transportation options, 00:32:12.745 --> 00:32:22.846 - but they they're not consistent. There's a lot of errors. So there's like a lot not consistently being used. 00:32:23.394 --> 00:32:32.681 - In terms of coding it. Yeah, it's not. Yeah, there's I think more training might be needed or just maybe 00:32:32.681 --> 00:32:41.527 - they didn't maybe the police didn't have time. It's it's not it's not consistent and requires a lot 00:32:41.527 --> 00:32:50.814 - of cleanup. So we don't currently show it right now. Okay. And the other related question has to do with 00:32:52.642 --> 00:33:00.542 - List of causes is that taken directly from like the police reports? Like how did you determine? Yeah, 00:33:00.542 --> 00:33:08.751 - that's that's directly from the crash crash a to that would be just a selection that the that the officer 00:33:08.751 --> 00:33:16.573 - would make which one the primary factor or the Manner of collision, which one are you talking about? 00:33:16.573 --> 00:33:18.974 - Okay, so the officer selects a 00:33:20.290 --> 00:33:29.173 - the cause with primary factor and obviously a lot of them you know overlap and could easily select you 00:33:29.173 --> 00:33:37.970 - know one when maybe a couple applied or a different one was better. That is also subjective and up to 00:33:37.970 --> 00:33:46.681 - the officer basically. Right. And do you know are there secondary factors too. Like can they do they 00:33:46.681 --> 00:33:49.182 - get to select more than one. 00:33:49.506 --> 00:33:57.522 - Or are you not sure that I'm not sure about. OK. But there wasn't a way for you to like say have a primary 00:33:57.522 --> 00:34:05.613 - cause chart the way you have here and then a secondary cause chart like you couldn't select out a secondary 00:34:05.613 --> 00:34:13.779 - the narrative. The narrative will sometimes detail what the primary cause is and then it'll detail secondary 00:34:13.779 --> 00:34:17.150 - issues that led to the primary issue itself. 00:34:17.602 --> 00:34:26.440 - Narrative sometime can be several paragraphs Yeah Our engineering folks would look into all those crash 00:34:26.440 --> 00:34:35.277 - reports in more detail read the narratives Not just necessarily depend on this field the primary factor 00:34:35.277 --> 00:34:43.945 - of crash field So they would get a lot more detail from their crash reports this but this is We don't 00:34:43.945 --> 00:34:46.494 - so when we edit data we don't 00:34:46.754 --> 00:34:54.055 - Go in read every single narrative and then update or make our own judgment call on what the primary 00:34:54.055 --> 00:35:01.502 - factor was. We just go based on what the police officer selected. Okay great. Thank you. I might note 00:35:01.502 --> 00:35:09.533 - there's another item that falls through the cracks and that's horse drawn vehicles or horses with pedestrians 00:35:09.533 --> 00:35:13.694 - or with bicycles. This was an issue in northern Indiana. 00:35:13.922 --> 00:35:23.575 - So years ago with Yamish communities where a vehicle would strike a horse or a horse drawn carriage 00:35:23.575 --> 00:35:33.228 - and those were reported as pedestrian even though they were not necessarily pedestrian changes have 00:35:33.228 --> 00:35:42.398 - been made on that and those are always noted in the narratives themselves. So I appreciate you 00:35:42.882 --> 00:35:53.553 - on the scooters and it would be interesting to have some delineation between e-bikes and scooters because 00:35:53.553 --> 00:36:03.921 - one is much faster than the other and they're driven in different ways but so I would assume since our 00:36:03.921 --> 00:36:12.478 - focus is roadways that we are not going to be tracking ATV accidents in a farm field 00:36:12.898 --> 00:36:20.939 - Privately right. So we're not tracking that right. One of the things we're looking at in Monroe County 00:36:20.939 --> 00:36:28.901 - is to allow on certain road county roads the use of four wheel utility vehicles. And if we were to do 00:36:28.901 --> 00:36:36.708 - that I would assume that would be encompassed in the report somehow if there were an incident if it 00:36:36.708 --> 00:36:41.470 - touches the roadway. Yes. Okay. Perfect. That's public room. 00:36:41.634 --> 00:36:49.430 - Yeah, public heard. I'm sorry. Yeah. Perfect. Thank you. Well, I suppose the public, the private one 00:36:49.430 --> 00:36:57.227 - would also be report if the police were called and showed up, the private one would also be on there 00:36:57.227 --> 00:37:04.483 - as well. Yeah. I actually have another question that was brought up by a commissioner Thomas. 00:37:04.483 --> 00:37:08.574 - So thank you. Um, what about single vehicle crashes? 00:37:08.834 --> 00:37:15.623 - Because in here, I think all of this implies that, well, actually, I guess this is crashes involving 00:37:15.623 --> 00:37:22.614 - one or more. Yes. But all of it's one or more motor vehicles. So what about a single bicycle, a single? 00:37:22.614 --> 00:37:29.739 - I think we would have to read the narratives. A single what? Well, it says bicycle. Because I did realize 00:37:29.739 --> 00:37:36.461 - motor vehicle crashes involves one or more motor vehicles. So maybe a single vehicle crash. Because 00:37:36.461 --> 00:37:38.814 - that's like a safety issue, right? 00:37:39.106 --> 00:37:46.295 - Like were they driving too fast or was there like some other problem in the roadway that needs some 00:37:46.295 --> 00:37:53.628 - kind of amendment? But a bicycle crash could be the same sort of scenario in terms well I'll just say 00:37:53.628 --> 00:38:00.961 - I had a bicycle crash once that was related to a railroad track that was not in good condition and So 00:38:00.961 --> 00:38:08.510 - something like that was a roadway issue That would be reported. It's like an incident or some some other 00:38:08.674 --> 00:38:16.302 - Not cry. I would not be put in the crash category like a couple of years ago I think there was a bicycle 00:38:16.302 --> 00:38:23.784 - that like fell into a hole because of road construction and that wasn't reported on the crash reports. 00:38:23.784 --> 00:38:31.339 - OK. With the with the vehicles. Yeah those those are on the crash reports if it's one vehicle only like 00:38:31.339 --> 00:38:37.150 - the one fatality where they ran off the road and hit a tree. OK. Great. Thanks. 00:38:42.658 --> 00:38:51.858 - You already know that I have this question since I asked it on one day, but there's we have a bunch 00:38:51.858 --> 00:39:01.150 - of local agencies who have done a bunch of work in the aftermath of fatal and serious injury crashes 00:39:01.150 --> 00:39:09.982 - to address those safety issues do we have any way of connecting this data with remediation that 00:39:11.010 --> 00:39:19.560 - Various agencies have performed like I know that in the aftermath of some of the fatal crashes on 37 00:39:19.560 --> 00:39:28.788 - south that in dot has proposed various measures to make those intersections safer Similarly in the aftermath 00:39:28.788 --> 00:39:37.592 - of serious injury crashes at Eagleson and 17th I know that the city of Bloomington did some quick build 00:39:37.592 --> 00:39:40.894 - infrastructure changes. Do we have any 00:39:41.570 --> 00:39:50.926 - way of seeing what, if anything, has been done in the places, like connecting in our data sets, whether 00:39:50.926 --> 00:40:00.731 - on the crash dashboard or in this report or something like that, to connect the remediation to the incidents 00:40:00.731 --> 00:40:09.727 - that have occurred. I mean, I can speak to the NDOT side of the equation. There was a crash at 17th 00:40:09.727 --> 00:40:11.166 - and the bypass. 00:40:11.810 --> 00:40:21.697 - Think that was earlier this year or maybe late last year involving a motorcycle turning left on a what 00:40:21.697 --> 00:40:31.487 - I'd call permissive yellow and We reported that we Made an actual telephone call on that one and that 00:40:31.487 --> 00:40:41.086 - one the engineering staff safety engineering staff Seymour district Made that a hard red hard green 00:40:41.346 --> 00:40:50.366 - no permissive left turn yellow after that one because of the site distance. Right. My point is that 00:40:50.366 --> 00:40:59.656 - people are already doing a lot of work to address these safety incidents and it would be valuable both 00:40:59.656 --> 00:41:08.766 - for us to understand like what gets addressed and what hasn't been addressed and also to communicate 00:41:09.634 --> 00:41:19.494 - that work that is in fact being done, as you say, because all of the LPAs represented here are taking 00:41:19.494 --> 00:41:29.643 - action when there are serious injury crashes. To be able to communicate that in something like the crash 00:41:29.643 --> 00:41:37.086 - dashboard. Yeah, yeah, I'm curious as to where, so first of all, if the LPAs 00:41:37.506 --> 00:41:45.886 - You know, we'd want to share that information or publicly in any way. And if so, where it would be most 00:41:45.886 --> 00:41:54.105 - useful or if they already share it in their own ways. I mean, certainly it's something we could do if 00:41:54.105 --> 00:42:02.163 - the crash falls within our purview as the of the MPA. But but yeah, if I don't know if Lisa has any 00:42:02.163 --> 00:42:05.950 - thoughts about that, I think you can see where 00:42:06.082 --> 00:42:14.437 - Some of the projects that get set up through the program that's usually typically derived from higher 00:42:14.437 --> 00:42:23.121 - crash locations for Monroe County old 37 south. If we have Fairfax Road we have the high friction project 00:42:23.121 --> 00:42:31.558 - there. So I think you can. I don't know how you want to relate it on the dashboard but I think you can 00:42:31.558 --> 00:42:35.326 - relate that the LPAs do set up those projects 00:42:35.778 --> 00:42:43.654 - in coalition to the trash data. And how you want to coincide it together on the dashboard, I get what 00:42:43.654 --> 00:42:51.375 - you're saying. I totally understand. People care a lot and are making significant investments based 00:42:51.375 --> 00:42:59.482 - on the fact that we all care a lot about this. And I think it would just be valuable to be able to track 00:42:59.482 --> 00:43:03.806 - that and communicate that to people who maybe don't see 00:43:03.906 --> 00:43:12.214 - Right. The connection between a crash a couple years ago and some project in the tip that and like then 00:43:12.214 --> 00:43:20.522 - some construction on their road that being able to communicate that I think would show our constituents 00:43:20.522 --> 00:43:28.670 - that we are in fact doing the good work that really is getting done here. And it might be also within 00:43:28.866 --> 00:43:35.052 - I know that city of Bloomington and Monroe County do a three-year crash data and I think in some of 00:43:35.052 --> 00:43:41.361 - those reports it shows the Improvements that you've made at certain areas and how that crash data has 00:43:41.361 --> 00:43:47.609 - decreased So I think there might be a way to even more report it in those those annual reports But I 00:43:47.609 --> 00:43:53.980 - think some of that is already there I think from I can't speak for city of Bloomington, but I'm pretty 00:43:53.980 --> 00:43:56.702 - sure that that's where you address that and 00:43:56.930 --> 00:44:02.999 - This is what the measurements this is why the crashes have decreased at this and this is why 00:44:02.999 --> 00:44:06.718 - this intersection has lowered on that on that chart. So. 00:44:08.482 --> 00:44:14.511 - Yeah kind of similarly and I want to say I really appreciate that you did this report and we talked 00:44:14.511 --> 00:44:20.601 - about it maybe a few months ago about the concept and I really appreciate that that you did this and 00:44:20.601 --> 00:44:26.872 - maybe one of the things that could be potentially added to your you have the 2025 fatal crash locations 00:44:26.872 --> 00:44:33.263 - and descriptions maybe another column could be added that's like was there any remediation or any changes 00:44:33.263 --> 00:44:37.182 - as a result because like the 17th Street and the bypass thing is 00:44:37.314 --> 00:44:45.389 - is on here. And there was a change as a result of that particular crash. And I think some of the other 00:44:45.389 --> 00:44:53.307 - ones too, as people have said. And maybe that kind of thing could get easily added on as a column to 00:44:53.307 --> 00:45:01.147 - yearly reports on this in the future by all entities. Because I mean, if we have kind of an ongoing 00:45:01.147 --> 00:45:07.262 - list over the years of these, then it could get, I guess I would hope that in 00:45:07.362 --> 00:45:16.169 - Areas that that do have serious or fatal injuries because of something that could be changed like the 00:45:16.169 --> 00:45:22.558 - 17th and bypass where like the light timing was changed essentially that. 00:45:23.010 --> 00:45:29.272 - we would track those over the years like if the change is big enough that we can't necessarily afford 00:45:29.272 --> 00:45:35.533 - it this year but we do it three years down the road that we can retroactively go back and be like hey 00:45:35.533 --> 00:45:42.286 - remember this thing and then keep that as a column because I mean we don't have I mean we're not Indianapolis 00:45:42.286 --> 00:45:48.486 - you know we're not having a fatal crash every day and so at least locally it feels like we should be 00:45:48.486 --> 00:45:50.942 - able to track that over multiple years. 00:45:51.074 --> 00:46:00.144 - Speaking for the Office of Traffic Safety They meet annually in February of every year central office 00:46:00.144 --> 00:46:09.747 - district office safety staff meet with the MPOs urbanized areas and we go through rankings of intersections 00:46:09.747 --> 00:46:19.262 - and also segments roadway segments based on fatality costs crash costs and property damage crash costs and 00:46:19.554 --> 00:46:26.868 - And those are usually noted that if something went down because of a countermeasure application the 00:46:26.868 --> 00:46:34.256 - previous year the previous same years sometimes it takes to three years or four years before some of 00:46:34.256 --> 00:46:41.790 - the countermeasures will actually show up in a reduction. But yeah we they do that. They do that every 00:46:41.790 --> 00:46:45.886 - year. All locations within the entire Seymour district. 00:46:46.498 --> 00:46:55.033 - And within our respective urbanized areas and then they consult with us on the urbanized areas Okay, 00:46:55.033 --> 00:47:03.738 - this is what it is. This is what we did This is what's happening. What do you think and we provide our 00:47:03.738 --> 00:47:12.189 - our input on those issues? Julie did you have a no? Okay. Yeah, I was just gonna say I had be happy 00:47:12.189 --> 00:47:16.414 - to report that information somehow if the LPS are 00:47:16.994 --> 00:47:36.959 - Okay with that, so I'll try and reach out to them. Additional questions, anybody? We've got time. We're 00:47:36.959 --> 00:47:43.294 - doing well. Thank you. Item 6.9. 00:47:45.826 --> 00:47:54.049 - Just to share a few updates on some local projects that are receiving MPO funds And some that are receiving 00:47:54.049 --> 00:48:01.738 - state-to-state funds the Monroe County high friction surface treatment on Fairfax Road project. They 00:48:01.738 --> 00:48:08.667 - have finalized their designs The soil sampling is in progress and they're working on stage 00:48:08.667 --> 00:48:14.910 - three documentation there is no right-of-way or utility work for this project and 00:48:15.522 --> 00:48:23.934 - Dillman Road bridge number 83 the design is in progress. The bridge will have to be closed 00:48:23.934 --> 00:48:33.363 - Due to environmental reasons they're working on stage 2 design submission and The right away phase is 00:48:33.363 --> 00:48:38.910 - moving to fiscal year 27 old SR 37 and Dillman Road project 00:48:40.930 --> 00:48:49.477 - The the dates for that project are shifting. We'll be talking about that later No cars features were 00:48:49.477 --> 00:48:58.194 - found on the property and they'll finalize drainage and detention in June Bridge safety inspection and 00:48:58.194 --> 00:49:05.726 - inventory the county completed that in March which was the required compliance month and 00:49:07.426 --> 00:49:16.646 - Rockport Road Bridge number 308 on South Bowlin Lane south of Bowlin Lane. The construction will begin 00:49:16.646 --> 00:49:26.315 - in June and the bridge is expected to close June 2nd. I'm assuming that's still accurate Lisa for Rockport. 00:49:26.315 --> 00:49:33.118 - Yeah it has been moved to June 8th. Just when it will close. OK. Thank you. 00:49:37.410 --> 00:49:45.569 - Eagleson Avenue Bridge replacement over the Indiana Railroad. They are doing pre-construction meetings 00:49:45.569 --> 00:49:54.124 - and road closure is anticipated September 2026. High Street, the city of Bloomington's High Street project. 00:49:54.124 --> 00:50:02.124 - Right-of-way acquisition is complete. Utility locations will take place this year. Construction next 00:50:02.124 --> 00:50:03.550 - year. The project 00:50:03.650 --> 00:50:13.023 - The project's construction phase unfortunately currently does not have any federal NPO funds But we 00:50:13.023 --> 00:50:22.677 - will be reviewing the addition of funds to that project later in this meeting Anticipated road closure 00:50:22.677 --> 00:50:32.894 - for 2026 utility locations relocations will be a mixture of flagging and one way Downtown curb ramps project 00:50:34.210 --> 00:50:44.640 - Phase four They're waiting on environmental report and No utility or right-of-way is required for the 00:50:44.640 --> 00:50:55.683 - project crosswalks phase three and North done are both in design North done project is going to be starting 00:50:55.683 --> 00:50:58.750 - right-of-way acquisition soon 00:51:03.362 --> 00:51:12.149 - College of Walnut Street phase one. The final analysis is still in progress. They anticipated construction 00:51:12.149 --> 00:51:20.526 - dates will be pushed out to fiscal year 30. We'll talk about that later. Curbs phase five designs and 00:51:20.526 --> 00:51:28.984 - project and they in process and they just issued a notice to proceed to a consultant. Crosswalks phase 00:51:28.984 --> 00:51:32.926 - four design consultant selection is in process. 00:51:34.626 --> 00:51:47.702 - And West Second Street there was a press release just yesterday the day before about that and construction 00:51:47.702 --> 00:51:59.678 - starting on that soon. Utility relocations are in progress. Any other comments. Question comment. 00:52:03.298 --> 00:52:12.065 - Bypass to Pete Ellis and Discovery Parkway 45 State Road 45 update There's there's still doing their 00:52:12.065 --> 00:52:20.920 - pre-construction and back pack Becky Packer could update but as far as I'm aware, they're still doing 00:52:20.920 --> 00:52:29.687 - their pre-construction and utility progress meetings will take place in June and We won't know about 00:52:29.687 --> 00:52:33.246 - road closures until those meetings occur 00:52:34.626 --> 00:52:40.711 - I would ask that you include that in your update every month, please, because I keep asking it every 00:52:40.711 --> 00:52:47.037 - month. There's a lot of concern out in the area I live in on that road out there because of what's going 00:52:47.037 --> 00:52:52.821 - to happen with road closure and those type of things, because it is a choke point, one road in, 00:52:52.821 --> 00:52:59.026 - one road out, and people are really sensitive of that. And there's a lot of activity with the students 00:52:59.026 --> 00:53:02.942 - and the church and the elementary school and so on in that area. 00:53:03.330 --> 00:53:11.313 - If you just give us a monthly update along with the other folks here that would be greatly appreciated. 00:53:11.313 --> 00:53:19.449 - Thank you. Currently the utilities are all this year so construction doesn't start till next year. Andrew 00:53:19.449 --> 00:53:27.124 - I know is he and his staff has invited to the pre con which I think is soon next week. But we won't 00:53:27.124 --> 00:53:32.574 - know anything about the utilities until mid June in the contract book. 00:53:33.602 --> 00:53:45.658 - I believe only Discovery and Pete Ellis are the closures, and those are not at the same time, so there 00:53:45.658 --> 00:53:52.798 - will be two different phases. I don't believe 45 will close. 00:54:05.410 --> 00:54:16.440 - moving on to Old business saying no old business new business item 8.1 We have some tip updates for 00:54:16.440 --> 00:54:27.910 - your consideration and approval The first update is to add a new Monroe County project called that road 00:54:27.910 --> 00:54:31.550 - bridge number 79 replacement and 00:54:33.794 --> 00:54:42.056 - The project is going to receive local bridge funds from the state of Indiana for its construction phases, 00:54:42.056 --> 00:54:50.006 - but all other phases will be using local funds. So no MPO funds, but state bridge funds. The proposed 00:54:50.006 --> 00:54:58.033 - work is removal and replacement of the existing bridge, and then also potentially upgrading the bridge 00:54:58.033 --> 00:55:02.398 - rail and adding multi-use path with pedestrian handrail 00:55:02.690 --> 00:55:14.513 - on the north side of the bridge. This is the bridge on that road right next to the Clear Creek Trail. 00:55:14.513 --> 00:55:26.451 - So you can see the proposed funds in the table below. I see I forgot the total project cost there. The 00:55:26.451 --> 00:55:28.190 - next update is 00:55:28.738 --> 00:55:35.989 - I had a question about that which maybe Lisa can answer which is will the There be a connection between 00:55:35.989 --> 00:55:42.961 - the path that's proposed for the bridge and the Clear Creek Trail that's adjacent there Yeah, we've 00:55:42.961 --> 00:55:50.002 - worked hand-in-hand with Tim Street and the staff and everything on the design of everything to make 00:55:50.002 --> 00:55:52.094 - it work with the trail Mm-hmm 00:55:55.970 --> 00:56:04.388 - The next update is related to some of the items we talked about last last meeting which were a shifting 00:56:04.388 --> 00:56:12.645 - of funds and so college and walnut phase one project the city desired to move the construction phases 00:56:12.645 --> 00:56:20.820 - for that project to fiscal year 2030 just as a projection lining it up with phase two of the project 00:56:20.820 --> 00:56:24.382 - and hopefully addressing both both at once. 00:56:25.634 --> 00:56:34.727 - More information to come, but 2030 is still plenty of time in the future as of now. And so they have 00:56:34.727 --> 00:56:43.820 - determined, though, that to be safe, they'd like to move it to fiscal year 30. And so what happened, 00:56:43.820 --> 00:56:52.824 - and then also the county, to be safe, wanted to move old SR 37 and Dillman Road project from fiscal 00:56:52.824 --> 00:56:54.174 - year 28 to 29. 00:56:55.362 --> 00:57:04.068 - And so what we had to do, and this is all detailed in the memo from the last meetings packet, what we 00:57:04.068 --> 00:57:12.774 - had to do is that money that was freed up in 2029 by College of Walnut phase one. MPO staff were able 00:57:12.774 --> 00:57:22.334 - to give about half of that to the Dillman Road intersection, the Dillman and SR 37 project when it moved to 29. 00:57:22.498 --> 00:57:34.572 - around two million about two million of that 29 funds the remaining two million of the 29 funds were 00:57:34.572 --> 00:57:46.645 - exchanged with another MPO for 2030 funds so that used the 2029 funds and then when Dillman moved to 00:57:46.645 --> 00:57:50.590 - 29 that freed up funds in 28 and 00:57:54.050 --> 00:58:06.221 - The MPO exchanged 28 funds for fiscal year 27 funds. And so the tables in item two and three show those 00:58:06.221 --> 00:58:17.924 - changes with College and Walnut and 37 and Dillman moving to their new fiscal years. And then those 00:58:17.924 --> 00:58:20.382 - exchanges happening. 00:58:23.266 --> 00:58:31.198 - High Street then was able to get some federal funding for its construction phase in 27 due to exchanging 00:58:31.198 --> 00:58:39.131 - with another MPO. So you can see in this table that exchange with the Area Plan Commission of Tippecanoe 00:58:39.131 --> 00:58:46.685 - County allows us to get High Street, which is good because the LPAs spend extra money going through 00:58:46.685 --> 00:58:53.182 - the federal review process so they can be eligible for federal funds through the MPO. 00:58:53.538 --> 00:59:08.700 - And we always want to try and get them as many federal funds as possible, especially in the construction 00:59:08.700 --> 00:59:21.118 - phases. And then I'll finish up all of those by saying, if these proposed changes are 00:59:23.106 --> 00:59:35.786 - Approved This is a brief table a brief snapshot of what the fiscal constraint would look like so We 00:59:35.786 --> 00:59:47.198 - have You know allocated our funds for 26 27 30 but after all of these exchanges we have a 00:59:48.386 --> 00:59:56.843 - some allocated funds. We have plenty of things in fiscal year 20 and 29 to apply those funds to but 00:59:56.843 --> 01:00:05.384 - we haven't formally allocated them to any project yet. We'll have those discussions in July with the 01:00:05.384 --> 01:00:13.502 - LPS to try and figure out what might be best. Either that or MPO staff will make a proposal and 01:00:14.274 --> 01:00:24.277 - Bring it to the the committee, but we plan to talk to LPS about that first so Those changes will be 01:00:24.277 --> 01:00:34.380 - coming in the future Any questions comment Scott Brought this up. Let I brought this up last meeting 01:00:34.380 --> 01:00:41.982 - and I'll continue to bring it up because there's a lot of Negative pushback 01:00:42.690 --> 01:00:49.513 - Social media even at the lunch bunches and the breakfast bunches that get together and talk with respect 01:00:49.513 --> 01:00:56.140 - to college and walnut I'm not taking issue with any of the funding discussion that's up here on phase 01:00:56.140 --> 01:01:02.833 - one phase two I just don't know and if there is what in fact you're going to do in phase one and phase 01:01:02.833 --> 01:01:09.656 - two The options that have been proposed for college and walnut. There's a lot of folks who are not happy 01:01:09.656 --> 01:01:12.190 - with them Those comments are out there 01:01:13.058 --> 01:01:19.113 - the groups that I represent want to see what those changes are. And so when I see that we're moving 01:01:19.113 --> 01:01:25.288 - forward with funding for phase one and phase two that tells me there is a one a requirement on the on 01:01:25.288 --> 01:01:31.706 - the books and there's funding sources being identified to meet that requirement. That's my understanding. 01:01:31.706 --> 01:01:38.306 - So do we have my question is as we go forward with college and Walnut we need to have a better understanding 01:01:38.306 --> 01:01:42.302 - what in fact is going to what the options really are and and what 01:01:42.978 --> 01:01:50.357 - that I guess the city is going to decide decide upon because of the concern that is out there with respect 01:01:50.357 --> 01:01:57.460 - to the options that have been discussed previously. And Andrew you might talk to that or maybe there's 01:01:57.460 --> 01:02:04.494 - some maybe there's definitions on what phase one phase two does and that would be very helpful for us 01:02:04.494 --> 01:02:10.494 - to get asked questions about it so we can explain it to others. Yeah I guess just big. 01:02:10.754 --> 01:02:19.279 - College and walnut have been in the tip since the last call for projects. So essentially what's it we're 01:02:19.279 --> 01:02:27.398 - looking at right now is essentially a specific to that project is Essentially pushing it out a year 01:02:27.398 --> 01:02:35.599 - so still keeping it in the tip but not changing it but getting more time because Things are still in 01:02:35.599 --> 01:02:39.902 - motion the city Does have plans to move forward with 01:02:40.034 --> 01:02:48.107 - Adoption of a study, but that hasn't yet been Completed or really it formally started So it will be 01:02:48.107 --> 01:02:56.825 - discussed publicly in a future Transportation Commission meeting of the city of Bloomington then ultimately 01:02:56.825 --> 01:03:04.898 - the intent is for City Council to weigh in as an amendment to the city's transportation plan and so 01:03:04.898 --> 01:03:09.822 - anything that would be a part of a project with MPO funds is 01:03:10.178 --> 01:03:16.776 - Gonna be pending all of that and that's why it's been pushed out of here because that hasn't been been 01:03:16.776 --> 01:03:23.439 - formalized So I hope that answers the questions, but I do know there is some uncertainty I do know that 01:03:23.439 --> 01:03:29.909 - there is not an official plan Out there and that it will be forthcoming in the coming months And I'm 01:03:29.909 --> 01:03:36.763 - just trying to I had a minute I could pull up roughly when we think it will be going to the Transportation 01:03:36.763 --> 01:03:39.518 - Commission of the city of Bloomington Yeah 01:03:39.842 --> 01:03:45.268 - So that helps somewhat I still don't know what phase one and phase two does other than the fact that 01:03:45.268 --> 01:03:50.694 - it's a placeholder for money Probably for the study that's coming up with options that you all would 01:03:50.694 --> 01:03:56.066 - take and discuss within transportation and And the council etc. I assume that's the approach you're 01:03:56.066 --> 01:04:01.653 - taking something like that Yeah, I think specific to the the money that's in this project is it's still 01:04:01.653 --> 01:04:04.446 - going to be pending official adoption of a plan but 01:04:04.610 --> 01:04:11.002 - But this money generally speaking what I anticipated to address is More like maintenance focused and 01:04:11.002 --> 01:04:17.711 - low-hanging fruit like connecting building sidewalks where it does not exist Replacing old traffic signal 01:04:17.711 --> 01:04:24.103 - infrastructure and upgrading intersections to be consistent with whatever the to be adopted plan are 01:04:24.103 --> 01:04:30.495 - but there is just some some old infrastructure that needs to be replaced so more maintenance focused 01:04:30.495 --> 01:04:33.406 - but in a manner that would be consistent with 01:04:33.698 --> 01:04:41.225 - What the future corridor plan is and so my next question is what is the role of this body? with respect 01:04:41.225 --> 01:04:48.608 - to options being considered I Guess by the city transportation and City Council. Do we have a role in 01:04:48.608 --> 01:04:55.918 - that this body right here? I Think the role of this body of any project in the tip is essentially to 01:04:55.918 --> 01:05:02.142 - approve the funding of the project and that's and that has already been completed and 01:05:02.370 --> 01:05:13.962 - So ours is not to question the options ours is to approve the funding. That is my understanding. Okay. 01:05:13.962 --> 01:05:25.554 - Thank you. Julie. I think based on Scott's question my question is for the city representatives if you 01:05:25.554 --> 01:05:28.030 - could tell the public 01:05:28.354 --> 01:05:37.102 - When and how they can comment on a plan once it's published Or as it's being revised and considered 01:05:37.102 --> 01:05:46.112 - and then who actually ratifies it. Thank you Yeah, that that's a great question. So ultimately my best 01:05:46.112 --> 01:05:49.086 - estimate is that sometime in July 01:05:49.314 --> 01:05:55.758 - There will be a transit a specific transportation commission of the city of Bloomington meeting to review 01:05:55.758 --> 01:06:01.958 - and discuss the corridor study and the findings and that would be a meeting that public comment would 01:06:01.958 --> 01:06:08.037 - be welcome. And then after that meeting it will also need to go to the city plan commission because 01:06:08.037 --> 01:06:13.022 - it would be an amendment to the city's transportation plan and then and so likely 01:06:13.506 --> 01:06:20.446 - Maybe later in July or August and then and then after that would go to City Council So all three of 01:06:20.446 --> 01:06:27.524 - those public bodies will review and have opportunity for public input I'm just gonna add to that that 01:06:27.524 --> 01:06:34.533 - on the city of Bloomington website bloomington.in.gov slash transportation that slash see see WCS is 01:06:34.533 --> 01:06:38.142 - the college and walnut corridor study page and that 01:06:38.338 --> 01:06:47.092 - I believe is generally updated with things like public input sessions and stuff like that. So that is 01:06:47.092 --> 01:06:55.932 - another place that the public can just kind of look to keep track of. I have generally found that like 01:06:55.932 --> 01:06:58.078 - the previously mentioned 01:06:58.530 --> 01:07:07.257 - Bloomington transit input sessions about the route change like usually these sorts of meetings are pretty 01:07:07.257 --> 01:07:15.490 - well publicized in terms of input from the public So my follow-up to that is Lots of questions have 01:07:15.490 --> 01:07:24.958 - been asked I know I I have asked questions answers to those questions have not necessarily been forthcoming and so 01:07:25.442 --> 01:07:32.158 - I know in other bodies we go to great pains in the public hearing portion to attempt to address every 01:07:32.158 --> 01:07:39.006 - single question and provide at least, whatever the body is, feedback on what we think the proper course 01:07:39.006 --> 01:07:45.656 - of action is. So I understand that things are being posted, and I understand the city's website, and 01:07:45.656 --> 01:07:52.437 - I understand all that, but the public is not necessarily aware of all these websites, nor do they even 01:07:52.437 --> 01:07:53.886 - go to these websites. 01:07:54.210 --> 01:08:00.887 - And so they rely upon whatever that body is, that hearing body, to come forth and hear the presentation 01:08:00.887 --> 01:08:07.628 - of what's being proposed and then to take and provide a comment on what they think about that. And we've 01:08:07.628 --> 01:08:14.176 - seen that recently in other activities that have been taking place within the city and county. I know 01:08:14.176 --> 01:08:20.788 - personally outside of a select body of an awful lot of people who do not want to have the changes that 01:08:20.788 --> 01:08:23.934 - are being proposed made to college and wellness. 01:08:24.866 --> 01:08:30.929 - They don't think it's right. They think it's going to be an impediment on the downtown, the businesses, 01:08:30.929 --> 01:08:37.051 - and likewise. And even the flow of traffic, when in fact we have students and parents and football games 01:08:37.051 --> 01:08:42.939 - and basketball games and the like, and what's going to happen to the community. Now, I'm not here to 01:08:42.939 --> 01:08:48.769 - debate those topics here. I apologize if others see that's what I'm trying to do. I'm not trying to 01:08:48.769 --> 01:08:54.366 - do that. I just want to make sure that whatever comments are coming forward, they're addressed. 01:08:54.690 --> 01:09:00.632 - and sometimes they're positive and sometimes they're negative. I understand that. But people need to 01:09:00.632 --> 01:09:06.692 - be aware of that and putting it on a website is not necessarily the right course of action because not 01:09:06.692 --> 01:09:12.869 - everybody has access to that website. That's my only comment. I'm encouraging the public hearing portion 01:09:12.869 --> 01:09:18.811 - where people have a chance to come out and vet and they need to hear responses to their questions on 01:09:18.811 --> 01:09:23.518 - why or why not their considerations are being addressed. That's all. Thank you. 01:09:24.514 --> 01:09:30.173 - I would say that those things are already being done and I would say that all of us and all 01:09:30.173 --> 01:09:36.448 - of our organizations advertise the best we can to get as much feedback as possible from the community 01:09:36.448 --> 01:09:42.846 - and there's always the argument of oh well so-and-so doesn't have access to this so-and-so doesn't have 01:09:42.846 --> 01:09:49.182 - access to that there's always going to be that argument in terms of public feedback and there's always 01:09:49.858 --> 01:09:57.065 - much effort as possible given to trying to get the word out to all all manner of of people who might 01:09:57.065 --> 01:10:04.415 - want to respond to that and so to public who are listening to this or to Members of the public who you 01:10:04.415 --> 01:10:11.694 - might speak to like I mean If somebody is that interested in that concern what they could always call 01:10:11.694 --> 01:10:15.262 - the city and talk directly, you know on the phone 01:10:15.522 --> 01:10:24.033 - To a member of planning and transportation or engineering who would be happy to let them know about 01:10:24.033 --> 01:10:32.545 - those input sessions via telephone, but I mean all we can do is is advertise on the mediums that we 01:10:32.545 --> 01:10:41.822 - have I would just like to emphasize that public hearings as we can see from the high attendance level at the 01:10:41.954 --> 01:10:50.251 - this public hearing are not always the most accessible way to provide information to the public. And 01:10:50.251 --> 01:10:58.630 - so we shouldn't over-index on attendance at public hearings, which tends to feature the same sorts of 01:10:58.630 --> 01:11:07.174 - people all the time, like me. I attend a lot of public hearings and public meetings. But it's important 01:11:07.174 --> 01:11:11.774 - to have broad access beyond the sorts of people who can 01:11:11.970 --> 01:11:22.315 - make it to meetings like this one or like the Transportation Committee. But I have a different question, 01:11:22.315 --> 01:11:32.955 - which is, Katie, we're making a bunch of trades with other MPOs around the state as part of these fundings. 01:11:32.955 --> 01:11:41.822 - Are we getting back, how much are we losing in a dollar amount since across these trades? 01:11:42.050 --> 01:11:52.756 - losing in what way? Other than inflation. When we go to these other MPOs and say, are we trading dollar 01:11:52.756 --> 01:12:03.359 - for dollar or are we giving more than we're getting since we're the ones who need to make these trades 01:12:03.359 --> 01:12:10.462 - to accommodate schedule changes? Making trades is quite common among 01:12:10.658 --> 01:12:17.946 - most of the MPOs because especially the smaller ones because They often only do one or two projects 01:12:17.946 --> 01:12:25.235 - at a time and they try to maximize the funding For that project and so they'll you know Group a lot 01:12:25.235 --> 01:12:32.741 - of funds into one year and maybe don't have funds for the next couple years as that construction takes 01:12:32.741 --> 01:12:36.094 - place so but yes, it is dollar for dollar and 01:12:36.450 --> 01:12:44.936 - It does not account for inflation. So, you know if we are getting 20 30 funds from somebody else giving 01:12:44.936 --> 01:12:53.177 - them our 20 29 certainly There is some unspoken loss there, but we are getting 27 funds for somebody 01:12:53.177 --> 01:13:00.766 - else's 20 and we're giving them 28 so you could also argue that it balances out in a way and 01:13:01.794 --> 01:13:12.067 - Okay, thanks, I seem to recall that an earlier trade that we did we ended up Down a small amount I Think 01:13:12.067 --> 01:13:22.438 - when we did a trade with the Indianapolis NPO The Indianapolis NPO trade was for the first street project 01:13:22.438 --> 01:13:28.798 - yeah, and that was dollar-for-dollar. Oh that was okay. Yeah and 01:13:28.930 --> 01:13:36.842 - We got their money and spent it immediately and we're not paying them back until later They asked about 01:13:36.842 --> 01:13:44.449 - an inflationary factor. We laughed they agreed and Yeah, because they had they had to use the money 01:13:44.449 --> 01:13:52.665 - or lose it I'm glad that our MPO staff drives a hard bargain with the other MPs Especially in Indianapolis. 01:13:52.665 --> 01:13:58.142 - Yes More broadly I expressed this worry at the CAC meeting as well, but 01:13:59.362 --> 01:14:11.858 - Given that we're making all of these changes roughly to move projects that are already in the tip to 01:14:11.858 --> 01:14:24.602 - later years for reasons that are very understandable, I'm concerned that we need to be planning as for 01:14:24.602 --> 01:14:28.190 - projects further out so that 01:14:28.418 --> 01:14:39.623 - we don't run out. If our 2030 projects are projects that we were putting in the tip in 2024, like for 01:14:39.623 --> 01:14:50.608 - college and Walnut, then the projects that are going to be listed in, major projects that are going 01:14:50.608 --> 01:14:58.078 - to be in the tip for 2031 or 2032 are projects that we would expect 01:14:58.210 --> 01:15:08.914 - to be seeing in the tip already and they aren't there right now. So, obviously this is not something 01:15:08.914 --> 01:15:19.512 - that we're going to address at this meeting. However, this is a concern I have that right now we're 01:15:19.512 --> 01:15:26.718 - not proposing things with the, proposing sufficient things with the 01:15:27.042 --> 01:15:38.236 - Recognition of what the timelines for the projects we actually execute look like Yeah, I mean You can 01:15:38.236 --> 01:15:49.870 - kind of consider the NPO a little bit like a grant agency of some sort You know the local LPAs do propose 01:15:49.870 --> 01:15:56.894 - projects The NPO itself doesn't have the authority to work with 01:15:57.314 --> 01:16:05.302 - consultants and contractors and do our own projects and I think I think Indy MPO does that but But We 01:16:05.302 --> 01:16:13.760 - do have a new tip cycle every two years and so that will often bring things up also there could be projects 01:16:13.760 --> 01:16:21.592 - that Will be submitted with this falls call for projects for the next tip that maybe are not in the 01:16:21.592 --> 01:16:26.526 - tip at this point because the local public agencies plan to do 01:16:26.722 --> 01:16:35.292 - the preliminary engineering phases and the right away phases with just local money. And they may want 01:16:35.292 --> 01:16:43.863 - to apply for federal funding for the construction phases. And that's why it's maybe not on the tip at 01:16:43.863 --> 01:16:52.517 - this point. With regards, I mean, I'm not in the mind of the folks that do submit projects at the call 01:16:52.517 --> 01:16:55.038 - for projects every two years. 01:16:55.266 --> 01:17:02.488 - But I think that a big priority of, you know, City of Bloomington in particular is College and Walnut 01:17:02.488 --> 01:17:10.207 - Project. And that will take some time, which is probably why you don't see much else in the future upcoming. 01:17:10.207 --> 01:17:17.288 - That will take a lot of funding. So if these two have any other insights? I agree. I agree. I think 01:17:17.288 --> 01:17:24.510 - the one thing I'll just add for the group's sake is until we approve what is currently on our docket, 01:17:24.642 --> 01:17:31.193 - Right now there is literally no money in the tip to program for the design of the project. That's beyond 01:17:31.193 --> 01:17:37.558 - 2030 So just is no incentive for an LPI to ask to add something when there isn't any money for it And 01:17:37.558 --> 01:17:44.047 - it I think in the coming months anticipating a new call for projects so I think they're just there just 01:17:44.047 --> 01:17:50.910 - isn't the incentive to Add it to the tip, but I imagine all agencies are always thinking about what's next. I 01:17:51.586 --> 01:17:59.374 - Mm-hmm. And I mean the tip is dynamic and if if there's nothing, you know Right now there might be in 01:17:59.374 --> 01:18:07.239 - 2032 And it might be something huge and all the funds, you know We may want to do trades for 2031 just 01:18:07.239 --> 01:18:15.409 - so we can get more funds into 2032. We're always gonna have to adjust depending on what the local projects 01:18:15.409 --> 01:18:19.838 - are that want funds and if they don't submit enough or if 01:18:20.034 --> 01:18:29.082 - You know, sometimes there are delays, environmental delays with NDOT or right of way delays that are 01:18:29.082 --> 01:18:38.489 - not anticipated. And, you know, I'm not saying that the project management is perfect. There's sometimes 01:18:38.489 --> 01:18:47.806 - more time maybe could be budgeted for certain things. But if the, you know, if they don't have anything 01:18:48.130 --> 01:18:55.395 - If they want to submit for federal funds or they don't have any projects they want to go through the 01:18:55.395 --> 01:19:02.588 - federal review process for and they just want to use local money, that's fine. We'll either move it 01:19:02.588 --> 01:19:10.141 - to a year where there is something that needs more or you know that thankfully there is a flexing option 01:19:10.141 --> 01:19:16.830 - to Bloomington Transit as well. But yes, I agree and there's definitely some work we can do. 01:19:17.058 --> 01:19:30.493 - with with regards to timelines Any other questions we still have a quorum I Guess okay in that case. 01:19:30.493 --> 01:19:44.194 - I move that we accept the amendments to the tip Do we need to move to approve resolution 2026 oh eight 01:19:44.194 --> 01:19:45.790 - is that the 01:19:46.050 --> 01:19:55.376 - Motion because that resolution is Sorry say that again see is the appropriate motion to approve resolution 01:19:55.376 --> 01:20:04.092 - 20 2608 as presented Yeah, the amendments within that resolution. Yeah Yeah, yes, that's that's the 01:20:04.092 --> 01:20:09.758 - motion is to approve the amendments to resolution 20 2608 second 01:20:16.674 --> 01:20:26.901 - We have a motion and we have a second. Do we have any other comments. Do we have public comment. Seeing 01:20:26.901 --> 01:20:37.129 - none all those in favor of resolution 20 26 dash 0 8 with the proposed changes do so by saying aye aye. 01:20:37.129 --> 01:20:46.078 - Any opposed. Seeing none motion carries. Moving on to public comment. I think we have any. 01:20:48.162 --> 01:20:58.010 - Communications from committee members on non-voting matters not included on the agenda Seeing none I 01:20:58.010 --> 01:21:07.857 - know I'm not a committee member, but may I just add to something that hope he asked earlier and that 01:21:07.857 --> 01:21:17.022 - is oh I Need to share something else here you asked about the amendments and modifications so 01:21:17.954 --> 01:21:25.878 - Even though that information is not in our tip, this has been posted to our website, and this shows 01:21:25.878 --> 01:21:33.643 - what we consider the first one is an amendment classification, and the next table is modification 01:21:33.643 --> 01:21:41.645 - classification. I'm happy to send that to you, but I will share this information at the next meeting 01:21:41.645 --> 01:21:46.558 - as well. This has been posted to our website on the tip page, 01:21:46.818 --> 01:21:56.287 - This shows what what our current process is And so essentially next meeting basically want to just do 01:21:56.287 --> 01:22:05.570 - a renewal a Review of this process with you guys and then if you want to make any changes to it you 01:22:05.570 --> 01:22:11.326 - can So we'll just be sharing it as an informational item next 01:22:11.554 --> 01:22:19.416 - Next meeting and then eventually if you do make any updates, we'll just put those into the next tip 01:22:19.416 --> 01:22:27.829 - for review this fall. I took this off the website recently because it wasn't accessible by screen readers. 01:22:27.829 --> 01:22:35.927 - And so that's when we took a few things off that weren't accessible and then they changed the deadline 01:22:35.927 --> 01:22:40.094 - for that. So I can put it back up there. That's all. 01:22:44.834 --> 01:22:52.091 - Thank you. The next meetings are technical advisory committee meeting is July 22nd at 10 a.m. Citizens 01:22:52.091 --> 01:22:59.348 - Advisory Committee is July 22nd at 5 30 p.m. And policy committee is July 24th at 10 30 a.m. All these 01:22:59.348 --> 01:23:03.646 - meetings are available by hybrid and I move for adjournment.