topic Re: Dissolving lines with opposing direcionality in Geoprocessing Questions

Dissolving lines with opposing direcionality

TomSomers — Fri, 23 Mar 2012 17:51:49 GMT

When you dissolve arcs using the dissolve tool, does directionality of the arcs come into play. In other words, if two adjacent arcs are not going in the same direction will they not be dissolved.

Re: Dissolving lines with opposing direcionality

Robert_LeClair — Fri, 23 Mar 2012 18:14:03 GMT

It can come into play if you check the Unsplit Lines parameter in the DISSOVLE GP tool. By doing so, lines are only dissolved when two lines have an end vertex in common.

Regards,

Robert LeClair
Esri-Denver

Re: Dissolving lines with opposing direcionality

TomSomers — Fri, 23 Mar 2012 18:21:04 GMT

So if it is unchecked, all connecting lines with the same chosen attribute value will be dissolved regardless of directionality?

Re: Dissolving lines with opposing direcionality

Robert_LeClair — Fri, 23 Mar 2012 18:21:52 GMT

Yes, this is the default behavior...

Re: Dissolving lines with opposing direcionality

DanLee — Fri, 23 Mar 2012 19:46:37 GMT

There seems to be some confusion about the Unsplit Line parameter here. The correct descriptions are:
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Dissolve/00170000005n000000/
"�?�The Unsplit lines parameter with two options, DISSOLVE_LINES and UNSPLIT_LINES, only applies to line input. When the default DISSOLVE_LINES option is specified, lines are dissolved into a single feature. When UNSPLIT_LINES is specified, only two lines that have a common endpoint (known as pseudonode) are merged into one continuous line."

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/How_Dissolve_Data_Management_works/00170000005r000000/
"The Unsplit lines parameter can be used to remove endpoints that are common to only two lines and merge the two lines into one continuous line. A common endpoint shared by no more than two lines is also known as a pseudo node."

An endpoint here doesn't mean an "ending point" (vs. the "starting point"); it just means either end of a line.

So make sure you have the "Unsplilt line" checkbox checked to get lines connected with a pseudo node merged, regardless of their "line directions".

Re: Dissolving lines with opposing direcionality

TomSomers — Mon, 26 Mar 2012 11:20:33 GMT

Thanks for the info. The strange thing is that when I processed the data with the "Unsplilt line" checkbox checked I end up with many lines duplicated. It also seems to dissolve the lines through intersections. Very strange.

Re: Dissolving lines with opposing direcionality

DanLee — Mon, 26 Mar 2012 15:36:33 GMT

Could you attach a small sample data that reproduces the issues and describe exactly how you processed to get the strange results (Dissolve and Intersect)?

Re: Dissolving lines with opposing direcionality

TomSomers — Mon, 26 Mar 2012 15:51:24 GMT

Sure, the attached file contains a piece of what I'm trying to dissolve. It contains hydro data which I'm trying to dissolve based on a field called Feat_Code. I used the dissolve tool in the arc toolbox and I'm using Arc 9.3.

I checked the "Unsplit Lines" box and also selected most of the other attributes in the "Statistics Field" option with their appropriate statistic types.

Re: Dissolving lines with opposing direcionality

DanLee — Mon, 26 Mar 2012 18:13:04 GMT

Tom,

Thank you for providing the test data. ArcGIS 9.3 does have a bug in Dissolve, not doing UNSPLIT correctly. I can't think of an easy workaround. Sorry about the problem you run into.

I have tested in ArcGIS 10 SP3 and Dissolve seems to work correctly; I didn't verify every resulting feature, but a few that didn't work in 9.3. Many features remain unchanged even they have common feature code because they are not connected.

If you can find a colleague who has ArcGIS 10 and can run the process for you, that would be great. Otherwise, I hope you would upgrade to ArcGIS 10 in the near future.

Re: Dissolving lines with opposing direcionality

Jong-GeunKim — Sun, 06 May 2012 11:19:48 GMT

This post clearly explained what I wanted to know. Thanks a lot.

I am wondring if there is any way for the UNSPLIT (or other method) to honor the directions of pre-dissolve lines so that the resulting dissolved line does not flip the directionality of the originals? This turned out critically important since the lines of my road network are digitized along the driving direction. So I would like to maintain the direction of the original lines while reducing the network size by using UNSPLIT.

Any comments or recommendations are appreciated.

J-G Kim

Re: Dissolving lines with opposing direcionality

DanLee — Mon, 07 May 2012 15:32:46 GMT

Thanks for the good question. I think the tool could provide an option for additional analysis to preserve existing line direction as long as a set of connected lines are all in the same direction. I will propose the enhancement for a future release. If you like, please submit an enhancement request through Esri Support as well.

Re: Dissolving lines with opposing direcionality

geodanadmin — Fri, 14 Dec 2012 08:05:49 GMT

Fix by rebuilding geometry in arcobjects & perform ITopologicalOperator.Simplify. (TODO: set MAware, ZAware, M's and/or Z's)

        private IFeatureClass FixArcGisDoubleLinesBug(IFeatureClass unsplitFeatureClass)
        {
            IFeatureCursor updateFeatureCursor = unsplitFeatureClass.Update(null, false);
            try
            {
                for (IFeature feature = updateFeatureCursor.NextFeature(); feature != null; feature = updateFeatureCursor.NextFeature())
                {
                    IGeometry srcGeometry = feature.ShapeCopy;
                    var srcPointCollection = srcGeometry as IPointCollection;

                    IPath targetPath = new PathClass();
                    var targetPointCollection = targetPath as IPointCollection;
                    object missing = Type.Missing;

                    for (int i = 0; i < srcPointCollection.PointCount; i++)
                    {
                        IPoint aPoint = new PointClass();
                        aPoint.X = srcPointCollection.Point.X;
                        aPoint.Y = srcPointCollection.Point.Y;
                        targetPointCollection.AddPoint(aPoint, ref missing, ref missing);
                    }

                    IPolyline targetPolyline = new PolylineClass();
                    var targetPolylineGeometries = targetPolyline as IGeometryCollection;
                    targetPolylineGeometries.AddGeometry(targetPath as IGeometry, ref missing, ref missing);

                    ITopologicalOperator topologicalOperator = targetPolyline as ITopologicalOperator;
                    topologicalOperator.Simplify();

                    feature.Shape = targetPolyline;

                    updateFeatureCursor.UpdateFeature(feature);

                }
            }
            finally
            {
                if (updateFeatureCursor != null)
                    Marshal.FinalReleaseComObject(updateFeatureCursor);
            }