laptop and a wrench


The ArcGIS for Server GeoEvent Extension 10.3.1 does not honor the time zone settings on a feature service.

Last Published: July 29, 2016 ArcGIS for Server
Bug ID Number BUG-000092462
SubmittedNovember 24, 2015
Last ModifiedJune 5, 2024
Applies toArcGIS for Server
Version found10.2
StatusWill Not Be Addressed

Additional Information

An ArcGIS Server map/feature service can be configured to represent its date/time values in a local time zone rather than the default (which is UTC). Refer to the map/feature service's Date Field Setting property. The best practice recommendation, when using GeoEvent Server to ingest event data and apply real-time analytics, is to treat all date/time values as UTC. Primarily this is because, once instantiated as a GeoEvent, an attribute value of type Date is a long integer value without any units. All events are atomic and the product's intent, by design, is that the long integer value always represent the number of milliseconds since the Unix epoch (January 1, 1970 midnight UTC). If an inbound event stream broadcasts its event data with date/time values represented as string values without a time zone designation (e.g. "12/31/2012 23:59:59"), GeoEvent already assumes the date/time is being expressed in the server machine’s local time zone. In this specific case, and only if all client applications also reside in the same time zone as the GeoEvent Server, it might make sense to set a feature service's Date Field Setting property to match the relative date/time value of the event data being ingested. Otherwise GeoEvent uses the received value's designated time zone to instantiate a Date value relative to the Unix epoch (January 1, 1970 midnight UTC). This is done deliberately with the assumption that a server machine’s data is normally broadcast without regard to the location or configuration of a potential client which might subscribe to receive the server’s broadcast data. Coordinated universal time (UTC) is how servers and clients coordinate date/time values when they are in different geographic regions.

Steps to Reproduce

Bug ID: BUG-000092462


  • ArcGIS for Server

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options