Originally Posted by
Qwkynuf
Thanks, I hope my comments didn't come across as critical, I was just sharing what looked like anomalies on my first try. The lounge thing is tricky because my first reaction would be that you should consider connections too - but then you create a whole bunch of complexity. Maybe, if you are already considering connections to be one arrival + one departure, you could just have an "or" construct for "club exists at departure airport *or* club exists at arrival airport"?
In the case of this trip the output was confusing because there are clubs at both PDX and ATL. Strictly speaking, I could have entered the club at PDX before departure, at ATL on my outbound connection, at ATL on my return connection, and at PDX on arrival.
I think it just illustrates the actual complexity of things when we as user say "Well, Delta should just do such and such". Sure, it's easy to solve this problem, but you have to consider all of the other problems that the fix is likely to create.
Your comments came across as well-intentioned, constructive criticism, which is what I posted this here for.
Arrivals lounges without an onward segment were just one of the things I thought was too niche and complex for the first version – my assumption was that if you're looking for a Sky Club as an arrivals lounge you would know the policy. I also don't have a good way yet of presenting the fact that the lounge was in the arrival airport, and I didn't want folks looking for a lounge in GPT that doesn't exist. If folks on FT think the information is important enough I may add it as another column though.
I will note that the Sky Club access calculation does take into account whether you can use an "arrivals lounge" from the previous segment, e.g. with an Amex Platinum
you don't have Sky Club access when flying BOS-KL-AMS but
you do if you fly DEN-DL-BOS-KL-AMS.