POST
|
Hi Andrew - I had a similar question this morning when the ESRI service didn't work and got it answered here: https://community.esri.com/thread/180264 Check your application's config.json file and modify the value for "geometryService" to point to your own service instead of using the one by ESRI. Ruben
... View more
07-21-2016
02:22 PM
|
0
|
0
|
326
|
POST
|
Hi Robert, we already have our own ArcGIS Server. I wasn't aware that I could switch over that service to be using our server though. Thanks for the reply. I fixed the entry in the config.json file of my app and everything works fine now. Thanks for your help. Ruben
... View more
07-21-2016
12:22 PM
|
0
|
0
|
726
|
POST
|
Today, when using WAB, it loads very slowly. Firebug shows me that the request to the service mentioned in the title is the cause of this. Sometimes, it takes one minute until I get an error message back from that service, sometimes (luckily) I get the error message back faster. Here's the call that's issued by WAB: http://utility.arcgisonline.com/arcgis/rest/services/Geometry/GeometryServer/project?f=json&outSR=26912&inSR=4326&geomet… WAB is waiting for an answer from that service before the loading indicator disappears. Here's what the answer is, once it comes back after a minute: {"error":{"code":500,"message":"Error executing project","details":[]}} Then, after WAB does some more loading, it issues a second request to that same service (same parameters again) and it's another minute until I get the same, disappointing answer. Is this something only I'm experiencing? Any pointers? Because after two minutes of loading, the application seems to be working fine, is there something I can set in the application to just tell WAB not to do that call at all? Thanks. Ruben Schoenefeld Utah Dept of Transportation
... View more
07-21-2016
11:42 AM
|
0
|
2
|
2181
|
POST
|
Is it a large dataset? When I download large datasets through the OpenData API, I usually get a "Processing" answer back and I will have to reload multiple times before I actually get a valid answer. Copy and paste the OpenData API URL into your browser's address bar and load it. Do you immediately get all the data or do you get a "Processing" message? Ruben
... View more
09-10-2015
11:38 AM
|
0
|
1
|
305
|
POST
|
Hi - I'm trying to use one of our layers available as an OpenData export API in OpenLayers. At first, I was trying to use the BBOX strategy, thinking that it was the best way to filter the data for the user. OpenLayers attaches the bbox parameter to the URL in the following format: [...]_0.geojson?bbox=408089.48072144,4509936.1932796,427160.51927856,4521936.8067204 However, OpenData doesn't accept this as a bounding box and instead wants the following format: [...]_0.geojson?where=&geometry={"xmin":-15518551.2305655,"ymin":4072458.8381785434,"xmax":-9339993.360219777,"ymax":5540049.781253537,"spatialReference":{"wkid":102100,"latestWkid":3857}} Has anybody gotten the OpenLayers BBOX strategy to play nice with ESRI OpenData? The reason I even want to use the a bounding box when requesting the data is because the layer contains enough data to take a while to load, which brings up my second headache with the OpenData API. When requesting large datasets, instead of getting back any data, I'm getting back the following reply: {"status":"Processing","processing_time":0,"count":3276} It's very unpredictable however. Sometimes, when I reload the application, after loading between 30 seconds and a couple of minutes, I'm getting the whole set of data back and sometimes, I'm seeing this "Processing" answer. Is there an API parameter I can provide to OpenData that will prevent this? Thank you. Ruben
... View more
09-10-2015
11:34 AM
|
0
|
0
|
2179
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|