# Automatically Connect Adjacent Work Areas **URL:** \ **Category:** Suggestion and Feature Requests\ **Tags:** mapping\ **Created:** [June 25, 2026, 2:26am UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703 "2026-06-25T02:26:03Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![srachele11796](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/srachele11796/32/4706_2.png) [@srachele11796](https://forum.yarbo.com/u/srachele11796)\ **Post date:** [June 25, 2026, 2:26am UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/1 "2026-06-25T02:26:03Z")
Currently, users must create a separate path between work areas, even when those areas directly touch each other. I would like Yarbo to automatically recognize when two areas share a boundary and allow travel between them without requiring a manually created path. When transitioning between adjacent areas, Yarbo could cross at any point along the shared boundary, selecting the most efficient location based on its current position and route. An additional benefit would be obstacle avoidance. If Yarbo’s preferred crossing point is temporarily blocked by a vehicle, person, equipment, or other obstacle, it could simply choose another accessible point along the shared boundary instead of stopping or requiring a predefined path. This would simplify map creation, reduce setup time, eliminate unnecessary connector paths, and make navigation between adjacent areas more reliable and flexible across all Yarbo modules and tasks. ---
**Author:** ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)\ **Post date:** [June 25, 2026, 3:58am UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/2 "2026-06-25T03:58:30Z")
I would caution that I think this would be fine for overlapping areas, but not boundaries that are merely close or touching. I’d much rather define a boundary crossing area for that situation but an overlapping area should be easily justified to be safe to cross at any point in the overlap. ---
**Author:** ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)\ **Post date:** [June 25, 2026, 7:43am UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/3 "2026-06-25T07:43:11Z")
Thanks for sharing your suggestion! I’ve passed it along to our product team for consideration. We appreciate your feedback! ---
**Author:** ![srachele11796](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/srachele11796/32/4706_2.png) [@srachele11796](https://forum.yarbo.com/u/srachele11796)\ **Post date:** [June 25, 2026, 12:59pm UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/4 "2026-06-25T12:59:19Z")
Agreed! I make all of my areas overlap slightly to ensure there isn’t a gap. ---
**Author:** ![rgloverii](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/rgloverii/32/956_2.png) [@rgloverii](https://forum.yarbo.com/u/rgloverii)\ **Post date:** [June 25, 2026, 4:42pm UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/5 "2026-06-25T16:42:19Z")
I think there are a lot of cases where Yarbo really needs to follow a pre-established path to traverse from Area A to Area B. There may be unintended consequences if Yarbo can just cross wherever it randomly decides to. ---
**Author:** ![srachele11796](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/srachele11796/32/4706_2.png) [@srachele11796](https://forum.yarbo.com/u/srachele11796)\ **Post date:** [July 9, 2026, 2:30am UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/6 "2026-07-09T02:30:35Z")
I have been trying to come up with a time where crossing from area a to area b at any point would be a bad thing. If both perimeters are overlapped slightly so all of that area will be mowed, the places that you would have an issue with crossing would have a no go zone, right? Maybe I am misunderstanding what you mean or just I just don’t have any of these instances in my yard. ---
**Author:** ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)\ **Post date:** [July 9, 2026, 3:36am UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/7 "2026-07-09T03:36:05Z")
> [@srachele11796](#): > > just I just don’t have any of these instances in my yard. I think it’s the latter here. Another example might be a thin fence where the boundary lines might slightly touch and with the change in algorithms, it may think “oh this touching part is safe” and then run into a fence. Could also be on hills/slopes/small valleys/wash outs/etc and crossing at this angle could be less than optimal or put the unit into track slippage, but is fine running parallel along the boundary for the perimeter passes, but perpendicular to the boundary is dangerous. Yes you could possibly put a NGZ here, but they have a minimum size and will also change the mowing pattern around it. Which if it’s a wash out/ravine or something that might be worse because it’s doing risky maneuvers around the NGZ instead of just driving straight. ---
**Author:** ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)\ **Post date:** [July 9, 2026, 12:00pm UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/8 "2026-07-09T12:00:00Z")
@bryan.wheeler nailed it. The breakup of my areas is partially determined by slopes and hazards. Unrestricted crossing could be very bad. Another approach might be a to draw a line in overlaps (similar to trimming selections). Random crossing would be permitted anywhere along that line. ---
**Author:** ![rgloverii](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/rgloverii/32/956_2.png) [@rgloverii](https://forum.yarbo.com/u/rgloverii)\ **Post date:** [July 9, 2026, 12:54pm UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/9 "2026-07-09T12:54:59Z")
Another good and obvious real world example would be two grass cutting areas in your front yard. They are zone 1 and zone 2. In between them is your driveway. The driveway is _also_ a zone, but only for snowblowing. It would be bad for Yarbo to randomly drive through the driveway to get from zone 1 to zone 2, potentially running into cars and other things along the way. The desire would be for Yarbo to _ **only** _ traverse the driveway via a pre-established pathway that is known to be safe. ---
**Author:** ![steve](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/steve/32/816_2.png) [@steve](https://forum.yarbo.com/u/steve)\ **Post date:** [July 9, 2026, 4:10pm UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/10 "2026-07-09T16:10:41Z")
…or at the very least, be constrained to areas attributed to the current toolhead. ---
**Author:** ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)\ **Post date:** [July 9, 2026, 4:18pm UTC](https://forum.yarbo.com/t/automatically-connect-adjacent-work-areas/6703/11 "2026-07-09T16:18:06Z")
You and your logic! 😂