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

Timeinterval is not necessarily an integer value #74

Closed
bveldkamp opened this issue Sep 24, 2021 · 1 comment
Closed

Timeinterval is not necessarily an integer value #74

bveldkamp opened this issue Sep 24, 2021 · 1 comment

Comments

@bveldkamp
Copy link

bveldkamp commented Sep 24, 2021

I have a service that is time enabled, and has an interval of roughly 12 days. It returns this:

"timeInfo": {
	"timeExtent": [
		1546300800000,
		253402214400000
	],
	"timeReference": null,
	"timeRelation": "esriTimeRelationOverlaps",
	"defaultTimeInterval": 0.39425893413496776,
	"defaultTimeIntervalUnits": "esriTimeUnitsMonths",
	"defaultTimeWindow": 0,
	"defaultTimeWindowUnits": "esriTimeUnitsMonths",
	"hasLiveData": false
},

On which DescribeServices() throws an error: One or more errors occurred. (Input string '0.39425893413496776' is not a valid integer. Path 'timeInfo.defaultTimeInterval', line 1, position 3188

davetimmins added a commit that referenced this issue Sep 25, 2021
@davetimmins
Copy link
Owner

Changed that to a double in release 2.0.1

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

No branches or pull requests

2 participants