This may be a duplicate suggestion, but I was not able to find anything. I have two situations that I have seen.
When Mowing Mapped Area A it may be abutting / overlap with Mapped Area B. If the core goes from Area A to B because of GPS issue it will call an out of bounds issue. This should not be counted as out of bounds since it is a known mapped area.
When mowing Map A the core will do zero turns to keep it in a tight area, but Map Area B would be used to make the turn since it is a known area.
Suggest allowing known mapped area to be considered as area that are not out of bounds or that can be used for additional navigation capabilities.
I was thinking about this for a bit, and I think there is a problem with your suggestion.
Sometimes there is a really good reason why areas are split up into multiple areas and you REALLY don’t want Yarbo even touching an adjacent area.
Here’s an example I thought up: Mowing Area 1 and Area 2 are adjacent. Today, I only want to mow Area 1 because I have cars, yard equipment, etc. parked in Area 2. I want Yarbo to mow Area 1 in its entirety, but if it strays even a little bit into Area2, it will run into something.
I have snowblower zones set up that way for my driveway. I split up the driveway into multiple areas that I can select depending on if my kids or visitors are home and parked in the driveway.
So at least for me, I would NOT want Yarbo to ever utilize part of an adjacent zone for turning around or whatever.
For Option 1, it would have hit your car anyways because it will travel outside the mapped area with GPS issues and then when it finally has traveled too far it will just stop and say out of bound or collision occurred after it hit your car. This wouldn’t have stopped that. Option 1 is to address GPS issues and trying to get it to resume without me having to do it.
For Option 2, if something is parked within a foot of another zone that too is probably a problem as it will wonder out. My point here is in tight spaces it will zero turn when it has room in an adjacent zone to smart turn but still zero’s and tear up the yard.
Like the others have said, set as an option then, strict to address what you are after and allowed to accommodate this request.
Hi @mike1 Thank you for sharing! We generally don’t recommend overlapping mapped areas, as it can sometimes lead to routing or recognition issues. That said, your idea gives us a different perspective to think about.
