| Summary: | itinerary does not show full airport name when there are multiple airports | ||
|---|---|---|---|
| Product: | [Applications] KDE Itinerary | Reporter: | johnathan <testing1237a-c> |
| Component: | general | Assignee: | Volker Krause <vkrause> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | All | ||
| Latest Commit: | https://invent.kde.org/pim/kitinerary/commit/295b576dac8fa1588636012766190500d98607af | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
boarding pass
android rendering of airport |
||
Created attachment 151212 [details]
android rendering of airport
Similar to bug 457684 that is most likely a data extraction issue, it doesn't know the departure terminal. If that is known it's displayed right below the departure airport name. Git commit 295b576dac8fa1588636012766190500d98607af by Volker Krause. Committed on 16/08/2022 at 17:03. Pushed by vkrause into branch 'release/22.08'. Perform airport terminal detection in the generic boarding pass extractor This was only done in post-processing so far, in case the terminal information had been wrongly put into the airport name field. But it actually works just as well here if we use a vastly less aggressive end anchor. M +1 -0 autotests/extractordata/synthetic/iata-bcbp-demo.pdf.json M +15 -0 src/lib/extractors/genericboardingpassextractor.cpp https://invent.kde.org/pim/kitinerary/commit/295b576dac8fa1588636012766190500d98607af |
Created attachment 151211 [details] boarding pass SUMMARY This one is strange and rather dangerous. In New Delhi, India there are actually 2 airports. New delhi T2 and T3. They are situated at a distance from one another and flights operate at either airport depending upon if the airline is domestic or international (t2 for domestic and t3 for international) as attached screenshots, the boarding pass does show clearly T3 but the same is not rendered in the android app at least and i suspect the same is case in all versions? maybe the airport name is being parsed from list of airports? i am not sure but in this particular case, the critical information is NOT present