No photograph yet. This kind of neighbourhood is easier to recognise than to describe, and a picture would tell a reader more about “Sub-urban” than the parameters below can.
A photograph is recorded for this typology but cannot be published: nobody has been able to establish who holds it or on what terms. That question is open in issue #55.
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 | Suburban residential, Ward et al. (2016) swindon composite |
|---|---|
| paved | Suburban residential, Ward et al. (2016) swindon composite |
Fills bldgs. The archetype is named 'Suburban residential, Ward et al. (2016)' and declares target land_cover.bldgs, place 'swindon' and representativeness 'city'. It declares no attaches_to.
Fills paved. The archetype is named 'Suburban residential, Ward et al. (2016)' and declares target land_cover.paved, place 'swindon' and representativeness 'city'. It declares no attaches_to.
| Composite identity | supported The composite is named 'Sub-urban' and described as 'Swindon (sub-urban)'. Both slots take archetypes named 'Suburban residential, Ward et al. (2016)' declaring place 'swindon', so the name and the description are both carried by what is assembled. The composite declares profile_type 'Residential', which agrees with the 'residential' in the component names, and period 'Pre80', which nothing in the assembly contradicts. |
|---|---|
| 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 'swindon-uk--suburban-residential-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 Swindon as the UK's sub-urban 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 'swindon', 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: one town's suburban surfaces are offered as the UK's sub-urban urban type. A maintainer should decide whether to reclassify the composite or to record that Swindon is the intended stand-in for UK suburbs. |
| 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 Swindon pair and neither is used by any other typology, so the composite is distinguishable from every other entry under archetypes/typologies. It is the only UK typology that is not a central-London entry, and the only one of the three declaring place 'uk' whose description does not say 'sample data'. The name 'Sub-urban' is shared with archetypes/typologies/sweden--sub-urban and archetypes/typologies/finland--sub-urban, which declare different places and different components in both slots. |
This is the tidiest typology of the seven reviewed. The bldgs and paved slots take the matched Swindon pair from one curated bundle, both named 'Suburban residential, Ward et al. (2016)', both declaring place 'swindon' inside the country the composite claims, and neither is used anywhere else, so name, description, profile type and components all say the same thing and nothing borrows across a border or across an urban form. The one claim the assembly does not support is reach: the composite declares representativeness 'regional' while both components declare 'city', so the UK's sub-urban type rests entirely on one town's measurements. That may well be intended, since a national typology has to come from somewhere and Swindon is what the database has, but the composite records no such decision, and a country-scale claim resting on a single city is exactly what the representativeness field exists to make visible. A maintainer should either narrow the class or state on the composite that Swindon stands deliberately for UK suburbs. 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: swindon, site, land_cover
emis:
value: 0.91
ref:
ID: ward2016
DOI: 10.1016/j.uclim.2016.05.001
desc: swindon, 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: swindon, 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