Opened 13 years ago

Last modified 13 years ago

#36 closed defect

PrintTag (geo_print.c) could produce unreadable results — at Version 1

Reported by: rnicz Owned by: warmerdam
Priority: normal Milestone:
Component: libgeotiff Version:
Keywords: Cc:

Description (last modified by warmerdam)

In some cases listgeo could produce unreadeble ModelPixelScaleTag values.

Format code for sprint (FMT_DOUBLE - "%-17.15g") could use all 17 characters and PrintTag (geo_print.c) procedure don't care about spaces between fields. In result you can get following listgeo output: 

      ModelPixelScaleTag (1,3):
         0.5002263635690950.5002263635690950

instead of 

      ModelPixelScaleTag (1,3):
         0.500226363569095 0.500226363569095 0

Unfortunatelly bad formatting is not detected by geotifcp.

--

Best regards

RNicz

Change History (2)

comment:1 by warmerdam, 13 years ago

Description: modified (diff)

Could you supply a small file presenting this problem?

I have *not* encountered this with the timepoints when I thought I would in the past.

by rnicz, 13 years ago

Attachment: #36-test.meta​ added

listgeo output to reproduce error

Note: See TracTickets for help on using tickets.