-
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 Rural Data Requests (2024 Q3) #315
Comments
Thanks to @rkelson for suggestions on improving the usefulness of this feature. I have taken it a step further and added the request itself into the matrix. Hopefully this will allow a bit more transparency to the process. |
Looking good. You can probably cross the bridge when you get there but my guess is there needs to be a spot to track the miscellaneous county data that rolls in, off schedule, from the rural counties. |
All rural data for January requested 1/5/2024. -Michael |
Sprint 4 Notes All rural data for February requested 2/5/2024. |
@MichaelAGRC, no need to request address points from Garfield for March, Les sent me an update on 2/15. |
Considering the data received might come well after the data is requested, I've added a comment for the parcels i've processed so I don't keep going crazy. |
This is closed. |
Benefit
By requesting data monthly from select rural counties of Utah, we endeavor to keep our public facing data as up to date as possible.
Acceptance Criteria
Receiving data from the rural 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. Kane parcels).
We could document here counties available from AGOL or the like:
Data Requested from county/Received and Available From L:\agrc\data\county_obtained
January
Parcels processed: Grand, Wasatch,
February
Parcels processed: Tooele, Carbon
March
Parcels processed: Garfield, Iron
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: