update docs to match new download format (and correct column names)#388
Merged
update docs to match new download format (and correct column names)#388
Conversation
katamartin
reviewed
Apr 21, 2026
| | `GEOID` | int | [Geographic Identifier](https://www.census.gov/programs-surveys/geography/guidance/geo-identifiers.html) representing building (multiple buildings might belong to the same GEOID) | | ||
| | `longitude` | degrees | Longitude of building centroid | | ||
| | `latitude` | degrees | Latitude of building centroid | | ||
| | `centroid_longitude` | degrees | Longitude of building centroid (CSV only; encoded in `geometry` for GeoJSON) | |
Member
There was a problem hiding this comment.
Oof looks like these have gotten really out-of-whack!
We updated both these columns and and the analogous columns for regional statistics downloads to drop the verbose centroid_* prefix. The goal of that PR was to document complementary changes that would be made on the data processing side, but it looks like that didn't quite happen (cc @norlandrhagen).
Rather than make any pipeline changes, I'd suggest the following:
- Subsetted data downloads: Is it possible to remove the
centroid_*prefix in Client downloads via duckdb-wasm ocr-web#155 and revert this change? - Regional statistics downloads: It looks like lat/lon have been dropped from these entirely 😕 . Shall we just update the documentation to reflect that?
- By deleting these entries in the schema:
Lines 63 to 64 in f90484e
- By deleting these entries in the schema:
katamartin
reviewed
Apr 21, 2026
| | `longitude` | degrees | Longitude of building centroid | | ||
| | `latitude` | degrees | Latitude of building centroid | | ||
| | `centroid_longitude` | degrees | Longitude of building centroid (CSV only; encoded in `geometry` for GeoJSON) | | ||
| | `centroid_latitude` | degrees | Latitude of building centroid (CSV only; encoded in `geometry` for GeoJSON) | |
Member
There was a problem hiding this comment.
Should we also add an entry for geometry?
katamartin
reviewed
Apr 21, 2026
Co-authored-by: Kata Martin <katasm@gmail.com>
for more information, see https://pre-commit.ci
katamartin
approved these changes
Apr 21, 2026
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.
Updates docs to match new direct download pattern from carbonplan/ocr-web#155
Swaps in a new screenshot, and updates locations in the docs to match GeoPackage => GeoJSON change as well as csv column name correction.