Forum Replies Created
-
AuthorPosts
-
Sonny MohammadzadehParticipant
Looks like I fixed the problem with the at-large states. I used 00 instead of 01 and it worked. The other districts I mentioned still don’t show up.
Sonny MohammadzadehParticipantThanks so much Bill! That’s awesome! There’s a handful of districts that still don’t show up though. None of the at-large states (ak01, mt01, etc), but then a handful of other districts don’t work either (ut04, tx33-36, sc07, nv04, fl26-27, az09), plus a handful that don’t show up on the graph. I think for the at-large states the syntax might be different, but on the other ones I’m not sure.
Sonny MohammadzadehParticipantBill, I wanted to make some activities for my stats students using the recent election data. I’m confused though. I assumed since US_congressional_boundaries was one of the options for lookupboundary, that that meant the districts were provided. I think I’m misunderstanding something here.
Sonny MohammadzadehParticipantHello. I understand that for making state boundaries we need a ‘state’ attribute where we use the state name or abbreviation. What about for the congressional boundaries? That is using lookupBoundary(US_congressional_boundaries,district) what should the entries for the ‘district’ attribute look like? I tried the common abbreviations – e.g. AK-AL, CA-10, NY-19, etc. – but it doesn’t work. It just gives me back “a boundary”. Also, have the districts been updated in the database since PA had there maps redrawn this summer?
-
AuthorPosts