Latest Contributions by JoshuaBixby

It isn't called "code wrap" but Insert > Syntax Highlighting ... View more

It is a misnomer.  "Last used ArcGIS Pro" really means the last time you authenticated against the license server to try and use ArcGIS Pro.  Whether ArcGIS Pro is successfully launched once the license is obtained/checked isn't what is being tracked on Esri's side. ... View more

The code you provide above is from the Making Field Calculations help from ArcGIS 9.3/9.3.1, and therein lies your problem.  The code Esri provided was VB/VBA and involved accessing ArcObjects.  Starting with ArcGIS 10.0, Esri moved to a VBScript parser instead of a fuller-featured VB/VBA.  Although some VB code still works in the code block for the field calculator, the specific code you used doesn't because you can't acess ArcObjects through VBScript. Even if the code you posted worked, VB support has been on life support for a long time, and you should really consider moving to Python.  If you simply change the parser to Python, the following code will work in the expression box (you don't need a code block): !shape.extent.XMax! . Since it seems you are working with points, and single points at that, the extent of the geometry will be the geometry itself.  You could also use !shape.firstPoint.X! as well. ... View more

If Esri is only posting ArcGIS Pro Prerelease (no updates) in MyEsri, and users need to update through ArcGIS Pro, how do you recommend he upgrades if he can't launch ArcGIS Pro? ... View more

You may want to check out Issue with SQUID Proxy server and ArcGIS Online and ArcGIS Pro. ... View more

I decided to open an Esri Support case on this issue.  First response, Advanced Services was "needed with ArcIMS Metadata Server."  Say what?  Maybe ArcIMS Metadata Server did require Advanced Services, I don't know and don't care enough to know given ArcIMS's last release was 4+ years ago, but I simply can't believe ArcIMS had anything to do with dropping Advanced Services for Desktop and Workgroup database at ArcGIS 10.3. We'll see what the next response brings.... ... View more

I revisited the Help for Building a query expression, where it states: If the string contains a single quote you will first need to use another single quote as an escape character. In Python, the backslash is the dominant escape character, but there are some additional escape sequences.  My sample code above that used text replacement to escape the single quote used the backslash, but ArcGIS wants users to escape a single quote by using another single quote. The updated code worked for an example I ginned up on my machine: expression = "{} = '{}' AND {} = '{}'".format(SelectCriteriaF,                                               str(list_UV_CriteriaF ).replace("'","''"),                                               SplitCriteria,                                               str(listSplit ).replace("'","''")) ... View more

Unfortunately without specifics of what the variables are when the code errors, or even the exact error text, those of us trying to help are grasping as straws to some extent. ... View more

If you print out an example using all the variables along with the error messages, it might help narrow down the issue. ... View more

As imperfect as PatchFinder may be, I think it's batting average is higher than relying on Build Numbers, especially from applications other than ArcGIS Administrator.  Looking at FAQ:  What are the build numbers for releases of ArcGIS Desktop?, one can see that build numbers for ArcGIS 10.1 SP1 QIP are incorrect in ArcMap and ArcCatalog.  The ArcGIS 9.3.1 SP2 QIP had a similar issue. Taking the above information together with the fact that most patches don't update build numbers, our organization has moved away from using build numbers for identifying anything beyond major/full releases.  In fact, we have an Esri Support Case open right now over how to definitively show the OpenSSL patch has been applied because PatchFinder isn't showing the patch on some machines that it has been applied on. Of course, the issue only gets muddier when dealing with patching Background Geoprocessing as well as Desktop.  Just be aware that identifying installed patches has historically been as much an art as a science. ... View more

I encourage you to check out Python string formatting.  Not only is using built-in string formatting more Pythonic than concatenating several strings together, I would also argue it is more readable. First, I would just try restructuring the expression using string formatting to see if that works: expression = "{} = '{}' AND {} = '{}'".format(SelectCriteriaF,                                               str(list_UV_CriteriaF ),                                               SplitCriteria,                                               str(listSplit )) If that doesn't work, then you might have to try string replacement to insert an escape character before the quote.  From looking at the code, I am not sure which variable is causing the problem, so I just replaced text on both.  This might work: expression = "{} = '{}' AND {} = '{}'".format(SelectCriteriaF,                                               str(list_UV_CriteriaF ).replace("'","\\'"),                                               SplitCriteria,                                               str(listSplit ).replace("'","\\'")) ... View more

Another idea, are both your datasets in the same workspace?  That is a requirement for this tool. ... View more

There is basically a bug in the expression builder.  Try removing the quotations from around the fields.  Even if you verify the expression and it fails, it can still run correctly.  Not sure if this is exactly your problem, but I run into the errand quotations with the expression builder all the time. ... View more

Are your keys currently row numbers from a table?  If so, you are basically treating a dictionary like a list, which is more awkward to work with than if it was just a list.  The focus of the dictionary key should be the BuildingID, not the row number. Assuming you want each building to have the three hazards mentioned above, and only those three hazards, the following (untested) code might work: # import functions from modules that are available but not commonly imported  from collections import defaultdict  from numpy import fromiter, dtype # group hazards by building haz_group = defaultdict(list) with arcpy.da.SearchCursor(in_table, ['BuildingID', 'HazardID']) as cur:     for k, v in cur:         haz_group .append(v) # create iterable and populate with flagged buildings build_iter = (k for (k, v) in haz_group.iteritems() if v.sort() != [16, 17, 18]) tmp1 = fromiter(build_iter, dtype([('BuildingID', 'S10')])) # dump numpy array to table arcpy.da.NumPyArrayToTable(tmp1, out_table) # or just print BuildingIDs to console for build in build_iter:     print build Note that if you are going to just print the buildings, drop lines 13 and 16 because line 13 will exhaust the generator so lines 19 and 20 won't print anything.  Instead of creating a generator expression, you could use a list comprehension and the list would persist.  I tend to work with generator expressions because lists can consume large amounts of memory with very large data sets. NOTE:  Updated Line 12 to address the HazardID not necessarily being sorted in original table. ... View more