idea Tool that disperses lines for overlapping routes. in ArcGIS Pro Ideas

Tool that disperses lines for overlapping routes.

JasonHrabe — Wed, 21 Jul 2010 17:46:43 GMT

We create the map symbology and ArcGIS Server service for our transit department. There are ~ 20 to 25 routes. Along certain busy locations, there can be as many as 9 routes that overlap. Currently we use line offsets to make sure that all routes are visible. This can be tricky, since changing the offset to make a line visible in one location can make it disappear behind another line in a different location, causing a domino effect. It has been suggested to me to use cartographic representations, but we can't do this since we are not the owners of the data. It also doesn't fix the bigger problem of addressing route changes/additions. Since bus service is expanding here, routes are occasionally moved or added, causing us to do a lot of symbology work. I would like to see a tool that disperses line symbology where there are coincident routes, but leaves it as is (on the centerline) when it is the only route.

Re: Tool that disperses lines for overlapping routes.

chaimschwartz1 — Sun, 27 Jul 2014 08:21:27 GMT

This is a huge must for us too, and one important advantage of competing transportation-oriented-gis software.

Re: Tool that disperses lines for overlapping routes.

Anne-MarieGintberg1 — Mon, 01 Dec 2014 07:21:06 GMT

Yes, go for it. Its a big issue for us too. We do have a lot of suggestions for hiking routes, with many overlapping parts.

Re: Tool that disperses lines for overlapping routes.

ErnestoCarreras2 — Thu, 08 Jul 2021 20:15:22 GMT

It is also huge for us at our Transit Department. We have to deal with the same issues as described by @JasonHrabe

Re: Tool that disperses lines for overlapping routes.

wayfaringrob — Tue, 10 Jan 2023 20:20:56 GMT

Yes, I could also see this being useful for trail data -- with a sidepath, for example, that may be mapped in or parallel to the ROW, allow it to cheat to the side as needed. Would probably need to take scale into account for the correct offset at each level. It's like the inverse of clustering -- rather than combining features at smaller scales, make them more distinct.

Sometimes our office will make a copy of the layer and name it *_carto, but again - this relies on manual editing that is not always practical nor possible.