Ideas for wcs2kml 0.2

0 views
Skip to first unread message

Jeremy Brewer

unread,
Sep 12, 2007, 8:00:56 PM9/12/07
to wcs2kml
This topic is brainstorming for what we should aim for in wcs2kml
0.2. Feel free to add feature requests.

For now my list is:
- unit tests + test data + changes to Makefile.am for testing
- include smart compressor script for turning non-transparent parts of
regionated images into JPEG
- beef up fits2png.py to expose more options from fitsimage as
commandline flags
- Fix Makefile.am for build on Windows (I need help on this)
- integrate support for numpy into Python modules (support Numeric/
numpy or just numpy?)

Further down the line:
- integrate parts of fitslib into pyfits & switch to pyfits?

Chris

unread,
Sep 13, 2007, 9:41:00 AM9/13/07
to wcs2kml
I am all for supporting just numpy. Numeric support has been dropped
by the community. Heck the numpy folks have been working with Guido
to get an array interface based upon the numpy c-api into Python 3000.

I also think that PyFITS should be used. Of course I will admit to
being biased. Looking at fitslib.py code the only things that are not
already in the PyFITS interface are the FITS class and the find_hdus
function. You could leave these helper functions in the fitlib.py
module and just use PyFITS everywhere else until we can get something
similar into PyFITS itself.

Chris

Reply all
Reply to author
Forward
0 new messages