ITinFeatureEdit.CanAddVertex Method

Checks if a new polygon/polyline vertex can be added without creating spatial conflict.

[Visual Basic .NET]
Public Function CanAddVertex ( _
    ByVal pPoly As IGeometry, _
    ByVal pNewPoint As IPoint, _
    ByVal bClose As Boolean, _
    ByVal spacing As Double _
) As Boolean

[C#]
public bool CanAddVertex (
    IGeometry pPoly,
    IPoint pNewPoint,
    bool bClose,
    double spacing
);

[C++]
HRESULT CanAddVertex(
  IGeometry* pPoly,
  IPoint* pNewPoint,
  VARIANT_BOOL bClose,
  double spacing,
  VARIANT_BOOL* pbCanAdd
);

[C++]

Parameters
pPoly [in]

  pPoly is a parameter of type IGeometry
pNewPoint [in]

  pNewPoint is a parameter of type IPoint
bClose [in]
  bClose is a parameter of type VARIANT_BOOL
spacing [in]
  spacing is a parameter of type double
pbCanAdd [out, retval]
  pbCanAdd is a parameter of type VARIANT_BOOL

Product Availability

Description

This member is used primarily for conflict detection when using the TIN as a data structure to record point, line, and polygon features.

Returns TRUE if the passed point can be added as a vertex to the passed polygon/polyline without creating a conflict. The geometry isn't actually added to the TIN. It's treated as 'proposed' geometry. Presumably, code would use this member to ensure there is no conflict before proceeding.

The input poly object can be a polygon or polyline. It may have zero or more vertices already present.

The passed point is treated as if it were to be added at the end of the geometry's point collection.

A conflict results if any TIN features are within the specified spacing of the proposed geometry. This includes segment and edge distance checking as well as vertex and node checking.

The ITinFeatureEdit.ElementsIgnoredInConflictTest setting determines what, if any, TIN elements are excluded from the conflict test.

The Close argument is ignored if the input poly object is a polyline.

See Also