Skip to content

Improve remaining locality GeoNames ID coverage after v0.1.3 #8

Description

@mustafazeydani

v0.1.3 intentionally leaves locality-level GeoNames ID coverage partial.

Current release coverage:

  • Localities: 7,605
  • Localities with GeoNames IDs: 4,274
  • Localities still missing GeoNames IDs: 3,331
  • GeoNames locality ID coverage: 56.2%

Progress since this issue was opened:

  • v0.1.2 added 281 widened-radius one-to-one GeoNames locality matches using exact normalized names and same-governorate checks.
  • v0.1.3 added 225 Arabic article-insensitive one-to-one GeoNames locality matches within 2 km.
  • The reusable matcher now supports dry-run/apply modes and selected Arabic article-insensitive variants.

Current concentration of missing GeoNames IDs by governorate:

  • Aleppo: 919
  • Al-Hasakah: 876
  • Raqqa: 393
  • Idlib: 291
  • Hama: 223
  • Homs: 158
  • Latakia: 129
  • Tartus: 109
  • Deir-ez-Zor: 96
  • Daraa: 44
  • Rif Dimashq: 42
  • Quneitra: 30
  • As-Suwayda: 21
  • Damascus: 0

Notes:

  • Do not infer IDs from name similarity alone.
  • Keep every accepted ID source-backed and documented through an import manifest.
  • Review remaining candidates in focused governorate batches, starting with Aleppo and Al-Hasakah.
  • If a locality has no safe GeoNames match, leave it unresolved until a stronger approved source exists.

Related releases:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions