 lilleman
|
88cea644b6
|
Ship a tenth of each place's streets, at least ten, and a tenth of the US places owning a ZCTA, drawn by population
|
2026-10-11 16:42:23 +02:00 |
|
|
lilleman
|
203486a9d3
|
Answer architecture round 8: a shipped package's folder spells its namespace (data/sv_SE, data/geo/SE) under its lowered Go name, as a second bench chose, a mounted root folder reads as its namespace, and item 196 cites goal 9.2
|
2026-10-11 16:02:48 +02:00 |
|
|
lilleman
|
7b70530a8a
|
Answer architecture round 5: the shipped packages are enus, svse, geose, geous and misc, each holding its files at its root under its manifest's namespace, and the errors use the wording a bench of the Audience chose
|
2026-10-11 16:02:48 +02:00 |
|
|
lilleman
|
b8eba1eb35
|
Ship en_US, sv_SE, misc, geo/SE and geo/US as Go packages exporting FS, listed by data.Modules(), and fail a bare New naming WithDataFS
|
2026-10-11 16:02:48 +02:00 |
|
|
lilleman
|
a318dc7f42
|
Answer prose round 1: fence's docstring splits rule, shapes and result, each drop message names what was missing, the US geo row says a place needs a street, and file item 169
|
2026-10-09 12:35:12 +02:00 |
|
|
lilleman
|
32e01565b4
|
Answer architecture round 3: fence's docstring says a locality needs entries in both child maps, and zcta_localities says what it maps to
|
2026-10-09 12:35:12 +02:00 |
|
|
lilleman
|
c032cb779c
|
Answer architecture round 2: street.tsv is written from the kept localities, fence checks a child holds rows, and its names say what they hold
|
2026-10-09 12:35:12 +02:00 |
|
|
lilleman
|
71b17d104b
|
Answer architecture round 1: fence keeps a locality holding both a street and a postal code, returns what it dropped so the SE import still exits on a lost kommun and the US one counts its counties, and file item 168 for data-import tests
|
2026-10-09 12:35:12 +02:00 |
|
|
lilleman
|
6d285249e4
|
Meet the parent-has-a-child fence in one shared geo.fence step, which states the locality row each country hands it
|
2026-10-09 12:35:12 +02:00 |
|
|
lilleman
|
2431edeab0
|
Answer stability round 1: README's pick.go and datatype.go rows name what stayed, geo.py's options sort with each script's own, geo.py claims only shared steps, route defines fromRow as pathPos does, and disagreement's panic names the kinds
|
2026-10-07 02:27:24 +02:00 |
|
|
lilleman
|
ae5b95e88a
|
Share the steps every country's geo import takes in geo.py, so geo-se.py and geo-us.py hold only their own rules
|
2026-10-07 02:27:24 +02:00 |
|
|
lilleman
|
02eb95b94b
|
Move the birth number into its own table under sex, drop the sexed US titles, and split the import helper by content
|
2026-09-18 18:27:11 +02:00 |
|
|
lilleman
|
e5711cbdb4
|
Rank a ZCTA's parts among incorporated places only, drop numbered loops and highways, and say which places ship no address
|
2026-09-18 01:42:09 +02:00 |
|
|
lilleman
|
8c2b51ebed
|
Refuse an empty download, finish the NVDB pull atomically, drop route designations and unlettered names from the streets, and give a ZCTA to the place holding most of it
|
2026-09-18 01:34:11 +02:00 |
|
|
lilleman
|
92f58edc2d
|
Share one fetch and one TSV writer across the import scripts, and name the geo scripts' stages
|
2026-09-18 01:10:44 +02:00 |
|
|
lilleman
|
1029b789b5
|
Rebuild geo/US from the Census Bureau as five linked tables, and read en_US.address from its address record
|
2026-09-18 00:52:08 +02:00 |
|