Solved

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

8 months ago
Feb 22, 2026 12:21 PM UTC
2 replies
106 views

+2

wilmar
Contributor

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?

Best answer by max_h

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.

View original

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.