Closed sckott closed 9 years ago
Good question. It's functionality that seems like it should be in sp
, and given what you said about the package limiting it's scope to reading and writing geo/topojson, not exporting them makes good sense to me.
Cool.
WRT scope: it could change, but also don't want to overlap with what other spatial packages are doing (but honestly, I'm no spatial expert with R, so if you think there's functionality we should add here...)
Ideally I'd submit a PR or issue to sp
(if it was developed on github), because I feel like that's the package where these functions belong. Thoughts? How do you go about submitting an issue to a package on r-forge? Just email the maintainer?
Hmm, never contributed on R-forge. I think it's svn based, not git. I guess I'd ask the maintainer how they want it to be done
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
hey @ateucher Do you want
as.SpatialPointsDataFrame.SpatialPoints
andas.SpatialPointsDataFrame.SpatialLines
exported for users? Or just for internal use?