Found actual problem. The comparator in the KDTree had search first instead of current. All results now correct and it's about 500% faster now that the tree is navigated properly
Found actual problem. The comparator in the KDTree had search first instead of current. All results now correct and it's about 500% faster now that the tree is navigated properly

franc00018/OfflineReverseGeocode,AReallyGoodName/OfflineReverseGeocode