Alternative to TripIt = TripWaffle

[tripwaffle]

This might have already been noted (forgive me if so), but some of the airline codes are incorrect. Or rather, the AI is strugging with codes that have been retired and reused.

Examples from my data:
DJ (former Virgin Blue) coming up as Air Dijbouti
3K (former Jetstar Asia) comes up as Fedex
TT (Former Tiger Air) comes up as Scott
CO (former Continental) coughing up as ???

The odd one out is TL which is the current code for Air North but is coming up as TMA Cargo.

View attachment 507192

Turns out those IATA codes have all been reassigned over the years and our logo lookup was keying off whoever owns the code today rather than the carrier at the time.

I changed it so we now resolve by ICAO (which doesn't get reassigned) when the booking has one, so historic Virgin Blue, Jetstar Asia, Scoot, etc now show their own tails. Airnorth wasn't in our airline list at all yet (bi-planes perhaps?) ... so I've added an entry.

A small number of older imports only carry the 2-letter code with no further metadata so those may still resolve to the current code holder. Filing that one as "wont fix" for now.

 

[tripwaffle]

In other news, big update to the iOS app landed today:

• Faster cold start, smoother scrolling, pull-to-refresh
• Edge-swipe back and the rest of the native iOS gestures
• Home screen widgets: your next trip and upcoming events at a glance, in three sizes
• Spotlight search: find any trip or event from iOS search
• Proper offline mode: view your trips without a connection

tripwaffle App - App Store

Much like the recent Android app release though, most the work in this one was house-keeping / refactoring for the future.

 

[SeaWolf]

A small number of older imports only carry the 2-letter code with no further metadata so those may still resolve to the current code holder. Filing that one as "wont fix" for now.

I've got a bunch of flights from a TripIt import that are coming up as Air Dijbouti incorrectly assigned. Is there a way for us to fix this up ourselves? Like, can we redo the TripIt import with the ICAO code, or manually add the ICAO code ourselves to those flights?

 

[tripwaffle]

I've got a bunch of flights from a TripIt import that are coming up as Air Dijbouti incorrectly assigned. Is there a way for us to fix this up ourselves? Like, can we redo the TripIt import with the ICAO code, or manually add the ICAO code ourselves to those flights?

My bad, missed that one.

Air Djiboutis IATA is "DJ", which collides with Virgin Australia's old DJ code (apparently Virgin used DJ until ~2011, switched to VA, then Air Djibouti relaunched in 2015 and got re-assigned DJ. sheeeesh.)

Anyway, fix is deployed, no re-import necessary.

 

[Captain Halliday]

Turns out those IATA codes have all been reassigned over the years and our logo lookup was keying off whoever owns the code today rather than the carrier at the time.

I changed it so we now resolve by ICAO (which doesn't get reassigned) when the booking has one, so historic Virgin Blue, Jetstar Asia, Scoot, etc now show their own tails. Airnorth wasn't in our airline list at all yet (bi-planes perhaps?) ... so I've added an entry.

A small number of older imports only carry the 2-letter code with no further metadata so those may still resolve to the current code holder. Filing that one as "wont fix" for now.

Thanks for the quick fix.

Interestingly it had US airways correct in the previous version, but not so this time (bottom row, second from right)

And it's still showing Scoot when it should be Tiger.

Understanding you need to prioritise the small fixes... is the ICAO field something users can edit. ie. can I fix them myself?

 

[Captain Halliday]

And another layout suggestion for your consideration.

In Lifetime stats, I think it would improve readability of the Top Countries by Flights and Top Countries by Nights were laid out more like Top Airports & Top Airlines.

 

[tripwaffle]

And another layout suggestion for your consideration.

In Lifetime stats, I think it would improve readability of the Top Countries by Flights and Top Countries by Nights were laid out more like Top Airports & Top Airlines.

Makes complete sense thanks.

 

[RooFlyer]

Apologies if this has already been answered.

Am editing an old trip trying to put in SCL 13:35 - SYD 17:45+1. System doesn't 'take' the arrival time presumably because it doesn't make sense on that route - ideally it should recognise that its the next day? Or should be an optional day field available for arrival?

Trip = Mendoza and Chile Heemskirk March 2016 profile 47063

 

[moa999]

And it's still showing Scoot when it should be Tiger.

Likely because when Scoot acquired Tiger Asia in 2017 and merged AOC they took over the TGW/ TR codes so it's in essence a rebranding for historical flights.
Pre-2017 Scoot flights were SCO/ TZ.

 

[tripwaffle]

Thanks for the quick fix.

Interestingly it had US airways correct in the previous version, but not so this time (bottom row, second from right)

And it's still showing Scoot when it should be Tiger.

Understanding you need to prioritise the small fixes... is the ICAO field something users can edit. ie. can I fix them myself?

Pre-2017 TR/TGW should now resolve to "Tigerair" instead of "Scoot"
Pre-2017 TZ/SCO should now resolve to "Scoot" instead of "Transair Limited"
Pre-2011 DJ should now resolve to "Virgin Blue"

Weighing up the pros/cons of exposing ICAO field to users, but currently more inclined to add a "this airline looks wrong" button so that we can then apply systematic fixes. Will kick it around some more, but please feel free to float anything else you come across.

 

[tripwaffle]

Apologies if this has already been answered.

Am editing an old trip trying to put in SCL 13:35 - SYD 17:45+1. System doesn't 'take' the arrival time presumably because it doesn't make sense on that route - ideally it should recognise that its the next day? Or should be an optional day field available for arrival?

Trip = Mendoza and Chile Heemskirk March 2016 profile 47063

Apologies; the save was failing because the form's "is this an overnight flight?" check only looked at the times, not the timezones.
Fixed now to be smarter: please try the edit again and it should stick.

Optional 'arrival day' field is in no way a bad idea, but we'll try to using smarts to avoid it if at all possible.