This should interest jebr, norfolkwesternhenry, and others from the Minneapolis area. I tried to play around with the new Amtrak website and typed in Minneapolis. Instead of MSP, MSL comes up as the default option. You have to manually type in MSP to get it to work.
Yeah, I remember discovering this back on launch (though it was buried way back and probably got lost in the shuffle to some extent):
The web site does not recognize Saint Paul as an origin.
It will, however, recognize "St. Paul" (or "Minneapolis", but only for the airport Thruway stop, so that's not entirely helpful.) St. Paul's one of those tricky towns that I've seen other websites (mainly bus services) glitch out with as well if it's not typed in the way they're expecting, so it doesn't surprise me that Amtrak's website suffers from similar issues. Minneapolis only pulling up the airport stop, however, is bad design (the entry still starts "St. Paul-Minneapolis" just like the train station, so I'm not sure what the difference is.)
But yeah, while I haven't notified Amtrak of it yet, I'm surprised they haven't noticed it and fixed it on their end. I usually just type "MSP" somewhat instinctually anyways (even on airport websites) so I haven't really noticed it other than that time, as MSP does still pull up St. Paul Union Depot.
The only thing I can forgive Amtrak for slightly is being particular on the spelling of St. Paul. I'm frustrated, though, that Amtrak hasn't fixed it to at least put Union Depot as the default option for both St. Paul and Minneapolis. I'm honestly not even sure why they list MSP airport as an option. The connection isn't even built properly for anyone going west of Saint Paul (it requires going down to La Crosse and then back up to the airport on 8/28, which is a nice little 6 hour detour, and the connection won't even build for 7/27.) East of St. Paul isn't much better, either - the website won't build the connection from the airport for anything east of St. Paul. The connection from 7/27 for points east of La Crosse is also no faster than simply going up to St. Paul and then taking the local 54 bus to the airport, and by that point it's so late that you're likely looking at an overnight anyways.
I'm not a fan of eliminating options, but in this case the "option" is so sparse and doesn't really build properly for anyone to be able to make a round trip that it's essentially worthless. Given that it seems to be throwing the website into a tizzy (not to mention that the service from Union Depot is easily replaced by a frequent local bus) I say remove the MSL stop on that Thruway. Its main purpose is to connect to Rochester anyways, so just let it do that and stop trying to add a pretty much useless option with it as well.