First build of PostGIS module of GeoTools2. Needed to load geometry_columns table?



The first build of the GeoTools2 is almost OK except that of PostGIS.
This is module that I am most interested in.
By doing "maven test" in (excluding all other tests) only.

I am getting the following console message excerpt
25/11/2003 11:03:39 setUp
INFO: exception while making schemaCouldn't make schema: org.geotool no geometry found in the GEOMETRY_COLUMNS table fo
r jdbc_test of the postgis install. A row for geom is required for geotools t
o work correctly
25/11/2003 11:03:39 testMaxFea
INFO: ...threw data source
ption: Couldn't make schema: no geometry
found in the GEOMETRY_COLUMNS table for jdbc_test of the postgis install. A r
ow for geom is required for geotools to work correctly

I installed PostGreSQL/PostGIS correctly and tested with the accompanying sample of the PostGIS
and it worked perfectly. Now I am wondering if any additional sql script is needed to load into PostGre, besides postgis.sql,
in order to make the GeoTools run properly.

I guess that the table geometry_columns must be loaded. So, is there any standard procedure for doing that?
Do I need to run the samples tests in some specified order?

SinceI am a rookie in the field the automatic successful test of the postgis is very helpful for our learning and a good starter.

thanks a lot




April 10, 2015, 3:17 PM

CodeHaus Comment From: cholmes - Time: Sun, 15 Feb 2004 16:25:55 -0600
The geometry_columns table should be part of the postgis.sql installation. There should be nothing more past that to get geotools working with postgis. I can't investigate right now, as my geotools install is not building properly (need to install jai), but I don't see how this error is made. It looks like 'testset' for the tablename was replaced by jdbc_test, as it's looking for a geometry column for jdbc_test, which is not on the public server. We probably actually should get rid of the public server - is the more up to date test, you just need to modify to point to your db, and it will create the tables and test them (though I haven't tested in awhile).

I'll try to take some time to review the tests, but I use the postgis module all the time, as part of geoserver, so I'm confident it should work, and you should not need any additional tables. If your postgis install does not have a geometry_columns table then you probably did not install it right. The only thing you'll need to do to get working with postgis is to make sure you create your tables with the 'AddGeometryColumn' function, as that creates the right values in the geometry_columns table.

April 10, 2015, 3:17 PM

CodeHaus Comment From: chorner - Time: Wed, 12 Jul 2006 18:58:14 -0500
A successful PostGIS install has a geometry_columns table, and properly imported data has the correct rows added as well. Fixing broken installs is beyond the scope of the datastore.








Affects versions