agrc / porter

UGRC tracks the additions, replacements, and deletions of SGID items (in the broadest sense of add, replace, or delete) through issues in this repository.
https://gis.utah.gov/documentation/policy/
MIT License
2 stars 0 forks source link

Add Utah US Congressional Districts 2022 to 2032 #162

Closed gregbunce closed 2 years ago

gregbunce commented 2 years ago

Summary

Background

Recently, the Utah Legislative body voted to approve/pass the US Cong Dist created by the Utah Legislative Redistricting Committee. Much like in 2000, there are 4 districts in Utah. These districts show where the 4 Utah Congressmen represent our great state in DC.

The data should be available in

1 Check [x] all the areas where you expect the data to show up.

The data is of high quality

Where is the data source

Choose one.

Action items

  1. Assign a person who should complete the task by replacing name with their github @name.
  2. Check [x] the box when the task is completed and add the date of completion.
  3. ~Strike~ out all items that do not apply.

:robot: Automation validation

  1. Assign yourself or someone to check the item by replacing name with their github @name.
  2. Check [x] the box and add the date of verification 2020/01/01 when the task is verified.
  3. ~Strike~ out all items that do not apply.

Notification

Group Task Assignments

  1. Check [x] the box when you have assigned all the tasks relevant to your group.
stdavis commented 2 years ago

I removed the farm from AGOL task since the source of this data will be internal.

gregbunce commented 2 years ago

we should work through any concerns here in the comments before we rename the existing layers (as outlined above).

also, I'd like to use the same naming and renaming convention for the other 3 layers we'll be introducing in porter soon (utah state house; utah state senate, utah school board). the boundaries for these four, collective, layers were recently adopted by the utah leg and signed off on by the gov. they complete the once-every-10-years data that the state of Utah is responsible for during redistricting.

the whole idea of adding the end date, is to make the dates in the layer name make more sense. to me, the single, beginning date is super confusing.

these are the internal layers I'm proposing we rename by adding the end dates: image

and here are their names in the agol items table where i propose we add the end dates as well (aka: how they get named in the public-facing data),: image

steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 3 out of 3 tasks :+1:
@mheagin has completed 1 out of 3 tasks :no_entry:
@stdavis has completed 1 out of 2 tasks :no_entry:
@steveoh has completed 0 out of 4 tasks :no_entry:
@jacobdadams has completed 0 out of 1 tasks :no_entry:
@rkelson has completed 0 out of 1 tasks :no_entry:
gregbunce commented 2 years ago

the task of renaming these layers has moved to a separate, new porter issue (167).

steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 3 out of 3 tasks :+1:
@mheagin has completed 1 out of 3 tasks :no_entry:
@stdavis has completed 1 out of 2 tasks :no_entry:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

The name for this layer should have Utah in front of it.

This website commit should be reverted once this is corrected.

gregbunce commented 2 years ago

@stdavis can I add "Utah" in front of the published name in the meta agol items table for this layer? aka: will that kick off the processes to rename the agol data - and also not blow anything else up? image

stdavis commented 2 years ago

@gregbunce Changing the value in the AGOL_PUBLISHED_NAME field will not mess anything up but it will not automatically update the corresponding AGOL item either. You'll have to do that manually.

jacobdadams commented 2 years ago

Auditor will update the title if it's changed in the metatable ☝️

gregbunce commented 2 years ago

thanks for the clarification, @stdavis and @jacobdadams
i renamed the layer in the metastable and now i'll watch the magic happen.
I also updated the info above in this porter issue to match the new name (the addition of 'Utah').

gregbunce commented 2 years ago

/remind me on 12/3/2021 to update the gis.utah.gov data page to match the new name (so the URL to opendata works)

github-actions[bot] commented 2 years ago

@gregbunce set a reminder for 12/3/2021

jacobdadams commented 2 years ago

The AGOL name was changed to Utah US Congress Districts 2022 to 2032 in this morning's Auditor run 👍

gregbunce commented 2 years ago

pull request to fix ugrc data page link - adding utah back into the layer name.

gregbunce commented 2 years ago

@eneemann do you know if sweeper has checked the new political district layers?

eneemann commented 2 years ago

Yeah, they were swept on 20 Nov. The metadata could be improved, the 2 issues below were identified. Otherwise, they looked good.

  1. Summary is longer than Description!
  2. Description is missing link to gis.utah.gov data page.
mheagin commented 2 years ago

We need to update the download link for the Geodatabase and Shapefiles, they are still going to the 2012 data

gregbunce commented 2 years ago

@mheagin are you able to resolve the two issues erik pointed out about the metadata for the 4 new political district layers? it would only need fixing in the Internal database metadata (aka: ArcCatalog or Pro). maybe just switch the summary and description and then add a link to the open data URLs. let me know if you are swamped and i'll take a shot at it.

Yeah, they were swept on 20 Nov. The metadata could be improved, the 2 issues below were identified. Otherwise, they looked good.

  1. Summary is longer than Description!
  2. Description is missing link to gis.utah.gov data page.
mheagin commented 2 years ago

Just looking at that, I can add the web link. Not sure about the summary and description they look close but Desc look longer? metadata

gregbunce commented 2 years ago

yeah, that's a little confusing to me, too. maybe @eneemann or @jacobdadams can shed light on that. also, maybe that piece is just fine. but, adding the links would be good. maybe that's all we need to do for these.

also, for reference, here's the ugrc metadata policy

mheagin commented 2 years ago

I could refine the summary a little more and move the parts about it creation to the description.

eneemann commented 2 years ago

I think that is more of a warning that the summary and description might be switched around. The links are more important.

On Thu, Dec 2, 2021, 13:26 Greg Bunce @.***> wrote:

yeah, that's a little confusing to me, too. maybe @eneemann https://github.com/eneemann can shed light on that. also, maybe that piece is just fine. but, adding the links would be good. maybe that's all we need to do for these.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/agrc/porter/issues/162#issuecomment-984974440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJEOB7JM5M4IOXCXVH6HF43UO7I5XANCNFSM5IKO64PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

mheagin commented 2 years ago

Take a look now. Is this better? Summary

This feature class represents 4 Congressional Districts Utah currently comprises for purposes of electing members to the US House of Representatives and defining constituent areas for each seat.

Description

This dataset includes the political districts used for the United States Congressional districts in Utah (US House of Representatives). The US Congress Districts 2022 to 2032 will be used for election purposes beginning January 1, 2022. Elected officials began representing these districts in January 2023. These boundaries supersede the US Congressional Districts that were used in 2012-2021Statewide Political District Boundaries are drawn by the Utah Legislature and adopted into state law as part of the decennial redistricting process that began in 2021. These districts represent US House of Representatives (Congressional) Districts as per Census Block Assignment file enrolled with HB2004.For information and downloads on all political districts check UGRC data page https://gis.utah.gov/data/political/2022-2032-house-senate-congressional-districts/

gregbunce commented 2 years ago

it looks good to me. thanks, @mheagin are you able to do that for the reaming 3 political datasets? thanks again

mheagin commented 2 years ago

If everyone is fine with that wording I will change the others too.

mheagin commented 2 years ago

I have updated all the political districts metadata.

github-actions[bot] commented 2 years ago

:wave: @gregbunce, on to update the gis.utah.gov data page to match the new name (so the URL to opendata works)

steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 2 years ago

conductor results for tasks - 162

check status
gregbunce has completed 5 out of 5 tasks :+1:
mheagin has completed 3 out of 3 tasks :+1:
stdavis has completed 2 out of 2 tasks :+1:
@steveoh has completed 0 out of 4 tasks :no_entry:
jacobdadams has completed 1 out of 1 tasks :+1:
nathankota has completed 1 out of 1 tasks :+1:
@rkelson has completed 0 out of 1 tasks :no_entry:
gregbunce commented 2 years ago

i propose we close this out. any objections?