Last edit by: hillrider
Here are some more hidden features of the ITA software.
The extensions to the itasoftware routing language are accessed by postpending commands after a '/'. There's a wide set of commands available, but there's no description of them available on the ITA web site. Unfortunately, each command applies only to one part of the trip, so they must usually be entered in each box.
EXCLUDE SPECIFIC AIRLINES
Command is "-airlines XX ..."
Ex: prohibit jetBlue or Delta
from: BOS ::/ -airlines B6 DL
to: LAX ::/ -airlines B6 DL
LIMIT TO SPECIFIC AIRLINES
Command is "airlines XX ..."
Ex: consider only jetBlue or Delta
from: BOS ::/ airlines B6 DL
to: LAX ::/ airlines B6 DL
LIMIT TO A SINGLE ALLIANCE
Command is "alliance star-alliance|oneworld|skyteam"
Ex: oneworld carriers only
from: BOS ::/ alliance oneworld
to: LAX ::/ alliance oneworld
EXCLUDE CODESHARES
Command is "-codeshare"
Ex: prohibit jetBlue or Delta
from: BOS ::/ -codeshare
to: LAX ::/ -codeshare
LIMIT DURATION OF ITINERARY, IN MINUTES
Command is "maxdur XXX"
Ex: no more than 5hrs for each part of trip
from: BOS ::/ maxdur 300
to: LAX ::/ maxdur 300
EXCLUDE OVERNIGHT STOPS, AIRPORT CHANGES, REDEYES, PROPELLER PLANES, TRAINS, HELICOPTERS, ANY KIND OF SURFACE TRAVEL
Commands are "-overnight", "-change", "-redeye", "-prop", "-train", "-helicopter", "-surface"
Ex: no overnight stops, no airport changes, no redeyes, no propeller planes
from: BOS ::/ -overnight, -change, -redeye, -prop
to: LAX ::/ -overnight, -change, -redeye, -prop
SET MINIMUM OR MAXIMUM TIME FOR CONNECTIONS, IN MINUTES
Commands are "minconnect XX", "maxconnect XX"
Ex: no less than one hour, no more than two hour connections
from: BOS ::/ minconnect 60, maxconnect 120
to: LAX ::/ minconnect 60, maxconnect 120
EXTRA CONNECTION TIME
Command is "padconnect XX"
Ex: require at least 20 minutes more than airline specified minimum connection time
from: BOS ::/ padconnect 20
to: LAX ::/ padconnect 20
PUTTING LOTS OF THINGS TOGETHER
Separate with commas.
Ex:
from: BOS :: UA UA / f bc=l|bc=y, -redeye, -prop
to: LAX :: UA+ / f ua.bos+lax.yup, padconnect 20, -overnight
The extensions to the itasoftware routing language are accessed by postpending commands after a '/'. There's a wide set of commands available, but there's no description of them available on the ITA web site. Unfortunately, each command applies only to one part of the trip, so they must usually be entered in each box.
EXCLUDE SPECIFIC AIRLINES
Command is "-airlines XX ..."
Ex: prohibit jetBlue or Delta
from: BOS ::/ -airlines B6 DL
to: LAX ::/ -airlines B6 DL
LIMIT TO SPECIFIC AIRLINES
Command is "airlines XX ..."
Ex: consider only jetBlue or Delta
from: BOS ::/ airlines B6 DL
to: LAX ::/ airlines B6 DL
LIMIT TO A SINGLE ALLIANCE
Command is "alliance star-alliance|oneworld|skyteam"
Ex: oneworld carriers only
from: BOS ::/ alliance oneworld
to: LAX ::/ alliance oneworld
EXCLUDE CODESHARES
Command is "-codeshare"
Ex: prohibit jetBlue or Delta
from: BOS ::/ -codeshare
to: LAX ::/ -codeshare
LIMIT DURATION OF ITINERARY, IN MINUTES
Command is "maxdur XXX"
Ex: no more than 5hrs for each part of trip
from: BOS ::/ maxdur 300
to: LAX ::/ maxdur 300
EXCLUDE OVERNIGHT STOPS, AIRPORT CHANGES, REDEYES, PROPELLER PLANES, TRAINS, HELICOPTERS, ANY KIND OF SURFACE TRAVEL
Commands are "-overnight", "-change", "-redeye", "-prop", "-train", "-helicopter", "-surface"
Ex: no overnight stops, no airport changes, no redeyes, no propeller planes
from: BOS ::/ -overnight, -change, -redeye, -prop
to: LAX ::/ -overnight, -change, -redeye, -prop
SET MINIMUM OR MAXIMUM TIME FOR CONNECTIONS, IN MINUTES
Commands are "minconnect XX", "maxconnect XX"
Ex: no less than one hour, no more than two hour connections
from: BOS ::/ minconnect 60, maxconnect 120
to: LAX ::/ minconnect 60, maxconnect 120
EXTRA CONNECTION TIME
Command is "padconnect XX"
Ex: require at least 20 minutes more than airline specified minimum connection time
from: BOS ::/ padconnect 20
to: LAX ::/ padconnect 20
PUTTING LOTS OF THINGS TOGETHER
Separate with commas.
Ex:
from: BOS :: UA UA / f bc=l|bc=y, -redeye, -prop
to: LAX :: UA+ / f ua.bos+lax.yup, padconnect 20, -overnight
TIP: More hidden features of ITA
#46
Join Date: Mar 2009
Location: Kingdom of Saudi Arabia
Programs: UA-1k, 1mm, Marriott-LT Platinum, Hertz-Presidents Circle
Posts: 6,355
There is a way to search by fare bucket, and it was posted within the last month or so. I would say that would be the way.
#49
Join Date: May 2007
Location: ORD, DEL
Programs: AA (Plt Pro; 1.5 MM)
Posts: 6,185
However, from the first search one can figure out which airlines are including substantial YQ on your route and which ones are not. Then one can limit the later searches to one or the other group.
Last edited by aktchi; Mar 2, 2010 at 10:27 am
#50
Join Date: Mar 2010
Location: St. Louis
Programs: AA PLT, UA 1P
Posts: 17
No tight connections?
Is there an advanced switch I can provide to exclude all "tight connection" routings?
Also, I know that "-change" prevents routings with a change of airports between legs (so no red "EWR/JFK" in the Stops column). But how do I force ITA to use the same airport for the outbound and return legs of a round trip? When you use a semicolon-separated list of destinations (e.g. "AUS;MCI;MEM"), it does no good to fly into AUS and out of MEM...
Also, I know that "-change" prevents routings with a change of airports between legs (so no red "EWR/JFK" in the Stops column). But how do I force ITA to use the same airport for the outbound and return legs of a round trip? When you use a semicolon-separated list of destinations (e.g. "AUS;MCI;MEM"), it does no good to fly into AUS and out of MEM...
#51
Join Date: Mar 2009
Location: Kingdom of Saudi Arabia
Programs: UA-1k, 1mm, Marriott-LT Platinum, Hertz-Presidents Circle
Posts: 6,355
Is there an advanced switch I can provide to exclude all "tight connection" routings?
Also, I know that "-change" prevents routings with a change of airports between legs (so no red "EWR/JFK" in the Stops column). But how do I force ITA to use the same airport for the outbound and return legs of a round trip? When you use a semicolon-separated list of destinations (e.g. "AUS;MCI;MEM"), it does no good to fly into AUS and out of MEM...
Also, I know that "-change" prevents routings with a change of airports between legs (so no red "EWR/JFK" in the Stops column). But how do I force ITA to use the same airport for the outbound and return legs of a round trip? When you use a semicolon-separated list of destinations (e.g. "AUS;MCI;MEM"), it does no good to fly into AUS and out of MEM...
I believe you have the or airport within xxx amount of miles showing some number. Set that to zero and search again. It will only bring back your departure airport RT.
#52
Join Date: Sep 2005
Location: BRU
Programs: LH SEN, SN Gold, Eurostar Carte Blanche, BA, QF, AF
Posts: 6,856
Doesn't "padconnect" kind of result in what you want? My guess is that if the minimum connection time is, say, 30 minutes, you might get a tight connection warning for connections between 30 and 60 minutes. If you want to exclude the tight connections you would just use "padconnect 30" as it will increase MCT by 30 minutes.
Now you just need to experiment to find out up to how many minutes above MCT are called a tight connection.
Now you just need to experiment to find out up to how many minutes above MCT are called a tight connection.
#53
Join Date: Apr 2009
Location: 1 AU
Programs: Support the Tyrants Travel Club
Posts: 2,708
Is there an advanced switch I can provide to exclude all "tight connection" routings?
Also, I know that "-change" prevents routings with a change of airports between legs (so no red "EWR/JFK" in the Stops column). But how do I force ITA to use the same airport for the outbound and return legs of a round trip? When you use a semicolon-separated list of destinations (e.g. "AUS;MCI;MEM"), it does no good to fly into AUS and out of MEM...
Also, I know that "-change" prevents routings with a change of airports between legs (so no red "EWR/JFK" in the Stops column). But how do I force ITA to use the same airport for the outbound and return legs of a round trip? When you use a semicolon-separated list of destinations (e.g. "AUS;MCI;MEM"), it does no good to fly into AUS and out of MEM...
#54
Join Date: Mar 2010
Location: St. Louis
Programs: AA PLT, UA 1P
Posts: 17
Doesn't "padconnect" kind of result in what you want? My guess is that if the minimum connection time is, say, 30 minutes, you might get a tight connection warning for connections between 30 and 60 minutes. If you want to exclude the tight connections you would just use "padconnect 30" as it will increase MCT by 30 minutes.
Perfect! I hadn't thought to look under the "more options" link. Thanks!
#55
Join Date: May 2007
Location: ORD, DEL
Programs: AA (Plt Pro; 1.5 MM)
Posts: 6,185
from: ORD ::/ minconnect 60, maxconnect 180
to: LHR ::/ minconnect 60, maxconnect 180
This feature should be used sparingly and very conservatively. In the above example, would you really want to avoid a great connection at a great price just because it was 57 minutes or 184 minutes? Similarly, what is a tight connection time at one airport may well be comfortable at another. This is where auto-thinking by software does not work for me. I prefer to pretend to be far more flexible than I really am, and then select my flights manually.
Minconenct and maxconnect specify absolute times in minutes; padconnect specifies extra time over the airline recommended minimum. To specify at least 30 minutes more than the airline recommended minimum connection time -
from: SFO ::/ padconnect 30
to: JFK ::/ padconnect 30
Same precaution applies here: Be very conservative. You wouldn't want to miss a great flight that fell only a few minutes outside your criteria.
Uncheck the box that says "Allow Airport Changes".
Last edited by aktchi; Mar 22, 2010 at 1:03 pm
#57
Join Date: Apr 2010
Programs: SPG Gold
Posts: 142
Say if you'd like to specify a B fare class on the NYC-PEK segment.
Use the multi-city search option.
and type in NYC:: /f bc=b in the origin of the first segment
and type in PEK in the destination of the first segment
and leave PEK-BKK to the second segment and so forth
Use the multi-city search option.
and type in NYC:: /f bc=b in the origin of the first segment
and type in PEK in the destination of the first segment
and leave PEK-BKK to the second segment and so forth
#58
Join Date: Mar 2008
Posts: 439
Say if you'd like to specify a B fare class on the NYC-PEK segment.
Use the multi-city search option.
and type in NYC:: /f bc=b in the origin of the first segment
and type in PEK in the destination of the first segment
and leave PEK-BKK to the second segment and so forth
Use the multi-city search option.
and type in NYC:: /f bc=b in the origin of the first segment
and type in PEK in the destination of the first segment
and leave PEK-BKK to the second segment and so forth
#60
Join Date: Mar 2009
Location: Kingdom of Saudi Arabia
Programs: UA-1k, 1mm, Marriott-LT Platinum, Hertz-Presidents Circle
Posts: 6,355
fare restrictions prevent this many times. For example if you book your over water in W (and W is the lowest available) then it many times won't book anything lower than W for your domestic segments. It has to be in the fare restrictions somewhere and not really worth time to read and figure it out. A less time consuming way of doing it is calling and constructing it with an agent who will know if it is possible for your city routings.