-
Notifications
You must be signed in to change notification settings - Fork 0
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
Monthly Big 5 Data Requests (2024 Q3) #314
Comments
I added a table with check boxes to help track what was or was not provided by the county. I omitted a check box for SLCo parcels as they send them directly to me when necessary and do not need to be requested. |
I like the improvements @rkelson has made and I'd be happy to keep the ball rolling. |
I don't think SL County needs to be in there for address points, I download them each month from sftp. |
I was not sure how to deal with what we can each individually acquire and what Michael should pull down and que up for the group. I actually pull down the Washington and Utah Co parcels when I need them. I can edit the table to reflect that. |
I am not sure where the white dots are coming from above the check boxes. Feel free to hack at it if you like |
I removed the Parcels Received/Requested check boxes from Utah and Washington county. I pull these down when needed. Just trying to clean up some clutter |
This is closed |
Benefit
By requesting data monthly from the big 5 counties (Weber, Davis, Salt Lake, Utah and Washington), we endeavor to keep our public facing data as up to date as possible.
Acceptance Criteria
Receiving data from the above listed counties will be counted as accepted criteria.
Notes
UGRC's SGID Data Update Schedule (address points, parcels, roads)
Data requests typically happen the first week of the month.
Some counties or datasets are available for download and do not need to be requested. Some counties also send updates when needed (e.g. Salt Lake parcels):
Data Requested from county/Received and Available From L:\agrc\data\county_obtained
January
February
March
Risks
Not receiving the data is a risk, but not one that we can easily mitigate.
Issue Reference
refs #
The text was updated successfully, but these errors were encountered: