wcs2kml - Project Hosting on Google Code

Earlier this year Aug 25, 2009 r42 (Added --align_with_base_imagery flag for debugging. ) committed by jeremy.d.brewer - Added --align_with_base_imagery flag for debugging. Added --align_with_base_imagery flag for debugging. Mar 25, 2009 r41 (Moved several files over to CHECK style asserts with more in...) committed by jeremy.d.brewer - Moved several files over to CHECK style asserts with more informative errors. Moved several files over to CHECK style asserts with more informative errors. Mar 24, 2009 r40 (Updated tests to use the ASSERT macros in base.h rather than...) committed by jeremy.d.brewer - Updated tests to use the ASSERT macros in base.h rather than standard C assert. Now tests are more verbose about what they are doing. Fixed a bug in run_tests.py where the return code was always 0. Now we can actually know when a test fails (a good thing). Fixing this bug revealed that some tests relying on test data had not updated their paths properly, and those bugs were fixed. Updated tests to use the ASSERT macros in base.h rather than standard C assert. Now tests are more verbose about what they are doing. Fixed a bug in run_tests.py where the return code was always 0. Now we can actually know when a test fails (a good thing). Fixing this bug revealed that some tests relying on test data had not updated their paths properly, and those bugs were fixed. Mar 24, 2009 r39 (First stab at integrating base.h and string_util.h into this...) committed by jeremy.d.brewer - First stab at integrating base.h and string_util.h into this code base. This makes many Googlely pieces of code possible, e.g. CHECK() rather than assert(). First stab at integrating base.h and string_util.h into this code base. This makes many Googlely pieces of code possible, e.g. CHECK() rather than assert(). Mar 24, 2009 r38 (More license changes. Hopefully this is the final commit th...) committed by jeremy.d.brewer - More license changes. Hopefully this is the final commit that deals with annoying header changes. More license changes. Hopefully this is the final commit that deals with annoying header changes. Mar 24, 2009 r37 (Small updates to run_tests.py to print out number of tests a...) committed by jeremy.d.brewer - Small updates to run_tests.py to print out number of tests and failures. Updated the license headers to include the author. Small updates to run_tests.py to print out number of tests and failures. Updated the license headers to include the author. Mar 22, 2009 r36 (Credit: Jeremy Brewer Small cleanup from previous commit. ...) committed by jeremy.d.brewer - Credit: Jeremy Brewer Small cleanup from previous commit. Delete 2 files and updated the README. Credit: Jeremy Brewer Small cleanup from previous commit. Delete 2 files and updated the README. Mar 22, 2009 r35 (Credit: Jeremy Brewer Major refactoring to the build system...) committed by jeremy.d.brewer - Credit: Jeremy Brewer Major refactoring to the build system. Don't be surprised if things are broken in this commit. Highlights are: - Moved to a straight Makefile + static binary. No more autoconfig mess. - Renamed PngImage -> Image. - Changed to New BSD license (previously Apache). - Wrote run_tests.py for running the unit tests via 'make check'. Credit: Jeremy Brewer Major refactoring to the build system. Don't be surprised if things are broken in this commit. Highlights are: - Moved to a straight Makefile + static binary. No more autoconfig mess. - Renamed PngImage -> Image. - Changed to New BSD license (previously Apache). - Wrote run_tests.py for running the unit tests via 'make check'. Mar 22, 2009 r34 (Credit: Ryan Scranton I don't think this bug should current...) committed by jeremy.d.brewer - Credit: Ryan Scranton I don't think this bug should currently trigger, but Ryan pointed out that for pixels outside of the original image we weren't setting is_opaque to false. It's conceivable that we could generate black tiles in this case. Credit: Ryan Scranton I don't think this bug should currently trigger, but Ryan pointed out that for pixels outside of the original image we weren't setting is_opaque to false. It's conceivable that we could generate black tiles in this case. Older Dec 02, 2008 r33 (Credit: Jeremy Brewer Added 64-bit read & write support to ...) committed by jeremy.d.brewer - Credit: Jeremy Brewer Added 64-bit read & write support to PngImage. Very small changes to Makefile.normal and wcs2kml.cc are also included. Credit: Jeremy Brewer Added 64-bit read & write support to PngImage. Very small changes to Makefile.normal and wcs2kml.cc are also included. Aug 04, 2008 r32 (Credit: Jeremy Brewer Fixed a bug where FITS headers with N...) committed by jeremy.d.brewer - Credit: Jeremy Brewer Fixed a bug where FITS headers with NAXIS1 and NAXIS2 values with NAXIS=0 (these are technically invalid) would project all points to 0, 0. To fix this, I modified Fits::AddImageDimensions() to ensure that NAXIS is always >= 2 regardless of whether NAXIS1 and NAXIS2 are present. Additionally, I found that the CDELT3 and CDELT4 and related keywords didn't affect the projection as I previously thought. I thus removed the checks for these keywords as all of my test images project properly (including the IRAS images which were the initial reason for this check). I'm unsure of what the intial problem I had was, though I suspect it was from the WCSAXES keyword which acts like NAXIS. Finally, I updated wcs2kml.cc to print out the image boundaries. This is useful because the user can see when our projection engine is producing funny results (such as a 0 pixel scale, the bug this CL addresses). Credit: Jeremy Brewer Fixed a bug where FITS headers with NAXIS1 and NAXIS2 values with NAXIS=0 (these are technically invalid) would project all points to 0, 0. To fix this, I modified Fits::AddImageDimensions() to ensure that NAXIS is always >= 2 regardless of whether NAXIS1 and NAXIS2 are present. Additionally, I found that the CDELT3 and CDELT4 and related keywords didn't affect the projection as I previously thought. I thus removed the checks for these keywords as all of my test images project properly (including the IRAS images which were the initial reason for this check). I'm unsure of what the intial problem I had was, though I suspect it was from the WCSAXES keyword which acts like NAXIS. Finally, I updated wcs2kml.cc to print out the image boundaries. This is useful because the user can see when our projection engine is producing funny results (such as a 0 pixel scale, the bug this CL addresses).

r32 (Credit: Jeremy Brewer Fixed a bug where FITS headers with N...) committed by jeremy.d.brewer - Credit: Jeremy Brewer Fixed a bug where FITS headers with NAXIS1 and NAXIS2 values with NAXIS=0 (these are technically invalid) would project all points to 0, 0. To fix this, I modified Fits::AddImageDimensions() to ensure that NAXIS is always >= 2 regardless of whether NAXIS1 and NAXIS2 are present. Additionally, I found that the CDELT3 and CDELT4 and related keywords didn't affect the projection as I previously thought. I thus removed the checks for these keywords as all of my test images project properly (including the IRAS images which were the initial reason for this check). I'm unsure of what the intial problem I had was, though I suspect it was from the WCSAXES keyword which acts like NAXIS. Finally, I updated wcs2kml.cc to print out the image boundaries. This is useful because the user can see when our projection engine is producing funny results (such as a 0 pixel scale, the bug this CL addresses).

Credit: Jeremy Brewer Fixed a bug where FITS headers with NAXIS1 and NAXIS2 values with NAXIS=0 (these are technically invalid) would project all points to 0, 0. To fix this, I modified Fits::AddImageDimensions() to ensure that NAXIS is always >= 2 regardless of whether NAXIS1 and NAXIS2 are present. Additionally, I found that the CDELT3 and CDELT4 and related keywords didn't affect the projection as I previously thought. I thus removed the checks for these keywords as all of my test images project properly (including the IRAS images which were the initial reason for this check). I'm unsure of what the intial problem I had was, though I suspect it was from the WCSAXES keyword which acts like NAXIS. Finally, I updated wcs2kml.cc to print out the image boundaries. This is useful because the user can see when our projection engine is producing funny results (such as a 0 pixel scale, the bug this CL addresses).

Earlier this year

Older