168 reputation
7
bio website
location
age
visits member for 1 year, 11 months
seen Feb 28 at 16:20

Aug
14
answered Why would Update (Analysis) tool from ArcGIS Desktop 10.0 create duplicate features in file geodatabase?
Aug
13
comment Why would Update (Analysis) tool from ArcGIS Desktop 10.0 create duplicate features in file geodatabase?
Thanks for your efforts
Aug
1
comment Why would Update (Analysis) tool from ArcGIS Desktop 10.0 create duplicate features in file geodatabase?
The ones that are not working are in a file geodatabase. The ones that are working are actually just shapefiles (the difference is because the same process is being used in different contexts).
Jul
31
asked Why would Update (Analysis) tool from ArcGIS Desktop 10.0 create duplicate features in file geodatabase?
Feb
5
awarded  Supporter
Jan
8
comment Spatial Query works while stepping through debugger but not otherwise
For now I have developed a workaround by first transforming the line feature class to a point feature class (using the line midpoints), then performing the 'contains' spatial queries, then going back and removing the lines without matching points. It's a bit clunky but it works. I'm going to leave this unanswered for a little bit just in case someone does have an idea why the spatial query would work inconsistently as I experienced.
Jan
8
revised Spatial Query works while stepping through debugger but not otherwise
deleted 59 characters in body
Jan
7
revised Spatial Query works while stepping through debugger but not otherwise
added 59 characters in body
Jan
7
comment Spatial Query works while stepping through debugger but not otherwise
Thanks for your additional suggestion - I have implemented as you suggested but I am still encountering a difficulty.
Jan
7
comment Spatial Query works while stepping through debugger but not otherwise
Thanks for the additional comments. I have examined the variables and can't find any that aren't set correctly, and I have option explicit on. The original code was extracted from a method called by the OnClick event. The feature classes are passed to this method by the OnClick event, where the feature workspace is set. And this is all already inside a Try-Catch block (boundaries are before and after the snippet) that is not springing an error.
Jan
7
revised Spatial Query works while stepping through debugger but not otherwise
Updated with more information on error
Jan
7
revised Spatial Query works while stepping through debugger but not otherwise
added code
Jan
7
comment Spatial Query works while stepping through debugger but not otherwise
Thanks for your suggestion. I'm not actually getting an error - it's just that I can tell this particular block of code isn't running based on the results I'm getting (and when I try to step through with the debugger to see where it's going wrong, it ends up running just fine and giving the proper results). I am using the COM releaser on the cursor.
Jan
7
comment Spatial Query works while stepping through debugger but not otherwise
I've just discovered that if I put in a message box at the breakpoint location, the code will also run (with the breakpoint removed), if that helps with diagnosis!
Jan
7
asked Spatial Query works while stepping through debugger but not otherwise
Dec
19
comment “There is not enough memory” Error when accessing IArea.LabelPoint
I'm still confused about WHY this error occurred, so if anyone out there has an idea why one feature out of the dozens of features that this worked for suddenly decided to misbehave, please let me know!
Dec
19
awarded  Scholar
Dec
19
revised “There is not enough memory” Error when accessing IArea.LabelPoint
added solution in readable format
Dec
19
accepted “There is not enough memory” Error when accessing IArea.LabelPoint
Dec
19
comment “There is not enough memory” Error when accessing IArea.LabelPoint
Dim pSafeFeature As ESRI.ArcGIS.Geodatabase.IFeature Dim pParcelFC As ESRI.ArcGIS.Geodatabase.IFeatureClass If Not pFeature Is Nothing Then pParcelFC = CType(pFeature.Class, ESRI.ArcGIS.Geodatabase.IFeatureClass) pSafeFeature = pParcelFC.GetFeature(pFeature.OID) and then proceeding with pSafeFeature instead of pFeature.