Thanks - this should be fixed now (in the beta version), please check & advise.

Thanks hauteboy^ Now loaded into place.

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.

0.95012 is in the beta area
 

Beta version

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.

{sorry - read the thread in the wrong order - moved to discussion in other thread}

This restriction is too strict. AA will allow a transit of more than one stop. Likewise, a transit involving more than one stop in Asia is equally possible.

If the airlines consider it ok, why should we insist it is not?

Per the other thread ( :( ), 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.

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:

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

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.

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.

Guam is coming up with continent of SWP in the validator. According to IATA, Guam is in Asia.

Thanks. I'm not sure what is wrong. AFAICT GUM is served by OW only from NRT & KIX. When I use the official ow planner for something like LHR-NRT-GUM-NRT-LAX-LHR, it gives me a Region (Asia) has been re-entered warning for GUM-NRT. Both it and MileageMonkey are OK for a route such as LHR-NRT-GUM,SYD-LAX-LHR. The official OW planner is OK with GUM,SYD but disallows GUM,NRT due to not being in the same region.

My guess (subject to being advised otherwise :)) is that OW treats GUM as being in SWP, regardless of where IATA thinks it is :)

Dang - it is north of the equator! Has anyone tried or managed to include GUM on a xONEx?

If it really is SWP then that forces a surface segment (like PPT) :(

Is it possible for the validator to allow for purchased extra segments?

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 :td:

A thread about this change is here