X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 1E5AC11F65FD for ; Wed, 29 Mar 2006 16:56:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 31289-01 for ; Wed, 29 Mar 2006 16:56:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.sonalysts.com (sentry.sonalysts.com [198.6.208.103]) by postgresql.org (Postfix) with ESMTP id CFFD911F65FA for ; Wed, 29 Mar 2006 16:56:27 -0400 (AST) Received: from localhost ([127.0.0.1]) by mail.sonalysts.com (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)); Wed, 29 Mar 2006 15:56:22 -0500 Message-ID: <442AF473.7020600@sonalysts.com> Date: Wed, 29 Mar 2006 15:56:19 -0500 From: Josh Rovero Organization: Sonalysts, Inc. User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Achilleus Mantzios , pgsql general Subject: Re: [SQL] Flight numbers data References: <1143651002.3625.147.camel@state.g2switchworks.com> <1143663136.32384.314.camel@localhost.localdomain> In-Reply-To: <1143663136.32384.314.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200603/1459 X-Sequence-Number: 93324 We built an operational flight tracking and weather system that uses Postgresql, http://www.sonalysts.com/wXstation One data feed (FAA ASDI) uses both aircraft registration numbers (tail numbers) and airline-assigned flight numbers. Typically if you have the latter, you won't get the former. This feed only has information for flights in the U.S. or to/from the U.S. The data feed also includes flight plans, so it wouldn't be too hard to build up a flight number schedule over a short period of time. Outside the U.S. the problem is more difficult. > Has anyone from the postgresql camp ever solved such a problem? >