Latest Contributions by BrentDavis

Often we need to edit a polygon feature and recalculate a longitude and latitude field for the centroid of the feature.  Historically, we have been doing this editing calculation within arcmap, but have been trying it out in ArcGIS pro. Unfortunately when we try and calculate the centroid x-coordinate and centroid y-coordinate for longitude and latitude in decimal degrees we are getting very large values as compared to the workflow used in arcmap.  It looks like the format is being displayed in meters. Below are the setting we are using: Here is the output of (Lat,Lon) for a test feature that was created. Any ideas on how to reproduce the calculate geometry function from arcmap? Thanks ... View more

We have scheduled four geoprocessing tools which appends collected data from four hosted feature layers on AGOL into four local database tables. The tools are scheduled every night.  Five of the six days of scheduled appends were successful, but one of the days produced an error for each of the four scheduled tools: "When running a geoprocessing tool, ArcMap returns the following error message: Error 000229: Cannot open <value>. This error message indicates the data required by the geoprocessing tool is unavailable or invalid. However, the error message can display when the data is valid and accessible if background geoprocessing is enabled." Each tool is scheduled to run at the same time. My best guess is poor internet connectivity or issues with the system health of ArcGIS online at the time the tools were scheduled. Also, on some days we are receiving 'broken data source' exclamation marks next to the hosted web layers when they are viewed as a feature layer within an ArcGIS pro project. When we close ArcGIS pro and then restart the project the broken data sources are repaired.  Does anyone have any ideas about the causes of this or better solution? We would like a more robust approach to appending data nightly from ArcGIS online. Thanks ... View more

I am trying to schedule the append geoprocessing tool with the 'Preserve Global IDs' environment variable set.  When the tool is scheduled the global IDs are not preserved.  If you look at the scheduled task calendar you can check that the 'Preserve Global ID' environment was not passed to the tool when scheduled to run. I tried a few things in order to get something to work.  The first thing was to uncheck and recheck the box next to Preserve Global IDs.  When I schedule the tool, the details of the tool history did show that 'Preserve Global IDs' environment was used, but it was still not preserving global IDs. Finally, I set up the append tool as a model in ModelBuilder. I had a feeling there was a bug in the environment hierarchy with regard to how environment variables are passed to scheduled tools. I unchecked and rechecked the box next to 'Preserve Global IDs' for the append tool within a model I had built and it did preserve the Global IDs once the model was scheduled to run. It seems what is happening is that the defaults are overriding was is set in the environment panes unless they are refreshed by unchecking and rechecking the global ID box.  Once the program detects a change in the environment pane it will pass them to the scheduled tool. ... View more