Opened 8 years ago
Last modified 6 years ago
#3776 new defect
[raster] ST_DumpAsPolygons() stop differenciate values when they are higher than 1048576
Reported by: | pracine | Owned by: | dustymugs |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS GDAL |
Component: | raster | Version: | 2.3.x |
Keywords: | raster | Cc: |
Description (last modified by )
This works fine:
SELECT (ST_DumpAsPolygons(ST_SetValue(ST_AddBand(ST_MakeEmptyRaster(1, 2, 0, 0, 1), '32BUI'::text, 1048575), 1, 1, 1048576))).* rast
returning two polygons, but this fails:
SELECT (ST_DumpAsPolygons(ST_SetValue(ST_AddBand(ST_MakeEmptyRaster(1, 2, 0, 0, 1), '32BUI'::text, 1048576), 1, 1, 1048577))).* rast
The only difference is when the pixel values get over 1048576 (which is 0x100000 by the way).
Change History (5)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Description: | modified (diff) |
---|
comment:3 by , 7 years ago
Milestone: | PostGIS 2.3.3 → PostGIS 2.4.0 |
---|
comment:4 by , 7 years ago
Milestone: | PostGIS 2.4.0 → PostGIS 2.5.0 |
---|
comment:5 by , 6 years ago
Milestone: | PostGIS 2.5.0 → PostGIS GDAL |
---|
Going to assume this is a GDAL bug. Still a problem with PostGIS 2.5.0beta1 and GDAL 2.2.4. I'll need to check 2.3 to see if it's fixed in GDAL 2.3
Might be a symptom of #2353