-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
nested data #72
Comments
before I dive into this, given your progress with anglr and your own developments, and the development in geovctrs / geom, would it be better to get a fully formed design for what this 'nested data' will look like, so it can help the whole spatial ecosystem? |
Maybe, I definitely feel responsibility to do this - but the fact is I still don't have a "complete landscape" vision - I've really settled into building componentry, and leveraging data frame nesting and splitting and grouping - I'm much more into the tibble/tidyr approach than you are I see. I like your But, why are you working with sf anyway? Why not store the coordinates and the track attributes together in a df as is perfectly natural? Don't you end up creating work having to find the |
Oh it's googlepolylines yeah? So that is totally streamlined and necessary, and you have to use a separate mechanism for the aesthetics. And how you have it is a neat generalization of the SF vertex model, so I think it's perfectly fine - and is something others can easily leverage. |
Oh and sorry I totally forgot about the |
actually, no, not any more. That was my original way of reducing data size as it's sent to the browser, specifically for |
So I'm not fixed to |
Oh right, understood - thanks! |
continuing this discussion
as well as
list_columns
, have alist_data
, orcombine_lists
, or something, which will put all the list columns into a single data.frame column.Will also need the reverse, to
split_lsits
or sommat.And will only allow one-level of nesting.
The text was updated successfully, but these errors were encountered: