Global planner ignores footprint

edit

That is different. One thing is for the global planner to get close to the obstacles and the other thing is for the planner to completely ignore the footprint and plan in an impossible route

I just read the answer. What a shitty planner then this global planner in ROS, unbelievable and no documentation that states such an important feature. Wasted my time instead of just writing a new one...

@EdwardNur your lack of understanding reflects poorly on something/someone, and that thing is not the ROS global planner. I encourage you to understand the topic more clearly before you speak negatively about someone's work. Good luck generating anything nearly as robust as what ROS has to offer, I imagine it will take you a while...

@JackB Did I tell something about ROS? ROS is not the global planner, I believe you should educate yourself :) I just meant that the planner is a piece of crap if it does not do even a sanity check and blindly sends a stupid path.

I will respond to this last comment just so future people reading this will not be misinformed.

It is YOUR improper configuration of the global planner that led to the results you see. There are thousands of users with a properly configured global planner that do not experience the poor results you had. Good luck.

@JackB Yes that is exactly the reason why you keep answering to these question, surely it is my improper usage of the planner, lol. You are talking about this crappy global planner as it was some legendary library but no, calm down, this is just a global planner that every student in their computer science degree courses will do.

Also I am commenting here last time for any future people that will come up with the similar problem:

Do the sanity check yourself at the very last steps of the planner to check wether the planner is feasable. @JackB says this is an improper configuration but I have decided to give this a chance and searched for the solution and there is nothing to be configured to include this sanity check, this feature simply does not exist.

No wonder that ROS2 navigation ditched this planner as a default one.