refresh GRU page and expand source data section - #2591
Merged
Conversation
damonmcc
marked this pull request as ready for review
August 31, 2026 13:15
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what
why
motivated by a recent round of running GR QA reports for Geosupport 26C
when GR (formerly GRU) uploads files to DO and then needs us to archive data and run the reports, we have to check which source data isn't up-to-date, go to the DE repo to individually run the ingest action, and then run the checks. it's easy to accidentally run the checks with old source data
the page also carried stale info: it linked workflows that no longer exist, said building footprints aren't batch-updated (they're on a weekly cron), and said developments needs no manual update (its publish workflow is archived)
notes
unsigned output links depend on NYCPlanning/db-gru-qaqc#280, which is merged and makes future runs upload public-read objects. the 812 existing objects under
db-gru-qaqc/{version}/were set public-read separately, and the older top-level prefixes were left private7 of 8 check names already matched GR's list. their ninth report isn't a missing check:
saf-vs-padwrites both the vs-PAD and vs-GRID files, so it stays one rowscreenshot of GRU page in local app run