Tag Info

New answers tagged

0

Yes - I think the way to figure out how to do it is by setting up very simple master and sub models. The master model should do no more than take in a string from its tool dialog and then run the sub-model. The sub-model should take as one of its inputs a string and use that string to perhaps create a shapefile using the string as its name. You should be ...


0

Perhaps the validation issue is where you are editing the models from? ArcGIS gave me trouble if I edited sub-models from the Catalog, but no trouble if I edited them from inside the main model.


0

Also possible to use MERGE each output file to the last, using a feedback loop. http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Iteration_using_feedback


3

The ultimate in stupidity. All I was missing (in any of the ways I approached it) was "QUOTATION MARKS" around the expression. ie. Expression = "%Value%" if using Parse Path, or "%Name%" if not using Parse Path


0

I would imagine the problem is with the fact you named the output of FeatureClass to FeatureClass tool using the inline substitution syntax which makes no sense. Rename that to something like "output" (do not include the quotes!). Then your field calculate tool expression stays as %Name% which is the inline substitution coming from the variable Name which ...


1

I had the same problem but with rasters produced by model. After spending quite a lot of time trying to make Add to Display work I finally decided to implement arcpy script to add output raster to ArcMap data frame. I think the same can be applied in your case. My solution is derived from the one found here. So, make python script with code similar to this ...


0

I haven't really used model builder too much (usually just hack my way through a model to run some script I made), because I usually use ArcPy for stuff. But maybe I could help you go in the right direction. I would suggest to use the Add Field tool from toolbox datamanagement->Fields->Addfield. then hook the output of that up to calculate field from the ...


0

your problem is a combination of two problems 1) write the name of the fc into a field Use Feature Class "Name" from Iterate Feature Classes to Calculate Field with Model Builder 10.1 then 2) extract a small part. For the second, just use the field calculator with the python parser !Image![2:6]


1

A couple of things to test. You say it has Z values. A feature class can be Z aware but have no Z values. So first thing to test is does your point dataset actually have a number for its Z value? You mention that it is a multipoint dataset. May be its a bug in the tool (I've personally never used it), may be it only accepts single part datasets? Try ...


1

I would add a precondition going From: The "Value" coming out of the iterator To: "Make Table" (the 1st tool you run on "Final1(2)") This will make sure the value changes each time


1

There is no guarantee that a model exported to Python will run without debugging and, depending on your model's complexity, that debugging effort could be considerable. I would wrap your model into a very short Python script that consists of little more than arcpy.ImportToolbox(). For example, if you have a TestModel (without an alias) in ...


2

It looks like you need to set a temporary alias on your toolbox (or a permanent one via its Properties) as described in the Help for ImportToolbox (arcpy): If the toolbox does not have an alias, the module_name is required. When a tool is accessed through the ArcPy site package, the toolbox alias where the tool is contained is a required suffix ...


0

It appears as though I had to use the Iterate Tables rather than Iterate Files, and then it worked just fine.


1

You may need to include a Collect Values tool between the Iterate output and the next processing step (CreateFeaturesFromText). Example from ArcMap's Help Page (in a different model, so just illustrating the principle)


2

!shape.length3D! does work. I had to make sure that I selected the PYTHON_9.3 Expression type in the Calculate field Options dialog. (I'm running 10.2.)


0

ModelBuilder only allows one iterator per model. I would integrate a model within a model in order to iterate over multiple tables.


0

If I understand correctly, each of the input shapefiles consists of only one land use type. If that's the case, here's what I would suggest: Use the Merge tool three times to merge all of the A, B and C input shapefiles into three new shapefiles, each containing all polygons of a single land use type. On each of the merged shapefiles, run the Dissolve tool ...


0

You can use CreateMapSDDraft (arcpy.mapping) or Upload Service Definition (Server) http://resources.arcgis.com/en/help/main/10.1/index.html#//00540000001p000000


3

I'd try nesting the iterate part in a sub-model - as suggested in this earlier question: How to prevent running part of a model when iterator is used?


1

Found what was causing the model to use my default gdb. Just needed to check the paths of the intermediate data within the model. Some of the intermediate data had leftover paths to the default gdb. I just repathed those to the Scratch gdb that I specified in the Environment Settings and everything runs now on other's computers.


0

This can be achieved with a relatively simple model, no programming required! The model is below: I use the summary statistics tool to sum your first field and place this value in an in_memory table. Then use the get Field value tool (a model only tool) to get that value. Then a simple calculate field tool on your second field using in-line substitution (in ...


1

You can use a precondition to control if the model executes. The following model assumes your raster is an integer grid so the SOY class is an integer value. This means you can use the raster in the select by attribute tool. So get count should return 1 if SOY exists in the raster and as it is a precondition to the raster to polygon tool that part of the ...


0

I have resolved the issue so I thoughht i'd close this by sharing the answer. 1) the "null" values on all rows but the first one Thanks to Richard Fairhurst in the commenting section on the Patch tip. The patch fixed it. 2) returning the count value of points per line segment in my model, I had to: use the 'Repeat Victimsation (Geographical) tool from ...


0

From the perspective of someone using what you've created: there is no difference. Its a tool. Technically speaking a python toolbox (.pyt) is a python script but structured in a way that ArcGIS understands its a toolbox + tool. The model and script tool are something that live inside a toolbox (.tbx). The script tool references an independent python file ...


2

There is not an Iterate Fields tool in ModelBuilder. I can think of two possible workarounds: Modify the model to run as a Python script. Define a list of the fields you want to use, and define a loop to go through each one and execute the IDW/export functions. I would go with this one personally, but it would be (much) easier with some Python knowledge. ...


0

It sounds like you want to do a couple of nested loops, one for the feature classes in a workspace, and one for the features in each feature class. This is painful (but possible) to do with ModelBuilder. If you want to get your hands dirty with Python (which I definitely recommend for stuff like this), here is an example to get you started: import arcpy, ...


1

Here is the model, it uses inline substitution a described by Aaron. Note the output of the Polygon to raster tool is ..\fGBD_Scratch.gdb\ras_%Value%. Value is coming from the iterator which in this case was set to FID to hand out unique rows. So the first raster dataset would be ras_1, then ras_2, etc.


4

There are several ways to deal with naming in model builder. ArcGIS has a help section on this: A quick tour of using inline variable substitution. One slick way to quickly create unique names from an iterator is by calling the %i% or %n% system variables, which output files in the following form: file1, file2, file3, file4... The %i% system variable ...


0

I would use the Select tool and then write this expression: "Modified_date" >= CURRENT_DATE -1 It should return all your records greather than equal today minus 1 day (i.e. 24 hous), therefore yesterday at 6am. It definitely works with the Definition Query SQL as we use it in our organisation to only view our "incidents" in the last fortnight: ...


1

I'm not sure this is the answer that I was looking for (especially since the original model worked for another user), but I ended up getting it to run successfully with a bit of a work-around. I put everything after Add Join into a submodel and it worked perfectly.



Top 50 recent answers are included