Opened 12 years ago
Closed 12 years ago
#1882 closed defect (worksforme)
regress failure st_asraster, st_resample on mingw64 9.1 mingw64 built 9.1
| Reported by: | robe | Owned by: | dustymugs |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.1 |
| Component: | raster | Version: | 2.0.x |
| Keywords: | Cc: |
Description
Normally I get crashes against EDB 9.1 and mingw64/mingw64 compiled 9.1 pass with flying colors. I am getting failures on st_asraster and st_resample. This isn't the box I normally test on so might be a false alarm like my gdal is misconfigured or something.
See attached.
Attachments (1)
Change History (5)
by , 12 years ago
| Attachment: | raster_mingw64_91onmingw64.zip added |
|---|
comment:1 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Summary: | regress failure on mingw64 9.1 mingw64 built 9.1 → regress failure st_asraster, st_resample on mingw64 9.1 mingw64 built 9.1 |
comment:2 by , 12 years ago
comment:4 by , 12 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I assume your changes have nothing to do with this ticket dusty aside from maybe catching when GDAL Data is not configured right. Anyrate on my regular mingw64 build system for 9.1, the raster tests all pass so I'll dismiss this as a non-issue.
Note:
See TracTickets
for help on using tickets.
It looks like GDAL is misconfigured as it appears that both failures have to do with raster transformations resulting in a raster with the same spatial attributes as in the input raster (though it shouldn't be). It looks like the env variable GDAL_DATA may need to be set.