get_nearest_locations works just across the entire GPX database, which is fine for some uses, but if one is trying to match up all the waypoints against tracks (which could be used for an individual part of a trip), there is no way to just match against a track.
Luckily the fix is trivial, unfortunately it is cut-and-paste since we don't inherit from a more generic track vs tracks object.
This pull request also includes #272, please don't apply both. Just giving you the option to decide if you want the added functionality or just the bug fix
get_nearest_locations works just across the entire GPX database, which is fine for some uses, but if one is trying to match up all the waypoints against tracks (which could be used for an individual part of a trip), there is no way to just match against a track.
Luckily the fix is trivial, unfortunately it is cut-and-paste since we don't inherit from a more generic track vs tracks object.
This pull request also includes #272, please don't apply both. Just giving you the option to decide if you want the added functionality or just the bug fix