#1199 closed defect (wontfix)
[raster] ST_AsRaster problem with scale being < 1.
| Reported by: | Bborie Park | Owned by: | Bborie Park |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.0 |
| Component: | raster | Version: | master |
| Keywords: | Cc: |
Description
The following fails to properly burn the specified value to the generated raster. If both scales are ≥ 1, there are no problems. Need to see how gdal_rasterize utility works around the problem.
SELECT ST_Value(ST_AsRaster(ST_MakePoint(0, 0), 0.1, 0.1), 1, 1);
SELECT ST_Value(ST_AsRaster(ST_MakeLine(ARRAY[ ST_MakePoint(0, 0), ST_MakePoint(1, 0) ]), 0.1, 0.1), 1, 1);
Change History (2)
comment:1 by , 13 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 13 years ago
Further testing after upgrading GDAL to trunk r23097 showed that this problem resolved itself with the latest revision.
Note:
See TracTickets
for help on using tickets.
Can't fix as testing identical geometries with PostGIS and gdal_rasterize showed that the behavior displayed in PostGIS matched that of gdal_rasterize. Might be a gdal bug?