ITinFeatureEdit.ConvertToPolylines Method

Converts qualified edges to a polyline feature class.

[Visual Basic .NET]
Public Sub ConvertToPolylines ( _
    ByVal pFeatureClass As IFeatureClass, _
    ByVal pFilter As ITinDynamicFilter, _
    ByVal bSkipDensifiedNodes As Boolean, _
    [ByRef pFieldName As Object] _
)

[C#]
public void ConvertToPolylines (
    IFeatureClass pFeatureClass,
    ITinDynamicFilter pFilter,
    bool bSkipDensifiedNodes,
    ref object pFieldName
);

[C++]
HRESULT ConvertToPolylines(
  IFeatureClass* pFeatureClass,
  ITinDynamicFilter* pFilter,
  VARIANT_BOOL bSkipDensifiedNodes,
  VARIANT* pFieldName
);

[C++]
Parameters
pFeatureClass 
  pFeatureClass is a parameter of type IFeatureClass
pFilter [in]
  pFilter is a parameter of type ITinDynamicFilter
bSkipDensifiedNodes [in]
  bSkipDensifiedNodes is a parameter of type VARIANT_BOOL
pFieldName [optional]
  pFieldName is a parameter of type VARIANT
  To indicate this parameter is undefined pass a reference to a VARIANT with type VT_ERROR and scode value of DISP_E_PARAMNOTFOUND.

Product Availability

Description

Extracts embedded TIN polylines and writes them out to the specified feature class.

The specified feature class must exist and be polyline based.

If the feature class is Z enabled the polylines written to it will be 3D, otherwise they will be 2D.

The specified filter must be edge based (e.g. TinEdgeTypeFilter) and implement ITinDynamicFilter. You can use ITinEdgeTypeFilter2 with its RegularEdgesExcluded property set to TRUE to extract hard and soft breaklines as polyline features.

The option to skip densification nodes is for excluding points added by the triangulator to breaklines in order to make them Delaunay conforming. This option only works on TINs that have been created/edited in memory without having been saved to disk.

A field will be added to the feature class and is used to store a numeric code for the output features. In the case of edge type, a value of 1 is used for soft breaklines and 2 for hard. The added field will be called 'Code' unless you provide a different name via the optional field name argument.

Do not have WorkspaceEdit turned on as this member needs to add fields to the output feature class, a schema edit operation that WorkspaceEdit does not permit.

See Also