Latest Contributions by CharlesBailey3

Thanks Seth - so if you make a custom template and put it in that Utilities folder, should be able to modify the config parameters based on the dimensions in the print template - like say we want the legend to be in a single column on the right side of a landscape layout - adjust the data frame size and the anchor point. It does modify the frame as expected, but that's not the output from the print result - seems to be cropping it by about 15-20%. If you use a custom template based on the configuration of the stock templates, the frame is pretty close to the output...but that won't work for us. But, I think there's enough merit for users to be able to see an accurate extent of what they are about to print - especially since it takes so long to generate the print image... that this is worth spending some time to try and figure it out. cob ... View more

I was able to use the Utilities' Printing Tools on our server instead of creating a custom export task out of desktop. The templates it's pulling from are in Program Files->ArcGIS->Server->Templates->ExportWebMapTemplates. This worked similarly to the arcgisonline service for me when no other print services published from desktop would work at all. Same problems as listed above. But the problem I'm having is in adjusting the layout frame to reflect changes in my print templates - I'm sure the dimensions are the same as what's in the print layout template, but it prints a different extent than what is shown in the layout, which makes me wonder if the scale is correct. The template data frames are all in WGS84 web mercator aux sphere - would that make a difference? Thanks, cob ... View more

Hi Aravind - I tried this several times, and the result of running the model does not show any output layers, only inputs. It does actually work in the desktop and creates an output but it is not showing up in the results. When I try to run it in the GP widget, there is no error but the output is empty box. Just running the tool in desktop does produce an output entry in the results, this only happens when I run a model. What am I doing wrong? Thanks, cob PS another issue - the data needs to be reprojected in order for the area to be accurate - so my model had a project tool and the output went to the AddGeoFields tool. This worked in the desktop but like I said no Output in the results window. Thx for your help - cob ... View more

OK I'll try it and let you know. Thanks a bunch Aravind! cob ... View more

There are all of those parameters listed in the second error message (the one copied and pasted) but the only ones I was selecting were 'area' and 'perimeter length'. After the first error message (attached png) I changed the selected parameter to 'area_geodesic' and got the second error message. All I did to set it up was run the tool in desktop on a dataset similar to the feature service (it would not run on the actual service in the map, failed with error) which was basically a local copy of the service projected to Albers so it would let me select 'area' and 'perimeter length' in the checklist. I then shared the results from desktop as a service by connecting to our arcgis server, and put the url from this published service into the GP widget config dialog. I actually did this before the service was shared to AGOL but it didn't make any difference which method I used. I think it actually worked one time before I shared it to AGOL but the data was coming from a version copied to our server instead of the AGOL feature service - at least I think that's where it was coming from. At that time it created a temporary layer as an operational layer in the layer list, but as I said it wasn't operating on the data our users will be editing. The whole point is to be able to update area calculations after the users edit - like cutting polygons, etc. Did the model builder method you describe allow you to add fields and calculate geometry for a selected feature service in the app? Thanks, cob ... View more

Looking at my reply I should have mentioned the first error message is the attached image, which occurred when I requested the area field be added. I noticed when I ran the tool in desktop that when I selected the local copy of our AGOL feature service to run the tool on, it would not allow the selection or area or perimeter length even though the data is in WGS84 Web mercator auxiliary sphere which is a projected CS, correct? So that's why I requested area-geodesic in the second attempt even though I didn't think it made any sense. Have you actually been able to get this to work (i.e. add and calculate fields) for a feature service in AGOL? Thanks very much, cob ... View more

Hi Aravind, thanks for the reply. When I changed the message to info in the arcserver, here's what I got: So I changed the desired geometry field to add to 'area_geodesic' and then got this message: Submitted. Executing... Executing (Add Geometry Attributes): AddGeometryAttributes "Feature Set" AREA_GEODESIC FEET_US ACRES PROJCS['USA_Contiguous_Albers_Equal_Area_Conic_USGS_version',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Albers'],PARAMETER['False_Easting',0.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-96.0],PARAMETER['Standard_Parallel_1',29.5],PARAMETER['Standard_Parallel_2',45.5],PARAMETER['Latitude_Of_Origin',23.0],UNIT['Meter',1.0]] Start Time: Wed Dec 30 11:49:05 2015 Executing (Add Geometry Attributes): AddGeometryAttributes "Feature Set" AREA_GEODESIC FEET_US ACRES PROJCS['USA_Contiguous_Albers_Equal_Area_Conic_USGS_version',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Albers'],PARAMETER['False_Easting',0.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-96.0],PARAMETER['Standard_Parallel_1',29.5],PARAMETER['Standard_Parallel_2',45.5],PARAMETER['Latitude_Of_Origin',23.0],UNIT['Meter',1.0]] Start Time: Wed Dec 30 11:49:06 2015 Running script AddGeometryAttributes... Completed script AddGeometryAttributes... Succeeded at Wed Dec 30 11:49:06 2015 (Elapsed Time: 0.21 seconds) Succeeded at Wed Dec 30 11:49:06 2015 (Elapsed Time: 0.24 seconds) Failed. Could not service request. As far as the layer list in the widget dialog I did exactly what you described in the desktop scenario. In the widget config I selected 'user defined' input instead of choice list or draw tool. When choice list is selected the tool operates on the data that is copied to the server when the service is published, which is no use to us. I want to try your model method but I don't quite understand about the static layer that the tool operates on - isn't that why you set the input parameters in the model? If necessary it would be ok to have a pre-set layer to operate on but it needs to be one of our feature services in AGOL - and I'm not quite sure how to set that up - with the URL? I already tried to set a constant value URL in the widget pointing to one of our services but that didn't work either gave a similar long winded error like it succeeded but then failed at the end. Can you tell anything about what is going on from these messages? Thanks again, cob ... View more

Got it working, hooray! At first it wouldn't hold the setting in AGO assistant, then it stopped tracking, and I removed the layer from all maps and created another tracking layer based on it, put it in a new map and saved the layer, then the map. It still feels kinda shaky but we will see. I never would have figured this out in a hundred years without your help...thanks! ... View more

I think I'm getting close with this, Leah. I have the query working in Arcmap using the hosted feature service, but I can't get the AGO-assistant to accept the json for the query. I guess the syntax is a little different; I tried several variations to no avail. Can you send me the exact query syntax that worked for you in AGOL? Thanks for your help, time and patience...cob ... View more

Well, it's just a feature service created in AGOL based on the location tracking template from ESRI. Is the info I need contained in the rest from the template file or from the one I created based on it? If it's ESRI's file is should be easy to come up with a boilerplate because most are using that template to create the tracking layer and we want to do the same thing (plot current location of collector). I'm sorry, it's likely I'm not following you too well - my understanding of database infrastructure is limited. Thanks much, cob ... View more

Thank you Leah. I see where the query is, but not sure how to reference the data table in the query i.e. the db_193 stuff - is this information in here?   "id": "Aerial_Tracking_5587",   "layerType": "ArcGISFeatureLayer",   "url": "http://services2.arcgis.com/iXA1dC6ldRMKRwra/arcgis/rest/services/Aerial_Tracking/FeatureServer/0",   "visibility": true,   "opacity": 1,   "title": "Aerial Tracking",   "itemId": "507623ea30c341ecb26b3652df53bd1a",   "layerDefinition": {   "definitionExpression": "Accuracy < 25" Thanks! cob ... View more

Could you elaborate on this a bit more? Can you access the json from the layer properties in AGOL? And what does the query look like? Thanks, cob ... View more