After doing an in-depth investigation on the data, we have a few questions which we want to check with you:
A reminder, In our process, the user enters his flight number with the airline code and departure date as “DAL503 on 22.1” and we need to show him his flight -> only 1 option
- what is the meaning of ident and actual_ident fields on AirlineFlightScheduleStruct that returns from AirlineFlightSchedules API?
for example, DAL503 on 22.1 returns Array size 6, which includes this flight number 5 time as actual_ident and the last one, uses for a different flight origin and destination
we can show the user the first option, but how can we be sure this is the right one? Which “ident” number should we choose?
- What should be the right format of the airline and flightno inputs on AirlineFlightSchedules API ?
We take the flight number and airline code that the user enters as 1 string and split it into 2 strings: 1 as the airline and 1 as the flight number
What should be the logic?
W62846 - > airline = W6 and flightno= 2846
DAL503 -> airline = DL and flightno= 503
This is what we think:
If the string has more than 1 letters, take all the letters and the rest should be the flight number
If the string has 1 letter, take the first 2 characters, and the rest should be the flight number
If the string has 0 letters, ask the user to check it in google to know the airline
Is it current, or we must ask from the user to provide the airline and the flight number separately and validate first the airline?
- does the same flight number can be used on the same day on different hours? This is what we see in the first example (1 to KEWR and the second to KPDX)