|
POST
|
Great to hear you got this thing running. I don't know, I would make sure you validate the model before you re-run it. Your model looks like it should run correctly. You may want to try "turning it off and turning it on again" -- ie restart Pro. Often that fixes things for me when things do not run as they should!
... View more
11-29-2021
02:31 PM
|
0
|
0
|
2419
|
|
POST
|
The thing in percents is a model variable, not a default thing I think you think it is. I don't see a %Value% variable in your model anywhere. This won't work because there is no variable to substitute so it will use the text "%Value%" and %'s aren't allowed for items in the geodatabase. %Name (2)%_tbl may work for the output to your zonal statistics as table - though you want to connect the variable Name (2) to the Zonal Statistics As Table tool as a precondition to make sure the Parse Path runs first.
... View more
11-29-2021
01:03 PM
|
0
|
4
|
11488
|
|
POST
|
Float rasters do not support raster tables, because they would have millions of records and wouldn't be that useful. If you integerized the data you could build a raster attribute table, but I don't think that is what you want. You want to make bunch of rasters and animate them right? I'd start here. ArcGIS Pro Help: Animation Basics
... View more
11-29-2021
12:56 PM
|
0
|
0
|
2480
|
|
POST
|
I checked this, in Pro 2.8. It looks like you have an Esri Grid (the OID tipped me off); the raster table is an INFO table. It appears the Add Field button does not work with Esri Grid tables. Funny, because you can edit the INFO table contents! If you convert the raster to .tif (I recommend this) or FGDBR you can add a field from the attribute view. However (interestingly) the Add Field tool works fine to add fields to an Esri Grid INFO table.
... View more
11-29-2021
12:28 PM
|
0
|
3
|
9427
|
|
POST
|
Is this ArcMap? Sounds to me like a good time to migrate to Pro so you can assign extension licenses more flexibly from named users!
... View more
11-29-2021
12:18 PM
|
0
|
2
|
3103
|
|
POST
|
Note if you use Pro, you don't need to iterate the polygons, you can just iterate on the rasters in a single model. The ModelBuilder workflow I showed above processes each polygon one at a time so it would work in ArcMap. As for Zonal Statistics As Table processing overlapping features, read the fine manual. At least it is advertised that way - but I always trust, but verify! If the Input raster or feature zone data (in_zone_data in Python) has overlapping features, the zonal analysis will be performed for each individual feature.
... View more
11-29-2021
11:51 AM
|
0
|
6
|
11496
|
|
POST
|
If you aren't adding features, just updating attributes, I agree that Spatial Join followed by Add Join and Calculate Field is what you want to do. If you are adding new valves you want to use Append with NO_TEST and map your data across using the field map. If it is a mix you may want to do a select by location to find the ones that are new and the ones that are existing and handle them differently. If this is a process you will do again, this may be a good job for ModelBuilder (though note the field maps you edit inside MB are 'hard coded' and get reset when you connect inputs, so it will only work if the input and output datasets do not change). I highly suggest working on copies as you develop this workflow -- a lot of things could go wrong!
... View more
11-29-2021
11:48 AM
|
1
|
1
|
2388
|
|
POST
|
Just to prove it can be done, here is an example I worked up for the good of the thread. (The Calculate Value tool in the main model was needed because the iterator generates "fieldname #" for the field name on each iteration, I cleaned it up with the Calculate Value expression %Polygon ID field%[-2:], output data type Field.)
... View more
11-28-2021
01:32 PM
|
0
|
8
|
11525
|
|
POST
|
1. You need to do the zonal statistics in the submodel. This example in the help (this is Pro but it applies to ArcMap too) shows this, the processing has to happen in the "inner loop", then each inner iteration set of results can be passed back up. You need to be careful to name your outputs uniquely using model variables so each zonalstats output table doesn't get overwritten, e.g. %shedname%_%rastername%_tbl. It gets really complicated fast which is why we often use Python for complex iterations like this. 2. There are tools to process overlapping polygons in ArcMap available! Here are two toolboxes to check out. Spatial Analyst Supplemental Tools NAWQA Area-Characterization Toolbox 3. You said you don't have a Pro license. This is not true, although you may not have an install set up, but legally if you are licensed for ArcMap you are also licensed for Pro. If you don't have a site administrator to help you with this, contact Esri customer service and they can set you up with a license. Hope this helps!
... View more
11-28-2021
10:33 AM
|
0
|
9
|
11529
|
|
POST
|
Industry common practice is to go through Illustrator (ie distill the pdf) if you need to do spot color processing of your graphics. If you plan to do a lot of prepress you may want to look into ArcGIS Maps for Adobe Creative Cloud.
... View more
11-25-2021
12:39 PM
|
0
|
0
|
4058
|
|
POST
|
@SoratoSouza_e_Silva wrote: Hi, I'm having trouble converting this tool's expression to Python 3, could someone help me? arcpy.CalculateField_management("selecionado_View", "selecionado_" + Safra + ".SELECIONADO", "[selecionado_" + Safra + ".SELECAO] + [selecionado_" + Safra2 + ".SELECAO]", "VB", "") I'm not sure what this dot means What the dot means, from the help for Add Join: In the resulting input table, fields will be prefixed with the input's name and a period (.), and all fields from the join table will be prefixed with the join table name and a period as the default. Here's a crack at a Python 3 conversion. I second the suggestion in this thread that playing around with the Calculate Field tool interactively would help you learn some of the ins and outs of this, especially if you try Copy as Python command after filling out the tool dialog. A key thing to keep in mind is the python string should be directly interpretable as a Python expression (with the exception of field names surrounded by ! characters) and data types are not converted for you as in VB. # I am assuming Safra, Safra2 are Python variables of type string.
tbl = "selecionado_" + Safra # ex. selecionado_foo
tbl2 = "selecionado_" + Safra2 # ex. selecionado_foo2
# expr below becomes:
# "!selecionado_foo.SELECAO! + !selecionado_foo2.SELECAO!"
expr = "!{}.SELECAO! + !{}.SELECAO!".format(tbl, tbl2)
arcpy.CalculateField_management("selecionado_View",
tbl + ".SELECIONADO", expr, "PYTHON")
... View more
11-24-2021
12:13 PM
|
1
|
1
|
4014
|
|
IDEA
|
If my code block is non trivial, I copy it out to an IDE to edit it and paste it back in. It is just too easy for me to make spelling and indentation errors in that widget.
... View more
11-23-2021
09:12 PM
|
0
|
0
|
1392
|
|
POST
|
The issue you may be running into is that VB doesn't care about data type, if you throw a string function at it, it will use a string rep of the value. For example, you can add "1" and "1" and get 2. In Python you need to convert data types yourself, so, assuming your PLANTIO is a date field, you may be able to get what you want like this: expr = 'float(' & str(anuAtual) & ') - float(time.strftime(!PLANTIO!,"%Y"))'
# at runtime, expr will be something like:
# float(1999) - float(time.strftime(!PLANTIO!,"%Y"))
arcpy.CalculateField_management("temp_informe_Layer", "EST_SUBREP",
expr, "PYTHON") More on handling dates in Calculate Field in the help!
... View more
11-23-2021
08:56 PM
|
3
|
2
|
1309
|
|
POST
|
To apply symbology from a .lyrx to either a vector or raster outputs in ModelBuilder: 1. Make the output a model parameter and apply a lyrx to its symbology property in the Model Properties dialog. This usually works best when the model is run as a tool. 2. Create a layer in the model with Make Feature Layer or Make Raster Layer, and run the Apply Symbology to Layer tool, and then add to display. Hope this helps!
... View more
11-23-2021
08:39 PM
|
1
|
1
|
1683
|
|
POST
|
Have you considered building a geodatabase topology and setting a rule to tag disconnected nodes (dangles)? Or (@DanPatterson suggestion) running Feature Vertices to Points, asking for Start and End points, then Near the points to themselves and finding all points with NEAR_DIST > 0?
... View more
11-23-2021
08:29 PM
|
0
|
0
|
3089
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-11-2021 01:26 PM | |
| 5 | 12-10-2021 04:58 PM | |
| 1 | 02-27-2017 09:30 AM | |
| 2 | 12-04-2023 01:05 PM | |
| 1 | 04-12-2016 10:17 AM |
| Online Status |
Offline
|
| Date Last Visited |
06-19-2024
12:10 AM
|