Live data from Hacker News

The maddening mess of airport codes [video]

youtube.com

61–70 of 159 posts

Re: The maddening mess of airport codes [video]

#61
post #49

Earlier quoted context omitted.

Or better try telephone region codes, which are ambiguous when a phone number is written as a consecutive string of digits, without +/()/-/space.

You say this as if it’s a universal thing, like IATA codes, but I assume it’s a quirk of some particular country? My region code definitely does not have this. Sounds pretty nuts to me btw, how does that work when you turn it into standard E.164 format like “+123456789”?

Many countries (if not all of them) use localized numbering format - short numbers to hit the local destinations (intra-city calls), numbers with city prefixes to get to the numbers in a different city within the same country, specific prefixes (i.e. 00) for international calls, etc. The most convenient way of processing this mess is to rewrite the numbers (called/calling) on the ingress, into e164, and then processing the call using the routing table/rules of the pbx. On the egress the numbers may be rewritten again using the local numbering rules. This is how I built the international telephony system in one of my previous companies at least.

Some countries are easier in their numbering system (Singapore being an obvious example) and some are not (China doesn’t disclose number ranges allocated for different regions/cities, which makes the renumbering step more difficult)

Re: The maddening mess of airport codes [video]

#62

The entire world of airline coding (as in "encoding") is fascinating to me: there are all kinds of ancient semi-human-readable formats like ACARS[1] and IATA Teletype[2] that are still pushing data around. Not the mention standard meal codes[3], like BLML for "bland meal" and CLML for "celebration cake meal." [1]: https://en.wikipedia.org/wiki/ACARS [2]: https://en.wikipedia.org/wiki/Airline_teletype_system [3]: http…

I have done work integrating real time systems with flight data in all of these encodings and telex for a large intl travel company that does contracts at an airport you have flown at. A lot of legacy systems are using very early web protocols like SOAP or old encodings e.g. Telex messages.

Re: The maddening mess of airport codes [video]

#64
post #49

You think airport codes are bad, try airline codes. The IATA standard is still only two (2) letters, leading to insanity like recycling codes after one airline dies, meaning the meaning of the code is time-dependent, and, even worse, "controlled duplicates" where two airlines are intentionally assigned the same code at the same time , since they fly in different parts of the world and pinky-promise to never overlap.…

Or better try telephone region codes, which are ambiguous when a phone number is written as a consecutive string of digits, without +/()/-/space.

[deleted]

Re: The maddening mess of airport codes [video]

#65

Earlier quoted context omitted.

You say this as if it’s a universal thing, like IATA codes, but I assume it’s a quirk of some particular country? My region code definitely does not have this. Sounds pretty nuts to me btw, how does that work when you turn it into standard E.164 format like “+123456789”?

Britain has different length area codes. 020 is London, 0121 is Birmingham, 01234 is Bedford, 015396 is Sedburgh, population 2700. The local part of the number is 8, 7, 6 or 5 digits accordingly. I never found this to be a problem. If you're dialing locally from a land line, you usually know the local code. For national or international dialing it doesn't matter. Occasionally people put the space in the wrong place,…

This feature of a numbering system is referred to as “open-plan numbering“. In a place with “closed-plan” numbering, all telephone numbers have the same length and format.

Re: The maddening mess of airport codes [video]

#67

Earlier quoted context omitted.

I've also wondered why cryptically abbrevated things like NOTAMS are still the way they are. It made sense in a teletype/telegraph world where brevity was worth time and money. From wikipedia, this is a typical NOTAM: A1234/06 NOTAMR A1212/06 Q)EGTT/QMXLC/IV/NBO/A/000/999/5129N00028W005 A)EGLL B)0609050500 C)0704300500 E)DUE WIP TWY B SOUTH CLSD BTN 'F' AND 'R'. TWY 'R' CLSD BTN 'A' AND 'B' AND DIVERTED VIA NEW GREEN…

You should try having to read several hundred of them before a long-haul duty! Good luck trying to find the runway closure notam buried among the 400 reports of a crane within curvature-of-the-earth viewing range of an airport, or the 300 reports of birds that were once seen near, or somewhere near the runway. Too hilarious not to share: https://fixingnotams.org/wp-content/uploads/2019/11/Field-Gu...

That's one hell of an interesting read.

Re: The maddening mess of airport codes [video]

#68
post #49

You think airport codes are bad, try airline codes. The IATA standard is still only two (2) letters, leading to insanity like recycling codes after one airline dies, meaning the meaning of the code is time-dependent, and, even worse, "controlled duplicates" where two airlines are intentionally assigned the same code at the same time , since they fly in different parts of the world and pinky-promise to never overlap.…

Or better try telephone region codes, which are ambiguous when a phone number is written as a consecutive string of digits, without +/()/-/space.

Or just the date. The dumb game of dd/mm/yy versus mm/dd/yy when you live in a dd/mm/yy country is infuriating.

Re: The maddening mess of airport codes [video]

#69
post #61

Earlier quoted context omitted.

You say this as if it’s a universal thing, like IATA codes, but I assume it’s a quirk of some particular country? My region code definitely does not have this. Sounds pretty nuts to me btw, how does that work when you turn it into standard E.164 format like “+123456789”?

Many countries (if not all of them) use localized numbering format - short numbers to hit the local destinations (intra-city calls), numbers with city prefixes to get to the numbers in a different city within the same country, specific prefixes (i.e. 00) for international calls, etc. The most convenient way of processing this mess is to rewrite the numbers (called/calling) on the ingress, into e164, and then processi…

There's many places where you can skip the area code or similar when dialling, but I think the original poster was thinking of systems where the actual numbering has variable-length components.

Re: The maddening mess of airport codes [video]

#70

The entire world of airline coding (as in "encoding") is fascinating to me: there are all kinds of ancient semi-human-readable formats like ACARS[1] and IATA Teletype[2] that are still pushing data around. Not the mention standard meal codes[3], like BLML for "bland meal" and CLML for "celebration cake meal." [1]: https://en.wikipedia.org/wiki/ACARS [2]: https://en.wikipedia.org/wiki/Airline_teletype_system [3]: http…

#3 has RFML - Refugee Meal. I wonder what that is.

humble pie
Post reply on HN