Ticket #2623 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Datum ignored in NLAPS header file

Reported by: ysiddiqui Owned by: warmerdam
Priority: high Milestone: 1.6.0
Component: GDAL_Raster Version: 1.5.2
Severity: normal Keywords: NLAPS
Cc:

Description

When reading an NLAPS header file (*.H1), gdalinfo (and I assume other GDAL code) interprets the datum as WGS84, regardless of the actual datum listed in the file. The attached file is an example of where the datum is not WGS84. Line 30 says "HORIZONTAL_DATUM=NAD27;" There should be a document at USGS listing the datums that could be used in an NLAPS file -- try  this link.

Attachments

LT5022036000615710.H1 Download (2.8 KB) - added by ysiddiqui 5 years ago.
Example NLAPS header file with NAD27 datum

Change History

Changed 5 years ago by ysiddiqui

Example NLAPS header file with NAD27 datum

Changed 5 years ago by warmerdam

  • keywords NLAPS added
  • priority changed from normal to high
  • status changed from new to assigned
  • component changed from default to GDAL_Raster

Changed 5 years ago by warmerdam

  • status changed from assigned to closed
  • resolution set to fixed
  • milestone set to 1.6.0

I have reworked the NLAPS coordinate system handling to be somewhat more general though it only supports a few common named datums. In theory it will now support projections other than UTM though I have no examples of such.

I'm nervous enough that I'd rather not retrofit the changes to 1.5 branch. They are in trunk now (r15596).

Note: See TracTickets for help on using tickets.