Querying a time-enabled feature service with time param yields different results than where param

Jay_Gregory — Fri, 20 Feb 2026 18:51:39 GMT

I have a time-enabled feature service where each feature has a start time and end time - all in UTC time. The time reference in the service is set to UTC timezone and Respects Daylight Savings is set to false. I would like to query using the time parameter using two unix timestamps.

Using a time=1615075200000,1615161599000 query (along with where=1=1), I am getting different results than using a where=start_time>TIMESTAMP '2021-03-07 00:00:00' and end_time<TIMESTAMP '2021-03-07 23:59:59'

Specifically, the time query is returning records before 1615075200000, several days before in some cases.

Am I doing something wrong or is this a bug? I'm working on a fully patched 11.1 Enterprise instance.

My feature service time info is the following:

"dateFieldsTimeReference":{"timeZone":"UTC","respectsDaylightSaving":false} and "timeInfo":{"startTimeField":"start_time","endTimeField":"end_time","trackIdField":null,"type":"field","timeExtent":[1614524400000,1615234548000],"timeReference":{"timeZone":"UTC","respectsDaylightSaving":false},"timeInterval":1,"timeIntervalUnits":"esriTimeUnitsDays","exportOptions":{"useTime":true,"timeDataCumulative":false,"timeOffset":null,"timeOffsetUnits":null},"hasLiveData":false}.

topic Querying a time-enabled feature service with time param yields different results than where param in ArcGIS REST APIs and Services Questions

Querying a time-enabled feature service with time param yields different results than where param