You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
adding a timeInfo object as an optional addition to the Feature Service endpoint would allow koop-based services to appear to be time-aware for ArcGIS clients. timeInfo defines several basic items:
startTimeField: field used as the start timestamp for a feature
endTimeField: field used as the end timestamp for a feature
timeExtent: [, ] in epoch milliseconds
timeReference
timeZone
respectsDaylightSaving
timeRelation
defaultTimeInterval
defaultTimeIntervalUnits
defaultTimeWindow
hasLiveData
The text was updated successfully, but these errors were encountered:
I'm not sure if this this issue is the same as what I'm exploring now, but it seems FeatureServer does not respect time queries in ArcGIS Online with 'timestamp'. For example, where=CreationDate > timestamp '2019-05-06 06:59:59'. Even if field type is esriFieldTypeDate, this query returns a count of 0. I believe this is because FeatureServer does not recognize 'timestamp'.
adding a
timeInfo
object as an optional addition to the Feature Service endpoint would allow koop-based services to appear to be time-aware for ArcGIS clients. timeInfo defines several basic items:startTimeField
: field used as the start timestamp for a featureendTimeField
: field used as the end timestamp for a featuretimeExtent
: [, ] in epoch millisecondstimeReference
timeZone
respectsDaylightSaving
timeRelation
defaultTimeInterval
defaultTimeIntervalUnits
defaultTimeWindow
hasLiveData
The text was updated successfully, but these errors were encountered: