Latest Contributions by VincentLaunstorfer

The Field in ModelBuilder is a Field object and cannot be used 'as is' in an expression using the inline varaible syntax within double-quotes. To make it works, within ModelBuilder you should use the Calculate Value tool in Utilities and simply use "%Field%" expression, asking to get the Field name as a string. Then, you can use this calculated result as an inline variable. Here below is the working example. Hope this helps! ... View more

Hi, In the Imagery tab, I used the Raster Functions -> Data Management -> Mask in order to 'mask' unwanted pixels, as shown below. Although, you seem to have lots of unwanted pixel in your example. I would recommend to reclass your raster beforehand to 'group' all unwanted pixels together.  Hope this help   ... View more

Strange! It took a while for me to identify the issue. I cannot really help but I would recommend to open the *.pitemx items in either ArcGIS Desktop (ArcMap) or on another machine with another account to ensure the items resources do work. If it works, there is an issue with you login and/or ArcGIS Pro installation. ... View more

Hi Marcelo, Just found your post here and perhaps you can advise me. In ArcGIS Pro 3.2.1, I have large models in ModelBuilder with 4-5 Python scripts embedded as tools and I am looking for an efficient AWS EC2 machine to run my models (way) faster. So far, I tried an EC2 r6a.4xlarge and I am rather disappointed. A model running in 1h01 on my laptop took 1h15 on this virtual machine. It does not make sense as this r6a.4xlarge has 16 vCPU with 128 GiB vs 4 CPUs with 32 Gb. In theory, I guess I don't need GPUs but would it help to select a GPU enabled virtual machine? ... View more

Thanks Dan for the quotation "models set overwriteOutputs to False"! It helped me to understand why a model could not overwrite outputs, despite having correct Geoprocessing settings for the ArcGIS Pro application... For info, if a model embeds some custom Python tools and without explicitly setting overwriteOutputs = True, as models set overwriteOutputs to False by default, it also defaults the entire model to False (not only the python script). Good to know! ... View more

Thanks for looking at this post. The content of the expression variable is the second line of the code, as below: [["Detached", "!Detached!*!Ratio!", ""], ["Total", "!Total!*!Ratio!", ""]]  As you mentioned, the CalculateFields is expecting a Value table and here I tried to built a string. In fact, I tried to reuse the syntax provided when you export ModelBuilder to python... hence the [0] which I do not either understand its use. As for error message, on runtime, Python simply ignore the CalculateFields! As I said, using arcpy.management.CalculateField in a loop is an excellent workaround, using simple string variable (no need for Value table) ... View more

Hi, In case you get same error when opening ArcGIS Online .pitemx items on ArcGIS Pro, ensure you are logged into ArcGIS Online account. It looks silly but it now works for me. Usually, I am logged in internal portals and this prevents opening ArcGIS Online .pitemx items! Please ESRI, provide a more informative error message in this situation. In comparison, ArcGIS Desktop (ArcMap) do not display errors when opening .pitem items if not logged in. ... View more

I found a workaround... Instead of dealing with building an 'expression' string variable in a for loop to calculate all fields with CalculateFields, I am calculating fields directly in the for loop, one by one with  arcpy.management.CalculateField. It is just as good and the syntax is much easier! ... View more

Hi, In the steps you went through, you are actually updating the Default symbol of the Annotation Class... meaning you are updating the 'template'. Not the actual Annotation. In practice, if you create a new annotation using this 'template', you should get the color you selected. Conceptually, all annotations (objects if you prefer) point to Annotation Classes which come from the label classes from the feature layer you converted to Annotation. Then, you can change some properties of annotations (such as color) individually and in that case the annotation do not point to the 'template' any more. It makes annotation maintenance more difficult if many. Good practice is to keep the label classes as tidy as possible before converting to Annotation. Some background here: https://pro.arcgis.com/en/pro-app/3.0/help/mapping/text/display-geodatabase-annotation.htm Hope this help ... View more