Repository navigation
Shift corner lots warehouse script data ingest to raw script - #1123
Merged
wrridgeway merged 9 commits intoNov 5, 2026
Merged
wrridgeway merged 9 commits into
wrridgeway merged 9 commits into
Conversation
wrridgeway
commented
Nov 4, 2026
Comment on lines
+246
to
257
| cross_final %>% | ||
| inner_join( | ||
| town_parcels %>% | ||
| mutate(id = row_number()) %>% | ||
| st_drop_geometry() %>% | ||
| select(pin10, id), | ||
| by = "id" | ||
| ) %>% | ||
| select(-id) %>% | ||
| relocate(pin10) %>% | ||
| geoparquet_to_s3(remote_file) | ||
| } |
Member
Author
There was a problem hiding this comment.
This is the only substantive change to this script. It was throwing an error when we joined cross_final to town_parcels because the resulting dataframe was no longer an sf object. This produces the same exact output, but retains the sf class for the resulting dataframe.
wrridgeway
commented
Nov 4, 2026
Member
Author
There was a problem hiding this comment.
I suggest reviewing this diff with whitespace hidden.
wrridgeway
marked this pull request as ready for review
November 4, 2026 19:31
jeancochrane
approved these changes
Nov 4, 2026
jeancochrane
left a comment
Member
There was a problem hiding this comment.
Looks good to me, thanks for the cleanup and the thorough QC!
wrridgeway
deleted the
1122-shift-corner-lots-warehouse-script-data-ingest-to-raw-script
branch
November 5, 2026 15:35
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.
This PR creates a new raw script that ingests OSM data for "main" roads so that we don't have to do it again any time we rebuild corner lots. As @jeancochrane stated in #1100 (comment) we might want to consider renaming the raw script to signal the data's broader usefulness, but for this PR I'm leaving the naming scheme for the sake of a more easily understandable lineage.
I rebuilt corners for 2023 in
s3://ccao-data-warehouse-dev-us-east-1/spatial/ccao/corner/using this new warehouse script to compare its output to what's currently inspatial.corner. Below I have code that shows a comparison for Barrington. There are differences, but they are quite minor, and the disagreements do seem to be largely for parcels where defining a corner status leaves room for argument.More broadly, we also see that the total number of corner lots for 2023 is, again, very similar to what it is currently in our data: