Hi James,
I suggest you avoid upper case letters in table & column names if you can. It
makes a few things easier
The syntax in both SQL statements is wrong. Try:
select
ST_CreateGeometryColumn('public','CLEANEDCAMDENGPS','geom',4326,'POINT',2);
the fields are (in order):
schema where t
Id just be updating the existing database column using makepoint and concatnate
from the lat and long columns.
Peter
James Smith wrote:
Dear all,
Would appreciate some help. I have created an existing database (with
PostGIS extension) and it has a table called CLEANEDCAMDENGPS which is
po
Dear all,
Would appreciate some help. I have created an existing database (with
PostGIS extension) and it has a table called CLEANEDCAMDENGPS which is
populated with approx 600,000 rows. There are 20 or so columns in the
table, two of which are Latitude and Longitude (WGS84). I would now
like to c
30 million records isn't really a lot with an index and shouldn't be taking
quite that long?
Johnathan
On May 29, 2011, at 12:28 AM, Stephen Woodbridge
wrote:
> I have had similar performance experiences working with tiger data in other
> applications, ie not this geocoder, where queries cos
its fixed - there was a typo in a script that caused spatial_ref_sys
not to be loaded
--
Brian Hamlin
planetwork.net
OSGeo California Chapter
(415) 717-4462 cell
___
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refr
