Ticket #4260 (closed defect: fixed)

Opened 20 months ago

Last modified 20 months ago

OGR GMT layer: wrong extent identification

Reported by: peifer Owned by: warmerdam
Priority: normal Milestone: 1.9.0
Component: OGR_SF Version: svn-trunk
Severity: normal Keywords: GMT
Cc:

Description

The extent of my sample gmt file is: # @R-4/-3.9/37/37.1 However, ogrinfo reports:
Extent: (4.000000, 37.000000) - (-3.900000, 37.100000).

The first character is obviously swallowed when reading the gmt header. I changed line 183 in ogrgmtlayer.cpp which seems to help:

 // char **papszTokens = CSLTokenizeStringComplex( osRegion.c_str() + 1,
    char **papszTokens = CSLTokenizeStringComplex( osRegion.c_str() + 0,

The sample GMT file is attached.

Attachments

bb4326.gmt Download (0.5 KB) - added by peifer 20 months ago.
grid2.gmt Download (0.8 KB) - added by peifer 20 months ago.
Another sample GMT file

Change History

Changed 20 months ago by peifer

Changed 20 months ago by peifer

Another sample GMT file

Changed 20 months ago by peifer

I attach another sample file (grid2.gmt) where the actual extent of # @R900000/1000000/900000/1000000 is reported to be Extent: (0.000000, 900000.000000) - (1000000.000000, 1000000.000000).

Changed 20 months ago by rouault

  • status changed from new to closed
  • resolution set to fixed
  • milestone set to 1.9.0

Applied, thanks

r23112 /trunk/gdal/ogr/ogrsf_frmts/gmt/ogrgmtlayer.cpp: OGR GMT: fix GetExtent?() result that swallowed the first char of the minx bound (#4260)

Note: See TracTickets for help on using tickets.