Skip to main content
Question

FeatureReader drops a 0 in a 'datetime' in case of reading an OGC Geopackage

  • February 22, 2026
  • 1 reply
  • 18 views
wilmar
Participant
Forum|alt.badge.img+1

I'm trying to read a OGC geopackage which contains fields of the type 'datetime'.
In FME 2025.1 (which uses version 16 of the FeatureReader) something unexpected happens: in case the number of seconds starts with a 0 (zero), this zero gets dropped after reading the data. See record 21 in the screenshots for an example:
In FME 2025 the field ‘tijdstipRegistratieLV' misses a 0 after the '1009' (10 hour 9 minutes).
In FME 2023 the readout is correct: 20101214100907 (2010 december 14th, 10 hour 09 minutes 07

Is this a known issue/bug?

    1 reply

    max_h
    Enthusiast
    Forum|alt.badge.img+24
    • max_hEnthusiast
    • Enthusiast
    • February 23, 2026

    That error was fixed in 2025.2.1 as it seems:

    Geopackage Reader: Cannot parse datetime values in FME 2025.1

    Changelog - FME by Safe Software

    So I guess try updating and then run the workspace again.

      Community Stats

      32,431
      Posts
      122,985
      Replies
      40,160
      Members

      Latest FME

      Terms & ConditionsCookie settingsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.