Ticket #63 (closed defect: wontfix)

Opened 4 months ago

Last modified 2 months ago

handling Geotiff ASCII keys

Reported by: hobu Owned by: mloskot
Priority: major Milestone: 1.0
Component: General Version: svn-trunk
Keywords: geotiff Cc:
LAS Format Version: Not Applicable

Description (last modified by mloskot) (diff)

Mateusz,

Do you have any time to polish up the LASHeader::SetGeoreference function? I saw you left some comments there, and we need to be able to write ASCII keys before we can release 1.0.

Attachments

first-bits-of-ascii-key-support-ticket-63.patch (6.8 kB) - added by mloskot 4 months ago.
This patch includes first bits of GeoTIFF ASCII key support. Because of lack of test LAS files, some issues are still unclear to me. Call: looking for ASPRS LAS files with complet set of GeoTIFF keys included

Change History

Changed 4 months ago by mloskot

  • status changed from new to assigned
  • milestone set to 1.0

Hobu, I'm on it today. Yes, I want to target it to 1.0

Changed 4 months ago by mloskot

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

Fixed in trunk (r816).

After this submissions, following valgrind commands give Zero errors or leaks 

$ cd /path/to/liblas/trunk
$ valgrind --tool=memcheck --leak-check=full ./apps/.libs/las2las test/data/srs.las t.las
$ valgrind --tool=memcheck --leak-check=full ./apps/.libs/lasinfo t.las

Changed 4 months ago by mloskot

  • keywords geotiff added
  • status changed from closed to reopened
  • resolution fixed deleted

GeoTIFF ASCII keys support is still missing.

Changed 4 months ago by mloskot

  • description modified (diff)

Changed 4 months ago by mloskot

  • description modified (diff)

Changed 4 months ago by mloskot

This patch includes first bits of GeoTIFF ASCII key support. Because of lack of test LAS files, some issues are still unclear to me. Call: looking for ASPRS LAS files with complet set of GeoTIFF keys included

Changed 2 months ago by hobu

  • status changed from reopened to closed
  • resolution set to wontfix

Thinking about this more, I don't think we need to support writing ASCII keys, just reading them. libgeotiff doesn't return ASCII keys for any of the coordinate systems that the proj4 conversion functions support at this time. I'm closing this for now...

Note: See TracTickets for help on using tickets.