I agree that the loss of individual fields is a major downside of MKPlacemark and CLPlacemark being deprecated. Now they are embedded in MKMapItem as additional opaque context with no information as to what they are. Here's what's lost: CLPlacemark's postalAddress.street is now only available as part of the strings in MKMapItem's fullAddress (in address or addressRepresentations) Example: Street Rd & Avenue Rd in Street Rd & Avenue Rd, Cupertino, CA 95014, United States Similarly, CLPlacemark's administrativeArea (the state in the US) is only available as part of the strings in MKMapItem's cityWithContext or fullAddress. It's also not clear if this context will always be the state, it may be something else per the documentation (The city name along with the country name, to provide additional disambiguating context.) Example cityWithContext: Cupertino, CA There are no equivalents to CLPlacemark's subAdministrativeArea (typically a county in the US) or subLocality (typically a neighbo
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags: