[postgis-tickets] [PostGIS] #2777: Huge literal in enforce_max_extent_rast check constraint
PostGIS
trac at osgeo.org
Mon Jun 23 09:31:42 PDT 2014
#2777: Huge literal in enforce_max_extent_rast check constraint
--------------------+-------------------------------------------------------
Reporter: strk | Owner: dustymugs
Type: defect | Status: new
Priority: medium | Milestone:
Component: raster | Version: trunk
Keywords: |
--------------------+-------------------------------------------------------
After importing a raster with this command:
{{{
raster2pgsql -C -I -s 4326 -Y -t '256x256' -l 2,4,8,16
}}}
The definition of the imported table has an "enforce_max_extent_rast"
which uses a literal geometry value using 177,797 hex characters.
Shouldn't it just be a 5 vertices polygon ?
The constraint reads:
{{{
"enforce_max_extent_rast" CHECK (st_coveredby(st_convexhull(rast),
'<177,797 hex chars here>'::geometry))
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2777>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-tickets
mailing list