New oneworld itinerary validator
Apr 4, 2007, 12:19 am
#46
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Apr 4, 2007, 10:26 am
#47
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
I've moved the beta version into the main folder now. If for some reason you need 0.95010, it is accessible through the "other versions" link.
Apr 13, 2007, 5:17 pm
#48
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
0.95012 is in the beta area
Beta version
Due to a challenge ... there is now a new beta version. Comments / testing welcome
Due to a challenge ... there is now a new beta version. Comments / testing welcome
- Added rule; if two entries to Asia or N.America occur, check that one is a transit (no intra-continent sectors)
- When using "link to" function; perform "submit" automatically so that map & validation is done at time of page load
- For point-point checks, permit more flexible entry (like OWE section) - i.e. whitespace, "//", -xAAA etc.
Apr 14, 2007, 2:13 pm
#50
Join Date: Jun 2004
Location: Madrid, Spain & Santiago, Chile
Programs: AA EXP
Posts: 3,181
If the airlines consider it ok, why should we insist it is not?
Apr 14, 2007, 2:24 pm
#51
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
), I changed this to a warning only...so now it flags it as a possible problem, but continues validating and will produce a "valid" itinerary. I'm open to removing the check entirely, if that is the consensus...thanks for the feedback.
Apr 15, 2007, 10:30 pm
#52
FlyerTalk Evangelist
Join Date: Nov 2004
Location: Melbourne
Programs: ►QFWP/LTG►VA WP►HyattExpl.►HiltonGold►ALL Silver
Posts: 21,994
Another issue; mel-akl-lax-jfk-lhr-hkg-mel-per-mel validates as OK.
Since AUG '05 MEL-PER can now only be done once - it is now included in the Oz Transcon limitation:
i.e. PER-MEL/SYD/BNE-CNS.
Specifically:
Since AUG '05 MEL-PER can now only be done once - it is now included in the Oz Transcon limitation:
i.e. PER-MEL/SYD/BNE-CNS.
Specifically:
Code:
J/WITHIN AUSTRALIA ONLY ONE NONSTOP/SINGLE PLANE SERVICE FLIGHT IS PERMITTED BETWEEN THE FOLLOWING POINTS - BNE/CNS/SYD/MEL - PER MEL/SYD - DRW MEL/SYD - BME EXCEPTION - 1. NO RESTRICTION BETWEEN SYD/MEL-PER FOR PASSENGERS ORIGINATING IN PER WHEN IN CONJUNCTION WITH TRAVEL TO/FROM JNB/BOM/SHA/PEK. 2. NO RESTRICTION BETWEEN SYD/MEL-PER FOR PASSENGERS ORIGINATING IN NEW ZEALAND WHEN IN CONJUNCTION WITH TRAVEL TO/FROM JNB.
Apr 16, 2007, 11:43 am
#53
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Thanks - that was originally fixed (along with the BME-SYD/MEL and DRW-SYD/MEL restrictions) in 0.95008, but got lost in the major change to 0.95009.
Now working (or not
) again: http://slfft.allhyper.com/beta/award...KG-MEL-PER-MEL
Also, if it doesn't have a flight in it's database, instead of terminating the check it will now just highlight that segment as a problem, and carry on (so it's assuming it's database is wrong). Example: http://slfft.allhyper.com/beta/award...AX-HKG-LHR-MIA
Now working (or not
) again: http://slfft.allhyper.com/beta/award...KG-MEL-PER-MELAlso, if it doesn't have a flight in it's database, instead of terminating the check it will now just highlight that segment as a problem, and carry on (so it's assuming it's database is wrong). Example: http://slfft.allhyper.com/beta/award...AX-HKG-LHR-MIA
Apr 16, 2007, 11:37 pm
#54
Join Date: Oct 2006
Location: DTW
Programs: AA EXP, DL FO
Posts: 1,719
Whenever the validator returns a warning (such as using MIA-ANC) the nifty chart at the bottom of the page with a segment/distance/points/class summary doesn't display.
Last edited by vxmike; Apr 16, 2007 at 11:56 pm
Apr 17, 2007, 1:56 am
#55
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Fixed, thanks. I also added MIA-ANC. Be sure to force a reload of everything (shift-reload on Firefox) to ensure you get the new versions. Changes are still in the beta version only.
Jun 11, 2007, 12:30 am
#57
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Guam is coming up with continent of SWP in the validator. According to IATA, Guam is in Asia.
My guess (subject to being advised otherwise
) is that OW treats GUM as being in SWP, regardless of where IATA thinks it is
Jun 11, 2007, 2:32 pm
#58
Moderator, Hilton Honors
Join Date: Nov 2003
Location: on a short leash
Programs: some
Posts: 71,422
If it really is SWP then that forces a surface segment (like PPT)
Jun 30, 2007, 4:18 am
#60
FlyerTalk Evangelist
Join Date: Apr 2001
Location: MEL CHC
Posts: 21,024
The rules have changed
The rules have changed (for the worse). The Explorer rule sheet (file 3015owrulev38_pm mark ups.pdf) on the OneWorld site was updated 30 Jun 06.
From 3015owrulev38 “A minimum of 3 and a maximum of 20 segments, including surface segments, are permitted for the entire journey.”
The including surface segments is new
A thread about this change is here
From 3015owrulev38 “A minimum of 3 and a maximum of 20 segments, including surface segments, are permitted for the entire journey.”
The including surface segments is new
A thread about this change is here
Last edited by Mwenenzi; Jun 30, 2007 at 7:57 am Reason: thread link added