topic Re: REST API - No JSON Object could be decoded in Python Questions

REST API - No JSON Object could be decoded

TrilliumLevine1 — Fri, 22 May 2015 10:05:59 GMT

Hello All,

I have a script that I'm using to download services as a geodatabase using the REST api. It works about half the time -- the other half the time I get a 500 error stemming from a 'No JSON object could be decoded' error. Anyone have any idea why this might be happening? I don't think it's a bug in my script, since it works sometimes, but I've attached it in case anyone has any ideas and wants to see how it's put together. Any feedback is greatly appreciated!

Re: REST API - No JSON Object could be decoded

RebeccaStrauch__GISP — Fri, 22 May 2015 16:42:12 GMT

Any chance it is hitting secure services that you don't have proper credentials? Just a guess, I haven't fully deciphered your script.

Re: REST API - No JSON Object could be decoded

TrilliumLevine1 — Tue, 26 May 2015 07:12:25 GMT

Nope, it's definitely not a credential problem.

Re: REST API - No JSON Object could be decoded

DougBrowning — Tue, 10 Nov 2015 22:27:59 GMT

I have the same issue. At 10,000 features it worked great. Not at 32,000 and it dies with the same error as you.

Re: REST API - No JSON Object could be decoded

BruceHarold — Tue, 10 Nov 2015 23:01:21 GMT

Try:

'expiration': 60,

in your credentials. i.e. an integer, not a string.

It looks like the token is timing out. You have to manage token lifecycle.

This is a whole lot easier in ArcGIS Pro.

Regards

Re: REST API - No JSON Object could be decoded

DougBrowning — Tue, 10 Nov 2015 23:09:29 GMT

Thanks but where do I put this? No idea where to add that.

Opps thought this was from REST. Here is the code where do I add that?

#Get a local replica of the HFS

proxy_port = None

proxy_url = None

agolSH = AGOLTokenSecurityHandler(username=username,password=password)

fs = FeatureService(url=url,securityHandler=agolSH,proxy_port=proxy_port,proxy_url=proxy_url,initialize=True)

result = fs.createReplica(replicaName='Demo', layers='0,1,2,3', keep_replica=False, layerQueries=None, geometryFilter=None, returnAttachments=True,returnAttachmentDatabyURL=False,returnAsFeatureClass=True, out_path=outDir)

Re: REST API - No JSON Object could be decoded

BruceHarold — Tue, 10 Nov 2015 23:22:09 GMT

Line 139, in the file downloaded.

As written it was '60', not 60.

Re: REST API - No JSON Object could be decoded

DougBrowning — Tue, 10 Nov 2015 23:28:32 GMT

You must be looking at the other guys code. Mine is this.

from arcrest.security import AGOLTokenSecurityHandler

from arcrest.agol import FeatureService

from arcrest.common.filters import LayerDefinitionFilter

#Get a local replica of the HFS

proxy_port = None

proxy_url = None

agolSH = AGOLTokenSecurityHandler(username=username,password=password)

fs = FeatureService(url=url,securityHandler=agolSH,proxy_port=proxy_port,proxy_url=proxy_url,initialize=True)

Re: REST API - No JSON Object could be decoded

BruceHarold — Tue, 10 Nov 2015 23:31:31 GMT

Oops, sorry, yes I was.

I know the arcrest author, I'll bring him in - stand by.

Re: REST API - No JSON Object could be decoded

JonathanQuinn — Wed, 11 Nov 2015 01:49:32 GMT

In the meantime, if you run Fiddler while running the script, you may be able to get the request that doesn't return JSON and see what the actual response is. I'd imagine it's html and not JSON, so the WebView response will help in Fiddler, but that's just a guess.

Re: REST API - No JSON Object could be decoded

DougBrowning — Wed, 11 Nov 2015 16:37:30 GMT

I am pretty sure it is JSON being returned since

1. I have ran this script 20+ times just fine when there were less records.

2. I can take some of the layers out and it works fine. It crashes between 33,517 and 34,178 records.

3. I can also download any layer by itself with no issues so not a data issue.

This does have definition queries in it which I noticed split the data into different layers when publishing to AGO then combines then back together when bringing down a replica. Not sure if that matters but wanted to mention it.

I also am not sure it is a timeout issue as it does not take very long to do all but one of the layers (which is just 661 records). I can do any combination of layers 0-4 just not all of them at once. If I go into AGO and ask for a JSON file the file I get is 66 MB. Seems high since there are only 5 fields in each layer.

Thanks a lot