highstock-processing time requires processing world time offset

Highstock's data format uses [[Time, Data],[time, data],[time, data],[time, data]], and time uses 13-bit millisecond values, such as [1133136000000,69.66], The time format used is UTC (World standard Time), so in the background to the time processing, not just a simple conversion to millisecond value, if only for millisecond value, in the foreground of the graphics will appear in the data line and time dislocation phenomenon. Only millisecond values converted to UTC will not appear misaligned.

Java takes the millisecond value under UTC:

Nullnew SimpleDateFormat ("yyyy-mm-dd"= Df.parse ("2012-11-26"=  Calendar.getinstance (Timezone.getdefault ()); // Timezone.getdefault () Gets the host's default TimeZone, which is the time zone offset. Cal.settime (date); List.add (Date.gettime () +cal.gettimezone (). Getrawoffset ()); // Cal.gettimezone (). Getrawoffset () is a relative offset from UTC // date.gettime () +cal.gettimezone (). Getrawoffset () is the millisecond value of the corresponding UTC in 2012-11-26 non-UTC format milliseconds

UTC format milliseconds

highstock-processing time requires processing world time offset