We have yet to flush out tract and block data. So we don't have any knowledge to impart on this. Sorry.
Todd McNeeley Programmer, Information Management Team Development [email protected] | 573-884-3297 direct | 573-219-8341 mobile Tiger Institute for Health Innovation | www.tiger-institute.org PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL -----Original Message----- From: Gpc-dev [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, January 9, 2017 2:56 PM To: [email protected] Subject: Gpc-dev Digest, Vol 35, Issue 25 Send Gpc-dev mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://listserv.kumc.edu/mailman/listinfo/gpc-dev or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Gpc-dev digest..." Today's Topics: 1. geocoding: how to join at tract, census block resolution? (Dan Connolly) 2. Fwd: RE: geocoding: how to join at tract, census block resolution? (Thomas Mish) ---------------------------------------------------------------------- Message: 1 Date: Mon, 9 Jan 2017 20:38:02 +0000 From: Dan Connolly <[email protected]> To: "[email protected]" <[email protected]> Cc: "<[email protected]>" <[email protected]> Subject: geocoding: how to join at tract, census block resolution? Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" Hi Dave, More questions! I'm copying gpc-dev so we can all learn together. Before you reply all, note the public archive http://listserv.kumc.edu/pipermail/gpc-dev/ I'm working with Maren and Sravani on this stuff. Joining on zip code was straightforward: we used the zcta5 column of acs_20135a/zcta_860/ge.00_file.dat.gz. But now we're trying to join on tract and census block. What columns of acs_20135a/blck_grp_150/ge.00_file.dat.gz and acs_20135a/tract_140/ge.00_file.dat.gz should we use? What are their primary key columns? Which documentation would tell us this? BLKGRP looks like a single-digit number; it's clearly not a unique key to the blck_grp_150 data. TRACT is a bigger number, but it's not a unique key to tract_140 either. It seems to be unique within state, though. Is that right? Should we join TRACT_ID and ST_ABRV from geocoded_kumc.txt with TRACT and STUSAB of tract_140? Have any other GPC sites figured this out yet? MU? UTHSCSA? For reference, these are the columns of our kumc_geocoded.txt data: 'OID,Join_Count,TARGET_FID,Loc_name,Status,Score,Match_type,' 'X,Y,Match_addr,DISP_LON,DISP_LAT,SIDE,' 'ARC_Address,ARC_City,ARC_State,' 'ARC_Zip,ADDRESS,CITY,STATE,ZIP,New_X,New_Y,ID,BLOCK_ID,' 'FIPSST,FIPSCO,FIPSSTCO,TRACT_ID,ST_ABRV,CO_NAME,ST_NAME context: https://informatics.gpcnetwork.org/trac/Project/ticket/140 https://informatics.gpcnetwork.org/trac/Project/ticket/350 -- Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20170109/0fadb97a/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 09 Jan 2017 20:55:30 +0000 From: Thomas Mish <[email protected]> To: GPC STANDARDS <[email protected]> Subject: Fwd: RE: geocoding: how to join at tract, census block resolution? Message-ID: <cy1pr06mb23007c0c87ef18e601831e4eb1...@cy1pr06mb2300.namprd06.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Baker-McAlister Geoffrey I <[email protected]> Sent: Monday, January 9, 2017 2:49:35 PM To: Thomas Mish Subject: RE: geocoding: how to join at tract, census block resolution? Hey Tom, So, this is what I was relaying to you and Debbie last Friday. There are 5 levels in the US Census hierarchy: 1. State (two digit - 55 for WI) 2. County (three digit - 045 for Dane) 3. Tract (6 digit - I don't have a good example, but you get the idea) 4. Block Group (1 digit) 5. Block (I think 2 digit, honestly, I don't know for sure. I hardly ever work with blocks) When someone says, "give me the block group of 301 S. Westfield Rd, Madison WI, 53717," what they are really asking for is the concatenation of 1, 2, 3 and 4. If you are only given 4, it will not tell you anything. Geoff From: Thomas Mish [mailto:[email protected]] Sent: Monday, January 09, 2017 2:42 PM To: Baker-McAlister Geoffrey I Subject: Fwd: geocoding: how to join at tract, census block resolution? Geoff Is there any guidance or words of wisdom you could offer to other groups looking at this problem. TM Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Gpc-dev <[email protected]<mailto:[email protected]>> on behalf of Dan Connolly <[email protected]<mailto:[email protected]>> Sent: Monday, January 9, 2017 2:38:02 PM To: [email protected]<mailto:[email protected]> Cc: <[email protected]<mailto:[email protected]>> Subject: geocoding: how to join at tract, census block resolution? Hi Dave, More questions! I'm copying gpc-dev so we can all learn together. Before you reply all, note the public archive http://listserv.kumc.edu/pipermail/gpc-dev/ I'm working with Maren and Sravani on this stuff. Joining on zip code was straightforward: we used the zcta5 column of acs_20135a/zcta_860/ge.00_file.dat.gz. But now we're trying to join on tract and census block. What columns of acs_20135a/blck_grp_150/ge.00_file.dat.gz and acs_20135a/tract_140/ge.00_file.dat.gz should we use? What are their primary key columns? Which documentation would tell us this? BLKGRP looks like a single-digit number; it's clearly not a unique key to the blck_grp_150 data. TRACT is a bigger number, but it's not a unique key to tract_140 either. It seems to be unique within state, though. Is that right? Should we join TRACT_ID and ST_ABRV from geocoded_kumc.txt with TRACT and STUSAB of tract_140? Have any other GPC sites figured this out yet? MU? UTHSCSA? For reference, these are the columns of our kumc_geocoded.txt data: 'OID,Join_Count,TARGET_FID,Loc_name,Status,Score,Match_type,' 'X,Y,Match_addr,DISP_LON,DISP_LAT,SIDE,' 'ARC_Address,ARC_City,ARC_State,' 'ARC_Zip,ADDRESS,CITY,STATE,ZIP,New_X,New_Y,ID,BLOCK_ID,' 'FIPSST,FIPSCO,FIPSSTCO,TRACT_ID,ST_ABRV,CO_NAME,ST_NAME context: https://informatics.gpcnetwork.org/trac/Project/ticket/140 https://informatics.gpcnetwork.org/trac/Project/ticket/350 -- Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20170109/baf9b42c/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev ------------------------------ End of Gpc-dev Digest, Vol 35, Issue 25 *************************************** _______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
