On Sat, Dec 10, 2011 at 04:46:26PM -0600, Aren Cambre wrote:
> The script's first gripe was that the *spatial_ref_sys* table already
> exists. Shouldn't it automatically kill and reload that table? Is that a
> bug?
Was a bug, now fixed: http://trac.osgeo.org/postgis/ticket/1365
No, isn't supposed
Ok, just checking.
http://svn.osgeo.org/postgis/trunk/extras/tiger_geocoder/tiger_2010/
Looks like something like this might do it:
cd /usr/share/postgresql/contrib
# edit create_geocode.sh
# then run it
./create_geocode.sh
or just load them from here:
http://svn.osgeo.org/postgis/trunk/extras
I refreshed the functions list and the parent DB and even opened/closed
pgAdmin III. :-)
I also ran this script:
*SELECT * FROM pg_proc proc JOIN pg_language lang*
*ON proc.prolang = lang.oid*
*ORDER BY proname;*
Double-checked myself with:
*SELECT * FROM pg_proc proc JOIN pg_language lang*
*ON p
Try right click on database and/or function list and refresh it.
On 12/10/2011 6:15 PM, Aren Cambre wrote:
Thanks.
Now here's what I don't get: where are the *geocode* and
*geocode_intersection* functions? If I look at the functions list in
*spatial_db_template*'s *public* schema (using pgAdmin
Thanks.
Now here's what I don't get: where are the *geocode* and *
geocode_intersection* functions? If I look at the functions list in *
spatial_db_template*'s *public* schema (using pgAdmin III), should I see
those two? I thought they were included in the base PostGIS 2.0 product?
Aren
On Sat,
You can ignore all the notices. As long as you do not get a rollback,
then things should be ok.
The script is just trying to clean out potential obsolete functions that
might be there if the database was created many versions ago and
upgraded to this point.
-Steve W
On 12/10/2011 5:46 PM, A
Thanks. Yup, I see it now. My mind was stuck in 3rd generation languages
where things stop when you get an exception.
The script's first gripe was that the *spatial_ref_sys* table already
exists. Shouldn't it automatically kill and reload that table? Is that a
bug?
Anyway, I deleted it and reran
Oops! My head is always in the raster world, so I just ran with the
raster upgrade. Sorry about that.
If you're getting an error, you'll want to scroll up past the
transaction error message as the very first error message should be
related to the actual statement that is failing.
-bborie
On Sa
Thanks. Yesterday I found *postgis_upgrade_20_minor.sql* in *
/usr/share/postgresql/9.1/contrib/postgis-2.0*.
When I ran that, I got tons of errors like this:
*psql:/usr/share/postgresql/9.1/contrib/postgis-2.0/postgis_upgrade_20_minor.sql:3235:
ERROR: current transaction is aborted, commands ign
Aren,
Since you're tracking trunk, after you've done the configure, make and
make install, you'll want to run the upgrade script
rtpostgis_upgrade_20_minor.sql
Usually, the file is installed in the same place as rtpostgis.sql. If
you can't find the upgrade file, you can find it in your checkout
Thanks. I got the latest SVN snapshot. I was able to* configure*, *make*,
and *make install*. The problem is there seems to be missing steps between
building the whole thing and getting changes into my preexisting
PostGIS-enabled database.
Aren
On Fri, Dec 9, 2011 at 9:47 PM, Bborie Park wrote:
If you used something like...
svn check out https://svn.osgeo.org/postgis/trunk
You can safely run...
svn update
If that works, I'd recommend doing...
svn cleanup
-bborie
On Fri, Dec 9, 2011 at 7:19 PM, Aren Cambre wrote:
> I admit this is a dumb question, but here it is.
>
> I installed Po
I admit this is a dumb question, but here it is.
I installed PostGIS on my Ubuntu 11.10 environment a few weeks ago using
the excellent instructions at
http://www.letseehere.com/postgis-geocoder-using-tiger-2010-data.
Since then, the *geocode_intersection* function was added, and I need it.
I'm n
13 matches
Mail list logo
