|
POST
|
At this time, as of ArcGIS Pro 2.6, there is not a user interface to allow a custom tool to show the undo toggle. We maintain a hardcoded list of system tools which have been tested to ensure the complete operation can be registered with an edit session and cleanly undone using undo/redo/save/discard buttons. Since there is no guarantee that a custom tool meets the same requirements (your code or model can literally do anything) we haven't made it possible for a custom tool to expose the Enable Undo feature. I can provide an unsupported and "use at your own risk" workaround for your specific tool and machine which you can give a try. 1. Find the file C:\Program Files\ArcGIS\Pro\Resources\ArcToolBox\Toolboxes\editsession.txt and edit in a text editor 2. Add a new line at the bottom with <yourtoolboxalias>.<yourtoolname> 3. Save and close the file. 4. Save and close Pro 5. Reopen Pro and open the tool to see the Undo toggle at the bottom next to the Run button. here is the format your toolbox.tool entry should take: (my toolbox alias is LASiteSelection, and the model name is Model1)
... View more
10-14-2020
01:43 PM
|
2
|
6
|
7317
|
|
POST
|
Thomas Zuberbuehler a software bug makes the shortcut not work in the 2.6.x series. The bug has been resolved in Pro 2.7 which will be available later this year.
... View more
10-12-2020
11:45 AM
|
0
|
0
|
697
|
|
POST
|
Daniel Cardenas The shortcut has been re-added to the Pro 2.7 alpha/early adopter snapshot. Thank you for reporting the problem.
... View more
09-23-2020
11:52 PM
|
2
|
1
|
2512
|
|
POST
|
Angela Deegan please zip the file gdb and email to [email protected]. Thanks!
... View more
09-16-2020
03:29 PM
|
0
|
1
|
2512
|
|
POST
|
Angela Deegan yes please try to make a file gdb copy. When you have the file gdb copy you can also check if the same problematic behavior occurs with file gdb input to Table To Table.
... View more
09-16-2020
02:00 PM
|
0
|
3
|
2512
|
|
POST
|
Angela Deegan I just tested using Table To Table with an input feature class (from file gdb) which has an assortment of field types. The table export completed successfully for both file gdb output as well as csv. Can you share the feature class where you are seeing this problem?
... View more
09-16-2020
12:51 PM
|
0
|
5
|
2512
|
|
POST
|
I just tested exporting a simple integer raster with several field types to an output csv using Table To Table in ArcGIS Pro 2.6.1. It completed successfully and the csv has the fields and values I expect. Can you share the raster you are having this issue with?
... View more
09-16-2020
12:49 PM
|
0
|
0
|
2484
|
|
POST
|
Wilfred Darr you appear to have all the features selected so all of them should be calculated. Would you be able to upload the feature class in question for me to debug? What software version are you using? Just for some sanity, I ran Calculate Geometry using a local file gdb World Countries feature class, using similar parameters to what you showed, and it completed successfully in 3 seconds.
... View more
09-16-2020
10:35 AM
|
1
|
1
|
17083
|
|
POST
|
Geoprocessing uses a default/best transformation when on-the-fly reprojecting datasets between different datums. The only place we have the auto-selection of this transformation visible is from the Project tool. So I suggest you can use this workaround/ Lets call your Append input Data_A, and your append target Data_B. Open the Project (Data Management) tool, select Data_A as the Input Dataset. If Data_B is in the map, for the Output Coordinate System parameter you just need to select Data_B from the layer choicelist. If it's not in the map, click the button to select a coordinate system, use the button to import a coordinate system, then in the dataset browser find and select Data_B. Back in the Project tool, the default Geographic Transformation between the two datums is populated.
... View more
09-16-2020
10:18 AM
|
1
|
1
|
2629
|
|
POST
|
Daniel Cardenas We are tracking this regression in 2.6 -- the shortcut will be added back to 2.7 at least, and we may be able to include in a 2.6.x patch depending what we find is the problem.
... View more
09-10-2020
01:25 AM
|
1
|
3
|
2512
|
|
POST
|
Chris Lope Can you clarify if this is a typo My entire project file is only like 46Mb. If your project file (the actual .aprx file in your project folder) is 46mb there is something going on, that's actually a huge project file. My aprx with many maps, layers, layouts, etc are usually under 1mb, sometimes only 100kb. I'm guessing this was a typo, maybe you mean the project folder is 46mb, or maybe the aprx is 46kb? If your aprx is 46mb it is likely your project file has become inflated with storage of something (map graphics? huge geoprocessing history?), which might explain performance problems.
... View more
08-30-2020
09:24 AM
|
3
|
1
|
5440
|
|
POST
|
For each address there is more than 1 surveyresponse for that address. Looks like perhaps 5 (1070-1065) are matched multiple times. Hover over that warning message that shows 1070 records at the bottom of the attribute table to see information about the 1:m join. The 1:m join results in duplication in the output of Features To Points.
... View more
08-27-2020
10:59 AM
|
1
|
1
|
4134
|
|
POST
|
When you extract the package, the item that gets added to history for rerunning is called a geoprocessing task - it contains all the parameter settings and data pointers that you used when you previously ran the tool. The raw toolbox containing the original model is included in the package as well, as it is the tool that the task calls during execution. You can get to the original toolbox and model within the extracted package if you want to make modifications. We don't easily expose the underlying model, as it is needed in the original condition for the task to be able to successfully run, and that is the purpose of the geoprocessing package, to give someone a geoprocessing tool that they can rerun with the same or their own data. Yellow highlight - the geoprocessing task; Blue circle - the original toolbox and model. The Model1 folder is the folder I used for the Output Folder parameter of Extract Package.
... View more
08-20-2020
02:00 PM
|
1
|
0
|
1617
|
|
POST
|
Dan Patterson is right, you need to use the default selection for the fields, longitude should be the X field and latitude the Y field. I did some quick data entry for the first and last record in your pictured table, with the settings that match your pictured XY Table To Points execution and it displayed both points in central CA. This is using ArcGIS Pro 2.6.
... View more
08-17-2020
11:34 PM
|
0
|
10
|
18026
|
|
POST
|
First, make sure you are opening the tool under the Spatial Statistics toolbox. There is a big-data processing tool by a similar name under the GeoAnalytics Desktop toolbox which does not allow Explanatory Training Rasters. Then can you provide a screenshot of the tool? I can see the parameter in the circled location.
... View more
07-11-2020
10:02 AM
|
1
|
1
|
907
|
| 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 |
Online
|
| Date Last Visited |
58m ago
|