Latest Contributions by curtvprice

Bug report also says fixed in 2.1 BUG-000091451: The values of the ObjectID field for feature classes..  ... View more

Dan is correct, more on this: ArcGIS should allow the ability to permanently reorder fields in a table‌ In arcpy the best way to do this is to create an arcpy FieldMappings object and use it with the Table to Table or Feature Class to Feature Class tool to make a new copy of the table with the order and field names you want. It's a little challenging but it does work. Going the numpy table route is Dan's go-to approach, I am less handy with numpy and pandas than he is. The numpy route is probably faster, but less scalable than using a field mapping inside the arcpy cocoon. Note, I should say in ModelBuilder‌ you could create a field map using the Calculate Value tool, using an arcpy function to do the work of creating the field map, return the string representation and pass it to the tool that needs it. This seems to be a common use case so I should write a blog post about it sometime. ... View more

Anne-Marie, I found both these bugs on support.esri.com: ArcGIS Pro (fixed 2.3) BUG-000106677: Setting a Raster Analysis Mask in the Environment Se..  ArcMap 10.7 (not in product plan 6/2019): BUG-000101814: A raster shifts its geographic position when applyin..  So it appears the excellent Juan Laguna   may have been incorrect, this was not fixed in 10.7.  We have been warned that bug fixes to the old ArcMap platform are lower priority, all major development is now happening on Pro. Do you have a vector mask? Worth trying a raster mask (better performance anyway) or no mask and see if you still get the shift. Or you could do it in ArcGIS Pro. I really like the 2.5 version, it has come very far since the early days. ... View more

I loathe Arcade.  Even if you don't take issue with Esri creating a new, proprietary language, which I do take issue with, usability wasn't a design priority if JavaScript was the inspiration for syntax and structure. I could not agree more. "That @#$% circus language" ... View more

These do look like bugs which I recommend reporting. Two workarounds for you to try: 1. Keep raster names <= 13 characters. A commonality I'm seeing here are long raster names. This has to do with historical limitations in some tools. 2. I have always gotten better raster processing performance (and avoided weirdness) by using file based rasters, that is, esri grid, or these days, .tif, stored in a folder.  I think gdb rasters are great for read but not as good for writing. ... View more

Unclear to me why it would stop after three iterations. One thing I noticed though, I suggest you put the iterator inside a submodel so you don't run the path distance over and over again on every iteration. Iterators re-run all tools in the model  (unless you somehow prevent this with a precondition logic - a sub model is an easier way to control that). If you must run it every iteration (unclear), you may want to set a precondition from the output to the iterator to the path distance tool, to make sure the path distance runs after the selection is made. ... View more

I think you need a precondition to connect "means" to the Calculate Field tool, to make sure your value of means is updated with your stats result before you run the Calculate Field.  ... View more

This is kind of fun once you figure out how it works! Extract By Circle needs a object of type Point for that parameter, in the ExtractByCircle help they have a Python example that looks like this. outExtCircle = ExtractByCircle("elevation", arcpy.Point(482838.823, 222128.982), 500, "INSIDE")‍‍‍ ‍ You need a string representation, because all variables in ModelBuilder are text strings, even when they represent other data types. These aren't always obvious (Point string rep would be  something  "100.0 00.0 NaN NaN" -- but most aren't that simple, think: Spatial Reference) so I like to construct them using the Calculate Value tool. You use this tool to create a Python string expression and assign its type to Point. Say X and Y are model variables you extracted from your table using Get Field Value. You set these as preconditions to the Calculate Value tool, then use: Calculate Value expression: str(arcpy.Point(%X%, %Y%)) Calculate Value data type: Point The output is a text representation of a Point, which  you assign as Point type using the data type parameter. If you do this, you can connect the point value output to Extract By Circle! ... View more

Are you sure you need full resolution on this? Bandwidth may not be an issue, but processing zillions of cells with any neighborhood operator is just a LOT of data to process. Even if you downloaded tiles on the data it would take you weeks I'm sure. ... View more

That works for me too. Thank you - great tip. With COVID our students locked off campus and for bandwidth issues can't easily get data off our esridata folder, so this is really helpful! Today type:"layer" and type:"layer package" seem to be working for me. I still think AGOL advanced searching needs more detailed documentation, for example a list of what type: keywords are supported, and whether "layer" and "layer package" are synonymous. ... View more

Just some thoughts I'd try it in Pro, they have been doing a lot of tiling work to support multiprocessing (and distributed ! processing) and this has made large overlays much more robust and scalable. That and Pro does it all in 64 bit which solves a lot of memory management issues. If your workflow is tied to ArcMap, and you haven't installed background 64 bit processing, I'd try that - then you get ArcMap tools running in 64 bit which also can help with scalability. Good luck! ... View more

I think you are doing it right, I found your post and added a test model to this thread: Sub-model cannot iterate features with same name ?‌ ... View more

Kory Kramer I been robbed!  (Seriously, Tom's answer was better though and truly deserves the correct.) ... View more