RTQ Validator URL not working - anyone else able to use it?
#31
Join Date: Jun 2004
Location: Madrid, Spain & Santiago, Chile
Programs: AA EXP
Posts: 3,181
Originally Posted by SLF
I'm not doubting you, but I don't see that in the OW timetable
Edited to add: the latest version, dated 13-JUL-06, now includes this flight.
Last edited by Viajero; Jul 19, 2006 at 5:25 am
#32
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Originally Posted by Viajero
The OW timetable is wrong.
#33
Join Date: Jul 2005
Location: YVR occasionally
Programs: OW Emerald (AA-EXP, BA-Gold)
Posts: 261
Originally Posted by SLF
I'm not doubting you, but I don't see that in the OW timetable
#34
FlyerTalk Evangelist
Join Date: Nov 2004
Location: Melbourne
Programs: ►QFWP/LTG►VA WP►HyattExpl.►HiltonGold►ALL Silver
Posts: 21,995
A fellow OZ FTer has pointed out the cached version is not correctly processing the setting for the 'earn' radio button element when "Qantas status credits (post May 25,2005)" is select. It seems to be giving results for pre May 25 irrespective of this setting.
#35
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Originally Posted by serfty
A fellow OZ FTer has pointed out the cached version is not correctly processing the setting for the 'earn' radio button element when "Qantas status credits (post May 25,2005)" is select. It seems to be giving results for pre May 25 irrespective of this setting.
#36
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Originally Posted by serfty
A fellow OZ FTer has pointed out the cached version is not correctly processing the setting for the 'earn' radio button element when "Qantas status credits (post May 25,2005)" is select. It seems to be giving results for pre May 25 irrespective of this setting.
I've also hidden the list of changes I added in the yellow box at the top - to see these, just choose the "changes" link which will toggle their visibility.
#37
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
GIB is now recognized as a European location for the purposes of counting towards allowed EU sectors on a OWE. Previously it was shown as "intercontinental" - this could have led to the incorrect belief that something like GIB-LHR-DXB-LHR-HEL-LHR-JFK-HKG-LHR-GIB was valid. Force a reload (shift-refresh) if you see unexpected results to ensure your browser isn't working from old data.
Note also that this thread is referenced from the end of the second post in the sticky in this forum (thanks SanDiego1K ) - so it should always be easy to find.
Note also that this thread is referenced from the end of the second post in the sticky in this forum (thanks SanDiego1K ) - so it should always be easy to find.
#38
Join Date: Mar 2005
Location: London
Programs: BA Silver
Posts: 540
Originally Posted by SLF
GIB is now recognized as a European location for the purposes of counting towards allowed EU sectors on a OWE. Previously it was shown as "intercontinental" - this could have led to the incorrect belief that something like GIB-LHR-DXB-LHR-HEL-LHR-JFK-HKG-LHR-GIB was valid. Force a reload (shift-refresh) if you see unexpected results to ensure your browser isn't working from old data.
Note also that this thread is referenced from the end of the second post in the sticky in this forum (thanks SanDiego1K ) - so it should always be easy to find.
Note also that this thread is referenced from the end of the second post in the sticky in this forum (thanks SanDiego1K ) - so it should always be easy to find.
Cheers SLF!
#39
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Originally Posted by sdorling
KEF could do with the same treatment as it too is showing up as intercontinental.
#40
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
The 0.95001 version will accept OWE routes with the following:
Thus (from another thread ), the following route will now be processed correctly:
ARN-MAD-GUA-MIA-SXM-JFK//DCA-SLC//SFO-JFK-GIG-SCL-xLAX-HKG-MNL-HKG-SIN-HKG-AMS-MAD-ARN
- containing spaces (these are discarded)
- using the "//" notation for a surface sector ("," is already supported)
- using -xAAA (transit) or -oAAA (stopover) to explicitly indicate transit/stopover in AAA (note the number of stopovers is not checked, this could be a future enhancement)
Thus (from another thread ), the following route will now be processed correctly:
ARN-MAD-GUA-MIA-SXM-JFK//DCA-SLC//SFO-JFK-GIG-SCL-xLAX-HKG-MNL-HKG-SIN-HKG-AMS-MAD-ARN
Last edited by SLF; Aug 17, 2006 at 1:50 am Reason: clarified meaning of "x" & "o"
#41
Join Date: Jun 2003
Location: NYC
Programs: AA Plat/2MM, Marriott Titanium
Posts: 277
SLF,
First of all, thank you for maintaining this tool. I have a question about the most recent change:
This implies that "x" is for stopover and "o" is for transit. However, you then use the following example:
ARN-MAD-GUA-MIA-SXM-JFK//DCA-SLC//SFO-JFK-GIG-SCL-xLAX-HKG-MNL-HKG-SIN-HKG-AMS-MAD-ARN
where it seems that "xLAX" indicates a transit. So, which way is it? I would suggest that "x" should be for transit, and "o" should be for stopover since I believe that is the way it shows up on airline tickets (although I don't have any handy to verify this).
FWIW, I've been lurking on this forum for quite a while, and people seem to use "x" sometimes to mean transit and sometimes to mean stopover. Perhaps a standard way of specifying itineraries could be documented and added to the "sticky" so that (hopefully) people will write itineraries in a more consistent manner.
First of all, thank you for maintaining this tool. I have a question about the most recent change:
Originally Posted by SLF
The 0.95001 version will accept OWE routes with the following:
...
using -xAAA or -oXXX to indicate stopover/transit (note the number of stopovers is not checked, this could be a future enhancement)
...
using -xAAA or -oXXX to indicate stopover/transit (note the number of stopovers is not checked, this could be a future enhancement)
ARN-MAD-GUA-MIA-SXM-JFK//DCA-SLC//SFO-JFK-GIG-SCL-xLAX-HKG-MNL-HKG-SIN-HKG-AMS-MAD-ARN
where it seems that "xLAX" indicates a transit. So, which way is it? I would suggest that "x" should be for transit, and "o" should be for stopover since I believe that is the way it shows up on airline tickets (although I don't have any handy to verify this).
FWIW, I've been lurking on this forum for quite a while, and people seem to use "x" sometimes to mean transit and sometimes to mean stopover. Perhaps a standard way of specifying itineraries could be documented and added to the "sticky" so that (hopefully) people will write itineraries in a more consistent manner.
#42
Suspended
Join Date: Jun 2002
Location: Hong Kong
Programs: None any more
Posts: 11,017
monster,
You are correct: "x" is transit, "o" is stopover.
You are correct: "x" is transit, "o" is stopover.
#43
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Originally Posted by monster
So, which way is it? I would suggest that "x" should be for transit, and "o" should be for stopover since I believe that is the way it shows up on airline tickets (although I don't have any handy to verify this).
#44
Join Date: Dec 2005
Programs: QF Gold, SQ, AA, HA
Posts: 126
I've noticed a bug in the most recent version concerning the calculation of QF SCs. Flights in the '4801-5800' mileage bracket (eg. BKK-HEL) show up as earning 45 SCs in Y when in fact they earn 35. The values in J and F appear to be correct, however.
#45
Join Date: Sep 2004
Location: Europe
Programs: Various
Posts: 3,087
Originally Posted by mrboh
I've noticed a bug in the most recent version concerning the calculation of QF SCs. Flights in the '4801-5800' mileage bracket (eg. BKK-HEL) show up as earning 45 SCs in Y when in fact they earn 35. The values in J and F appear to be correct, however.