Latest Contributions by JoshuaBixby

Thanks for the update/clarification and for posting the links. ... View more

What are you trying to accomplish?  I see in your code that you are setting the output feature class name to the name of your input feature class, hence the error message.  Are you trying to overwrite an existing feature class with a subselection of itself? ... View more

Correct.  As a side note, you should really consider using the os.path module to create file system paths (like feature classes in feature datasets). Starting at the fieldList statement towards the bottom of your script: fieldList = [f.name for f in arcpy.ListFields(fc, "*", "STRING")] with arcpy.da.UpdateCursor (fc, fieldList) as cursor:     for row in cursor:         row = [(fld if fld is not None else 'TBD') for fld in row]         # row = [(fld if fld else 'TBD') for fld in row] # this would capture empty strings too and not just NULL         cursor.updateRow(row) ... View more

With ArcMap, the easiest way to access a 64-bit Python interpreter that works with ArcPy is to install 64-bit Background Geoprocessing.  When you install 64-bit Background Geoprocessing, it installs a 64-bit Python interpreter/package.  After the 64-bit Python interpreter is installed, you can point PyScripter to use it instead of the 32-bit one. Just a note of caution/awareness.  Since the 64-bit Python interpreter is installed last or after the 32-bit, your Python file associations will likely be pointed to the 64-bit interpreter.  Although this isn't an issue most of the time, there are some limitations of the 64-bit ArcPy like no access to personal geodatabases.  You can change your Python file type associations back to the 32-bit interpreter if you want. Also, since ArcGIS Pro is natively 64-bit, you can also access 64-bit ArcPy by installing that application. ... View more

I may not be describing this perfectly, but the gist of your problem relates to how dictionaries "store" information.  A Python dictionary doesn't store the actual values in it, it stores pointers to locations in memory.  So, a single call to sys.getsizeof() isn't giving you the total size of the data in the dictionary as much as it is giving you the total size of the data structure that is containing all of the reference information to your data. >>> from sys import getsizeof >>> dic1 = {1:range(1)} >>> dic1 {1: [0]} >>> getsizeof(dic1) 140 >>> dic2 = {1:range(100)} >>> dic2 {1: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, ..., 98, 99]} >>> getsizeof(dic2) 140 >>> The Python 3 documentation for sys.getsizeof() references a recursive sizeof recipe that should work for you. ... View more

Please remember to mark your question as answered. ... View more

Can you provide a bit more information about your datasets?  I was just able to apply a definition query to a feature class in a file geodatabase and export a layer package without any errors. ... View more

Kory Kramer​, thanks for following through and updating the GeoNet discussion.  ... View more

It appears to be a bug, you should submit an Esri Support incident (Incident opened, bug logged). I can reproduce the behavior using a table in a file geodatabase.  If you use a cursor, the correct values are shown, it is just a display issue in ArcGIS Pro. ... View more

Providing a bit more information might help us help you better: What Desktop product are you using?  ArcMap or ArcGIS Pro? What version of the product are you using? What type of cursors are you using?  There are the original/older cursors and the not-so-new-now ArcPy Data Access cursors. What is your backend data store?  File geodatabase, personal geodatabase, enterprise geodatabase?  If the latter, what DBMS and version? What are the properties of the field you are trying to edit? ... View more

Forward-looking statement or incomplete statement?  Arguable, I guess, but Pro 1.3 is what should have been stated.  For now, the plan appears to be just for Pro, not for ArcMap. ... View more

Although the correct answer has been stated already, here is a link to some relevant documentation:  001324: Personal Geodatabases are not supported in 64-bit versions of ArcGIS. Description Personal geodatabases do not scale well in the 64-bit environment. They cannot be used by 64-bit versions of ArcGIS. Solution Modify your data sources to a supported type with 64-bit ArcGIS. Using the Create File GDB tool, you can create a file GDB and then import your layers into it using the Feature Class to Geodatabase (multiple) tool. As the error description states, this isn't an ArcGIS Pro issue, per se, it is a 64-bit ArcGIS issue.  Whether one is talking about ArcGIS for Server, Background Geoprocessing (64-bit), or ArcGIS Pro; personal geodatabases aren't supported because the applications are 64-bit. ... View more

I just installed Pro 1.2 on an ArcMap 10.4 machine, and I must be missing something because I don't see Conda or anything that looks like Conda.  This is starting to feel a bit like the ArcGIS 10.3.1 SciPy announcement.  How do those financial types couch it again, in their prospectuses?  Oh yeah, "forward looking statements."  Maybe the session description is a present-tense forward-looking statement. ... View more