Alternative to TripIt = TripWaffle

[tripwaffle]

Minor fix @tripwaffle.

I've noticed that flights imported from Flightradar24 are not reading the flight reason correctly.

Flight reason 2 is importing as "crew", where it should be "work".

reason=0 -> 'business'
reason=1 -> 'leisure'
reason=2 -> 'work' (just fixed; was 'crew')
reason=3 -> (never seen)
reason=4 -> ?

Thanks for reporting.

 

[SeatBackForward]

Are there any plans to track incoming flights - for the delays notification?

 

[tripwaffle]

Are there any plans to track incoming flights - for the delays notification?

We are tracking inbound already in some instances, but it's all a matter of data coverage, and we're cheap like that

In terms of using this for delay notifications: it gets pretty complicated, as airlines can swap aircraft (if they have any available) at the last moment. So in a way, you'd also have to know what other nearby inventory is on hand.

There's essentially an unlimited amount of analysis/optimisation you can do on flight tracking / prediction so we're mostly focused on easy wins at this stage.

 

[rigram]

I have "long itineraries" and the dashboard looks messy - can this be improved? Suggestion: possibly display a month of visible days, with an adjustable slider to move the visible month left or right....

 

[tripwaffle]

I have "long itineraries" and the dashboard looks messy - can this be improved? Suggestion: possibly display a month of visible days, with an adjustable slider to move the visible month left or right....

My bad, we should of tested this scenario. Now fixed to dynamically drop date labels, which is functional for now.

 

[rigram]

My bad, we should of tested this scenario. Now fixed to dynamically drop date labels, which is functional for now.

View attachment 506691

Thankyou - easier on the eye now

 

[TheCollecter]

Hi @tripwaffle I'm having fun manually keying in flights from last year or so, it's like a trip down memory lane Two questions:

1. Flight QF33 from PER > CDG about a year ago comes up only as SYD > PER (the leg I wasn't on) - how can I manually correct that?
2. Only the one QF Dom flight from this month shows actual depart/arrive times. Everything older has nothing... am I doing something wrong?

Thank you

 

[tripwaffle]

Hi @tripwaffle I'm having fun manually keying in flights from last year or so, it's like a trip down memory lane Two questions:

1. Flight QF33 from PER > CDG about a year ago comes up only as SYD > PER (the leg I wasn't on) - how can I manually correct that?
2. Only the one QF Dom flight from this month shows actual depart/arrive times. Everything older has nothing... am I doing something wrong?

Thank you

Oh boy, was this a rabbit hole.

1. As you identified: QF33 is a multi-leg flight, which ordinarily we'd match the upcoming leg/segment based on booking email details. Understand the need to correct historic flights though, so now it's possible to change airports/times from the add/edit flight page.

2. We're not fetching enrichment details for historic flights, only upcoming ones. Rationale is its expensive- a single tripit import would generate hundreds of lookups for us. Plus data gets patchier the further back you go (we could realistically only do 6-12 months back at present).

Hope all this makes sense, but shout if I've missed anything. Appreciate the feedback.

 

[TheCollecter]

Oh boy, was this a rabbit hole.

1. As you identified: QF33 is a multi-leg flight, which ordinarily we'd match the upcoming leg/segment based on booking email details. Understand the need to correct historic flights though, so now it's possible to change airports/times from the add/edit flight page.

2. We're not fetching enrichment details for historic flights, only upcoming ones. Rationale is its expensive- a single tripit import would generate hundreds of lookups for us. Plus data gets patchier the further back you go (we could realistically only do 6-12 months back at present).

Hope all this makes sense, but shout if I've missed anything. Appreciate the feedback.

Magic, thank you!

1. I have adjusted, and now looking good
2. Understood... just checking I wasn't making a mistake

I'm enjoying, keep up the good work