Latest Contributions by NeilClemmons

No.  The order of the points in the point collection match the order in which they appear in the polyline or polygon that they represent.  For a polygon, outer rings will have points ordered clockwise and interior rings will have points ordered counter-clockwise. ... View more

I've never noticed any problems.  In fact, most of the coordinates systems I work with regularly are based on NAD 83 or WGS 84.  I don't do a lot of projecting though. ... View more

Do you have error handling in your code?  I don't see it in what you've posted.  It's up to you as the developer to handle errors within your own code (that's not something that ArcMap could do for you).  All of your code should be within Try/Catch blocks at points where exceptions would be thrown out to the ArcMap application.  You should also place Try/Catch blocks within your call stack at points where it makes sense (where those points are is up to you).  In the code you've posted, you're starting an edit operation without first starting an edit session.  This isn't allowed.  You must first called IEditor.StartEditing and pass in a reference to the workspace you want to edit.  You can also preface that by checking IEditor.EditState to see if an edit session has already been started and then check IEditor.EditWorkspace to see if the edit session has been started on the workspace you want to edit.  If the edit session has not been started, then you will need to start it yourself.  If it has been started but on a different workspace then you should stop the current edit session and start a new one. ... View more

You can find most of them here: http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/#/ArcMap_commands/00010000029s000000/ ... View more

Try using the actual GUID for the tool instead of the ProgId. {AD1891E4-7C79-11D0-8D7C-0080C7A4557D} I've run into problems using the ProgId. ... View more

Without seeing your code there's not much I can do.  Be sure to use the CODE tags when posting your code (the # button on the toolbar) so that it formats correctly and is easier to read. ... View more

That isn't entirely accurate.  The problem isn't that the geometry is multi-part; it's that the geometry type is incorrect.  For example, if the feature class is a Polyline class then you can insert any geometry as long as it implements IPolyline.  It doesn't matter how many segments the polyline contains or if the segments are not all connected (i.e. it's a multi-part polyline).  You can't, however, insert a Line, EllipticArc, CircularArc, or one of the other line type geometries.  It has to be IPolyline. You can check the geometry type expected by the feature class via IFeatureClass.ShapeType.  Here is a breakdown of some common scenarios: esriGeometryPoint - geometry must implement IPoint esriGeometryMultiPoint - geometry must implement IMultiPoint esriGeometryPolyline - geometry must implement IPolyline esriGeometryPolygon - geometry must implement IPolygon ... View more

The spatial reference of a feature is determined by the feature class in which it is stored.  If you get a feature out of a feature class and project its geometry into another coordinate system, you will change the coordinates and spatial reference of that geometry object.  However, if you set the feature's geometry back to the projected geometry and store it, the feature will have updated coordinates but the spatial reference will remain that of the feature class.  If you want to change the spatial reference of all of the features in the feature class, then you will also need to change the spatial reference of the feature class after you've projected them. ... View more