Coordinate formats list

[vitaliy-sova-ios]

No description provided.

[tigrim]

Android keeps this preference owned by CoordinateFormatSettingsStorage (preferredCoordinateFormatIdsPreference), while iOS registers it in OAAppSettings and passes it into the storage. Is this intentional for iOS preference registration / backup-import support? If yes, this looks fine, but it may be worth keeping it private/internal to OAAppSettings unless other code is expected to access it directly.

[tigrim]

I found a few behavior gaps compared with the Android implementation this was ported from:

1. CoordinatesFormatViewController.swift: the Add and Edit buttons are visible, but their handlers are empty. On Android, Edit opens CoordinatesFormatEditFragment, and Add opens AddCoordinateFormatFragment. Without those flows, users cannot add, remove, or reorder preferred formats.

2. CoordinateFormatIds.swift / BuiltInCoordinateFormat.swift: the iOS port currently includes only 6 built-in formats, while Android also has swiss_grid, swiss_grid_plus, and maidenhead. Also, iOS accepts epsg: ids in normalize, but CoordinatesFormatViewController.resolveFormats resolves only built-in formats via compactMap, so EPSG/custom grid formats coming from Android sync/import would silently disappear from the list.

3. OAPointDescription.mm / OAQuickSearchCoordinatesViewController.mm: the new preferred format list is not wired into the places Android uses it for. Android takes the primary format from coordinateFormatSettingsStorage for quick search and share/context flows, while iOS still reads the legacy settingGeoFormat and a fixed format set. This means the new settings screen can show a preferred list that does not actually control quick access in search/context menu flows.

[tigrim]

Since the task is still in progress, I’ll re-review the comments I left once the entire task is completed.