Ok, I have a better fix in SVN r8300. imsave now accepts a "dpi" kwarg (default of 100) to set the DPI metadata in the file.
Mike Michael Droettboom wrote: > You're right. Thanks for the sanity check. > > What's happening is that when using imsave is used, it generates a > figure image with a dpi of 1 (to force 1 output pixel per input pixel), > but this is sort of a hack. Let me see if I can find a way around this > hack. > > Mike > > Ryan May wrote: > >> On Thu, May 6, 2010 at 1:40 PM, Michael Droettboom <md...@stsci.edu> wrote: >> >> >>> It looks like the conversion from dots-per-inch (matplotlib's internal >>> representation) to dots-per-meter (the unit defined in the PNG standard) >>> was bogus. This should be fixed in SVN r8298. >>> >>> >> Are you sure that's right? This doesn't look like a conversion to dots >> per meter: >> >> size_t dots_per_meter = dpi * 2.54 * 100.0 >> >> To my eyes, unit-wise, that looks like dots/inch * cm/inch * cm/m = >> dots * m / inch**2. The original looks correct in regard to units to >> me: >> >> size_t dots_per_meter = dpi * 100 * (1 / 2.54) -> dots/inch * cm/m * >> inch/cm -> dots/m >> >> Am I missing something? >> >> Ryan >> >> >> > > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------------ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
