Oh sorry, the module is Geo::Distance

I've kept my work to the closest() method. I have made modifications to get it working properly with DBI. I also added the 'inner radius simplistic calculation' (see the to do list) but there are issues with it. Its not really a radius, but instead its an inscribed square. (The initial test is a circumscribed square). But the inner test cannot be used if you need the actual distances from the centerpoint, which would include sorting the results by distance.

I also added doing both the outer and inner optimizations for arrayref sources, again with the same distance caveat.

I am a mathematician by education, but have no formal training in non-euclidian geometry, so im wary about messing with the various distance calculations at this point.

Geo::Distance has a few recent releases, so looks promising for you. The author is actually a monk, too (bluefeet), but unfortunately inactive for a while.. He also has a section on his website for the module here. Best of Luck!

Seriously though, if the module has a mailing list, use that.

If the bugs are open on it's http://rt.cpan.org page, send patches there.

In all other cases send the patch directly to the author.

I don't think there is any code for communication, just be polite and good natured, and be sure to explain exactly what problem you're fixing, and how you're fixing it.

When sending patches try to follow the coding style of the author, like tabs vs. spaces, or my $self = shift vs my ($self, $param) = @_, and so on. This saves the author some time fixing it up, and the code is readable to them without any work.

Also be sure to use the project's version control system if it has one. svk and darcs have the capability to submit patches via email, and it just works. Other VCSs have their own diff formats, which can be easily applied. When in doubt, send a unified diff, and no other format.

Keep in mind that your work should be appreciated, because it counts. In fact, I think that by simply submitting you've already done your part.

If you feel that the author isn't paying attention, post the patch on your website, and remind them a bit. If the patch is not a specific case, but one that applies to everyone, especially a bug fix, then it should be applied, but do keep in mind that sometimes for reasons of bloat or feature creep your patch might be rejected. If you feel it appropriate, a fork of the project (like Catalyst / Maypole, for example) might be in order.

That's all I've got to say. Thank you for helping out!

Thanks. I checked out that page, and now have a better understanding of the calculations.

Unless im missing something though, i believe that those are the same calculations used in the Geo::Distance module currently.