Latest Contributions by curtvprice

‎12-08-2021

Please do report it (and share the NIM in this thread so it will get voted up!) This sounds like a mission critical bug. Doing this in Python is the obvious workaround. With the advantage of being able to do more parameter validation and error messages!

‎12-08-2021

ArcPro licenses are best assigned from named users unless you want to share a limited number of extension licenses among users, if that is the case I recommend sticking with concurrent for your Pro licenses. I don’t know anything about the extra licenses you are talking about

‎12-07-2021

The problem is not the model but the tools you are using (which you are not specifying) that may not support shapefiles. You may want to try running that particular tool on your input interactively to see if it works at all on your data. (Note, shapefiles do not have a Shape_Area field if you are using that.) ArcGIS Pro Help: Geoprocessing considerations for shapefile output

‎12-06-2021

Comment from the X-Ray download page (ArcGIS Online) - The X-Ray add-in for ArcCatalog will not be certified on ArcGIS Catalog 10.8 -10.8.1. We do not intend to update or certify the addin for any future releases. (In saying that, there is nothing preventing the addin from working in 10.8 or 10.8.1 and some folks are using it successfully.) Sounds like it is not supported, so if it doesn't work, you should probably try 10.7.

‎12-06-2021

The transformation warning has to do with the coordinate systems of the inputs. Some transformations between horizontal datums are simply not supported. You can probably turn this message off by turning off the geotransformations in the backstage (settings).

‎12-06-2021

I have seen this when I have an old incompatible extension installed (ie my uninstall of the old version did not include everything ArcGIS).

‎12-05-2021

Dan, nested looping is supported, but it can be tricky, and you can run afoul of ModelBuilder tool validation (and quirks). You are correct that that these nested workflows are sometimes easier to do by going to Python. Note you can call a model tool from a python script pretty easily so if you can get a good geoprocessing workflow worked out in a model you can write a fairly simple Python driver script to loop on it, and run the script from several entry points, including the command line, Jupyter notebook, script tool, or even as a python function in the Calculate Value tool. I think if @圈圈 has the exactly same looping working with the older version of software, this is definitely something to take to tech support. I have successfully done nested looping in 2.8.

‎12-05-2021

The easiest way to do this in ModelBuilder is to use the Sort tool to sort by CODE and Shape_Area and then write a python function in Calculate Field tool with a code block with a function that assigns values according to your rules as you navigate through the sorted table. Or, take what I bet is @DanPatterson's advice and do this in Python/numpy in a Calculate Value function that reads the table, sorts it and does your logic. I do not follow your logic here.

‎12-01-2021

Zap the NaN's: str(arcpy.Describe(r"%buffer fc%").Extent).replace("NaN","") Do not forget to set the Calculate Value output data type to Extent so you can connect it to the tool's parameter of type extent. This validates OK for me. No promises whether it actually gets the tool to give you the output you want though! If it needs to be WGS84, run your buffer with an output coordinate system setting of WGS84 and use that to calculate your extent. Executing (Calculate Value): CalculateValue str(arcpy.Describe(r"efillcells_poly").Extent).replace("NaN","") # Extent Start Time: Wednesday, December 1, 2021 5:29:49 PM Value = 622280.000000002 4857190 626460 4862460 Succeeded at Wednesday, December 1, 2021 5:29:50 PM (Elapsed Time: 0.03 seconds) Executing (Layer To KML): LayerToKML efillcells_poly C:\gisclass\efillcells_poly_LayerToKML.kmz 0 NO_COMPOSITE "622280.000000002 4857190 626460 4862460" 1024 96 CLAMPED_TO_GROUND Start Time: Wednesday, December 1, 2021 5:29:50 PM Succeeded at Wednesday, December 1, 2021 5:29:51 PM (Elapsed Time: 1.91 seconds)

‎12-01-2021

Two approaches to pass that extent to the tool: 1) connect the extent feature class (buffer output) to the layer to kmz tool and choose Extent environment. The tool help does say it honors the environment extent. 2) use Calculate Value to return extent object : str(arcpy.Describe(r"%buffer fc%").Extent), data type Extent and connect that extent to the layer to KMZ tool parameter Good luck!

‎12-01-2021

I have never been a big fan of packages, which work by unzipping a bunch of cruft into a users's documents folder (with the aforementioned long, nasty paths with spaces, which have a bad habit of breaking spatial analyst tools.). I would know more about if I hadn't have had problems like this whenever I have tried it. I have been more successful just making sure relative paths are set in the model tool properties and zipping the entire project folder. Even then I have had problems with hard-coded paths in my models this term working with students. I need to spend more time on this to figure out the best practices in Pro (vs ArcMap). Another tip to make model tools more portable is to make liberal use of memory (in_memory in ArcMap) (as long as data not too big) and environment based paths (%workspace%, %scratchGDB%, %scratchFolder%) so my model tools aren't as dependent on paths that may not be there.

‎12-01-2021

If you verified that a) spatial analyst is installed and b) you have a license in ArcGIS Administrator and you have checked the Spatial Analyst box then you should not get 010096 (which is specifically no spatial analyst license, not installed is a different error message). If a reinstall does not fix it, contact tech support. Esri KB article: Error: ERROR 010096: There is no Spatial Analyst license currently available or enabled

‎11-29-2021

Maybe a 2.9 bug?

‎11-29-2021

Good solution removing the space. This can happen with the Spatial Analyst tools - they often bail on names, layer names, or even paths with spaces or any special characters.

‎11-29-2021

Yes, Add Field button worked fine for me with a raster .tif table. I would make sure you don't have an edit session open. It's possible file naming is an issue, and there are so many things that can make a layer non editable and it is sometimes not easy to diagnose! Try the Add Field tool maybe you'll get a useful error message.

Online Status	Offline
Date Last Visited	‎06-19-2024 12:10 AM

My Ideas

Latest Contributions by curtvprice

Re: The iterator of main model can only be iterated once in ArcGIS Pro2.8.3

Re: Best Practice for Multiple Users and Single-Use License

Re: Calculate Area Model Builder Error

Re: X-Ray for ArcCatalog - Extension does not appear

Re: Trouble with ModelBuilder model

Re: Trouble with ModelBuilder model

Re: The iterator of main model can only be iterated once in ArcGIS Pro2.8.3

Re: ModelBuilder - automatic rename attributes in table based on shape area

Re: Model Builder Layer to KMZ Extent to Export Error

Re: Model Builder Layer to KMZ Extent to Export Error

Re: Trouble with ModelBuilder model

Re: Installing Spatial Analyst Tools ArcGIS Desktop

Re: Adding fields to Raster attribute tables

Re: 2 iterators in the same model builder

Re: Adding fields to Raster attribute tables

Re: ModelBuilder SQL Expression Using Inline Varia...

PyCharm Setup for ArcGIS Desktop

Re: Error 010240 - Could not save raster dataset.....

ArcInfo Workstation Commands

Re: Is it possible to configure SA in a Python scr...

ArcGIS Desktop Installation Support

R-ArcGIS

Coordinate Reference Systems

Python Snippets