lilleman 1afcbc1a83 Answer stability round 1: bind the locality so population still weighs an address, test the field paths agree, and restate why birth-number sits under sex

2026-10-05 00:50:23 +02:00

..

address.json

Answer stability round 1: bind the locality so population still weighs an address, test the field paths agree, and restate why birth-number sits under sex

2026-10-05 00:50:23 +02:00

locality.json

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

2026-09-18 00:23:25 +02:00

locality.tsv

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

2026-09-18 00:23:25 +02:00

municipality.json

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

2026-09-18 00:23:25 +02:00

municipality.tsv

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

2026-09-18 00:23:25 +02:00

postal-code.json

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

2026-09-18 00:23:25 +02:00

postal-code.tsv

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

2026-09-18 00:23:25 +02:00

region.json

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

2026-09-18 00:23:25 +02:00

region.tsv

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

2026-09-18 00:23:25 +02:00

street.json

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

2026-09-18 00:23:25 +02:00

street.tsv

Rebuild the geo trees without route designations, with ZCTAs at the place holding most of them

2026-09-18 01:34:11 +02:00