Skip to content

Clarify reverse-geocoding precision in map views - #553

Merged
stef-k merged 4 commits into
mainfrom
fix/address-precision-guidance-551
Sep 4, 2026
Merged

Clarify reverse-geocoding precision in map views#553
stef-k merged 4 commits into
mainfrom
fix/address-precision-guidance-551

Conversation

@stef-k

@stef-k stef-k commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • retain meaningful detected-place names in Location and Trip views
  • hide raw provider feature classifications for specific results
  • show plain-language approximation guidance for postcode, city, local-area, and regional results
  • preserve stored metadata and API/import/export contracts

Closes #551

Validation

  • client tests: 111 passed
  • frontend typecheck and production build
  • dotnet build --no-restore
  • repository search found no remaining user-facing Feature type label
  • git diff --check

LOC

One-time #551 exceptions were explicitly approved for the narrowly edited legacy files Manager Groups Map, User Groups Map, and Trip Viewer. No broader exception applies.

@stef-k
stef-k merged commit ed21dec into main Sep 4, 2026
1 check passed
@stef-k
stef-k deleted the fix/address-precision-guidance-551 branch September 4, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace technical Geoapify feature types with useful address-precision guidance

1 participant