Latest Contributions by HarryBowman

I'm trying to call distanceTo from a PointGeometry to a Polyine and am running into trouble whenever the polyline is one I just cooked up. Any pointer on what I'm doing incorrectly would be welcome. #get the first point feature and the first line feature poi = arcpy.da.SearchCursor("POIs","SHAPE@").next()[0] line = arcpy.da.SearchCursor("Streets","SHAPE@").next()[0] print poi.distanceTo(line)  #returns 0.017893575694200557 #get first part of line part = line.getPart(0) #get the first two points on that part p0 = part[0] p1 = part[1] #make a new polyline out of those two points seg = arcpy.Polyline(arcpy.Array([p0,p1])) print seg.length #returns 0.0017140186696764268, so the segment is there as a polyline #try to get the distance from the poi to the segment poi.distanceTo(seg) This is what comes back: Runtime error Traceback (most recent call last):   File "<string>", line 1, in <module>   File "c:\program files (x86)\arcgis\desktop10.1\arcpy\arcpy\arcobjects\arcobjects.py", line 809, in distanceTo     return convertArcObjectToPythonObject(self._arc_object.DistanceTo(*gp_fixargs((other,)))) ValueError: <geoprocessing describe geometry object object at 0x16068EE0> ... View more

I've been having problems with Select by Location running very slowly. I ran an experiment in which there was one point feature to do the section and I selecting all the lines within 200 m of that one point feature. The lines are in a geodatabase, which claims to have a spatial index built. 27 million lines, but with the spatial index, that shouldn't matter, right? After huge delay in GP, I tried it in the interface - same thing, huge delay, but it at least provided the information that it was reading envelopes - hundreds of thousands before I canceled (and crashed ArcMap...again). With a spatial index built, why would Select by Location (and Clip) read all those envelopes - it should be reading just a few after using the index. What is up? UPDATE: I started it again and am watching ArcGIS read through *all* the envelopes of the streets. 27 million of them. That's not right - it should be using the spatial index to just grab the close envelopes. ... View more

If I have multiple processes working away, the sample posted at http://blogs.esri.com/esri/arcgis/2012/09/26/distributed-processing-with-arcgis-%e2%80%93-part-1/ makes it appear that you can write to a single table in_memory\identical  in all the processes. That would suggest a separate copy of the workspace for each process, which I think it was Bruce Harold says in the comments. But frankly, I am still lost. What's making me confused is the commentary in this threadhttp://gis.stackexchange.com/questions/35614/concurrent-use-of-in-memory-workspace-in-arcpy which makes it seem like in_memory is shared across processes and is sort of like a "folder" in that you are OK to write to multiple tables as long as they have different names, but NOT to the same table name. Note, ths gis.stackexchange post is from 2011. So my question is whether a separate in_memory workspace is created for each process (so all processes end up writing to their own in_memory\table1 or whether it is shared, so you need to change the table names in_memory\table1, in_memory\table2, etc. or something else? I know I should just code and test, but maybe my test will work but under the hood it is "unsafe." ... View more

Nothing is showing up at all where I'd expect to see progress indicated in ArcMap. The process runs and I get a little pop up notice when it is complete, as before. I cannot see anything where I was expecting to see a "scrolling progress" before. The help system makes it looks like I should see something (the screen shot shows a progress bar, not the marquee style from before). Background processing is enabled. Do I need to do something else to make this visible? The process is running (I looked in Task Manager) but there is no indication in the ArcMap UI. Update: Correc this to be "sometimes" cannot see bar at all. Sometimes the scrolling marquee is there, sometimes not. ... View more