Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft timeInfo needs #57

Open
slibby opened this issue Oct 30, 2017 · 2 comments
Open

Draft timeInfo needs #57

slibby opened this issue Oct 30, 2017 · 2 comments

Comments

@slibby
Copy link
Member

slibby commented Oct 30, 2017

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
@tannerjt
Copy link

tannerjt commented May 27, 2020

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'.

@rgwozdz
Copy link
Member

rgwozdz commented May 27, 2020

Hello @tannerjt - do you have request URL with an example of this you can pass to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants