-
Notifications
You must be signed in to change notification settings - Fork 59
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
geojsonio2 or re-write for v1.0? #165
Comments
I've been having similar thoughts @sckott. Quick thoughts on your ideas:
I'm not sure many people use geojson lists... I support them in rmapshaper, but I'd bet not many people go that route. I'd be happy to drop them - could remove them in a branch and run some revdep checks?
I think we should still support them, but perhaps we could just convert them to sf and then do the conversion to geojson. Possobly using
Probably, but hard to say right now. There are some I don't even know what to do! And I too get confused/forget what functions do what...
Two things come immediately to mind - |
|
I often lose track/get confused about what different functions do (what they take as input and give as output), and since v0.1 in 2015 sf has come along and other changes in the spatial pkg landscape. Maybe it's worth considering a re-thinking of the package, its purpose, its role in the suite of spatial pkgs. An overall goal i think would be to simplify, probably drop the input/output options that aren't used very much
ideas
thoughts @ateucher ? anyone else?
The text was updated successfully, but these errors were encountered: