This tool converts the points in a point data source to lines (polylines) in a new or existing line data source. An integer unique ID field in the point attribute table is required to distinguish between different output lines, and another integer field is required that defines the order in which points will be connected. This order field does not have to start at 1 for each line, so if your point attribute table is already ordered you can either use the FID field, or better yet add a suitable order field using the addcodedfield command.
The split option controls whether a single polyline is written for each unique ID (the default), or whether each line segment connecting a pair of sequential points is written as a separate line in the output data source.
convert.pointstolines(in, uidfield, orderfield, out, [split], [where]);
|in||the input point data source|
|uidfield||the unique ID field in the point data source that identifies collections of points that make up each line)|
|orderfield||the point attribute field that can be used to sort the points into the correct order (must be numeric or date, but not a date stored as a text field)|
|out||the output line data source|
|[split]||(TRUE/FALSE) if TRUE, writes each line segment connecting a pair of sequential points as a separate line (default=FALSE)|
|[where]||the selection statement that will be applied to the feature data source to identify a subset of features to process (see full Help documentation for further details)|
convert.pointstolines(in="C:\data\telemetry.shp", uidfield="ANID", orderfield="STEP", split=TRUE, out="C:\data\anpaths.shp");
convert.pointstolines(in="C:\data\samplelocs.shp", uidfield="SAMPID", orderfield="ORDER", out="C:\data\transects.shp");