Re: [R-sig-Geo] maptools, rgdal, rgeos and rgrass7 retiring Monday, October 16
Agreed 100%. I'm blown away by the amount of work and care that you put into helping people use these packages. I never would have completed my dissertation without the willingness to respond thoughtfully to my obviously "noob" questions on this forum. -Original Message- From: R-sig-Geo On Behalf Of Danlin Yu Sent: Tuesday, October 3, 2023 9:36 AM To: r-sig-geo@r-project.org Subject: Re: [R-sig-Geo] maptools, rgdal, rgeos and rgrass7 retiring Monday, October 16 Dear Dr. Roger Bivand: I echo this comment and sentiment. Dr. Roger Bivand is not only a great scholar and generous contributor, maintainer to the R-spatial task force, but also a fantastic mentor to us all. No amount of "thank you" would be sufficient. Best, Danlin On 10/3/2023 5:22 AM, Gilberto Camara wrote: > Dear Roger > > Your enormous and generous dedication to R-spatial is amazing and a model to > all of us!! Many, many thanks! > > All the best > Gilberto > > Prof Dr Gilberto Camara > Senior Researcher > National Institute for Space Research (INPE), Brazil > https://gilbertocamara.org/ = > > >> On 3 Oct 2023, at 10:15, Roger Bivand wrote: >> >> The legacy R spatial infrastructure packages maptools, rgdal and rgeos will >> be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been >> replaced by rgrass and will be archived with the retiring packages. >> >> The choice of date matches the previously announced archiving during October >> 2023, and the specific date matches the release schedule of Bioconductor >> 3.18 (some Bioconductor packages depend on retiring packages). >> >> sp_2.1-0 was published October 2, 2023, dropping all dependencies on the >> retiring packages. sp will continue to be available and maintained, but not >> developed further. Users of sp classes may continue to make use of them, but >> will have to use sf or terra to read, write or manipulate objects with >> coercion (for a guide to coercion, see >> https://cran.r-project.org/web/packages/rgrass/vignettes/coerce.html). >> >> Information about the evolution project may be found in reports and >> resources at https://r-spatial.github.io/evolution/; a recent blog by Jakub >> Nowosad may also be useful as an overview of what has been going on: >> https://geocompx.org/post/2023/rgdal-retirement/. For more detail, see >> https://r-spatial.github.io/evolution/ogh23_bivand.html and a video >> recording of this presentation https://av.tib.eu/media/63141 (August 28). >> >> All directly affected package maintainers have been alerted to the impending >> changes, some in December 2022, most others in March-April 2023. Many have >> already updated their packages on CRAN - thank you for your understanding! >> The remainder received github issue comments and email reminders in the last >> ten days, and will receive final notices to update by October 9. >> >> On R-universe, builds of packages archived on CRAN are dropped automatically >> (https://github.com/r-universe-org/help/issues/286). Read-only github >> mirrors of archived packages will remain available in principle while github >> exists (https://github.com/r-hub/rhub/issues/568), for example >> https://github.com/cran/rgdal. Other binary builds (Debian, Fedora, Ubuntu) >> have been alerted; support at Anaconda has been alerted. >> >> On CRAN, the retired packages will continue to be available as source >> packages on https://cran.r-project.org/src/contrib/Archive. maptools, rgdal >> and rgeos also retain their R-forge repositories, which may be used to >> retrieve functions for adding to other packages. >> >> A snapshot of Windows and macOS binary packages may be found on >> https://github.com/r-spatial/evolution/tree/main/backstore. >> >> Please raise questions by replying to this post, or as issues on >> https://github.com/r-spatial/evolution. >> >> >> -- >> Roger Bivand >> Emeritus Professor >> Norwegian School of Economics >> Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway roger.biv...@nhh.no >> ___ >> R-sig-Geo mailing list >> R-sig-Geo@r-project.org >> https://stat.ethz.ch/mailman/listinfo/r-sig-geo > ___ > R-sig-Geo mailing list > R-sig-Geo@r-project.org > https://stat.ethz.ch/mailman/listinfo/r-sig-geo -- ___ Danlin Yu, Ph.D. Professor of GIS and Urban Geography Department of Earth & Environmental Studies Montclair State University Montclair, NJ, 07043 Tel: 973-655-4313 Fax: 973-655-4072 Office: CELS 314 Email: y...@montclair.edu webpage: csam.montclair.edu/~yu Academic Editor and Editorial Board Member: Remote Sensing Special Issues: https://www.mdpi.com/journal/remotesensing/special_issues/UPES_Big_Data_ra Editor's Choice Articles: https://www.mdpi.com/journal/remotesensing/editors_choice Most Cited & Viewed: https://www.mdpi.com/journal/remotesensing/most_cited
Re: [R-sig-Geo] Calculating median age for a group of US census blocks?
This is correct on the second question, at least for more recent censuses. On the first question, imagine a block where the ages of three individuals are 60, 50, and 40, and another one where the ages are 20, 20, and 20. Using your approach you would have 50 * 3 = 150 for the first block, and 20*3 = 60 for the second block. The median of 60 and 150 is 105. Even dividing that by three you get 35, which is not the correct median age (30). -Original Message- From: R-sig-Geo On Behalf Of Josiah Parry Sent: Monday, August 7, 2023 2:38 PM To: Kevin Zembower Cc: r-sig-geo@r-project.org Subject: Re: [R-sig-Geo] Calculating median age for a group of US census blocks? Hey Kevin, I don't think you're going to be able to get individual level data from the US Census Bureau. The closest you may be able to get is the current population survey (CPS) which I believe is also available via tidycensus. Regarding your first question, I'm not sure I follow what your objective is with it. I would use a geography of census block groups as the measure of median for census block groups. Otherwise it is unclear how you are defining what a "group of blocks" is. On Mon, Aug 7, 2023 at 2:34 PM Kevin Zembower via R-sig-Geo < r-sig-geo@r-project.org> wrote: > Hello, all, > > I'd like to obtain the median age for a population in a specific group > of US Decennial census blocks. Here's an example of the problem: > > ## Example of calculating median age of population in census blocks. > library(tidyverse) > library(tidycensus) > > counts <- get_decennial( > geography = "block", > state = "MD", > county = "Baltimore city", > table = "P1", > year = 2020, > sumfile = "dhc") %>% > mutate(NAME = NULL) %>% > filter(substr(GEOID, 6, 11) == "271101" & > substr(GEOID, 12, 15) %in% c(3000, 3001, 3002) > ) > > ages <- get_decennial( > geography = "block", > state = "MD", > county = "Baltimore city", > table = "P13", > year = 2020, > sumfile = "dhc") %>% > mutate(NAME = NULL) %>% > filter(substr(GEOID, 6, 11) == "271101" & > substr(GEOID, 12, 15) %in% c(3000, 3001, 3002) > ) > > I have two questions: > > 1. Is it mathematically valid to multiply the population of a block by > the median age of that block (in other words, assign the median age to > each member of a block), then calculate the median of those numbers > for a group of blocks? > > 2. Is raw data on the ages of individuals available anywhere else in > the census data? I can find tables such as P12, that breaks down the > population by age ranges or bins, but can't find specific data of > counts per age in years. > > Thanks for your advice and help. > > -Kevin > > ___ > R-sig-Geo mailing list > R-sig-Geo@r-project.org > https://stat.ethz.ch/mailman/listinfo/r-sig-geo > [[alternative HTML version deleted]] ___ R-sig-Geo mailing list R-sig-Geo@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-geo ___ R-sig-Geo mailing list R-sig-Geo@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-geo
