On Mon, Aug 13, 2012 at 12:43:21PM -0700, James Marca wrote: > On Sat, Aug 11, 2012 at 03:53:56PM -0400, Paragon Corporation wrote: > > Correct. It's just with loading tabblock data which isn't used in Geocoder. > > I don't have it used in any function at the moment actually though its a > > table a couple of people asked for for stats > > which is why we included it. > > > > anyrate just fixed the issue for tiger_2011 (distributed with PostGIS 2.1) > > and will have fixed for tiger_2010 (distributed with PostGIS 2.0) soon as > > well > > Awesome. But...now I hit a new problem > > NOTICE: INSERT INTO > tiger_data.ca_tabblock(the_geom,intptlon,intptlat,awater,aland,funcstat,uace,ur,mtfcc,name,tabblock_id,countyfp,statefp) > SELECT the_geom,intptlon,intptlat,awate; > ERROR: value too long for type character varying(15) > CONTEXT: SQL statement "INSERT INTO > tiger_data.ca_tabblock(the_geom,intptlon,intptlat,awater,aland,funcstat,uace,ur,mtfcc,name,tabblock_id,countyfp,statefp) > SELECT the_geom,intptlo" > PL/pgSQL function "loader_load_staged_data" line 24 at EXECUTE statement > > > I am processing California. > > I will add the -e flag to the psql command to see what is too long .
I think the issue is tiger_staging.ca_tabblock.gid is character_varying(16), while tiger.tabblock.tabblock_id is character varying(15). There are 343 entries in tiger_staging.ca_tabblock with gid length of 16, all the rest are 15. Is it okay to just change tabblock_id to varchar(16)? Regards, James
pgpFbIL9pc2qf.pgp
Description: PGP signature
_______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
