Originally Posted by
zoombee
That's promising! May get new bugs as old issues are worked on but hopefully after a period of changes it'll settle and actually work 🤞 -- I was about to ask if someone with access to a GDS and was slightly technically might be interested in a brainstorm call to discuss what an itineray validator tool needs. I've been looking at using AI to write application specifications and then having AI produce the app so this might have been a fun and useful real world test case but not if someone is finally fixing the official tool.
[bit more context: the tool in [url=https://www.flyertalk.com/forum/oneworld/401874-new-oneworld-itinerary-validator.html]Oneworld Itinerary Validator Thread is long dead but I think I have the code somewhere (iirc I hosted it for a while) which would be a fair starting point. It would be nice to have a way to validate and/or price a route even if you can't then book. It could also make an agent more willing to provide cost effective booking services (the tool could kick out a validated available route which they require to service a request). Very much idle musing at this point but might have been worth a chat if we thought the official tool was near certain to remain borderline unuseable]
I've written ~200 lines of Python that can run some very basic checks on a route. It's extremely rudimentary and requires manual labelling of whether each flight is an intracontinental or an intercontinental flight, but I've found it useful for quickly checking that I've breached none of the limits on the number of segments, free flight segments within each continent, intercontinental departures/arrivals, stopovers, etc. It also tells me how many of each I have left. It can also generate links to the Great Circle Mapper and the xONEx Credit Calculator (for BA).
Here it is if anyone's interested in playing with it:
https://pastebin.com/nbuBPgBu
Could probably hook it up to a route/airport database and make it identify the type of each segment automatically.
As for pricing, I've got another script that takes a list of segments (origin-destination + marketing carrier + whether it's a stopover or not) and converts it into a request to the OW RTW backend API for pricing. It's useful for getting a rough estimate of YQ/YR and how that varies depending on the route and marketing carriers, and unlike the frontend you don't have to bother with actual dates or flight numbers and codeshares aren't an issue, but unfortunately it's still got some of the limitations present on the website (e.g. the first segment can't be marketed by QR and it seems to reject some valid routes). Not sure how useful that one is though... it'll probably require actual access to a GDS to make something better than the official tool.
ps: not really convinced AI would be capable of doing what you want properly.