Hi Il giorno mar, 03/04/2012 alle 05.46 -0700, JamesH ha scritto: > Removed the -M and seems to have run however unlike the usual 1 row in the > table, it has generated 64 rows each with different rast values. This seems > to me to be wrong but at present I'm having difficulty viewing through QGIS > or OpenJump so can't visually examine. >
the -M parameter should not be a problem! For me it works fine! > It did return a new output message (below) which seems to be alright minus a > few constraints missing: > NOTICE: CREATE TABLE will create implicit sequence > "height_newcastle_rid_seq" for serial column "height_newcastle.rid" > NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index > "height_newcastle_pkey" for table "height_newcastle" > NOTICE: Adding SRID constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding scale-X constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding scale-Y constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding blocksize-X constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding blocksize-Y constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding alignment constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding number of bands constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding pixel type constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Unable to get the pixel types of a sample raster > CONTEXT: PL/pgSQL function "addrasterconstraints" line 91 at assignment > PL/pgSQL function "addrasterconstraints" line 53 at RETURN > WARNING: Unable to add constraint: 'pixel_types'. Skipping > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding nodata value constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Unable to get the nodata values of a sample raster > CONTEXT: PL/pgSQL function "addrasterconstraints" line 94 at assignment > PL/pgSQL function "addrasterconstraints" line 53 at RETURN > WARNING: Unable to add constraint: 'nodata_values'. Skipping > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding out-of-database constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Unable to get the out-of-database bands of a sample raster > CONTEXT: PL/pgSQL function "addrasterconstraints" line 97 at assignment > PL/pgSQL function "addrasterconstraints" line 53 at RETURN > WARNING: Unable to add constraint: 'out_db'. Skipping > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > NOTICE: Adding maximum extent constraint > CONTEXT: PL/pgSQL function "addrasterconstraints" line 53 at RETURN > > Query result with 1 row discarded. > Query returned successfully with no result in 375 ms. > > > "By chance, are you making changes to the sql file outputted by the loader?" > No Bborie, not from running raster2pgsql through to opening the sql file and > running it in PostgreSQL. > > "paste here the output of: SELECT postgis_full_version()" > POSTGIS="2.0.0beta4" GEOS="3.3.3dev-CAPI-1.7.3" PROJ="Rel. 4.8.0, 6 March > 2012" GDAL="GDAL 1.9.0, released 2011/12/29" LIBXML="2.7.8" USE_STATS (procs > from 2.0 r8238 need upgrade) > I believe beta4 was installed ok? > Postgis has not been upgraded correctly! You have to run postgis_upgrade_20_minor.sql, found in postgis folder, to upgrade "procs" postgis! Not sure if this helps you solve the problem! > Regards, > James Regards, -SL _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
