Opened 15 years ago

Closed 5 years ago

#2963 closed defect (wontfix)

NITF: Multiple image segments with different geoereferencing

Reported by: gaopeng Owned by: warmerdam
Priority: normal Milestone: closed_because_of_github_migration
Component: GDAL_Raster Version: 1.6.0
Severity: normal Keywords: NITF
Cc:

Description

The sample image, sample2.ntf, contains multiple image segments. The image seg 0 has a SR and georeferencing, but other image segments have none. As the result, these image segments don't register.

An alternative solution to attaching SR and georeferencing for all image segments is to remove it from all of them.

The sample image is at ftp://GDAL@ftp.esri.com/NITF/sample.zip.

Change History (5)

comment:1 by warmerdam, 15 years ago

Keywords: NITF added
Status: newassigned

I have made several passes through the code, and it does not seem practical to give the desired behavior in the driver without substantial rewriting. The main problem is that it is hard to establish which images have georeferencing without a lot of processing since there are several sources from which georeferencing might be derived (IGEOLO, and various TREs).

comment:2 by warmerdam, 12 years ago

Milestone: 1.6.4

Remove non-serious milestone.

comment:3 by Jukka Rahkonen, 9 years ago

Sample image perhaps not available. At least the site asks for username/password. NITF specialists perhaps could say it such NITF files are valid and suggest how to handle them.

comment:4 by Even Rouault, 9 years ago

Summary: Multiple image segments with different geoereferencingNITF: Multiple image segments with different geoereferencing

comment:5 by Even Rouault, 5 years ago

Milestone: closed_because_of_github_migration
Resolution: wontfix
Status: assignedclosed

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.

Note: See TracTickets for help on using tickets.