Latest Contributions by JoshuaBixby

@KoryKramer, with standard SQL the following expression does not select NULL: FIRE_NAME <> 'ZWINGE' I just fired up Pro 3.0.2 and tested Select By Attributes on a feature class in a file geodatabase, and results were as expected, which is not to select NULL. ... View more

@Jon-PaulMcCool, @RandyCasey is absolutely correct.  The use of NULL introduces 3-value logic into SQL comparison operators.  Since NULL cannot be equal or unequal to any other value, including NULL itself, one cannot select NULL records based on equality comparisons.  ... View more

Have you tested it outside of an enterprise geodatabase?  Is the code your running and the changes to the data working on the same version of the data?  If I have users modifying data in version X and they don't reconcile and post, I won't see them in version Y. ... View more

Can you elaborate on what you mean by "reinstating these license?"  Cancelling a license file does not deauthorize already-deployed licenses, so the licenses are still active and valid if you look under Authorizations. ... View more

To both improve your own troubleshooting and get better feedback from Community members, focus on creating and sharing a Minimal, Reproducible Example (MRE):  How to create a Minimal, Reproducible Example - Help Center - Stack Overflow.  Having an MRE is also most helpful when opening cases with Esri Support. ... View more

If you are using ArcGIS Pro, I suggest you use literal strings or f-strings: expression = f"{str(Num)[4:7]} not between {dateStart} and {dateEnd}" ... View more

When I try just building your expression I get an error before I even get to the arcpy tool:  (The specific values I used don't matter for test building expression, just the data types matter, and I had to change !Num! to just Num for testing)     >>> Num = 123456 >>> dateStart = 1 >>> dateEnd = 2 >>> expression = "str(Num)[4:7] not between '" + dateStart + "' and '" + dateEnd + "'" Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: can only concatenate str (not "int") to str >>>     Are you sure you are pasting your exact code? ... View more

Python slicing is start to stop, not start through stop, so [5:8] returns only 3 characters and not 4 characters. ... View more

What version of Pro are you using?  I just tested in Pro 3.0.2, and when I enter '06/24/1896' it gets saved as '6/24/1896'. ... View more

With the information provided, it is difficult to comment on whether changing your workflow to pandas would be more efficient.  Are the feature classes in an enterprise geodatabase, file geodatabase, or something else?  If file or mobile geodatabase, are they stored locally or on network share?  Could you copy the feature classes into memory before processing?  Are the fields you are querying indexed appropriately?  There are likely more questions I could come up with if I spent a bit more time thinking about it. Exporting a dataset into memory via pandas could definitely be faster, but not necessarily because there are lots of ways of processing data in pandas and some are faster than others.  If the dataset is very large and it won't fit in memory, then having the Python process start paging will cause performance hit regardless of specific pandas workflow. Given there are so many factors involved, the best approach is to do some testing oneself.  Is it worth taking the time to test?  Probably if you are here asking the question(s). ... View more