ios百度地图sdk 网格_使用sdk v6地图支持ios14大概位置2 0-CSDN博客

ios百度地图sdk 网格

Developers can begin working with Mapbox iOS SDK version v6.2.0-beta.1 to fully support Apple iOS14, including Approximate Location. This prerelease tracks the current iOS14 beta. We recommend that iOS developers begin using Mapbox SDK v6.2.0 as soon as possible to update their apps, providing a smooth experience for users when iOS14 is released.

开发人员可以开始使用Mapbox iOS SDK版本v6.2.0-beta.1来完全支持Apple iOS14，包括“近似位置”。此预发行版跟踪当前的iOS14 beta。我们建议iOS开发人员尽快开始使用Mapbox SDK v6.2.0更新其应用程序，以便在iOS14发布时为用户提供流畅的体验。

iOS14’s Approximate Location feature allows users to reduce the precision of location data shared with an app. When a user enables Approximate Location for an app, it will receive obfuscated data instead of the user’s exact location — only the general area of the end user will be reported, rather than the precise location data available in previous iOS versions. The size of this area will vary between dense urban areas and less populous ones. Apple has suggested that a typical size for the area is a 5km radius. Approximate Location reduces location data’s frequency, too: when enabled, location is recomputed about four times per hour. A thorough discussion of Approximate Location can be found in the What’s New In Location talk from this year’s WWDC.

iOS14的“近似位置”功能使用户可以降低与应用共享的位置数据的精度。当用户为应用程序启用“近似位置”时，它将接收混淆的数据，而不是用户的确切位置-仅报告最终用户的一般区域，而不是先前iOS版本中可用的精确位置数据。该区域的大小将在人口稠密的城市地区和人口较少的城市地区之间变化。苹果公司建议该区域的典型大小是半径5公里。近似位置也降低了位置数据的频率：启用后，每小时大约重新计算位置四次。有关近似位置的详细讨论，请参见今年WWDC 的“位置中的新功能”演讲。

Mapbox iOS SDK version v6.2.0 fully supports iOS Approximate Location by wrapping and augmenting the iOS CoreLocation API, making it easier for developers to build in iOS14 while avoiding the negative user experiences that Approximate Location can cause. Notable features include:

Mapbox iOS SDK版本v6.2.0通过包装和扩展iOS CoreLocation API完全支持iOS近似位置，这使开发人员可以更轻松地在iOS14中进行构建，同时避免了近似位置可能引起的负面用户体验。值得注意的功能包括：

[MGLMapViewDelegate mapView:didChangeLocationManagerAuthorization:] allows apps to take action whenever an end user enables or disables Approximate Location.
[MGLMapViewDelegate mapView：didChangeLocationManagerAuthorization：]允许应用程序在最终用户启用或禁用“近似位置”时采取措施。
[MGLLocationManager.accuracyAuthorization] reflects the level of precision that the end user has authorized.
[MGLLocationManager.accuracyAuthorization]反映了最终用户已授权的精度级别。
Developers may request temporary access to full-precision location information with [MGLLocationManager.requestTemporaryFullAccuracyAuthorizationWithPurposeKey:].
开发人员可以使用[MGLLocationManager.requestTemporaryFullAccuracyAuthorizationWithPurposeKey：]来请求对精确位置信息的临时访问。
When an MGLUserTrackingMode that requires precise user location is enabled, the SDK will automatically check for and, if needed, prompt the user to grant permission.
启用要求精确用户位置的MGLUserTrackingMode时 ，SDK将自动检查并在需要时提示用户授予权限。
User location annotations will automatically reflect when precise location data is not available.
当没有精确的位置数据时，用户位置注释将自动反映。

Approximate Location will bring valuable new privacy controls to end users. But it also means that apps that use location data will risk delivering bad user experiences if they do not prepare for scenarios in which Approximate Location is enabled.

近似位置将为终端用户带来有价值的新隐私控制。但这也意味着使用位置数据的应用程序如果不为启用“近似位置”的方案做好准备，就有可能带来糟糕的用户体验。

iOS precise location permissions dialog with options “allow once” “turn on in settings” and “keep precise location off” — An app’s access to precise location data can be enabled during the initial request for location data; later, in-app on a temporary basis; or permanently, at any time, in the app’s system settings.

Many location use cases require precise location data. Features like navigation, displaying user location, or fitness tracking will behave in undesirable ways or become unusable when Approximate Location is enabled. Examples of undesirable or unexpected behaviors that apps should plan to address:

许多位置用例需要精确的位置数据。启用“近似位置”后，导航，显示用户位置或健身跟踪等功能将以不良方式运行或无法使用。应用程序应计划解决的不良或意外行为的示例：

Confusing user location sharing. If end users share their location with others and the app does not have a way to mark a shared location as precise or approximate, users may have confusing and problematic interactions. Example: two users attempting to meet up at a location are confused by an approximate shared location.
令人困惑的用户位置共享。 如果最终用户与其他人共享他们的位置，而该应用程序无法将共享位置标记为精确或近似，则用户可能会感到困惑和麻烦。 示例：两个试图在某个位置集合的用户被一个近似的共享位置所迷惑。
Unusable navigation. Navigation workflows rely on a frequently updated measurement of the end user’s precise location in order to position the map, detect the need for route recalculation, monitor speed and provide prompts for upcoming maneuvers. Approximate Location provides updates with insufficient precision and frequency for any of these tasks. Example: a user launches an automotive navigation feature with approximate location enabled, causing their position to appear stationary even though their car begins moving.
无法使用的导航。 导航工作流依赖于对最终用户精确位置的频繁更新测量，以便定位地图，检测对路线重新计算的需求，监控速度并为即将进行的操作提供提示。 “近似位置”无法为这些任务中的任何一项提供足够的准确性和频率更新。 示例：用户启动启用了大致位置的汽车导航功能，即使他们的汽车开始移动，也会导致他们的位置显得静止。
Unexpected location information. End users may regard Approximate Location information as incorrect. Example: an end user is surprised to see their social media posts tagged as originating from a place they have never visited.
意外的位置信息。 最终用户可能认为“近似位置”信息不正确。 示例：最终用户惊讶地看到自己的社交媒体帖子被标记为源自他们从未访问过的地方。
Data pollution. If an app publishes and stores user location data and does not have a way to detect location data’s level of precision, it may not be able to easily filter out data points collected while Approximate Location is turned on. Example: an app collecting fitness data in the background reports inaccurate metrics (e.g. average walking pace) by failing to discard data collected while Approximate Location is enabled.
数据污染。 如果应用发布并存储用户位置数据，但无法检测位置数据的精确度，则可能无法在“近似位置”打开时轻松过滤掉收集的数据点。 示例：在后台收集健身数据的应用通过在启用“近似位置”时无法丢弃收集的数据，报告了不准确的指标(例如，平均步行速度)。

The default state of iOS14’s location permission UI will allow the collection of precise location data, and previously installed apps will retain their already-granted access to precise location information when users upgrade to iOS14. But developers should still check if precise location data is available before their apps launch features that depend on it.

iOS14的位置许可UI的默认状态将允许收集精确的位置数据，并且当用户升级到iOS14时，以前安装的应用将保留对精确位置信息的已授予访问权限。但是，开发人员仍应在其应用程序启动依赖于此的功能之前，检查精确的位置数据是否可用。

When precise location is needed but unavailable, developers must ask the end user for access to it, whether through a temporary authorization or a change in the app’s system settings. Developers also need to account for changes in location precision at unexpected times, since users may visit an app’s system settings and disable its access to precise location data whenever they wish. The Mapbox SDK offers ways to detect when such changes occur.

当需要精确位置但不可用时，开发人员必须要求最终用户访问该位置，无论是通过临时授权还是通过更改应用程序的系统设置。开发人员还需要在意外的时间考虑位置精度的变化，因为用户可以随时访问应用程序的系统设置并禁用对精确位置数据的访问。 Mapbox SDK提供了检测何时发生此类更改的方法。

iOS14 app settings dialog, which includes new options for location data use by widgets and precise location — In iOS14, an app’s system settings will include a toggle for Precise Location data.

App developers need to upgrade to Mapbox iOS SDK version v6.2.0 or later to fully support iOS Approximate Location. Previous versions of the Mapbox SDK do not support iOS Approximate Location. There are no plans to backport these changes to any previous versions of the SDK.

应用开发人员需要升级到Mapbox iOS SDK版本v6.2.0或更高版本，以完全支持iOS近似位置。 Mapbox SDK的早期版本不支持iOS近似位置。 没有计划将这些更改回移植到任何早期版本的SDK。

Please note that iOS14 is still in beta and subject to change. A public release date for iOS14 has not been announced but is generally believed to be imminent. More details are expected at Apple’s recently announced event on September 15. We will be tracking Apple’s preview releases closely and adjusting as needed.

请注意，iOS14仍处于测试阶段，可能会发生变化。 iOS14的公开发布日期尚未公布，但一般认为即将到来。预计将在9月15日苹果公司最近宣布的活动中获得更多细节。我们将密切跟踪Apple的预览版本，并根据需要进行调整。

Download the release, read the detailed docs, and keep an eye on the blog for additional updates to our Maps SDK.

下载版本，阅读详细的文档，并关注博客，以获取对我们的Maps SDK的其他更新。