You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to add support to the Coded Text File Parser to apply a time offset to all datetime values? For example, if my datetime properties are in GMT, could this tool add support for adjusting the times (and potentially the dates, where appropriate) to PST?
It would be even better if there were support for generic offset conversion without reference to a reference time zone (i.e. GMT/UTC). For example, instead of implementing this feature in a way that it expects GMT data, just have it apply an offset (up to 24 hours +/-). This way, if I had PST data that was supposed to be EST data, I could just apply a +3 hour offset. In other words, the -8 hour offset should have any reference to Pacific time (as would be the case if it expected the source data to be GMT).
Thoughts?
The text was updated successfully, but these errors were encountered:
Would it be possible to add support to the Coded Text File Parser to apply a time offset to all datetime values? For example, if my datetime properties are in GMT, could this tool add support for adjusting the times (and potentially the dates, where appropriate) to PST?
It would be even better if there were support for generic offset conversion without reference to a reference time zone (i.e. GMT/UTC). For example, instead of implementing this feature in a way that it expects GMT data, just have it apply an offset (up to 24 hours +/-). This way, if I had PST data that was supposed to be EST data, I could just apply a +3 hour offset. In other words, the -8 hour offset should have any reference to Pacific time (as would be the case if it expected the source data to be GMT).
Thoughts?
The text was updated successfully, but these errors were encountered: