POST
|
Hey Rebecca, did you ever solve this? I have had similar problems where I will change the name of a custom toolset I made, but the catalog window in Pro still shows the old name. I tried changing the toolset name in ArcCatalog too, and Pro still did not register the change in name. I've also occasionally had the same issue when trying to rename models I created. And actually, now that I think about it, once ArcGIS Pro would not let me change metadata in a tool I made, until I had restarted my computer and closed and re-opened ArcGIS Pro several times. So I wouldn't be surprised if there is some problem with the cache functionality in ArcGIS Pro. I haven't updated to 2.1 yet, I plan to soon, so they might have fixed the problem in 2.2, but in 2.1 I have had quite a few problems throughout the process of creating a custom toolbox, and it seems that the cache history functionality in Pro might be involved.
... View more
07-06-2018
11:43 AM
|
1
|
0
|
978
|
POST
|
Hi Jared, I assume you have already found an answer or a work-around, given that this question is from 2015, but just in case, with ArcGIS Pro 2.1.x, you can right click on a toolset and rename it.
... View more
06-29-2018
05:05 PM
|
0
|
0
|
284
|
POST
|
Update! This morning it worked! I have no idea what I did different, but here's a list of suggestions I've compiled for anyone else having trouble with metadata in models for ArcGIS Pro! Click Save after every box/section completed in the metadata Regularly save your project too If the program stops saving your metadata....try restarting Pro, restarting your computer, restarting Pro again, closing things and restarting a couple more times, etc. It might work the next day! If you are creating models to be run in the geoprocessing pane and want to create dialog explanations for each parameter input like I did, finalize all your model parameter names BEFORE creating the dialog explanations for the model steps (Side note: to create dialog explanations, Edit Metadata and then in the Item Description section, scroll down to Syntax, click the parameter name, and enter your text in "Dialog Explanation") Keep a separate external text file with all of your metadata dialog explanations etc., just in case something odd happens and you loose all your data, or in case you have to go back and change parameter names. When documenting the dialog explanations for your models, it's probably not a good idea to switch between tasks (opening and editing models, editing metadata) at the same time. Sit down and figure out what you want to write for each section in the metadata first. Take that time to open and close all your models to remember what you did, edit typos etc. THEN when you are ready to focus solely on the metadata, start filling out the metadata Check regularly to make sure that when you hit Save and the syntax box closed, that it actually DID save your edits. Cheers! Blythe
... View more
06-23-2018
11:56 AM
|
6
|
0
|
1700
|
POST
|
I wrote metadata for a couple models that I created in ArcGIS Pro, and upon finding something in the metadata I wanted to change, I went back again to edit the metadata (right clicked on model in Catalog pane > Edit Metadata). However, after making my changes and clicking "Save," my work did not save. I have tried opening and closing the metadata editor, restarting Pro, restarting my computer...nothing. Does anyone know why this is happening or how (any way, custom python scripts, whatever) I can most easily work around this bug and update my metadata? This is the latest in a long line of difficulties I have been having in saving metadata for models and script tools in ArcGIS Pro. Miscellaneous but Possibly Pertinent Information: - Earlier today I was able to create the metadata that I am trying to update. However, now I cannot even create or edit metadata for a different model within the toolbox that I am working with. -Even earlier today, I updated my ArcGIS Pro version from 2.1.2 to 2.1.3 - My models are saved in a custom toolbox that I created. Originally I created the toolbox in ArcGIS Pro, but I have been cycling through different versions of my final toolbox so I copied the toolbox (several times now) in ArcCatalog and then continued to edit the new copy in ArcGIS Pro. The tools run fine. I just have trouble creating metadata that persists. - The other week, when I was using ArcGIS Pro version 2.1.2, I discovered that changing the name of a parameter in a model deletes the metadata for that parameter (taught me to save all my model metadata in an external file), but I have not made any changes to the model that I am trying to update today. Thanks! Blythe
... View more
06-22-2018
02:28 PM
|
1
|
2
|
2229
|
POST
|
Oh yeah, I did change that. I changed it to string. Thanks!
... View more
05-30-2018
05:22 PM
|
0
|
0
|
1947
|
POST
|
Thank you! And yes, if the result is not equal to 1.0 it should fail.
... View more
05-30-2018
04:34 PM
|
0
|
2
|
589
|
POST
|
Oh thank you! That might be the thing that is still causing me problems when I try and run the tool. I'll change that now and see if that works. (Right now I am getting a generic "Unable to complete operation" error).
... View more
05-30-2018
04:04 PM
|
0
|
4
|
1947
|
POST
|
Alright so it didn't work as a Feature Set, but then when I specified the output in the script tool parameters as Feature Layer, and also specified that the derived output was obtained from the output layer, it worked! It showed the proper geometry symbol in ArcMap when I ran it and when I used the geoprocessing service in Web AppBuilder the tool did not have any issues with the geometry type either! It let me change the default symbology and everything. It still doesn't work haha, but the geometry issue is solved now This is how I edited the output parameters:
... View more
05-30-2018
04:03 PM
|
0
|
2
|
1947
|
POST
|
Oh whoops I was looking at the wrong thing. The output actually did not show a proper geometry symbol when I ran it in ArcMap.
... View more
05-30-2018
02:57 PM
|
0
|
10
|
1947
|
POST
|
Hey Jonathan! The results were added to the display in ArcMap when I ran the tool. I then changed the symbology of the results and exported the geoprocessing service. When I try and run it as a service in a web application though it doesn't work. I click the button to execute the model and the button grays out for a bit and then it goes back to normal, as if the service timed out or something. Great to know that the math module is fine. Attatched is the toolbox. Thanks! Blythe
... View more
05-30-2018
02:38 PM
|
0
|
11
|
1947
|
POST
|
I am trying to publish a geoprocessing service that takes an input file from a web application, does a custom field calculation based on user defined integer inputs, and outputs a feature service that can be viewed and exported from the web application. However, when I publish my geprocessing service and bring it into Web AppBuilder using the geoprocessing tool widget, I cannot choose the option "Add result as operational layer" and the output has the error "Can not set renderer because of unknown geometry type." This is the REST URL for my geoprocessing service: WetlandPrioritization/WetlandPrioritizationTool_Ac (GPServer), and the screen shot below show my output parameter as having no geometry type. Question 1) Does anybody know why I cannot see the geometry type? I am assuming this is the reason I cannot add my result as an operational layer. Question 2) I am assuming the error above is why the tool will not run. But I also realized that I am using the python math module in my python script....Is that a problem? Do I need to download that module somehow onto my server, or can I assume the math module will work in the gp service? My workflow for creating the Geoprocessing Service: I created a script tool with a Feature Layer as the input, and a Feature Class as a derived output. I then ran the tool in ArcMap (10.5) and published the geoprocessing service onto my organization's server (version 10.5). For Parameters in the Service Editor, I chose "Asynchronous" and "View results with map service," as I believe I can view the gp service results as a map service in addition to whatever my normal outputs are (such as an operational layer). I also specified maximum number of records returned by the server as 3000 because I have 2313 features in the input feature class that will be used by the tool. I then published the tool. I have attached the source code that my web tool is running. Thanks!
... View more
05-30-2018
12:24 PM
|
0
|
13
|
3390
|
Title | Kudos | Posted |
---|---|---|
1 | 06-22-2018 02:28 PM | |
1 | 07-06-2018 11:43 AM | |
6 | 06-23-2018 11:56 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|