For any following pairwise_distance-OMG-parallelism-is-tough-in-Python thing, @dimpase solved it — so grateful! 
https://github.com/oliviaguest/pairwise_distance/issues/2 …
-
-
I'm going to write this thing in serial code in C now just for "fun".

-
step 1: to do geopy.distance.great_circle(a,b).km in C :-)
-
hehehe yes I am actually going way slower because I'm struggling with remembering C https://en.wikipedia.org/wiki/Haversine_formula …
-
Looks like there's something from OSGeo that might be useful? You may have already found this. https://github.com/OSGeo/proj.4/wiki/GeodesicCalculations …
-
omg nice!!

-
good catch, although no docs for the library interface. one has to dig into geod source...
-
I need great_circle so I used this and all done!

https://rosettacode.org/wiki/Haversine_formula#C … cc @usethespacebar — promise to try and learn some Cython... -
but I can't promise for this project as the C code is already loading and saving csvs. This was so so so much easier C > Python for this!
End of conversation
New conversation -
-
-
r u working behind a firewall you can't ssh through?
-
OMG OK wait and I will.



-
this still has to cope with like 50 million data points though
-
I took this literally and based on the 350k points in my postgres test this would 'only' take 10.5 years on my machine
. -
it's literal
-
I really do have tons of points, I could get the literal exact number if you want soon
this is why C makes so much sense
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
