Hi! Thanks for pointing out the problem. I just investigated Wintergreen and found out that my scripts were correctly inserting Wintergreen into the database, but then inserting Wintergreen, AB on top of it. (In other words, there's another resort somewhere named Wintergreen, and that resort's info was overwriting the valid data.) I corrected this. (I've had to do that with several other resorts that also don't have unique names - such as Hidden Valley.)
I also corrected the trail count at Wintergreen. The # of trails open and % open is provided by AccuWeather, but the total trails is provided by me, based on my resort profiles. Resorts have a tendency of increasing trail counts (even without cutting trees!), which I don't always catch, so some of my info might be out of date. I'll be going through all the resort profiles this summer to bring them completely up to date.
If you see anything wrong with other resorts, please let me know. Be sure to check the "last modified date" to make sure it's current - sometimes resorts aren't timely in reporting their conditions. But in the case of Wintergreen, it was a problem on my end (the best type, because I can fix those!)