GPS navigation fails to create a global path when the target exceeds the global map's dimensions.

[ghhhgfgh]

When using the GPS navigation demo method, the global map has a fixed size of 50 (meters/units). Since the robot is positioned at the center, navigation fails if the destination is outside this boundary, as it cannot create a global path.

Even after increasing the global map size to 100, it remains insufficient for outdoor environments. However, setting the map too large leads to performance issues, as the navigation stack occasionally clears and re-creates the costmap, causing lag and system slowdowns.

[SteveMacenski]

How about using a rolling global costmap? You don't need to represent all of a 10x10km (for example) area at the same time, you just need to have enough for the next point of interest. If you make the costmap the maximum size of the 2 largest consecutive points you'd go through * 2 (for each direction), then you should be good to go. This is what we explain in the GPS tutorial as well.