[postgis-users] NoData Constraint

[Bborie Park]

Hey David,

No.  It isn't a problem per-se.  Some would say that it is a problem 
since the ideal is that all rasters in a table have the same raster and 
band metadata.  Personally, having the NODATA value be different across 
different rasters in a table isn't significant as it will NOT affect any 
raster operations done on any subset or all rows of the table.

-bborie

On 02/07/2012 07:55 AM, David Quinn wrote:
> When loading a raster into my database I get the following message:
>
> PL/pgSQL function "addrasterconstraints" line 49 at RETURN
> WARNING:  Unable to add constraint: 'nodata_values'.  Skipping
> CONTEXT:  PL/pgSQL function "addrasterconstraints" line 49 at RETURN
>
> All other messages seem fine. Is it a problem that the NoData constraint is
> not added? Should I be replacing my NoData values in the raster with
> something else before uploading?
>
> Thanks,
> David
>
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users

-- 
Bborie Park
Programmer
Center for Vectorborne Diseases
UC Davis
530-752-8380
bkpark at ucdavis.edu