Latest Contributions by ShitijMehta

Check this blog for considerations when exporting a model to a Python script. ... View more

Can you share your model/script tool? ... View more

Try running your script tool with all the input values once and save the model. Now connect the output of the script tool to the next tool. Make sure that the feature type that your script tool is creating is an accepted as a valid input type for the next tool. Remove all the previously added input values from your script tool parameters to make the tool a generic tool once again. ... View more

Hello abowron, Hello jeremyjurick, Can any one of you please share a subset of your data? This would make it easy for us to find the problem and suggest a solution. Thanks! ... View more

Hello All, Our developers are looking into the joined fields with Null values problem. We will inform you in a day or two. ... View more

This is what you can try: Use the iterator and connect the output feature class (green oval) as input to Make Feature Layer tool. Use Make feature layer tool to make a selection based on your sql query. Connect the output to the Get Count tool. Get Count tool (see help on this tool) - if there are any selected features the output of get count tool is 1 and the tool connected to it downstream will run. if no features are selected, and the count is 0, the output of get count will be 0 and the downstream will not run. Copy features in the end with output of make feature layer tool as input to the tool and output of the get count as the precondition to the tool. Hope this works for you. ... View more

Try the attached script tool to add custom message in ModelBuilder. ... View more

Have you created a model for your workflow? Can you share it? If not the toolbox an image? For the second selection in Select Layer By Location what selection type are you using? New Selection/Subset Selection...? ... View more

You layer should retain the calculated value as the calculate field only modifies the input and does not create a new output. But I do not know what going on. Try this: You can use the Copy tool in the end or after the Calculate Field tool. Connect your input feature classes (blue oval you are making the selection on) not the selected features in a layer and set a precondition on this copy tool to only run after the calculate field has been run. ... View more

1) Edit your model. Go to Model-->Model Properties-->Environments tab-->General and set the curreent workspace environment and the scratch workspace environment there. Hit OK Now use current workspace as %workspace% and scratch workspace as %scratchworkspace% in your input and output path respectively. 0r 2) Right click anywhere in your model and from the side menu click Create Variable. Create a variable of type workspace. You can rename the variable to anything say: Input Workspace. Provide the variable a workspace value and use it in other tools as %Input Workspace%. **Its always recommended that you set the environments at the ArcMap/application level if all your models are using the same workspace. ---------------------------------------- Iterate though a list of workspaces or the feature classes and tables inside the workspaces? What do you want to do by iterating over workspaces? ... View more

In the ModelBuilder doc editor the general information: Abstract, keywords, author and constraints remain internal and can be viewed by opening the doc editor for the model. The remaining info: summary, illustrations, usage tips.... can be previewed and checked from the help page. To see the help page right click the model and click Help. ... View more

If you are working with 9.3 or 9.3.1 try using the variable of type list or series. List of inputs will all run together and create a list of individual outputs. The individual outputs will have to use %i% in the output name as in-line variable substitution. Download this example and read help: http://resources.esri.com/geoprocessing/index.cfm?fa=codeGalleryDetails&scriptID=15728 Read how to use lists, series and inline variable substitution: http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Iteration_using_Lists http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Iteration_using_Series http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=In-line_variable_substitution Hope it helps. ... View more

If you are new to ModelBuilder I would strongly suggest reading the online help for it. if you are using 9.3 or 9.3.1 http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Creating_a_simple_model If you are using 10 prerelease http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/What_is_ModelBuilder/002w00000001000000/ You need two things: 1) Model Parameter which lets the user input values from model tool dialog. To create a model parameter: In MB create variables (8 if you want 😎 and select them, right click and check Make Model Parameter. A letter P appears besides the variable indicating that it is now a model parameter. Now when you double click a model from Catalog window the model will open with a dialog and you will see the variables as input parameters, in the order you made them model parameters. You will have to read a bit to understand more about changing model parameter order and data types of the variable in the model. I suggest you read the help from this link. http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Creating_stand_alone_variables/002w0000003v000000/ http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Creating_model_parameters/002w0000003z000000/ 2) Next to use the variables/ user input model parameter values you can use the variable in the model as in-line variable substitution. You might have to read some help for the first time. http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Examples_of_inline_model_variable_substitution/002w0000005w000000/ See the attached image  to understand a small example of how to use in-line variable substitution. Hope this helps. ... View more

try setting the relative path option for the script tool. right click the script tool in Arc Catalog-->Properties-->General tab--> check the relative path option. make sure your script tool points to the correct script that you are sharing along with your tool. ... View more

try making your input a layer first by using Make feature layer tool and then select layer by attribute. ... View more