Latest Contributions by JoshuaBixby

There is little to nothing that is unique with how ArcGIS Pro utilizes CPUs.  It is a Windows application that is mostly single-threaded, partially multi-threaded, and partially GPU-enabled.  To Esri's credit, Pro is much more multi-threaded than ArcGIS Desktop/ArcMap, but a lot of geoprocessing still depends on the single-threaded performance of a given CPU. There are many factors that influence the performance of an application besides CPU, and there can be other factors that are non-application specific that make a strong case for choosing one CPU over another.  Both of these CPUs are designed for laptops, so power consumption/efficiency is likely a factor to consider. In short, there are lots of factors to consider, and you haven't shared any information for people to make specific suggestions on which may work best for you. ... View more

There are two separate programs for engaging with Esri staff and software prior to final release.  The earliest form of engagement, which is usually alpha or early beta releases, is Holistic Testing Program for Esri Software Development: The Holistic Testing Program consists of a select user group designed to test Esri software releases using real-world workflows and datasets. By implementing user workflows as an integral part of Esri's software testing strategy, software issues can be identified early on and fixed prior to releasing the final product. Throughout this process, Esri will gain knowledge and understanding of current GIS user workflows and scenarios. The Holistic Testing Program is an opportunity for Esri users to be involved early on with software development to ensure that the needs of fellow customers are met. The other program, which is already mentioned here and is usually late beta releases or pre-releases, is Early Adopter Community | Esri Early Adopter Program: This community represents a wide range of experience levels, environments, industries, security needs, and workflows. By joining our Early Adopter Community, you can have exclusive access to early release versions of Esri software. As a member of Esri’s Early Adopter Community, you will have the opportunity to interact with Esri’s development, product teams, and other like-minded community members. We are eager to hear your feedback on our early releases. You can share product feedback, contribute ideas and enhancement requests, and share thoughts and workflow questions on specific product forums within the Early Adopter Community. Although each program's website makes it seem as simply as filling out a form and signing up, it isn't necessarily that simple.  For some products, getting involved is as simple as asking, for others you really have to put forward a compelling case for why you should be included.  For a couple products, it took years before the Holistic Testing doors were opened to me, so asking isn't necessarily a sure bet it will happen, at least not right away. Whether Holistic Testing or Early Adopter, I have never gotten the impression there is a singular Esri point-of-contact that coordinates everything happening within/under the "program."  Different product teams utilize the programs to different extents, including not participating at all. I highly recommend you reach out to your Esri account team or person and inquire about joining a specific program for a specific product. I also strongly suggest you put together a business case, or at least documentation, that covers workflows that are specific and important for your organization and explain why you need to test the new versions prior to release. ... View more

Depending on the back-end DBMS, you can do subqueries in definition queries that would be able to do what the OP asks.  The issue is it would be a performance killer, and would make the layer slow for anything but the smallest of data sets. ... View more

Creating a new field, or even casting to TEXT is unnecessary.  If the numbers are integers, you can rely on basic integer math to find all numbers within the 2000 range: VACANT / 1000 = 2 ... View more

Possibly related to Autocomplete not working for lazily imported modules : PY-49357 (jetbrains.com).  The package tested in submitting the defect is similar to ArcPy in that autocomplete works in VS Code but not PyCharm. ... View more

The same question was asked and answered over on GIS SE for VS Code:  VS Code Intellisense with modern arcpy syntax - Geographic Information Systems Stack Exchange.  I am guessing the answer for VS Code will work for PyCharm too. ... View more

You have to start with the Shapefile Technical Description, which I linked to in my earlier comment.  That describes the binary structure of the file contents.  From there, you have to open the file and read the raw contents.  There are several tools for doing such work.  I happened to use PowerShell to read the file in and then used BitConverter Class (System) | Microsoft Docs to do the conversion. ... View more

Looking at the attached shape file *.shp file and comparing it to an new, empty shape file *.shp file from ArcGIS Pro, there are 3 fields that are different (see ESRI Shapefile Technical Description) Byte 32 - Shape Type is "Null Shape" in the attached but "Polygon" in the new Pro Byte 36 - Bounding Box XMin is 1.0 in attached but 0.0 in new Pro Byte 44 - Bounding Box YMin is 1.0 in attached but 0.0 in new Pro I really doubt the discrepancy in the bounding box values is causing the issue, it is most likely ArcGIS Pro (I haven't tested ArcMap) doesn't like the "Null Shape" for the shape type. ... View more

It seems clear there is something in the other shape file writer that ArcGIS does not like, but it is hard to say without you posting a copy of a shape file for people to test. ... View more

This kind of question is asked fairly regularly on GeoNet/Community, were you not able to find any of those posts while searching?  Also, have you tried anything specific yet?  If so, what isn't working with it? ... View more

The Name column looks like a string representation of a Python tuple containing a str and int., so using Python eval built-in should work: >>> a = "('tienda la samaritana', 100)" >>> eval(a)[1] 100 >>> ... View more

arcpy.CalculateGeometryAttributes_management is simply an alias for arcpy.management.CalculateGeometryAttributes, so you should never get different results between them.  If you do get different results, there is a ArcPy defect somewhere. According to the documentation you reference, the geometry_property parameter should be in the form of a Value Table, which is one form of a multi-value input.  Working with multivalue inputs—ArcGIS Pro | Documentation .  Working with Value Table objects is quite clunky, so there are Python list and string representations of them, which is what you commonly see in documentation examples.   ... View more

Here is your code I am just copying and pasting back -------------------------------------------------------------------------------- import multiprocessing from processRun import multifunction def main(): pool = multiprocessing.Pool(processes=4) pool.map(multifunction, range(0,1)) pool.close() pool.join() if __name__ == "__main__": main() My processRun file looks like: import arcpy def multifunction(num): arcpy.management.GenerateTessellation("C:\\Users\\jay\\Documents\\test.shp", "-86.809667396 33.5218054870001 -86.7009855469999 33.6051117490001", "SQUARE", "900 SquareMeters", 'GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]];-400 -400 1000000000;-100000 10000;-100000 10000;8.98315284119521E-09;0.001;0.001;IsHighPrecision') :   ... View more

@Jay_Gregory, I ran your code as-is (except changing output location), and it runs fine on my machine with Pro 2.9.2.  The result is an 11MB or so shape file. ... View more

That Python package expands, a little, on the built-in str.title() functionality so I don't know if it really offers much here since the OP is after truecase conversion. ... View more