No photograph yet. This kind of neighbourhood is easier to recognise than to describe, and a picture would tell a reader more about “CBD” than the parameters below can.
Offer a photographWe can only publish one if it names its photographer and its licence — public domain, CC0, or a Creative Commons licence. A photograph with no stated terms cannot be shown, however well it fits.
| bldgs | City centre zurich composite |
|---|---|
| paved | City centre zurich composite |
Fills bldgs. The archetype is named 'City centre' and declares target land_cover.bldgs, place 'zurich' and representativeness 'city'. It declares no attaches_to.
Fills paved. The archetype is named 'City centre' and declares target land_cover.paved, place 'zurich' and representativeness 'city'. It declares no attaches_to.
| Composite identity | curation required The composite is named 'CBD' and described as 'Central Zurich'. Both slots take Zurich city-centre archetypes, archetypes/surfaces/bldgs/zurich--city-centre and archetypes/surfaces/paved/zurich--city-centre, each named 'City centre', so the name and the description agree with what is assembled. The composite also declares profile_type 'Residential'. That field is descriptive metadata migrated from the legacy Types table's ProfileType column by scripts/migrate_to_records.py and is read by nothing else under scripts/, so it selects no record; it is nevertheless what the entry says about the activity its urban type represents, and the four entries named 'CBD' disagree. archetypes/typologies/finland--cbd and archetypes/typologies/uk--cbd-sample-run declare 'Commercial'; this composite and archetypes/typologies/china--cbd declare 'Residential'. A maintainer should decide what a central-business-district typology means here and make the four consistent. |
|---|---|
| Composite target | supported The composite's own target is 'typology', which is what every entry under archetypes/typologies declares, and each slot takes a component declared for it: the bldgs slot takes an archetype declaring target land_cover.bldgs and the paved slot an archetype declaring target land_cover.paved. The two components share the slug 'zurich--city-centre' under different surface families, so the shared name does not put either in the wrong slot. Neither component declares attaches_to; in this database that field is carried only by the profile records under db/records/profiles, so slot fit here is judged on the components' declared target. |
| Own parameter values | not applicable The composite declares no parameters block of its own, so it asserts no value beyond the two components it selects. |
| Composition rationale | not applicable The composite claims no composition source, and the repository records no published rationale for taking central Zurich as Switzerland's urban type. The components' own sources belong to their assessments, not to this review. |
| Place applicability | supported The composite claims place 'switzerland'. Both components declare place 'zurich', which db/places.yml resolves to country 'switzerland', so every part of this typology comes from inside the country it claims, and the description 'Central Zurich' states the origin openly. That the whole of Switzerland's only typology rests on one city is a question of reach rather than of place, and it is taken up under representativeness. |
| Representativeness | curation required The composite declares representativeness 'regional' while both components declare 'city'. Nothing in this assembly carries the class the composite claims, which distinguishes it from the Swedish typologies, where at least the building archetype is regional. One city's central district is therefore offered as a country-scale urban type. Whether to reclassify the composite or to let the claim stand because central Zurich is the intended stand-in for Swiss city centres is a maintainer's decision. |
| Slot and season mapping | supported An assembly of two existing surface archetypes into the two slots the typology format defines; the composite produces no value of its own. A typology carries no season and no wet/dry mapping of its own, because those live inside the surface components' ohm blocks, so there is no seasonal mapping to check at this level. |
| Completeness and uniqueness | supported The assembly is complete: scripts/migrate_to_records.py maps only the legacy Types table's 'Buildings' and 'Paved' columns into a typology's uses block, and both slots are filled. Both components come from the same curated Zurich city-centre pair, so the building and paved descriptions are drawn from one place and one bundle rather than assembled across sources. This is the only typology declaring place 'switzerland' and the only one taking either Zurich component, so nothing duplicates it. The name 'CBD' is shared with archetypes/typologies/china--cbd, archetypes/typologies/finland--cbd and archetypes/typologies/uk--cbd-sample-run, which declare different places and different components in both slots. |
This is the most internally consistent selection in the typology set on the question the slots ask. Both components come from one curated Zurich city-centre pair, both declare place 'zurich', which resolves to country 'switzerland', and both fit the slot they fill, so the composite's description 'Central Zurich' is exactly what it assembles. Two things about the entry's own claims do not follow. Both components declare representativeness 'city' while the composite declares 'regional', so unlike the Swedish typologies, where the building archetype at least carries the composite's own class, nothing here supports a country-scale claim: Switzerland's single urban type is one city's central district. And the composite declares profile_type 'Residential' while calling itself a CBD, a field the four 'CBD' entries fill two ways, with archetypes/typologies/finland--cbd and archetypes/typologies/uk--cbd-sample-run declaring 'Commercial'. Neither question can be settled from the repository: reclassifying the composite and letting one city stand deliberately for Swiss city centres are both defensible, and profile_type is inherited descriptive metadata that resolves to no record here. A maintainer should decide both, ideally once for the whole CBD family. No component value is at issue; those remain subject to their own assessments.
Paste under typology in a SUEWS YAML configuration; every value carries its citation.
bldgs:
alb:
value: 0.12
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: london, site, land_cover
emis:
value: 0.95
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
storage_drain_params:
store_min:
value: 0.25
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
store_max:
value: 0.25
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
drain_eq:
value: 3
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
drain_coef_1:
value: 10
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
drain_coef_2:
value: 3
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
wet_threshold:
value: 0.25
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
snowpack_limit:
value: 190
ref:
ID: jarvi2014
DOI: 10.5194/gmd-7-1691-2014
desc: generic, generic, land_cover
ohm_coef:
summer_wet:
a1:
value: 0.238
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a2:
value: 0.427
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a3:
value: -16.7
ref:
ID: unreferenced
DOI: null
desc: beijing, city
summer_dry:
a1:
value: 0.238
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a2:
value: 0.427
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a3:
value: -16.7
ref:
ID: unreferenced
DOI: null
desc: beijing, city
winter_wet:
a1:
value: 0.238
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a2:
value: 0.427
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a3:
value: -16.7
ref:
ID: unreferenced
DOI: null
desc: beijing, city
winter_dry:
a1:
value: 0.238
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a2:
value: 0.427
ref:
ID: unreferenced
DOI: null
desc: beijing, city
a3:
value: -16.7
ref:
ID: unreferenced
DOI: null
desc: beijing, city
paved:
alb:
value: 0.09
ref:
ID: jarvi2014
DOI: 10.5194/gmd-7-1691-2014
desc: helsinki, site
emis:
value: 0.91
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
storage_drain_params:
store_min:
value: 0.48
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
store_max:
value: 0.48
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
drain_eq:
value: 3
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
drain_coef_1:
value: 10
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
drain_coef_2:
value: 3
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
wet_threshold:
value: 0.48
ref:
ID: jarvi2011
DOI: 10.1016/j.jhydrol.2011.10.001
desc: generic, generic, land_cover
snowpack_limit:
value: 190
ref:
ID: jarvi2014
DOI: 10.5194/gmd-7-1691-2014
desc: generic, generic, land_cover
ohm_coef:
summer_wet:
a1:
value: 0.719
ref:
ID: unreferenced
DOI: null
desc: land_cover
a2:
value: 0.194
ref:
ID: unreferenced
DOI: null
desc: land_cover
a3:
value: -36.6
ref:
ID: unreferenced
DOI: null
desc: land_cover
summer_dry:
a1:
value: 0.719
ref:
ID: unreferenced
DOI: null
desc: land_cover
a2:
value: 0.194
ref:
ID: unreferenced
DOI: null
desc: land_cover
a3:
value: -36.6
ref:
ID: unreferenced
DOI: null
desc: land_cover
winter_wet:
a1:
value: 0.719
ref:
ID: unreferenced
DOI: null
desc: land_cover
a2:
value: 0.194
ref:
ID: unreferenced
DOI: null
desc: land_cover
a3:
value: -36.6
ref:
ID: unreferenced
DOI: null
desc: land_cover
winter_dry:
a1:
value: 0.719
ref:
ID: unreferenced
DOI: null
desc: land_cover
a2:
value: 0.194
ref:
ID: unreferenced
DOI: null
desc: land_cover
a3:
value: -36.6
ref:
ID: unreferenced
DOI: null
desc: land_cover
typology