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
In the exported CSV table, the date/time strings are quite verbose. For example: Wed Feb 15 2017 07:54:22 GMT+0100 (Central European Standard Time)
This string format is computationally expensive to parse. Could the format be changed to ISO 8601 compliant strings? The trade-off may be reduced human readability, but I suspect the CSV tables would be parsed in some way anyway.
Second, exporting date/time as UTC would make sense, as the recorded data refers to worldwide user interactions. It also simplifies parsing since it can then be treated as time zone naive.
The text was updated successfully, but these errors were encountered:
In the exported CSV table, the date/time strings are quite verbose. For example:
Wed Feb 15 2017 07:54:22 GMT+0100 (Central European Standard Time)
This string format is computationally expensive to parse. Could the format be changed to ISO 8601 compliant strings? The trade-off may be reduced human readability, but I suspect the CSV tables would be parsed in some way anyway.
Second, exporting date/time as UTC would make sense, as the recorded data refers to worldwide user interactions. It also simplifies parsing since it can then be treated as time zone naive.
The text was updated successfully, but these errors were encountered: