Suggestions on storing and retrieving geocode data

From: "George Woodring" <george(dot)woodring(at)iglass(dot)net>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Suggestions on storing and retrieving geocode data
Date: 2006-01-26 17:55:46
Message-ID: 1B1B254441DB31448BD34C5BD73B0B8B1BE777@PHOENIX.istructure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I am looking for suggestions on storing and retrieving geocode
information.

My application currently stores 2 columns (lat, long) as numeric and I
have a btree index on them. This works fine for the current set of
data, but as it expands I know it will become an issue.

I am looking at changing the index to an rtree, but I did not know if it
is better to create a point column or if I could use the existing
lat/long columns.

The query will always be to select points inside a box.

Thanks in advance,
Woody

----------------------------------------
iGLASS Networks
211-A S. Salem St
Apex NC 27502
(919) 387-3550 x813
www.iglass.net

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ben Trewern 2006-01-26 18:03:46 Re: Alternative to knoda, kexi and rekall?
Previous Message Rich Shepard 2006-01-26 17:51:17 Re: Access Problem After Version Upgrade -- Update