Skip to content
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

Add ASDAR 2ed comment description to help page #66

Closed
rsbivand opened this issue Nov 10, 2019 · 4 comments · Fixed by #67
Closed

Add ASDAR 2ed comment description to help page #66

rsbivand opened this issue Nov 10, 2019 · 4 comments · Fixed by #67

Comments

@rsbivand
Copy link
Contributor

rsbivand commented Nov 10, 2019

ASDAR 2d, pp. 47-48 description needed in sp help pages and link to rgeos for analysing exterior/interior (pp. 132-133). Still not guaranteed to be valid because shapefiles treat interior rings touching exterior rings differently.

@rsbivand
Copy link
Contributor Author

rsbivand commented Nov 10, 2019

Ping @rsbivand @mdsumner

@edzer
Copy link
Owner

edzer commented Nov 10, 2019

library(sp)
?Polygons

and search for "comment"; see also sf/R/sp.R, and search for comment.

@mdsumner
Copy link

thanks, I see it's documented in rgeos::createSPComment also on rforge only, but can be browsed on the read-only github rforge mirror at https://github.com/rforge/rgeos/blob/master/pkg/man/comment-functions.Rd

@rsbivand
Copy link
Contributor Author

The github mirror is useless, not supported by the maintainer, so by definition not where to go. Read the package help page at https://cran.r-project.org/package=rgeos, and find the maintainer-provided documentation site at http://rgeos.r-forge.r-project.org/index.html where http://rgeos.r-forge.r-project.org/reference/comment-functions.html provides the online version of ?createSPcomment.

@edzer edzer closed this as completed in #67 Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants