| Re: Crowd support wanted for adding metadata to READ_PNG and WRITE_PNG [message #93666 is a reply to message #93614] |
Mon, 26 September 2016 17:25   |
andrewcool777
Messages: 27
Registered: November 2012
|
Junior Member |
|
|
On Tuesday, 6 September 2016 20:56:50 UTC+9:30, superchromix wrote:
> On Monday, September 5, 2016 at 5:11:17 AM UTC+2, andrew...@gmail.com wrote:
>> Hi All,
>>
>> The PNG image format is a wonderous thing. Lossless, but with user selectable variable compression, 8 or 16bit image data, and most importantly, the ability to
>> have user-defined metadata!
>>
>> Yet for some reason, in their infinite wisdom, RSI never provided the functionality to read or write the metadata when they wrote the routines! :-(
>>
>> I run a number of airglow cameras, provided by the great guys at Keo Scientific,
>> and the images are saved as PNG files, with a basic set of metadata. Now I've been able to write IDL code to extract that metadata, and write PNG files with (extended, modified) metadata, as reported previously, but it's quite (read _very_) slow, and would definitely be better off done within the IDL Read_PNG and Write_PNG routines!
>>
>> However, as I'm the only IDL user on the planet to request this feature, I'm told by Harris Support that it won't happen unless more users put their hands up and
>> say "Me too, please!"
>>
>> So here's my plea to you. If you think it might be a Good Thing to have IDL's
>> own PNG routines handle the reading and writing of user supplied metadata, please
>> submit a Feature Request to support@harris.com to this effect.
>>
>> Many Hosannas will be said in your name for doing so...
>>
>>
>> Regards,
>>
>> Andrew Cool
>> www.skippysky.com.au (for all your astronomy weather forecast needs...)
>
> This is not exactly what you're looking for, but just out of curiosity.. Have you considered using the equivalent routines from Python? Are these not, essentially, available within IDL as of the latest releases?
>
> If you are distributing an IDL application, perhaps this wouldn't work for you? Or, would it? What are the implications of using the IDL-Python bridge for distributed IDL applications which are meant to be run via the virtual machine?
>
> best
> Mark
Python. Exactly what Harris said. So why then am I paying bucketloads of money for IDL? I'd like IDL to do the job, not get fobbed off onto some 3rd party, flakey software that has it's own set of bugs and quirks to contend with.
Whilst I'm not distributing the code externally, neither do I want to force all my colleagues to install Python - a task made even more difficult by the Defence
environment that we work in.
I'm of the opinion that IDL, as a very expensive, graphics orientated package
should be able to correctly handle a very common, standard image format, without passing the buck.
If I have to start using Python, perhaps I don't need IDL, and Harris are shooting themselves in the foot?
Andrew
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
