Timeslider - time information is shifted

Question

I published data on the ArcGIS server with following service: http://176.34.114.255/ArcGIS/rest/services/fleetPoc/fleetTracks/MapServer (A layer with cartracks, a table with info about the cartracks)

I want to run a timeslider on the track layer which includes data with time information from 7/20/2010 - 8:23:00 AM to 7/21/2010 - 12:37:00 AM

The layer is time-enabled, with following settings in mxd:
*layer time extent -> calculated automatically: and as a result set to 7/20/2010 - 8:24:00 AM to 7/21/2010 - 12:38:00 AM)
*Advanced setting: UTC+1 (as data are in Germany) / no correction for daylight savings
*time offset = 1 min

Following, looking at:
*general service: http://176.34.114.255/ArcGIS/rest/services/fleetPoc/fleetTracks/MapServer the Time Info informs: Time Extent: [2010/07/20 08:24:00 UTC, 2010/07/21 00:38:00 UTC] 
*click on the tracks: http://176.34.114.255/ArcGIS/rest/services/fleetPoc/fleetTracks/MapServer/0 the Time Info informs: Time Extent: [2010/07/20 07:24:00 UTC, 2010/07/20 23:38:00 UTC]; 
Time Zone: W. Europe Standard Time;  Respects Daylight Saving: False

In my timeslider I want to get the timeinformation automaticaly from my layer using:timeInfo=fLayer.timeInfo;
map.timeSlider = myTimeSlider;
myTimeSlider.createTimeStopsByTimeInterval(timeInfo.timeExtent,1,TimeInfo.UNIT_MINUTES);

(It concerns a ArcGISdynamiclayer so units are hardcoded but I'd like to retrieve the timeInfo directly from the layer.

However, when I run the application, the timeslider starts 2 hours later and ends 2 hours later:  7/20/2010 - 10:24:00 to 7/21/2010 - 02:38:00 
When I debug on the timeInfo: it returns also information 2 hours too late: startTime = 7/20/2010 - 10:24:00 GMT+0200, endTime = 7/21/2010 GMT+0200.

I tried the removing the advanced settings in the mxd (no UTC info); adding/removing the daylight savings but that did not help.

Does somebody has a tip how to tackle this issue?

Thanks in advance!
Kindly,
Leen

LeenD_hondt · Answer

I have been testing for a long time this issue. I think it is an issue of the timeslider itself. If someone can confirm or reject this, it would be great!

My conclusion of testing: The time settings (extent) in the timeslider are depending on the time set on the pc of the client.

EXAMPLES FROM ESRI:
When you check on examples on the site of ESRI where the timeslider has hour information, changing the time settings on your pc (client pc) does has an impact on the time seen on the timeslider. This is independently of whether you use a arcgisdynamic layer or a feature layer

Examples checked:
ex 1 Redlands collisions-> data in dates (no time info) -> no check possible    
ex 2 volcanos -> data in years (no time info) -> no check possible     
ex 3 http://help.arcgis.com/en/webapi/flex/samples/index.html#/TimeSlider__dynamic_service_/01nq00000035000000     
 Arcgisdynamic layer is used 
        Changing time settings on own pc (client pc) changes time on viewer    
ex 4 http://help.arcgis.com/en/webapi/flex/samples/index.html#/Filtering_by_time/01nq0000003n000000     
 Featureservice is used     
 Changing time settings on own pc (client pc) changes time on viewer     
ex 5 http://help.arcgis.com/en/webapi/flex/samples/index.html#/Time_rendered_earthquakes/01nq00000009000000     
 Featureservice is used     
 Changing time settings on own pc (client pc) changes time on viewer     
ex 6 http://help.arcgis.com/en/webapi/flex/samples/index.html#/Time_aware_Image_service/01nq00000062000000     
 same problem

When I try with my own data:
-Server is in Ireland (time settings: UTC, daylight savings)
-Client is in Belgium (time settings: UTC+1, daylight savings)
-Data itself are from UTC+1 (in Germany)
-Using an arcGISdynamic layer
-I want to call my time info trough "timeInfo=(fLayer as ArcGISDynamicMapServiceLayer).timeInfo" (not via setting the start- and endtime)

While testing, I noted the following:
-Not setting an time information on the mxd on the server -> time slider has not appropriate time (start-endtime) -> 2h shift noted
-Changing the time settings on the client -> has an impact on time extent of the timeslider locally
-Changing the time settings on the server -> has no impact on time extent on timeslider locally
-In the mxd on the server, setting the advanced settings, the appropriate timezone (UTC+1) -> has no impact on time extent on timeslider locally
-In the mxd on the server, setting the time settings on the timeslider (UTC+1) -> has an impact on the time extent on timeslider locally

Conclusion for my arcgisdynamic data (in UTC+1) if I do not want to touch the time settings of both the client (UTC+1, daylight savings) nor the server (UTC, daylight savings):
-Set the timeslider to UTC+1 on the server mxd. Timeslider timeextent will correspond with data. However, somebody in another time zone will view the time extent differently (in my eyes this is a bug)

Any tips/advice on how to tackle this would be great!
I published data on the ArcGIS server with following service: http://176.34.114.255/ArcGIS/rest/services/fleetPoc/fleetTracks/MapServer (A layer with cartracks, a table with info about the cartracks)