Date error in charts (GE 4.4.2 and HTML5 Viewer 2.5.2, Firefox and IE)

Permanently deleted user

08 Februari 2016 12:34

Hi there

 

I have a SVL site that I have just migrated over to HTML5 and have noticed that the year for the date gets incremented in the viewer?!  In the SVL viewer the date appears just fine ie. its all the same year (2016) but in HTML5 viewer note how the date gets incremented up to 2018 (and month is changed). Here is the chart in HTMl5:

 

_img_ alt="Wrong year displayed on date axis" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000TS7P&feoid=Body&refid=0EM60000000Lv8v" _/_img_

 

...and the very same Site.XML in the SVL Viewer:

 

_img_ alt="Dates correct in SVL Viewer" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000TS7P&feoid=Body&refid=0EM60000000Lv90" _/_img_

 

There is only late Jan/early Feb data in the database. Its a DataLink but it does work fine in the SVL viewer.

 

Is this a bug?

 

Thanks

 

Doug

0

• 

  Permanently deleted user

  16 Februari 2016 21:08

  Hi Douglas, 

   

  It is a known issue in the HTML5 viewer that it displays the date/time columns in UTC as oppose to the local time. This will be fixed In the new release of the HTML5 viewer version 2.6. The new version is not out yet but it is scheduled for release during the first quarter of this year.

   

  I hope this helps.

   

  - Carmen

  0
• 

  Permanently deleted user

  17 Februari 2016 10:06

  Thanks Carmen :)

  0
• 

  Permanently deleted user

  17 Februari 2016 20:05

  My HTML 5 Viewer is displaying 3/8/2015 12:02 PM as 3/8/2015 5:02 AM. We are in PST. It seems it is treating the date as UTC and trying to covert to the local time. However the time is already in local time. Is this the issue going to be resolved in the next release? or is this a different issue? Do you have workaround for this?

  0
• 

  Eric Parsons

  17 Februari 2016 21:07

  Hi Masao, Geocortex Viewer for HTML5 2.6 and Geocortex Essentials 4.5 will allow you to specify which time zone your data is stored in, which will enable non-UTC date/time values to display correctly. These versions are currently in beta and scheduled to be released this quarter.

  0
• 

  Permanently deleted user

  08 Mars 2016 20:21

  Ours is an actual DATE issue, not time.  Our DB states 1996-03-15 and it is displayed when queried as 1996-03-14, 4:00:00 PM.  Any idea why this is happening?

  0

Du måste logga in om du vill lämna en kommentar.