Latest Contributions by JoshuaBixby

We are on a large BPA/ELA which hasn't expired, or at least our current extension hasn't.  I have reached out to our Esri Customer Service Representative to help sort out what is going on.  A couple of our AGOL administrators said they never received an e-mail, so we have some work to sort out those mailing lists too. Once the dust settles, I will give an update in case others run into similar situations in the future. ... View more

Unfortunately, this is one of my gripes with the AGOL-based licensing scheme, i.e., AGOL administrators in larger organizations aren't necessarily in the same part of the organization as the GIS users because of the way ELA/contracts are established.  Maybe our admins got an e-mail, but would they even know what it meant if they actually read it. Appreciate the feedback, at least I now know who I have to go track down. ... View more

What, specifically, is the id of the record you are trying to select?  Is it 14036678?  If so, it is the underscore that is tripping you up.  The LIKE operator is for pattern/wildcard searching.  There are two operators, the percent sign (%) and the underscore (_).  The % operator matches zero or more characters while the _ operator only matches one character; thus, '11%' will match '11' while '11_' will not. ... View more

I think insert and update cursors were more the target for enabling with statements than search cursors, but people have a tendency to want to keep best practices simple.  Instead of having one best practice for insert and update cursors and a different one for search cursors, we have ended up with one for all three. I like list comprehensions, and I think they can work well with search cursors.  I was just pointing out the trade-offs of the two approaches, not trying to evangelize one over the other. ... View more

The documentation does give the impression that database locks will be released, but the documentation doesn't get into specifics of which locks.  Currently, using a with statement for da-based search cursor releases the read lock on the layer but not the schema lock.  My guess is that the schema lock can't be removed because the with statement resets the cursor iteration to streamline using the cursor again.  Explicitly deleting the cursor object will remove the final schema lock.  Is this poor documentation or a bug?  I haven't submitted a Support case to get an answer, but I am leaning toward Esri saying the former. ... View more

I agree a list comprehension can shave several lines off the code block, but we also lose the with statement.  I don't know whether it is formally documented, but I have read and heard several Esri staffers say using with statements is a best practice when working with cursors. ... View more

It is easier to look at code and provide feedback than statements describing the code.  What code are you using to build the table views? ... View more

Can you include more of the error message? ... View more

I did a quick performance check of the code above using pre-computed centroids stored and indexed versus generating centroids on the fly.  The latter approach took over 5x longer to run, and that was on a fairly modest-sized dataset. ... View more

I am not sure what your unique identifier is for municipalities, so I went with "id." SELECT m.shape, m.municipality, s.parcel_count   FROM admin.MUNICIP m,        (SELECT sm.id, count(*) as parcel_count           FROM admin.PARCEL sp, admin.MUNICIP sm          WHERE sm.shape.STIntersects(sp.shape.STCentroid()) = 1       GROUP BY sm.id) s WHERE s.id = m.id If you only wanted parcel count by municipality, without the associated shape, then the subquery itself would do the job.  Since you want the associated shape, you need to join the subquery results back to the municipality layer for mapping purposes. Performance wise, I am not sure how the above code will do.  You mention 17 hours, that does seem excessively long.  There are several things that could be going on.  One could be poor or nonexistent spatial indexes.  Check the execution plan to make sure spatial indexes exist and are being used.  I am also thinking that converting to a centroid on the fly could cause a performance hit.  For the minimal storage hit of adding a point field, it might make sense to store both the parcel polygon and centroid and then index both of them.  Also, if the parcel count isn't changing very much on a minute or hourly basis, it might be worth considering computing it once a day and storing the value for mapping and reporting. ... View more

It seems you are using the older/original search cursor instead of the newer data access (da) search cursor.  Have you tried using the da.SearchCursor with a Python with statement?  Does that change the result? ... View more

I, too, would be interested if there was a way to see all of the layers and table views created with arcpy outside of ArcMap, but I haven't found a way yet.  Obviously within ArcObjects it is being done, but it doesn't seem to be exposed through arcpy.  I guess the logic is that if you are creating them in your code then you should have an idea what you have created and can delete them as well, i.e., track it yourself.  I wouldn't mind being wrong on this one. ... View more

A cursory performance check shows SQL postfix being the quickest against a file geodatabase and SQL prefix being the slowest.  Runtimes relative to SQL postfix:  SQL postfix (+0%),  List (+3%),  Set (+4%), SQL prefix (+14%).  Interestingly enough, having the data in a personal geodatabase nearly doubled the runtimes of every approach across the board. ... View more

Although I think the approach is sound, it is bad practice to use a built-in function name as a variable identifier, i.e., naming a list 'list'.  The code as written will work, but shadowing a built-in name could cause confusion further down in the script. Another option for finding unique values is to use the set data type, which inherently doesn't allow duplicates. #Create empty set  salesSet = set()  with arcpy.da.SearchCursor(table, ["Sales"]) as cursor:      for sale, in cursor:          #Add sales to set          salesSet.add(sale) del sale, cursor #Iterate through set  for sale in salesSet:      arcpy.MakeFeatureLayer_management(table, "tableView", "Sales = '" + sale + "'")      ...      ... A slightly different tack is to let the database engine identify unique values either through a SQL prefix with arcpy.da.SearchCursor(table, ["Sales"], sql_clause=('DISTINCT', None)) as cursor: or SQL postfix. with arcpy.da.SearchCursor(table, ["Sales"], sql_clause=(None, 'GROUP BY Sales')) as cursor: Performance wise, I am not sure where each approach falls out, but I can't imagine the differences being noticeable.  My personal preference is using DISTINCT in a SQL prefix, but I know that ArcGIS 10.1 had issues with SQL clauses in cursors, so using a set data type might work with more versions. ... View more