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
This commit is contained in:
+2
-2
@@ -69,8 +69,8 @@ replacement, and each removed path, column or flag.
|
||||
- `geo.SE` and `geo.US`: five linked tables per country, `region`, `municipality`,
|
||||
`locality`, `postal-code` and `street`, weighted by population and address counts
|
||||
and built from SCB, GeoNames, Trafikverket NVDB and the US Census Bureau, and an
|
||||
`address` record binding one street and reading its locality, postal code and region
|
||||
through it. `sv_SE.address` and `en_US.address` bind those records once, so
|
||||
`address` record binding one locality and drawing its street and postal code inside
|
||||
it. `sv_SE.address` and `en_US.address` bind those records once, so
|
||||
`en_US.address.street` no longer carries `name` and `suffix`, and a locale folder
|
||||
loads only beside `geo`.
|
||||
- `{date(from,to,'layout')}` and `{time('layout')}`: a second between two days, or
|
||||
|
||||
Reference in New Issue
Block a user