glam/frontend/public/schemas/20251121/linkml/modules/classes/Settlement.yaml
2026-01-19 00:09:28 +01:00

140 lines
4.1 KiB
YAML

id: https://nde.nl/ontology/hc/class/settlement
name: settlement
title: Settlement Class
imports:
- linkml:types
- ./Country
- ./Subregion
- ../slots/country
- ../slots/has_or_had_geographic_subdivision # was: subregion - migrated per Rule 53/56 (2026-01-17)
- ../slots/geonames_id
- ../slots/latitude
- ../slots/longitude
- ../slots/settlement_name
- ../slots/specificity_annotation
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ./SpecificityAnnotation
- ./TemplateSpecificityScore # was: TemplateSpecificityScores - migrated per Rule 53 (2026-01-17)
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
- ../slots/country
- ../slots/geonames_id
- ../slots/latitude
- ../slots/longitude
- ../slots/settlement_name
- ../slots/specificity_annotation
- ../slots/has_or_had_geographic_subdivision # was: subregion - migrated per Rule 53/56 (2026-01-17)
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ../slots/country
- ../slots/geonames_id
- ../slots/latitude
- ../slots/longitude
- ../slots/settlement_name
- ../slots/specificity_annotation
- ../slots/has_or_had_geographic_subdivision # was: subregion - migrated per Rule 53/56 (2026-01-17)
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
classes:
Settlement:
class_uri: gn:Feature
exact_mappings:
- schema:Place
- gn:P.PPL
close_mappings:
- wikidata:Q486972
- crm:E53_Place
description: 'City, town, or municipality identified by GeoNames ID.
GeoNames (https://www.geonames.org/) is a geographical database that provides
stable identifiers for settlements worldwide. Each settlement has a unique
numeric GeoNames ID that persists even if names or boundaries change.
Purpose:
- Link custodian places to their specific city/town location
- Enable city-specific feature types (e.g., "City of Pittsburgh Historic Designation")
- Provide geographic precision beyond country/subregion level
GeoNames ID format: Numeric (e.g., 5206379 for Pittsburgh)
Examples:
- GeoNames 2759794: Amsterdam, Netherlands
- GeoNames 5206379: Pittsburgh, Pennsylvania, USA
- GeoNames 3451190: Rio de Janeiro, Brazil
- GeoNames 1850147: Tokyo, Japan
- GeoNames 2643743: London, United Kingdom
Design rationale:
- GeoNames IDs are stable, language-neutral identifiers
- Avoid ambiguity from duplicate city names (e.g., 41 "Springfield"s in USA)
- Enable geographic coordinate lookup via GeoNames API
- Widely used in heritage data (museum registries, archival systems)
External resolution:
- GeoNames API: https://www.geonames.org/
- GeoNames RDF: https://sws.geonames.org/{geonames_id}/
- Wikidata integration: Most major cities have Wikidata links
Alternative: For settlements without GeoNames ID, use settlement name + country
as fallback, but prefer obtaining GeoNames ID for data quality.
'
attributes:
settlement_id:
identifier: true
range: uriorcurie
required: true
description: 'Unique identifier for this settlement record.
Format: Use GeoNames URI when available (e.g., https://sws.geonames.org/2759794/)
or generate from settlement_name + country code.
'
slots:
- country
- geonames_id
- latitude
- longitude
- settlement_name
- specificity_annotation
- has_or_had_geographic_subdivision # was: subregion - migrated per Rule 53/56 (2026-01-17)
- has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
slot_usage:
geonames_id:
required: false
settlement_name:
required: true
country:
required: true
has_or_had_geographic_subdivision: # was: subregion - migrated per Rule 53/56 (2026-01-17)
required: false
latitude:
required: false
longitude:
required: false