Credit again to hauteboy; it was an unfinished project which I've added to. Alas this is really only an approximation - it is based on the aircraft type, and is just intended as a guide. I can override it for specific sectors and have done for the ones you have highlighted (thanks!), plus a few others.

Filtering added to the OWE planner.

Thanks - something was wrong ... the coordinates for SNA placed it at DNV. I've moved SNA back to California :) (in the beta version)

[QUOTE=WearyBizTrvlr;7517619]
LHR to CAI, TLV, EWR(?), PHL, MCT, GCM,[QUOTE]

EWR has F on all 777 operated services. GCM on the other hand is all 767 and has Y, W & J only.

Corrected, thanks.

Could you check the coordinates for Manila, Philippines? I get 3331 miles from the validator and 3895 from the QF website.

It's a great tool - keep up the good work!

Actually all Lan Argentina flights are missing not just IGR.. my old PDF scanner used to ignore XL/4M flights since they weren't valid. I'll update this.

The F/J/Y indicator is trickier; my scanner attempts to determine which classes are available depending on aircraft type. Eg. with BA and QF which operate the same aircraft but F/J depends on route.

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

0.95013 is in beta
 

Yes, sort of :) There is an "ignore errors" check-box now which will permit continued processing despite any errors encountered.

Beta version available for testing here. Please report any issues back to this thread.

• Added valid/invalid status indicator next for OWE validator section to allow quick determination of status
• Fixed "link to this itinerary to preserve entered "-x", "-o" values etc.
  Example
• Streamlined the layout a little, incl. changing "Submit" to "Go!" and "Help" to "?" on buttons
• Added more information to the help dialogs
• Added an "Ignore errors" checkbox to the OWE planner to allow further validation to continue even if the validator suspects an error (this could be most useful for itins with additional purchased sectors, and/or if the validator is ever wrong on something it will at least allow results to be obtained
• Added a "link to this itinerary" feature to the point-point mappings
  Example :)
• Fix the point-point calculator, which got accidentally broken in 0.95011 ... and no-one noticed!
• Add a section with some useful links. Other suggestions welcome!

Thanks. That's now included too in the beta :(

I've added a check-box to "ignore surface sectors", which should be used on tickets issued pre-July 2007. This itinerary uses 5 or 7 coupons, depending on which rules are applied.

I wonder if now that we're forced to use a coupon for a surface sector, whether we can claim f/f miles? :)

Thanks
 

Thanks for super quick fix. Their is some debate now if open jaw is allowable on *ONE* due to the "including land segments" rule

Will we ever get past beta ;) Rules changing too much

Interesting comment on post 26 of the other thread. Open to interpretation ???

The most current version of MileageMonkey can be found here.
Older & beta versions can be found here.

Thanks for the tool, but I'm a bit stumped on the calcs used.

syd-lax-las-atl-lga-jfk-lhr-bkk-sin-syd comes up with the correct sector status credits, but the total, 1260, is out by 170 SCs

Am I doing something wrong here?

Using the link-to feature, this shows as 1260 - however, it is also flagging services it doesn't believe exists:
Note that it's working on the assumption that you're right & it's wrong (i.e. that the services do exist), so it's proceeding to count them as valid sectors.

Perhaps you wanted to explicitly mark them as surface sectors, like this: http://slfft.allhyper.com/0.95/award...HR-BKK-SIN-SYD

Does that give you the answer you're expecting? If not, can you help me understand the problem better?

Tried MEL-AKL-SCL-GIG-GRU-LIM-EZE-LHR-DXB-LHR-KEF-LHR-SIN-NRT-DEL-NRT-HKG-PER-MEL-CNS-MEL
in v0.95012 get
linkbut lists all 20 segments

In http://slfft.allhyper.com/beta/award.htm
linkeven after ticking "Ignore errors (for expert users!)"
Seems to stall after 1st error

LHR-KEF-LHR is in BA's shedule, but not sure if its seasonable or to be dropped along with the other BA routes

BA flies to Reykjavik from LGW, not LHR. That's probably the problem.

You're both right. MM shouldn't have stopped after that error with the expert mode selected. And BA fly ex-LGW to KEF. If you change LHR in your itin to LON, MM is happy...the $64000 question is can you get it ticketed like that without needing coupons for LGW-LHR & v.v.

Edit: the reported problem should be fixed now in the beta version

I've moved 0.95013 out of beta to the main page. If you need an older version, choose it from here. Any bookmarks you have which reference the "beta" version should automatically redirect to the main version. If you don't see 0.95013, try forcing your browser to refresh fully (shift-refresh on Firefox).

SLF, you are doing a lot of good, timely, work to keep this tool up to date and useful. I just wanted to say thank you.

I was thinking of posting a similar message today but got sidetracked.

SLF I would like to add my thanks too for all the effort you have gone to in not only resurrecting this tool, but making some great improvements and keeping it up to date. :-:

Thanks SLF from me too ^^^

Add another to the chorus of thanks. ^

I am trying to validate the following:

SYD-HKG-SIN-BKK,SGN-NRT-SVO-BUD,SOF-LON-CAS,RAK-BCN-BUE-LIM-LPB-SCL-SYD

And I get an error on:

12: RAK-BCN: 4th of 4 (Europe)
Rule violated!!!! [RAK-BCN] Max 1 segment(s): Ghana/Nigeria/Kenya/Uganda/Tanzania transit (second EUR entry?)


Is this actually a valid itinerary? The oneworld tool doesnt have a problem with it and I can't see a problem in the rules.

Hi Rhys1, welcome to FT.

<never mind>

Welcome to Flyer Talk Rhys1 :)

Morocco is treated as part of Europe according to xONEx rules, and so allowed on that basis. Perhaps the surface segment (within Morocco) is confusing the validator?

Thanks :) Been a long time reader.

I have tried without the surface sector and still get the error.

Thanks - that should be sorted out now. Morocco was being treated as being in Europe, however it was also being treated as being in Africa.

Another welcome to FT :) And thanks for noticing that bug :)