|
IDEA
|
While this doesn't fully accomplish the idea, it may help improve your experience: ArcMap-style toolbar for ArcGIS Pro
... View more
12-05-2017
10:41 PM
|
4
|
0
|
7924
|
|
IDEA
|
While it isn't a full "classic view" give this customized quick access toolbar for Pro a try: ArcMap-Style Toolbar for ArcGIS Pro
... View more
12-05-2017
10:39 PM
|
2
|
0
|
7248
|
|
POST
|
Hi Rupert, thanks for your comment. I'd like to ask further questions and continue this discussion. I appreciate you sharing your experiences with ArcGIS Pro. First, you stated Rupert Gonzalez wrote: Pro is not multi-threaded. At best it can run a single background geoprocessing thread without locking up the GUI. This is actually one of the reasons that Pro IS multi-threaded: it's ability to run geoprocessing in a dedicated thread so that other work can be done in the app while a tool is running. While geoprocessing is running you can add and explore map data, set and change symbology or labeling, create map layouts, build a geoprocessing model, work with raster functions, publish content to ArcGIS Online or your Enterprise, and hundreds of other things. I think what you're really discussing is that geoprocessing tools cannot run using parallel processing - using multiple cores or processes to break up a task into multiple smaller jobs. At the 2.0 release, ArcGIS Pro has more than 50 Desktop tools that leverage distributed processing to use multiple cores or spawn multiple processes to do parallel processing. The tools range from foundational vector proximity and overlay tools like Buffer, Clip, and Intersect, to raster analysis tools like Viewshed, Zonal Statistics, and Weighted Overlay, and even geostatistical interpolation tools like Empirical Bayesian Kriging. These tools, and many others, leverage the Parallel Processing Factor environment to control their distributed processing. Maybe the tools that you use most cannot be set to run in parallel, if you would describe your workflows it will help us on the development team to prioritize the tools that we rewrite as parallel. I would also like to point out that the new ArcGIS Enterprise GeoAnalytics capability is available in Pro. GeoAnalytics performs distributed space-time analysis against big data using a server cluster and Spark. This is an incredible new capability of the ArcGIS platform that is closely integrated in Pro, and it's as easy to run GeoAnalytics as another Desktop geoprocessing tool. Here is a demonstration of that. To summarize this point, more tools' algorithms are being rewritten each release to support parallel processing, so you will see this list continue to grow. The same can be said for leveraging GPU for processing, as has been done for specific Spatial Analyst tools. Second, you stated There are new packages that can do in two or three seconds what Pro takes hours. If you have examples or some scenario that matches this description, I would be very interested to work with you so I can pass it on to our developers for improvement. Thanks again for sharing. ~Drew, Esri Geoprocessing development team
... View more
06-05-2017
03:47 PM
|
1
|
1
|
2359
|
|
POST
|
If anyone continues to have problems with crashes in Pro, please try this workaround. Workaround: installed package crashing Pro 1.4.1 Note that the issue described in this workaround, and the original problem with the system toolboxes not loading, have been resolved in Pro 2.0 which is coming out soon. Thanks, Drew
... View more
06-01-2017
11:28 AM
|
0
|
1
|
1013
|
|
POST
|
Please try the workaround described at https://community.esri.com/message/690550-workaround-installed-package-crashing-pro-141
... View more
06-01-2017
11:27 AM
|
0
|
0
|
1798
|
|
POST
|
I haven't seen issues with the GPU cause geoprocessing to fail to load before, that is an interesting theory. If anyone is still having the problem, can they try to delete any files from the folder C:\Users\{yourusername}\AppData\Local\ESRI\Local Caches then restart Pro to see if it is able to load the system tools? Restarting Pro should generate two files that start with g* in the above directory, one ~50kb and one ~400kb. If it is still failing to load the system tools, please try to execute a simple arcpy command from the Python window in Pro, and see if the method fails - something simple like arcpy.GetInstallInfo(). If this fails, there is a serious problem with the Python environment, and this knowledge will help with further troubleshooting.
... View more
03-31-2017
01:30 PM
|
1
|
2
|
1798
|
|
POST
|
Hello all, You should absolutely not need to uninstall all Esri or Python-related software on your machine - this is not by design and I'm sorry to hear you're experiencing it. One thing that can cause problems with the geoprocessing cache is if you have a PYTHONPATH system environment variable set to a non-Pro Python installation. This was the cause of the crashes described here. ArcGIS Desktop and Server since 10.2 hasn't required the use of the PYTHONPATH system variable, so if you are still using it I suggest to clean it up. Drew
... View more
03-30-2017
03:22 PM
|
0
|
4
|
2111
|
|
POST
|
This issue was caused by the PYTHONPATH environmental variable pointing to an ArcGIS Desktop 10.3 Python folder. These PYTHONPATH variables are no longer needed since Desktop 10.0, and can be deleted. Removing the variable value caused the crashing to stop for Terry. In the next release of Pro the crash has been addressed even if the PYTHONPATH variable still exists.
... View more
03-23-2017
02:37 PM
|
3
|
2
|
3971
|
|
POST
|
Please contact technical support with this issue. It could be a problem with the Python installation in Pro, or numerous other things. You can try to run a simple arcpy command in the Pro Python window to see if Python is OK. For example arcpy.GetInstallInfo() Tech support will be able to guide you through and likely find a workaround. Thanks -Drew
... View more
03-09-2017
01:23 PM
|
2
|
0
|
3971
|
|
POST
|
Hello, Have you reported the issue to technical support? If so, can you let me know the BUG ID? That would be the very best way to get the issue into the system so it can be fixed in a next release. Thanks, Drew
... View more
09-22-2016
12:19 PM
|
0
|
0
|
682
|
|
POST
|
Interactive line profiling is not yet available in ArcGIS Pro, it will be added in a future release. Around the 1.2-1.3 time frame.
... View more
08-31-2015
02:19 PM
|
1
|
7
|
4086
|
|
POST
|
You cannot set this option specifically for geoprocessing. However you can set a mapping option so that newly added layers are not visible (turned off in the Contents pane). This applied to geoprocessing as well. Make newly added layers visible setting
... View more
08-31-2015
02:18 PM
|
1
|
1
|
1286
|
|
POST
|
Here is a hint: Sneak peek of animation flight path test view in @ArcGISPro next release.
... View more
08-31-2015
02:12 PM
|
0
|
1
|
2392
|
|
POST
|
Service area maps are cool! Generate Service Areas is a ready-to-use service tool accessed from logistics.arcgis.com. The tool is using network data hosted by Esri on arcgis.com. You can learn more about these services here, ArcGIS Network Analysis services.
... View more
08-31-2015
12:36 PM
|
0
|
0
|
663
|
|
POST
|
Hello, The ability to export from ModelBuilder to a Python script was removed from ArcGIS Pro 1.1 because it did not match user expectations to provide a one-to-one export of your model to Python. The scripts generated by exported models were missing nested sub-models, and did not include iterators, feedback loops, and in-line variable substitution. Models with these components would require major changes that most people who use Export are not able to make themselves. There is currently no plan to add this capability back into ArcGIS Pro. ModelBuilder export to Python was often used by those who wanted to learn the Python syntax for a geoprocessing tool, or who wanted a Python script that could execute their existing workflow of geoprocessing tools. Others wanted a Python script so the workflow could be run through Windows Task Scheduler. You can use these alternatives to accomplish these goals: Start by building and saving a model, then create a new Python script file (which is just a text file with .py extension), then using a text editor or Python IDE add lines to the new script to import arcpy, import the toolbox containing your model, and finally run the model. Now when you run the Python script (double click the .py file from Windows explorer, or execute it from Task Scheduler) it is actually running your model. import arcpy arcpy.ImportToolbox(r"c:\pathtotbx\Toolbox.tbx", "mytools") arcpy.MyModel_mytools(r"c:\modelinputs\Data.gdb\InputFeatures") In ArcGIS Pro you can copy the Python syntax for any geoprocessing tool you have run. Go to Project>Geoprocessing History, right-click any tool, and select Copy Python Command to copy the exact Python syntax needed to run the geoprocessing tool with the same parameter settings previously used.
... View more
08-13-2015
01:06 PM
|
5
|
0
|
5092
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 03-22-2024 09:27 AM | |
| 2 | 03-08-2024 01:56 PM | |
| 3 | 02-21-2024 11:58 AM | |
| 1 | 05-09-2023 02:24 PM | |
| 3 | 02-27-2023 05:23 PM |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|