Add the geo trees for SE and US as linked tables, and build each locale's address on them #20

2026-09-18T00:55:51+02:00

lilleman commented

2026-09-18 00:55:51 +02:00

Step 2 of the data plan in todo.md: geo/SE and geo/US as five linked tables each (region, municipality, locality, postal-code and street), rebuilt by data-import/geo-se.py from SCB, GeoNames and Trafikverket NVDB and by data-import/geo-us.py from the Census Bureau; an address record per country over one consistent draw, which sv_SE.address and en_US.address read. Two child tables under one pinned ancestor are tested; the tests that loaded one locale now load the whole set; a column walk skips tables without token cells.

lilleman added 7 commits 2026-09-18 00:55:51 +02:00

Test two child tables under one pinned ancestor, a keyless child, and both descents listed 2127b3277c

Load the whole shipped set where a test loaded one locale, and admit registered street and place names 42c74b9b43

Rebuild geo/SE from SCB, GeoNames and NVDB as five linked tables, and read sv_SE.address from its address record 8c005070ec

Skip the row loop of a column walk when a table has no token cells, and scan a cell for braces by byte 7993e04d95

Rebuild geo/US from the Census Bureau as five linked tables, and read en_US.address from its address record 1029b789b5

Document the geo trees, their sources and the choices behind them, and mark step 2 done db271f82ee

Re-pin the shipped shape with the geo trees and the address records over them

Tests / vet + fmt + tests (pull_request) Successful in 1m18s

Details

Tests / Gitea release from CHANGELOG.md (pull_request) Has been skipped

Details