Skip to content

Alert browser: improve area/region labeling for non-US sources (Canada, MeteoAlarm) #91

Description

@kellylford

Background

For U.S. NWS alerts we now append the state abbreviation to each affected area (e.g. "Limestone, AL; Moore, TN"), derived by zipping areaDesc with the parallel geocode.UGC codes (each code's first two letters are the state). See the alert browser digest → group detail.

The non-US providers don't yet get equivalent treatment, so their affected-area labels can be terse, bare, or inconsistent.

What to improve

  • Canada (ECCC). Area is currently built from feature_name_en + province joined by ", ". Verify this reads well for every alert type, and that the province is present/abbreviated consistently (some feeds may omit it or spell it out).
  • Europe (MeteoAlarm). Area comes from the CAP <area><areaDesc> values joined by ", ". These are region/zone names with no country context — when browsing a single country that's implicit, but the label granularity and readability vary a lot country to country (some give named regions, some codes). Consider whether a country prefix/suffix or cleanup is warranted.

Notes

  • The US mechanism (UGC state prefix) is US-specific and does not generalize — each provider needs its own approach based on the fields its feed actually carries.
  • Accessibility: whatever labeling we land on must read cleanly as a single VoiceOver element per area row, consistent with the US rows.
  • Not urgent; filed to track the non-US half after the US state-suffix change.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions