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 beijing composite |
|---|---|
| paved | City centre beijing composite |
Fills bldgs. The archetype is named 'City centre ', declares target land_cover.bldgs, place beijing and representativeness city.
Fills paved. The archetype is named 'City centre ', declares target land_cover.paved, place beijing and representativeness city.
| Composite identity | supported The composite is named CBD and described 'Central Beijing', and both components are the Beijing archetypes named 'City centre ' carrying place beijing, so the label identifies what is assembled. One envelope field does not fit that reading: profile_type reads 'Residential' on an entry named 'CBD'. In the legacy Types table profile_type is descriptive metadata migrated verbatim, it selects no component and sits outside the uses block, so it changes nothing this review covers, but the two strings do not describe the same district and the field is worth settling when the typology metadata is next revisited. |
|---|---|
| Composite target | supported The composite's own target is typology, 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. No archetype in this database declares attaches_to, which is carried only by the 477 records under 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 archetypes it selects. |
| Composition rationale | not applicable The composite claims no composition source, and the repository records no published rationale for pairing these two archetypes. The components' own selections belong to their composition assessments, not to this review. |
| Place applicability | supported The composite claims place china, and both components declare place beijing, which db/places.yml resolves to country china. Nothing is imported from outside the country the composite claims. The national typology does rest on one city: archetypes/surfaces/bldgs/beijing--city-centre and archetypes/surfaces/paved/beijing--city-centre are the only building and paved archetypes in the database carrying a Chinese place, the remaining Chinese entries under archetypes/surfaces being vegetation sets for which a typology has no slot, so no broader Chinese assembly was available to select. |
| Representativeness | curation required The composite declares representativeness regional while both components declare city, so one city's archetypes stand for a national typology. The substitution was not avoidable, because the database holds no Chinese building or paved archetype classed regional, but the reach the composite claims is its own: either this is a Beijing typology and should say so, or Beijing is accepted as the Chinese exemplar and that decision is recorded. Every typology whose components come from a named city carries the same city-under-regional pattern, so a maintainer should settle it once across the typology set rather than entry by entry. |
| Slot and season mapping | supported An assembly of two existing archetypes into two slots; the composite produces no value of its own. A typology carries no seasonal or wet/dry axis, because the four OHM positions live inside the surface archetypes, so the only mapping made here is one archetype per slot and each slot receives exactly one. |
| Completeness and uniqueness | supported A typology has two component slots and no others: the migration maps the legacy Types table's Buildings and Paved columns into bldgs and paved and nothing else (scripts/migrate_to_records.py), and all fourteen entries under archetypes/typologies fill exactly those two. This composite fills both, so the assembly is complete. Its pair of components is unique: no other entry under archetypes/typologies selects archetypes/surfaces/bldgs/beijing--city-centre or archetypes/surfaces/paved/beijing--city-centre. The name CBD alone does not identify the entry, since archetypes/typologies/finland--cbd, archetypes/typologies/switzerland--cbd and archetypes/typologies/uk--cbd-sample-run carry it too; the path, the place and the selected components separate them. |
China's CBD typology is assembled from the two Beijing city-centre archetypes and from nothing else, which is the right instinct: the components sit inside the country the composite claims, they are the only Chinese building and paved archetypes the database holds, they carry the targets their slots need, and both of the two slots a typology has are filled. What the composite adds on its own account is reach. It declares representativeness regional while both components declare city, so Beijing stands for China. No alternative existed at the time of assembly, so this is not a selection error; it is an unrecorded decision about how far one city may travel, and it recurs wherever a typology draws on a named city. A maintainer should settle it once for the typology set: relabel these entries to the class of their components, or state that the city named in the description is the accepted national exemplar. Separately, the entry's legacy profile_type field reads 'Residential' on an entry named 'CBD'; it drives no selection here, but it does not describe the same district. The components' own compositions and values remain subject to their own assessments; this review does not revisit them.
Paste under typology in a SUEWS YAML configuration; every value carries its citation.
bldgs:
alb:
value: 0.18
ref:
ID: ao2016
DOI: 10.1175/JAMC-D-16-0082.1
desc: shanghai, central_business_district, site
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.12
ref:
ID: ao2016
DOI: 10.1175/JAMC-D-16-0082.1
desc: 'shanghai, central_business_district, site, source bounds 0.12–0.14 (active:
minimum)'
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.805
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a2:
value: -0.193
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a3:
value: -9.39
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
summer_dry:
a1:
value: 0.805
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a2:
value: -0.193
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a3:
value: -9.39
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
winter_wet:
a1:
value: 0.805
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a2:
value: -0.193
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a3:
value: -9.39
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
winter_dry:
a1:
value: 0.805
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a2:
value: -0.193
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
a3:
value: -9.39
ref:
ID: umep-dev2017a-input-tables
DOI: null
desc: alland, site, material
typology