Nice! You already have a working algorithm for that ?
I've done some googling few months ago and I couldn't find anything on this topic, so I just gave up at the time.

Yes, I have, don't give up and wait for me to finish a new release, and I will explain how this feature solves a lot of works when you work with map providers.

Hey Karam,
Thanks a lot for your hard work and thanks for adding the request feature 😄🙏
I just got time to try the getOrderByNearestNeighbor function and it's working as expected 👍
But there are few points I wanted to mention:

1. Currently with the way the setPoints is implemented, it's not possible to pass eloquent models or database rows that include a longitude and latitude attribute/column, as the setPoints function only accepts an array of coordinates in format of [lat, lng]. One may say extracting the coordinates from eloquent and passing it to setPoints is no problem and I agree with that, but the thing is, after getOrderByNearestNeighbor returns the result, you'd have no idea which coordinate belongs to which model/record. So you'd have to write a loop including where clauses to trace back the coordinates to the relevant model
2. I'm getting a Non static method 'setMainPoint' should not be called statically.intelephense(1036) just wanted to put this out there.
3. I think getOrderByNearestNeighbor should be renamed to getNearestNeighbors and maybe it could also take few arguments like :

getNearestNeighbors(
 $number_of_returned_neighbors, // this is to limit number of points returned
 $order_by = 'nearest', // this is to give ability to change order, maybe they want the farthest neighbors
 $include_main_point = false // this is to give option for whether to include the MainPoint in the results or not because currently it's included by default
)

4. Also this idea occurred to me, maybe the NearestNeighbors function could also take a radius argument, to find points upto a certain radius (in km), because for example you may want to show the user the nearest restaurants and if there is no radius limitation, some restaurants stored in the database might be located in another city and you'd only want to show the user points that are located in their resident area.

I hope this was a useful feedback. Sorry If I'm all talk and not much of a contributor 😅 I'm way too of a noob to contribute to an open source project effectively

Hello Hassan and thanks for the comments,
1- In fact, if you look at my v2.2.0 pull request, you will find that I have already planned and I'm adding now what you are actually saying in relation to the order of the nearest neighbor algorithm in order to take the order from the farthest to nearest and also in relation to determining whether the point lies in a region or a radius.
2- I'm working now to add scopes to the models, so you can pass points as an eloquent or query builder.
3 - if setMainPoint still gives you an exception please mark this as an issue with description, so I can fix it.

There is no difficulty in implementing some algorithms, but the difficulty lies in returning results to the client code
If you have the time and ability, I welcome any contribution you make.