Latest Contributions by DaveForsberg

It would be useful to add an option to order the outputs of the SplitLine, SplitLineAtPoint, etc. geoprocesses based on the direction of the line being split (from the start point to the end point, or in the direction of the increasing measure values).  Currently, if a line is being split into 5 sections, the output is usually in the ordered of: 1st section, and then some random order for the remaining sections. Because of this, addition programming code has been added to the C# applications we've developed to properly order the split lines for use in subsequent analysis.  Adding this option would significantly improve our applications performance. ... View more

It would be useful to add an option to order the outputs of the SplitLine, SplitLineAtPoint, etc. geoprocesses based on the direction of the line being split (from the start point to the end point, or in the direction of the increasing measure values).  Currently, if a line is being split into 5 sections, the output is usually in the ordered of: 1st section, and then some random order for the remaining sections. Because of this, addition programming code has been added to the C# applications we've developed to properly order the split lines for use in subsequent analysis.  Adding this option would significantly improve our applications performance. ... View more

When creating applications using the Pro SDK, we are often executing a series of geoprocesses.  It would be useful to have the option to save the output feature class of various geoproccessing functions (Buffers, Intersects, etc.) directly to defined objects in the application code, instead of writing the results to a geodatabase.  Then use these in-memory feature classes as inputs to other geoprocesses in the series. For example: Buffer buffer1  = new AnalysisTools.Buffer(); Buffer buffer2  = new AnalysisTools.Buffer(); IFeatureClass bufferedFc1 = geoprocessor.Execute(buffer1, null); IFeatureClass  bufferedFc2 = geoprocessor.Execute(buffer2, null); Intersect intersect = new AnalysisTools.Intersect(); intersect.in_features = buffered1, buffered2; intersect.out_feature_class = ... written to a geodatabase feature class object result = geoprocessor.Execute(intersect, null); This would increase the applications performance by eliminating the need to write the results of each geoprocess step to a geodatabase, only to be read back into the application, and finally deleted at the end of the series. ... View more