Skip to content

Releases: stcorp/coda

2.13

04 Nov 15:59
Compare
Choose a tag to compare

πŸ“… 2015-04-29

  • Fixed Python wrapping of functions coda.time_string_to_parts,
    coda.time_string_to_double, and coda.time_string_to_double_utc.
    (they now accept both format and string parameters again)
  • Added Python 3 compatibility.
    In Python 3 coda_expression_eval_string() returns 'bytes' and
    coda_cursor_read_string() returns 'unicode'.
  • Added --open_as option to codadump debug mode.
  • Doxygen documentation is now made with doxygen 2.8.9.1.

2.12.1

04 Nov 16:13
Compare
Choose a tag to compare

πŸ“… 2015-02-24

  • Added option to 'codadump debug' to disable the use of fast-size
    expressions.
  • offset and size arguments to Python coda.cursor_read_bytes() function
    are now optional.
  • Fixed issue where strings returned via the Python interface were sometimes
    shortened if the string contained '\0' or other non-printable characters.
  • Fixed issues where detection of xml files could fail.
    Problems could occur when an element was fully empty (not even containing
    whitespace) or when the element string content or closing tag crossed an
    8Kb boundary in the file.
  • Added entry for 2015-06-30 in leap second table.

2.12

04 Nov 16:00
Compare
Choose a tag to compare

πŸ“… 2015-01-15

  • Fixed memory corruption in 'time to string' functions in Python interface.
  • Added -D option to all command line tools to allow explicit setting
    of CODA definition path.
  • Added feature to reference record fields by index in CODA expressions
    using the '/{0}' style syntax.
  • Improved performance of reading vsf_integer data.

2.11.1

04 Nov 16:03
Compare
Choose a tag to compare

πŸ“… 2014-11-14

  • Detection of HDF5 files now also supports HDF5 files where the
    superblock is not located at the start of the file but at offset
    512, 1024, or 2048. Files that have the superblock starting at
    higher offsets are still not supported.
  • Error messages for offset/size/availability expressions now show at
    which cursor position the error occured.
  • Updates to windows build systems.

2.11

04 Nov 16:04
Compare
Choose a tag to compare

πŸ“… 2014-08-27

  • Refactored XML backend and memory backend
    All XML data is now first fully read in memory (using expat) and then
    accessed from there. Since CODA no longer tries to directly read from
    the files anymore this means that:
    • all data will now be correctly returned as UTF-8
      (even if the XML file had a different encoding)
    • XML entities are now properly parsed
    • error messages that quote xml element content will no longer display
      parts of the xml closing tag in case the xml content was shorter than
      expected.
      Other backends that used in-memory storage (e.g. SP3, RINEX, GRIB, CDF)
      also have been refactored to use the new memory backend.
  • SP3, RINEX, CDF and GRIB backends now present numbers more accurately
    (i.e. matching the underlying float or double precission).
  • Reworked all CODA time functions. The following functions have
    been introduced:
    coda_time_double_to_parts(), coda_time_double_to_parts_utc(),
    coda_time_parts_to_double(), coda_time_parts_to_double_utc(),
    coda_time_parts_to_string(), coda_time_string_to_parts(),
    coda_time_double_to_string(), coda_time_double_to_string_utc(),
    coda_time_string_to_double(), coda_time_string_to_double_utc().
    The following functions are now deprecated and will be removed in a
    future CODA release:
    coda_datetime_to_double(), coda_double_to_datetime(),
    coda_time_to_string(), coda_string_to_time(),
    coda_utcdatetime_to_double(), coda_double_to_utcdatetime(),
    coda_time_to_utcstring(), coda_utcstring_to_time()
    Refer to the bottom section of the libcoda/coda-time.c source code
    to see how to map from the old functions to the new functions.
  • The CODA expressions time format now supports '*' as a special character to
    indicate that values should have leading spaces instead of leading zeros.
  • Improved debug output of codadump
  • Added --no-mmap option to codacheck
  • Improved Fortran interface documentation. Default configuration and examples
    now use 64-bit interface instead of 32-bit interface.
  • Changed default Python version for Windows build to Python 2.7.

2.10.1

04 Nov 16:04
Compare
Choose a tag to compare

πŸ“… 2014-03-21

  • Fixed use of CODA_BUILD_SUBPACKAGE_MODE in CMake build.
  • Fixed small html documentation generation issue in codadd for conversions.

2.10

04 Nov 16:04
Compare
Choose a tag to compare

πŸ“… 2014-02-01

  • Added support for 'offset' and 'invalid' attributes for a Conversion element
    in codadef files.
  • Added int(bool) to CODA expressions.
  • Added size check for content of xml elements to codacheck.
  • Fixed issue where coda_cursor_has_attributes() and coda_type_has_attributes()
    would always return false for HDF5. This could result on attributes not being
    shown in several interfaces (e.g. codadump)
  • Fixed bug in codadump debug argument parsing.

2.9.1

04 Nov 16:05
Compare
Choose a tag to compare

πŸ“… 2013-06-27

  • When parsing an ascii datetime value fails, codacheck will now continue
    checking the remainder of the product.

2.9

04 Nov 16:06
Compare
Choose a tag to compare
2.9

πŸ“… 2013-05-22

  • Added 'SwapDimensions' option to IDL and MATLAB interfaces (default enabled).
    With this option you can disable the automatic transpose operation that CODA
    performs on multi-dimensional array data.

2.8.1

04 Nov 16:07
Compare
Choose a tag to compare

πŸ“… 2013-03-07

  • Fixed issue where ascii time value format definitions with an ascii mapping
    that maps the empty string to NaN, had this mapping applied for any value
    (regression introduced in 2.8).
  • Fixed issue where trying to use coda_cursor_read_bytes/bits on a 'no data'
    special type element could cause a segmentation fault.
  • Time parsing of a string now allows the fractional part of a second to be
    longer than 6 digits (although remaining digits will be ignored and the
    time value will always be truncated at microsecond resolution).
  • The 'complex' special type is no longer restricted to binary data (but
    can now also be used for e.g. ascii data formats).