Latest Contributions by yosukekimura

Thank you for pointer.  I got started learning memory_profiler.  I also found that using common sense for saving memory make sense instead of relying on tools too much. ... View more

Here is more or less what I would do...  I am taking method 4 of my original post. Tool has two boxes, one grayed out (Figure 1).  Usually specify output file name in top box (Figure 2).  If I put a file which has partial but valid data, script moves the file name to bottom clear the top box (Figure 3).  execute() find value for the second box (Parameter in_csv ) instead of the first box (out_csv), and append the data.  If the file provided is not compatible with the tool, tool is going to overwrite the file (Figure 4).  Code at the end. Figure 1. Intial dialog Figure 2. New file Figure 3. Appending to partial file. I set the file name in first box, and the script judge that it is for appending and move it the second box Figure 4. Overwriting existing file.  In this case the csv file I provided is not what's expected for appending, so tool is going to overwrite. The code: (too long?) ... View more

I have the Tool as class, but it's rather large.  I can make stripped down version if needed.  But really, I haven't done much beyond very basic things.  I just asked before spending hours for reinventing wheels This is what I have for the parameter right now def getParameterInfo(self):     # other params ...     ## Output parameter     out_csv = arcpy.Parameter(             displayName="Output CSV File (.csv)",             name="out_csv",             datatype="DEFile",             parameterType="Required",             direction="Output")     out_csv.filter.list = ['csv']     # more... In the updateMessage(), I have this piece of code, where I may write checking code instead of write(f.next()) . def updateMessage(self, parameters):     # other things...     # my test     canappend = False     pth = out_csv.valueAsText     if pth is not None and os.path.exists(pth):         # so this does lets me read the file         # so suppose i write some small code to do the check, and call that when needed         with open(pth,'r') as f:             # TODO this part should be some testing code             fo.write(f.next())             canappend = True     # more tests ... ... View more

Darren's method should work, and this is an alternative. # make table of pair of zero distance arcpy.GenerateNearTable_analysis(fcOrig, fcOrig, tblNear, "0",     "NO_LOCATION", "NO_ANGLE", "CLOSEST", "0") if int(arcpy.GetCount_management(tblNear).getOutput(0)) > 0:   # grab ids that showed up in the table   ids = set([ _[0] for _ in  arcpy.da.SearchCursor(tblNear,('IN_FID'))])   # grab shape   oid = arcpy.Describe(fcOrig).OIDFieldName   outpoly = [_[0] for _ in arcpy.da.SearchCursor(fcOrig, [ 'SHAPE@, oid])       if _[1] in ids ]   # save   arcpy.CopyFeatures_management(outpoly, fcTouching) ... View more

I haven't tested, but      p.disjoint(q) intead of      p.distanceTo(q)==0 may runs faster particularly when there are a bunch of polygon. your method is O(n^2) so may have trouble with large number of polygons... ... View more

This sounds a good work around.  It doesn't resolve the issue of Select Layer By Location, but what I wanted to do from the first place was to cycle through feature within extent.  I really don't have to select anything.  I will try this in my code see if performance is good.   Thank you so much for all the help! ... View more

Joshua, Thank you for taking time testing this out.  Interesting that INTERSECT_3D behave differently, but I don't know how to interpret this behavior.  I never used 3D feature in ArcGIS, and this particular feature class was created by me starting from arcpy.Polygon() based on input coordinate values I got. The fact that making feature class of only this single problematic polygon let the ArcGIS to behave as expected make me speculate that somewhere ArcGIS is setting analysis resolution of coordinates and the extent of original feature class is so large compared distance of the polygon to extent.  But the SelectLayerByLocation doenst observe much environmental settings, maybe too dangerous for user to arbitrary set some threshold for vector data.  Hopefully in version 10.3, passing Extent object will "fix" the problem I see. For the time being I will stick with CopyFeatures method, because it is working and robustness is more important since this is part of bigger script.    Part of input for my script is your employer, by the say, US Forest Service ... View more

Thank you for advice. I ran CheckGeometry on both extent polygon and features polygon, neither returned anything.  I ran RepearGeometry tool on both, but the symptom was the same. ... View more

I would use Generate Near Table ArcGIS Help (10.2, 10.2.1, and 10.2.2)  with search_radius = 0 to make table of features that are touching.  then select from the layer which is included in the near table's "IN_FID" field.  These are the feature which touches at least one neighbor.  Not clear if you want them to get dissolved.  Do so if you want to ArcGIS Help (10.2, 10.2.1, and 10.2.2) .  The rest of features are the lone features.  Save each of them by Copy Features tool ArcGIS Help (10.2, 10.2.1, and 10.2.2)  . ... View more

Thank you so much again for the help! 1.  It is a single part.  Most of features are, and this particular one definitely is. 2. I am using WGS84, and everything is made to WGS84.  I figured how to set reference to arcpy.Polygon, so the extent polygon knows the spatial reference now. 3. I actually tested what I am doing in my ArcMap.  Specifically, I run the script but I also exported the extent polygon, the feature class, feature layers, while I set the extent to be global first.  The image I had was showing those exported feature (shape file).  I then manually tried to select by geometry in two way.  One is from the ArcMap's tool (Selection ->Select By Location ...).  I also run "Select Layer By Location" tool from the tool box.  Neither of them did not select this blue feature, even though blue is included in the pink (extent).  Extent's top is 56.565833 dd, and the feature's top is 56.557500 dd , so off by 0.0833 degree (~ 0.5 minutes). I also have a new observation.  I made the problematic feature into a feature class lone feature.  Then this select by location feature works, it picks up the feature.  But if I apply the tool to the original feature which has ~1600 features spreading across the continent, that particular feature is not selected.  The features are wide spread across the area, and each polygon is tiny in comparison to the extent.  So I am wondering ArcGIS somehow sets criteria to lower for the spatial accuracy and then this polygon got dropped somehow...? I made three shape files, and posted here https://utexas.box.com/s/a6q45925jrpxzknxdp357fremtjhprhz It has three features, ext1, feat1 and feat1_sel.  ext1 is the extent polygon, feat1 the feature class of ~1600 features.  feat1_sel is the one having trouble.  4. sorry for the type for cursor.  I always use arcpy.da.cursor.  They should have just overwritten old  cursor. yosuke ... View more

Thank you for help! So my extent is one giant box.  my feature having trouble in particular this time is a small rectangle sitting inside the extent rectangle.  I understand that INTERSECT, CONTAINS etc has slight difference but I understand that they both select the blue feature in the pic below.  pink is the extent polygon The extent is a lot larger than the feature.  Below show the extent, and tiny dot near top left corner is the feature causing trouble. ... View more