I see the time zone offset is off by an hour in ignition. What could be causing it?
Testing with system.date.getTimezoneRawOffset() function.
I'm in CST/CDT time zone.
Due to this, my CSV imports with timestamps data is displayed with 1 hour offset.
Is it due to daylight saving? how do we address this issue in ignition?
Returns the amount of time in milliseconds to add to UTC to get standard time in this time zone. Because this value is not affected by daylight saving time, it is called raw offset.
Description
Returns the current timezone offset versus UTC, not taking daylight savings into account.
Not sure how this relates to your CSV files. Maybe you can explain the problem you're actually having and an example of the data in those files.
Well...
Your offset seems right to me. What did you expect ?
edit:
Wait, I think I got it (I'm not super familiar with CST/CDT).
I'm guessing you were expecting a 5 hours offset because the raw offset should ignore DST ?
edit again:
I mixed up CST and CDT (REALLY not familiar).
CDT is offset by 1 for DST, so CST is the one 6 hours behind UTC, which corresponds to the 6 hours offset you get
Ok, my csv file has datetime fields data like this
when I import this into ignition, data is getting displayed like this
Using Pytz library to convert the timezone to local from UTC
Currently the server is located in MO State, CST timezone
Don't use python libs for this kind of things, use java's.
Time to guess:
What's happening here is that the time in your csv is using CDT, so 5 hours behind UTC.
BUT, your ignition is probably set up to use CST. So you get that 1 hour offset.
yes. how do we configure CDT in ignition? and day light saving
To compound the problem, the Daylight Savings Time laws were changed some time back.
