Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#4803 closed defect (fixed)

NITF DESDATA segments can be really large for LiDAR files

Reported by: hobu Owned by: warmerdam
Priority: normal Milestone: 1.9.2
Component: GDAL_Raster Version: unspecified
Severity: normal Keywords:
Cc:

Description

The DESDATA are currently being escaped, and for large LiDAR files, this causes the allocation of the escaped string to overflow. Instead of returning NITF_DESDATA for cases where the DESDATA is > 10mb, we should instead return the offset and byte length of the DESDATA for the user to go fetch themselves.

Change History (4)

comment:1 by hobu, 10 years ago

We will instead add NITF_DESDATA_OFFSET and NITF_DESDATA_LENGTH metadata entries in the case where the DESDATA is > 10mb.

comment:2 by hobu, 10 years ago

Fixed in r24911 and backported in r24912.

comment:3 by hobu, 10 years ago

Resolution: fixed
Status: newclosed

Tweaked in r24913 and r24914.

comment:4 by hobu, 10 years ago

const warning killed in r24915 and r24916

Note: See TracTickets for help on using tickets.