Change timeline timezone

[almende]

Change timeline timezone

[josdejong]

That is not on the planning. The Timeline internally already uses moment.js here and there, so it may be relatively easy to implement moment-timezone.js.

[losttheplot]

If anyone has successfully implemented this suggestion, please could they post the basic steps necessary, to help get me started - thanks :)

[ftringali]

For 3.7.1 version, changing the line (row 25600)
c._isUTC = false;
to
c._isUTC = true;
did the trick.

Using the minified version, search for o._isUTC=!1 and change it to o._isUTC=!0

Hope this helps

[josdejong]

That looks like a dangerous trick...

[ftringali]

Why?

However, dealing just with UTC dates created via epoch I see no side effect.

[josdejong]

It's generally a bad idea to change internal, private variables of an external library, there can easily be overlooked side effects. You will eventually shoot your self in the foot with these kind of hacks.

• With every update of the library, you need to be careful fixing this manually changed thing again (hopefully, the trick still can be applied in newer versions of the library having changed internals).
• Probably, after a couple of months you forgot about this manual change in the code, and after updating to a newer version of the library things break. Furthermore,
• Your colleagues probably don't know about this hook at all and assume the moment.js library works as described in the docs of the library, which isn't the case anymore. That can give weird, hard to track down situations.
• If your application happens to use multiple modules all relying on moment.js, these modules may act unexpectedly as they assume the default behavior as documented by moment.js itself.

Did you have a look at moment.utc()? Docs: http://momentjs.com/docs/#/parsing/utc/

[ftringali]

Yep, I agree (strongly). But I need a "quick and dirty" solution and the timeline uses moment() in too many places to propose a change on your side.

Is there a way to vote for desired enhancements?

[josdejong]

This issues section is both for issues and feature requests.

But again, isn't moment.utc() doing exactly what you need?

[gonzafirewall]

I have the same problem i need that the timeline show me the time in the timezone that i configure, example. I am in Argentina (-3) y pass to setCursorTime the utc time and need that the timeline show me the date in timezone La_Paz that is (-4), Now if i pass a moment object or a Date object i see that the timeline convert to my locale.

[ftringali]

@jos
yes, it does... but the setting of moment.utc objects as items has no effect on the timeline labels.

Please, let us know

[josdejong]

Good point. Maybe as a solution the Timeline should allow to give your own moment constructor via the options, so that you can return moment.utc(...) or some custom time zone instead of local time.

[lee-nk]

Hi. Just wanted to add my vote to this feature request. We are using the Timeline in a web app that is used by people in multiple time zones, and it is very important to us to be able to all use UTC time. For now we are just adding 12 hours to items in the timeline to get the correct times. Thanks :)

[fdelapena]

+1 for this, having a large amount of data and manipulating array timestamps from server or client side is not fast.

[jonhel]

+1

[AdamNowaczyk]

This is something we need as well. We need to show graphs in the server timezone, not user timezone. We use Graph2D and we pass dates in ISO 8601 format. Any suggestions on how to 'force' vis js to that timezone?

Thanks,
Adam

[arixol]

Our application also needs this fix. A simple setTimezoneUTC=true option would suffice for us.

We pass dates using UTC time and the Timeline rearranges them based on local time, so our points are inaccurate.

For example, if I add the date 2015-06-08T15:30:49.000Z to the Timeline and the user is in New York, it will show up in the Timeline as 11:30:49 EDT, which doesn't make sense and confuses the user. When I apply ftringali's hack of setting o._isUTC=!0 in vis.min.js, the point shows up where it should at 15:30:49 UTC.

Are there any plans to make this a setting?

Thanks.

[Heinzelemente]

The same for our projects. Please add this soon +1:

[josdejong]

I've implemented support for time zones by means of a configuration option moment. This is by default is date constructor of moment.js, but can be overloaded which allows applying a custom time zone:

// display in UTC
var options = {
  moment: function(date) {
    return vis.moment(date).utc();
  }
};

// display in UTC +08:00
var options = {
  moment: function(date) {
    return vis.moment(date).utcOffset('+08:00');
  }
};

See this example: https://github.com/almende/vis/blob/develop/examples/timeline/other/timezone.html

I would love to get some feedback on whether the current implementation works correctly and addresses these issues. You can checkout or download the develop branch to give it a try.

[Atala]

Just when I needed it. Thanks!

Seems to work fine for me with basic UTC usage.

[BuschnicK]

Is it possible to change the time zone dynamically after the timeline has already been constructed? I've tried modifying the options member, but that didn't seem to have any effect:
timeline.options.moment = function(date) {
return vis.moment(date).utc();
}

I'm working on a tool that displays data from around the globe and I'd like to be able to switch between local time zone and UTC time zone.

[josdejong]

You can update the options at any moment via Timeline.setOptions(options), so I guess you could provide a new moment instance with different time zone.

[BuschnicK]

That's what I tried, but it doesn't update the timeline.
On Apr 5, 2016 10:08, Jos de Jong [email protected] wrote:You can update the options at any moment via Timeline.setOptions(options), so I guess you could provide a new moment instance with different time zone.

—You are receiving this because you commented.Reply to this email directly or view it on GitHub

[daniel-pfeiffer]

I just figured that also utc is itself a constructor, so you can simplify the 1^st above example to:

// display in UTC
var options = {
  moment: vis.moment.utc
};

With 2 less function calls this is also more efficient.

[AbdulAdnanBaig]

I've been facing a common issue for a few days now, The scenario goes as follows.

1. I receive the timezone of a user on Login and pass that param to the timeline.
2. Now when i change the system timezone to a different zone, the chart still holds the timezone of the user which i provide and does not overwrite it with the system time zone (As Expected).
3. But if i neglect the system timezone, and manually set a time and date, the chart immediately picks up that manually changed wrong data and overwrites my the user timezone.

Help me find a solution where under any circumstance, there cannot be any overwriting of timezone. The source can only be one.