-
Notifications
You must be signed in to change notification settings - Fork 284
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
Joins between sf objects and data.frames #372
Comments
Thanks; the first problem is not an error, but indeed annoying, I will look into it. The second problem is not an |
Thank you @edzer. I tested it a little bit and works great. I've also opened a new issue in the |
Now, > full_join2 %>% st_sf
Simple feature collection with 3 features and 2 fields (with 1 geometry empty)
geometry type: MULTIPOLYGON
dimension: XY
bbox: xmin: -84.32385 ymin: 33.88199 xmax: -75.45698 ymax: 36.58965
epsg (SRID): 4267
proj4string: +proj=longlat +datum=NAD27 +no_defs
NAME VALUE geometry
1 Ashe 1 MULTIPOLYGON(((-81.47275543...
2 Surry 4 MULTIPOLYGON(((-80.45634460...
3 Rowan 6 MULTIPOLYGON() substitutes the |
Lately I've been trying to use joins for pairs of sf objects and data.frames and I came across two problematic groups of joins:
When a row exist in a data.frame, but doesn't exist in a sf object. Then, a new row with a
GEOMETRYCOLLECTION
geometry is added.When a data.frame is the main object in join. Then, a new object has a geometry column, but doesn't have a sf class.
My idea is:
MULTIPOLYGON
I'm not sure, if those ideas are the best. What do you think? @edzer @hadley @Robinlovelace
The text was updated successfully, but these errors were encountered: