Opened 14 years ago

Closed 14 years ago

#3289 closed defect (invalid)

Reading addtional metadata from NITF segments

Reported by: gaopeng Owned by: warmerdam
Priority: high Milestone: 1.7.0
Component: GDAL_Raster Version: 1.6.1
Severity: normal Keywords: NITF
Cc:

Description (last modified by warmerdam)

Could you add the following metadata items:

The following metadata tags can be found under the PIAIMC segment:

CLOUDCVR
SENSNAME
MEANGSD

The following metadata tags can be found under the CSEXRA segment:

SENSOR
PREDICTED_NIIRS
CIRCL_ERR
LINEAR_ERR

Attactched contains more info on these segments.

Attachments (1)

NITFRasterTypeAttributes.xlsx (11.3 KB ) - added by gaopeng 14 years ago.

Download all attachments as: .zip

Change History (5)

by gaopeng, 14 years ago

comment:1 by warmerdam, 14 years ago

Description: modified (diff)
Milestone: 1.6.41.7.0
Owner: changed from Warmerdam to warmerdam
Priority: normalhigh
Status: newassigned

comment:2 by warmerdam, 14 years ago

Gao,

Are you aware you can already fetch the raw value of these TREs via the "TRE" domain?

eg.

const char *pszValue = GDALGetMetadataItem( poDS,"PIAIMC", "TRE" );

this is described at the bottom of:

http://www.gdal.org/frmt_nitf_advanced.html

If you still want this broken out as mainline metadata I can do so, but the generic mechanism was put in place to limit the amount of TRE type specific metadata that needs to be handled.

comment:3 by gaopeng, 14 years ago

We tried "TRE" domain, and I was told it doesn't return the needed metadata. I'll check again, and get back to you.

comment:4 by gaopeng, 14 years ago

Resolution: invalid
Status: assignedclosed

Using "TRE" and parsing the string we are able to extract the metadata needed. I am closing this Ticket if there is no other requests for the parsed name-value pairs.

Note: See TracTickets for help on using tickets.