Opened 17 years ago
Closed 17 years ago
#1640 closed defect (fixed)
Remove 500 char limit on HFA metadata reads and allow updates
Reported by: | Sam Gillingham | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | 1.4.2 |
Component: | GDAL_Raster | Version: | 1.4.1 |
Severity: | normal | Keywords: | HFA |
Cc: |
Description
The attached proposed patch resolves 2 issues with the HFA metadata:
- You cannot read more than 500 characters of data. However, since the metadata is written to a GDAL specific node and GDAL sets the maxNumChars field we can safely rely on this field to tell us how many characters to read.
- When updating the HFA file and overwriting metadata, duplicate nodes get created. This crashes Imagine. The patch checks for their existance before creating new ones.
Attachments (1)
Change History (2)
by , 17 years ago
Attachment: | hfaopen.cpp.patch added |
---|
comment:1 by , 17 years ago
Keywords: | HFA added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
sues confirmed.
Patch applied in trunk (r11542) with some adjustments for code style, and simplification.
Test script (autotest/gdrivers/hfa.py) extended with a couple metadata related checks to regression test this change.
Patch merged into 1.4 and 1.4-esri branches.
Thanks Sam!
Note:
See TracTickets
for help on using tickets.
proposed patch