Opened 15 years ago

Closed 15 years ago

#2753 closed defect (worksforme)

Problem coordinates in JP2-compressed NITF

Reported by: ysiddiqui Owned by: warmerdam
Priority: normal Milestone:
Component: GDAL_Raster Version: 1.5.3
Severity: normal Keywords: nitf
Cc:

Description

JPEG2000-compressed QuickBird NITF files are reported by gdalinfo (with Kakadu support) as having lat/long coordinates that are impossible. For example, the following coordinates are reported for the attached file:

Corner Coordinates:
Upper Left  ( -56.8304837, -15.8165996) ( 56d49'49.74"W, 15d48'59.76"S)
Lower Left  ( -56.8309003, -15.6595117) ( 56d49'51.24"W, 15d39'34.24"S)
Upper Right (     302.995,     -15.810) (302d59'41.74"E, 15d48'37.26"S)
Lower Right (     302.995,     -15.653) (302d59'40.24"E, 15d39'11.74"S)
Center      ( 123.0820139, -15.7349306) (123d 4'55.25"E, 15d44'5.75"S)

Note the attachment is the 5 MB header of a file that is much larger.

Change History (5)

comment:1 by ysiddiqui, 15 years ago

File could not be attached. It is located at the following FTP site:

Site: ftp.i3.com Login: fwarmerdam Password: coreopsis Folder: nitf_problem File: nitf_header.zip

comment:2 by warmerdam, 15 years ago

Keywords: nitf added
Status: newassigned

comment:3 by warmerdam, 15 years ago

Yusuf,

I get reasonable values with gdalinfo from the 1.5 branch (including quite a few fixes after 1.5.3). What binaries are you using? From OSGeo4W?

Corner Coordinates:
Upper Left  ( -56.8304837, -15.8165996) ( 56d49'49.74"W, 15d48'59.76"S)
Lower Left  ( -56.8309003, -15.6595117) ( 56d49'51.24"W, 15d39'34.24"S)
Upper Right ( -57.0050719, -15.8103495) ( 57d 0'18.26"W, 15d48'37.26"S)
Lower Right ( -57.0054886, -15.6532615) ( 57d 0'19.76"W, 15d39'11.74"S)
Center      ( -56.9179861, -15.7349306) ( 56d55'4.75"W, 15d44'5.75"S)

comment:4 by ysiddiqui, 15 years ago

I was using FWTools v2.1.0. You are right that the OSGeo4W version gives the above values. Doh!

comment:5 by warmerdam, 15 years ago

Resolution: worksforme
Status: assignedclosed

It appears this has already been fixed in 1.5 and 1.6 and trunk. Please reopen if you find otherwise.

Note: See TracTickets for help on using tickets.