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 | Central London, Ward et al. (2016) london composite |
|---|---|
| paved | Central London, Ward et al. (2016) london composite |
Fills bldgs. The archetype is named 'Central London, Ward et al. (2016)' and declares target land_cover.bldgs, place 'london' and representativeness 'city'. It declares no attaches_to, and its construction slot takes records/constructions/uk--lindberg-f2020--central-london-sample-run.
Fills paved. The archetype is named 'Central London, Ward et al. (2016)' and declares target land_cover.paved, place 'london' and representativeness 'city'. It declares no attaches_to.
| Composite identity | curation required The composite is named 'CBD' and described as 'Central London (sample data)'. Both slots take archetypes named 'Central London, Ward et al. (2016)', so the central-London half of the description matches what is assembled. The sample-data half appears nowhere in the name, and it is not incidental: the entry path is archetypes/typologies/uk--cbd-sample-run, and the construction under the bldgs component is records/constructions/uk--lindberg-f2020--central-london-sample-run, named 'Central London [sample run]'. SUSPECT_MARKERS in scripts/check_db.py lists 'sample run' and 'sample data' as names that read as test fixtures rather than data, and make check does report that construction record; the check inspects only the name field, which here reads 'CBD', so the composite itself passes silently. A reader choosing this entry from the site sees 'CBD' and a UK regional class, not a demonstration dataset. A maintainer should decide whether the entry is a publishable urban type and, if it is, whether its name should say what its description already says. |
|---|---|
| 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 share the slug 'london-uk--central-london-ward-et-al-2016' 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 London as the UK's CBD type. The components' own sources belong to their assessments, not to this review. |
| Place applicability | supported The composite claims place 'uk', which db/places.yml gives as name 'UK', country 'united-kingdom' and subnational true. Both components declare place 'london', which db/places.yml resolves to country 'united-kingdom'. Every part of the typology comes from inside the country it claims. |
| Representativeness | curation required The composite declares representativeness 'regional' while both components declare 'city'. Nothing in this assembly carries the class the composite claims: a single central-London pair of surfaces is offered as a UK-wide urban type. A maintainer should decide whether to reclassify the composite or to record that central London is the intended stand-in for UK city centres. |
| 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. The former OBTESTCASE sibling and its dedicated building surface were retired as an earlier compilation test chain under issue 58. No other surviving typology has this uses block, so the identity is now unique. The remaining questions concern whether this sample-run assembly should be published as a UK-wide CBD type and how it should be named, not whether it duplicates another published entry. |
The slot mechanics are sound. Both components are a matched central-London pair from the same curated bundle, both declare place 'london' inside the country the composite claims, and each is declared for the slot it fills. What the entry claims around that assembly is where it fails. It declares representativeness 'regional' while both components declare 'city', so one city centre stands for the whole UK. It describes itself as 'Central London (sample data)' while presenting under the name 'CBD', and the sample-run character runs down into the building archetype's construction, records/constructions/uk--lindberg-f2020--central-london-sample-run, which make check already reports as a suspect name; the composite escapes the same warning only because the check reads the name field and the name field says 'CBD'. The former OBTESTCASE sibling was retired under issue 58, leaving this as the unique surviving assembly. The remaining curation decisions are whether demonstration data should be published as a UK urban type at all and, if so, what it should be called and how far it may travel. None of that depends on a component's values, which 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.91
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: london, city
storage_drain_params:
store_min:
value: 0.25
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
store_max:
value: 0.25
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
drain_eq:
value: 3
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
drain_coef_1:
value: 10
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
drain_coef_2:
value: 3
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
wet_threshold:
value: 0.6
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
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.51
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.337
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: -28.85
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
summer_dry:
a1:
value: 0.51
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.337
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: -28.85
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
winter_wet:
a1:
value: 0.598
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.337
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: 11.3
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
winter_dry:
a1:
value: 0.598
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.337
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: 11.3
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
paved:
alb:
value: 0.1
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: se-england, site, land_cover
emis:
value: 0.95
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: london, city
storage_drain_params:
store_min:
value: 0.48
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
store_max:
value: 0.48
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
drain_eq:
value: 3
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
drain_coef_1:
value: 10
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
drain_coef_2:
value: 3
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
wet_threshold:
value: 0.6
ref:
ID: ward2018
DOI: 10.1002/joc.5200
desc: swindon, site
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.722
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.3
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: -36.14
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
summer_dry:
a1:
value: 0.722
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.3
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: -36.14
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
winter_wet:
a1:
value: 0.848
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.3
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: 14.16
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
winter_dry:
a1:
value: 0.848
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a2:
value: 0.3
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
a3:
value: 14.16
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: land_cover
typology