GMT Offset on Date/Time fields on maptip

Permanently deleted user

10. Mai 2014 09:25

I have an SDE service that we are editing in Geocortex.  One of the fields is a date field, it populates in Geocortex with a date picker and a time slider.  On maptips, I am displaying the date (feature description).  The date in the maptip does not refect the date in the field, there is a 6 hour offset.  I assume this is a GMT correction - if I enter 5/19/2014 12:00 AM, it shows up as 5/19/2014 6:00 AM.  If I want the maptip to show the correct date (5/19/2014) - I have to enter the date as 5/18/2014 6:00 PM.   HTML5 viewer, if that makes any difference, but its not a viewer setting, so i'm assuming it wont.

 

I feel like I'm taking crazy pills over here (name that movie for bonus points) - can somebody tell me this is NOT a bug?  My customers are hating me right now!

 

Also if anybody knows how to strip the time stamp off the date completely in a maptip - even better.  I understand I might have to create a view..?

0

• 

  Permanently deleted user

  12. Mai 2014 07:01

  Jake,

  welcome to the jungle (name that band for bonus points :) - as this has been going on for a while now and I'm not sure that there's a solution in place that suits everyone?

  https://support.geocortex.com/SupportForums/Thread.aspx?pageid=0&mid=2&ItemID=7&thread=47901

  you can see that LG would like everyone to store UTC, and they have programmed that into their UI, which is great for those that store UTC, but we don't and from feedback many others don't. It's an interesting one, as the maptips is a different kettle of fish to say the edit date fields, or the Query search on dates.... We get the 'local' date-time displayed in the maptip and in AU fomat (not US) up until the 12th (I think from memory) of the month, then it swings across to the US format! We're on 1.9.1 viewer and I'll soon be testing 2.2 to see how this is handled. 

  Bottom line, for us, and others that store local time, it's a real pain - as we do not/cannot display any date fields in the edit attributes as it will just go and add the UTC offset for us (11 hours) so it looks like the next day being displayed to them, yet the maptips show the correct date for almost half of the month before swapping formats. We've had all sorts of fun with this, and we're lucky that our users have not complained 'that much'. Our workflows cater for the UTC offsets when users add data, and edit so we've got around this shortcoming but it has not been easy!

  hope this has shed some light one what you are experiencing. As for the time-stripping, there is one or two threads on this forum also that you'll find interesting. 

  cheers

  GF

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.