Repository navigation
docs(site): show how to group records by state, LGA, district, or area - #76
Merged
Merged
Conversation
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.
A page for the use the prefix type and the SQL files were built for: counting or selecting records by place without a map or boundary files.
It shows the four prefixes of one code, a plain Python example, the same function on a pandas or Polars column, and the SQL form with a link to
sql/. Rows that are not well-formed codes are counted underNone, so they stay visible. A closing note says what a prefix does not carry: names, boundaries, or population.I ran every Python example on the page before committing. The site index links to it, and one conflict there with the address record paragraph was resolved by keeping both.