Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developers.arcgis.com/swift/faq/ below:

ArcGIS Maps SDK for Swift Frequently Asked Questions | ArcGIS Maps SDK for Swift

ArcGIS Maps SDKs for Native Apps was previously known as ArcGIS Runtime SDK. It builds on the proven architecture of ArcGIS Runtime 100.x, and is designed to leverage the latest developer framework innovations.

ArcGIS Maps SDK for Swift delivers out-of-the-box support for features like Swift Concurrency, SwiftUI, structs, protocols, enums with associated values, and native Swift collections. It replaces the Objective-C based ArcGIS Runtime SDK for iOS and some rewriting of application code is required to migrate existing apps.

• Introducing the ArcGIS Maps SDKs
• ArcGIS Runtime in 2022 and beyond
• Migrating from 100.x to 200.x

No. Esri's product-specific Terms of Use (a supplement to the Master Agreement: Products) states that use of ArcGIS Maps SDKs for Native Apps in a service is not permitted. A general reference to the ArcGIS Maps SDKs for Native Apps in note 19 states "License may not be used to develop Internet or server-based Value-Added Applications".

Local data files are geo-enabled data available in a file residing on your users' device(s), regardless of how it got there. ArcGIS Maps SDKs for Native Apps support a variety of different local file data formats. Depending upon the type of data, a specific license level may be required to use that data in an application built with Native Maps SDKs.

Lite:

• View layers and packages from ArcGIS Location Platform. If ArcGIS packages contain local data that are not originally part of the ArcGIS Location Platform, viewing that data may require a higher license level. For example, to read raster files in a mobile map package or mobile scene package you need a Standard license. Refer to ArcGIS sources in the Layers page for a list of layers and packages from ArcGIS Location Platform.
• View layers from services in open formats such as WMS or KML accessed as a web resource. Access to services that are not part of ArcGIS Location Platform could require additional licensing not managed by Esri.
• Download, edit, and sync features in a public ArcGIS feature service. These services are available on the Internet and are not secured.

Basic:

• Download, edit, and sync features in a private ArcGIS feature service. These services are only accessible on a local network and/or are secured.

Standard:

• View local data that is not part of ArcGIS Location Platform, including KML accessed as a file resource, shapefiles, GeoPackages, ENC layers (S-57), local raster layers, use raster functions, and local raster elevation sources. Although this data may be generated by ArcGIS products, the data format is not owned or managed by Esri.
• Edit local data that is not part of the ArcGIS Location Platform, including shapefiles and GeoPackages.

ArcGIS Maps SDK for Local Server is a component that enhances the functionality of desktop-focused ArcGIS Maps SDKs for Native Apps applications:

• ArcGIS Maps SDK for .NET
• ArcGIS Maps SDK for Java
• ArcGIS Maps SDK for Qt

It is available as a separate installation to supplement the functionality of the Native Maps SDKs supported on Windows and Linux desktops. It is powered by packages created in ArcGIS Pro, which can be hosted by Local Server as local map, feature, and geoprocessing services. Desktop-focused Native Maps SDKs also provide a client API to access Local Server services.

Before you deploy an application built with ArcGIS Maps SDKs for Native Apps into production, you must license your app with one of the four ArcGIS Runtime license string levels: Lite, Basic, Standard, or Advanced, or implement user authentication (formerly known as Named user login and ArcGIS identity).

A license string is not required to develop applications built with ArcGIS Maps SDKs for Native Apps, and there is no need to authorize your development machine. While developing and testing, you can access all capabilities of the ArcGIS Maps SDKs for Native Apps API by omitting the license string.

A license string is required to deploy your app, even if you are using API key authentication. The license string enables specific SDK capabilities and removes the developer watermark. The access token authorizes access to content and services, such as accessing maps, geocoding, or routing services.

See License levels and capabilities for details.

The ArcGIS Runtime license level enabled for an ArcGIS account (formerly named user) is dependent upon the user type. The ArcGIS Maps SDKs for Native Apps documentation contains detailed information mapping which user type applies to each Runtime license level for all supported software in the Get a license topic.

Some user types do not include an ArcGIS Runtime license, such as Storyteller and Insights.

ArcGIS Maps SDKs for Native Apps documentation contains details about license strings, including the free Lite license string, and information about how to obtain a higher license level if required by your app. Read more at License and deployment. Also, refer to the Native Maps SDKs product-specific Terms of Use for more information.

Not by itself; Access tokens grant access to ArcGIS Location Platform services. If you are using an API key access token with one of the ArcGIS Maps SDKs for Native Apps, you must also include a license string to license your app for deployment. Refer to the Mapping and location services guide for basic requirements.

License strings are available at the free Lite level here. For paid license strings (Basic, Standard, and Advanced levels), license string extensions, or distributed deployment packs, contact your Esri account representative. The Production licenses table describes how to obtain each license level using either license strings or user authentication.

Yes, you can compile applications built with ArcGIS Maps SDKs for Native Apps with a Lite license string to provide access to Lite functionality, and also offer the ability to log in through a user authentication workflow with an ArcGIS account. See Get a license to determine what ArcGIS Runtime license level is available through which user type.

License strings are often used by customers who do not have access to an ArcGIS Online or ArcGIS Enterprise account or who are using an application that will remain offline for greater than 30 days. You are required to track the number of ArcGIS Runtime license string deployments used at each level (Basic, Standard, and Advanced), as each app installation available (including multiple apps used by a single user) counts as a deployment.

User authentication (formerly Named user login and ArcGIS identity) is typically used to sign in users with an ArcGIS account, and whose devices or applications will be online at least once every 30 days (the default timeout of user authentication workflows). A notable benefit of this model is that the license is attached to the user, not the application, so that one authorized user can license more than one ArcGIS Maps SDKs for Native Apps application.

Yes. Navigate to Your Lite license string to obtain your free unique ArcGIS Runtime Lite license string. This string can be shared across all applications with the ArcGIS Location Platform account or ArcGIS Online account from which it was created.

Note: Protect your license string: it is unique to your ArcGIS Location Platform account or ArcGIS Online account.

Applications built with ArcGIS Maps SDKs for Native Apps are licensed per deployment.

If you use a license string, you are required to track the number of ArcGIS Runtime license string deployments used at each level (Basic, Standard, and Advanced), as each app installation available (including multiple apps used by a single user) counts as a deployment.

If you implement user authentication, the license is attached to the logged-in user, not the application, so that one authorized user can license more than one application.

ArcGIS Runtime license strings for paid levels (Basic, Standard, and Advanced) or extensions are purchased from Esri and distributed via deployment packs. Upon purchase of a deployment pack, you are provided with a unique license string for the level or extension you purchased. Additional deployment packs for a level or extension you purchased previously do not include another license string, however, additional unique license strings can be provided upon request. Contact your Esri account representative.

Note: Protect your license string: it is unique to your ArcGIS Location Platform account or ArcGIS Online account.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4