-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s2_latlng --> s2_lnglat? #69
Conversation
Codecov Report
@@ Coverage Diff @@
## master #69 +/- ##
=======================================
Coverage 91.95% 91.95%
=======================================
Files 35 35
Lines 1938 1938
=======================================
Hits 1782 1782
Misses 156 156
Continue to review full report at Codecov.
|
I now see > ls(2)[grep("lng", ls(2))]
[1] "as_s2_latlng" "s2_lat_lng_rect" "s2_latlng" I will rename |
I'll clean up the names now...I renamed the rect function to |
I like the |
I'll also do the first few release steps on this branch and merge so it's ready for |
@edzer - I know I preached early on about wrapping types to match the S2 names, but it turns out the BigQuery names are more user-friendly, and everything in that world is lng, lat (or x, y). I think a dedicated class for a "point" will be important for optimization later...it's unlikely that point geographies are fast. Keeping the x, y axis order will probably save a lot of headaches...while programming the class I messed up the order way too many times.
I think it's early enough to do a refactor like this...you were right about the point thing all along!