Milliseconds are lost when reading from Geopackage?

Question

I have used FME 2022.2.5 to write datetimes with millisecond accuracy to a Geopackage. But when I try to use the same FME and a FeatureReader to read the datetimes from the Geopackage I get truncated datetimes with second accuracy.

When I use the SQLite format in the FeatureReader when reading the features, the datetimes include millisecond accuracy.

I have inspected the Geopackage using DBeaver and there I can see the datetimes with milliseconds and the type is DATETIME.

I would expect FME to be able to read DATETIME's from a Geopackage file with millisecond accuracy, but that might not be the case?

Regards, Casper

Page 1 / 1

Hi @Casper Børgesen,

FME is converting the Geopackage internal SQLite datetime to an FME datetime for convenience, but in doing so is truncating to the nearest second. I am escalating this to a support case, so we can look at changing the conversion settings.

Reply

daveatsafe · Answer

Hi @Casper Børgesen​,FME is converting the Geopackage internal SQLite datetime to an FME datetime for convenience, but in doing so is truncating to the nearest second. I am escalating this to a support case, so we can look at changing the conversion settings.

Reply

Community Stats

Sign up

An FME Account is required to contribute

Login to the community

An FME Account is required to contribute

Scanning file for viruses.

This file cannot be downloaded