You are viewing limited content. For full access, please sign in.

Question

Question

Location Services - ESRI Rest Service

Laserfiche
Updated September 10
asked on July 25 • Show version history

I watched Fichebait's really well done video demoing the location services in Laserfiche.

https://www.youtube.com/watch?v=2cu8yL3fk28&ab_channel=FICHEBAIT

I was curious if anyone has enabled the location services for an ESRI rest service and would be willing to share their experience or screenshots

 

3 0

Replies

replied on August 19

@████████@████████

I hope you guys don't mind me addressing you directly, but we've hit some roadblocks with this process that I think only Laserfiche can answer.

 

We got an error regarding storing geocoding results. The reverse geocoding error is because my account is not set up to receive reverse geocoding results. It's my organization's policy. The solution is to update the authorization code with "forstorage": false, but I don't think that's an option in Laserfiche. How do I "override this"?

Also, with just a secret client and client ID it is still requiring sign in authorization.  There is nowhere in location services to save the user token that is also generated, so how do we avoid having to sign-in?

 

Reverse Geocoding.png
Sign-In.png
Reverse Geocoding.png (39.69 KB)
Download
Sign-In.png (174.34 KB)
Download
0 0
View 1 previous reply
replied on August 19

It's been a while, but I can take a stab. For the first part, the result of the geolocation request is going to be stored in Laserfiche, so ESRI requires us to pass that as a parameter. They wouldn't authorize an integration that stored the data without indicating that in the request. Is your organization's policy that you are not permitted to store reverse geocoding results?

I'll have to pass the question about the user token on to the team. It's possible they've updated their authentication flow recently.

0 0
replied on August 20

Hi Brian, Thanks for getting back in touch. Yes for my account setup it is our organization's policy that we are not permitted to store geocoding results. I will double check that, but I'm 85% sure that is the case.  Let me ask for clarification.

 

Please keep me posted on any other info

0 0
replied on August 29

ESRI requires users to authenticate, the API key doesn't remove that. I would expect it to behave similarly to using ESRI directly, where the login should be valid for a certain amount of time before the user is asked to authenticate. That's all handled on the ESRI side though, so if you have strict settings (like a short timeout) that could be the cause.

0 0
replied on September 10

@████████ Hi Brian,

Sorry for such a delayed response. This option is looking like a no go for us. I think our AGOL environment is too strict to access it through Location Services, but I appreciate you following up

0 0
replied on August 19

It's been a while, but I can take a stab. For the first part, the result of the geolocation request is going to be stored in Laserfiche, so ESRI requires us to pass that as a parameter. They wouldn't authorize an integration that stored the data without indicating that in the request. Is your organization's policy that you are not permitted to store reverse geocoding results?

I'll have to pass the question about the user token on to the team. It's possible they've updated their authentication flow recently.

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...