ArcGIS Versioned Archive Dates Not in UTC

692
3
Jump to solution
07-11-2017 02:51 PM
JoseSousa
Esri Contributor

Hi,

I have noticed that the dates being pushed to versioned archive tables "_H" GDB_FROM_DATE and GDB_TO_DATE are local not in UTC. Is there a way to change this behavior?

Cheers,

Jose 

0 Kudos
1 Solution

Accepted Solutions
Asrujit_SenGupta
MVP Regular Contributor

No, we don't have that flexibility yet.

The archive process—ArcGIS Help | ArcGIS Desktop 

Working with historical versions—ArcGIS Help | ArcGIS Desktop 

When working with archived information, it is important to understand that the date and time recorded in the gdb_from_date and the gdb_to_date fields of the archive reflect the date and time a transaction took place—when a feature was added, edited, or removed from the feature class. This date and time is received from the server OS. This affects how you access and query the archive.

View solution in original post

3 Replies
Asrujit_SenGupta
MVP Regular Contributor

No, we don't have that flexibility yet.

The archive process—ArcGIS Help | ArcGIS Desktop 

Working with historical versions—ArcGIS Help | ArcGIS Desktop 

When working with archived information, it is important to understand that the date and time recorded in the gdb_from_date and the gdb_to_date fields of the archive reflect the date and time a transaction took place—when a feature was added, edited, or removed from the feature class. This date and time is received from the server OS. This affects how you access and query the archive.

JoseSousa
Esri Contributor

Hi Asrujit,

Thanks for replying. I hope this is implemented somewhere in time.

Cheers,

Jose

0 Kudos
andysp
by
New Contributor III

Just in case anyone else happens upon this thread: we typically have versioned feature classes with Editor Tracking enabled. We have recently started to implement archiving. Our editor tracking timestamps are in UTC and our archive table (_H) timestamps are in local time.

However, it appears that for nonversioned data, the archive timestamps are in UTC rather than local time. (Editor tracking timestamps are still in UTC as well.)

This is on 10.4.1 with an Oracle back end; YMMV.

0 Kudos