On Monday 27 March 2006 19:28, Paul Surgeon wrote:
> On Monday 27 March 2006 18:45, Lee Elliott wrote:
> > I think we could identify the appropriate countries
> > accurately using the geometric stuff in postgres (dunno if
> > other dbms have the functions and datatypes).
> >
> > Basically, I believ
On Monday 27 March 2006 18:45, Lee Elliott wrote:
> I think we could identify the appropriate countries accurately
> using the geometric stuff in postgres (dunno if other dbms have
> the functions and datatypes).
>
> Basically, I believe we would have to take the country outlines
> and use them to
On Sunday 26 March 2006 10:26, Paul Surgeon wrote:
> On Saturday 25 March 2006 19:48, David Megginson wrote:
> > On 25/03/06, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> > > The airports list is barely usable: there are so many
> > > entries in it that you don't easily find anything. And the
> > >
On Sun, 26 Mar 2006 11:26:41 +0200
Paul Surgeon wrote:
>
> The best would be to have a country and state/province field in the
> airport DB and that would need to come from Robin Peel unless we want
> to have a different DB again.
We could straddle the fence and have a second file which maps
airpo
--- Melchior FRANZ wrote:
> The airports list is barely usable: there are so many entries
> in it that you don't easily find anything. And the slider resolution
> is much too high for finding an entry with it alone. Move it
> just one pixel, and you jumped over oodles of airports. The arrow
> butto
On Sunday 26 March 2006 13:49, David Megginson wrote:
> On 26/03/06, Paul Surgeon <[EMAIL PROTECTED]> wrote:
> > I did do some work on that a long time ago using the ICAO codes to break
> > up the data by country but ran into a couple of problems.
> >
> > 1. There is no state/province field in the
On 26/03/06, Paul Surgeon <[EMAIL PROTECTED]> wrote:
> I did do some work on that a long time ago using the ICAO codes to break up
> the data by country but ran into a couple of problems.
>
> 1. There is no state/province field in the airports db and it can't be deduced
> from ICAO codes.
> 2. The
On Saturday 25 March 2006 19:48, David Megginson wrote:
> On 25/03/06, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> > The airports list is barely usable: there are so many entries
> > in it that you don't easily find anything. And the slider resolution
> > is much too high for finding an entry with
On 25/03/06, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> The airports list is barely usable: there are so many entries
> in it that you don't easily find anything. And the slider resolution
> is much too high for finding an entry with it alone. Move it
> just one pixel, and you jumped over oodles
The airports list is barely usable: there are so many entries
in it that you don't easily find anything. And the slider resolution
is much too high for finding an entry with it alone. Move it
just one pixel, and you jumped over oodles of airports. The arrow
buttons have no repeat function, so they
10 matches
Mail list logo
