Opened 13 years ago
Closed 5 years ago
#4289 closed defect (wontfix)
[PATCH] Setting the GeoTransform parameters doesn't work on the Intergraph format
Reported by: | DaveOke | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | closed_because_of_github_migration |
Component: | GDAL_Raster | Version: | 1.8.0 |
Severity: | normal | Keywords: | |
Cc: | ilucena |
Description (last modified by )
If the user creates a new Intergraph formatted raster file, calling set geotransform doesn't carry though from the dataset to the raster band, resulting in an incorrect transformation matrix being encoded in the resultant intergraph .grd file.
We fixed this issue by modifying the IntergraphRasterBand::FlushBandHeader function to copy the transformation matrix from the dataset, only if a transformation matrix has been set, to the raster band before the headers are written.
Attachments (1)
Change History (7)
comment:1 by , 12 years ago
Description: | modified (diff) |
---|
comment:2 by , 12 years ago
Cc: | added |
---|
comment:4 by , 9 years ago
It looks to me that changes has not been applied to /gdal/browser/trunk/gdal/frmts/ingr/IntergraphBand.cpp
If the user has set a transformation matrix, encode the new transformation
matrix into the band if (poGDS->bGeoTransformSet)
memcpy(&hHeaderOne.TransformationMatrix, &poGDS->hHeaderOne.TransformationMatrix, sizeof(double)*16);
Meanwhile there has been other changes. Perhaps it would be best if DaveOke could make a new patch on top of current trunk, or what?
comment:5 by , 9 years ago
Summary: | Setting the GeoTransform parameters doesn't work on the Intergraph format → [PATCH] Setting the GeoTransform parameters doesn't work on the Intergraph format |
---|
comment:6 by , 5 years ago
Milestone: | → closed_because_of_github_migration |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.
Perhaps you could attach to that ticket your changes as a patch