Connect with us

Kansas

The North Kansas City stadium site might just be the best one

Published

on

The North Kansas City stadium site might just be the best one


A lot has happened since John Sherman, principal owner of the Kansas City Royals franchise, first floated the idea of a new stadium in November of 2021. The road since then has been winding and frustrating, and four years and one failed vote later and we don’t know where the stadium is going or what it will look like.

But there is a light at the end of the tunnel. The Royals’ lease with the Truman Sports Complex ends after the 2030 season, which means they have to start on construction relatively soon to be ready by the 2031 season. Missouri and Kansas have both passed state-level funding. And the Royals had planned on announcing their final plan earlier this year, which implies they are close to an answer themselves.

Lately, there has been a lot of smoke surrounding the North Kansas City option. The office of NKC mayor Jesse Smith put out a press release on October 16 stating that:

The City of North Kansas City continues to have conversations with the Kansas City Royals regarding the possibility of a stadium and related development in North Kansas City. These discussions are substantial and will ultimately involve collaboration among the State of Missouri, Clay County, and the City in any final framework.

Additionally, the Missouri legislature had previously passed a bill that allows Clay County to create a sports complex authority that would govern the stadium. And we can’t forget that North Kansas City was one of two initial proposed sites by the Royals back in August 2023.

Advertisement

Like many folks, my reaction to the proposed Clay County site was one of skepticism. What was the point? To just leave a suburban area to go to another suburban area? Why not just stay in Kauffman Stadium?

I have since come around, and not because I am being paid off by the Royals. I have no idea what they’re doing and they have declined to comment on media requests about the stadium for a while now. No; I genuinely think that the North Kansas City site is the best one outside the East Village site, which seems dead. Let’s dig into why.

The Royals’ new stadium goals

So much has happened that it’s worth re-visiting the first real piece of official communication the Royals put into the world: an open letter from Sherman about what the Royals wanted to accomplish.

There are two things that stand out as clear benchmarks for what the Royals wanted the stadium to be from the very start of this project. First, though downtown was the primary goal, the Royals were cognizant that there were other sites that could work. They were pursuing sites “both in downtown Kansas City and close to it.”

Advertisement

Second, and most importantly, the Royals wanted to build a ballpark district, with “residential, commercial, and community components.” As Sherman wrote, their version was to construct “a new ballpark district and all that comes with it – one that is woven into the fabric of our city, can host events and concerts, and boosts our local economy.”

Why North Kansas City works

Kauffman Stadium is a beautiful park that exists within an ugly car dystopia that sucks the life out of the entire area. It’s surrounded by acres and acres of useless concrete. It’s cut off from goods, services, housing, and lodging. It is an unwalkable island wasteland.

Contrast that with walkable areas, where you don’t have to drive a car to get to where you want to go. More importantly, there are people already there. People live in walkable areas in multiunit apartments and condos, and walkable areas have narrower streets, more public transit, and a significantly higher density of resources and services than car-centric areas.

Downtowns are usually the only areas in American cities that have walkability and density. But suburbs can be walkable, too. Consider the area around Johnson Drive and Lamar in Mission, Kansas, versus the area around 119th Street and Strang Line Road in Olathe. Both Kansas City suburbs, but one is significantly prettier, more lively, and livable than the other.

Advertisement

North Kansas City is one of the only areas in the metro that has the ingredients for significant walkability. Indeed, the Armour Road area is already walkable and bikeable.

The above screenshot of Google Maps shows roughly where the Royals have proposed their site: bordered by Armour Road on the north and 16th Avenue on the south, and from Erie Street on the west to Howell Street on the east. North of Armour Road, there are rows and rows of houses, a public library, North Kansas City High School, and multiple new apartment complexes.

Add the streetcar into the equation, and the area quickly becomes an opportunity to transform into the type of urban neighborhood that is a destination. RideKC has already created an extensive and recent study of what an extension would look like up to North Kansas City, and their plan is to extend the line over the Heart of America Bridge and then up Swift Street.

And though walkability is key, car access is still easy. I-35 is immediately to the east, and there’s access to I-29, I-635, and Highway 169—along with access to downtown and I-70 via Highway 9.

So why wasn’t NKC the first choice?

Advertisement

No site is perfect, which I’m sure the Royals have grappled with significantly.

At the same time, there are some pretty big reasons why downtown is a better option than North Kansas City. One is population; the downtown KC population is about 32,000 people, compared to under 5,000 people in NKC as of the 2020 census. Furthermore, Jackson County has over two and a half times as many residents as Clay County, which is a significant difference when it comes to tax revenue and the inevitable “public” part of the “public-private partnership” that the Royals want.

And, of course, that streetcar thing? It’s already downtown.

But at this point in the juncture, North Kansas City is also the only place that fulfills all of the Royals’ initial desires for the project. The Washington Square Park site downtown is tiny and there is not space for a “ballpark village.” No site in Johnson County or Wyandotte County makes much sense for that, either, and a Legends site would end up as Kauffman Stadium West (derogatory).

If the Royals aren’t going to pull the trigger on the East Village site—which has always been the best choice—for whatever reason, North Kansas City provides a way to catalyze some public transit investment and transform the area into something the Royals can be proud of.

Advertisement

At least, if the public isn’t on the hook for too much money. But that, as they say, is a whole different ball game.



Source link

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Kansas

New downtown stadium will mean less parking for Royals fans

Published

on

New downtown stadium will mean less parking for Royals fans


KANSAS CITY, Mo. — From 25,000 parking spots to 19,000 within a 10-minute walk to the stadium, that’s how many Kansas City Mayor Quinton Lucas says will be available near the new Royals ballpark in Crown Center, with 9,000 of those spots on the actual campus.

While there will be less parking, Royals fan Roger Nickell says he believes this move is good for Kansas City.

“I think anything that makes Kansas City an exciting place to come to, and a good destination, the parking itself is not going to be the issue,” Nickell said “We’d rather have good things in our city, and if you go to other cities, Kansas City is actually really, really easy right now.”

While it might not be ideal for some, downtown stadiums and parking is the normal for a number of teams and cities throughout Major League Baseball. Upwards of 20 teams have a stadium in the downtown area, including the Twins, Cardinals and Tigers.

Advertisement

“I think every new stadium in the MLB is being built downtown, so I kind of expected it,” Royals fan Jackson Fort said. “I think parking will be kind of, they’ll have to figure out something because there’s going to be a big building and not a lot of space to put it. I think you’ll see a lot more Ubers and less of that tailgating scene that the chiefs and the royals are so known for.”

While tailgating as we know it will look different, walking to the stadium won’t actually look that bad if you use the streetcar. From the stop at the World War I Museum, you’re looking at a nine-minute walk to Crown Center, and four-minute walk if you get off at Union Station.

“I think it would be a good thing for the city, for the baseball park and for everybody,” avid streetcar user Gary Henderson said. “Especially for the people who use the trolley would get a chance to see how comfortable it is and maybe it’ll increase their business too.”

With hopes of the new stadium to be ready for opening day in 2030, the Royals, Kansas City, and fans have time to figure out any potential obstacles.

“I think we’ll get to figure it out,” Royals fan Caden Tucker said. “I think that they have plenty of time to be able to figure everything out and make sure everything’s not going to be packed in here and just kind of slowed down in the process.”

Advertisement

While a lot of parking will be taken away in the near future, if one thing is for certain, the Royals will not. The current lease for Kauffman stadium is set to expire in 2031.



Source link

Continue Reading

Kansas

PBS Kansas remembers employee killed in Wichita shooting; estranged husband charged

Published

on

PBS Kansas remembers employee killed in Wichita shooting; estranged husband charged

























PBS Kansas remembers employee killed in Wichita shooting; estranged husband charged | Trusted News Source for Wichita & Kansas | kake.com

We recognize you are attempting to access this website from a country belonging to the European Economic Area (EEA) including the EU which
enforces the General Data Protection Regulation (GDPR) and therefore access cannot be granted at this time.

For any issues, contact news@kake.com or call 316-943-4221.

Advertisement



Source link

Continue Reading

Kansas

Final 7-Round Kansas City Chiefs 2026 NFL Mock Draft: Putting my skills to the test against an AI trained to think like Brett Veach

Published

on

Final 7-Round Kansas City Chiefs 2026 NFL Mock Draft: Putting my skills to the test against an AI trained to think like Brett Veach


I trained my AI to think and draft like Kansas City Chiefs GM Brett Veach. Then I challenged it to a duel for my final 2026 NFL Mock Draft.

Chiefs GM Brett Veach speaks to the media during his pre-draft introductory press conference.
YouTube/Chiefs

You’re going to see a lot of final mock drafts for the Kansas City Chiefs this week, but I decided to make mine a little bit differently this year.

Advertisement

I wanted to give Chiefs fans an idea of what I would do while also adding a predictive element. What I settled on was a dueling mock draft against an AI trained to think like Chiefs GM Brett Veach.

How did I train my AI? First, I uploaded Veach’s draft history since he took over as general manager following the 2017 NFL Draft. Then, I fed it pre-draft and post-draft press conference transcripts to give the AI context on how Veach views the NFL Draft. I weighted the more recent press conferences more heavily. From there, I uploaded historical data on key thresholds at specific position groups. It had access to confirmed combine formals and pre-draft meetings with 2026 NFL Draft prospects, along with historical context on their importance.

I also uploaded the Chiefs’ stats from last season so the AI could quantify areas that needed improvement relative to NFL averages. The final piece of the puzzle was to upload the Chiefs’ 90-man offseason roster and team needs.

To execute the mock draft, I used the A to Z Sports NFL Mock Draft Simulator. I provided the AI with the list of the 10 best available players at a given pick. I made my picks before the AI, but I didn’t tell it who I had chosen. The AI was prompted to use all available data to make a decision for each draft pick. With all that in mind, here’s a look at how the mock draft competition turned out.

Final Kansas City 2026 NFL Mock Draft

Pick No. 9

Top available: Mansoor Delane, Caleb Downs, Jordyn Tyson, Spencer Fano, Makai Lemon, Monroe Freeling, Jermod McCoy, Kenyon Sadiq, Ola Ioane, and Keldric Faulk.

Advertisement

My pick: Arizona State WR Jordyn Tyson

Solving for the Chiefs’ need for “the guy” on offense in the future just feels like the right move for this draft class. Travis Kelce can’t play forever. Add Tyson and get back to scoring 30+ per game.

What AI Brett Veach did: Auburn DE Keldric Faulk

Edge rusher was the No. 1 need that I provided to the AI. At 6-foot-6 and 275 pounds with 34-inch arms, Faulk meets virtually every Chiefs threshold from a physical standpoint. It’s not an exciting pick for fans, but even a robot can see the upside here.


Pick No. 29

Top available: Kadyn Proctor, Akheem Mesidor, Caleb Banks, Cash Howell, T.J. Parker, CJ Allen, Denzel Boston, Chris Johnson, R Mason Thomas, and Colton Hood.

Advertisement

My pick: Tennessee CB Colton Hood

I’m becoming increasingly comfortable with the idea of taking a cornerback early. The old NFL adage goes that you can never have too many cornerbacks, and the Chiefs need bodies there. Not just for 2026, but also for the long term. Hood gives you a physical man coverage corner who can play outside, but probably crosstrains inside, too.

What AI Brett Veach did: Alabama OT Kadyn Proctor

Offensive tackle wasn’t rated as highly on the AI’s needs list. However, the Chiefs did have a top-30 visit with Proctor. I think it probably took note of Brett Veach’s comments about offensive tackle drying up by pick No. 35. He also hits some athleticism thresholds, despite missing on one key measurable (arm length).


Pick No. 40

Top available: Caleb Banks, Chris Johnson, R Mason Thomas, Denzel Boston, Chris Bell, Zion Young, Christen Miller, Chris Brazzell, D’Angelo Ponds, and Gabe Jacas.

Advertisement

My pick: Florida DT Caleb Banks

There are obviously some questions regarding the nagging foot injury. Plus, there’s still some development and pad-level issues to work out. I just think the 6-foot-6, 310-pound defender would really thrive by learning from Chris Jones.

What AI Brett Veach did: Florida DT Caleb Banks

What a copycat. Based on the information I gave the AI, this doesn’t surprise me. Banks had the medical top-30 visit with Kansas City. Veach, of course, mentioned needing two more defensive linemen in this class during his pre-draft presser. This just makes me feel even more strongly that this is a no-brainer pick if he’s available at pick No. 40.


Pick No. 74

Top available: Ted Hurst, Davison Igbinosun, Dom Orange, Antonio Williams, Jonah Coleman, Genesis Smith, Caleb Tiernan, Dani Dennis-Sutton, Will Lee III, and Keionte Scott.

Advertisement

My pick: Penn State DE Dani Dennis-Sutton

A member of the 2026 All-Juice Team, Dennis-Sutton feels like he was built in a lab solely for Steve Spagnuolo. He hits all of the physical thresholds, but also is quietly one of the more productive players at the position.

What AI Brett Veach did: Georgia State WR Ted Hurst

I think this might have been a “best player available” pick for the AI. Hurst took a pre-draft visit with the Chiefs, and wide receiver is pretty high on the needs list. It makes sense why the AI Brett Veach would value him here.


Pick No. 109

Top available: Brian Parker, Nick Singleton, Isaiah World, Oscar Delp, Dontay Corleone, Bud Clark, Kaleb Proctor, Harold Perkins, Emmett Johnson, and Charles Demmings.

Advertisement

My pick: TCU S Bud Clark

A versatile safety prospect for the Chiefs. Clark has ball skills for days, with four consecutive college football seasons with 3 or more interceptions. At 6-foot-1 and 188 pounds, he’s also a physical presence in run support. He fits the Spags mold.

What AI Brett Veach did: Stephen F. Austin CB Charles Demmings

Cornerback also ranked highly on the needs list, so I can see how the AI prioritized this position group at this pick. Veach also has a history of drafting FCS talent, including Fayetteville State CB Joshua Williams and Western Illinois DT Khalen Saunders. Demmings fits the mold for what K.C. likes at the cornerback spot in terms of physicality and athleticism.


Pick No. 148

Top available: Sam Roush, Kevin Coleman, Jalon Kilgore, Billy Schrauth, Kaleb Elarms-Orr, Ephesians Prysock, Justin Jefferson, Zane Durant, Logan Taylor, and Jeff Caldwell.

Advertisement

My pick: Stanford TE Sam Roush

I’m a big Roush fan. He’s already one of the better blocking tight ends in the class, but I also think there’s big upside as a pass-catcher. He has a 6-foot-6 and 267-pound frame. Plus, he’s a legacy player in Kansas City.

What AI Brett Veach did: South Carolina DB Jalon Kilgore

Nickel/safety versatility probably appealed to the AI here. There’s also really good ball production with eight career interceptions and 21 passes broken up. I think he’s rather role-limited in the NFL, but the AI could’ve done a whole lot worse at pick No. 148.


Pick No. 169

Top available: Landon Robinson, Josh Cameron, Caden Curry, Taureen York, Demon Claiborne, Domani Jackson, Eli Raridon, Cade Klubnik, J.C. Davis, and Keagen Trost.

Advertisement

My pick: Illinois OT J.C. Davis

I hadn’t taken an offensive tackle yet, so this felt right. This one is a bit of a homer pick as Davis played for my UNM Lobos before transferring to play for my Fighting Illini. If the Chiefs wait on offensive tackle, he’s the one I’d want them to target.

What AI Brett Veach did: Navy DT Landon Robinson

Doubling up on the pass-rushing interior defensive linemen. I see you, Brett Veach AI. Robinson is undersized, but his athleticism and production are absolutely worth taking a chance on. Being the top-ranked player on the list I gave to the AI probably played a part in this decision.


Pick No. 176

Top available: Jeremiah Wright, Ar’Maj Reed-Adams, Mikail Kamara, Marlin Klein, Adam Randall, Trey Moore, Jakobe Thomas, Nick Barrett, Kaelon Black, and Febechi Nwaiwu.

Advertisement

My pick: Michigan LB Jimmy Rolder

Call it a reach on my part, as Rolder is 201 on the A to Z Sports big board. Only a one-year starter. Instinctive with impressive closing speed at 6-foot-2 and 238 pounds. He’s someone who could slot in as a SAM linebacker in 2026, but potentially develop into the green-dot-wearer down the line.

What AI Brett Veach did: Indiana RB Kaelon Black

I noted three things the Chiefs still needed at running back in team needs for the AI: Pass protection, short-yardage, and return specialists. Black (5-foot-10, 210 pounds) can handle the first two, at the very least. The one thing I found interesting here is that running back was very low on my AI’s needs list.


Pick No. 210

Top available: Tyren Montgomery, John Michael Gyllenborg, Robert Spears-Jennings, Skyler Gill-Howard, Diego Pounds, Carver Willis, Caleb Douglas, Eli Heidenreich, Red Murdock, and George Gumbs Jr.

Advertisement

My pick: Florida EDGE George Gumbs Jr.

Gumbs felt like that developmental speed-rusher prototype that the Chiefs want, but haven’t really hit on. He’s long (6-foot-6 with 34-inch arms), springy, super-athletic, and the flash plays look really good. It’s just all about further development and consistency.

What AI Brett Veach did: Buffalo LB Khalil “Red” Murdock

The AI got a little sassy with me and spat out Red’s government name. I feel like Brett Veach’s recent comments about the linebacker position stuck with the AI here. I also feel like it valued Murdock’s production (364 tackles and 17 forced fumbles in his career).


Final verdict

Charles Goldman’s Final 2026 NFL Mock Draft:

Advertisement
  • 9: Arizona State WR Jordyn Tyson
  • 29: Tennessee CB Colton Hood
  • 40: Florida DT Caleb Banks
  • 74: Penn State EDGE Dani Dennis-Sutton
  • 109: TCU S Bud Clark
  • 148: Stanford TE Sam Roush
  • 169: Illinois OT J.C. Davis
  • 176: Michigan LB Jimmy Rolder
  • 210: Florida EDGE George Gumbs Jr.

AI Brett Veach’s Final 2026 NFL Mock Draft:

  • 9: Auburn DE Keldric Faulk
  • 29: Alabama OT Kadyn Proctor
  • 40: Florida DT Caleb Banks
  • 74: Georgia State WR George Hurst
  • 109: SFA CB Charles Demmings
  • 148: South Carolina DB Jalon Kilgore
  • 169: Navy DT Landon Robinson
  • 176: Indiana RB Kaelon Black
  • 210: Buffalo LB Red Murdock

Overall, I was surprised by how well the AI drafted. My draft feels a bit more top-heavy with the instant-impact contributors, but I think the AI might’ve actually done a better job on Day 3. That felt especially Brett Veach-like, given his history and penchant for finding late-round steals.

If I do this again next year, I think I’ll feed the AI some of our draft rankings at A to Z Sports to give it better context. It had access to prospect data, but not any specific set of rankings. That’s probably the one area this experiment failed. The only context it had for “best” was the order of the 10 players I gave it to choose from at each pick. If I had the ability to “reach” as I did at 176, the AI should be able to.



Source link

Advertisement
Continue Reading
Advertisement

Trending