From: | Jeff Hoffmann <jeff(at)propertykey(dot)com> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org>, Brook Milligan <brook(at)biology(dot)nmsu(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: geographic coordinate types? |
Date: | 2000-08-16 14:51:02 |
Message-ID: | 399AAA56.18866F11@propertykey.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker wrote:
>
> For example? We use the point type for doing long/lat coordinates, and
> for calculating distance between places on one of our projects ... but I
> take it you are thinking of something more elaborate then that?
>
i got the impression that the "real" mapping types includes
transformation functions -- i.e., we have data in both state plane and
lat/long (UTM) and they need to play nice together. some more details
would be nice -- there are free packages out there to do the
transformation at the application level (search for PROJ and gctpc for a
couple of pointers), but nobody i know of has needed anything like that
enough to actually put it in the database itself. i think it would be
interesting to put out there exactly what you need to see what isn't
there, what can be worked around, what would be a good target for future
development, etc. i've had a few "wouldn't it be nice thoughts" about
similar things, but it's always been easier to workaround because as far
as i can tell there's not a whole lot of interest in those features.
--
Jeff Hoffmann
PropertyKey.com
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-08-16 15:24:29 | Re: AW: Open Source Database Routs Competition in New Bench mark Tests |
Previous Message | Brook Milligan | 2000-08-16 14:49:02 | Re: geographic coordinate types? |