The Maps App for iOS shows how a robust application can be built around the ArcGIS Platform using the ArcGIS Runtime SDK for iOS and Swift. It demonstrates best practices around some simple but key functionality of the ArcGIS Runtime. You can use the Maps App as is, or extend it to meet your specific needs.
- Place Search
- Geocode addresses
- Reverse Geocode
- Turn-by-turn Directions
- Dynamically switch basemaps
- Open Web Maps
- Work with ArcGIS Online or an on-premise ArcGIS Portal
- OAuth authentication
The project also demonstrates some patterns for building real-world apps around the ArcGIS Runtime SDK.
- Defining a modular, decoupled UI that operates alongside a map view
- Asynchronous service and UI coding patterns
- Internal application communication patterns
You will need Xcode and the ArcGIS Runtime SDK (v100.1 or later) installed locally.
Fork the Maps App repo
Once you have forked the repo, you can make a clone and open maps-app-ios.xcodeproj in Xcode.
- Clone the Maps App
cdinto themaps-app-iosfolder- Make your changes and create a pull request
If you make changes in the fork and would like to sync those changes with the upstream repository, you must first configure the remote. This will be required when you have created local branches and would like to make a pull request to your upstream branch.
- In the Terminal (for Mac users) or command prompt (for Windows and Linux users) type
git remote -vto list the current configured remote repo for your fork. git remote add upstream https://github.com/Esri/maps-app-ios.gitto specify new remote upstream repository that will be synced with the fork. You can typegit remote -vto verify the new upstream.
If there are changes made in the Original repository, you can sync the fork to keep it updated with upstream repository.
- In the terminal, change the current working directory to your local project
- Type
git fetch upstreamto fetch the commits from the upstream repository git checkout masterto checkout your fork's local master branch.git merge upstream/masterto sync your localmasterbranch withupstream/master. Note: Your local changes will be retained and your fork's master branch will be in sync with the upstream repository.
The app can be run as is, but it's recommended you do some configuration to set up OAuth to be relevant to your users (certainly it should not be deployed without these changes):
- Register an ArcGIS Portal Application.
- Configure the Maps App project to reference that application.
- License the app to remove the Developer Mode watermark.
For OAuth configuration, create a new Application in your ArcGIS Portal to obtain a Client ID and configure a Redirect URL. The Client ID configures the ArcGIS Runtime to show your users, during the log in process, that the application was built by you and can be trusted. The Redirect URL configures the OAuth process to then return to your app once authentication is complete.
- Log in to https://developers.arcgis.com with either your ArcGIS Organizational Account or an ArcGIS Developer Account.
- Register a new Application.

- In the Authentication tab, note the Client ID and add a Redirect URL, e.g.
my-maps-app://auth. We will use this URL in the Configuring the project section below.
Configure Redirect URL
- Open the project in Xcode and browse to the
maps-app-iostarget'sInfopanel and expand theAGSConfigurationdictionary (see steps 1-4 in the screenshot below). - Set the
AppURLSchemevalue to match the Redirect URL scheme (the part before the://, e.g.my-maps-app) configured in "Register an Application" above. Note how theAppURLSchemeandAuthURLPathcombine to construct the Redirect URL.
- Expand the URL Types section and modify the existing entry.
- The Identifier doesn't matter, but should be unique (e.g.
com.my-org.my-maps-app). - The URL Scheme should match the Redirect URL scheme (the part before the
://, e.g.my-maps-app) configured in "Register an Application" above.
- The Identifier doesn't matter, but should be unique (e.g.
Configure Client ID
- In the Navigator pane, click to expand the group
maps-app-ios/Maps Appto reveal a file namedAppSettings.swift. - Within
AppSettings.swiftset the value of the static variableclientIDto the application's Client ID noted above.
Remove the Licensed for Developer Use Only watermark on the map view by setting the Runtime License Key.
This step is optional during development, but required for deployment.
- Get your Runtime Lite License Key by clicking the
Show my ArcGIS Runtime Lite license keyat the top-right of the Licensing Your ArcGIS Runtime App page (you must be logged in). - Open the project in Xcode and navigate to
AppSettings.swift, the same file used to configure your applications client id. - Set the value of the static variable
licenseKeyto the value from step 1.
Learn more about Esri Example Apps here.
- Xcode
- ArcGIS Runtime SDK for iOS
- For directions and to browse Web Maps you will also need an ArcGIS Online Organizational account or an ArcGIS Online Developer account.
Anyone and everyone is welcome to contribute. We do accept pull requests.
- Get involved
- Report issues
- Contribute code
- Improve documentation
Copyright 2017 Esri
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
A copy of the license is available in the repository's LICENSE file.
For information about licensing your deployed app, see License your app.
Some great open source components are available out there for iOS developers. The following have been used in this project, with much gratitude to their authors.
- SVProgressHUD is licensed under the MIT License.
- FlexiblePageControl is licensed under the MIT License.
Wildfire Common Operating Picture (COP)
Stakeholders • DOI Wildland Fire (BLM, BIA, NPS, FWS, USGS) • U.S. Forest Service & Interagency Partners • State Forestry & Fire Agencies • Local Fire & Emergency Management • Incident Command Teams (IMT/ICS) • Aviation Operations (Air Tankers / Helicopters) • Law Enforcement & Evacuation Authorities • Tribal Governments • Utilities & Infrastructure Operators • Public Safety Communications
⸻
Benefits (Closes Operational Gaps) • Single real-time common operating picture • Faster ignition detection & response • Predictive fire spread intelligence • Improved evacuation decision support • Enhanced firefighter safety awareness • Better aircraft coordination & deconfliction • Reduced manual reporting & radio traffic • Cross-agency situational alignment • Real-time weather & risk monitoring • After-action analytics for prevention
⸻
Technical Solution • Unified geospatial wildfire dashboard (web-based) • Multi-source data fusion: • Satellite thermal (MODIS / VIIRS / GOES) • Weather & wind models • Terrain, fuels & vegetation layers • Active fire perimeters & incidents • AI-driven fire spread prediction • Automated alerting & early warning engine • Aircraft tracking (ADS-B integration) • Mobile-friendly field interface • API layer for interagency data sharing • Cloud-hosted scalable architecture (AWS/Azure) • Historical analytics & reporting
⸻
Layout Recommendation (important)
Use: • Title at top • Three columns underneath • No more than 10pt–12pt font • Icons above each column (people / checkmark / architecture)

