ios 城市列表选择

# [](#) [](https://travis-ci.org/intuit/LocationManager) [](https://coveralls.io/r/intuit/LocationManager) [](http://cocoapods.org/pods/INTULocationManager) [](http://cocoapods.org/pods/INTULocationManager) [](LICENSE) INTULocationManager makes it easy to get the device's current location and heading on iOS. It is an Objective-C library that also works great in Swift. INTULocationManager provides a block-based asynchronous API to request the current location, either once or continuously. It internally manages multiple simultaneous location and heading requests, and each one-time location request can specify its own desired accuracy level and timeout duration. INTULocationManager automatically starts location services when the first request comes in and stops location services as soon as all requests have been completed, all the while dynamically managing the power consumed by location services to reduce impact on battery life. ## What's wrong with CLLocationManager? CLLocationManager requires you to manually detect and handle things like permissions, stale/inaccurate locations, errors, and more. CLLocationManager uses a more traditional delegate pattern instead of the modern block-based callback pattern. And while it works fine to track changes in the user's location over time (such as for turn-by-turn navigation), it is extremely cumbersome to correctly request a single location update (such as to determine the user's current city to get a weather forecast, or to autofill an address from the current location). INTULocationManager makes it easy to request both the device's current location, either once or continuously, as well as the device's continuous heading. The API is extremely simple for both one-time location requests and recurring subscriptions to location updates. For one-time location requests, you can specify how accurate of a location you need, and how long you're willing to wait to get it. Significant location change monitoring is also supported. INTULocationManager is power efficient and conserves the device's battery by automatically determining and using the most efficient Core Location accuracy settings, and by automatically powering down location services (e.g. GPS or compass) as soon as they are no longer needed. ## Installation *INTULocationManager requires iOS 6.0 or later.* ### Using [CocoaPods](http://cocoapods.org) 1. Add the pod `INTULocationManager` to your [Podfile](http://guides.cocoapods.org/using/the-podfile.html). ```ruby pod 'INTULocationManager' ``` 1. Run `pod install` from Terminal, then open your app's `.xcworkspace` file to launch Xcode. 1. Import the `INTULocationManager.h` header. * With `use_frameworks!` in your Podfile * Swift: `import INTULocationManager` * Objective-C: `#import <INTULocationManager/INTULocationManager.h>` (or with Modules enabled: `@import INTULocationManager;`) * Without `use_frameworks!` in your Podfile * Swift: Add `#import "INTULocationManager.h"` to your bridging header. * Objective-C: `#import "INTULocationManager.h"` ### Using [Carthage](https://github.com/Carthage/Carthage) 1. Add the `intuit/LocationManager` project to your [Cartfile](https://github.com/Carthage/Carthage/blob/master/Documentation/Artifacts.md#cartfile). ```ogdl github "intuit/LocationManager" ``` 1. Run `carthage update`, then follow the [additional steps required](https://github.com/Carthage/Carthage#adding-frameworks-to-an-application) to add the iOS and/or Mac frameworks into your project. 1. Import the INTULocationManager framework/module. * Swift: `import INTULocationManager` * Objective-C: `#import <INTULocationManager/INTULocationManager.h>` (or with Modules enabled: `@import INTULocationManager;`) ### Manually from GitHub 1. Download all the files in the [INTULocationManager subdirectory](LocationManager/INTULocationManager). 1. Add the source files to your Xcode project (drag and drop is easiest). 1. Import the `INTULocationManager.h` header. * Swift: Add `#import "INTULocationManager.h"` to your bridging header. * Objective-C: `#import "INTULocationManager.h"` ## Usage ### Requesting Permission to Access Location Services INTULocationManager automatically handles obtaining permission to access location services when you issue a location request and the user has not already granted your app permission to access location services. #### iOS 6 & 7 For iOS 6 & 7, it is recommended that you provide a description for how your app uses location services by setting a string for the key [`NSLocationUsageDescription`](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW27) in your app's `Info.plist` file. #### iOS 8 Starting with iOS 8, you **must** provide a description for how your app uses location services by setting a string for the key [`NSLocationWhenInUseUsageDescription`](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW26) or [`NSLocationAlwaysUsageDescription`](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW18) in your app's `Info.plist` file. INTULocationManager determines which level of permissions to request based on which description key is present. You should only request the minimum permission level that your app requires, therefore it is recommended that you use the "When In Use" level unless you require more access. If you provide values for both description keys, the more permissive "Always" level is requested. ### Getting the Current Location (once) To get the device's current location, use the method `requestLocationWithDesiredAccuracy:timeout:block:`. The `desiredAccuracy` parameter specifies how **accurate and recent** of a location you need. The possible values are: ```objective-c INTULocationAccuracyCity // 5000 meters or better, received within the last 10 minutes -- lowest accuracy INTULocationAccuracyNeighborhood // 1000 meters or better, received within the last 5 minutes INTULocationAccuracyBlock // 100 meters or better, received within the last 1 minute INTULocationAccuracyHouse // 15 meters or better, received within the last 15 seconds INTULocationAccuracyRoom // 5 meters or better, received within the last 5 seconds -- highest accuracy ``` The `timeout` parameter specifies how long you are willing to wait for a location with the accuracy you requested. The timeout guarantees that your block will execute within this period of time, either with a location of at least the accuracy you requested (`INTULocationStatusSuccess`), or with whatever location could be determined before the timeout interval was up (`INTULocationStatusTimedOut`). Pass `0.0` for no timeout *(not recommended)*. By default, the timeout countdown begins as soon as the `requestLocationWithDesiredAccuracy:timeout:block:` method is called. However, there is another variant of this method that includes a `delayUntilAuthorized:` parameter, which allows you to pass `YES` to delay the start of the timeout countdown until the user has responded to the system location services permissions prompt (if the user hasn't allowed or denied the app access yet). Here's an example: ```objective-c INTULocationMana