This is less a question and more of a finding to report.
In 2016, File Geodb Open API treats date values "1901-01-01" as "19000101000000", but in 2021.2.5, the reader treats the same value as "000000". The effect is the record gets thrown out, despite the writer saying all features are written.
We've had to build in a StringReplacer to find all the "000000" to replace with the original date value.
Is this a bug?
Update:
Affects "1900-01-01" as well.
+13
Hello @janet , this sounds odd. I don't have your exact build installed, the closest I had was 2021.2.0, but I haven't been able to reproduce the issue in this build or older versions. Would you be able to share a sample FGDB?
I used FME to add a date column to an existing FGDB. I noticed that altering the Date attributes TYPE on the writer changed how my data was being read in. For example, if Date TYPE = DATE then dates are read into FME like this: "19010101" (which I believe is FME's internal date format) whereas if Date TYPE = STRING dates are read: "1901-01-01". Might be worth checking if you're creating the dates in FME!
I'm happy to try and take a closer look however! Best, Kailin.
Hello @janet , this sounds odd. I don't have your exact build installed, the closest I had was 2021.2.0, but I haven't been able to reproduce the issue in this build or older versions. Would you be able to share a sample FGDB?
I used FME to add a date column to an existing FGDB. I noticed that altering the Date attributes TYPE on the writer changed how my data was being read in. For example, if Date TYPE = DATE then dates are read into FME like this: "19010101" (which I believe is FME's internal date format) whereas if Date TYPE = STRING dates are read: "1901-01-01". Might be worth checking if you're creating the dates in FME!
I'm happy to try and take a closer look however! Best, Kailin.
Here's a sample dataset where one record has "1900-01-01" according ArcGIS.
I can replicate the behaviour through Data Inspector in 2020.2 (20787), 2019.1.3.1 (19643).
+13
Here's a sample dataset where one record has "1900-01-01" according ArcGIS.
I can replicate the behaviour through Data Inspector in 2020.2 (20787), 2019.1.3.1 (19643).
Hello @janet , thanks for sharing your data! I was able to reproduce the "000000". Unfortunately, this seems to also occur in 2022.0. I think you've stumbled across a bug - I will file a ticket with the development team. I'll paste the bug number on this thread once its created! Best, Kailin.
+13
Here's a sample dataset where one record has "1900-01-01" according ArcGIS.
I can replicate the behaviour through Data Inspector in 2020.2 (20787), 2019.1.3.1 (19643).
FMEENGINE-73425.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
