ARC GIS Android Guide

ArcGIS Runtime SDK for
Android
Copyright 1995-2017 Esri. All rights reserved.

ArcGIS Runtime SDK for Android
Table of Contents
Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Get started
Install the SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Migrate to 100.1 from 10.2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Develop your first map app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Fundamentals
Maps (2D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Layers and tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Features and graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Symbols and renderers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Tasks and jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Geometries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Spatial references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Loadable pattern for asynchronous resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Work with maps (2D)
Display a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Build a new map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Add raster data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Wraparound maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Save a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Create an offline map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Create an offline layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Work with scenes (3D)
Display a scene . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Navigate a scene view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Add graphics to a scene view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Follow a graphic in a scene view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Display information
Add graphics overlays to your app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Add graphics and text to graphics overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Search
Identify features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Search for places (geocoding) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Search for related features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Edit features
Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Edit features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Relate features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Edit geometries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Sync offline edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Copyright 1995-2017 Esri. All rights reserved. 2

Route and get directions

Find a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Perform analysis
Geoprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Run a geoprocessing task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Use the cloud and servers
Access the ArcGIS platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Access portal content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Search for content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Add items to a portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Share a portal item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Release your app
License your app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Deploy your app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Reference
Release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Essential vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Geographic coordinate systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Projected coordinate systemsPart 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Projected coordinate systemsPart 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Platform error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Legal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Guide
This guide describes how to use the ArcGIS Runtime SDK for Android to build Android apps that incorporate capabilities such as mapping,
geocoding, routing, geoprocessing, and other spatial analytics provided by ArcGIS Online or your own on-premises ArcGIS servers.
A great place to start developing once you have installed and set up the SDK is to develop your first map app, or try out the samples. For
what's new in this release, see Release notes.
With the ArcGIS Runtime SDK for Android you can build apps that:
Add high performance 2D & 3D mapping and GIS capabilities to your apps.
Consume content and services from ArcGIS Online and Portal for ArcGIS (using the portal API).
Let mobile users take their work with them, provisioning them with the offline processing and data (basemaps and operational
data) that they need in the field.
Add tools to edit data while out in the field, and sync edits made offline when back online.
Search for features or attributes in your GIS data using SQL or spatial criteria and display the results.
Perform blazing fast offline searches for locations (geocode and reverse geocode).
Calculate drive times and multi-stop routes with driving directions (find routes).
Execute sophisticated geoprocessing tasks and display their results.
Allow users to add graphics and markup to a map interactively.
Display map details through informational pop-ups on features.
What you get

A rich mapping API for Android, provided through .jar files
An Android Archive (AAR) file to use as a dependency in your Gradle build script.
Full API Reference and online Guide documentation to help you learn how to use the API
A suite of samples that demonstrate SDK functionality
A Blog highlighting new developments and important SDK related news
A user to user Forum where you can discuss your development issues with other SDK developers
To find out how to get set up with this SDK, read Install and set up.

Install the SDK

You can get started developing apps with ArcGIS Runtime SDK for Android using:
Gradle (recommended)
The SDK Download
Gradle
We recommend installing with Gradle, which will install the needed dependencies and the SDK binaries from a Bintray Esri repository. For
a more detailed walkthrough of these steps, see Develop your first map app. For more information on Gradle, see https://gradle.org.
1. In the project build.gradle file, within the repositories block, add a directive to add Esri's maven repository URL to your
project. Esri's repository is not open source and therefore not available in the default repository in the script, so you must specify
this URL.
allprojects {
[...]
dependencies {
repositories {
jcenter()
// Add the Esri public Bintray Maven repository
maven {
url 'https://esri.bintray.com/arcgis'
}
}
}
[...]
}
2. In the app module build.gradle file, within the dependencies block, add a directive to include the ArcGIS Runtime SDK for
Android dependency to your app.
dependencies {
compile 'com.esri.arcgisruntime:arcgis-android:100.1.0'
[...]
}
3. Depending on what ArcGIS functionality you use in your app, it is likely you will also need to add permissions to your manifest, as
described in the following section.
You're ready to start programming with the ArcGIS Runtime SDK for Android! From here you may want to try developing your first map
app, or dive right in to samples or the API Reference.
Required permissions and features

Android is a permissions-separated operating system. Depending on what ArcGIS capabilities you use in your app, you may need to
add permissions to your manifest, as follows. Be sure not to include permissions for capabilities not included in your app.
If an app is running on Android API level 22 or below, all permissions are requested, and granted or denied, at install time. If an app is
running on Android API level 23 or above, normal permissions are requested and automatically granted at install time; however,
dangerous permissions must be requested at run timeyou will need to add code to your app to do this. The Android framework or
Android Support library can be used to check for permissions, and request permissions if not already granted. For more information, see
Declaring Permissions and Requesting Permissions at Run Time.
ArcGIS Runtime SDK for Android capabilities that require permissions:
Access to the Internet (most apps will require this) - normal permission in Android API 23 and above
Access to files on disk (some apps will require this) - dangerous permission in Android API 23 and above
Access to the device's GPS will require fine location permissions - dangerous permission in Android API 23 and above
Apps that use MapView will require using OpenGL 2.x
The following code example (for the AndroidManifest.xml file) includes permissions for all capabilities. Note that OpenGL is included as
a feature.
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-feature android:glEsVersion="0x00020000" android:required="true" />

SDK download
The best way to ensure that the ArcGIS Runtime SDK for Android is properly setup and updated is to make use of Gradle, as described
above. However the SDK can also be downloaded, and added to your project manually by including the local AAR and all dependency
artifacts. You can also download a separate PDF of the Guide documentation.
Download, install, and set up the local SDK

1. Sign in to ArcGIS for Developers.
2. Click the Downloads icon at the top right of the page and download the ArcGIS Runtime SDK for Android to your machine.
3. Unzip the downloaded archive to a location on your development machine.
Now you can manually add dependencies to the ArcGIS Runtime SDK for Android, or use other resources contained in the download.
Note: You can also download previously released versions of the SDK from the same Downloads
page.
Contents of the SDK download
The download contains everything you need to develop ArcGIS Runtime SDK for Android apps.
doc: API reference documentation
legal: Licensing documentation
libs: An Android library module (.aar), containing API jar libraries arcgis-android-api and it's third-party dependencies, and
core native libraries

Migrate to 100.1 from 10.2.x

When you compile your 10.2.x application code against 100.x libraries for the first time, you will get a lot of compilation errors.
Conceptually, you'll need to consider 100.x as almost a different product from the previous versions of ArcGIS Runtime. In reality it is the
same product, but it will best serve you to think about it as a different API, at least from the beginning. The way in which your workflows
are achieved has been re-designed in many cases to fit better with the ArcGIS platform and the Web GIS model as it has evolved today.
The aim of this topic is to outline areas of the API that have undergone considerable changes and to provide guidance for re-factoring
10.2.x code for a 100.x app. Although not an exhaustive list, it will help you get past some of the major migration hurdles. It will also help
you decide whether functionality required for your app is available in 100.x. In some cases, it might be better to wait for a future release of
the 100.x family before migrating a particular app.
Functional changes
In many cases, functionality that appears to be missing from 100.1 is available but has been implemented differently. These changes
generally require you to rework your code to use new programming patterns or classes. The following sections describe some of the
functional areas of the API where these types of changes have been implemented.
Maps
The Map object has been split out from the view that displays it, to represent the model or viewmodelcomponent in a Model-View-
Controller (MVC) or Model-View-ViewModel (MVVM) architecture. These important objects are at the heart of the ArcGIS Runtime and
have an API that follows the ArcGIS Web GIS information model. They contain operational layers, basemaps, bookmarks, pop-ups, and
other ArcGIS specific data to be leveraged in your apps. They also include APIs to instantiate maps from URLs, portal items, or default
basemaps. For details on how to add views and maps to your 100.1 apps, see Build a new map.
Views
The GeoView interface, implemented by MapView, is solely responsible for display and interaction, separating concerns from model
objects, e.g. ArcGISMap. The Views contain graphics overlays, as well as operations, to easily identify features and graphics without
having to write any layer type specific code. There is a lot you can control with the GeoView.
Loadable
The Loadable interface was newly introduced at 100.0.0. It's design and purpose is intended for those workflows that involve
accessing lots of data over the wire from connected online resources. All resources, such as maps, layers, tasks etc, that load metadata
asynchronously to initialize their state adopt the loadable pattern. The loadable pattern makes the behavior of loading state more
consistent and uniform, and also makes its asynchronous nature more explicit. Loadable resources do not automatically load their state.
They load lazily, when asked either by the developer, or by other objects that depend on them. This becomes quite useful for those
cases where you may, for example, what to obtain information from a map resource without having to visualize it first. The status of a
loadable resource can be easily monitored to determine if it is loading, loaded successfully, or failed to load, and you can retry loading it
if it failed to load.
Common use cases for using Loadable are explained and demonstrated through code examples in the Loadable pattern topic.
If 10.2.x versions of your apps performed editing tasks involving feature services, it's important for you to understand the new loadable
pattern clearly. Features from an ArcGISFeatureTable return ArcGISFeature objects which implement the loadable pattern for
increased efficiency. When getting ArcGISFeature objects for rendering and query purposes, a minimum set of required fields is
returned, such as identifiers, geometry, fields used for symbolizing, and so on. When you want to edit the feature, you must load it first,
otherwise the edit operation will fail. For complete details and code examples of loading features in editing workflows, see the Edit
features guide topic.
Graphics overlays and graphics

Graphics have always been used to display temporary or ad-hoc geographic data on top of a map. In 10.2.x, you added graphics to
your map using a GraphicsLayer. Graphics are now added to GeoViews as overlays. This ensures that graphics are always displayed
on top, even when map layers are reordered. This also makes it convenient to switch out maps while still keeping the graphics in place.
The guide topic Add graphics overlays to your app provides code for creating graphics overlays and adding them to the map. You can
see the code for adding and working with graphics in a graphics overlay in Add graphics and text to graphics overlays.

At 100.x, there is also a simpler pattern for identifying graphics within graphics overlays. The identifyGraphicsOverlayAsync
method on GeoView (MapView or SceneView) identifies visible graphics in the specified graphics overlay, near the provided screen
point. The Identify Graphic code example demonstrates the usage of this method.
Feature tables
ServiceFeatureTable now has a FeatureRequestMode that is similar to the 10.2.x Mode property (Snapshot or OnDemand). The
value determines how features are requested from the service for use in the client.
On Interaction with Caching - Features are requested and stored in the table when needed based on user interaction (panning
or zooming to different extents, for example). Features are cached to reduce the number of requests for features.
On Interaction without Caching - Features are always requested from the service. There is no caching of features, so this
consumes the largest amount of network bandwidth.
Manual Caching - Features are only requested when explicitly requested by the app. All queries are made to the local version of
the data.
Offline
The APIs for common operations such as editing, searching, geocoding or routing are the same whether you are online or offline. This is
one of the big differences to keep in mind at 100.x. Also, with respect to packaging Offline maps, ArcGIS Pro comes center-stage with
the ability to create and share offline mobile map packages. A Mobile Map Package (.mmpk) is a set of items bundled together for
transport, often for use in offline workflows. The items are one or more maps, their associated layers and data, and optionally networks
and locators. A mobile map package also includes metadata about the package that you can glean useful information from using the
new API. You don't need a Local Server to access these packages.
Check out the MobileMapPackage class in the API reference and the Open a mobile map section of this topic for a thorough
description of how to work with Mobile Map Packages. There is a helpful code sample for opening and using mobile map packages as
well.
You can also take your connected ArcGIS based feature and tiled layers offline on demand with dedicated tasks and associated jobs,
just as you were able to with previous versions. However, you might find that the class names and methods differ slightly from previous
versions. The GeodatabaseSyncTask works with ArcGIS feature services to take features offline in a mobile geodatabase
(.geodatabase file) and allow them to be edited and synced. The ExportTileCacheTask extracts tiles from a tiled ArcGIS map
service as a tile package (.tpk file) and allows them to be viewed offline.
The Edit features guide topic provides code examples and in-depth discussion for editing both online and offline with the new API.
Authentication
All security and authentication related aspects are managed by a new AuthenticationManager class which helps to unify and
centralize how authentication is performed, regardless of the security solution in place. It allows the developer to have as little or as
much control over how authentication related issues are handled in an app. It also caches credentials by default and therefore reduces
the number of times a user is prompted for credentials. The authentication manager issues an authentication challenge whenever
security related events are encountered. Developers can monitor these challenges and respond with credentials to get access to
secured resources, or allow the authentication manager to prompt the end user for credentials.
Portal
The mapping API has been re-factored to be more integrated with the portal API at version 100.x. The API allows you to load maps
stored in a portal (web maps) into your app, make updates to web maps and save changes back to the portal item, and save maps
created with your runtime app as a new portal item. These web maps can then be used elsewhere within the ArcGIS system.
The concepts and code examples for displaying a web map by ID and/or "opening" a web map without the need to display it are covered
here, in the Access content topic. Also in this topic, you'll find useful examples of how to fetch thumbnails of items, access portal item
data, as well as list the groups that a user belongs to.
If your applications will be taking advantage of the new map saving capabilities, the Save a map topic will provide great examples for
doing this. See the Create and Save a Map sample for code as well.
Error handling
Certainly you've had to handle errors in your applications in many different ways. With 100.x, it's now easier to determine where errors
occur in the stack so you can provide better error messages to your Runtime app users. A new standardized error domain property is

available, which indicates if the error occurred client-side within the ArcGIS Runtime or server-side from an ArcGIS Server service or
web service. A consistent error code property can be used to further diagnose what the error was and what error message should be
displayed to the user. For a complete list of error domains and codes, please see the Platform error codes topic in the guide.

Develop your first map app

This tutorial guides you through the process of creating a basic mapping app with the ArcGIS Runtime SDK for Android, that displays a
map using a specific initial map extent, using the Android Studio integrated development environment (IDE).
You can view the completed code as a sample in the Display a Map sample.
Prerequisites
Before you start, make sure you've done the following:
Met the system requirements.
Installed Android Studio, the official IDE for Android, from Google.
Acquired a basic understanding of developing apps for the Android platform and the terminology used. See the Android
Developers homepage for information.
Create a new project in Android Studio

When you start Android Studio, the Welcome screen is displayed. From here, you can create a new Android app project.
1. Under Quick Start, click Start a new Android Studio project.

If you already have a project open, you can click File > New > New Project.
2. In the Application name text box, type Display map.
Optionally, change the Company Name and Project Location, and click Next.
3. Leave the default Phone and Tablet option selected, choose API 16: Android 4.1 or later from the Minimum SDK drop-down
list, and click Next. (Note that different Android Studio versions may have different default Android SDK versions.)
4. Click Empty Activity, and click Next.
5. Leave the default names in the remainder of the wizard and click Finish.
A new Android app project opens, showing a default layout.

You have now successfully created an Android project containing an app module. Next you'll add the ArcGIS Runtime SDK for Android
dependency.
Add the ArcGIS Runtime SDK for Android AAR dependency

Here you'll update the gradle build script to add the ArcGIS Runtime SDK for Android dependency to your app module. This will
automatically download the Android Archive (AAR) package from the Esri public Bintray Maven repository when you build your app.
Android is a permissions-separated operating system. You'll also add permissions for the functionality your app requires.
1. In the Android project view window, under Gradle Scripts, double-click build.gradle (Project: <project name>). This opens
the gradle build script for the whole project.
This opens the gradle build script for your application module. If you are unfamiliar with the Gradle build system, see Build
System Overview.
2. In the repositories section of the script, add a new section maven, with a value url 'https://esri.bintray.com/
arcgis'. The full section should now look like the code below:
allprojects {
repositories {
jcenter()
// Add the Esri public Bintray Maven repository
maven {
url 'https://esri.bintray.com/arcgis'
}
}
This directive tells Gradle where to look for the ArcGIS Runtime SDK for Android dependencies, by specifying a Maven repository
URL.
3. In the Android project view window, under Gradle Scripts, double-click build.gradle (Module: <module name>).
4. In the dependencies section of the script, add a new value "compile 'com.esri.arcgisruntime:arcgis-android:100.1.0'". The
dependencies section should now look like the code belowthe exact list of dependencies present will depend on the version of
Android Studio and the project settings chosen:
dependencies {
compile 'com.esri.arcgisruntime:arcgis-android:100.1.0'
compile fileTree(dir: 'libs', include: ['*.jar'])
[more dependencies...]
}
5. In the Android Studio toolbar, click Sync Project with Gradle Files. Alternatively, when you see the Gradle files have changed
since last project sync message at the top of the gradle script window, click Sync Now.
6. In the Android project view window, under app > manifests, double-click AndroidManifest.xml.
This opens the manifest file for your app.
7. Add the following XML elements as children of the existing manifest:
<uses-permission android:name="android.permission.INTERNET" />
<uses-feature android:glEsVersion="0x00020000" android:required="true" />
This informs the Android launcher that your app requires permission to access the Internet. If an app is running on Android API
level 23 or above, normal permissions are requested at install timeinternet access is a normal permission, so no additional
work is required to enable this permission. It also indicates that your app requires the OpenGL version 2.0 software feature for
the app to run. Most apps you develop with the ArcGIS Runtime SDK for Android will need this feature and a minimum of this
permission. For more information, see the Android Developers topics Android Permissions and Uses Feature Element.
You've added a dependency to the ArcGIS Runtime SDK for Android AAR to your app module. Next, you'll add a map showing a map
service to the app and set up an initial extent for that map.
Add a MapView to your layout

Now that you've created an app with an ArcGIS Runtime SDK for Android AAR dependency, the next step is to add a MapView to the
activity layout.
1. In the Android project view window, under app, click res > layout, and double-click activity_main.xml.

This opens the Preview view of the central content for the main activity layout. Note that depending on the exact Android Studio
version you are using and the initial activity template you chose, the project may contain multiple layout XML filesfor example if
you chose the Basic Activity template, you may need to instead open the content_main.xml layout.
2. At the lower left of the window, click Text to show the XML view of the layout if it's not already shown.
By default, there are two tags in the layout XML file.
The first is an Android RelativeLayout. This is a view that can show other views inside itself. It arranges its children
views relative to each other. For more information, see the Relative Layout and User Interface documentation from
Google.
The second is a TextView, a child of the relative layout, displaying the text "Hello world!".
3. Select the entire TextView XML element and replace it with a MapView element as follows:
<com.esri.arcgisruntime.mapping.view.MapView
android:id="@+id/mapView"
android:layout_width="fill_parent"
android:layout_height="fill_parent" >
</com.esri.arcgisruntime.mapping.view.MapView>
For a more comprehensive understanding of the declarative approach to user interface (UI) design, see Declaring Layout.
Set a map on the MapView

By default, a MapView does not display anything, so the next step is to define a map to be displayed. You will specify that the map shows
a worldwide topographic basemap from ArcGIS Online. As it's often more useful for an app to initially display a specific region rather than
its entire extent, you'll also set the map to zoom in to a specific center pointshowing the Esri campus in Redlands, California.
1. In the Android project view window, under app, click java > [package name], and double-click MainActivity.
This opens the Java code defining the default activity of your app.
2. Add the following class variable declaration to the top of the MainActivity class:
private MapView mMapView;
3. Android Studio will highlight in red the MapView class, which must be imported into the class. Place the pointer at the line with
text highlighted in red and press Alt+Enter to resolve the symbol. Choose to import
com.esri.arcgisruntime.mapping.view.MapView.
import com.esri.arcgisruntime.mapping.view.MapView;
4. Add the following code to the onCreate method, after the existing call to setContentView:
mMapView = (MapView) findViewById(R.id.mapView);
ArcGISMap map = new ArcGISMap(Basemap.Type.TOPOGRAPHIC, 34.056295, -117.195800, 16);
mMapView.setMap(map);
Note: You'll need to import com.esri.arcgisruntime.mapping.ArcGISMap and

com.esri.arcgisruntime.mapping.Basemap.
This code gets a reference to the MapView defined in the layout. An ArcGISMap is created with a specific predefined
Basemap.Type, centered at a specific set of coordinates, and zoomed to a specific level of detail. The ArcGISMap is then set
into the MapView.
5. Add the following code to override the onPause and onResume methods of the activity, and pause and resume the MapView
when those methods are called:
@Override
protected void onPause(){
mMapView.pause();
super.onPause();
}
@Override
protected void onResume(){
super.onResume();
mMapView.resume();
}
You have now completed the steps to add an ArcGIS Runtime SDK for Android map to your new Android app. You are now ready to build
and test your app.

Build and run the app

To test your app, you need to have either a connected device ready for debugging or an emulator set up and started. To find our more, see
the Android documentation Using the emulator or Using hardware devices.
1. On the Android Studio toolbar, click Run.

2. On the Choose Device dialog box, choose the device or emulator you're going to use, and click OK.
3. When the app opens on your device, it shows a street map centered on Redlands, California. You can double-tap the map to
zoom in.
When you create a new project, Android Studio automatically creates a run configuration to launch the app on your device. You'll see
something similar to the following screen shot:
That's it, you've completed your first ArcGIS Runtime SDK for Android app.
Don't forget that you can view the completed code in our Display a Map sample on GitHub.

Maps (2D)
A map can tell a story, present an idea, or showcase a situation. It can help you do hundreds of things, from finding the nearest hospital to
viewing earthquake events in relation to high-population areas.
Unlike most maps, ArcGIS maps have many additional capabilities. For example, they can contain data organized by layers and can
contain analysis capabilities that let you reveal patterns and solve many types of problems. You can use your own data, Esri's data, or
both in your app's map.
A map is typically composed of a basemap that provides geographic context and operational layers that contain the salient content of the
map.
In ArcGIS Runtime apps, a map is used in conjunction with a map view to visualize geographic data on a screen. A map represents the
model tier in an MVC architecture, and a map view represents the view tier:
A map specifies where the geographic content (data) comes from and how it's organized (what layers it has, what bookmarks,
initial viewpoint, and so on). Content in the layers may come from a variety of map sources, including from online sources or from
local data stores, such as a feature table in a mobile geodatabase or data from a mobile map package. For more information on
the data and layer types you can include in a map, see Layers and tables.
A map view renders the map's content and controls how users navigate and interact with the map. Operations such as rotation,
panning, and zooming allow the user to change their viewpoint of the map. A map view can have graphic overlays for displaying
graphics over the map, such as the results from a query or analysis. A map view translates display coordinates to map coordinates
so your app can associate user interactions with map coordinates.
ArcGIS Runtime provides map and map view objects that you can use to build new maps, display maps, save maps and share maps. Also
see the API reference.
Note: When you use spatial data from different layers or map sources in your map for
viewing or analysis, you may need to consider spatial reference. For details, see
Spatial references.
Objects that can be symbolized on your map can come from persisted data (feature
data, such as roads and parcels in a geodatabase) and transient data (graphics, such
as data coming through a web socket). For details, see Features and graphics, and
Symbols and renderers.

Map sources
Online maps
ArcGIS includes a Living Atlas of the World with beautiful and authoritative maps on thousands of topics. Explore maps and data from
Esri and thousands of other organizations and combine them with your own data to create new maps and applications.
A map you create in an ArcGIS Online's map viewer is an interactive map that displays geographic information to tell stories and answer
questions. These maps are available to a wide audience and include multi-scale basemaps, layers targeted to a specific audience, and
information pop-ups that allow users to drill into specific features they are interested in. These maps also support visualization, editing,
analysis, and time. Maps can be viewed on a wide variety of clients, including mobile apps, desktop apps, and web browsers. How-to
steps for creating these maps are in ArcGIS Online Help's get started with maps topic.
You can create maps, share maps, and load maps into your app from ArcGIS Online or from any organization's portal.
Offline maps
Offline maps are an important part of the ArcGIS systems where users can work in a partially or fully disconnected environment. Offline
maps support visualization, editing and syncing edits, routing and geocoding. With this data your users can get directions to a location,
explore the surrounding area, and work with their assets. You can use ArcGIS to author data for offline use using different patterns
where the main two ways are called service pattern and desktop pattern. For details, see Offline.
Note: If you'd like a ready-to-use and regularly updated street map in your offline maps (that
includes a locator and network dataset) see Add StreetMap Premium data.
Services pattern
If you want to create offline data on-demand from services use the Services pattern. You can use the offline map task to take the
whole map offline if your online map is authored for offline use. For details, see the Services pattern on Create an offline map. You
can also take individual layers directly offline. For more details, see Services pattern on Create offline layers.
Desktop pattern
If you want to pre-created data that is distributed to the client use the Desktop pattern. This workflow is `view-only` so you cannot
make edits to the data that is synchronized back to the original data source. With ArcGIS Pro you can create mobile map packages
which combine your organizations maps, assets, road networks, or locators into a single file. For details, see Mobile map package.
You can also create packages for individual layers using ArcGIS Desktop. For more details see Desktop pattern on Create an offline
layer.

Offline
Offline maps allow your users to continue being highly productive even when their network connectivity is poor or non-existent. Your apps
will allow users to view maps, collect information, update data, find places and route to new locations, all while disconnected from the
Internet. If you wish you can synchronize the map updates with other users once a connection is re-established.
Capabilities of your offline map

You can add the following capabilities to your offline map:
Viewing basemaps: (often using tiled raster or vector layers but also using compressed mobile basemap layers). Tiled layers
consist of either raster tiles or vector tiles. Raster tile layers (sometimes referred to in platform documentation simply as tiled
layers) are pixel-based images of the basemap with cartography pre-rendered at multiple scales. Using less data than raster tile
layers, vector tiled layers deliver cartography that often looks better on high resolution devices because they are rendered quickly
on-the-fly using the display's native resolution.
Editing operational data: (also known as feature data or vector data). This includes querying and editing the location, shape,
attributes, related tables, and attachments of features.
Syncing edits: when online again, upload edits made on the device and/or pull down only the updated features that others have
edited, if your data is service based.
Performing blazing fast searches for locations (geocode and reverse geocode) and routes. For details, see Search for places.
Offline map patterns

There are two main patterns available for building offline apps with ArcGIS Runtime:
Services pattern: Best for supporting numerous users who share data, this pattern allows multiple offline users to edit the same
data layers and synchronize edits later, when online.
Desktop pattern: Best for supporting apps with read-only data that requires periodic updates.
Note: License: An app licensed at the Lite level can include viewing offline basemaps, viewing and
downloading updates to offline feature data contained in a geodatabase, working with offline
routing and geocoding. The Basic license level adds more capabilities including offline editing
and uploading edits to a sync-enabled feature service. A standard license level is required for any
use of Local Server. See License your app for more information on license levels.
Services pattern
The services pattern is best for supporting numerous users who share data. This pattern allows multiple offline users to edit the same data
layers and synchronize edits later, when online.
Data
Operational Data
For operational data, you can use a sync-enabled feature service from ArcGIS Online or ArcGIS Enterprise to create a mobile
geodatabase for offline use. Through the synchronization process, you can control whether a user can upload their edits, download
others' edits, or both. This allows the app to maintain an up-to-date view of the data. When more than one user is editing the same
feature and the edits conflict, the last edit synchronized to the service overrides the others.
For details on using hosted feature layers, see manage hosted feature layers in the ArcGIS Online help. For details on using ArcGIS
Server feature services, see preparing data for offline use and Tutorial: Setting up feature service data for offline use in the ArcGIS
Server documentation.
Basemap Data
For basemap data, ArcGIS tiled map services and ArcGIS Online basemaps allow for the on-demand creation of raster tile caches,
letting you take your basemaps offline. This can be from your own ArcGIS Server or a hosted tile layer. For details on enabling export
of tiled map services, see Allow clients to export cache tiles in the ArcGIS Server documentation.
Esri offers a set of basemaps that supports offline use. These services require an ArcGIS Online organizational subscription or an
ArcGIS Developer account. These services do not consume credits.

Create an offline map

You can author a map that can be taken offline. The easiest way to create one is to use ArcGIS Online or ArcGIS Enterprise authoring
tools. For more details on how to create a map, seeGet started with maps in the ArcGIS Online documentation. Remember to share the
map after it has been created to your desired audience. For more detail on how to share a map, see Share maps in the ArcGIS Online
documentation. You can also author maps using ArcGIS Runtime SDKs.
When building a map that is planned to be taken offline, you need to add layers that have offline capabilities enabled. Any layers that do
not have offline capabilities cannot be taken offline.
Your app can create a local copy of your map using the OfflineMapTask. This task requests all of the services that are needed to
generate the offline data, and then downloads and stores that data into your device. After the map has been downloaded, your app can
go offline and start using offline map. For more detail on how to work with the OfflineMapTask see Services section of the Create an
offline map document.
Note: In release 100.1 the OfflineMapTask supports the following layer types : tiled services,
feature services and feature collections
The advantage of this approach is that you will have a one single document that describes your offline map, its layers and symbology.
This map can be used in multiple applications, if needed, and you can make changes to it easily.
Note: If you need to provide offline routing or geocoding in the application, create the locator and
network datasets using the desktop pattern.
Create offline layers

You can also create individual layers and take each of them offline using the ArcGIS Runtime SDK. This level of control will allow you to
manage how and when the data is generated and stored on the device. For more details on how to take individual layers offline, see the
create an offline layer documentation
If you need to access the same geodatabase on many devices, you can generate it once and load it onto the devices. This pre-planned
workflow will reduce the number of requests made to the server but requires that you register the geodatabase with every device.
Desktop pattern
The desktop pattern is best for supporting apps with read-only data requiring periodic updates. In this pattern the content is created before
delivery to the clients by using ArcGIS Desktop or other means. This content can include features, tabular data, tile caches, network
datasets for directions and locators. The content can be packaged individually or combined into a mobile map package.
Any of these packages can be shared with your ArcGIS organizational account, downloaded or sideloaded directly to your device.

Offline map can be packaged within a mobile map package (.mmpk files) using ArcGIS Pro. Each package can contain multiple maps,
their associated layers and data, and optionally networks and locators. After the mobile map package is downloaded or sideloaded onto
your device, you can use the MobileMapPackage class to open the package and start using the offline map. For more detail on how to
work with mobile map packages see the create an offline map documentation.
One advantage of this approach is that you can prepare the data using ArcGIS Pro and sideload it directly onto the devices without
needing an internet connection at any point. You can also prepare the data once and deliver a copy of it to many devices without
needing to generate packages on demand one by one.
Note: Currently all mobile map packages that are authored by ArcGIS Pro are read-only.
For more detail on how to create a mobile map package, see create a map package from ArcGIS Pro documentation. If you'd like a
ready-to-use and regularly updated network dataset (and locator) for your area of interest, you can license StreetMap Premium data (in
mobile map package format). For details, see add StreetMap Premium data.
Create offline layers

You can also create individual layer packages directly from the ArcGIS for Desktop or ArcGIS Pro. This approach will provide you with
more control over when individual packages are generated and you can work with each package separately.

ArcGIS Desktop can also be used for creating runtime content but with limited capabilities. For more information see creating ArcGIS
Runtime content in the ArcMap help.
For more detail on how to work with individual layer packages, see create an offline layer documentation.

Layers and tables

In ArcGIS, a layer is used to display geographic data in a map. In general, a layer's data comes from a single source, such as a map
service URL or geodatabase table. A layer uses an associated renderer to symbolize data and might also define properties for the display
of things like labels and pop-ups. This decoupling of the layer's data and how it's rendered gives you the flexibility to present the same
data in a variety of ways. As the name indicates, layers are stacked or "layered" in the map and drawn from bottom to top. As a developer,
you can control the order of the layer in the map as well as it's visibility. Many apps also provide this functionality in the UI, allowing the
user to turn layers on and off, move them up and down in the display order, or even change how they are rendered.
In short, layers give your users the ability to visualize, explore, analyze, query, and edit geographic data. This SDK provides you with a
wide range of layer types to access many different geographic data sources. The functionality and performance of these layers depend on
the characteristics of the data and how it is accessed and displayed in an app.
A table is a data source for ArcGIS data and may or may not contain geometry information. A table can contain related features. Some
areas of the ArcGIS Platform use the term "table" to refer only to a table with no geometry information. In ArcGIS Runtime, such tables are
referred to as non-spatial tables. A non-spatial table can store descriptive information but doesn't store a geographical component so its
features cannot be drawn on a map. It can share the same data source as a layer, but it doesn't include geometry.
This document describes the major layer types, outlines their characteristics, and indicates how you would typically expect to use them. It
also describes non-spatial tables. You can get references to layers and tables from an existing map, or you can build a new map by
creating and adding layers and tables to it.
Choosing layer types

Layers allow access to a range of geographic data sources. These data sources may be static in nature or may contain data that changes
over time. Your choice of layer type will be driven by factors such as the source of the data, how you want to access and display the data,
and your specific performance criteria.
Data sources
There are lots of sources of geographic data.
Online data sources are provided by online GIS web services that include map services and feature services.
ArcGIS map services fall into two broad categories: tiled and dynamic. Tiled services provide pre-generated (cached) tiles based on the
tiling scheme of the layer. Tiles may be provided as raster image tiles or as vector data tiles. The layer then assembles these tiles in the
client app. You can access a tiled map service using a tiled layer. Dynamic map services, however, provide map images created on the
fly as requested by the client. You can access dynamic map services using a map image layer.
Feature services allow you to access individual features in a map. Feature services such as those from ArcGIS Enterprise and ArcGIS
Online return sets of features from a single layer in response to the map's visible extent, or to an attribute or spatial query. You can
access this type of service using a feature layer.
An ArcGIS image service provides access to raster data through a web service. An image service can be cached like a map service to
improve performance. When an image service has been cached, it supports dynamic access and tiled access. Dynamic access
provides access to data, for queries and for downloading, plus access to individual items. It also provides access to data for use in
processing and analysis while tiled access provides faster and more scalable access to pre-cooked tiles as a tiled service. To access an
image service as a dynamic image service, use a raster layer which allows you to retrieve the metadata of the image service and use
the data with raster functions to do analysis. To access a cached image service as a tiled service, use a tiled layer which only allows you
to retrieve metadata of a tiled service and display the tiled image.
You can also access data sources such as mobile map packages or tile packages, located locally or on a network. These local data
sources also have specific types of layers to access the data.
Note: Geographic data that is generated temporarily (for example, the results of a query or the
location of a GPS) is often displayed on a short-term basis in a graphics overlay. See Add
graphics overlays to your app for more information.
Layer classes
Layers allow you access to the data sources described above. The diagram below shows the major layer classes in the API and
inheritance relationships. Class names in italics are abstract.

Common layer properties

All layer classes inherit common properties from the Layer class. This class implements the Loadable interface, that provides the
asynchronous pattern for loading the layer's resources. The class also implements the LayerContent interface . Some of the common
properties of this class and its interfaces are listed below:
Display the layer's name using the getName method.
See the layer's description using the getDescription method.
Get the layer's full extent using the getFullExtent method.
Determine what spatial reference is used by the layer using the getSpatialReference method.
Hide and show the layer using the setVisible method.
Control how transparent or opaque a layer is using the setOpacity method using the opacity property.
Change the visible layer's scale range thresholds using the setMinScale and setMaxScale methods.
Layers with image-based data sources may be image adjustment layers (inherit from ImageAdjustmentLayer) which allows the
brightness, contrast, and gamma of the layer to be adjusted at run time. The underlying data source is not changed.
Each layer class is used as either a basemap or an operational layer. The following sections discuss the typical classes to use for your
basemap or operational layers. However, these are not absolute rules, and the choice of class should be based on an understanding of
the functional and performance characteristics of each type as outlined below.
Basemap layers
A basemap provides your map with a rich contextual background to help users orient the map. It provides a visual framework on which
you can overlay operational layers, perform analysis, and visualize geographic information.
Basemap data is typically provisioned from:
ArcGIS Online which provides a number of ready-to-use basemaps such as Streets, Topographic, Imagery with Labels, and so on
Your organization's own business focused basemaps
Mashing up your own layers together
If you are creating your own basemap it is important to consider:
It may be appropriate to publish your data as a dynamic (non-cached) map service if the data changes frequently or if the data is
to be used in maps with different projections. You access this data using an ArcGIS map image layer.
If the basemap data is relatively static then it may be more appropriate to publish it as a tiled (cached) map service. In this case
you can display this data using an ArcGIS tiled layer.
If your users will not have reliable connectivity, consider providing offline basemapsfor example as a tile package, local tile
cache, or mobile map package.
Data storage space can be decreased and drawing performance increased with the use of vector tiled layers.
The following describes the types of online and offline tiled layers that are used as basemap layers.
Online tiled layers

API classes: ArcGISTiledLayer, ArcGISVectorTiledLayerTiled map service layers are connected to cached map services
that provide map tiles at predefined scales in a tiling scheme. The tiling scheme is set by the server. The tiles may be either image
(raster images), or vector (tiled vector information) tiles. They are drawn on the map view and arranged into their tiling scheme by the

client API. Map image tiled services can contain multiple sublayers. The same classes can also be used offline, to display tiles from
local tile packages (.tpk, .vtpk files).
Functional characteristics
Each tile is cached on the server and must be considered as a static map service. It cannot change over time unless the cache is
refreshed. You cannot reproject the tile into a different spatial reference, you cannot change the visibility of the individual sub-layers,
and the layer cannot be queried or edited. Additionally, vector tiles adapt seamlessly to the resolution of the display, can be restyled
locally (for example for nighttime schemes), and can be rotated while labels remain unrotated.
Performance characteristics
The tiles are generated only once when the cache is originally created on the server. If a map extent requires multiple tiles each tile
request can be made on multiple threads. The responses are then handled asynchronously so that tiles are requested and drawn
individually from one another. This approach results in many small requests to the server and little client-side processing to draw the
returned images. The size of each returned tile increases as the resolution or complexity of the image or vectors in the tile increases.
For example, high-resolution imagery tiles can be larger in file size than topographic mapping for the same area and map extent.
Vector tiles are generally significantly smaller than image tiles for the same area and extent, and are tailored for rapid display.
Offline tiled layers

API classes: ArcGISTiledLayer, ArcGISVectorTiledLayerA cache of tiles can be created, provisioned to the client device,
and displayed as a layer in an app, without the need to remain connected to the service. For a raster tiled map service, you can use
ExportTileCacheTask to generate and download a cache directly from the service to the device. The cache may be a single raster
Tile Package (.tpk) file, or an ArcGIS Compact Cache. Alternatively you can use ArcGIS Pro to create a map tile package or vector tile
package and provision it to the device.
Functional and performance characteristics
Local tiled layers display even faster than tiled service layers, as no network calls are required to retrieve the image tiles. However,
data must be prepared in advance by being generated and downloaded to the device over the network, or by provisioning the
generated files directly to the device file storage. Other functional and performance characteristics are similar to that of tiled service
layers.
Mobile basemap layers

API classes: MobileBasemapLayerA mobile map package can be created in ArcGIS Pro and provisioned for display in your app.
The package may contain one or more mobile maps, each of which contains a basemap with mobile basemap layers. They contain
vector features in a compressed format.
A mobile basemap layer represents multiple feature layers from a geodatabase, rendered together in a group to form a vector basemap.
This layer abstracts the complexity of many layers into a single, simple-to-use basemap layer.
Functional and performance characteristics
Like offline tiled layers, mobile basemap layers display quickly because no network calls are required to retrieve the data. However,
data must be prepared in advance in ArcGIS Pro and downloaded to the device over the network, or by provisioning the generated
files directly to the device file storage. You cannot select, query, or edit features in a mobile basemap layer.
Operational layers
Operational layers focus primarily on data that changes more frequently than that of a basemap. Online operational data can be
provisioned as either a feature service accessible using a feature layer, or as a dynamic (non-cached) map service accessed using a map
image layer. The choice of service type depends on what functionality and performance characteristics are required. If editing is required
then a feature service is appropriate; however, if complex rendering is required, a dynamic map service may be more appropriate. More
differences are highlighted below.
Feature layers
Feature layers display data from feature services or from supported local data sources such as geodatabases. Feature layers can be
used to display, select, and query features in a layer. If the underlying feature service or table supports editing, you can use it with a
feature layer as a basis for editing geometry, attributes, and attachments. Features also form the basis for spatial analysis, comparing

features' spatial relationships and attributes. No matter what your field of work is, spatial analysis helps to derive additional information
from your data for better decision making.
Features in a feature layer are retrieved from a feature service as the app is used, or alternatively, are read from a feature data source
stored locally on the machine. Features can also be downloaded from a sync-enabled feature service when the device is connected and
cached locally for use when the device is offline. Choose from the options below (online, offline, or offline with sync) according to the
workflows you want to support in your app.
Online
API classes: FeatureLayer (based on a ServiceFeatureTable)The geometry, attributes, and attachments of features from a
feature service are temporarily cached in a table on the client. The feature layer uses this table to draw the features natively in the
map, based on the map extent. New features are retrieved automatically when you navigate the map. The local table cache is
discarded when the layer is disposed.
Create and initialize a ServiceFeatureTable using a URL of the service, then create a FeatureLayer by passing in the
ServiceFeatureTable to the constructor, and add the FeatureLayer to the map. The ServiceFeatureTable class is a
subtype of FeatureTable, which is used for offline feature layers.
Feature request modes The feature request mode controls how often features are retrieved from the service and how it is cached
on the client. ServiceFeatureTable supports three different modes, which significantly affect the functionality and performance of
the layer. You can set the mode you require by using the setFeatureRequestMode method of the ServiceFeatureTable before
the table is initialized.
On interaction cacheThe default mode for spatial and non-spatial tables. This mode is best for editing data that does not
change frequently on the server, or if there is a large amount of data on the service. This mode is recommended if you have
an occasional or unreliable connection to the service. When the table is used in a layer in a map, features are requested for
the visible extent and are cached locally. Features continue to be requested and cached as you navigate the map to other
extents. For extents that have already been visited, features are not requested again unless the cache has been cleared or
refreshed. Features can also be requested by querying or populating the table directly. The API chooses the optimal way to
execute a query, either querying the local cache, or querying the service and importing the results into the local cache. For
example, if a spatial query is executed in the current map extent, results are obtained from the local cachethis avoids re-
fetching features from the service.
Manual cacheThis mode is recommended when the data from the service is not expected to change frequently and when it
is not critical for the client app to always have the most recent changes. The amount of data populated to the local cache from
the service is expected to be small. The table's local cache can only be populated by calling the populateFromService
method of ServiceFeatureTable. Features are never requested, and the cache is never populated based on map
interaction.
On interaction no cacheThis mode is recommended if it is critical for your app to always be working with the latest data. It
is expected that this mode will have a higher network usage. This mode is not recommended if you have an occasional or
unreliable connection to the service. When the table is used in a layer in a map, features are requested for the visible extent
and are not cached locally. Features are requested from the server each time you navigate the map, regardless of whether
the extent has been visited before. Queries are always executed against the server. Navigating the layer or querying the table
both cause the local cache to be cleared and repopulated.
Offline, sync-enabled
API classes: FeatureLayer (based on a GeodatabaseFeatureTable) A local cache of a feature service can be downloaded
and displayed as a layer in your app, without the need to remain connected to the service. Features are downloaded to a local
geodatabase file, using the GeodatabaseSyncTask.
Create and initialize a GeodatabaseFeatureTable, and create a FeatureLayer by passing in the GeodatabaseFeatureTable
to the constructor, then add the FeatureLayer to the map. Learn more about creating offline maps.

Offline
API classes: FeatureLayer (based on a GeodatabaseFeatureTable from a local geodatabase) Use a feature layer to display
data from a cache of features in a geodatabase (.geodatabase) that has been created in ArcGIS Desktop and provisioned directly
to the device.
Create and initialize a GeodatabaseFeatureTable using the local path to the geodatabase file, and create a FeatureLayer by
passing in the GeodatabaseFeatureTable to the constructor, then add the FeatureLayer to the map. Learn more about creating
offline maps.
For all feature layers, individual features can be queried and filtered based on spatial queries or text-based SQL WHERE clauses. If
the layer is created from an editable feature service and the service is configured to support editing, the feature layer can be edited,
and edits can be pushed to the service when required.
If the feature layer was created from a sync-enabled feature service, edits made to the features in an offline layer can be uploaded to
the service, and updates from the service can be synced to the client app.
Local caches cannot be reprojected automatically, so they should be used in a map that has the same spatial reference as the local
cache.
Find out more about editing feature layers.
As full feature information is cached locally in a geodatabase, and features are drawn natively, this layer type offers excellent display
performance of display when zooming and panning the map, within the extent of cached features. Querying such features is also
efficient, enabling app functions such as providing real-time updates of query results in a map.
The local geodatabase cache must be initially created, which requires server-side processing time, and the download to the device
may require extensive network usage and subsequent local device storage. Additionally, app memory increases with the number and
complexity of the features cached. Network usage can be eliminated by provisioning the cache directly to the device in advance (the
offline case), by creating the cache using a desktop computer and copying it to the device internal memory (or expandable memory
cards if your device supports this). This workflow may be suitable if the data is not changing too frequently
Feature collection layers

API classes: FeatureCollectionLayerA layer that manages the display of all tables in a feature collection. A feature collection
may contain one or more feature collection tables, which contain a set of features. Tables in the collection can have different schema,
geometry types, and rendering but are managed as a group, so things like visibility and draw order in the map are determined by the
feature collection layer.
A feature collection layer is used to display the features in a feature collection. A feature collection provides a way of grouping
logically-related feature collection tables. Redlining information (called "Map Notes" in ArcGIS Online), for example, may contain
points, lines, polygons, and associated text to describe things in the map. Because they have different schema and geometry types,
these features are stored in several distinct tables. As a feature collection, however, their visibility and draw order can be managed
with a single feature collection layer. Individual feature tables in the collection are rendered as feature layers (described previously).
A feature collection can be saved in the map or as a stand-alone portal item. In either case, the raw format of the data is JSON that
describes the schema and features contained in each table. If you need to share the feature collection between several maps, it's
best to store it as a separate portal item. Each map that uses the collection can add the collection from the portal item. If you need to
make frequent (near real-time) edits to features in the collection, consider storing these in a feature service instead, because the
collection is not refreshed until the map or portal item is reloaded. If features are used by a single map and/or are not subject to
frequent updates, it might be best to store them directly in the map. Edits made to features stored in a map will be saved when the
map is saved. Edits made to features stored in a portal item (and loaded into a map, for example) must be explicitly saved to the
original portal item to persist those changes.

Feature collection layers are designed to display a moderate amount of feature data (hundreds or perhaps thousands of features).
They are ideal for sharing static data (not subject to frequent updates, in other words) amongst several clients.
As full feature information is cached locally in a geodatabase and features are drawn natively, this layer type offers excellent display
performance when zooming and panning the map, within the extent of cached features.
The local geodatabase cache must be initially created by deserializing the JSON representation of features. Downloading features to
the device may require extensive network usage and local device storage space, but once the features are present in the client, the
app no longer needs to make requests for the data and will run faster. Additionally, app memory increases with the number and
complexity of the features in the collection.
Map Image layers

API classes: ArcGISMapImageLayerA dynamic (non-cached) map service can contain multiple layers, rendered by the server each
time a request is made, and returned to the client as a single raster image. The image does not contain any additional information about
the features in the map.
Map images are created and returned by the server on every request. Therefore, if your data has been changed those changes will
be seen as soon as a new map image is requested and returned. You can also control the visibility of sub-layers in this map image
layer and you can filter data by adding layer definition expressions. The spatial reference of this layer type can also be changed from
the service's default, and the service re-projects each image on-the-fly to the requested output spatial reference (that of the map).
The API does not include specific methods to query individual dynamic map service layers. However, the layer's end point URL can
be used to create a separate queryable feature layer.
For every map request, the map service creates a map image on-the-fly. Consequently, the server rendering time depends on the
amount and complexity of the data in the map. If the map service is well optimized, this should result in a relatively quick response to
the client, but will typically be longer than responses for an equivalent tiled map service layer. The file size of the returned map image
also depends on the data in the map. As the server response is an image, this can be drawn quickly as it requires little client-side
processing.
ArcGIS map image layers are good candidates for showing features that change periodically over time, or that require some sort of
filtering by the user, as long as the feature information (attributes, geometry, or symbol) is not required in the client. They are often
used in conjunction with a feature layer in selection mode to show the latest map data without having to pull all of the feature
information from the server (as with feature layers) on every map request.
Scene layers
API classes: ArcGISSceneLayerA layer to display 3D features from a scene service or locally available scene package. Scene
layers can be used to represent and visualize 3D objects, such as textured or untextured buildings, or 3D mesh data, such as imagery
captured by drones.
All of the layer types that are supported for 2D display can also be displayed in 3D. Using ArcGIS Pro, 3D content can also be delivered
as scene packages (stored on the client) or as online scene services. These data sources support consuming large volumes of
multipatch features, such as buildings for entire cityscapes. See the Display a scene topic for more information about working with
scenes and displaying data in 3D.

A scene service is used to provide one of the following types of 3D data:

3D Objects: 3D object scene layers are used to represent objects such as buildings, trees, and street furniture that are
explicitly modeled in three dimensions.
Integrated Mesh: 3D mesh data is typically captured by an automated process for constructing 3D objects out of large sets of
overlapping imagery. The result integrates the original input image information as a textured mesh including 3D objects, such
as buildings and trees, and elevation information. Integrated mesh scene layers are generally created for citywide 3D
mapping; they are often captured by drone and cannot be restyled.
Point Scene: To ensure fast visualization, cached scene layers are used to display large amounts of 3D point data, like all the
trees in a city, for example. Point scene layers are automatically thinned to improve performance and visibility at smaller
scales. Automatic thinning means that not all features are displayed at small scales; as you zoom in, additional features are
displayed. Point scene services are not supported for ArcGIS Runtime SDK at this release.
In a 3D map (scene), scale is not consistent across the display, as it is in a two-dimensional map. In other words, the same number of
pixels near the horizon, represents a much larger area than the same number of pixels in the foreground. For a scene layer, therefore,
the rendering of 3D data is based on the current level of detail (LOD), determined by the distance from the camera.
Each object in a 3D object service is represented differently at various levels of detail (LOD) determined by the camera distance. As
the camera distance changes in the scene, objects will be displayed appropriately for the current LOD. This ensures that performance
in the client is good and memory usage is low, although objects will frequently be loaded and unloaded according to the current LOD.
Raster layers
API classes: RasterLayerA layer to display image data from a raster data source, such as a raster file, mosaic dataset, image
service, or the result of a raster function. You can change how a raster layer is visualized by creating a raster renderer and applying it to
the layer. For more information about working with rasters, see Add raster data.
A raster consists of a matrix of cells (or pixels) organized into rows and columns (or a grid) where each cell contains a numeric value.
The values in a raster can represent discrete features, such as land use codes, or continuous phenomenon such as elevation. Rasters
are digital aerial photographs, imagery from satellites, digital pictures, or even scanned maps. For more information about working with
raster data in ArcGIS Runtime, see the Add raster data topic.
Raster data is often used to provide context for other information in the map (as a basemap, in other words). Aerial photography, for
example, can often give a more realistic or timely view of what's on the ground or illustrate changes in the terrain over time. Many
sources of analytical data are available in a raster format, such as those derived from satellite imagery. These data may be used for
feature identification, classification, change analysis, and so on.
Rasters are composed of one or more bands. A band is represented by a single matrix of cell values (like a layer of data within the
raster), and a raster with multiple bands contains spatially coincident matrices of cell values representing the same area on the
ground. An example of a single-band raster dataset is a digital elevation model (DEM), where each cell contains one value
representing the elevation at that location. A satellite image, on the other hand, commonly has multiple bands representing different
wavelengths of the electromagnetic spectrum. Landsat imagery, for example, contains seven bands that represent data from the
visible and infrared parts of the spectrum. Another example of a multiband image is a true color orthophoto in which there are bands
to represent red, green, and blue light.
Raster datasets can be quite large. The size of the dataset depends on: the geographic extent of the data, the size of the cells used,
the number of bands, and so on. As with any data consumed locally, file size can be an issue for storage as well as for transferring
datasets onto a device.
Non-spatial tables
Non-spatial tables can contain data from feature services or local geodatabases. In ArcGIS Runtime, they're represented by either
ServiceFeatureTable (for online) or GeodatabaseFeatureTable (for offline) instances.

The main difference between a spatial table and a non-spatial one is that a feature layer can be created from a spatial table and its
features can be displayed on a map. A non-spatial table does not have associated geometry, symbology or rendering information, and
therefore, its features cannot be drawn on a map. You can, however, still add a non-spatial table to a map, and it can be part of a maps
tables. You can iterate over a map's tables, add or remove them from the map, query or edit them.
Feature request modesThe default feature request modes for online non-spatial tables are the same as their spatial counterparts. For
details, see Feature request modes on this page.
LoadingNon-spatial tables, like their spatial counterparts, adopt the loadable protocol and are not loaded by default. Tables are loaded
internally when other asynchronous operations, such as query, are performed. Alternatively they can be loaded explicitly. Note: Loading a
table wouldn't fetch its data. Data is fetched as needed when querying or populating it. For more information on loadable resources, see
Loadable pattern for asynchronous resources.
Code examples for non-spatial tables follow.
Get non-spatial tables from an existing mapA map authored in ArcGIS Online or Portal for ArcGIS can contain tables in
addition to a basemap and operational layers. Tables can also be in maps authored using ArcGIS Desktop and they can be
packaged as mobile map packages for ArcGIS Runtime apps. When a map is opened in an ArcGIS Runtime app, the map's table
property contains an array of non-spatial tables.
Initialize a tableYou can create tables in code and add them to the list of map's tables. Instantiating a table would return an
unloaded table. You can set options like featureRequestMode before loading the table. A table created and loaded this way can
be used in its own rightqueried, edited, and so on, but it can also be added to a map.
Temporary graphics
Graphics are used to display temporary information that is not covered by the other types of layer above. They can be created based on
user actions, or results from an operation, or converted from the information in an external information feed. Each Graphic is defined in
memory in your app and is stored in the GraphicsOverlay of a MapView. Learn how to add graphics overlays to your app.

Features and graphics

In ArcGIS Runtime SDKs, features and graphics represent real-world objects on a map. Every feature and graphic has a geometry
representing its shape and location, as well as other attributes that further describe the represented object. For example, polygon features
could represent land parcels and include attributes about each one such as parcel ID or owner. Point graphics could represent event
locations, including the event's time and type. When displayed on a map, features and graphics may be rendered using a variety of
symbols.
Features and graphics are similar to one another in that they both have a geometry and attributes, this is represented by the geo-element
interface which they both implement. However, features are designed for different uses than graphics. Your choice between using a
graphic or a feature depends on various factors, such as whether they are persisted in a data store or a map, whether they all share a
single geometry type and set of attributes, or how your app displays them. This topic describes and compares features and graphics and
helps you choose which is best to use in various cases.
The following table compares important characteristics of features and graphics:
Comparison of features and graphics

Characteristic Feature Graphic
Display method In a feature layer in a map in a map view. In a graphics overlay in a map view.
Persistence In a feature table in a data store (such as a In app memory only.
database or service) or in a map.
Geometry type Features of different geometry types cannot exist Graphics of different geometry types can exist in the same graphic overlay.
(point, line, and in the same layer.
so on)
Attributes Features in the same data store or feature layer Each graphic may have a set of attributes unlike other graphics in the
have a common attribute schema. same graphic overlay.
Symbolization Symbolized according to the renderer defined for Symbolized individually or according to the graphics overlays renderer.
the feature service or the feature layer.
If persisted in a feature collection table in a map,
the renderer can be overridden with feature-
specific symbols.
Identifiable Via the map view. Via the map view.
Editable Created, updated and deleted using feature table Created through a graphic constructor and added to the graphics overlay
operations graphics collection. Attributes and geometry updated by reference on a
graphic instance
How features and graphics relate to a map

A map contains layers, among other things. Feature layers in a map are used to display features, feature layers are bound to a feature
table. Features are not displayed using a graphics overlay.
A map view contains a map and graphic overlays, among other things. Graphic overlays in a map view are used to display graphics on top
of the map and any layers the map contains. Graphics are not displayed using layers.
Where do features come from?

Features can be hosted in an online service, stored locally in a database, saved in a map or saved as a portal item. How you access
features in your app affects how you make and manage edits to them.
Feature services
A feature service provides online access to features and can be hosted by ArcGIS Enterprise or ArcGIS Online. A feature service
contains one or several collections of features. If you visit the REST Services Directory page for a feature service, you'll see the
collections of features it contains listed under the Layers heading, as shown in the following image. Features of different geometry types
(point, line, and polygon, in other words) cannot exist in the same collection, so it's common to see features organized according to
geometry type in addition to theme.

The feature service in the example contains several datasets, including three that describe C2 Military Operations using points, lines,
and areas (polygons). The number in parenthesis indicates the index position inside the feature service. To access a specific set of
features, append the index position to the URL for the service. Hostile Units, for example, can be accessed at
https://sampleserver6.arcgisonline.com/arcgis/rest/services/Military/FeatureServer/6.
Feature tables
Features in your ArcGIS Runtime app are stored in feature tables of which there are many types. Features that come directly from a
feature service are stored in a service feature table, which is created using the URL for the service and index position (see the URL
above). Features read from a local geodatabase are stored in a geodatabase feature table, for more information on how to create a
geodatabase see Create an offline layer. Static features stored in a map or portal item are stored in a feature collection table as part
of a feature collection.
Since a feature service or local geodatabase can contain several sets of features (tables, in other words), you may need to create many
feature tables in your ArcGIS Runtime app to represent all the datasets you need.
Types of features
Different feature table types return different feature objects. Feature tables that inherit directly from the FeatureTable base class return
the Feature object type. Feature tables which inherit from ArcGISFeatureTable have additional capabilities such as attachments, these
return ArcGISFeature objects.
For increased efficiency, the ArcGISFeature object implements the loadable pattern. When fetching features for rendering and query
purposes, a minimum set of required fields are returned, such as identifiers, geometry, fields used for symbolizing, and so on. When you
need all of the available fields you can simply load the feature.
Note: When querying features, you have the option to return your results as loaded features so all
fields are immediately available.
Feature layers
It's not necessary to display the features you work with in your app. If you want your user to view (and interact with) features on a map,
however, add the feature table that contains them as a feature layer. A feature layer can display features from any type of feature table.
See the layers and tables topic for more information about creating and working with feature layers.
Features in a feature layer can use different request modes, including caching of features, for efficient display on the client. You should
be aware of the various feature request modes, as the caching behavior of feature layers may affect the editing experience. Feature
request modes are described in detail in the layers and tables topic.

Caution: A feature layer can also display data from a map service or a geodatabase in a mobile map
package, in which case the data in the underlying feature table will be read-only.
Where do graphics come from?

Graphics are created by the developer and added to the application. They can be created from results from various operations such as
querying, identifying, geoprocessing, geocoding or routing. They can also be created from external data sources, but if you want to persist
the data in a map then you must use features. Graphics can also be created by the developer as a result of a map click or touch.
When to use features

Persistence is a built-in characteristic of features. Features are persisted in a data store such as a database, a service, a map or a portal
item. When this data store is available to multiple apps and users, a common set of data is available to all. Sharing data among users is a
common use case for features.
Compare this to graphics, which reside in the memory of a single running app session. Graphics are created by the app during the session
and are available only during that session.
You can publish features as part of a feature service. Layers in a feature service can be displayed in a map, symbolized in various ways,
and queried using attribute, spatial, or temporal criteria. The editing workflows and tools available in ArcGIS Runtime SDK also make it
possible to expose editing functionality in your app. You can even add code to control the type of edits made and who gets to make them.
When to use graphics

Apps create graphics as needed, and graphics do not need to be persisted. Therefore, graphics are ideal for displaying things that are
specific to the session, or anything that is displayed only temporarily. For example, the results of some tasks are returned as graphics,
which your app may display on a graphics overlay.
The following are some common uses for graphics:
Display text on top of a map
Highlight a section of the map by overlaying a polygon graphic
Display results from spatial analysis, such as buffer polygons created around features
Display a route between two locations
Display geometry drawn interactively by the app user
Animate data items that change quickly, such as moving objects
For more information about using graphics, see Add graphics and text to graphics overlays. For more information about using a graphics
overlay, see Add graphics overlays to your app.

Symbols and renderers

Symbols define all the non-geographic aspects of a graphic or feature's appearance, including color, size, border, and transparency. You
can apply a symbol directly to individual graphics when you create them. You can also use symbols to create a renderer for graphics
overlays or feature layers.
With a renderer, you can:
Use one symbol for all features in a layer (or all graphics in an overlay), regardless of attribute values
Symbolize features in a layer (or graphics in an overlay) differently based on one or more of their attribute values
The only way to set symbols on features is to use a renderer.
Symbols
Remember that a symbol is not the thing being represented on the map. Instead, it controls how those things (graphics or features)
display. The relationship is similar, for example, between the words you are reading now (the content) and the font that is used to display
them (presentation). Changing the font style, size, and color will not change the meaning of the text, but is likely to have an impact on the
effectiveness of the presentation. Likewise, the quality of a map's presentation can improve with the proper use of symbols to convey
information.
Each symbol type can be used to symbolize specific geometry type(s). Whether you're applying a symbol directly to a graphic or using a
symbol to create a renderer, ensure the geometry type of the graphic or feature being symbolized is compatible with the symbol you want
to use. The following is a table of the symbols available in the API with the compatible geometry types and a brief description:
Symbol/Class Geometry Description

SimpleMarkerSymbol point, multipoint Symbolizes points or multipoints with basic shapes.
PictureMarkerSymbol point, multipoint Symbolizes points or multipoints with images.
SimpleLineSymbol polyline Symbolizes polylines with pre-defined styles.
SimpleFillSymbol polygon, envelope Fills polygons or envelopes with a color and pre-defined styles.
TextSymbol point, multipoint, polyline, polygon Displays text.
Depending on the type of geometry you want to symbolize, you'll have different options available for defining your symbol. Points, lines,
and polygons all have a basic symbol you can use: SimpleMarkerSymbol, SimpleLineSymbol, and SimpleFillSymbol
respectively. You can also symbolize points using a PictureMarkerSymbol.
Some symbols provide the ability to set an angle for rotating the symbol. This might be useful for showing things like direction (for wind
measurements or moving vehicles, for example). You may also have the ability to define an x or y offset, meaning the symbol displays at a
specified distance from the location of the feature it represents. This can be especially useful when working with text.
The simple symbol types (SimpleMarkerSymbol, SimpleLineSymbol, and SimpleFillSymbol) give you the ability to quickly create
a symbol by choosing a style (for example solid or cross hatched fill for polygons; solid or dashed line for polylines; square or circle marker
for points), setting a color, and defining a size (for markers) or width (for lines). For markers and fills, you can also define an outline symbol
(using a line symbol).
Picture symbols
Picture symbols, such as PictureMarkerSymbol, allow you to use an image to symbolize a feature. The image may be stored locally,
or come from an online source. The size of the image can be specified in your platforms device independent units in the same way as
your other application resources.
Picture marker symbols can be created from an image on disk, such as a JPEG file, or from the URL to an image on a remote machine
accessible without security. Remote images are downloaded once per application and cached for future use; for this reason they are
loadable resources.

There are various ways to create picture marker symbols. For example:
You can create a picture marker symbol from an image on the file system:
//Create a picture marker symbol from a file on disk
BitmapDrawable pinBlankOrangeDrawable = (BitmapDrawable) Drawable.createFromPath(mPinBlankOrangeFilePath);
final PictureMarkerSymbol pinBlankOrangeSymbol = new PictureMarkerSymbol(pinBlankOrangeDrawable);
//Optionally set the size, if not set the image will be auto sized based on its size in pixels,
//its appearance would then differ across devices with different resolutions.
pinBlankOrangeSymbol.setHeight(20);
pinBlankOrangeSymbol.setWidth(20);
//Optionally set the offset, to align the base of the symbol aligns with the point geometry
pinBlankOrangeSymbol.setOffsetY(10); //The image used has not buffer and therefore the Y offset is height/2
pinBlankOrangeSymbol.loadAsync();
You can create a picture marker symbol from a URL:

//Create a picture marker symbol from a URL resource
//When using a URL, you need to call load to fetch the remote resource
final PictureMarkerSymbol campsiteSymbol = new PictureMarkerSymbol(
"http://sampleserver6.arcgisonline.com/arcgis/rest/services/Recreation/FeatureServer/0/images/e82f744ebb069bb35b234b3fea46deae");
campsiteSymbol.setHeight(18);
campsiteSymbol.setWidth(18);
campsiteSymbol.loadAsync();
You can create a picture marker symbol from an Android Drawable:

//Create a picture marker symbol from an app resource
BitmapDrawable pinStarBlueDrawable = (BitmapDrawable) ContextCompat.getDrawable(this, R.drawable.pin_star_blue);
final PictureMarkerSymbol pinStarBlueSymbol = new PictureMarkerSymbol(pinStarBlueDrawable);
pinStarBlueSymbol.setHeight(40);
pinStarBlueSymbol.setWidth(40);
//Optionally set the offset, to align the base of the symbol aligns with the point geometry
pinStarBlueSymbol.setOffsetY(
11); //The image used for the symbol has a transparent buffer around it, so the offset is not simply height/2
pinStarBlueSymbol.loadAsync();
Applying a symbol to a graphic

Graphics are in-memory features that provide a basic way to display geometry on the map. Graphics are unique in that they can be
symbolized using a renderer for the overlay that contains them (described later in this topic) or by applying a symbol directly to the
graphic. For a description of how to work with graphics, see Add graphics and text to graphics overlays.
The following example shows how to create a point graphic, apply a symbol, then display it on the map.
//create a simple marker symbol
SimpleMarkerSymbol symbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, Color.RED, 12); //size 12, style of circle
//add a new graphic with a new point geometry
Point graphicPoint = new Point(-226773, 6550477, SpatialReferences.getWebMercator());
Graphic graphic = new Graphic(graphicPoint, symbol);
graphicsOverlay.getGraphics().add(graphic);
Note: A symbol applied directly to the graphic overrides any symbols applied through the layer's
renderer.
Renderers
As the name implies, a renderer is an object that determines how features or graphics in a layer should be rendered (drawn) on the
display. The renderer then draws them using symbols. A renderer includes logic for applying the appropriate symbol to each feature in a
layer or each graphic in an overlay. There are a variety of renderer types, each designed to use a different rendering logic. Most renderers
use attribute values to determine which symbol should be applied.

In a typical workflow, renderers are used to symbolize features in a feature layer, where the features are all of same geometry type. It's up
to you to create a renderer with symbols that can be applied to the geometry type of the layer (as listed the table above). A renderer can
also be applied to a graphics overlay, but should not be used for an overlay that has graphics of mixed geometry types. For such a
scenario, applying a symbol to each graphic as it's created is the preferred workflow.
There are several types of renderers you can create using the Runtime API including simple renderers and unique value renderers. Each
is described below.
Simple renderer
A simple renderer uses one symbol for all features in a layer (or all graphics in an overlay) regardless of attribute values.
The following code snippet shows how to create a simple renderer for a graphics overlay containing only points using a simple marker
symbol:
//create a simple symbol for use in a simple renderer
SimpleMarkerSymbol symbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CROSS, Color.RED, 12); //size 12, style of cross
SimpleRenderer renderer = new SimpleRenderer(symbol);
//apply the renderer to the graphics overlay (so all graphics will use the same symbol from the renderer)
graphicOverlay.setRenderer(renderer);
Unique value renderer

A unique value renderer symbolizes features in a layer (or graphics in an overlay) differently based one or more of their attribute values.
It's particularly useful when symbolizing features based on an attribute whose values represent names or categories, usually referred to
as nominal data. Unlike graphics, features do not have a symbol property and therefore cannot be assigned an individual symbol.
However, you can use a unique value renderer to set symbology on a layer based on each feature's attribute values. (You can do this
for graphics, too.)
Note: ArcGIS map services allow up to three fields to be used for unique value renderers. An ArcGIS
feature service allows only one. As a developer you can specify as many fields as you like,
ensuring that the order of the fields you specify corresponds to the order of the values you
specify.
Caution: When applying a renderer that uses attribute values on a feature layer which is bound to a
service feature table, you must ensure the required fields are specified in the tables outfields.
When instantiating a service feature table in code, by default only the minimum set of fields
required to render the features are requested (object id, geometry and renderer fields). When
loading service feature tables from a map, by default all fields are requested. Be sure to
override these defaults by setting the outfields before the table is loaded.
For example the following code snippet creates a unique value renderer that assigns different color polygons to different states, and
also defines a default symbol.

// Create service feature table

ServiceFeatureTable serviceFeatureTable = new ServiceFeatureTable(getResources().getString(R.string.sample_service_url));
// Create the feature layer using the service feature table
FeatureLayer featureLayer = new FeatureLayer(serviceFeatureTable);
// Override the renderer of the feature layer with a new unique value renderer
UniqueValueRenderer uniqueValueRenderer = new UniqueValueRenderer();
// Set the field to use for the unique values
uniqueValueRenderer.getFieldNames().add("STATE_ABBR"); //You can add multiple fields to be used for the renderer in the form of a list, in this case we are only
// Create the symbols to be used in the renderer

SimpleFillSymbol defaultFillSymbol = new SimpleFillSymbol(SimpleFillSymbol.Style.NULL, Color.BLACK, new SimpleLineSymbol(SimpleLineSymbol.Style.SOLID, Color.GRAY
SimpleFillSymbol californiaFillSymbol = new SimpleFillSymbol(SimpleFillSymbol.Style.SOLID, Color.RED, new SimpleLineSymbol(SimpleLineSymbol.Style.SOLID, Color.RE
SimpleFillSymbol arizonaFillSymbol = new SimpleFillSymbol(SimpleFillSymbol.Style.SOLID, Color.GREEN, new SimpleLineSymbol(SimpleLineSymbol.Style.SOLID, Color.GRE
SimpleFillSymbol nevadaFillSymbol = new SimpleFillSymbol(SimpleFillSymbol.Style.SOLID,Color.BLUE, new SimpleLineSymbol(SimpleLineSymbol.Style.SOLID, Color.BLUE,
// Set default symbol

uniqueValueRenderer.setDefaultSymbol(defaultFillSymbol);
uniqueValueRenderer.setDefaultLabel("Other");
// Set value for california

List<Object> californiaValue = new ArrayList<>();
// You add values associated with fields set on the unique value renderer.
// If there are multiple values, they should be set in the same order as the fields are set
californiaValue.add("CA");
uniqueValueRenderer.getUniqueValues().add(new UniqueValueRenderer.UniqueValue("California", "State of California", californiaFillSymbol, californiaValue));
// Set value for arizona
List<Object> arizonaValue = new ArrayList<>();
arizonaValue.add("AZ");
uniqueValueRenderer.getUniqueValues().add(new UniqueValueRenderer.UniqueValue("Arizona", "State of Arizona", arizonaFillSymbol, arizonaValue));
// Set value for nevada

List<Object> nevadaValue = new ArrayList<>();
nevadaValue.add("NV");
uniqueValueRenderer.getUniqueValues().add(new UniqueValueRenderer.UniqueValue("Nevada", "State of Nevada", nevadaFillSymbol, nevadaValue));
// Set the renderer on the feature layer

featureLayer.setRenderer(uniqueValueRenderer);
Note: Features whose attribute value falls outside the classes defined for the renderer are
symbolized with the default symbol. If a default symbol is not defined, those features won't
display.

Tasks and jobs

Tasks are bound to online or offline data or services, and provide methods to perform asynchronous operations using those resources. By
using tasks you can:
Download, collect, and update geographic information using GeodatabaseSyncTask
Download and display tiled basemaps using ExportTileCacheTask
Locate addresses and find addresses from map locations using LocatorTask
Calculate point-to-point or multi-stop routes and get driving directions using RouteTask
Perform complex GIS analysis by executing geoprocessing models using GeoprocessingTask
Tasks either return their results directly from asynchronous methods on the task, or make use of jobs to provide status updates and
results.
Tasks
Some operations return their results directly from asynchronous methods on the task, for example LocatorTask.geocodeAsync and
RouteTask.solveRouteAsync. For more complex or longer running operations, tasks make use of jobs instead.
To use tasks that return results directly:
1. Create the task by initializing it to use the required data or service.
Some operations can work both online and offline.
2. Define the task inputs.
Some operations require only simple value inputs (for example a simple geocode operation may only require an address
string as input).
Others require parameters to be defined (for example, to limit a geocode operation to a specific country).
3. Call the async operation method, passing in the inputs you defined.
4. Use the results from the operation as required, for example to display geocode results on a map.
The code below creates a LocatorTask using the default Esri global locator, and passes in an address to geocode. When the operation
is complete, the result location is retrieved and displayed in a GraphicsOverlay.
// Call geocodeAsync passing in an address
final LocatorTask onlineLocator = new LocatorTask("http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer");
final ListenableFuture<List<GeocodeResult>> geocodeFuture = onlineLocator.geocodeAsync("380 New York Street, Redlands, CA");
geocodeFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
// Get the results of the async operation
List<GeocodeResult> geocodeResults = geocodeFuture.get();
if (geocodeResults.size() > 0) {
// Use the first result - for example display in an existing Graphics Overlay
GeocodeResult topResult = geocodeResults.get(0);
Graphic gecodedLocation = new Graphic(topResult.getDisplayLocation(), topResult.getAttributes(),
new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.SQUARE, Color.rgb(255, 0, 0), 20.0f));
mGraphicsOverlay.getGraphics().add(gecodedLocation);
}
}
catch (InterruptedException | ExecutionException e) {
dealWithException(e); // deal with exception appropriately...
}
}
});
Some Tasks are loadable, and will load themselves when you call an asynchronous method (like that shown above) that requires the task
to be in a loaded state. Loadable objects are generally required to be loaded before their properties are filled out.
Define input parameters

Tasks offer numerous options that allow you to tailor the operation to your requirements. For example, when geocoding you can restrict
your search to a specific area, country, category of place, and/or number of results. When an author publishes a service or packages a
resource, they can choose default values for these options that suit the specific data or the most common use case for the service.
To find these default parameter values, tasks provide async methods that create parameters objects, initialized with these service-
specific values. You can then make any changes to the parameter values, before using to execute an operation. Creating parameter
objects in this way can be especially useful for operations with many options, such as solving a route.
The code below gets the default parameters for a RouteTask, and then ensures that results using these parameters will return both a
route and directions, and also that the output spatial reference matches that of the MapView.

// use async method on RouteTask to get default parameters (task can be loaded or not loaded)
final ListenableFuture<RouteParameters> defaultParametersFuture = routeTask.createDefaultParametersAsync();
defaultParametersFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
// get the parameters from the future
RouteParameters routeParameters = defaultParametersFuture.get();
// update properties of route parameters
routeParameters.setReturnDirections(true);
routeParameters.setReturnRoutes(true);
if (routeParameters.getOutputSpatialReference() != mapView.getSpatialReference()) {
routeParameters.setOutputSpatialReference(mapView.getSpatialReference());
}
// Use the updated parameters to solve a route...
}
}
}
});
Alternatively, some parameters objects have constructors that you can use if you know the values of all the input parameters you want
to use. This can be more efficient where parameter settings are simple.
For example, the code below creates geocoding parameters that restrict the country within which to geocode, and to limit the maximum
returned results.
GeocodeParameters geocodeParams = new GeocodeParameters();
geocodeParams.setCountryCode("France");
geocodeParams.setMaxResults(5);
Work online or offline

Many tasks can work either online by using services, or offline by using local data and resources. For example, you can geocode an
address by using the default Esri geocoding service, your own geocoding service, a locator file (.loc) or a mobile map package
(.mmpk).
// create an online locator from a geocoding service - here we use esri's default global locator...
// create an offline locator from a local .loc file - coverage will depend on the packaged locator dataset...
final LocatorTask offlineLocator = new LocatorTask(localLocatorPath + ".loc");
// mobile map packages can also contain locators - use this to get a reference to an offline locator...
final MobileMapPackage mmpk = new MobileMapPackage(localMmpkPath + ".mmpk");
mmpk.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
if (mmpk.getLoadStatus() == LoadStatus.LOADED) {
LocatorTask mmpkLocator = mmpk.getLocatorTask();
// use locator from a mobile map package according to the packaged locator coverage...
}
}
});
mmpk.loadAsync();
Tasks and jobs

Some tasks expose operations that have multiple stages (like preparing and downloading a geodatabase), and can generate multiple
progress messages (such as percentage complete). These types of tasks are always bound to ArcGIS Server or Local Server. An
example is generateGeodatabaseAsync on GeodatabaseSyncTask.
Instead of returning results directly, these tasks make use of jobs to monitor status, return progress updates, and return their results. Each
Job represents a specific operation of a task. Jobs are useful for longer-running operations, because they can also be paused, resumed,
and cancelled. Your app can support a user action or host OS terminating a running job object, and then re-create and resume the job
later.
To use operations like these:
1. Create the task by initializing it to use the required data or service.
2. Define the input parameters for the task.
3. Call the async operation method to get a job, passing in the input parameters you defined.
4. Start the job.
5. Optionally, listen for changes to the job status and check the job messages, for example to update a UI and report progress to the
user.
6. Listen for the job completion and get the results from the operation. Check for errors in the job, and if successful, use the results.

// Create the export tile cache

ExportTileCacheTask exportTilesTask = new ExportTileCacheTask("http://sampleserver6.arcgisonline.com/arcgis/rest/services/World_Street_Map/MapServer");
// Define the parameters for the new tile cache - in this case, using the parameter object constructor
ExportTileCacheParameters exportTilesParameters = new ExportTileCacheParameters();
exportTilesParameters.getLevelIDs().addAll(Arrays.asList(0, 1, 2, 3, 4, 5, 6, 7, 8, 9));
exportTilesParameters.setAreaOfInterest(
new Envelope(-1652366.0, 2939253.0, 2537014.0, 8897484.0, SpatialReferences.getWebMercator()));
// Create the export task, passing in parameters, and file path ending in ".tpk"
final ExportTileCacheJob exportJob = exportTilesTask.exportTileCacheAsync(exportTilesParameters, exportedTpkPath);
// Listen for job status updates, and report the most recent message to the user...
exportJob.addJobChangedListener(new Runnable() {
@Override
public void run() {
List<Job.Message> messages = exportJob.getMessages();
updateUiWithProgress(messages.get(messages.size() - 1).getMessage());
}
});
// Listen for when the job is completed

exportJob.addJobDoneListener(new Runnable() {
@Override
public void run() {
// Check if there was an error
if (exportJob.getError() != null) {
dealWithException(exportJob.getError()); // deal with exception appropriately...
return;
}
if (exportJob.getStatus() == Job.Status.SUCCEEDED) {
// Get the TileCache resulting from the successfull export job, and use it by adding a layer to a MapView
final TileCache exportedTileCache = exportJob.getResult();
ArcGISTiledLayer tiledLayer = new ArcGISTiledLayer(exportedTileCache);
mapView.getMap().getOperationalLayers().add(tiledLayer);
}
}
});
// Start the ExportTileCacheJob
exportJob.start();
Calling Job.getStatus retrieves the current point in the job's workflow. Started jobs periodically receive job changed events; this
happens with decreasingly frequency as a job progresses; more than one JobMessage may have been added to the job for each call.
The job done listener is called as soon as the job is complete, for both successes and failures. Completed jobs, whether they have
succeeded or failed, cannot be restarted.
Report job progress

A job represents an asynchronously running operation that might take some time to finish. As described previously, you can monitor
changes to job status for notification when a job has completed, failed, or been cancelled, but what about the time in-between? Users
may become frustrated waiting for a long job to complete without getting feedback on it's progress. Fortunately, jobs provide a
mechanism for reporting the current progress (percentage complete) for the running operation they represent.
As the job runs it . You can get the current progress of the job from the job's Progress property, an integer representing the percentage
of the operation that has been completed. This allows your app to provide more specific information about the status of a running job
using UI elements like progress bars, for example.
Pause, resume, or cancel or job

Jobs are designed to effectively handle a user exiting an app while the job is running, and to handle the app being terminated by the host
operating system. Jobs also deal with explicit pausing and cancellation of the operation.
Cancel a job
Sometimes the results of a job are no longer required. For example, a user could change their mind about the area of a tile cache they
want to download and want to cancel the job and start over.
Calling Job.cancel on a job immediately changes its status to Job.Status.FAILED and adds additional information to the job error
object. The job completion listener will be called. The error object indicates the error domain and code, which allows you to identify
when cancellation has occurred.
The code below shows, for a running ExportTileCacheJob, adding a JobDoneListener. Within the listener the code checks for
the appropriate error code and domain that indicates that the job has been cancelled. At this point, the code checks in case the tile
cache file was already created, and if so, deletes it.

// For a job that is running, listen for when the job is completed
runningJob.addJobDoneListener(new Runnable() {
@Override
public void run() {
// Check if there was an error
ArcGISRuntimeException jobError = runningJob.getError();
if (jobError != null) {
// Failure status can indicate cancellation, or other types of failure
if (runningJob.getStatus() == Job.Status.FAILED) {
// Check the error information to confirm if this was a user cancellation

if ((jobError.getErrorCode() == 18) &&
(jobError.getErrorDomain() == ArcGISRuntimeException.ErrorDomain.ARCGIS_RUNTIME)) {
// UI can be updated to indicate cancellation

updateUiWithProgress("Export has been cancelled");
// Could check if tile cache was downloaded before the task was cancelled, and clean up the file...
File tileCacheFile = new File(exportedTpkPath);
if (tileCacheFile.exists()) {
tileCacheFile.delete();
}
return;
}
}
dealWithException(jobError); // Deal with other types of failure...

return;
}
dealWithJobDoneSuccess(); // Deal with a successful job

}
});
Cancelled jobs cannot be restarted, although you can start a new job by re-using the same parameters. Cancelling a job does not
necessarily stop any server-side processes, because not all services support cancellation on the server side.
Pause and resume a job

Jobs can be long running operations, so there is no guarantee that they will be completed while the app is running. You can pause a job
explicitly using Job.pause. For example when an app is backgrounded and does not have permissions for background operation.
Pausing may also be useful if a user wishes to temporarily stop network access for any reason.
Job changed messages will not be received for a paused job. Pausing a job does not stop any server-side processes from executing.
While a job is paused, outstanding requests can complete, and therefore it's possible that a resuming a job will result in it having a
different state to when it was paused.
You can serialize a job to JSON to persist it if your app is backgrounded, or the process is otherwise terminated. When you deserialize it
again, the job will be in the Job.Status.PAUSED state regardless of its state when serialized, and should be restarted to resume
listening for completion. The job changed listener can be a good place to update the job JSON for storage by your app.
The code below shows, for an existing running Job, serializing the job to JSON.
mRunningJob.addJobChangedListener(new Runnable() {
@Override
public void run() {
// Every time the job changes, update the stored JSON that represents the Job.
mJobJson = mRunningJob.toJson();
}
});
This JSON can then be saved when appropriate, for example by overriding the onSaveInstanceState in an Activity and saving
the JSON String to the Bundle parameter. The JSON can be similarly retrieved when appropriate, for example in the
onRestoreInstanceState or onCreate method of the Activity, depending on if the job should be considered persistent or
temporary data.
static final String JOB_STATE = "jobState";
@Override
protected void onSaveInstanceState(Bundle outState) {
// Save the current Job JSON
outState.putString(JOB_STATE, mJobJson);
// Always call the superclass so it can save the view hierarchy state
super.onSaveInstanceState(outState);
}
@Override
protected void onRestoreInstanceState(Bundle savedInstanceState) {
// Always call the superclass so it can restore the view hierarchy
super.onRestoreInstanceState(savedInstanceState);
// Restore state members from saved instance
mJobJson = savedInstanceState.getString(JOB_STATE);
// Can immediately deserialize the available JSON to restart the Job

deserializeFromJson();
}

The Job can then be deserialized back from stored JSON, and restarted. Remember to set the job changed and done listeners again to
be informed when the job changes, and when it is complete and the result can be retrieved.
private void deserializeFromJson() {
if ( (mJobJson != null) && (!mJobJson.isEmpty())) {
mRunningJob = Job.fromJson(mJobJson);
if (mRunningJob != null) {
// Deserialized jobs have Job.Status.PAUSED, so restart the job.
mRunningJob.start();
// Resume listening for status changes and job completion.

mRunningJob.addJobChangedListener(new Runnable() {
@Override
public void run() {
dealWithJobChanged(); // See examples above
}
});
mRunningJob.addJobDoneListener(new Runnable() {
@Override
public void run() {
dealWithJobDone(); // See examples above
}
});
}
}
}
Loss of network connection

Additionally, jobs using services are designed to handle situations where network connectivity is temporarily lost without needing to be
immediately paused. A started job will ignore errors such as network errors for a period of up to 10 minutes. If errors continue for longer,
the job will fail and the message will indicate the loss of network connection.
To deal with partially-connected workflows, you can serialize and pause a job when your app detects that network connectivity has been
lost for a few minutes to avoid job failure purely due to this lack of network connectivity (as failed jobs cannot be restarted). The job can
then be deserialized and resumed when connectivity is reinstated.
From Android 6.0, the power-saving features Doze and App Standby can also affect the network connectivity of an application. Again,
you may wish to pause a running job if your app enters these states to avoid job failure due to the lack of persistent network connection.
Your app can check the Android PowerManager.isDeviceIdleMode and PowerManager.isPowerSaveMode methods, or use
broadcast intents to react when entering or exiting these modes.

Geometries
Geometries represent real-world objects by defining a shape at a specific geographic location. They are used throughout the API to
represent the shapes of features and graphics, layer extents, viewpoints, and GPS locations. They are also used as inputs and outputs of
spatial analysis and geoprocessing operations, and to measure distances and areas, among other uses.
The Geometry class provides functionality common to all types of geometry. Point, Multipoint, Polyline, Polygon, and Envelope
all inherit from Geometry, and represent different types of shapes.
The following are common geometry characteristics:

Geometries have a spatial reference indicating the coordinate system used by its coordinates.
Geometries can be empty, indicating that they have no specific location or shape.
Geometries can have z-values and/or m-values.
Geometries can be converted to and from JSON to be persisted or to be exchanged directly with REST services.
Geometries are immutable

Most geometries are created and not changed for their lifetime. Examples include features created to be stored in a geodatabase or read
from a non-editable layer, and features returned from tasks such as a spatial query, geocode operation, network trace, or geoprocessing
task. Immutable geometries (geometries that cannot be changed) offer some important benefits to your app. They are inherently thread-
safe, they help prevent inadvertent changes, and they allow for certain performance optimizations.
While immutable geometries appear to present problems for editing existing geometries, those problems are solved by using geometry
builders. Geometry builders are designed to represent the state of a geometry under construction while allowing modifications, thus
enabling editing workflows.
Envelope
Envelope geometries represent rectangular shapes with sides that are parallel with the x or y axis of the coordinate system. Most
commonly, they represent the spatial extent of layers or other geometries, or define areas of interest for tasks. They can be used as the
geometry of graphics and in many geometry operations, although they cannot be used as the geometry of features.
New instances of Envelope are defined by specifying a minimum and maximum x-coordinate and minimum and maximum y-coordinate,
and a SpatialReference. Optionally, a minimum and maximum z-value can be specified to define the depth of the envelope.
// create an Envelope using minimum and maximum x,y coordinates and a SpatialReference
Envelope envelope = new Envelope(-123.0, 33.5, -101.0, 48.0, SpatialReferences.getWgs84());
Another way to define an envelope is by using two points. The minimum and maximum x,y coordinates are calculated from the two points.
// minimum and maximum x and y will be calculated from points passed
Envelope envelopePoints = new Envelope(pointOne, pointTwo);
Point
Point geometries represent a single point, place, or location such as a geocoded house address in a neighborhood or the location of a
water meter in a water utility network. Larger geographic entities such as cities can be represented as points on small-scale maps. Points
can be used as the geometry of features and graphics and are often used to help construct other geometries. They are also used in
Viewpoints.
Points store a single set of x,y coordinates that represent the coordinates of a location (longitude and latitude for example), and a
SpatialReference. Optionally, a z-value (representing things such as elevation for example) can also be included. Instances of Point
can be created using constructors, which define the full geometry in a single call.
// create a Point using x,y coordinates and a SpatialReference
Point pt = new Point(34.056295, -117.195800, SpatialReferences.getWgs84());

// create a Point with a z-value as well

Point ptWgs84 = new Point(34.056295, -117.195800, 414, SpatialReferences.getWgs84());
Log.i(TAG, String.format("Point hasZs: %B", ptWgs84.hasZ())); // hasZ=TRUE
Caution: Remember when working with Point instances that have a geographic spatial reference, the x-
coordinate is the longitude (east or west), and the y-coordinate is the latitude (north or south).
When geographic coordinates are represented in strings, they are generally written using the form
"(latitude, longitude)", where the y-coordinate comes before the x-coordinate. Latitude values south
of the equator and longitude values west of the prime meridian are expressed as negative
numbers.
You can use CoordinateFormatter to convert a latitude, longitude formatted string directly to a
Point, and also return a latitude, longitude formatted string from an existing Point. Other
coordinate notations, such as Military Grid Reference System (MGRS) and United States National
Grid (USNG) are also supported.
Multipoint
Multipoint geometries represent an ordered collection of points. They can be used as the geometry of features and graphics, or as
input or output of geometry operations. For features that consist of a very large number of points that share the same set of attribute
values, multipoints may be more efficient to store and analyze in a geodatabase compared to using multiple point features. LIDAR is an
example of data that may use multipoints.
Multipoints are composed of a single read-only collection of Points. You can create a new Multipoint by calling a constructor and
passing in an iterable set of Points.
// create a Multipoint from a PointCollection
PointCollection stateCapitalsPST = new PointCollection(SpatialReferences.getWgs84());
stateCapitalsPST.add(-121.491014, 38.579065); // Sacramento, CA
stateCapitalsPST.add(-122.891366, 47.039231); // Olympia, WA
stateCapitalsPST.add(-123.043814, 44.93326); // Salem, OR
stateCapitalsPST.add(-119.766999, 39.164885); // Carson City, NV
Multipoint multipoint = new Multipoint(stateCapitalsPST);
To access each Point in an existing Multipoint, iterate over the ImmutablePointCollection returned from getPoints.
// iterate the Points in the ImmutablePointCollection from a Multipoint
for (Point pt : multipoint.getPoints()) {
Log.i(TAG, String.format("Point x=%f,y=%f, z=%f", pt.getX(), pt.getY(), pt.getZ()));
}
Use the MultipointBuilder to build a multipoint one point at a time or to modify an existing multipoint.
Polyline
Polyline geometries represent the shape and location of linear features, for example, a street in a road network or a pipeline in an oil
refinery. They can be used as the geometry of features and graphics, or as input or output of tasks or geoprocessing operations, such as
the output of a network trace.
Polylines are composed of a series of connected segments, where each segment defines a continuous line between a start and an end
point. You can also work with polylines by using point-based helper methods.
For example, use a constructor to create a new Polyline from a PointCollection. This creates a series of straight LineSegments
connecting the points you specified.
// create a Polyline from a PointCollection
PointCollection borderCAtoNV = new PointCollection(SpatialReferences.getWgs84());
borderCAtoNV.add(-119.992, 41.989);
Polyline polyline = new Polyline(borderCAtoNV);
Polylines can have multiple parts. Each part is a series of connected segments, but the parts can be disjoint from each other, for example,
in a polyline representing a discontinuous highway that has an unfinished section. Parts can also intersect at one or more vertices, for
example, in a polyline representing a river and its tributaries. The Polyline class inherits from Multipart, which provides members for
iterating through the segments and points of each part in a Polyline.
To build a polyline one point at a time, or to modify an existing polyline, use PolylineBuilder.

Polygon
Polygon geometries represent the shape and location of areas, for example, a country or a lake. They can be used as the geometry of
features and graphics, or as input or output of tasks or geoprocessing operations, such as the output of a drive-time analysis or a buffer
operation.
Polygons are similar to polylines in that they are also composed of a series of connected segments. However, polygons define closed
areas, so the end point of the last segment is always in the same location as the start point of the first segment, forming a closed
boundary. As with polylines, you can work with the vertices of the segments of a polygon by using point-based helper methods.
For example, use a constructor to create a new Polygon from an existing PointCollection, creating a series of LineSegments
connecting the points.
// create a Polygon from a PointCollection
PointCollection coloradoCorners = new PointCollection(SpatialReferences.getWgs84());
coloradoCorners.add(-109.048, 40.998);
Polygon polygon = new Polygon(coloradoCorners);
Tip: When defining a polygon, there is no need to explicitly close it by repeating the start point as
the last point. Polygons are always drawn as enclosed areas by ArcGIS Runtime. However,
you may need to simplify a geometry to store it in a geodatabase.
To build a polygon one point at a time, or modify an existing polygon, use a
PolygonBuilder.
Similar to polylines, polygons can have multiple parts but have different rules than those for multipart polylines. Each part of a multipart
polygon is a series of connected segments forming a closed ring. Each part must not cross any other part but may lie completely inside or
outside another part. For example, a polygon representing the state of Hawaii would comprise eight disjoint parts, one representing each
island. A polygon representing the country of South Africa, which completely surrounds the enclave of Lesotho, would comprise two parts,
one contained inside the other. The Polygon class also inherits from Multipart.
Multipart (Polygon and Polyline)

Polygon and Polyline inherit from Multipart, which in turn inherits from Geometry. Multipart provides access to the geometry's
ImmutablePartCollection. Each ImmutablePart in the collection is a collection of Segment objects. You can iterate through the
segments or points in each part.
// iterate each Part of a Polyline
ImmutablePartCollection parts = polyline.getParts();
for (ImmutablePart part : parts)
{
// iterate the collection of Points representing vertices of the ImmutablePart
for (Point pt : part.getPoints())
{
Log.i(TAG, String.format("Point: x=%f,y=%f, z=%f", pt.getX(), pt.getY(), pt.getZ()));
}
// iterate each Segment - ImmutablePart is a collection of segments
for (Segment seg : part) {
Log.i(TAG, String.format("Segment: (%f, %f) to (%f %f)",
seg.getStartPoint().getX(), seg.getStartPoint().getY(),
seg.getEndPoint().getX(), seg.getEndPoint().getY()));
}
}
A point-based convenience method is available to iterate through the Points that represent the vertices of all the parts, in a single step.
// get the combined set of Points from every ImmutablePart of a Polyline
for (Point pt : polyline.getParts().getPartsAsPoints())
{
Log.i(TAG, String.format("Point: x=%f,y=%f, z=%f",
pt.getX(), pt.getY(), pt.getZ()));
}
In the same way as Polygons and Polylines are immutable, the collections returned from Multipart are also
immutableImmutablePartCollection, ImmutablePart, and ImmutablePointCollection. However, when creating polygons
and polylines, you use the mutable equivalentsPartCollection, Part, and PointCollection. Point-based helper methods are
available on both the mutable and immutable classes.
Segments
A segment describes a continuous line between a start location and an end location. Every part in a multipart geometry is a collection of
Segments where the end of one segment is at exactly the same location as the start of the following segment. The ArcGIS system
supports both straight and curved segments, but at the current release, only straight LineSegments are supported in ArcGIS Runtime

SDK. Multipart geometries can be composed from and decomposed into segments if required; until true curves are supported fully,
using point-based methods offers equal functionality.
Because a single location is shared by adjacent segments, a single Point object is used to represent the shared location when you
iterate through the points in a part. As a result, when iterating through the points in a part of a polyline, there will be one more Point
than the number of Segments in that same part.
// iterate each Part of a Polyline
for (ImmutablePart part : polyline.getParts())
{
// find the number of Points representing vertices of the ImmutablePart
Log.i(TAG, String.format("Number of Points: %d", part.getPointCount()));
// find the number of Segments - ImmutablePart is a collection of segments
Log.i(TAG, String.format("Number of Segments: %d", part.size()));
Similar to the geometries they comprise, Segments are immutable.
Other aspects of geometries

Spatial references
The meaning of the coordinates in a geometry is determined by the geometry's spatial reference. The vertices and spatial reference
together allow your app to translate a real-world object from its location on the Earth to its location on your map.
In some cases, a geometry's spatial reference may not be set. Graphics that do not have a spatial reference are drawn using the same
spatial reference as the MapView in which they are drawn. When using a geometry builder to create a polyline or polygon geometry
from point geometries, you don't need to set the spatial reference of every point before you add it to the builder, as it will be assigned
the spatial reference of the builder it's added to. In most other cases, such as when using a geometry in geometry operations or when
editing a feature table, the geometry's spatial reference must be set.
Learn more about spatial references
Projection, topological, and other operations

Changing the coordinates of a geometry to have the same shape and location represented using a different spatial reference is known
as "projection" or sometimes as "reprojection". Because geometries are immutable, they do not have any member methods that project,
transform, or otherwise modify their content.
The GeometryEngine class provides a wide range of methods that read the content of geometries and modify that content to create
new geometries. There are methods to project, rotate, move, cut, densify, and generalize geometries. When creating geometries using
locations from the screen, and the map is a wraparound map, you may also need to consider normalizing a geometry before you save it
to a geodatabase or use it in tasks or other operations.
Converting to and from JSON

Geometries can be serialized and de-serialized to and from JSON. The ArcGIS REST API documentation describes the JSON
representation of geometry objects. You can use this encoding and decoding mechanism to exchange geometries with REST Web
services or to store them in text files.
// convert a Polygon to a JSON representation
String polygonJson = polygon.toJson();
// create a new Polygon from JSON
Polygon polygonFromJson = (Polygon) Polygon.fromJson(polygonJson);
Converting to or from JSON can add points to multipart geometries if the geometry has insufficient points to construct a segment.
Z-values and 3D
Geometries can have z-values, indicating values along the z-axis, which is orthogonal to both the x-axis and y-axis. Z-values can
indicate height above or depth below a surface, or an absolute elevation. For example, z-values are used to draw the locations of
geometries in SceneViews. Note that geometries are not considered true 3D shapes and are draped onto surfaces in the view, or in
some cases, drawn in a single plane by using z-values. Z-values are stored on Points and Envelopes. Therefore, because
Multipoints, Polylines, and Polygons are created from Points, all types of geometry can have z-values.
Whether or not a geometry has z-values is determined when the geometry is created; if you use a method that has a z-value parameter,
the new geometry will have z-values (the geometry's hasZ will be true). If you create geometries using constructors that take z-value

parameters, or if you pass into the constructor points or segments that have z-values, the new geometry will have z-values. A geometry
with z-values is sometimes known as a z-aware geometry.
It may be that not all vertices in your geometry have a z-value defined. NaN is a valid z-value used to indicate an unknown z-value.
However, the default z-value is zero. It is important to note that when you get z-values from a geometry that does not have z-values, the
default value of zero is returned. Check the hasZ property to determine whether a z-value of zero means that there are no z-values in
the geometry or that the z-value in the geometry's coordinates really is zero.
See Editing geometries for more information about editing workflows with respect to z-values.
M-values
M-values are used in linear referencing scenarios, and like z-values, every geometry can optionally store m-values. The default m-value
is NaN. If an m-value is specified as a parameter when a geometry is created, the new geometry will have m-values (the geometry's
hasM will be true). Note that when you get m-values back from a geometry, the default value of NaN (different than the default for z-
values) is returned for vertices that do not have m-values. A geometry with m-values is sometimes known as an m-aware geometry. See
Editing geometries for more information about editing workflows and m-values.

Spatial references
Spatial references are important, and for someone new to GIS, they can appear complicated. Spatial references ensure that spatial data
for different layers or sources can be integrated for accurate viewing or analysis. When you combine layers with different spatial
references for viewing or analysis, ArcGIS Runtime SDKs attempt to handle this disparity for you by setting defaults and requesting data in
the appropriate spatial reference from services where possible. But sometimes, you'll need to know about spatial references to get things
working. Whether it's to align data together, make your map look right, improve accuracy, or just make a layer show up, understanding the
basics of spatial references can be critical.
Spatial references can be referred to by a well-known ID (WKID). Some common WKIDs are mentioned in the text below; for a more
complete description, see Spatial reference specifications in this topic.
Why spatial references are important

To integrate spatial data together into a map or during analysis, ArcGIS Runtime must know where things are located on the Earth's
surface. To do this it uses coordinates. Coordinates are associated with a coordinate system, which is a frame of reference around a
model of the Earth's surface. Not all coordinates and their associated coordinate systems are the same; they can be in different units
(degrees minutes seconds, decimal degrees, or meters) or they can be based on different types of models. To move coordinates from one
coordinate system to another, mathematical transformations are used. A spatial reference provides all of this information, along with
parameters such as the desired level of precision, in a way so that spatial data can be viewed and analyzed together.
Coordinate systems and projections

The models used for coordinate systems are split into two main categories, geographic and projected:
Geographic coordinate systems (GCSs) use a three-dimensional spherical (or ellipsoidal) surface to define locations. The
coordinates are based on angles from the center of the earth to the surface. Typically GCSs use latitude and longitude specified in
degrees. The coordinates derived from a GPS device are returned in a GCS named WGS84 (WKID=4326).
Projected coordinate systems (PCSs) are planar (two-dimensional), Cartesian, or "flat." Unlike a GCS, a projected coordinate
system has constant lengths, angles, and areas across the two dimensions. PCSs use a geographic coordinate system projected
onto a flat surface for use in a printed map or on a screen. There are different projections with different desirable characteristics,
such as preserving accuracy in particular areas of the Earth, maintaining the shape of features, or favoring accurate area or
distance measurements. Coordinates are identified by x,y coordinates on a grid. ArcGIS Online, Google, and OpenStreetMap
basemaps use the same projected coordinate system named Web Mercator Auxiliary Sphere (WKID=3857).
You may come across a third coordinate system, a local coordinate system, which is often unrelated to any other coordinate system. The
origin and the x,y coordinate units correspond to a local point of reference. Because the relationship of a local coordinate system to
another coordinate system cannot be established easily, these are sometimes referred to as unknown coordinate systems.
When you need to know about spatial references

Add layers to the map
When ArcGIS Runtime renders a map, it needs to draw all the data in the same spatial reference so that the data lines up. When you
create a map, the spatial reference of the first layer you add is used as the spatial reference of the entire map; this is typically the
basemap.
When you add additional layers to your map, you may need to request them in the same spatial reference your map is using. Whether
or not you must request this depends on what type of layer youre adding. The following sections describe layer types as they relate to
setting your maps spatial reference.
Graphics overlays
Graphics overlays support on-the-fly reprojection of graphics. On-the-fly reprojection requires extra processing that could slow down
the map view rendering time. When you add a graphic to a graphics overlay, it is best if the geometry in the graphic has the same
spatial reference as the map. You can explicitly convert geometries to the required spatial reference.
Feature layers from feature services
When using a feature service table created from a feature service from ArcGIS Online or ArcGIS Enterprise, the service supports
reprojection. When initialized, the table and its associated feature layer will automatically be set to the same spatial reference as the
map. This ensures the data is requested from the service in the correct coordinates, without the need to explicitly define the spatial
reference for the feature table. ArcGIS Runtime determines the correct spatial reference and requests data from the feature service
accordingly.

Feature layers from geodatabase feature tables
Your tables in the geodatabase must be in the same spatial references as the map you are adding them to, because on-the-fly
reprojection of data from these tables is not supported. If you're using the desktop workflow, ensure the ArcMap map frame is using
the desired spatial reference before you run the create runtime content tool. If you're using the services workflow, set the desired
spatial reference in the parameters used to generate the geodatabase.
Dynamic map service layers
If these are ArcGIS Online or ArcGIS Enterprise map services, then the server supports reprojection on the fly. When you add an
ArcGIS dynamic map service layer to the map, ArcGIS Runtime automatically asks for the map image in the correct spatial reference
for you (based on the map's spatial reference).
Tiled layers
Tiled layers are cached layers. At the time of caching, a spatial reference is used and is therefore predefined for the tiled layer. It's
typically not possible to request tiled layers in a different spatial reference from the one defined in the service using that cache (unless
the server supports doing this on the fly; most do not). If an ArcGIS tiled layer is added to a map with a different spatial reference from
the tiled layer, it cannot be drawn.
Raster layers
Raster layers support on-the-fly datum transformation and reprojection. For more information on using raster layers in your app, see
Add raster data.
Edit data
When creating new features from coordinates, the coordinate values must match the spatial reference for the layer; otherwise, the
features will not show up in the correct location on the map.
Perform analysis
Geometry objects used for analysis (for example, determining spatial relationships, such as where polygons intersect) require that the
spatial reference be known before the analysis is performed. Otherwise, results may not be accurate. Likewise, it's meaningless to
compare two geometries or determine their spatial relationship if they have different spatial references. To display a geometry in a map
layer, the geometry must have either the same spatial reference as the layer or be projected to the layer's spatial reference. To use two
geometries together, they should have the same spatial reference.
Convert geometries from one spatial reference to another

When using the geometry engine to convert geometries from one spatial reference to another, the in and out spatial references must be
specified. An appropriate datum transformation is used by default. You can also convert strings containing coordinates formatted as
latitude and longitude directly to points, and vice-versa. Other types of coordinates such as Universal Transverse Mercator (UTM) and
United States National Grid (USNG) are also supported.
Spatial reference specifications

To define a spatial reference, you can use either a WKID (sometimes also known as spatial reference ID or SRID) or a full-text definition
referred to as well-known text (WKT). WKIDs are defined by standards bodies or organizations. ArcGIS supports a variety of WKIDs,
typically those defined by the European Petroleum Survey Group (EPSG) or Esri, as well as a few other commonly used IDs. WKTs are
full-text definitions of all of the parameters that specify a spatial reference (as mentioned above). To see a list of supported WKIDs and
their WKT definitions, see the following:
Geographic coordinate systems
Projected coordinate systems
Related topics
Projected coordinate systemsPart 1

Loadable pattern for asynchronous resources

Resources such as layers, maps, portal items, tasks, and so on, commonly rely on remote services or datasets on disk to initialize their
state. The nature of accessing such data requires the resources to initialize their state asynchronously. The loadable design pattern unifies
the behavior that different resources use to load metadata asynchronously, and resources that adopt this pattern are referred to as
"loadable." The pattern also provides a mechanism to retry if previous attempts to load failed so that you can properly handle and recover
from exceptional circumstances such as network outages or service interruption. Loadable resources appropriately handle concurrent and
repeated requests to load in order to accommodate the common practice of sharing the same resource instance among various parts of
an application, and also permit cancellation so that you can cancel loading a resource, for example, if the service is slow to respond.
Finally, loadable resources provide information about their initialization status through explicit states that can be inspected and monitored.
Loadable API
Classes that conform to the loadable pattern implement the Loadable interface.
Load status
The getLoadStatus method returns the state of the loadable resource. Four states are possible.
NOT_LOADEDthe resource has not been asked to load its metadata and its state isn't properly initialized yet.
LOADINGthe resource is in the process of loading its metadata asynchronously.
FAILED_TO_LOADthe resource failed to load its metadata (for example, due to network outage, or the operation was
cancelled, and so on.) The error encountered is available from the getLoadError method.
LOADEDthe resource successfully loaded its metadata and its state is properly initialized.
The following state transitions represent the stages that a loadable resource goes through.
The Loadable interface includes listeners that make it easy to monitor the status of loadable resources, display progress, and take
action when the state changes.
Loading
A resource commences loading its metadata asynchronously when loadAsync is invoked. At that time, the load status changes from
NOT_LOADED to LOADING. When the asynchronous operation completes, the callback is invoked. If the operation encounters an error,
the error argument in the callback is populated, and load status is set to FAILED_TO_LOAD. If the operation completes successfully, the
error argument is null and the load status is set to LOADED, which means the resource has finished loading its metadata and is now
properly initialized.
Many times, the same resource instance is shared by different parts of the application. For example, a legend component and a table of
contents component may have access to the same layer, and they both may want to access the layer's properties to populate their UI.

Or the same portal instance may be shared across the application to display the user's items and groups in different parts of the
application. In order to accommodate this type of application development pattern and make things simple for you, loadAsync
supports multiple "listeners". It can be called concurrently and repeatedly, but only one attempt is ever made to load the metadata. If a
load operation is already in progress (LOADING state) when loadAsync is called, it simply piggy-backs on the outstanding operation
and the callback is enqueued to be invoked when that operation completes. If the operation has already completed (LOADED or
FAILED_TO_LOAD state) when loadAsync is called, the callback is immediately invoked with the past result of the operation, be it
success or failure, and the state remains unchanged. This makes it safe for you to liberally invoke loadAsync on a loadable resource,
without having to check if the resource is already loaded or not, and without worrying that it will make unnecessary network requests
every time.
If a resource has failed to load, calling loadAsync on it subsequently will not change its state. The callback will be invoked immediately
with the past load error. In order to retry loading the resource, you must use retryLoadAsync instead. The advantage of this approach
is that if, hypothetically, loadAsync were to retry loading a failed resource, an app could easily end up making many asynchronous
requests to load the same resource just because it shared the same resource instance in different parts of the application and each part
tried to load the resource without first checking if it was already loading. This pattern allows loadAsync to be invoked indiscriminately
without worrying that it might add overhead, and makes retrying a separate and explicit scenario using retryLoadAsync.
Retry loading
A resource retries to load its metadata when retryLoadAsync is invoked, but only if it previously failed to load (FAILED_TO_LOAD
state) or wasn't loaded to begin with (NOT_LOADED state). The resource transitions to the LOADING state and makes a new attempt to
fetch its metadata. The callback is invoked when the asynchronous operation completes.
If the resource has already fetched its metadata and has initialized its state (LOADED state), retry doesn't do anything. Instead, retry
immediately calls the callback with the past result and the state of the object remains unchanged. The object's metadata isn't fetched
again.
If an asynchronous operation is already in progress (LOADING state) when retryLoadAsync is called, it simply piggy-backs on the
outstanding operation and the callback is enqueued to be invoked when that operation completes.
The main use case for this method is if the loadable failed to load previously, for example, due to network outage or service interruption.
It is not meant to refresh the metadata for an already loaded resource which should instead be accomplished by creating a new
instance of the loadable resource.
Cancel loading
A resource cancels any outstanding asynchronous operation to load its metadata when cancelLoad is invoked and it transitions from
LOADING to FAILED_TO_LOAD state. The getLoadError method will return information that reflects that operation was cancelled.
This method should be used carefully because all enqueued callbacks for that resource instance will get invoked with an error stating
that the operation was cancelled. Thus, one component in the application can cancel the load initiated by other components when
sharing the same resource instance.
The cancelLoad method does nothing if the resource is not in LOADING state.
Conveniences
Cascading load dependencies
It is common for a loadable resource to depend on loading other loadable resources to properly initialize its state. For example, a portal
item cannot finish loading until its parent portal finishes loading. A feature layer cannot be loaded until its feature service table is first
loaded. This situation is referred to as a load dependency.
Loadable operations invoked on any resource transparently cascade through its dependency graph. This helps simplify using loadable
resources and puts the responsibility on the resource to correctly establish and manage its load dependencies.
The following code example shows how this cascading behavior leads to concise code. Loading the map causes the portal item to begin
loading, which in turn initiates loading its portal. You do not have to load each one of them explicitly.

// create a Map which is loaded from a webmap

UserCredential creds = new UserCredential("myuser", "password");
Portal portal = new Portal("http://myportal/");
portal.setCredential(creds);
final PortalItem portalItem = new PortalItem(portal, "5cdcac1d6d814b82a48453d3e3876fd1");
// make a map from portal item

map = new ArcGISMap(portalItem);
//load the map
map.loadAsync();
//listen to when it is loaded

map.addDoneLoadingListener(() -> {
System.out.println("map loaded");
});
It is possible that dependencies may fail to load. Some dependencies might be critical without which the initiating resource cannot load
successfully, for example, a portal item's dependency on its portal. If a failure is encountered while loading such a dependency, that
error would bubble up to the resource that initiated the load cycle, which would also fail to load. Furthermore, retrying to load that
resource would automatically retry loading the failed dependency. Other load dependencies may be incidental, such as a map's
dependency on one of its operational layers, and the resource may be able to load successfully even if one of its dependency fails to
load.
Overriding state before initialization

A loadable resource's state is not properly initialized until it has finished loading. Accessing properties of the resource before the
resource is loaded could return null or uninitialized values that might change when the resource finishes loading. Therefore, it is always
advisable to wait until the resource has finished loading before accessing its properties. However, many times, especially while
prototyping, you may want to change a property value before the resource is loaded without regard for its proper initialized value. For
instance, you may want to change the scale visibility of a layer or the initial viewpoint of a map. To simplify this workflow without
requiring that the resource first be loaded, loadable resources permit overriding their properties before the resource has finished loading
and the overridden value will take precedence over the value specified in the resource's metadata.
The following code example shows how you can override the min/max scale properties of a layer without having to load it first.
ArcGISMapImageLayer censusLayer = new ArcGISMapImageLayer("http://sampleserver6.arcgisonline.com/arcgis/rest/services/Census/MapServer");
censusLayer.setMinScale(5000);
censusLayer.setMaxScale(1000000);
censusLayer.loadAsync();
censusLayer.addDoneLoadingListener(() -> {
// overridden min & max scale values will be retained even when the resource finishes loading
System.out.println("Layer Status: " + censusLayer.getLoadStatus());
System.out.println("Min Scale: " + censusLayer.getMinScale() + " Max Scale: " + censusLayer.getMaxScale());
});

Display a map
Maps specify how geographic data is organized and how it should be communicated to your app users. Each instance of a map
(ArcGISMap) represents an individual map you can display for your users. To display a map you must assign it to a map view (MapView).
In an MVC architecture, the map represents the model tier and the map view represents the view tier. The map and map view work
together to visualize the geographic data on a screen.
Users can interact with the map and its layers using the map view's built-in navigation tools. You have many ways to enhance this
experience by configuring the look and feel of the map and adding business logic to these user interactions.
Open a map
You can open a map by creating it from a web map or from a mobile map package.
Create the map object from a web map

Web maps can be accessed using either their URL or directly from a portal using their portal item ID. Both methods are described here
along with the authentication process required to access the map if it or its data is not public.
Using a web map URL
You can construct the map object from one of the maps URL strings as follows:
ArcGISMap map = new ArcGISMap("URL/to/webmap");
The map constructor supports these three URL formats:

The map viewer URLFor example, https://www.arcgis.com/home/webmap/
viewer.html?webmap=69fdcd8e40734712aaec34194d4b988c. The URL is provided in the browser's address bar
when a web map is created or viewed using the ArcGIS.com map viewer.
The item details URLFor example, https://www.arcgis.com/home/
item.html?id=69fdcd8e40734712aaec34194d4b988c. This URL is found in the address bar when you're viewing the
details page for an item presented in My Content in ArcGIS.com.
The item data URLFor example, https://www.arcgis.com/sharing/rest/content/items/
69fdcd8e40734712aaec34194d4b988c/data?. This is the address of the JSON string that represents the information to
display the map.
If the map is not public, the APIs authentication challenge handler automatically requests that the user provides his credentials.

Using a web map portal item
You can construct the map object using the map's portal item ID. You can find this 32 character ID within any of the three URLs
described above. For example, here is a map that's identified by the item ID of 69fdcd8e40734712aaec34194d4b988c.
1. Create the portal object by providing the URL string to the portal. In the example below, the public map is accessed from
ArcGIS Online (www.arcgis.com).
//construct the portal from the URL of the portal
Portal portal = new Portal("http://www.arcgis.com");
2. Construct the portal item object by providing the portal and the item ID string for the map.
//construct a portal item from the portal and item ID string
PortalItem mapPortalItem = new PortalItem(portal, "e229d715f7ca4fa980308549fb288165");
3. Pass the portal item to the map constructor.

//construct a map from the portal item
ArcGISMap map = new ArcGISMap(mapPortalItem);
Upon completion of this code, neither the portal, portal item, nor the map are loaded. These objects will be loaded when you pass the
map to the map view or if you load them explicitly. See the loadable pattern topic for more information. You can override any of the
map's properties by setting their value before the map is loaded.
Authentication
If the map or its layers are not public, you need to provide credentials to access them. In these cases you can either rely on the APIs
authentication challenge handler to prompt the user for their credentials or you can provide your own login facility and pass the
credentials to the portal's setCredentials method as described in the Access the ArcGIS platform topic.
Create a map object from a mobile map package

A mobile map package is a file object (.mmpk) created in ArcGIS Pro. It is a transport mechanism for maps, their layers, data, networks,
and locators. A mobile map package can be sideloaded onto a device by email, or by platform-specific transfer mechanism, or it can be
downloaded from a portal to the device.
Note: StreetMap Premium also provides ready-to-use and regularly updated mobile map packages
that include a street map, locator, and network dataset for areas throughout the globe. For
details, see Add StreetMap Premium data.
Each mobile map package can contain one or more maps that can be displayed in a map view. For more information, see creating
mobile map packages.
1. Obtain the file path to the mobile map package.
// The mobile map package has been placed in the apps documents folder
File mmpkFile = new File(Environment.getExternalStorageDirectory(), dataPath + "CaliforniaNevada.mmpk");
String mmpkPath = mmpkFile.getAbsolutePath();

2. Construct the mobile map package object using the file path.
final MobileMapPackage mobileMapPackage = new MobileMapPackage("path/to/file/.mmpk");
3. The mobile map package must be loaded into the app before the maps themselves can be accessed. Once the mobile map
package is loaded, any of its maps can be assigned to the map view to be displayed.
mobileMapPackage.addDoneLoadingListener(() -> {
if (mobileMapPackage.getLoadStatus() == LoadStatus.LOADED) {
System.out.println("Number of maps = " + mobileMapPackage.getMaps().size());
// In this case the first map in the array is obtained
ArcGISMap mobileMap = mobileMapPackage.getMaps().get(0);
} else {
// If loading failed, deal with failure depending on the cause...
}
});
mobileMapPackage.loadAsync();
Upon completion of this code the map is not loaded. You can override any of the map's properties by setting their value before the map
is loaded. See the loadable pattern topic for more information.
Display the map in a map view

To display a map, you assign it to a map view. You can assign a map to more than one map view in your app. Each map view can display
a different visible area of the map, can be configured in different ways, and can be designed to respond differently to user gestures.
Assign a map to a map view as follows:
mapView.setMap(map);
Assigning a map to a map view initiates the maps load cycle. When that cycle completes, the map view initiates the load cycle on the
maps layers in order to draw them. For more information loading resources (load cycles), see Loadable pattern of asynchronous
resources. You can monitor the loading of the individual layers using the map view's LayerViewStateChangedListener.
You can load the map into your app before assigning it to a map view. This is useful if you want to validate the content of the map or you
want to access any content or properties in the map without displaying it. For example, this code loads the map explicitly and checks if the
map contains bookmarks before it displays the map in the map view.
map.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
if (map.getLoadStatus() == LoadStatus.LOADED) {
// Once map is loaded, can check its properties and content
if (map.getBookmarks().size() > 0) {
// For example, show UI and allow user to choose a map bookmark...
}
} else {
// If loading failed, deal with failure depending on the cause...
dealWithLoadFailure();
}
}
});
map.loadAsync();
Monitor layer loading

Assigning a map to a map view or explicitly loading a map triggers loading of the map's basemap and operational layers. Each time the
state of a layer changes, the map view's LayerViewStateChangedListener is triggered. Examine the layer's view status to
determine whether a layer is active, loading, not visible, out of scale, or whether an error has occurred with the layer's loading process.
mapView.addLayerViewStateChangedListener(new LayerViewStateChangedListener() {
@Override
public void layerViewStateChanged(LayerViewStateChangedEvent layerViewStateChangedEvent) {
// Each layer may have more than one layer view state.
StringBuilder layerStatuses = new StringBuilder();
for (LayerViewStatus status : layerViewStateChangedEvent.getLayerViewStatus()) {
if (layerStatuses.length() > 0) {
layerStatuses.append(",");
}
layerStatuses.append(status.name());
}
showMessage(String.format("Layer '%s' status=%s", layerViewStateChangedEvent.getLayer().getName(),
layerStatuses.toString()));
}
});
Monitor map drawing

If your users pan or zoom the map or the business logic in your app changes the visible area of the map, then new map content will need
to be drawn. There will be a short time delay before this map drawing phase is completed. Your app may need to know that the drawing is
complete. For example, you may want your app to take a snapshot, or screenshot, of the map only when the drawing has finished.

Use the map view's DrawStatusChangedListener to detect whether the map drawing is in progress or has completed. For example,
this code displays a progress bar if the drawing is still in progress.
For example, this code displays a progress bar while drawing is in progress.
mMapView.addDrawStatusChangedListener(new DrawStatusChangedListener() {
@Override
public void drawStatusChanged(DrawStatusChangedEvent drawStatusChangedEvent) {
if(drawStatusChangedEvent.getDrawStatus() == DrawStatus.IN_PROGRESS){
progressBar.setVisibility(View.VISIBLE);
Log.d("drawStatusChanged", "spinner visible");
}else if (drawStatusChangedEvent.getDrawStatus() == DrawStatus.COMPLETED){
progressBar.setVisibility(View.INVISIBLE);
}
}
});
Navigate the map

When a map is first loaded into a map view, it's displayed at a geographical location defined by the map's initial view point. User's can then
pan or zoom the map with a range of gestures that are built into the map view. You can access the visible area of the map as a polygon
returned by the map view's getVisibleArea method. The visible area is returned as a polygon, and not an envelope, because the map
may be rotated and each corner of the map may contain unique x-y coordinates.
Polygon polygon = mapView.getVisibleArea();
As a developer you can programmatically set the map's visible area in your app by calling one of the map view's many setViewpoint
methods. Many options are available to choose from to allow you to:
Rotate the map to a specified angle.
Zoom the map to the specified scale.
Zoom or pan the map so that a given geometry fits the visible area of the map view.
Zoom or pan the map to a specified location.
Zoom or pan the map to a specific view point. You can define a view point using a:
Center and scale
Center, scale, and rotation
Latitude, longitude, and scale
Target extent
Target extent and rotation
For example, the code that follows sets the view point to a specific lat, long, and scale with an animation that lasts two seconds. Each
method returns a boolean value so you can detect if the animation was interrupted by the user.
Viewpoint viewpoint = new Viewpoint(27.3805833, 33.6321389, 6E3);
final ListenableFuture<Boolean> viewpointSetFuture = mapView.setViewpointAsync(viewpoint, 2);

viewpointSetFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
boolean completed = viewpointSetFuture.get();
if (completed) showMessage("Animation completed successfully");
} catch (InterruptedException e) {
showMessage("Animation interrupted");
} catch (ExecutionException e) {
// Deal with exception during animation...
}
}
});
Configure the map view

You can enhance your user's map experience by displaying the device's current location, rotating the map display, or making the world
map seamless.
Display the users current location

Many devices provide information about their location through Wi-Fi, cellular networks, or GPS. The device's operating system passes
its location to the map view so you can display and track the device on a map. The map view always tries to get the most accurate
location available but the reported location could be a best approximation based on signal strength, satellite positions, and other factors.
By default, the map view displays the location with a blue, round symbol and a semi-transparent blue circle around this symbol to
indicate the range of accuracy.

The display of the location on a map, the symbol used, the animation, and the auto pan behavior are managed by an instance of the
LocationDisplay. Each MapView has its own instance of a location display.
Start displaying the devices location as follows:
LocationDisplay locationDisplay = mapView.getLocationDisplay();
locationDisplay.addDataSourceStatusChangedListener(new LocationDisplay.DataSourceStatusChangedListener() {
@Override
public void onStatusChanged(LocationDisplay.DataSourceStatusChangedEvent dataSourceStatusChangedEvent) {
if (dataSourceStatusChangedEvent.getSource().getLocationDataSource().getError() == null) {
showMessage("Location Display Started=" + dataSourceStatusChangedEvent.isStarted());
} else {
// Deal with problems starting the LocationDisplay...
}
}
});
locationDisplay.startAsync();
Note: Apps using LocationDisplay must be granted Location permissions.
For more information about displaying the location, see the LocationDisplay in the API Reference.
Enable wrap around

Most flat representations of the earth extend up to 180 degrees east and west longitude and make it difficult to visualize areas that span
across the 180th meridian. As we know the world is spherical and does not end at the 180th meridian. Enabling wrap around in the map
view displays a 2D map extending seamlessly across the 180th meridian. For more information, see the wrap around maps topic.
// wraparound is enabled if layers within map support it
mapView.setWrapAroundMode(WrapAroundMode.ENABLE_WHEN_SUPPORTED);
Note: If your map has wrap around enabled and you're working with map locations, map extents,
or are editing or sketching geometries with a map, you must normalize the geometries.
Note: Some maps do not support wrap around; maps that do support wrap around will
automatically be displayed in wrap around
Rotate the map

You may not want your map to display in a North-South direction in your device. You can reorient your map in the map view by setting
the viewpoint rotation. A positive rotation value rotates the map in an counterclockwise and a negative rotation value rotates the map in
a clockwise direction.
final ListenableFuture<Boolean> viewpointSetFuture = mapView.setViewpointRotationAsync(90);
viewpointSetFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
boolean completed = viewpointSetFuture.get();
if (completed)
showMessage("Rotation completed successfully");
} catch (InterruptedException e) {
showMessage("Rotation interrupted");
} catch (ExecutionException e) {
// Deal with exception during animation...
}
}
});
Enhance the user's map interaction

You can provide extra functionality as your users interact with the map by implementing your own map touch listener. Each method on
your listener will receive the touch event information at the position that the user interacted with the screen. You just need to add code
within the method to use these coordinates.
The easiest way to do this is to make use of the existing DefaultMapViewOnTouchListener.
1. Create a class that extends the DefaultMapViewOnTouchListener.
class MapSingleTapListener extends DefaultMapViewOnTouchListener {
2. Override the methods corresponding to the gestures you want to change the behaviour of. In this example, the single-tap gesture
is changed to display the tapped location in map coordinates by overriding onSingleTapConfirmed.
@Override
public boolean onSingleTapConfirmed(MotionEvent e) {
Point mapPoint = mapView.screenToLocation(new android.graphics.Point((int)e.getX(), (int)e.getY()));
showMessage(String.format("User tapped on the map at (%.3f,%.3f)", mapPoint.getX(), mapPoint.getY()));
return true;
}

3. Set an instance of your new listener class onto the MapView.

mapView.setOnTouchListener(new MapSingleTapListener(context, mapView));
Note: Alternatively, you can directly implement the MapView.OnTouchListener interface, and
handle all gestures yourself.
Take a snapshot of the map

Take a snapshot, or screen capture, of the visible area of a map using the map view's exportImageAsync method. Use the image within
the app or store it in a file to be shared, printed, or included in other documents.
The code below demonstrates how to save the exported Bitmap, returned from the exportImageAsync method future, to a file in the
Pictures directory of the devices local storage. Note that this code will require the WRITE_EXTERNAL_STORAGE Android permission.
final ListenableFuture<Bitmap> exportImageFuture = mapView.exportImageAsync();
exportImageFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
// Get the resulting Bitmap from the future
Bitmap bitmap = exportImageFuture.get();
if (bitmap != null) {
// Create a File to write the Bitmap into
File file = new File(Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_PICTURES), "map.png");
FileOutputStream fileOutputStream;
try {
// Write the Bitmap into the file and close the file stream.
fileOutputStream = new FileOutputStream(file);
bitmap.compress(Bitmap.CompressFormat.PNG, 100, fileOutputStream);
fileOutputStream.close();
} catch (IOException e) {
// Deal with exception writing file...
}
}
} catch (InterruptedException | ExecutionException e) {
// Deal with exception during export...
}
}
});
Note: If you want to store this image as a thumbnail of a portal item, be aware that the size limit of a
thumbnail is 1 MB. Check the image size before saving the image as a thumbnail and, if
necessary resize it.

Build a new map

A map gives you a structure for organizing your geographical data so your users can view, explore, and interact with it. This page
describes how to design and build a map with code and then save it for later use by another app or by a different user.
Note: You can also create a map for use in your ArcGIS Runtime app using ArcGIS Online's map
viewer (how-to steps are in ArcGIS Online Help's getting started with maps page).
To build a map with code for your ArcGIS Runtime app, you use this API to create a map. In this API, the map is represented by the
ArcGISMap class that gives you all the methods and properties you need to set the background layer, add the operational layers, set the
spatial reference, add bookmarks, and save the map. If you wish to display the map and allow users to interact with it then you pass the
map to the MapView class.
Map design considerations

When designing a map you must:
Choose a background for your map so that your users can orient themselves. Esri provides a number of standard basemaps that
you can use as a background or you can use other providers, such as your organization's basemaps. Alternatively, you can
construct a basemap in code.
Ensure that you specify a spatial reference for your map that allows the layers to be aligned and displayed together. It will be more
efficient if all of your operational layers have the same spatial reference as the map and basemap because the operational layers
will not need to be reprojected.
Start the map display in a specific and recognizable geographical area.
Only show the data that your users need. Set the minimum and maximum scale thresholds for layers so only useful information is
displayed at each scale.
Construct the map

This API provides several types of map constructors. Your choice will depend upon whether you wish to specify the desired basemap,
spatial reference or initial viewpoint when you create the map. There is the all-encompassing constructor that you can use to create a map
with a standard Esri Imagery basemap that is centered on a latitude and longitude location and zoomed into a specific level of detail.
map = new ArcGISMap(Basemap.Type.IMAGERY, 56.008993, -2.725301, 10);
In this example BasemapType.Imagery refers to the ArcGIS Online service available at the REST end point
https://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer. This basemap, like all the standard Esri basemaps, uses
the Web Mercator spatial reference and this, in turn, determines the spatial reference of the map. The latitude and longitude values center
the map at a particular location and the levelOfDetail determines the scale of data that is displayed. So, this constructor will display a
map at a specified location and scale no matter what size of map is displayed to the user.
Other map constructors

There are a number of other map constructors that you can use if you want to set the spatial reference, the basemap or the initial
viewpoint at a later point in time. Your choice depends on the workflow in your app. Use this constructor if you:
Know the basemap but not the starting location
map = new ArcGISMap(Basemap.createNationalGeographic());
Know the spatial reference but not the basemap

map = new ArcGISMap(SpatialReference.create(27700));
Want an empty map

map = new ArcGISMap();
Create a basemap
A basemap is composed of a collection of base layers and reference layers. The base layer can give your map a recognizable background
so that your operational layers are displayed in context. The reference layer can display useful text labels such as the city, street, river or
mountain names.

Base layers are displayed at the bottom of a map, and reference layers are displayed at the top, with the maps operational layers
sandwiched between them. The content of a basemap is typically static and does not change frequently so tiled layers make good
basemap layers as they provide faster access to relatively static maps. (For more information see Layer types.) As discussed previously,
ArcGIS Online provides a number of ready-to-use standard basemaps such as the World imagery, topographic, oceans, streets, and so
on. Or, you can add basemaps from your organization or another public service. Also, you can create your own basemap by combining
(mashing up) layers.
Standard ArcGIS Online basemaps

To use, instantiate a basemap, such as the ArcGIS Online World Streets basemap.
Basemap basemap = Basemap.createStreets();

map.setBasemap(basemap);
A single layer
You can also instantiate a basemap with a single layer. For example, you could instantiate a tiled layer, construct a basemap from that
layer and then pass that basemap to the map.
ArcGISTiledLayer tiledLayer = new ArcGISTiledLayer("http://services.arcgisonline.com/arcgis/rest/services/Canvas/World_Dark_Gray_Base/MapServer");
Basemap basemap = new Basemap(tiledLayer);

map.setBasemap(basemap);
Combining layers into one basemap

You can also combine a number of layers to create a single basemap as long as these layers have the same spatial reference. To do
this instantiate a number of layers and then add them to the baselayers list of the basemap.
ArcGISTiledLayer tiledLayer = new ArcGISTiledLayer("http://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer");
map.getBasemap().getBaseLayers().add(tiledLayer);
map.getBasemap().getBaseLayers().add(censusLayer);
Extra information
In terms of the map's spatial reference, it's important to understand the following:
If a map does not have a spatial reference, it will automatically be set by the map's first basemap.
If you add a basemap to a map that already has a spatial reference, it must have the same spatial reference as the map;
otherwise it will fail to draw. This is also true if you exchange one basemap for another.
If the map does not have a basemap, then the map will adopt the spatial reference of the first operational layer that is added to
the map.
Just like the map, the basemap loads asynchronously. This is described in more detail in the loadable pattern topic.
Add operational layers

Operational layers are a category of layers that provide geographic content that is of specific interest to the app. Your choice of layer type
will determine whether you can edit, query, identify or overwrite the layer rendering. For more information about the types of operational
layers please refer to the topic Layer types. Typically, operational layers contain data that changes more frequently than that of a
basemap.
To add an operational layer to the map, add the layer to the map's operational layers list.
// Add layer to the map (by default, added as top layer)
map.getOperationalLayers().add(censusLayer);
A layer that is added first is placed directly above the basemap and is in the 0th position in the map's operational layers list. If you add
additional layers they are placed above the last layer and their position will be incremented by one. So the next layer will be in the first,
then the next in the second position, and so on.

Note: If your code adds operational layers to an existing map, the maps original list of operational
layers is overridden to contain only the added layers. To keep the maps original operational
layers and add new ones, wait until the map is loaded before adding operational layers. You
can declare new operational layers outside the maps declaration, and use a signal handler to
wait for the map to finish loading before adding the new layers. See the next section of this
topic for details about loading a map and its layers.
If you wish to, you can insert a layer into the list of operational layers at a specific position.
ArcGISMapImageLayer usaLayer = new ArcGISMapImageLayer("http://sampleserver6.arcgisonline.com/arcgis/rest/services/USA/MapServer");
// Insert layer at position 0 (added as bottom layer of the map)
map.getOperationalLayers().add(0, usaLayer);
All operational layers are added to the map in the same way and also conform to the asynchronous loading pattern as detailed in the
Loadable pattern topic.
Operational layer properties

Each operational layer has a set of default properties. You can modify these properties so that they are more appropriate for your map.
For example, you can:
Set the maximum and minimum scale at which the layer is visible.
Change the opacity of the layer.
Change the visibility of the layer.
Override the rendering.
Specify a definition expression.
Change the order in which the layers are displayed in the map.
For more information please explore the specific layer and sublayer classes.
Load the map and its layers

The map has been designed to load as quickly as possible. You will be able to access the map and set its properties and iterate through
its layers even if a layer has failed or a layer's service response is slow. One broken layer should not prevent the entire map from being
used. A map should not load layers that are not needed. The advantage of this design is that the map can be used without having to wait
for all of the layer's to be available.
When you construct the map, its load status will be NOT_LOADED. You can load the map (initiate the map's load cycle) either by:
Calling loadAsync on the map
map.loadAsync();
map.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
//code here to check for error status
if (map.getLoadStatus() == LoadStatus.FAILED_TO_LOAD) {
showMessage("map failed to load : " + map.getLoadError().getMessage());
}
}});
Or, by setting the map on the mapview.

mapView = new MapView(context);
mapView.setMap(map);
Upon completion of the map's load cycle, the map's load status will be LOADED, indicating that:
The map's spatial reference has been defined by the basemap's spatial reference. The Esri basemaps defined in the API all use
Web Mercator.
The map's initial viewpoint has been specified, for example, by setting the map's latitude, longitude and level of detail. (The
levelOfDetail value sets the scale or resolution at which the map is displayed.)
The map's list of layers has been created.
The map can be in a loaded state and ready for user interaction even if the individual layers have not finished loading. The map's layers
could be in a LOADED, NOT_LOADED, or FAILED_TO_LOAD state. Please explore the Loadable pattern for more information on loading
maps and layers.

Save the map to a portal

You have designed and built a map. Now you can save the map so you, or other users, can view at a later time. To save the map to the
Portal for ArcGIS or your organization's portal the following conditions must be met:
The map must be in a loaded state.
Any layers that you wish to save must be in a loaded state.
You must be authenticated to a portal.
Have the map and layers been loaded?

Before attempting to save the map it is prudent to confirm that the map is loaded and that the layers are loaded. If a layer has failed to
load you may decide to save the map without the layer or investigate why you cannot access the layer. This will depend on your
workflow.
Note: If a layer has an invalid URL then the layer will have a layer type of Unknown Layer. This
layer will not be saved to the map.
// check map is loaded

if (map.getLoadStatus() == LoadStatus.LOADED) {
// check each operational layer
for (Layer layer : map.getOperationalLayers()) {
// is the layer loaded without error?
if (layer.getLoadStatus() == LoadStatus.FAILED_TO_LOAD) {
// deal with layer loading errors...
showMessage("layer " + layer.getName() + " not loaded");
}
}
}
Has the user authenticated with the portal?

When your user authenticates to a portal (including ArcGIS Online) they have access to the maps that they own. When they log into
ArcGIS Online or Portal for ArcGIS, these maps are visible in a set of folders under the My Content tab. In Portal for ArcGIS, the My
Content filter is selected by default. When a user saves a map with this API, the map is saved into a folder under My Content and is
accessible from there.
To authenticate a user to a portal you must create a portal object, provide the essential credentials and then asynchronously load the
portal. Just like map and layer classes, the Portal class conforms to the Loadable pattern.
// Set the DefaultAuthenticationChallegeHandler to allow authentication with the portal.
DefaultAuthenticationChallengeHandler handler = new DefaultAuthenticationChallengeHandler(activityContext);
AuthenticationManager.setAuthenticationChallengeHandler(handler);
// Create a Portal object, indicate authentication is required
final Portal portal = new Portal("http://www.arcgis.com", true);
// Load the portal

portal.loadAsync();
portal.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
// When the portal is loaded, check success
if (portal.getLoadStatus() == LoadStatus.LOADED) {
final PortalUser user = portal.getUser();
// Check there is an authenticated user (if user is null, only anonymous access is possible)
if (user != null) {
final ListenableFuture<PortalUserContent> contentFuture = user.fetchContentAsync();
// Existing maps belonging to the user are available in the PortalUserContent...
}
}
}
});
For more information on authenticating with a portal, see Access the ArcGIS Platform.
Save the map

Saving a map to the portal creates a new web map portal item. The map is placed in a folder of your choice in the My Content area of
the authenticated user. For full details on how to save the map to a portal, see Save a map.

Share the map

By default, the map that the user adds to the portal is only accessible to that user. The map is not available to others. For example, the
map does not appear in search results and is not part of any group. There are several options for sharing a map. The options are
described in the Share a portal item topic.

Add raster data

You can add raster data stored on your desktop or device or from an image service to your ArcGIS Runtime map by:
Adding a raster using a raster layerif you want to display the raster
Adding it for use with raster function
Raster data provides a unique way of conceptualizing, analyzing, and visualizing geographic phenomena that is distinct from vector
formats (using points, lines, and polygons to represent geographic features, in other words). For more information on raster data, including
advantages and disadvantages of using it, see What is raster data? in ArcGIS Desktop help.
Raster data is represented by the Raster class. Your ArcGIS Runtime app can work with a range of raster data including raster files,
mosaic datasets, raster data shared through image services, or the results of raster functions. A raster function can take any of these
rasters as input for analysis.
The Raster object implements the loadable pattern, which asynchronously accesses raster data from remote services or datasets.
Create a raster from a raster file

To add raster files stored on your desktop or device to your app, create a Raster object using the path of the raster file.
// create a raster from a raster file
String rasterFilePath = "/path/to/raster.format";
Raster raster = new Raster(rasterFilePath);
Create a raster from a mosaic dataset

Raster data stored in a local mosaic dataset should be read through MosaicDatasetRaster, which inherits from Raster. A
MosaicDatasetRaster object is instantiated with a path of the local geodatabase and a name of the dataset.
// create raster and raster layer
String rasterFilePath = "/path/to/raster.format";
Raster raster = new Raster(rasterFilePath);
RasterLayer rasterLayer = new RasterLayer(raster);
// add as a basemap
ArcGISMap map = new ArcGISMap(new Basemap(rasterLayer));
// Alternatively you can create a raster layer from a mosaic dataset
MosaicDatasetRaster mosaicDatasetRaster = new MosaicDatasetRaster("/path/to/mosaic.sqlite", "rasterName");
RasterLayer mosaicDatasetRasterLayer = new RasterLayer(mosaicDatasetRaster);
// add as an operational layer

map.getOperationalLayers().add(mosaicDatasetRasterLayer);
Create a raster from an image service

Raster and image data can be shared as an image service using ArcGIS Server. An image service provides access to raster data through
a web service. A single raster dataset or a mosaic dataset which contains a collection of raster datasets can be served as one image
service. The mosaic dataset can dynamically process and mosaic the images on-the-fly. An image service supports accessing both the
mosaicked image and its catalog, as well as individual rasters in the catalog. For more information on image services, see Key concepts
for image services in the ArcGIS help.
Use the ImageServiceRaster class to work with image services in your ArcGIS Runtime app. You can create an
ImageServiceRaster with the URL of an image service. And then if you want to display the raster data on a map, create a raster layer
for it.
ImageServiceRaster is a subclass of Raster, so any operation that can be applied to the Raster class, such as raster functions, can
also be applied to ImageServiceRaster. Besides the common properties inherited from the Raster class, ImageServiceRaster
has additional properties and capabilities such as the image service metadata and rendering rules. Once the image service raster has
been loaded, the metadata of the image service can be retrieved through the service info property, which is represented by
ArcGISImageServiceInfo. However, only a subset of the metadata including attribution text and a list of info of predefined service
rendering rules are exposed in ArcGIS Runtime. For more info on the metadata of an image service, see Image Service in the ArcGIS
REST API help.

// load the image service raster

final ImageServiceRaster serviceRaster = new ImageServiceRaster(url);
serviceRaster.loadAsync();
serviceRaster.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
if (serviceRaster.getLoadStatus() == LoadStatus.LOADED) {
// get service info
ArcGISImageServiceInfo serviceInfo = serviceRaster.getServiceInfo();
// get rendering rule info list
List<RenderingRuleInfo> renderingRuleInfos = serviceInfo.getRenderingRuleInfos();
}
}
});
Rendering rules
A rendering rule defines how the requested image should be rendered or processed. ImageServiceRaster allows you to apply
service-defined or client-defined rendering rules on an image service by setting its rendering rule property. You can create a
RenderingRule from a RenderingRuleInfo object or a JSON string that specifies a service-defined or client-defined rendering rule
and then set it on the image service raster. For the syntax of rendering rules, see raster function (JSON) objects in the ArcGIS REST
API help.
//example of creating a RenderingRule with a rendering rule info which has been retrieved from ArcGISImageServiceInfo and set it on am image service raster
List<RenderingRuleInfo> ruleInfos = serviceRaster.getServiceInfo().getRenderingRuleInfos();
if (ruleInfos.size() > 1) {
// create rendering rule
RenderingRule renderingRule = new RenderingRule(ruleInfos.get(1));
// get a property of rendering rule
renderingRule.getRenderingRuleInfo().getName();
// set on image service raster
serviceRaster.setRenderingRule(renderingRule);
// create a raster layer
RasterLayer layer = new RasterLayer(serviceRaster);
}
Alternatively you can create a RenderingRule using a JSON string that specifies a service-defined or client-defined rendering rule.
// create rendering rule
RenderingRule renderingRule =
new RenderingRule("{\"rasterFunction\" : \"Hillshade\",\"rasterFunctionArguments\" : {\"Azimuth\" : 215.0,\"Altitude\" : 75.0,\"ZFactor\" : 0.3},\"variableNa
// get a property of rendering rule
renderingRule.getRenderingRuleJson();
// set on image service raster
serviceRaster.setRenderingRule(renderingRule);
RasterLayer layer = new RasterLayer(serviceRaster);
Create a raster from a raster function

Functions can be applied to a raster to process that data. This processing is not permanently applied to the data; instead, it is applied on
the fly as the rasters are accessed.
ArcGIS Runtime supportsa subset of raster functions that the ArcGIS REST API supports.
The code below gives an example of how to create a raster from a raster function.
// create a raster function
RasterFunction rasterFunction = new RasterFunction("/path/to/raster/function.json");
// initialize the arguments of the raster function

RasterFunctionArguments rasterFunctionArguments = rasterFunction.getArguments();
List<String> rasterNames = rasterFunctionArguments.getRasterNames();
// assuming rasterNames has 2 entries, set the 2 rasters
rasterFunctionArguments.setRaster(rasterNames.get(0), new Raster("/path/to/raster/0"));
rasterFunctionArguments.setRaster(rasterNames.get(1), new Raster("/path/to/raster/1"));
// create a new raster based on the function
Raster raster = new Raster(rasterFunction);
Raster functions supported by ArcGIS Runtime

ArcGIS Runtime supports a subset of raster functions supported by the ArcGIS REST API. The raster functions supported by ArcGIS
Runtime are provided in this section, along with the syntax for using them. The syntax is close to the ArcGIS REST syntax for the same
functions but is not exactly the same.
The general syntax for ArcGIS Runtime raster functions is the following:
{
"raster_function":{"type":"<Raster Function Name>"},
"raster_function_arguments":
{
"argument1":"<JSON Value Object>",
"argument2":"<JSON Value Object>",
"argumentN":"<JSON Value Object>",
"type":"Raster_function_arguments"
},
"type":"Raster_function_template"
}

Clip
{
{
"minx":{"double":value,"type":"Raster_function_variable"},
"miny":{"double":value,"type":"Raster_function_variable"},
"maxx":{"double":value,"type":"Raster_function_variable"},
"maxy":{"double":value,"type":"Raster_function_variable"},
"dx":{"double":cell_size_x,"type":"Raster_function_variable"},
"dy":{"double":cell_size_y,"type":"Raster_function_variable"},
"raster":{"name":"raster","is_raster":true,"type":"Raster_function_variable"},
},
"raster_function":{"type":"Clip_function"},
}
Colormap
{
{
"raster_colormap":{"colors":[color1,color2,...,colorN],"type":"Raster_function_variable"},
},
"raster_function":{"type":"Colormap_function"},
}
Colormap_to_RGB
{
"raster_function":{"type":"Colormap_to_RGB_function"},
{
},
}
Color_ramp
{
"raster_function":{"type":"Color_ramp_function"},
{
"resizable":{"bool":false,"type":"Raster_function_variable"},
"color_ramp":
{
"color_ramp":
{
"ramps":
[
{"to_color":[0,255,0],"from_color":[0,191,191],"num_colors":3932,"type":"Algorithmic_color_ramp","algorithmic_type":"hsv"},
{"to_color":[20,20,20],"from_color":[191,127,63],"num_colors":3935,"type":"Algorithmic_color_ramp","algorithmic_type":"hsv"}
],
"type":"Multipart_color_ramp"
},
"type":"Raster_function_variable"
},
"type":"Raster_function_arguments",
},
"type":"Raster_function_template",
}
Composite_band
{
"raster_function":{"type":"Composite_band_function"},
{
"raster_names":{"name":"raster_names","string_array":["r1","r2","r3","r4"],"type":"Raster_function_variable"},
"r1":{"name":"r1","is_raster":true,"type":"Raster_function_variable"},
},
}

Extract_band
{
{
"exact_match":{"bool":false,"type":"Raster_function_variable"},
"band_indexes":{"int_array":[2,1,0],"type":"Raster_function_variable"},
},
"raster_function":{"type":"Extract_band_function"},
}
Geometric
{
"raster_function":{"type":"Geometric_function"},
{
"raster_transform":{"raster_transform":"Raster Transform JSON object","type":"Raster_function_variable"},
"z_offset":{"double":0,"type":"Raster_function_variable"},
"z_factor":{"double":1,"type":"Raster_function_variable"},
"raster":{"is_raster":true,"name":"raster","type":"Raster_function_variable"},
},
}
Hillshade
{
"raster_function":{"type":"Hillshade_function"},
{
"z_factor":{"double":0.0002,"type":"Raster_function_variable"},
"slope_type":{"raster_slope_type":"none","type":"Raster_function_variable"},
"azimuth":{"double":315,"type":"Raster_function_variable"},
"altitude":{"double":45,"type":"Raster_function_variable"},
"nbits":{"int":8,"type":"Raster_function_variable"}, // Number of bits per pixel for output raster
},
}
Mask
{
"raster_function":{"type":"Mask_function"},
{
"nodata_values":{"double_array":[value1, value2, ..., valueN],"type":"Raster_function_variable"},
"nodata_interpretation":{"nodata_interpretation":"all","type":"Raster_function_variable"},
},
}
Pansharpen
{
"raster_function":{"type":"Pansharpen_function"},
{
"weights":{"double_array":[0.10000000000000001,0.5,0.40000000000000002,0.29999999999999999],"type":"Raster_function_variable"},
"pansharpen_type":{"pansharpen_type":"gram_schmidt","type":"Raster_function_variable"},
"pan_raster":{"name":"pan_raster","is_raster":true,"type":"Raster_function_variable"},
},
}
Raster_calculator
{
{
"expression":{"string":"r1 + r2","name":"expression","type":"Raster_function_variable"},
"raster_names":{"name":"raster_names","type":"Raster_function_variable"},
"raster_names":{"name":"raster_names","string_array":["r1","r2"],"type":"Raster_function_variable"},
},
"raster_function":{"type":"Raster_calculator_function"},
}

Stretch
{
"raster_function":{"type":"Stretch_function"},
{
"stretch_type":{"raster_stretch_type":"minimum_maximum","type":"Raster_function_variable"},
"min_values":{"double_array":[-10977],"type":"Raster_function_variable"},
"max_values":{"double_array":[8685],"type":"Raster_function_variable"},
"estimate_stats":{"bool":false,"type":"Raster_function_variable"},
},
}
Add a raster using a raster layer

It's not necessary to display the raster data you work with in your app. However, if you want your user to view raster data on a map, add
the raster as a RasterLayer. A RasterLayer can render raster data from any type of Raster.
RasterLayer rasterLayer = new RasterLayer(raster);
// add as a basemap
ArcGISMap map = new ArcGISMap(new Basemap(rasterLayer));
You can add it to a map as either a basemap or an operational layer. When adding a raster layer as an operational layer to a map with
different spatial reference, the layer will be reprojected on the fly and be added to the map.
// Alternatively you can add as an operational layer
RasterLayer mosaicDatasetRasterLayer = new RasterLayer(mosaicDatasetRaster);
// add as an operational layer
map.getOperationalLayers().add(mosaicDatasetRasterLayer);
You can also change the renderer, as described below, to control how the data is visualized on the map.
See Layers and tables for more information about creating and working with raster layers.
Change the renderer

When a raster layer is created from a raster, a default renderer is used to display the data on a map. As with other layer types supported
by ArcGIS Runtime, a raster layer allows you to change how it is symbolized by creating a raster renderer and applying it to the layer.
When you change the renderer of a raster layer, only the display properties of the layer are updated. The underlying raster data wont
be affected.
An example of setting a StretchRenderer with a Minimum-Maximum stretch type on a RasterLayer.
StretchParameters stretchParameters;
switch (stretchTypeComboBox.getSelectionModel().getSelectedItem()) {
case "MinMax":
stretchParameters = new MinMaxStretchParameters(Arrays.asList(minValue), Arrays.asList(maxValue));
break;
case "PercentClip":
stretchParameters = new PercentClipStretchParameters(minValue, maxValue);
break;
default:
stretchParameters = new StandardDeviationStretchParameters(standardDeviationValue);
}
// create blend renderer
StretchRenderer stretchRenderer = new StretchRenderer(stretchParameters, null, true, null);
rasterLayer.setRasterRenderer(stretchRenderer);
RasterRenderer is the base class inherited by all renderers available to display a raster layer and allows you to control how raster
data are presented (visualized). Each of the following renderers are types of RasterRenderer and can be used to display your raster
layer in different ways.
HillshadeRendererCreates a grayscale 3D representation of an elevation surface, with the sun's (hypothetical) position
taken into account for shading the image. It can be applied to a raster layer created with single-band raster data.
BlendRendererBlends a hillshade image (derived from the raster) with the original raster. This provides a look similar to the
original raster but with some terrain shading, for a rich, textured look.
ColormapRendererProvides a discrete mapping of raster pixel values to colors. All pixels matching the specified value are
rendered using the mapped color. This can be useful for tasks such as land classification.
StretchRendererDisplays continuous raster cell values across a gradual ramp of colors. Use the stretch renderer to draw a
single band of continuous data. The stretch renderer works well when you have a large range of values to display, such as in
imagery, aerial photographs, or elevation models.

RGBRendererUses the same methods as the stretch renderer but allows you to combine bands as red, green, and blue
composites.
Supported raster formats

ArcGIS Runtime supports a subset of raster file formats that ArcGIS Desktop supports. The raster file formats ArcGIS Runtime supports
include the following:
ASRP/USRP
CIB1, 5, 10
CRF
DTED0, 1, 2
GeoTIFF
HFA
HRE
IMG
JPEG
JPEG 2000
NITF
PNG
RPF
SRTM1, 2
Mobile mosaic datasets
Not all RPF products/formats are listed here, but they're generally supported. For descriptions of RPF formats supported by the U.S.
military, see the MIL-STD-2411 publication for details.
Note: You can create a mobile mosaic dataset by using the Mosaic Dataset to Mobile Mosaic Dataset
geoprocessing tool in ArcGIS Pro.

About raster data

A raster consists of a matrix of cells (pixels) organized into rows and columns (a grid, in other words) where each cell contains a value
representing information. Rasters are things like digital aerial photographs, imagery from satellites, digital pictures, elevation models,
output from spatial analysis, and so on. Rasters used as GIS data are generally categorized into two broad types: thematic, representing
discrete features on the ground in much the same way a polygon data set might (zoning or land use, for example) and continuous,
modeling a phenomenon that changes continuously across a surface (temperature or elevation, for example). Photographs and scanned
images are another type of raster data that you might use in your mapping app, perhaps for visualizing an area or as additional
information associated with features in your map.

Wraparound maps
A globe provides a better representation of the earth than a flat map does. In addition to more accurately displaying the shape of the earth,
a globe provides seamless interaction with the features it displays. When spinning a globe, for example, it does not stop when it reaches a
specific location (longitude). While a flat map has to divide the earth along a line of longitude (usually at 180 east/west), there's no reason
why a map displayed on a computer screen can't wraparound to provide a continuous display of features as you pan east or west.
Note: You may hear several different terms to describe the longitude at 180 east/west. While the
following terms are not completely analogous, they are often used to refer to this line of
longitude: Dateline, International Dateline, and Antimeridian.

Enable or disable wraparound

By default, a map view attempts to wrap your map for a continuous experience as the user pans the map east and west. To disable
wraparound behavior for a map view (or to re-enable it), you can set the wraparound mode to the appropriate value. Wraparound can only
be applied to a map view if the following requirements are met.
The map's full extent covers the world.
The map's spatial reference is WGS 84 (WKID=4326) or Web Mercator (WKID=102113, 102100, or 3857). This means that all
tiled layers in the map must belong to one of these spatial references. Dynamic layers, however, can be in any spatial reference
because they are capable of reprojecting their data.
Dynamic layers in the map are based on services from ArcGIS Server 10.0 or higher. Earlier versions of the REST API do not
support well-known text (WKT) values for spatial reference, which is required for making dynamic map services support
wraparound.
If these requirements are not met, attempting to enable wraparound will fail silently (without raising an error, in other words).
The following example disables wraparound behavior if it is enabled and attempts to enable wraparound if it is not enabled.
// Check if map is in wraparound mode:
if (mapView.getWrapAroundMode() == WrapAroundMode.DISABLED) {
// Enable wraparound
mapView.setWrapAroundMode(WrapAroundMode.ENABLE_WHEN_SUPPORTED);
if (!mapView.isWrapAroundEnabled()) {
// wraparound was enabled, but is not supported
}
} else {
// Disable wraparound
mapView.setWrapAroundMode(WrapAroundMode.DISABLED);
}
Normalize geometries
To better understand wraparound, it is helpful to visualize a map as being composed of frames. The portion of a map visible when
wraparound is not enabled is frame 0. Taking an example of a map with the WGS 84 coordinate system, frame 0 has X coordinates
between -180 (west) and +180 (east) longitude.
Adjacent to this frame to the east is frame 1, which extends hypothetically between +180 and +540 longitude. If you have panned across
the map eastwards until you have passed 180, you will be viewing frame 1. Similarly, adjacent to frame 0 to the west is frame -1, which
extends hypothetically between -180 and -540 longitude. The series of frames continues infinitely in both directions.
Longitude values (X coordinates) returned from a map may be real: in the range of -180 and +180 (within frame 0 in other words) or they
may be hypothetical: less than -180 or greater than +180 (outside of frame 0). Here are some examples of geometries that may contain
hypothetical coordinates if wraparound is enabled:
Map extent, returned from MapView.getVisibleArea.
Map locations, returned from MapView.screenToLocation.
The process of converting a geometry so that it contains only real coordinate values is called normalization. Geometries that contain
hypothetical values are not acceptable as inputs to spatial queries, projection, geocoding services, or routing services or for storage in a
geodatabase. Because it may be difficult to determine if a complex shape contains hypothetical coordinate values, it's usually more
efficient to simply normalize all geometry from the map when wraparound is enabled.
You can normalize geometries using normalizeCentralMeridian on the AGSGeometryEngine class.
if (mapView.isWrapAroundEnabled()) {
Geometry normalized = GeometryEngine.normalizeCentralMeridian(mapView.getVisibleArea());
}
The normalized geometry of a map extent that crosses the 180th meridian is a polygon consisting of two rings (split at that meridian).


Save a map
You can create a map by building a brand new map or by opening an existing map, as described in Display a map. Once constructed, the
map includes both properties, for example:
Map title and description
Copyright information
A thumbnail image
Ratings
and map content, for example:
The map's basemap
A list of operational layers
Information about layer visibility and rendering
Layer scale thresholds
The map's initial viewpoints
No matter how you create this map you can save it either as a brand new map or, if you have made any changes to the map, you can
save it back to its original map. This topic describes how to save a brand new map and how to save back any changes you've made to an
existing map.
Save a new map to a portal

When you save a new map to the portal you will create a new portal item with a type of WebMap that has a new unique item ID. The new
portal item will be placed in the My Content area of the user that was authenticated with the portal. When you save the map for the first
time you must provide at least a map title and a loaded portal object. You can also set these properties if you wish.
Tagsan array of tag strings to be used when users search for maps in ArcGIS Online or Portal for ArcGIS.
Foldera portal folder (PortalFolder) in which the map will be placed in My Content. By default the map will be saved to the
user's root folder.
Descriptiona description of the map.
Thumbnailan image ( byte array containing raw data for an image) that will be associated with the portal item and is shown on
the portal item details page in ArcGIS Online or Portal for ArcGIS.
Force save to supported versiona boolean flag to indicate whether or not the map should be saved as the web map version
supported by the API. This may cause data loss, as data unknown to the supported format will be lost when the map is saved.
The following example illustrates saving a new map with the asynchronous saveAsAsync method call, and getting the new PortalItem
from the method's future.
You can use an Android Drawable to create a byte array to use as the thumbnail for the new portal item as shown below.
// Get a Drawable to use as the default thumbnail and convert to byte[].
Drawable drawable = getResources().getDrawable(R.drawable.webmap_thumbnail);
Bitmap bitmap = ((BitmapDrawable)drawable).getBitmap();
ByteArrayOutputStream stream = new ByteArrayOutputStream();
bitmap.compress(Bitmap.CompressFormat.JPEG, 100, stream);
byte[] thumbnailDataArray = stream.toByteArray();
You can use an Android Drawable to create a byte array to use as the thumbnail for the new portal item as shown below.
// Get a Drawable to use as the default thumbnail and convert to byte[].
Drawable drawable = getResources().getDrawable(R.drawable.webmap_thumbnail);
Bitmap bitmap = ((BitmapDrawable)drawable).getBitmap();
bitmap.compress(Bitmap.CompressFormat.JPEG, 100, stream);
byte[] thumbnailDataArray = stream.toByteArray();
Access the map's item properties

After the map saving has completed, the maps portal item property is populated with the brand new portal item properties. You can
access all of the properties and set any of the writeable properties, as you require.

// Report current properties of the PortalItem of the Map.

SimpleDateFormat localDateFormat = new SimpleDateFormat("yyyy-MM-dd", Locale.getDefault());
localDateFormat.setTimeZone(TimeZone.getDefault());
String modifiedDate = localDateFormat.format(map.getItem().getModified());
String itemId = map.getItem().getItemId();
showMessage(String.format("Item '%s' was modified on %s", itemId, modifiedDate));
// Make changes to the properties as required.

map.getItem().setTitle("A brand new title");
map.getItem().setSnippet("A short description to be included in the UI");
If you wish to save any of these properties, call the map's save method as described in the following section.
Share the map

After the map has been saved to the portal, the map is available to share with other portal users. See the share a portal item topic for
more information.
Save changes to an existing web map

If you have opened a map, made changes to the map content or properties, and you want to save changes back to that map, then call the
asynchronous save method on the map. This method, of course, requires that the map has been previously saved to the portal and an
exception will be raised if it has not. If a layer in your map allows users to edit offline, be sure to sync their edits in addition to saving the
map.
// Setting forceSaveToSupportedVersion parameter to true means any unknown data in the map will not be saved.
final ListenableFuture<PortalItem> mapSaveFuture = map.saveAsync(true);
mapSaveFuture.addDoneListener(new Runnable() {
@Override
public void run() {
// Check the result of the save operation.
try {
newMapPortalItem = mapSaveFuture.get();
showMessage("Map changes saved");
// If saving failed, deal with failure depending on the cause...
dealWithException(e);
}
}
});


ArcGIS Runtime provides two main patterns for building offline apps:
Services pattern - If you are building a system that delivers constant updates to your users and synchronizes changes to the
central geodatabases, you should use the Services pattern. In this pattern you use ArcGIS Online or ArcGIS Enterprise to host a
set of tile and feature services that are used through a map (also known as a web map).
Desktop pattern - If you are preparing data in advance and then delivering that to multiple devices for viewing, you can use the
Desktop pattern. In this pattern you use ArcGIS Pro to author a mobile map package and then deliver that to your devices.
For more information on these patterns, see Offline.
You can also take individual layers offline instead of working with a map. For more detail on how to work with individual layers, see the
Create an offline layer topic. The main advantages of working directly with a map instead of layers is that you can share a common map
definition and allow ArcGIS Runtime to handle all the details of how the map is created or stored on the device.
Services Pattern
The Services pattern is based on maps hosted in ArcGIS Online or ArcGIS Enterprise. These web maps use a common map definition
that contains a basemap and a set of operational data. Each map definition may contain symbology and will define how the data is
visualized. These maps can be used across ArcGIS because they adhere to the same map specification. For example, you can create a
web map using ArcGIS Online and use the same map in an ArcGIS Runtime application, ArcGIS Collector, ArcGIS Pro, and so on.
Note: At the 100.1 release the OfflineMapTask supports the following services:
Tiled image raster services that have the exportTiles capability enabled.
Feature services that have sync enabled.
Feature collections.
To create and use a map offline you need to:

1. Create an offline map task
2. Specify the parameters
3. Examine the offline capabilities
4. Generate and download the offline map
5. Open and use the offline map
Create an offline map task

The offline map task (OfflineMapTask) works with maps that are based on a portal item that is hosted either in ArcGIS Online or
ArcGIS Enterprise. You need to provide the target map to the offline map task when it is instantiated by passing either the map or its
portal item as a parameter.
// Load map from a portal item
final Portal portal = new Portal("http://www.arcgis.com");
final PortalItem webmapItem = new PortalItem(portal, "acc027394bc84c2fb04d1ed317aac674");
// Create map and add it to the view

final ArcGISMap myMap = new ArcGISMap(webmapItem);
myMapView = new MapView();
myMapView.setMap(myMap);
// Create task and set parameters

final OfflineMapTask offlineMapTask = new OfflineMapTask(myMap);
Specify parameters
When you create an offline map, use the GenerateOfflineMapParameters class to control options like:
area of interest
scale range
exclude the map's basemap
include the feature's attachments
exclude features from editable feature layers
map's metadata

The set of default parameters ( createDefaultGenerateOfflineMapParametersAsync) is created using the method on

OfflineMapTask. This method also loads the map's portal item and copies its metadata to the itemInfo property, in preparation for
copying it to the offline map. The following code demonstrates how to retrieve and set some of the parameters.
// Create default parameters
final ListenableFuture<GenerateOfflineMapParameters> parametersFuture =
offlineMapTask.createDefaultGenerateOfflineMapParametersAsync(areaOfInterest);
parametersFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
final GenerateOfflineMapParameters parameters = parametersFuture.get();
// Update the parameters if needed
// Limit maximum scale to 5000 but take all the scales above (use 0 as a MinScale)
parameters.setMaxScale(5000);
// Set attachment options

parameters.setAttachmentSyncDirection(GenerateGeodatabaseParameters.AttachmentSyncDirection.UPLOAD);
parameters.setReturnLayerAttachmentOption(GenerateOfflineMapParameters.ReturnLayerAttachmentOption.EDITABLE_LAYERS);
// Request the table schema only (existing features won't be included)
parameters.setReturnSchemaOnlyForEditableLayers(true);
// Update the title to contain the region

parameters.getItemInfo().setTitle(parameters.getItemInfo().getTitle() + " (Central)");
// Override thumbnail with the new image based on the extent

final ListenableFuture<Bitmap> exportImageFuture = mMapView.exportImageAsync();
@Override
public void run() {
try {
Bitmap exportImage = exportImageFuture.get();
Bitmap thumbnailImage = Bitmap.createScaledBitmap(exportImage, 200, 133, false);
thumbnailImage.compress(Bitmap.CompressFormat.JPEG, 50, stream);
byte[] thumbnailBytes = stream.toByteArray();
parameters.getItemInfo().setThumbnailData(thumbnailBytes);
} catch (Exception e) {
e.printStackTrace();
}
}
});
}
}
});
Area of interest
The size of an offline map directly influences the time it takes to generate the offline map and download it to a device. Since the
generation and download speed is directly proportional to the size of the map, you should limit the map's geographical area to just the
area that you need. You can define this area by passing a Geometry object to the areaofInterest property.
Note: It's recommended that the area of interest is in the same spatial reference as the map to be
taken offline. This ensures that all the layers are visible after the offline map is generated.
Scale range
Tiled layers comprise a number of levels of detail. For a particular area of interest, the amount of space, generation time, and
download time increases significantly with every increasing level of detail. It's strongly recommended that you only download the
levels of detail that are relevant for your app. You can control this by setting the minimum and maximum scale parameters (minScale
and maxScale). If possible, choose a maximum scale that is not too zoomed in as this will generate a large number of unnecessary
tiles.
Note: Each service has a limit of how many tiles can be taken offline. It's recommended that you
always set a scale range to avoid hitting this limitation.
Exclude basemap
In some workflows you may want to exclude the basemap from the map and only take the operational layers offline. This provides the
advantage of a smaller file size, faster package generation, and a reduced download time. If you set the includeBasemap property
to false the OfflineMapTask will ignore all the layers included as part of the ArcGISMap's basemap.
If you exclude the basemap from your offline map, you need to add a basemap into your map after it has been loaded. For example, if
you have a workflow where you are sideloading a basemap to the device, there is no need to generate and download a basemap with
every offline map. You just need to add it as a basemap to your offline map.

Include feature attachments
Some feature services have the ability to add attachments (pictures, videos, and other documents) to individual features. Since these
files can be large you must consider your app's offline workflow to determine whether the attachments are needed by the app and
whether attachments need to be synchronized with the service when the app is next online. These two behaviors work in conjunction
with each other and are defined using the returnLayerAttachmentOption and attachmentSyncDirection properties on the
GenerateOfflineMapParameters class.
The return layer attachment property defines which layers should contain attachments in the offline map. The options are:
NONE- None of the layers will contain any attachments.
ALL_LAYERS - All of the layers will have attachments included.
READ_ONLY_LAYERS - Layers that do not have editing enabled will have attachments included.
EDITABLE_LAYERS - Layers that have editing enabled will have attachments included.
The attachment sync direction defines how the attachments are synchronized with the service. The options are:
NONE - Attachments are not synchronized as part of the synchronization operation.
UPLOAD - Attachments are uploaded from client to the service, but changes on the service are not pulled down to the
client.
BIDIRECTIONAL - Attachments are uploaded from client to the service, and changes on the service are pulled down
to the client.
Note: Attachment sync direction is new on ArcGIS Server 10.4 and the value is not applied
when working with services hosted on previous versions of ArcGIS Server.
Here are some workflows that describe how these two parameters affect each other.
Workflow 1 - Download attachments for all layers in the map, allow the user to add/remove attachments from the layers and
then synchronize these changes between the service and the client when online. For example: multiple users are collecting
data on the same area and they want to synchronize all the changes with the centralized services and share these changes
with other people in the field.
returnLayerAttachmentOption.ALL_LAYERS
attachmentSyncDirection.BIDIRECTIONAL
Workflow 2 - Download attachments for all read-only layers and update these layers when online. For example; Users are
offline and viewing a layer of buildings with photos that show how the building looks. If there are any new photos added to the
service these will be downloaded to the client during synchronization when online.
returnLayerAttachmentOption.READ_ONLY_LAYERS
Workflow 3 - Download attachments for editable layers only and upload them to the service when online. For example; Users
are offline and only need to view attachments for editable layers. If there are any read-only layers that provide context for the
map their attachments arent included to the local map. If users remove or add any new attachments these changes can be
synchronized to the service when online.
returnLayerAttachmentOption.EDITABLE_LAYERS
Workflow 4 - Do not download any attachments but allow any new attachments to be uploaded to the service when online. For
example; Users are offline and collecting new attachments in the field but do not need to view existing attachments.
returnLayerAttachmentOption.NONE
attachmentSyncDirection.UPLOAD
This scenario is important for collecting new features in the field. In this case you may want to exclude features from the
editable feature layer.
Exclude features from editable feature layers
If users are collecting new information in the field where they do not need to access previously created features, you can create an
offline map with empty editable feature layers. Do this by setting the GenerateOfflineMapParameters property
returnSchemaOnlyForEditableLayers to true.

Map's metadata
You can get an online map's metadata from the itemInfo property. It includes portal item properties such as the title, description,
short description (snippet, in other words), and thumbnail. This information is populated from the portal item that contains the map.
Get this metadata by creating the GenerateOfflineMapParameters using the
createDefaultGenerateOfflineMapParameters method on the OfflineMapTask. You can override any of these metadata
properties before you take the map offline. For example, if you are creating offline maps of different areas of interest of the same map,
you may want to change the map's title to indicate which area it contains.
You can also create a new OfflineMapItemInfo and manually set all the details.
// Create new item info
final OfflineMapItemInfo itemInfo = new OfflineMapItemInfo();
// Create new thumbnail from the map

final ListenableFuture<Bitmap> exportImageFuture = mMapView.exportImageAsync();
@Override
public void run() {
try {
Bitmap mapImage = exportImageFuture.get();
// scale to thumbnail size
Bitmap thumbnailImage = Bitmap.createScaledBitmap(mapImage, 200, 133, false);
// convert to byte[]
thumbnailImage.compress(Bitmap.CompressFormat.JPEG, 50, stream);
byte[] thumbnailBytes = stream.toByteArray();
stream.close();
// Set values to the itemInfo

itemInfo.setThumbnailData(thumbnailBytes);
itemInfo.setTitle("Water network (Central)");
itemInfo.setSnippet(webmapItem.getSnippet()); // Copy from the source map
itemInfo.setDescription(webmapItem.getDescription()); // Copy from the source map
itemInfo.setAccessInformation(webmapItem.getAccessInformation()); // Copy from the source map
itemInfo.getTags().add("Water network");
itemInfo.getTags().add("Data validation");
// Set metadata to parameters

parameters.setItemInfo(itemInfo);
}
}
});
Note: Upon loading the offline map this metadata is accessible using the ArcGISMap.item
property. In some situations you may want to access the metadata from the mobile map
package without having to load the map itself. You can do this using the
MobileMapPackage.item property.
Examine offline capabilities

There are many things that determine whether a map or its layers and tables can be taken offline. Use the
getOfflineMapCapabilitiesWithParameters method of the offline map task to explore this information. If there are layers or
tables that cannot be taken offline you will get a reason why. For example, if the target map is using an ArcGIS map image layer
(ArcGISMapImageLayer) then an error will be returned stating that the layer type is not supported by the OfflineMapTask.

Although this step is optional it's recommended that you examine these capabilities as you will avoid unnecessary work on the services
side. It's not recommended that you take a map offline unless all of its layers and tables can be taken offline because the map will not
be complete as originally designed. If you do take a map offline you should be aware of which layers or tables are missing from the
offline map.
final ListenableFuture<OfflineMapCapabilities> offlineMapCapabilitiesFuture =
offlineMapTask.getOfflineMapCapabilitiesAsync(parameters);
offlineMapCapabilitiesFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
OfflineMapCapabilities offlineMapCapabilities = offlineMapCapabilitiesFuture.get();
if (offlineMapCapabilities.hasErrors()) {
// Handle possible errors with layers
for (java.util.Map.Entry<Layer, OfflineCapability> layerCapability :
offlineMapCapabilities.getLayerCapabilities().entrySet()) {
if (!layerCapability.getValue().isSupportsOffline()) {
Log.e(TAG, layerCapability.getKey().getName() + " cannot be taken offline.");
Log.e(TAG, "Error : " + layerCapability.getValue().getError().getMessage());
}
}
// Handle possible errors with tables

for (java.util.Map.Entry<FeatureTable, OfflineCapability> tableCapability :
offlineMapCapabilities.getTableCapabilities().entrySet()) {
if (!tableCapability.getValue().isSupportsOffline()) {
Log.e(TAG, tableCapability.getKey().getTableName() + " cannot be taken offline.");
Log.e(TAG, "Error : " + tableCapability.getValue().getError().getMessage());
}
}
} else {
// All layers and tables can be taken offline!
Log.d(TAG, "All layers are good to go!");
}
}
}
});
Generate and download the offline map

To create an offline map you need to run a job that will generate an offline map. You create this job by passing the
GenerateOfflineMapParameters and a destination path on disk to the generateOfflineMapJob method on OfflineMapTask.
Running this job will create an offline map, using the specified parameters, saved to the path on disk. To see more details on how to
work with jobs in general, see the Tasks and jobs topic.
When the GenerateOfflineMapJob is finished, it will return an instance of GenerateOfflineMapResult. The hasErrors
property indicates errors when the layers and tables were taken offline. If this is set to true then there was at least one table or layer
that failed to be taken offline. This indicates whether a more detailed inspection of the results is needed. A layer or table that fails may
not support being taking offline.

If you want to use the offline map immediately, you can use the GenerateOfflineMapResult.offlineMap.
// Create default parameters
final ListenableFuture<GenerateOfflineMapParameters> parametersFuture =
offlineMapTask.createDefaultGenerateOfflineMapParametersAsync(areaOfInterest);
parametersFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
GenerateOfflineMapParameters generateOfflineMapParameters = parametersFuture.get();
// Create and start a job to generate the offline map
final GenerateOfflineMapJob generateOfflineJob =
offlineMapTask.generateOfflineMap(generateOfflineMapParameters, mExportPath);
generateOfflineJob.start();
generateOfflineJob.addJobDoneListener(new Runnable() {
@Override
public void run() {
// Generate the offline map and download it
GenerateOfflineMapResult result = generateOfflineJob.getResult();
if (!result.hasErrors()) {
MobileMapPackage mobileMapPackage = result.getMobileMapPackage();
// Job is finished and all content was generated
Log.e(TAG, "Map " + mobileMapPackage.getItem().getTitle() +
" saved to " + mobileMapPackage.getPath());
// Show offline map in a MapView
mMapView.setMap(result.getOfflineMap());
} else {
// Job is finished but some of the layers/tables had errors
if (result.getLayerErrors().size() > 0) {
for (java.util.Map.Entry<Layer, ArcGISRuntimeException> layerError : result.getLayerErrors().entrySet()) {
Log.e(TAG, "Error occurred when taking " + layerError.getKey().getName() + " offline.");
Log.e(TAG, "Error : " + layerError.getValue().getMessage());
}
}
if (result.getTableErrors().size() > 0) {
for (java.util.Map.Entry<FeatureTable, ArcGISRuntimeException> tableError : result.getTableErrors().entrySet()) {
Log.e(TAG, "Error occurred when taking " + tableError.getKey().getTableName() + " offline.");
Log.e(TAG, "Error : " + tableError.getValue().getMessage());
}
}
}
}
});
}
}
});
Open and use the offline map

When you download an offline map it is saved to disk as a mobile map package. You can open individual offline maps by passing the
download path to the MobileMapPackage constructor. This is the same path that you specified when generating the offline map.
// Create a mobile map package from the offline map
final MobileMapPackage offlineMapPackage =
new MobileMapPackage(mMobileMapPackage);
offlineMapPackage.loadAsync();
offlineMapPackage.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
// Get the title from the package metadata
System.out.println("Title: " + offlineMapPackage.getItem().getTitle());
// Get the map from the package and set it to the MapView
mMapView.setMap(offlineMapPackage.getMaps().get(0));
}
});
Limitations
Advanced symbols are supported only if they are defined in the original service. Any overrides with advanced symbols will result
in empty symbols in an offline map.
Area-of-interest geometries that cross the dateline are not currently supported.
If more than one feature layer in a map refers to the same feature service end point, only one feature layer will be taken offline.
The other feature layers will raise an error.
Desktop Pattern
The desktop pattern is based on mobile map packages created with ArcGIS Pro. A mobile map package (.mmpk file) is a self-contained
package that can contain one or more maps, their associated layers and data, and optionally networks and locators. Mobile map
packages are used across the ArcGIS platform because they adhere to a common package definition.
If you'd like a ready-to-use and regularly updated locator (and network dataset) for your area of interest, you can license StreetMap
Premium data (in MMPK format). For details, see Add StreetMap Premium data.

Open a mobile map package

You can inspect the contents of a mobile map package by constructing the MobileMapPackage class from the path to the package.
You must load the package to access the maps (which may contain networks for routing) and locators for geocoding. Each map within
the mobile map packages will also contain its own item metadata.
Open a mobile map

Once you have determined which map to use, you can pass it to the map view to be displayed. This map is no different from a web map
from ArcGIS Online or ArcGIS Enterprise. The map contains operational layers, a basemap and optionally bookmarks and other data.
For additional details on creating mobile map packages and using them in your app, see Create a map object from a mobile map
package.
Mobile map capabilities

Mobile map packages can contain the following layer types:
Feature layers from feature classes - these get consolidated into a geodatabase for each workspace type and are accessed as
geodatabase feature tables. These can include definition expressions.
Vector tiled layers from vector tile caches - these get packaged as a vector tile package and are accessed as an ArcGIS vector
tiled layer
Basemaps created from multiple feature layers - all feature layers inside the ArcGIS Pro basemap layer collection get
consolidated into a single mobile basemap layer. These compressed and high performance vector layers maintain the full GIS
data for your features yet allow you to use them as basemap layers.
Limitations
Some data and map configurations from ArcGIS Pro are not fully supported inside mobile map packages. For example:
Label placement - The ArcGIS Runtime label placement engine differs from that used in ArcGIS Pro. Therefore, label positions
and visibility can appear different. The following label options in ArcGIS Pro are converted to label properties inside mobile map
packages:
Allow overrun options - these result in an allow overrun true/false property.
Label placement options, including place overlapping - these result in a deconfliction strategy property of none, static or
dynamic as well as a label placement property which is used as the initial preferred location of the label. If dynamic
deconfliction is being used, then the label will move clockwise from this position to find clear space.
Duplicate labels and label largest part options - these result in a multipart property of label per segment, label largest, or
label per part
Line connection options - these result in a line connection property of none, minimize labels or unambiguous labels
Label priority ranking
Remove duplicate options, including distance - these result in a remove duplicate property of none, all, or features type,
as well as a remove duplicate distance property.
Repeat label options, including distance - these results in a repeat label property of true or false as well as a repeat
distance property
Stacking label options, including alignment - these result in a stack label property of true or false as well as a stack
alignment property of dynamic (assign the alignment depending upon the label's position with respect to its feature) or
text symbol (follow the alignment specified in the text symbol).
Popups - Popup definitions on layers are not currently supported
Scenes - Adding scenes to mobile map packages is not supported
Analyzer restrictions - There are also various restrictions applied through analyzers when creating a mobile map package. Some
of the more important items are listed below:
In each map, all basemap layers must share the same workspace
Maps cannot be packaged with operational layers and basemap layers that reference the same workspace.
The network dataset must be in a geodatabase of version 10 or greater.
Network attributes cannot contain script evaluators.

The spatial reference of the map must match the spatial reference of the vector tile layer.
A layer's extent must intersect the map
Layer datasets cannot contain custom features or class extensions.
Live traffic is not supported.
The network should have length, time and default cost attributes to be able to successfully generate directions.
Network field names cannot be longer than 31 characters.

Create an offline layer

To create an offline layer, you can use either the Services pattern, where you use ArcGIS Online or ArcGIS Enterprise to host a set of tile
and feature services that are enabled for offline use, or you can use the Desktop pattern, where you author packages in ArcGIS Pro for
sideloading onto your device, or you can create offline layers from mobile geodatabases and tile caches and add them to your own offline
map.
Instead of taking layers offline individually you can also take a whole map offline. For more details on how to take a map offline, see
Create an offline map. The main advantage of working directly with layers instead a map is that you can control everything at a granular
level. You can decide when and how individual offline layers are created, used and synchronized.
Services Pattern
The services pattern is best for supporting numerous users who share data. This pattern allows multiple offline users to edit the same data
layer and synchronize edits later, when online.
For operational data, you can use a sync-enabled feature service from ArcGIS Online or ArcGIS Enterprise to create a mobile
geodatabase for offline use. Through the synchronization process, you can control whether a user can upload their edits, download edits
made by others, or both. This allows the app to maintain an up-to-date view of the data. When more than one user is editing the same
feature and the edits conflict, the last edit synchronized to the service overrides those synchronized earlier. In a pre-planned workflow, you
generate the geodatabase once and load it onto many of your users' devices, thus reducing the number of generate requests to the
server. The pre-planned workflow requires you to register the geodatabase.
For basemap data, you can create raster tile caches on-demand from both ArcGIS tiled map services and ArcGIS Online basemaps.
These caches can be stored locally and accessed whilst offline.
Operational data from a sync-enabled feature service

To continue viewing, interacting with and editing features you can take specific features and feature layers offline by storing them in
geodatabase feature tables within a mobile geodatabase. The only limitations to this process are that the feature service must be from
ArcGIS for Server 10.2.2 or later, or from a service hosted on ArcGIS Online, and the feature service must have sync enabled
capabilities (allow disconnected editing with synchronization).
You can use a pre-existing feature service or create features services for your own data. To enable sync for a feature service:
In ArcGIS Online: you must edit the feature service item and check the Sync check box.
In ArcGIS Server: see Prepare data for offline use in the ArcGIS Server documentation.
To create a mobile geodatabase for offline use you need to:
1. Specify the geodatabase parameters, such as the area of interest.
2. Create the geodatabase using the methods on the GeodatabaseSyncTask. The geodatabase is populated with the relevant
features (within the area of interest, for example) and downloaded to the device.
3. Register the geodatabase if you are using a pre-planned workflow.

Specify the geodatabase parameters
When creating a mobile geodatabase, you can supply parameters to define:

Which layers to include in the mobile geodatabase.
The spatial reference of the mobile geodatabase.
The geographical area of interest. You typically supply the area of interest as an extent (envelope, in other words) but point,
line, and polygon (including multipart) geometries are also supported. This allows you to create more detailed areas of
interest. Regardless of the geometry, any features that intersect with the supplied area of interest are extracted.
A subset of features to copy to the geodatabase. You can provide an expression that filters features using attribute values,
such as ZONE = 'COM'.
The synchronization model for the layers. The synchronization model controls how edits made to the mobile geodatabase are
applied back to the feature service during synchronization. The model supported is defined by the data that was used to
create the sync-enabled feature service. If the data is non-versioned, the synchronization model is per-layer. This is the most
flexible model, allowing you to synchronize on a layer-by-layer basis, based on the layers you specify. If the data is versioned,
the synchronization model is per-geodatabase. This synchronizes the entire geodatabase, including all layers and tables at
once.
Whether to include feature attachments in the mobile geodatabase and whether they can be uploaded during synchronization.
You can construct a default set of these parameters (GenerateGeodatabaseParameters) using the
createDefaultGenerateGeodatabaseParametersAsync method on the GeodatabaseSyncTask. The default values take
into account the capabilities supported by the ArcGIS feature service and the data it contains. You can update these parameters
before creating the geodatabase.

Create the geodatabase
Use the GeodatabaseSyncTask class to initiate a request for a geodatabase from a sync-enabled feature service for your area of
interest. The method returns a GenerateGeodatabaseJob which once succeeded will provide access to the geodatabase.
private static void createOfflineData() {
// create a new GeodatabaseSyncTask to create a local version of feature service data
String featureServiceUrl = "http://sampleserver6.arcgisonline.com/arcgis/rest/services/Sync/SaveTheBaySync/FeatureServer";
final GeodatabaseSyncTask gdbSyncTask = new GeodatabaseSyncTask(featureServiceUrl);
// define an extent for the features to include

Envelope extent = mMapView.getCurrentViewpoint(Viewpoint.Type.BOUNDING_GEOMETRY).getTargetGeometry().getExtent();
// get the default parameters for generating a geodatabase
ListenableFuture<GenerateGeodatabaseParameters> generateGdbParamsFuture = gdbSyncTask.createDefaultGenerateGeodatabaseParametersAsync(extent);
generateGdbParamsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
GenerateGeodatabaseParameters generateGdbParams = generateGdbParamsFuture.get();
// set the sync model to per layer

generateGdbParams.setSyncModel(SyncModel.PER_LAYER);
// define the layers and features to include
int marineLayerId = 0;
int birdsLayerId = 1;
String dolphinsOnlyWhereClause = "type = 11";
// Clear and re-create the layer options
generateGdbParams.getLayerOptions().clear();
generateGdbParams.getLayerOptions().add(new GenerateLayerOption(marineLayerId, dolphinsOnlyWhereClause));
generateGdbParams.getLayerOptions().add(new GenerateLayerOption(birdsLayerId));
// do not return attachments
generateGdbParams.setReturnAttachments(false);
// create the generate geodatabase job, pass in the parameters and an output path for the local geodatabase
final GenerateGeodatabaseJob generateGdbJob = gdbSyncTask.generateGeodatabaseAsync(
generateGdbParams, mExportPath);
// handle the JobChanged event to check the status of the job

generateGdbJob.addJobChangedListener(new Runnable() {
@Override
public void run() {
onGenerateGdbJobChanged(generateGdbJob);
}
});
// start the job and log the job ID

generateGdbJob.start();
Log.d(TAG, "Submitted job #" + generateGdbJob.getServerJobId() + " to create local geodatabase");
}
}
});
}
// handler for the JobChanged event
private static void onGenerateGdbJobChanged(GenerateGeodatabaseJob job) {
// log error (if any)
if (job.getError() != null) {
Log.d(TAG, "Error creating geodatabase: " + job.getError().getMessage());
return;
}
// check the job status
if (job.getStatus() == Job.Status.SUCCEEDED) {
// if the job succeeded, add local data to the map
addLocalLayerToMap();
} else if (job.getStatus() == Job.Status.FAILED) {
// log failure
Log.d(TAG, "Unable to create local geodatabase.");
System.out.println();
} else {
// job is still running, log last message
Log.d(TAG, job.getMessages().get(job.getMessages().size() - 1).toString());
}
}
Your geodatabase is now on the local machine or device.
Register the geodatabase in a pre-planned workflow
If you want to generate the geodatabase once and load copies of it onto a number of devices then you must register the geodatabase
copy on each device that uses one. This pre-planned workflow and has the following benefits:
Allows you to control which maps and data your users can access by pre-loading them onto your users' devices.
Allows you to schedule the geodatabase generation for off-peak hours.
Reduces load on the server. Multiple clients aren't generating a geodatabase for the same area because you've generated it
for them.
For details and important tips on registering and unregistering geodatabases, see Register a geodatabase in a pre-planned workflow.

Basemap data from tiled map services

An offline copy of tiled map services (raster tiles) can be requested so that a basemap is available when the app is working in an offline
environment. These copies can be downloaded in the form of a tile package (a .tpk file) using the ExportTileCacheTask class. The
map service used for this operation must support the creation of an offline tile cache; specifically, it must support
the exportTiles operation that appears at the bottom of the service's HTML page.
When requesting a tile cache, define the following properties:
The levels of detail (also known as LODs) to include in the tile cache
An area of interest (this can be a polygon geometry or an envelope)
A spatial reference for the tile cache (defined on the extent geometry of the cache)
The compression quality of the tile package (this affects its file size)
You can construct a default set of these parameters (ExportTileCacheParameters) by providing an area or interest and desired
scale thresholds to the createDefaultExportTileCacheParametersAsync method on the ExportTileCacheTask. This
asynchronous method provides initialized parameters for exporting tiles. It will calculate the levels of detail (LODs) required based on
the specified min and max scale and the tiling scheme of the service.
When creating an offline tile cache from a tiled service, consider the following:
The export tiles operation used to generate tile caches is only available with services hosted on ArcGIS 10.2.1 for Server or
later.
Estimation of tile cache size is not available on ArcGIS Online hosted tiled services.
The time required to create a tile cache varies depending on the extent requested, the number of levels requested, the network
connection speed, and so on. Use the estimateTileCacheSize method on the ExportTileCacheTask class which
returns an EstimateTileCacheTaskJob to get the approximate size of a tile cache for a specific set of parameters. Try
generating a smaller tile cache to get an idea of how long caching will take when planning a large offline data capture event.
There is a limit to the number of tiles you can generate in a single request. When generating a tile cache from an ArcGIS Online
basemap, there is a limit of 100,000 tiles per request. Read more on this in the ArcGIS REST API Documentation.
Organizations that use their own ArcGIS Server to host an offline tile cache can configure the server's
maxExportTilesCount via the admin account to change the default limit of 100,000 tiles.
Desktop Pattern
You can use ArcGIS Pro or ArcGIS Desktop to generate operational layers, basemaps, scene layers, locators and networks for use in
ArcGIS Runtime. This workflow requires that you take this content, build your own maps and instantiate your own tasks to work with the
locators and networks. If you'd like a ready-to-use and regularly updated locator (and network dataset) for your area of interest, you can
license StreetMap Premium data (in MMPK format). For details, see Add StreetMap Premium data.
Create a mobile geodatabase for operational layers from ArcMap

To generate a geodatabase use the Share as > ArcGIS Runtime Content menu item as described in the ArcGIS help topic Creating
ArcGIS Runtime content. This is available with ArcGIS 10.2.1 for Desktop or later.
Create a raster tile basemap

You can use ArcGIS Pro or ArcMap to create a raster tile basemap. For more details on how to set the format, tiling schemes, and
levels of detail see:
ArcMap: How to create a tile package and About tile packages
ArcGIS Pro:Create Map Tile Package.
After you sideload the tile package onto your device's file system, you can add it as a map's basemap.
Create a vector tile basemap

ArcGIS Pro allows you to author a map for vector tile creation and create a vector tile package using a geoprocessing tool. You can add
this local vector tile package (.vtpk) as a vector tiled layer (ArcGISVectorTiledLayer) to your ArcGIS Runtime app and create a
basemap from it.

Create a scene layer package and local elevation source

ArcGIS Pro allows you to create a scene layer package using a geoprocessing tool. You can add this local scene layer package
(.slpk) as a scene layer (ArcGISSceneLayer) to your ArcGIS Runtime app and add it to a Scene.
To take this scene layer offline your app can define an elevation surface by consuming local raster datasets on the client. The following
formats are supported for creating a local elevation source:
ASRP/USRP
CIB1, 5, 10
DTED0, 1, 2
GeoTIFF
HFA
HRE
IMG
JPEG
JPEG 2000
NITF
PNG
RPF
SRTM1, 2

Mobile map package

Mobile map packages make it easy and fast for you to share your maps and basemaps with mobile applications such as Navigator for
ArcGIS 2.0 or later, and those developed with ArcGIS Runtime SDKs, starting with Quartz Beta 2.
A mobile map package consolidates maps or basemaps into a single file (.mmpk) that can be shared with your ArcGIS organizational
account or downloaded directly to your mobile device. Supported layer types within the maps and basemaps, along with their data, are
also combined in the package. The mobile map package format is optimized for modern mobile devices and can run on any platform
supported by ArcGIS Pro or the ArcGIS Runtime. Basemaps and their layers are compressed further to ensure they perform well on
devices. Developers creating apps using ArcGIS Runtime SDKs will see operational layers as well as just one non-editable basemap layer
for each basemap in a map, even if a basemap layer is created from multiple layers in ArcGIS Pro.
Common uses for mobile map packages include navigation and geocoding. Mobile map packages created for navigation can contain
private assets, custom asset locators, and custom road networks. In ArcGIS Pro 1.2 or later, you can add assets to a map, create asset
locators, build roads, and then combine all of this data into one file using the Create Mobile Map Package geoprocessing tool. This
package can then be shared using the Share Package geoprocessing tool with your ArcGIS organizational account, so users can
download or copy it to their devices and open it in Navigator or your own app, to search for and get directions to private assets on custom
roads.
Learn how to use the Share Package and Create Mobile Map Package tools in this topic. For more details about these tools, such as
usage, syntax, and code samples, see Share Package and Create Mobile Map Package.
Create a mobile map package

Note: For a network dataset to support mobile map packaging, it must meet certain requirements.
See Create Mobile Map Package for details. Mobile map packages only support simple
features, tables, relationship classes, locators, and network datasets. Mobile map packages
created in ArcGIS Pro for use in apps created with ArcGIS Runtime SDKs currently only
support the following layer types: feature layers from feature classes, and vector tiled layers
from previously created .vtpk files.
1. In ArcGIS Pro, on the Analysis tab in the Geoprocessing group, click Tools .
The Geoprocessing pane appears.
2. In the Geoprocessing pane, type Create Mobile Map Package and click this tool in the Search Results.
3. In the Input Map field, add the maps or basemaps to include in the package.
By default, the Create Mobile Map Package tool uses the current map as the Input Map.
Note: You can add multiple maps and basemaps into the package.
4. In the Output File field, specify an output location and name for the package.
5. In the Input Locator field, choose the address locator you want to use.
If you created a locator in this session, it will appear first in the drop-down menu. If you created it in another session, you will
have to browse for it.
6. Zoom to your desired map extent.
7. Set Extent to Current Display Extent.
Current Display Extent changes to As Specified Below in the drop-down menu, and the minimum and maximum values of the
extent appear.
8. If you would like the package in your mobile application to match the current extent in ArcGIS Pro, check Clip Features.
Everything in the map that is outside the current extent will be clipped. This further reduces the package size, making it even
faster and easier to share.
9. Edit the following fields as you see fit: Title, Summary, Description, Tags, Credits, and Use Limitations.
10. Click Run .

Note: You might receive a message that the Create Mobile Map Package tool completed with
the warning Live traffic is not supported when publishing to runtime.
This means that live traffic is only supported when the data is published as a service. If
you are creating this mobile map package for an app that works in disconnected
environments and does not use services, such as Navigator, you do not need to be
concerned with this warning.
The tool saves the .mmpk file to the output location you specified in step 4 of this section. You can share this file by following the
previous section or using common sharing methods.
For more details about how to create a mobile map package specifically for Navigator, see the Prepare maps tab in the Navigator help
system. For details about how to use a mobile map package for your own apps, see Create a map object from a mobile map package in
the Android and iOS ArcGIS Runtime SDK help systems.
Share a mobile map package

1. In ArcGIS Pro, on the Analysis tab in the Geoprocessing group, click Tools .
The Geoprocessing pane appears.
2. In the Geoprocessing pane, type Share Package and click this tool in the Search Results.
3. For the Input Package field, add the mobile map package (.mmpk) you created.
4. Provide information for the following fields: Summary, Tags, and Credits.
5. Determine who you would like to share the package with.
Tip: If you decide to share the package with specific groups in your organization, make sure
that your users belong to that group.
6. Click Run .
A message appears, indicating that the Share Package tool completed successfully. Users can now access it from their ArcGIS
organizational account and open it in their mobile apps.

Display a scene
Add 3D visualization to your app to view data in its near real-world perspective. To add 3D visualization, assign a scene to a scene view,
similar to the way you assign a map to a map view for 2D visualization. A scene view, like its 2D equivalent, the map view, gives you the
ability to zoom and pan around the scene.
The data you visualize in your 3D app is defined by the scene class. The types of data you can display in a scene include:
Basemaps, which can be draped over surface layers. A surface layer contains elevation information. A surface layer can come in
many forms, for example, local raster data such as a DEM or DTED or from an ArcGIS image service.
Operational layers, which can include feature layers or scene layers. Scene layers represent built and natural 3D content such as
buildings, trees, valleys, and mountains and can be accessed as scene services or local scene layer packages.
Surface layers, which define the elevation information of the 3D visualization.
Display a scene using a scene service

1. Create a scene that contains a basemap and a scene service.
// create a scene and add a basemap to it
ArcGISScene scene = new ArcGISScene();
scene.setBasemap(Basemap.createImagery());
// add a scene layer

final String sceneLayerURL = "http://tiles.arcgis.com/tiles/P3ePLMYs2RVChkJx/arcgis/rest/services/Buildings_Brest/SceneServer/layers/0";
ArcGISSceneLayer sceneLayer = new ArcGISSceneLayer(sceneLayerURL);
scene.getOperationalLayers().add(sceneLayer);
2. To display the scene, assign it to a scene view that you create.

// create SceneView from layout
mSceneView = (SceneView) findViewById(R.id.sceneView);
mSceneView.setScene(scene);
3. Run the project and it should resemble the following image. You can use gestures to pan and zoom around the scene. For more
information on navigating the scene, see the Navigate a scene view topic.
You may want to set the camera (set an initial viewing position) or add graphics.
Display a scene using a 3D surface

Add a surface layer to a scene with a basemap for 3D visualization in your app.

1. Create a scene and assign it to a scene view.

// create SceneView from layout
mSceneView = (SceneView) findViewById(R.id.sceneView);
mSceneView.setScene(scene);
2. Add an elevation surface and apply it to the scene.

// create an elevation source, and add this to the base surface of the scene
ArcGISTiledElevationSource elevationSource = new ArcGISTiledElevationSource(
http://elevation3d.arcgis.com/arcgis/rest/services/WorldElevation3D/Terrain3D/ImageServer);
scene.getBaseSurface().getElevationSources().add(elevationSource);
You can use gestures to pan and zoom around the scene. For more information on navigating the scene, see the Built-in navigation
section of the "Navigate a scene view" topic.
Set the camera

The position you view the scene from is defined by a camera class. When you create a new camera class, you must define the following
properties:
3D locationLatitude, longitude, and elevation
HeadingDirection the camera is pointing towards
PitchUp and down angle of camera
For example, to point the camera to toward the Snowdon mountainside, as shown in the following code snippet and image, use these
values:
For 3D location, use 53.06 latitude, -4.04 longitude, 1289 metres above sea level
For heading, use 295 degrees
For pitch, use 71 degrees
// add a camera and initial camera position (Snowdonia National Park)
Camera camera = new Camera(53.06, -4.04, 1289.0, 295.0, 71, 0.0);
sceneView.setViewpointCamera(camera);

Now you have a new camera you can apply to your scene view. You can apply it immediately using setViewpointCamera as shown in
the code below, or the camera can be animated to the new position using one of the asynchronous methods.

Navigate a scene view

You can navigate a scene view (a 3D map):
Using built-in navigation (described on this page), such as panning, zooming, and changing pitch
By programmatically changing camera position
Built-in navigation
The scene view has a number of built-in gestures that allow you to navigate a scene (3D) using the gestures. The tables below defines
these gestures:
Navigation User Action

Zoom in Two-pointer pinch
Single-pointer double-tap
Zoom out Two-pointer pinch
Two-pointer single-tap
Continuous zoom in / out Single-pointer double-tap, ending in a vertical up/down drag
Move/Pan Single-pointer drag or flick
Tilt the scene Two-pointer up-down drag (vertically aligned on the scene view)
Rotate the scene Two-pointer rotate
Programmatically change camera position

Your applications can programmatically navigate a 3D scene by creating a new camera and setting it to the scene view. A camera defines
the location from which you are viewing the scene.
The camera is shown in this image for illustration purposes; when you set camera settings (location, pitch), think of the camera class a real-life camera you're adjusting the position of.
Set the camera

For example, to point the camera to toward the Snowdon mountainside, as shown in the following code snippet and image, use these
values:
For 3D location, use 53.06 latitude, -4.04 longitude, 1289 metres above sea level
For heading, use 295 degrees
For pitch, use 71 degrees
// add a camera and initial camera position (Snowdonia National Park)
Camera camera = new Camera(53.06, -4.04, 1289.0, 295.0, 71, 0.0);

Now you have a new camera you can apply to your scene view. You can apply it immediately using setViewpointCamera as shown
in the code below, or the camera can be animated to the new position using one of the asynchronous methods.

Add graphics to a scene view

Add graphics to a scene view (a 3D map) when you want to:
Display temporary data, such as data that represents real-world objects moving at fast speeds (for example, a fleet of airliners)
Display data that doesn't share a common geometry type (such as point, line, or polygon) and doesn't share a common set of
attribute fields
Display graphics at a location above sea level or above the surface layer (if your data includes z-values)
This temporary data is stored in-memory, client side.
Adding graphics to scenes (3D) follows the same steps as adding graphics to maps (2D) with these additional considerations:
Surface placement modes
3D-specific symbols
Renderer properties for 3D
Add graphics to a scene view

Adding graphics to scenes (3D maps) is the same as adding graphics to maps (2D)you add a graphics overlay to the scene view then
you add graphics to that graphics overlay. In 3D, you can add graphics such as points, lines, polygons, and 3D marker symbols, all into
the same graphics overlay or into multiple graphics overlays.
The following code snippet shows how to create a graphics overlay and add it to a scene view. For additional details on adding graphic
overlays to a map (which also applies to scenes), see Add graphic overlays to your app. For details on adding graphics to a graphics
overlay, see Add graphics and text to graphics overlays (also applies to scenes).
// add graphics overlay(s)
GraphicsOverlay graphicsOverlay = new GraphicsOverlay();
graphicsOverlay.getSceneProperties().setSurfacePlacement(LayerSceneProperties.SurfacePlacement.ABSOLUTE);
sceneView.getGraphicsOverlays().add(graphicsOverlay);
Surface placement modes

For a graphics overlay, you can specify a surface placement mode or use the default of DRAPED. These modes control how the z-value of
your geometry is used when your graphics are drawn.
DRAPED(default) Graphics are drawn on the surface. The z-value has no effect.
ABSOLUTEGraphics are drawn at a height using the z-value referenced from above the globe skin (sea level).
RELATIVEGraphics are drawn at a height using the z-value referenced from above the surface layer.
The following code shows three points drawn in graphics overlays in the three different surface placement modes. The red graphic is
draped on the surface, the blue graphic is drawn in absolute mode, and the green in relative mode
// create overlays with elevation modes
GraphicsOverlay drapedOverlay = new GraphicsOverlay();
drapedOverlay.getSceneProperties().setSurfacePlacement(SurfacePlacement.DRAPED);
sceneView.getGraphicsOverlays().add(drapedOverlay);
GraphicsOverlay relativeOverlay = new GraphicsOverlay();
relativeOverlay.getSceneProperties().setSurfacePlacement(SurfacePlacement.RELATIVE);
sceneView.getGraphicsOverlays().add(relativeOverlay);
GraphicsOverlay absoluteOverlay = new GraphicsOverlay();
absoluteOverlay.getSceneProperties().setSurfacePlacement(SurfacePlacement.ABSOLUTE);
sceneView.getGraphicsOverlays().add(absoluteOverlay);
// create a text symbol for each elevation mode

TextSymbol drapedText = new TextSymbol(10, "DRAPED", 0xFFFFFFFF, HorizontalAlignment.LEFT,
VerticalAlignment.MIDDLE);
TextSymbol relativeText = new TextSymbol(10, "RELATIVE", 0xFFFFFFFF, HorizontalAlignment.LEFT,
TextSymbol absoluteText = new TextSymbol(10, "ABSOLUTE", 0xFFFFFFFF, HorizontalAlignment.LEFT,
// create point for graphic location

Point point = new Point(-4.04, 53.06, 1000, sceneView.getSpatialReference());
SimpleMarkerSymbol redSymbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, 0xFFFF0000, 10);
SimpleMarkerSymbol greenSymbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, 0xFF00FF00, 10);
SimpleMarkerSymbol blueSymbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, 0xFF0000FF, 10);
// add the point graphic and text graphic to the corresponding graphics
// overlay
drapedOverlay.getGraphics().add(new Graphic(point, redSymbol));
drapedOverlay.getGraphics().add(new Graphic(point, drapedText));
relativeOverlay.getGraphics().add(new Graphic(point, greenSymbol));

relativeOverlay.getGraphics().add(new Graphic(point, relativeText));
absoluteOverlay.getGraphics().add(new Graphic(point, blueSymbol));

absoluteOverlay.getGraphics().add(new Graphic(point, absoluteText));
The graphics render at different heights even though they all use the same z-value.

3D-specific symbols
Graphics in a 3D graphics overlay can use any of the symbols discussed in Add graphics and text to graphics overlays. You can also add:
A number of geometric-shape-based symbols such as cones, spheres, tetrahedrons
Model 3D symbols

Add shape-based symbols
The following code snippet shows how to create a sphere symbol and render it using a point geometry in a graphic.
// sphere symbol
SimpleMarkerSceneSymbol sphere = new SimpleMarkerSceneSymbol(SimpleMarkerSceneSymbol.Style.SPHERE, 0xCC880000, 3000,
3000, 3000, SceneSymbol.AnchorPosition.CENTER);
// sphere point
Point spherePoint = new Point(-4.04, 53.16, 1000);
// add graphic
Graphic sphereGraphic = new Graphic(spherePoint, sphere);
graphicsOverlay.getGraphics().add(sphereGraphic);
Add model symbols

A model symbol is used to provide a realistic three-dimensional visualization to symbolize scene features. These models define the
geometry and surface textures of real-world items such as aircraft. Create a ModelMarkerSymbol using a 3D model file, passing the
path to the file and a scale factor to the model symbol constructor. The supported model file types include Collada (.dae), 3D Max
(.3ds), Blender 3d (.blend), and the formats listed in the Open Asset Import Library (Assimp). Depending on the model file's default
orientation, you may have to rotate the symbol to get your model in the desired orientation.
Create these model symbols using the ModelSceneSymbol class as follows:

// load the plane's 3D model symbol
String modelURI = new File("path/to/folder", "file.dae").getAbsolutePath();
ModelSceneSymbol plane3DSymbol = new ModelSceneSymbol(modelURI, scaleOfPlane);
plane3DSymbol.loadAsync();
// create the graphic

graphicsOverlay.getGraphics().add(new Graphic(new Point(0, 0, 0, SpatialReferences.getWgs84()), plane3DSymbol));

Distance composite symbols
While model symbols closely resemble the real-world object they represent when viewed close up, when you zoom away from them,
the symbols gets smaller until they're no longer visible. If you want to see the location of your graphics at any distance from the
camera, use distance composite symbols. These symbols allow you to use different symbols depending on the distance the graphic is
from the camera.
The code snippet below the following images shows how to set up a distance composite symbol similar to the one shown in the
images.
When the camera is far away from the point, a red simple marker symbol displays.
As you zoom closer to the point, the symbol renders as a cone pointing in the aircraft's direction of travel.
When viewed even closer, the point displays as a model symbol, which is appropriate at this distance from the camera.
// set up the different symbols

int red = 0xFFFF0000;
SimpleMarkerSymbol circleSymbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, red, 10);
SimpleMarkerSceneSymbol coneSymbol = SimpleMarkerSceneSymbol.createCone(red, 10, 10);
coneSymbol.setPitch(-90);
String modelURI = new File("path/to/file.dae").getAbsolutePath();
ModelSceneSymbol modelSymbol = new ModelSceneSymbol(modelURI, 1.0);
modelSymbol.loadAsync();
// set up the distance composite symbol
DistanceCompositeSceneSymbol compositeSymbol = new DistanceCompositeSceneSymbol();
compositeSymbol.getRangeCollection().add(new DistanceCompositeSceneSymbol.Range(modelSymbol, 0, 100));
compositeSymbol.getRangeCollection().add(new DistanceCompositeSceneSymbol.Range(coneSymbol, 100, 1000));
compositeSymbol.getRangeCollection().add(new DistanceCompositeSceneSymbol.Range(circleSymbol, 1000, 0));
// create graphic
Point aircraftPosition = new Point(-2.708471, 56.096575, 5000, SpatialReferences.getWgs84());
Graphic aircraftGraphic = new Graphic(aircraftPosition, compositeSymbol);
// add graphic to graphics overlay
graphicsOverlay.getGraphics().add(aircraftGraphic);

Renderer properties for 3D

As with graphics overlays in 2D, in 3D you can use various renderers, such as simple renderers and unique value renderers, to control the
symbology using the attributes on your graphics. For details, see Symbols and renderers.
When using renderers in 3D, you can set properties to define rotation expressions or extrusion expressions.
The code snippet below shows how to set the heading, pitch, and roll of a graphic's attributes.
// create renderer to handle updating plane rotation using the GPU
SimpleRenderer renderer3D = new SimpleRenderer();
renderer3D.setRotationType(RotationType.GEOGRAPHIC);
Renderer.SceneProperties renderProperties = renderer3D.getSceneProperties();
renderProperties.setHeadingExpression("[HEADING]");
renderProperties.setPitchExpression("[PITCH]");
renderProperties.setRollExpression("[ROLL]");
graphicsOverlay.setRenderer(renderer3D);
Extrusion expressions can also be set up for polygons in a graphics overlay. The graphics shown in the following image have been
extruded on population attribute pop2000.
The following code snippet shows how to define the simple renderer and set extrusion properties:
// set renderer with extrusion property
SimpleRenderer renderer = new SimpleRenderer();
SceneProperties renderProperties = renderer.getSceneProperties();
renderProperties.setExtrusionMode(SceneProperties.ExtrusionMode.BASE_HEIGHT);
renderProperties.setExtrusionExpression("[HEIGHT]");
graphicsOverlay.setRenderer(renderer);

Follow a graphic in a scene view

Graphics can represent dynamic objects in the scene. A service might provide near real-time locations for a fleet of vehicles, for example.
Your device might read GPS information and display your current location as a graphic, or you might simply animate graphics on the
scene view by reading a hard-coded list of geographic coordinates. For these use cases, there are two ways in which your user might
want to visualize moving graphics in a scene view. They might want to view several graphics at once as they interactively explore the
entire scene, or they might want to continuously focus the camera relative to a specific element and track it as it moves through the scene.
Your app might even allow the user to interact both ways, sometimes selecting a particular graphic to follow, and then switching to explore
the entire scene.
Visualize dynamic graphics in a scene

A scene view uses the concept of a camera and a focal point to display data in three dimensions. The camera represents the location of
the observer in three-dimensional space (x, y, z), and the camera's focal point is the location that intersects the camera's line of sight. By
default, a scene view allows the user to interactively change the camera position to center on a focal point of their choice. However, you
may need to set the camera's focal point relative to a specific graphic or location in the scene view. In the case of a moving graphics, you
may want to continuously update the camera to maintain focus on a particular graphic as it moves through the scene.
To simplify the code required to keep the camera in sync with a moving graphic, ArcGIS Runtime provides a CameraController to
implement this behavior.
Note: A camera controller does not honor obstacles (such as terrain, extruded buildings, or other
graphics) as it follows a graphic. In other words, the camera does not move to avoid such
obstacles as it follows a graphic.
Prepare your graphics

To ensure your graphics can be tracked and properly displayed using the method described in this topic, follow these guidelines:
Graphics you want to follow should have attributes to store the current heading, pitch, and roll.
Each graphics overlay containing graphics you want to follow should have a renderer assigned.
The graphics overlay renderer should have heading, pitch, and roll expressions defined in the renderer scene properties. These
expressions should use the corresponding graphic attributes.
The graphics overlay that contains the graphic to follow must be added to the scene view.
Note: Renderer scene property expressions can use hard-coded values, but they usually contain
the name of an attribute. For example, the expression [heading] + 3.5 indicates that the
renderer will add 3.5 to the value of the attribute named heading for each graphic in the
graphics overlay. When referring to attributes in an expression, the attribute name should be
in square brackets, such as [heading].
You may need to adjust the heading, pitch, and roll properties on your symbol to make sure its initial appearance is correct.
The following example creates a graphics overlay with the appropriate scene properties, adds a single point graphic to it, and then adds
it to the scene view. The graphic is now ready to follow in the scene.
// create a new simple renderer and apply the scene properties that use the corresponding graphic attribute names
SimpleRenderer graphicsRenderer = new SimpleRenderer();
graphicsRenderer.getSceneProperties().setHeadingExpression("[Heading]");
graphicsRenderer.getSceneProperties().setPitchExpression("[Pitch]");
graphicsRenderer.getSceneProperties().setRollExpression("[Roll]");
// create a new graphics overlay, define absolute placement of graphics, and apply the renderer
GraphicsOverlay followGraphicsOverlay = new GraphicsOverlay();
followGraphicsOverlay.getSceneProperties().setSurfacePlacement(SurfacePlacement.ABSOLUTE);
followGraphicsOverlay.setRenderer(graphicsRenderer);
// create a plane graphic to track

Point startPoint = new Point(-117.00, 31.50, 2000, SpatialReferences.getWgs84());
Graphic planeGraphic = new Graphic(startPoint, planeSymbol);
planeGraphic.getAttributes().put("Heading", 270.0);
planeGraphic.getAttributes().put("Pitch", 45.0);
planeGraphic.getAttributes().put("Roll", 12.0);
// add the graphic to the overlay

followGraphicsOverlay.getGraphics().add(planeGraphic);
// add the graphics overlay to the scene view

sceneView.getGraphicsOverlays().add(followGraphicsOverlay);

Update graphic position

When using a camera controller to follow a graphic, update the position of the graphic and the camera updates its location accordingly.
Provide a new Point for the graphic's geometry, and update the heading, pitch, and roll attributes as needed. The graphics overlay
renderer (and associated scene properties) controls updating the display of the graphic's heading, pitch, and roll.
This code updates the geometry and attributes of the graphic being tracked.
planeGraphic.setGeometry(newPoint);
planeGraphic.getAttributes().put("Heading", newHeading);
planeGraphic.getAttributes().put("Pitch", newPitch);
planeGraphic.getAttributes().put("Roll", newRoll);
Camera controllers
A scene view has an associated controller that manages the camera for the scene. Each type of camera controller is designed to provide
a specific user experience for interacting with the scene display. The camera controller and its properties can be changed at run time, so
your app can provide the scene interaction experience best suited for the current context.
ArcGIS Runtime SDK provides the following camera controllers:
GlobeCameraController (default) Provides the default scene view camera behavior. Allows the user to freely move and
focus the camera anywhere in the scene.
OrbitGeoElementCameraControllerLocks the scene view's camera to maintain focus relative to a (possibly moving)
graphic. The camera can only move relative to the target graphic.
OrbitLocationCameraControllerLocks the scene view's camera to orbit a fixed location (map point). The camera can
only move relative to the target map point.
When any camera controller other than GlobeCameraController is active, the scene view's viewpoint cannot be assigned. Attempts to
do so do not raise an exception, but they are ignored.
Note: At this release, OrbitGeoElementCameraController works only with graphics.

Use a camera controller to follow a graphic
The OrbitGeoElementCameraController updates the camera focal point relative to a specified (stationary or moving) graphic. As the
user interacts with the scene view, the scene view's camera follows a focal point specified by the target graphic. Using this controller, the
camera moves in sync with the target.
Note: By default, the target graphic is also the camera focal point. The focal point can also be placed
relative to the target graphic by applying offsets. See Adjust the display for details.
The following example creates a new OrbitGeoElementCameraController and assigns it to the SceneView. The Graphic to follow
is passed to the object's constructor, along with the initial distance from the target to the camera. By default, the camera is positioned with
a heading of 0 and a pitch of 45 degrees. See Adjust the display for information about modifying camera settings.
// create an OrbitGeoElementCameraController, pass in the target graphic and initial camera distance
OrbitGeoElementCameraController orbitGraphicController = new OrbitGeoElementCameraController(planeGraphic, 1000);
sceneView.setCameraController(orbitGraphicController);
The graphic associated with an OrbitGeoElementCameraController cannot be changed after the controller is initialized. To follow
another graphic, you must create a new OrbitGeoElementCameraController for the other graphic and set it as the scene view's
camera controller.

Adjust the display

Although the OrbitGeoElementCameraController locks the camera to a target graphic, the exact location of the camera in relation
to the target can be adjusted using offset values. Other aspects of the scene display can also be modified, such as whether or not the
camera should automatically adjust its heading, pitch, and roll when those values change in the tracked graphic. Adjustments to the
camera display, as well as limiting user interaction with the scene view, can be changed dynamically at run time.
Camera target offsets
The position of the camera focal point relative to the target graphic can be adjusted using x, y, and z target offsets. This allows you to
make precise adjustments to the display of the scene, for example, placing the camera inside the cockpit of an airplane graphic.
These offsets can be assigned individually or applied at once using an animation.
The following example applies offsets for the OrbitGeoElementCameraController.

// set the x, y, and z camera target offsets (animate change over 2 seconds)
orbitGraphicController.setTargetOffsetsAsync(43, 0, -55, 2);
You can also use TargetVerticalScreenFactor to adjust the vertical position of the target in the display. Acceptable values
range from 0 (bottom of the display) to 1 (top of the display). The default is 0.5, which places the target in the center of the display.
Auto heading, pitch, and roll
Auto heading, when enabled for the camera controller, means that the camera will rotate to follow changes in the graphic's heading
and therefore provide a consistent view of the graphic. When auto heading is disabled, the camera remains at a constant heading and
the graphic may appear to rotate as its heading changes.
Auto pitch and auto roll have similar effects. When enabled, the camera rotates with the target's pitch or roll and the surface appears
to rotate around the graphic, as shown on the left in the following image. When disabled, the camera is not affected by changes in the
graphic's pitch or roll.
These settings are true by default.

AutoHeadingEnabled
AutoPitchEnabled
AutoRollEnabled

Move the camera
While the OrbitGeoElementCameraController is associated with the scene view, the camera can be moved relative to the
target graphic (either programmatically or interactively).
Camera distanceThe distance in meters between the camera and its target. The camera position is derived from this
distance plus the camera offsets.
Camera heading offsetThe clockwise angle measured in the target element symbol's horizontal plane starting directly
behind the symbol (default is 0). Any angle in degrees is valid but will be normalized between the minimum and maximum
camera heading offsets. If after normalization the value is outside of the allowed range, the nearest value within the range will
be used.
Camera pitch offsetThe counterclockwise angle from the positive z-axis of the target element's symbol relative to the
symbol's horizontal plane, as illustrated in the following image (default is 45). If the value specified is outside of the range
defined by the minimum and maximum camera pitch offsets, the nearest value within the range will be used.
The following example moves the camera using the OrbitGeoElementCameraController.

// update camera position: delta values for distance, heading, pitch, and roll (animate change over 2 seconds)
orbitGraphicController.moveCameraAsync(300, 0, 45, 2);
Note: You can also change the offset properties individually as an alternative to using the
moveCameraAsync method.
Limit user interaction

When using an OrbitGeoElementCameraController or OrbitLocationCameraController, you can define minimum and
maximum values for the camera distance, heading, pitch, and roll properties if you want to further restrict user interaction with the scene
view. User interactions and scene view animations obey these limits.
Tip: Since the camera controllers don't recognize obstacles (for example, terrain) when tracking a
graphic, limiting or restricting the possible camera positions can help avoid them.
The following example limits the distance and pitch for the camera, but not the heading.
// limit the camera distance to between 1,000 and 10,000 meters
orbitGraphicController.setMinCameraDistance(1000);
orbitGraphicController.setMaxCameraDistance(10000);
// limit the camera pitch to between 25 and 75 degrees
orbitGraphicController.setMinCameraPitchOffset(25);
orbitGraphicController.setMaxCameraPitchOffset(75);
Types of scene view interaction can also be completely disabled if needed. You may want the user to interact with the scene view by
changing the camera heading and pitch, but not the camera distance, for example.
The following code disables the ability for the user to modify the camera distance when interacting with the scene view.
// restrict the ability to interactively change the camera distance
orbitGraphicController.setCameraDistanceInteractive(false);
Stop following a graphic

To stop following a graphic, reset the scene view's camera controller to the default, GlobeCameraController.
In general, the only time you need to assign this camera controller to the scene view is to return to the default behavior after applying one
of the nondefault controllers.

The following code applies a new GlobeCameraController to the SceneView.

// apply the (default) globe camera controller
sceneView.setCameraController(new GlobeCameraController());
The globe camera controller allows the user to interactively change the camera position, focal point, and any of the camera properties.
Use this controller to let your user freely explore the scene. See Navigate a scene view for more information about interacting with a scene
view using the globe camera controller.

Add graphics overlays to your app

A graphics overlay is a container for temporary graphics that you want to display on your map view, such as the graphics in the following
illustration. The graphics you draw in your graphics overlays are created at runtime and are not persisted when your application closes.
Typical use cases for adding graphic overlays to your map view include the following:
Showing the location of a moving object. The locations could be from your own GPS receiver.
Showing the results of a geocoding or routing task
Drawing temporary map markups, sometimes referred to as red lining.
A map view can contain many graphics overlays that are drawn on top of the layers in your map. Each graphics overlay may contain a
number of graphics. A graphic is defined by the following components:
Geometry, which is either a point, line, or polygon
Symbology, which defines how your geometry is drawn. For example, if the geometry is a line, then your symbology would define
the line color as red.
Attributes, which are an optional set of items like fields in a database row.
Now you're ready to add graphics and text to your graphics overlays.
Note: Graphics overlays are visible only on a map view that contains a map.

Add graphics and text to graphics overlays

A graphic is a visible item on your map that can be seen as a point, line, polygon, or text. You can add graphics to your map view. These
are contained in graphics overlays and are for showing temporary data that's not persisted once the application closes. For example, you
may want to display a route between two locations or animate data items that change quickly.
This topic discusses adding graphics to your map in a way that generates a symbol instance for each graphic. If you're drawing a large
number of graphics with the same symbology, then you should consider applying a renderer to the graphics overlay instead, which allows
you to define the appearance of all the graphics in the overlay. Using renderers to add graphics is discussed in Symbols and renderers.
The image below shows an example of graphics drawn over a gray basemap. The graphics are showing:
Red markers showing location of buoys
Text symbols adding names to the islands of Craigleith and Bass Rock
A green cross hatched polygon showing a Gannet nesting ground on Bass Rock
A purple line showing the path of a boat trip.
For more information on graphics and when to use them, see Features and graphics. For more information on graphics overlays, see Add
graphics overlays to your app.
Add point graphics

The following steps show how to create the red buoy markers on the image above.
1. The location of point graphics is represented by the Point geometry class. The following code shows how the buoy locations are
defined:
SpatialReference SPATIAL_REFERENCE = SpatialReferences.getWgs84();
Point buoy1Loc = new Point(-2.72, 56.065, SPATIAL_REFERENCE);
The points are defined in the WGS84 spatial reference, which is generally the spatial reference you would obtain from a GPS
receiver, for example.
Tip: If the spatial reference of the geometry of a graphic is null, then it is assumed the
geometry is in the same spatial reference as the map view; if your graphics do not
display as expected and have a null spatial reference, check that the coordinates of your
geometry use the same spatial reference as the map view. If the spatial reference is set,
and is different to that of the map view, geometries are automatically reprojected for
display. For maximum efficiency, especially when dealing with large numbers of graphics
or moving graphics, geometries of graphics should have the same spatial reference as
the map view.
2. Define what the points look like. Points can be drawn as simple marker symbols (circles, crosses, diamonds, etc.) or picture
marker symbols represented by small bitmap images.
The code below shows how to define a red circle.
// create a red (0xFFFF0000) circle simple marker symbol
SimpleMarkerSymbol redCircleSymbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, 0xFFFF0000, 10);

3. Create graphics, which are defined by the point geometry and the symbol.
// create graphics and add to graphics overlay
Graphic buoyGraphic1 = new Graphic(buoy1Loc, redCircleSymbol);
4. Add the graphics to the graphics overlay, which will display them on the map view.
graphicsOverlay.getGraphics().addAll(Arrays.asList(buoyGraphic1, buoyGraphic2, buoyGraphic3, buoyGraphic4));
Add line graphics

The following steps show how to create the purple, dashed line representing the boat trip in the image near the top of this topic.
1. The geometry for the boat trip is represented by the Polyline class. This is built with a collection of points used to define the
vertices of the line.
// create a new point collection for polyline
PointCollection points = new PointCollection(SPATIAL_REFERENCE);
// create and add points to the point collection
points.add(new Point(-2.715, 56.061));
// create the polyline from the point collection

Polyline polyline = new Polyline(points);
For more information on drawing lines using the geometry API, see Geometries.
2. Define the symbol for the boat trip using the SimpleLineSymbol class.
The code below defines this as a purple dashed line.
//define a line symbol
SimpleLineSymbol lineSymbol =
new SimpleLineSymbol(
SimpleLineSymbol.Style.DASH,
Color.argb(255, 255, 128, 0), 4, 1.0f);
3. Create the graphic from the line geometry and line symbol.
// create the graphic with polyline and symbol
Graphic graphic = new Graphic(polyline, lineSymbol);
4. Add the graphic to the graphics overlay.

// add graphic to the graphics overlay
Add polygon graphics

The following steps show how to create the polygon representing the nesting ground area in the image near the top of this topic.
1. The geometry for the nesting ground is defined using the Polygon class. The vertices of the polygon are created from a
collection of points. For more information on building polygons, see Geometries.
// create a new point collection for polygon
PointCollection points = new PointCollection(SPATIAL_REFERENCE);
// create and add points to the point collection

// create the polyline from the point collection
Polygon polygon = new Polygon(points);
2. Define a symbol for the polygon. The symbol in the screen shot above is made up of a line symbol for the outline and a fill symbol
for the polygon fill.

//define the fill symbol and outline

SimpleLineSymbol outlineSymbol =
new SimpleLineSymbol(
SimpleLineSymbol.Style.DASH,
Color.argb(255, 0, 0, 128), 1, 1.0f);
SimpleFillSymbol fillSymbol =
new SimpleFillSymbol(
Color.argb(255, 0, 80, 0, 255),
SimpleFillSymbol.Style.DIAGONAL_CROSS,
outlineSymbol, 1.0f);
3. Create the graphic from the polygon geometry and fill symbol.
// create the graphic with polyline and symbol
Graphic graphic = new Graphic(polygon, fillSymbol);
4. Add the polygon graphic to the graphics overlay.

// add graphic to the graphics overlay
Add text
The following steps show how to add the "Craigleith" and "Bass Rock" text to the graphics overlay.
1. The geometry for text symbols is a point. The point represents the anchor point for the text. The following code defines the
anchor points for the two text symbols in the image at the top of this topic.
// create two points
Point bassPoint = new Point(-2.64, 56.079, SPATIAL_REFERENCE);
Point craigleithPoint = new Point(-2.72, 56.076, SPATIAL_REFERENCE);
2. Create the symbols for the text items.

//create text symbols
TextSymbol bassRockSymbol =
new TextSymbol(
10, "Bass Rock", Color.argb(255, 0, 0, 230),
HorizontalAlignment.LEFT, VerticalAlignment.BOTTOM);
TextSymbol craigleithSymbol =
new TextSymbol(
10, "Craigleith", Color.argb(255, 0, 0, 230),
HorizontalAlignment.RIGHT, VerticalAlignment.TOP);
3. Create the graphics from the point and text symbol.

// create two graphics from the points and symbols
Graphic bassRockGraphic = new Graphic(bassPoint, bassRockTextSymbol);
Graphic craigleithGraphic = new Graphic(craigleithPoint, craigleithTextSymbol);
4. Add the text graphics to the graphics overlays.

// add graphics to the graphics overlay
graphicsOverlay.getGraphics().add(bassRockGraphic);
graphicsOverlay.getGraphics().add(craigleithGraphic);
Identify graphics
In your app, you can add code to allow users to click on a graphic and get more information about it. For example, you may tap or click on
a seabird in your graphics overlay to display the name of the bird's species in a dialog box.
The identifyGraphicsOverlay method on the map view allows you identify graphics at a point on the map for a given graphics
overlay. If you have more than one graphics overlay and want to perform an identify operation on all graphics overlays, use the
identifyGraphicsOverlays method. The example below shows how you can perform an identify on a single graphics overlay in
response to a tap on the map view.

//set a custom touch listener on the MapView

mapView.setOnTouchListener(new MapTouchListener(this, mapView));
[...]
//define custom touch listener class, overriding the onSingleTapConfirmed method
class MapTouchListener extends DefaultMapViewOnTouchListener {
public MapTouchListener(Context context, MapView mapView) {
super(context, mapView);
}
@Override
//get the tapped location in screen coordinates.
android.graphics.Point screenPoint = new android.graphics.Point((int) e.getX(), (int) e.getY());
//use the screen location to perform the identify
final ListenableFuture<List<Graphic>> identifyGraphics = mapView.identifyGraphicsOverlay(graphicsOverlay,
screenPoint, 10, 2);
//wait for the results to be returned.
identifyGraphics.addDoneListener(new Runnable() {
@Override
public void run() {
seaBirdDialog(identifyGraphics);
}
});
return true;
}
}
You can iterate through each result returned from an identify. For example, you can display a list of the attribute values from each result.
Select graphics
Selecting a graphic is a way of bringing it to the attention of a user by drawing a halo around it. Change the selection state of a graphic by
using the setSelected method on the Graphic class.
Update graphics
It's possible to update the geometry or attributes of a graphic by using the graphics collection of the graphics overlay. The code below sets
a new geometry on a graphic (grItem).
// create a point from location clicked
mapView.setOnMouseClicked(e -> {
if (e.getButton() == MouseButton.PRIMARY) {
Point2D mapViewPoint = new Point2D(e.getX(), e.getY());
// add new location to selected graphic
Point mapPoint = mapView.screenToLocation(mapViewPoint);
selectedGraphic.setGeometry(mapPoint);
}
});
Remove graphics
To remove graphics you work with the graphics collection and call the remove method.
routeGraphicsOverlay.getGraphics().remove(routeGraphic);

Identify features
Maps often combine many sources of information such as feature layers, image layers, and graphics. Labels and legends don't always
provide enough information to work out what the map is displaying. Use the identify methods to quickly answer the question 'what is this
item here?', allowing your users to easily explore and learn about the map content by tapping or clicking on them. Information returned can
be shown in pop-ups or other UI components in your app.
You can identify the visible items at a specific point on screen:
Within all the layers in the map or only within a specific layer
Within all the graphics overlays in the view or only within a specific graphics overlay
Returning only the topmost item or all the items at that location
Returning the feature, graphic, or other item at that location, or by returning pop-ups for pop-up-enabled layers
Identify methods are asynchronous, so that the UI thread of your application is not blocked waiting for results. This is especially important
when working with data with resides on a server, as results do not return immediately. The results of an identify take into account:
Symbologytapping on a large marker symbol used to draw a point, or a wide line symbol used to draw a polyline or outline of a
polygon will include those items in the results; it's not just the geometry that is used.
Visibilitythe visibility of a graphics overlay or layer, and of an individual feature or graphic is checked, and results will only
include the visible items. The opacity of a layer or graphic is ignored.
Visible extentonly items within the currently visible map extent are included in identify results.
Identify is supported on graphics overlays, feature layers and map image layers, and also on tiled layers that are based on map services
that support identify. The sections below show you how to identify different items in the map in different ways, but these approaches can
be combined to provide general identify functionality if required.
Identify features in a feature layer

The steps below show you how to identify the features within a specific feature layer in the map. Later in this topic, these steps are
adapted to identify only the topmost feature, identify against multiple layers and different types of layers, and to identify graphics.
1. Listen to a tap or click event on the map or scene view, and get the point representing the center of the tap or click.
Create a class that inherits from DefaultMapViewOnTouchListener and provide a default constructor to set the layer to be
identified. Override onSingleTapConfirmed and in it, create an android.graphics.Point from the x,y coordinates of the
MotionEvent parameter. Set an instance of this class onto the MapView.
private class IdentifyFeatureLayerTouchListener extends DefaultMapViewOnTouchListener {
private FeatureLayer layer = null; // reference to the layer to identify features in
// provide a default constructor
public IdentifyFeatureLayerTouchListener(Context context, MapView mapView, FeatureLayer layerToIdentify) {
super(context, mapView);
layer = layerToIdentify;
}
// override the onSingleTapConfirmed gesture to handle a single tap on the MapView
@Override
// get the screen point where user tapped
android.graphics.Point screenPoint = new android.graphics.Point((int) e.getX(), (int) e.getY());
// ...
return true;
}
}
mapView.setOnTouchListener(new IdentifyFeatureLayerTouchListener(this, mapView, featureLayerToIdentify));
2. Call the required identify method, passing in the screen point from the previous step.
a. Choose either to identify against a specific layer, or to identify against all layers.
b. Specify a tolerance for the search radius of the identify operation. A tolerance of 0 identifies only items at the single pixel at
the screen point. However, typically this level of precision is hard to achieve, so you can supply a tolerance around the
screen point. A suitable tolerance for a tap operation on a touch screen should be equivalent to the size of the tip of a finger,
and a smaller tolerance should be considered for mouse pointers. The units of the tolerance are in Device-independent
pixels (DPs) - .
c. Specify whether to include pop-up information on the geo-elements returned. (If no pop-ups are defined for a layer or
graphics overlay, pop-ups will not be included in the results regardless of this parameter value).

d. Optionally, specify the maximum number of results per-layer to return. This may be especially useful if identifying on service
layers, as you can limit the amount of information returned to the client (the maximum results will also be limited by the
server).
The identifyLayersAsync method returns a ListenableFutureyou will use this to return the identify results. Add a done
listener to this future, and in the done listener Runnable, call getthis will return the actual identify results as an
IdentifyLayerResult.
// call identifyLayerAsync, specifying the layer to identify, the screen location, tolerance, types to return, and
// maximum results
final ListenableFuture<IdentifyLayerResult> identifyFuture =
mMapView.identifyLayerAsync(layer, screenPoint, 20, false, 25);
// add a listener to the future

identifyFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
// get the identify results from the future - returns when the operation is complete
IdentifyLayerResult identifyLayerResult = identifyFuture.get();
// ...
} catch (InterruptedException | ExecutionException ex) {
// must deal with checked exceptions thrown from the async identify operation
dealWithException(ex);
}
}
});
3. Results consist of layer content information about the layer the results are from, and a list of GeoElement. Each GeoElement
represents a feature identified at the given screen point. Iterate the results, access the geometry and attributes of the identified
features, and use them as required. In the example below, each identified feature is selected.
To select the identified features, cast the LayerContent from IdentifyLayerResult.getLayerContent() to
FeatureLayer. Iterate each GeoElement from IdentifyLayerResult.getIdentifiedElements() and cast to feature.
Call FeatureLayer.selectFeature(), passing in each identified feature. You could additionally add code to clear any
existing selection before each identify operation.
@Override
public void run() {
try {
IdentifyLayerResult identifyLayerResult = identifyFuture.get();
// a reference to the feature layer can be used, for example, to select identified features
FeatureLayer featureLayer = null;
if (identifyLayerResult.getLayerContent() instanceof FeatureLayer) {
featureLayer = (FeatureLayer) identifyLayerResult.getLayerContent();
}
// iterate each identified geoelement from the specified layer and cast to Feature
for (GeoElement identifiedElement : identifyLayerResult.getElements()) {
if (identifiedElement instanceof Feature) {
// access attributes or geometry of the feature, or select it as shown below
Feature identifiedFeature = (Feature) identifiedElement;
if (featureLayer != null) {
featureLayer.selectFeature(identifiedFeature);
}
}
}

dealWithException(ex); // deal with exceptions thrown from the async identify operation
}
}
});
Tip: Features are loadable, but when using identify methods, they are always returned
already loaded.
Identify features in all feature layers

When you do not know which specific layer to identify on, you can identify items in any layer in the map. Change the first workflow above
so that you do not specify the layer to identify. This time, the results are returned as a list of IdentifyLayerResult instead of a single
result.

// call identifyLayersAsync, passing in the screen point, tolerance, return types, and maximum results, but no layer
final ListenableFuture<List<IdentifyLayerResult>> identifyFuture = mMapView.identifyLayersAsync(
screenPoint, 20, false, 25);
@Override
public void run() {
try {
List<IdentifyLayerResult> identifyLayersResults = identifyFuture.get();
// iterate all the layers in the identify result

for (IdentifyLayerResult identifyLayerResult : identifyLayersResults) {
// iterate each result in each identified layer, and check for Feature results
Feature identifiedFeature = (Feature) identifiedElement;
// Use feature as required, for example access attributes or geometry, select, build a table, etc...
processIdentifyFeatureResult(identifiedFeature, identifyLayerResult.getLayerContent());
}
}
}
dealWithException(ex); // must deal with exceptions thrown from the async identify operation
}
}
});
Layers that do not support identify or do not have any results based on the inputs are not included in the returned list.
Identify topmost item only

To identify only the topmost item at the screen point (or the topmost item per layer, if identifying against all layers) change the first
workflow above by removing the maximum number of results parameter. GeoElements are still returned as a list, but the list will have
only zero or one items.
The code below selects only the topmost feature identified at the screen point, for all feature layers in the map.
// call identifyLayersAsync, passing in the screen point, tolerance, and return types, but no maximum results value
final ListenableFuture<List<IdentifyLayerResult>> identifyFuture = mMapView.identifyLayersAsync(screenPoint, 20,
false);
@Override
public void run() {
try {
for (IdentifyLayerResult identifyLayerResult : identifyLayersResults) {
// each identified layer should find only one or zero results, when identifying topmost GeoElement only
if (identifyLayerResult.getElements().size() > 0) {
GeoElement topmostElement = identifyLayerResult.getElements().get(0);
if (topmostElement instanceof Feature) {
Feature identifiedFeature = (Feature)topmostElement;
// Use feature as required, for example access attributes or geometry, select, build a table, etc...
processIdentifyFeatureResult(identifiedFeature, identifyLayerResult.getLayerContent());
}
}
}
}
}
});
Identify on map image layers

Identifying against map image layers and tiled map layers follows the same workflow as shown for feature layers. The difference when
identifying against map image layers are:
Results are returned as Features; unlike other features however, they will not have a reference to a FeatureTable.
Map image layers may have one or more sublayersidentify results from map image layers reflect this structure, and return
results for each sublayer separately. (Note that if you have specified a maximum number of results to return, this value applies per
sublayer.)
The code below shows how identify results are returned as Features for map image layers, which may have sublayer results that are
also Features. A recursive function can be used to iterate through all the layer and sublayer results.
Demonstrates how to get all Features that will be identified at the screenPoint given for all layers attached to MapView.

final ListenableFuture<List<IdentifyLayerResult>> identifyFuture = mMapView.identifyLayersAsync(screenPoint, 20,

false, 10);
@Override
public void run() {
try {
iterateIdentifyImageLayerResults(identifyLayersResults);

}
}
});
Demonstrates how to cycles through all identified layers and get Features that were identified.
public void iterateIdentifyImageLayerResults(List<IdentifyLayerResult> identifyLayerResults) {
if ((identifyLayerResults == null) || (identifyLayerResults.size() < 1)) return;

for (IdentifyLayerResult identifyLayerResult : identifyLayerResults) {
// for each result, get the GeoElements

// Map image layer identify results are returned as Features with a null FeatureTable; they cannot be
// selected, but you can get the attributes and geometry of them...
processIdentifyImageLayerResult(((Feature)identifiedElement), identifyLayerResult.getLayerContent());
}
}
// for each result, get the sublayer results by recursion
iterateIdentifyImageLayerResults(identifyLayerResult.getSublayerResults());
}
}
Return pop-ups as results

Some types of layer support pop-ups. You can use an identify method to return pop-ups for map content at a screen point.
The code below shows how you can use MapView.identifyPopups() to return Popups as identify results, instead of returning
GeoElements.
// call identifyLayersAsync, passing in the screen location, tolerance, and specifying that pop-ups should be
// returned as well as features; not passing in maximum results parameter means only topmost item is identified
// note that you can choose to return popups only, instead of both geoelements and popups if available
final ListenableFuture<List<IdentifyLayerResult>> identifyFuture = mapView.identifyLayersAsync(screenPoint, 10, false);
@Override
public void run() {
try {
// Here we just show the pop-up for the first (top) layer; if more than one layer may have pop-ups, or more
// than one element is identified in a single layer, add controls to the pop-up content to iterate through
// multiple pop-ups.
if (identifyLayersResults.size() >= 1) {
IdentifyLayerResult identifyLayerResult = identifyLayersResults.get(0);
// Only identifying the topmost item in this example, so only expecting one pop-up
if (identifyLayerResult.getPopups().size() >= 1) {
Popup identifiedPopup = identifyLayerResult.getPopups().get(0);
showPopup(identifiedPopup, screenPoint);
}
}

dealWithException(ex); // deal with exceptions thrown from the async identify operation
}
}
});
Identify graphics
Graphics are identified using methods different than those used for layers. You can choose to return graphics in a specific graphic overlay
or for all graphics overlays; you can also limit results to only the topmost graphic in each graphics overlay.
The code below shows how you can use MapView.identifyGraphicsOverlayAsync() to return Graphics as identify results, and
select them.

// identify graphics on the graphics overlay

final ListenableFuture<IdentifyGraphicsOverlayResult> identifyFuture = mMapView.identifyGraphicsOverlayAsync(overlay,
screenPoint, 10, false, 10);
@Override
public void run() {
try {
// get the list of graphics returned by identify
List<Graphic> identifiedGraphics = identifyFuture.get().getGraphics();
// iterate the graphics

for (Graphic graphic : identifiedGraphics) {
// Use identified graphics as required, for example access attributes or geometry, select, build a table, etc...
graphic.setSelected(true);
}
dealWithException(ex); // must deal with checked exceptions
}
}
});

Search for places (geocoding)

Using a place name or street address as input, your user can find locations of interest and interact with them on the map. The process of
matching locations on the map to an address is referred to as geocoding.
Geocoding overview
Address geocoding (or geocoding) is the process of using information contained in an address to interpolate a corresponding location on
the map. An address may define a precise street location, such as 380 New York Street, Redlands CA 92373. It may provide
only a general location, such as a city name or postal code, or it may be a familiar place name or landmark, such as Ayers Rock.
Using a reference data source, referred to as a locator, ArcGIS finds map locations by matching an input address with feature attributes.
The number and accuracy of the geocoded results (often called matches or candidates) may vary depending on the specificity and quality
of the input address provided. For example, the address New York is likely to return a match for the state of New York, the city of New
York, and perhaps several streets or points of interest that share that name. Geocoded locations are always points. If a match is made
with a polygon (a state or postal code, for example), the match location represents the center of that area.
Additional geocoding inputs can improve the relevance of results by restricting the search to a given area or finding matches that are near
a reference location. This allows you to find results for a specified country, map extent, or near the user's current or anticipated location. A
general search such as restaurant is unlikely to return useful candidates unless it is restricted to a specific area.
When several candidates are returned for an address, they are sorted by the quality of the match. This means it is generally safe to
assume that the first candidate in the results represents the best match. Sometimes, however, you may want to examine a set of top
candidates to determine the most appropriate match. Address candidates can contain the level at which they were matched (house,
street, postal code, and so on) and the interpolated address created by the locator. Both of these may help you determine the best match
or perhaps find problems in the original address input. If geocoding used a reference location, a distance attribute can help you find the
closest candidate.
Caution: The score attribute, an integer value ranging from 0 to 100, provides an estimate of relative match
accuracy within a single locator. If you are using a composite locator (such as the ArcGIS World
Geocoding Service), these values will represent the score within a locator for a specific level, but
not an overall evaluation of the match. A score of 100 for a postal code match is not necessarily a
more precise result, for example, than a score of 90 at the house level.
Addresses
Addresses are fundamental for geocoding and have some specific characteristics. An address is composed of one or more address
elements: individual components of the address, such as house number, street name, street type, and postal code. Address elements
help in the geocoding search, pinpointing an address to a particular location. Addresses come in various styles and formats, including
street address, a place name, or a location that is identified by a code. A common address format used in the United States consists of
the following series of address elements: house number, prefix direction, prefix type, street name, street type, suffix direction, and zone
information (such as city, state, and ZIP Code). Globally, addresses are represented in a variety of formats. However, while all of these
addresses differ to some degree, some things remain consistent. Each address consists of one or more address elements presented in
a particular address format recognized by those in the region.
When geocoding, you can pass in individual components of an address or provide all information as a single string to be parsed.
Defining each component of an address gives you more control but may require that you either parse the components before passing
them to the locator or provide additional UI controls for your user to enter each piece of information.
When geocoding, the type of information expected in an input address is determined by the address style configured by the locator
you're using. Some of the common address component field names for the ArcGIS World Geocoding Service
(https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer) are listed below as examples of the types
of input that may be expected. See Multiple input field geocoding for details.
AddressHouse number and street
NeighborhoodSubdivision of a city (not used for United States addresses)
CityCity or municipality
SubregionAdministrative region, such as a county or province (not used for United States or Mexico addresses)
RegionLargest administrative boundary associated with the address (state name in the United States)
PostalPostal code

CountryCodeName or ISO code of the country
Locators
The fundamental logic for geocoding is built into the locator and does not come from your ArcGIS Runtime SDK code. The locator
(created using ArcGIS Desktop) is the major component in the geocoding process and contains all the data necessary to perform
address matching. If you'd like a ready-to-use and regularly updated locator (and network dataset) for your area of interest, you can
license StreetMap Premium data (in MMPK format). For details, see Add StreetMap Premium data.
A locator is created based on a specific address locator style, which dictates what type of address input is expected and how matching
will be carried out. The following table lists some of the common address styles, the type of matching that it enables, and an example of
input address values:
Address style Description Input address examples

US Address - City Finds a city in the United States using reference data that stores city and state names Bonita, CA
State Punxsutawney, PA
US Address - Dual Interpolates an address location using a streets reference dataset that includes number 30 E. State St, Redlands CA
Ranges ranges for both sides of the street 92373
1060 W. Addison St,
Chicago IL 60613
General - Finds place names or landmarks worldwide using reference data with a place name Taj Mahal
Gazetteer attribute Ypres
General - Single Locates features using a specific field in the reference dataset 012883902
Field UTC330868-A
Note: This is not a complete list of the available address styles. For a more complete description,
see Commonly used address locator styles in the ArcGIS Desktop help.
Once created, an address locator contains a set of geocoding properties (preferences), a snapshot of the address attributes in the
reference dataset, and the queries for performing a geocoding search. The address locator also contains a set of address parsing and
matching rules that directs the geocoding engine to perform address standardization and matching.
A locator can be stored locally (as a *.loc file) or can be published as a locator service using ArcGIS Server. To perform geocoding, you
need to access either an online locator or one available locally on the device. Using ArcGIS Runtime SDK, you can connect to a variety
of online locators published and hosted by Esri, including address locators for Europe and North America, a street locator for the United
States, and a world places locator. These services allow you to begin geocoding with online data right away without having to create
and configure an address locator yourself. Locators can be created and configured with local data using ArcGIS Desktop as the
authoring environment. See the ArcGIS help topic Creating an address locator for detailed information.
Results
Geocoding results for a particular address are referred to as candidates. Depending on how specific and complete the input address is,
you may get several candidates from a geocode operation. Geocoding results are ordered by quality of the match, so the first candidate
is generally the best. Additional candidate information can be obtained by specifying supplemental output fields to include in the results.
The following table describes a few of the available fields you can include from the world geocoding service. This is only a
representative list of fields. For a complete list, see Output fields in the ArcGIS REST API documentation.
Note: The fields provided may vary between locators. See the Get locator info section of this topic
for information about querying a locator for its available result attributes.
Output field Description

Score Value between 0 and 100 that describes the relative quality of the match within a single locator.
Match_addr Complete address returned for the geocode request. The format is based on address standards for the country within which the
address is located.
Addr_type The match level for a geocode request. For example, a candidate that matches only to a postal code will have a value of
Postal. Supported match levels vary in different countries. See Output fields for a description of possible values for this field.
Side The side of the street on which the address was matched (relative to the direction of digitization of the reference line feature).
Possible values are L (left), R (right), or an empty string (undefined).
Distance The distance (meters) from the candidate to a specified location. The reference location needs to be specified as a parameter
before executing the task.

Rank A number indicating the importance of each candidate relative to others in the results. Rank is generally used to help distinguish
ambiguous place names using population as the criterion. A search for Las Vegas, for example, may return Las Vegas,
NV as the top ranked match (1) and Las Vegas, NM as a lower rank based on the relative population of those cities. If a
reference location and distance parameters have been set for a find operation, distance from the reference location will be used to
rank candidates.
Use a locator task

Geocoding is implemented using the LocatorTask class with an online or local locator. To implement this task in your code, follow these
general steps:
1. Create a LocatorTask using an online or local resource (locator service or file).
2. Specify geocoding preferences using the GeocodeParameters object. This is optional but allows you to request additional
attributes in the results, to restrict the search by area, set the maximum number of results, and so on.
3. Execute the task, passing in any required parameters (such as address values and geocode parameters).
4. Process the results (display a list of candidates for the user to choose from, display the best match as a graphic on the map, and
so on).
For example, create an online locator by passing the URL of the ArcGIS Online World Geocoding service to the LocatorTask
constructor; alternatively, create an offline locator by passing the full file path of the locator file.
// Create a LocatorTask using an online locator
onlineLocator.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
if (onlineLocator.getLoadStatus() == LoadStatus.LOADED) {
// Locator is ready to use
}
else {
dealWithLoadFailure(); // Deal with loading error appropriately...
}
}
});
onlineLocator.loadAsync();
Get locator info

Before executing a geocode operation, you may need information about a particular locator to work with it effectively. You may need to
know which input fields are used to locate an address, which attributes are available with the results, or the spatial reference in which
the candidate locations will be returned by default. You can use LocatorInfo to get the following information about a locator:
NameA string that identifies the locator
DescriptionA brief description
Result attributesA list of field names that are available for results
Search attributesA list of input fields used for multiline geocoding
Spatial referenceThe spatial reference used by the locator (and the default coordinate system for results)
Support for intersectionsA true or false value that indicates whether geocoding of street intersections is supported
Support for points of interestA true or false value that indicates whether searching points of interest (POI) is supported
Support for suggestionsA true or false value that indicates whether the locator supports offering suggestions for addresses
VersionThe version of the locator
The following example shows how you can examine the LocatorInfo of the LocatorTask to list the names of the attributes available
on geocode results:
// Get LocatorInfo from a loaded LocatorTask
LocatorInfo locatorInfo = locatorTask.getLocatorInfo();
List<String> resultAttributeNames = new ArrayList<>(resultAttributeCount);
// Loop through all the attributes available

for (LocatorAttribute resultAttribute : locatorInfo.getResultAttributes()) {
resultAttributeNames.add(resultAttribute.getDisplayName());
// Use in adapter etc...
}
Geocode parameters
When geocoding an address or point of interest, you can optionally provide preferences to control certain aspects of the geocoding
operation. The following list describes some of the properties you can control:
CountryThe full name or code for the country to which geocoding should be restricted

Maximum resultsA limit for the maximum number of address candidates to return
Output languageThe language (culture) in which result attributes will be returned
Output spatial referenceThe spatial reference in which geographic locations for address candidates will be returned
Result attributesA list of field names to include in the results (available fields can be queried from the locator)
Search areaA geographic shape that defines an area to geocode within
A similar (more limited) set of preferences is available when getting a set of address suggestions, as described in the following section.
Get address suggestions

You can use a locator task to find suggestions for a partial address entry. As your user types an address, for example, a list of
suggestions based on the first few characters of the address string can be displayed. Check LocatorInfo.supportsSuggestions
to see if a particular locator can provide address suggestions.
A search for address suggestions can optionally be restricted to a specified country or area on the map. To define a country, use the full
name or ISO 3166-1 (two or three character) code. See Geocode coverage in the REST API documentation for a list of countries and
corresponding codes. You can also indicate a preferred location (point) for the search, and set the maximum number of suggestions to
return.
Tip: Restricting your search or geocode operations to a specified country or location (as well as
the number of results) can improve performance.
The following example calls the suggestAsync method of a LocatorTask to get address suggestions based on user input. A
SuggestParameters object is used to restrict the search for suggestions to address that are located within the current map extent.
// Get LocatorInfo from a loaded LocatorTask
if (locatorTask.getLocatorInfo().isSupportsSuggestions()) {
// Get the current map extent
Geometry currentExtent = mapView.getCurrentViewpoint(Viewpoint.Type.BOUNDING_GEOMETRY).getTargetGeometry();
// Restrict the search to this map extent, and to no more than 10 suggestions
SuggestParameters suggestParams = new SuggestParameters();
suggestParams.setSearchArea(currentExtent);
suggestParams.setMaxResults(10);
// Get suggestions for user provided input
final ListenableFuture<List<SuggestResult>> suggestionsFuture = locatorTask.suggestAsync(userInput, suggestParams);
suggestionsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
List<SuggestResult> suggestResults = suggestionsFuture.get();
List<String> suggestedAddresses = new ArrayList<>(suggestResults.size());
// Iterate the suggestions
for (SuggestResult result : suggestResults) {
suggestedAddresses.add(result.getLabel());
}
// Show suggestions of complete addresses to the user, for example update a list adapter
showSuggestions(suggestedAddresses);
}
}
}
});
The address suggestion results do not contain location information, only the full address text. To get a location, you must take the
additional step of geocoding the suggestion as described in the following section.

Geocode an address
Use a LocatorTask to find geocode candidates from an address, point of interest, or address suggestion. An input address can be
defined as a single string, such as 380 New York Street, Redlands CA 92373 or you can define the individual components of
the address (such as number and street, city, region, postal code, and so on).
Tip: You can use LocatorInfo to get the input address field names for a locator.
If you define the address as a single string, it will be parsed into the appropriate address components by the locator.
// Call geocodeAsync passing in an address
final ListenableFuture<List<GeocodeResult>> geocodeFuture = onlineLocator.geocodeAsync("380 New York Street, Redlands, CA");
@Override
public void run() {
try {
if (geocodeResults.size() > 0) {
// Use the first result - for example display in an existing Graphics Overlay
Graphic gecodedLocation = new Graphic(topResult.getDisplayLocation(), topResult.getAttributes(),
new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.SQUARE, Color.rgb(255, 0, 0), 20.0f));
mGraphicsOverlay.getGraphics().add(gecodedLocation);
}
}
}
}
});
You can also geocode using a result from an address suggestion. The following example geocodes a suggested address as created in
the Get address suggestions section of this topic.
final ListenableFuture<List<GeocodeResult>> geocodeFuture = locatorTask.geocodeAsync(suggestionResult);
The following example matches a Japanese address with the ArcGIS World Geocoding Service. The geocode parameters restrict the
address search to Japan.
geocodeParams.setCountryCode("Japan");
// Geocode an address in Japan - Prime Ministers Office
String address = "";
final ListenableFuture<List<GeocodeResult>> geocodeFuture = locatorTask.geocodeAsync(address, geocodeParams);
@Override
public void run() {
try {
// Use the first result - for example display on the map
addGraphic(topResult.getDisplayLocation(), topResult.getAttributes());
}
}
}
});
Note: See Geocode coverage in the REST API documentation for a list of supported countries and
corresponding codes.

Find points of interest

You can also geocode points of interest using a place name, such as Eiffel Tower or even more general terms, such as bank or
bus stop. The geocode parameters allow you to restrict your search to a specified extent or to prefer candidates that are closer to a
specified location, which can be useful if searching for facilities near the user's current position. You can provide the user with
information about the locations, such as addresses, phone numbers, and URLs for candidates, as well as the distance from a reference
location.
Tip: Not all locators support geocoding a point of interest. The result information for candidates
will also vary with the locator. Use LocatorInfo to see if geocoding points of interest is
supported and which attributes are available for the result candidates, as described in a
preceding section. The Distance attribute will only contain (non-zero) values if a preferred
search location (point) is provided in the geocode parameters.
Geocoding a point of interest involves the same process as using an address described in the previous section. Instead of passing a
single-line address value as input, you can provide a place name. The following are examples:
Point of interest by name
Wrigley Field
Disneyland
mount everest
Point of interest by category
restaurant
petrol
coffee in Salt Lake City
Administrative place name, such as a city/county/state/province/country nameSeattle, Washington
Postal code92591 USA
You can use geocode parameters to refine or restrict search results when geocoding place names just as you do with addresses.
The following example searches for five ice cream shops near a specified location (the center of the map extent) and specifies that
name, phone number, address, and distance are returned in the results. The results are displayed as graphics that have the same
attributes as the geocode results (which could then be displayed in a callout for example).
if (locatorTask.getLocatorInfo().isSupportsPoi()) {
// Get the center of the current map extent
Point mapCenter = (Point) mapView.getCurrentViewpoint(Viewpoint.Type.CENTER_AND_SCALE).getTargetGeometry();
//Retrieve the 5 closest matches to the map center
geocodeParams.setMaxResults(5);
geocodeParams.setPreferredSearchLocation(mapCenter);
geocodeParams.getCategories().add("Ice Cream Shop");
//Ensure the results return the Address, Phone and Distance
List<String> resultAttributeNames = geocodeParams.getResultAttributeNames();
resultAttributeNames.add("Place_addr");
resultAttributeNames.add("Phone");
resultAttributeNames.add("Distance");
//Geocode the closest ice cream shops using the specified geocoding parameters
final ListenableFuture<List<GeocodeResult>> geocodeFuture = locatorTask.geocodeAsync("", geocodeParams);
@Override
public void run() {
try {
// Use the results - for example display on the map
for (GeocodeResult result : geocodeResults) {
addGraphic(result.getDisplayLocation(), result.getAttributes());
}
}
}
}
});


Search for related features

You can search for features in one table that are related to features in another table, provided a relationship was defined between the two
tables. Table relationships are defined using ArcGIS Desktop, as described in Essentials of relating tables in the ArcGIS Desktop help.
Note: For example, say your app lets users view all the fire hydrants (fire hydrant features) in a city
through a hydrants table. You now want users to be able to look up the inspection reports for a
given hydrant that are stored in a different table, say hydrant-inspections. If the two tables
are related, you can query the hydrants table for related features of a given hydrant, and the
query will return results from the hydrant-inspections table.
The following steps describe how to set up the above scenario of searching for inspection reports (related features) of a given hydrant
(feature). Note that you could also search for all fire hydrants inspected during a particular inspection.
Search for related features

1. Add the participating tables to the same map. If a table is a spatial table, you can create a feature layer from it and add it to the
list of the map's operational layers. If a table is non-spatial, you must add it to the list of the map's tables. Similarly in a
disconnected scenario, you'd add the tables to the map but you'd first download them into a mobile geodatabase.
Note that while the participating tables must be in the same map, they do not have to be loaded.
2. If you want to return only features from the table that participates in the provided relationship, set input parameters as described
in this step. Otherwise, skip to step 4.
a. Create a RelatedQueryParameters object.
b. Provide a relationshipInfo from the ArcGISFeatureLayerInfo class in the arcgisservices package. Any time
you create a RelatedQueryParameters object, you must also provide a relationshipInfo that defines the
relationship.
c. You can provide additional input parameters, such as a whereClause, to further filter the related features, whether or not
you wish to receive the geometry of the related features. You may also specify a list of fields to sort the results in.
3. Call the query method on the table containing the feature for which you want to search for related features as described in this
step, then skip to step 5. In the above hydrant example, if you want users to be able to view all inspection reports for a particular
hydrant, you would query the hydrants table.
In a connected scenario, whether a query is online or local depends on the feature request mode of the related table:
For On_Interaction_Cache, the query can be online or local as features are cached
For On_Interaction_NoCache, the query is always online
For Manual_Cache, the query is always local
In a disconnected scenario, all queries are local.
4. If you want to return related features from all participating relationships of a given feature, perform the search without any query
parameters.
5. Handle the returned query results.
Query operations are asynchronous and get called back with the query results and an optional error, if any. The results are an
array of RelatedFeatureQueryResult objects, one for each of the related table queried. If more than one table was queried,
multiple query operations may be performed internally and the query method is called back when all such operations have
completed.
Each RelatedFeatureQueryResult contains a list of related features that can be enumerated over. The query result also
contains relatedTable in addition to relationshipInfo because multiple instances of the same table can be added to the
map, for instance with different scale level visibility, definition expression, and so on. In such cases, a query is performed on each
table instance and a RelatedFeatureQueryResult object is returned for each.
The query result also contains:
The feature for which the related features were queried
Information on whether the resulting related feature count exceeded the maximum limit supported by the server

Editing
Editing means that you can add, update, and delete features. For more information on features see Features and graphics. Updating
features includes modifying feature attributes (changing the value of a feature's fields according to the type and range of values allowed);
modifying feature geometry (such as moving a point feature or reshaping a polygon or polyline feature); and if available adding, updating,
and deleting feature attachments (related files such as pictures, documents or videos). Feature layers inside your map's operational layers
collection provide the basis for editing. Feature layers store and edit their data using database tables called feature tables.
Editing features is supported in a number of workflows, described below:
Online feature service editing, where a table is created from the service, edits are made, and the changes are applied back to the
service as soon as the user has finished the edit operation. Suitable for multi-user editing scenarios.
Offline feature service editing and sync, where a local geodatabase is created from a sync-enabled feature service before going
offline, tables are retrieved from the geodatabase while offline, edits are made, then changes are applied back to the service when
the device is back online again (and server changes are optionally synchronized back). Suitable for multi-user offline workflows.
See Create an offline map for more information on offline workflows.
Static feature collection editing, where tables are created from the features in the map or a portal item, edits are made and
changes are saved back into the map or portal item. This is a suitable workflow for sharing static data to lots of clients, but should
not be used to edit data across a number of clients or to share data that changes frequently.
See Perform edits for more information.
Creating feature services for your data

Feature services provide the symbology, feature geometry, and set of attribute fields (schema) for your features. Feature services contain
service layers (feature data) and tables (nonspatial, tabular data) that you edit via a feature table for both online and offline feature service
workflows. Feature services allow for scalable multi-client editing for data which changes over time. For more information about feature
services, see What is a feature service?
Before you build an app that performs feature service editing, you need a feature service that exposes the layers you want to edit. There
are various ways to publish a feature service.
You can login to your organization's portal and publish features from a variety of data sources such as CSV files, GeoJSON,
shapefiles, feature collections, or file geodatabases. All of these options and their steps are outlined in the publish hosted feature
services topic.
You can publish feature services using ArcGIS Desktop. This involves setting up a map document, and defining a feature class
schema or importing an existing feature class. Optionally, you can define feature templates to make it easy for the app's end user
to create common features. You can then publish the map as a service to ArcGIS Online or ArcGIS Enterprise. For offline
workflows, you must enable the Feature Access capability and ensure that the service is sync-enabled.
You can create a feature layer using the ArcGIS for Developers site. Log in to the site using your organization account or your free
developers subscription. Access the Layers tab and click the Create New Layer button. For offline workflows, follow the
instructions to create the new feature layer ensuring that you have checked the box to enable the layer to be taken offline to allow
it to be viewed, edited, and synchronized. After creating a layer you can add data to it in the ArcGIS Online Map Viewer.
However you publish your service, REST URLs (endpoints) are created to both a map service and a feature service. Use these URLs to
reference the services in your app. The map service endpoint can be used for read-only access to features (viewing only), so make sure to
reference the feature service endpoint for editing. Offline editing workflows require sync-enabled feature services. A sync-enabled feature
service allows you to generate a geodatabase for offline use, and gives you the ability to sync your local edits back to the service.
Note: ArcGIS 10.2.2 for Server or later, or hosted services in ArcGIS Online, are required to publish
sync-enabled feature services.
Feature collections
Feature collections are static collections of features stored as JSON inside the map or a referenced portal item. Many ArcGIS Online
operations create feature collections, such as adding Map Notes to your map, importing shapefiles, importing GPX files or sharing analysis
results as items. There are two representations of feature collections which are important to understand when it comes to editing and
saving features.
1. Feature collections in a map - this is where the feature JSON is saved in a single map as a feature collection layer.
2. Feature collections as portal items - this is where the feature JSON is saved as a portal item. These feature collections can be
referenced in multiple maps.

The workflow for editing the features for both types of feature collections is the same. However, there are differences when persisting the
edits so that other users can see them. Feature collections in a map will be persisted when the map is saved, others who open the map
will see the edited features. Feature collections stored as portal items will not be saved when a map is saved, you will have to update or
save a portal item to ensure that others will see the edited features.
Feature collections should not be used for multi-user editing scenarios, as clients could easily hold on to older versions of the feature
collection and overwrite each others changes. Use feature services for these types of workflows.
Perform edits
Fine grained control over editing operations is available by using the editing API, allowing you to create and edit features, add, edit or
remove feature attachments, and edit the geometry of features.
For some feature service editing workflows, it's a good idea to have an analyst using ArcGIS Desktop periodically review the edits to verify
data integrity. Although components in the API can perform some data validation, other tasks such as validating topologies cannot be
performed using ArcGIS Runtime SDK alone.
Editor tracking
The editing framework supports the tracking of specific edits to features. This happens by tracking the following feature properties:
Which user created the feature
Date and time the feature was created
Which user last edited the feature
Date and time the feature was last edited

Edit features
ArcGIS Runtime supports editing workflows that leverage the use of features. A feature is a persisted piece of data (essentially a row in a
table) that includes a geographic location (shape) as well as attributes that further describe it, such as Name, Area, Population,
ZoningCode, and so on. Your app can include the ability to add and delete entire features or to make edits to existing feature geometry
and attributes. If your features have attachments (images or text files, for example) or related records in another dataset, that information
can be edited as well.
Features can be hosted in an online service, stored locally in a database, or saved in a map or portal item. How your features are stored
affects how you make and manage edits to them in your app. For more information on features and where they come from, see Features
and graphics.
Editing overview
Your apps can edit features while online (connected to the network and using data hosted online) or offline (without a network connection
and using local data). You can edit features from a service, a geodatabase, or a feature collection. For an introduction see Editing. While
all editing workflows are described in this topic, note that there is no difference in the code that actually makes the edits (adding, deleting,
or updating features, in other words).
Features from an ArcGISFeatureTable return ArcGISFeature objects which implement the loadable pattern for increased efficiency.
When fetching ArcGISFeature objects for rendering and query purposes, a minimum set of required fields is returned, such as
identifiers, geometry, fields used for symbolizing, and so on. When you want to edit the feature, you must load it first, otherwise the edit
operation will fail.
Note: When querying features from an online service, you have the option to return your results as
loaded features so all fields are immediately available and edits can be performed.
Feature editing is supported for a number of workflows. The developer patterns for each is described below:
The online feature service editing workflow is:
1. Create a service feature table from a feature service using the REST endpoint (URL, in other words) to identify the features you
want to work with, or open a map which already contains a service feature table via a feature layer.
2. Perform any edits against the service feature table (add, update, and delete features and feature attachments).
3. Apply your edits to the feature service right away.
The offline feature service editing workflow is:
1. Generate a local runtime geodatabase using a sync-enabled feature service while the user is onlineas described in Create an
offline map.
2. Create a geodatabase feature table from the local geodatabase. If this is for a connected feature layer already in a map, then that
layer will need to be switched out with a new feature layer created with this table.
3. Perform any edits against the geodatabase feature table (add, update, and delete features and feature attachments).
4. Synchronize your edits with the service once you have a network connection, as described in Sync offline edits.
The static feature collection editing workflow is:
1. Create a new feature collection or open a map which already contains a feature collection via a feature collection layer.
2. For new feature collections, create a new feature collection table and add it to the feature collection. For feature collections from a
map, access a feature collection table from the feature collection.
3. Perform any edits against the feature collection table (add, update, and delete features).
4. For feature collections which are to be stored in the map, save the map. For feature collections to be saved as a portal item, save
the feature collection as a portal item.
Create a feature table

Before you can edit features, you need to obtain feature data from a feature table.
In a connected workflow, the type of feature table you use and edit is a ServiceFeatureTable. In a disconnected workflow, the type of
feature table you use and edit is a GeodatabaseFeatureTable. Both classes inherit from ArcGISFeatureTable, which itself inherits
from FeatureTable.
For working with features by value, the type of table you use is FeatureCollectionTable. Feature collection tables do not contain
attachments and inherit directly from FeatureTable.

The methods to add, update, and delete features are common to FeatureTable and the methods for updating attachments are provided
by ArcGISFeatureTable. Therefore, all the methods you have at your disposal to edit features from a feature service are available both
online and offline. The ServiceFeatureTable used in connected editing provides additional methods to apply feature edits and
attachment edits back to the service. You should apply any edits to the service as soon as you have made them on your feature table.
Feature service edit capabilities

When working with features from a feature service online or offline, additional edit capabilities are defined to allow or prevent certain
types of edits to features. You should check these capabilities to determine what editing capability is available. You may also need to
verify ownership-based access is available for each edit you want to complete.
You can use properties on a feature table to find out what type of editing is supported.
Is editable: indicates if the table is editable.

Edit capabilities: describes the types of edits that are allowed for the table, such as adding, deleting, or updating features, for
example.
A feature service might also use ownership-based access control, which means edits to particular features are only available to certain
users. You can check ownership-based access using properties on the feature table.
Can add: whether or not the current user can add a feature to the table.
Can delete: whether or not the current user can delete a feature from the table.
Can update: whether or not the current user can edit an existing feature.
Online feature services

In an online workflow, you need a service feature table created from a feature service. If you have opened a map, you can use a feature
layer and retrieve its feature table and check it is of the correct type. For new layers, you can create a service feature table with the
feature service URL and then create a feature layer. Once the feature layer is in a map and displayed in a map view, features in the map
extent are added to the service feature table and can be edited. As you pan and zoom the map (that is, change the map extent), more
features are retrieved from the feature service and added to the service feature table. If you are not using a map or you want to pre-
populate your table with a fixed set of features, use the populateFromService method.
Note: The number of features you see when you initially visit a new area of the map is limited by the
feature service's maximum record count property (the default value for this property is 1,000).
Pan and zoom to query the service for more features. Once features are retrieved from the
service and visible in your map, they are available in your service feature table for editing and
querying.
For example, the code below instantiates a new service feature table from a URL.
// Create a feature table from a feature service
ServiceFeatureTable serviceFeatureTable = new ServiceFeatureTable("http://sampleserver6.arcgisonline.com/arcgis/rest/services/Sync/SaveTheBaySync/FeatureServer/0
Because they rely on a remote service to properly initialize their state, service feature tables use the Loadable pattern. You can load a
service feature table and check its load status before adding it to the map, which allows you to handle load failure and to retry loading
the table if necessary. However, if you use the feature table to create a feature layer and add that to a map or scene, the table will
automatically attempt to load when the layer is displayed.
Note: Features in a service feature table are Loadable for added efficiency; before editing your
feature ensure it is loaded otherwise the edit operation will fail.

Offline feature services

In an offline workflow, you need to first generate a runtime geodatabase from a sync-enabled feature service while you have a network
connection. Follow the geodatabase generation process described in Create an offline map. This process results in a geodatabase
stored locally on disk. The geodatabase contains one or more feature tables, one for each service layer or service table that you
requested in the geodatabase generation process. When offline, create geodatabase feature tables (GeodatabaseFeatureTable
class) from the geodatabase, for example, on application load. The features stored in the geodatabase tables are available for editing
whether you display them in a layer or not, but in most cases you'll want to create feature layers to display them for editing. Also,
consider generating an offline basemap to give the feature data some geographical context when your users edit offline.
Caution: You can also generate a runtime geodatabase using ArcGIS for Desktop, but these
geodatabases are read-only.
The following code sample shows how to create a feature table from a local geodatabase:
Note: The Geodatabase loading will fail if the geodatabase file cannot be found. The code above
shows how to check the load error for this or any other problems.
// Open a portal item containing a feature collection

final PortalItem collectionItem = new PortalItem(portal, featureCollectionItemId);
collectionItem.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
if (collectionItem.getLoadStatus() == LoadStatus.LOADED) {
// Verify that the item is a feature collection
if (collectionItem.getType() == PortalItem.Type.FEATURE_COLLECTION) {
// Create a new FeatureCollection from the item
FeatureCollection featureCollection = new FeatureCollection(collectionItem);
// Create a layer to display the collection and add it to the map as an operational layer
FeatureCollectionLayer featureCollectionLayer = new FeatureCollectionLayer(featureCollection);
featureCollectionLayer.setName(collectionItem.getTitle());
map.getOperationalLayers().add(featureCollectionLayer);
}
}
}
});
collectionItem.loadAsync();
Static feature collections

For working with static feature collections, you either need a map which already contains a feature collection layer, or you need to create
a new feature collection layer.
You can create a FeatureCollectionTable PortalItem that contains a feature collection. You can then create a
FeatureCollectionLayer from that table.
// Open a portal item containing a feature collection
final PortalItem collectionItem = new PortalItem(portal, featureCollectionItemId);
collectionItem.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
if (collectionItem.getLoadStatus() == LoadStatus.LOADED) {
// Verify that the item is a feature collection
if (collectionItem.getType() == PortalItem.Type.FEATURE_COLLECTION) {
// Create a new FeatureCollection from the item
FeatureCollection featureCollection = new FeatureCollection(collectionItem);
// Create a layer to display the collection and add it to the map as an operational layer
FeatureCollectionLayer featureCollectionLayer = new FeatureCollectionLayer(featureCollection);
featureCollectionLayer.setName(collectionItem.getTitle());
map.getOperationalLayers().add(featureCollectionLayer);
}
}
}
});
collectionItem.loadAsync();
Add layers to the map

You can display the features contained in the feature table by adding them to a feature layer in the map. Create feature layers from any
feature table then add them to a map. A feature layer, once added to a map, takes care of displaying the features contained in your
feature table within the map extent currently displayed. When features in the table are edited, the edits are visible right away in the
associated feature layer, but not immediately committed back to the feature source.
You can create a layer from a (local or online) feature table and add this to your map.
// Create feature layer from the table
FeatureLayer featureLayer = new FeatureLayer(featureTable);
// Add the layer to the map

map.getOperationalLayers().add(featureLayer);

You will be able to see features like this on your map.
Add features
For creating new features, it's common for an app to allow the user to click the map to specify a new feature's location. You can provide
this capability by listening to a click event on your map view, which in turn will call a function for adding a new feature.
Create a new class that inherits from DefaultMapViewOnTouchListener, and set an instance of this class onto the map view by
calling MapView.setOnTouchListner. In the overridden onSingleTapConfirmed method of your class, you can translate the event
parameters from a point in screen coordinates to a point in map coordinates, and then use this location for the new feature.
@Override
// create a screen point from the mouse event
android.graphics.Point screenPoint = new android.graphics.Point((int)e.getX(), (int)e.getY());
// convert this to a map point

Point mapPoint = mapView.screenToLocation(screenPoint);
// add a feature at this point
addFeature(mapPoint);
return true;
}
To add features to a feature table, create a new feature from geometry (for example, point, line, or polygon), create attributes for the new
feature, and then call add feature. This adds the feature to a table stored locally on your device. Even if you're editing a service feature
table, your edits are initially stored in a table on the client. You must explicitly apply service feature table edits to commit them to the
parent feature service.
Note: All features you add or update in a feature service should have valid geometry. Creating
features with empty (null) geometry can cause unexpected issues when working with features
in ArcGIS Runtime offline editing workflows.
It is good practice to write code which checks if the addFeatureAsync and applyEditsAsync methods have been successful, as
shown in the code below.

// check features can be added, based on edit capabilities

// create the attributes for the feature
java.util.Map<String, Object> attributes = new HashMap<String, Object>();
attributes.put("type", 1); // Coded Values: [1: Manatee] etc...
attributes.put("confirmed", 1); // Coded Values: [0: No] , [1: Yes]
attributes.put("comments", "Definitely a manatee");
// Create a new feature from the attributes and an existing point geometry, and then add the feature
Feature addedFeature = featureTable.createFeature(attributes, mapPoint);
final ListenableFuture<Void> addFeatureFuture = featureTable.addFeatureAsync(addedFeature);
addFeatureFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
// check the result of the future to find out if/when the addFeatureAsync call succeeded - exception will be
// thrown if the edit failed
addFeatureFuture.get();
// if using an ArcGISFeatureTable, call getAddedFeaturesCountAsync to check the total number of features
// that have been added since last sync
// if dealing with ServiceFeatureTable, apply edits after making updates; if editing locally, then edits can
// be synchronized at some point using the SyncGeodatabaseTask.
if (arcGisFeatureTable instanceof ServiceFeatureTable) {
ServiceFeatureTable serviceFeatureTable = (ServiceFeatureTable)featureTable;
// apply the edits
final ListenableFuture<List<FeatureEditResult>> applyEditsFuture = serviceFeatureTable.applyEditsAsync();
applyEditsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
final List<FeatureEditResult> featureEditResults = applyEditsFuture.get();
// if required, can check the edits applied in this operation
showMessage(String.format("Number of edits: %d", featureEditResults.size()));
}
}
});
}

// executionException may contain an ArcGISRuntimeException with edit error information.
if (e.getCause() instanceof ArcGISRuntimeException) {
ArcGISRuntimeException agsEx = (ArcGISRuntimeException)e.getCause();
showMessage(String.format("Add Feature Error %d\n=%s", agsEx.getErrorCode(), agsEx.getMessage()));
} else {
}
}
}
});
Tip: When adding new features, it is good practice to ensure the geometry of the new feature is not
null. If the location of a feature is not yet known, you may want to use an empty geometry.
Select features
In an editing app, a common workflow is for the user to choose features to edit by selecting them with a query or interactively on the map.
Features in a feature layer can be selected, which results in them being highlighted in the map view. You can select features based on
spatial relationships (sample points located inside the forest boundary polygon), using attribute criteria (pipes with a material_type attribute
of 'pvc'), or both (parcels outside the city limits with a zoning code of 'COM'). You can also get selected features from a layer, after letting
the user make an interactive or custom selection, for example.
In editing workflows, features are typically selected for tasks such as deleting or updating.

The code sample below shows how to select a set of features that are in a radius of 5000m of a supplied point.
// create a buffer from the point
final Polygon searchGeometry = GeometryEngine.buffer(mapPoint, 5000);
// create a query to find which features are contained by the query geometry
QueryParameters queryParams = new QueryParameters();
queryParams.setGeometry(searchGeometry);
queryParams.setSpatialRelationship(QueryParameters.SpatialRelationship.CONTAINS);
// select based on the query
final ListenableFuture<FeatureQueryResult> selectFuture =
arcGisFeatureTable.getFeatureLayer().selectFeaturesAsync(queryParams, FeatureLayer.SelectionMode.NEW);
// if required, can listen to the future to perform an action when features are selected
You can also select specific features using the select feature method and passing in a single feature.
Update features
Feature updates include moving or reshaping a feature's geometry or making edits to attribute values. As with all editing operations the
changes are not automatically committed to the features source, it is the developer's responsibility to do this.
The code snippet below takes a set of selected features and updates an attribute and changes the geometry to a new location.
// get selected features from the layer for this ArcGISFeatureTable
final FeatureLayer featureLayer = arcGisFeatureTable.getFeatureLayer();
final ListenableFuture<FeatureQueryResult> selected = featureLayer.getSelectedFeaturesAsync();
FeatureQueryResult features;
try {
features = selected.get();
} catch (ExecutionException | InterruptedException e) {
return;
}
// check there is at least one selected feature
if (!features.iterator().hasNext()) {
showMessage("No selected features");
return;
}
// get the first selected feature and load it
final ArcGISFeature feature = (ArcGISFeature) features.iterator().next();
feature.loadAsync();
feature.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
// now feature is loaded we can update it; change attribute and geometry (here the point geometry is moved North)
try {
feature.getAttributes().put("confirmed", 1);
Point currentLoc = (Point) feature.getGeometry();
Point updatedLoc = new Point(currentLoc.getX(), currentLoc.getY() + 50000, mapView.getSpatialReference());
feature.setGeometry(updatedLoc);
// update the feature in the table
arcGisFeatureTable.updateFeatureAsync(feature).get();
ServiceFeatureTable serviceFeatureTable = (ServiceFeatureTable) arcGisFeatureTable;
// can call getUpdatedFeaturesCountAsync to verify number of updates to be applied before calling applyEditsAsync
final List<FeatureEditResult> featureEditResults = serviceFeatureTable.applyEditsAsync().get();
// if required, can check the edits applied in this operation by using returned FeatureEditResult
checkUpdateResults(featureEditResults);
}
return;
}
}
});
Delete features
You can delete several features from a feature table using the delete features method that accepts a list of features, or just a single feature
with a call to delete feature. As with all editing operations the changes are not automatically committed to the features source, it is the
developer's responsibility to do this.

// get selected features from the layer for this ArcGISFeatureTable

final FeatureLayer featureLayer = arcGisFeatureTable.getFeatureLayer();
final ListenableFuture<FeatureQueryResult> selected = featureLayer.getSelectedFeaturesAsync();
FeatureQueryResult features;
try {
features = selected.get();
// get selected features

if (!features.iterator().hasNext()) {
showMessage("Use Edit Features > Select features first");
return;
}
// delete the selected features
arcGisFeatureTable.deleteFeaturesAsync(features).get();
//if dealing with ServiceFeatureTable, apply edits after making updates; if editing locally, then edits can
// can call getDeletedFeaturesCountAsync() to verify number of deletes to be applied before calling applyEditsAsync
}
return;
}
Feature attachments
Attachments are files you associate with a feature, including text, images, videos, and so on. Attachments are only available for features
from an ArcGIS feature table. You might want to attach a photograph to a parcel feature, for example, to show a picture of the property.
Attachments on a feature are manipulated using the following methods on the ArcGIS feature class.
Method Description
add attachment Adds a new attachment to a feature
delete attachment Deletes a single existing attachment
delete attachments Deletes a list of existing attachments
update attachment Updates an existing attachment
fetch attachments Accesses the attachments for a feature
ArcGIS feature inherits from the feature class, so you can cast from feature to ArcGIS feature if needed. Prior to adding, updating or
deleting features it is good practice to make sure that you have permission to perform one of these operations. This is done by using the
can edit attachments property. Once you have performed your attachment edits, these are applied to the feature using the update feature
method and finally the feature needs to be applied to the service by calling the apply edits method on your feature table.
// get feature as an ArcGIS Feature so we can add attachments
ArcGISFeature agsFeature = (ArcGISFeature) feature;
// add the attachment
File attachmentFile = new File(fileDirectory, "Image.jpg");
agsFeature.addAttachmentAsync(Util.getBytes(attachmentFile), "image/jpg", attachmentFile.getName()).get();
// save the attachments in the feature
arcGisFeatureTable.updateFeatureAsync(agsFeature).get();
// and/or ArcGISFeatureTable.getUpdatedFeaturesCountAsync
checkAttachmentResults(featureEditResults);
}

Relate features
You relate a feature in one table to a feature in another table for a variety of reasons, such as to allow your users to view information in
one table for features in another. For example, you might want a user to be able to view fire hydrant inspection reports from a reports table
and general fire hydrant information from hydrants table for the same set of fire hydrants.
When you relate features, you're editing them because the relate operation changes the attribute of the destination feature. The relate
operation associates the two tables by setting up a keyField attribute in the destination feature based on the corresponding origin feature.
The keyField value is the origin table feature's primary key or global ID. In this hydrant example, relating a hydrant and an inspection
report adds the keyField value of the hydrant feature in the hydrants table (origin table) to the corresponding (hydrant) field in the report
feature in the reports table (destination table).
The tables of the two features you want to relate must be in a table relationship with each other (must be related tables). Table
relationships are created using ArcGIS Desktop.
The pattern for editing a feature to relate it to another is the same as for editing a "regular" feature, as described in Edit features, whether
the feature is the origin feature in a table relationship or the destination feature. When tables participate in a table relationship like this, you
can perform additional editing-oriented operations not described in Edit features but described on this page:
Relate features
Unrelate features
Validate relate constraints
Relate two features

You use the relate method to relate a feature in one table to a feature in a different table as long as the two participating tables have a
valid relationship between them. The relate method sets up the foreign key (KeyField) value on the destination feature and can be called
on either the origin or destination feature.
Relating features is akin to changing the attributes of feature; it's synchronous and done in memory. A feature once related must be added
or updated to the table using addFeatureAsync(feature) or updateFeatureAsync(feature) for changes to be committed.
It's important to know the cardinality of the table relationship when you relate features.
Unrelate features
You may want to unrelate two already related features. For example, when a feature has a constraint violation, such as an invalid
cardinality, you may want to undo the last relate operation that caused the violation. Unrelating features resets the key field of the
destination feature. Like the relate method, unrelate is also synchronous and is done in memory. Therefore
addFeatureAsync(feature) or updateFeatureAsync(feature) must be called for changes to be committed to the table.
Validate the relationship constraints of a feature

You can check if a given feature violates any relationship constraints (for example, when a hydrant inspection report, is being added by a
user), such as cardinality violations. In 1:1 relationships, if an origin feature is already related to a destination feature, no other destination
feature can be related to it. In 1:n relationships, a destination feature can be related to only one origin feature (while the other way around
is permitted). For more info on cardinality and types of relationships, see Relationship class properties in the ArcGIS Desktop help.
Note that an update operation on a feature succeeds even if a relationship constraint has been violated by the edit. This is consistent
handling with ArcGIS Server and ArcGIS Desktop, which do not enforce cardinality violations. ArcGIS Desktop provides a Validate
Feature tool, which allows you to recover from violations in a back office operation after applying edits or syncing, if you choose to do so.
See Validating features and relationships in ArcMap for more information. However, if you wish to check for violations in your app and
recover from them, you can use the validate method.
Another type of constraint violation captured by the validatie method occurs in a composite relationship when an orphan feature is added
to the destination table without relating it to an origin feature. You can recover from this violation by relating the orphaned destination
feature to a valid origin feature.
Tip: Performance tip: If the related features are not local to the device, the validate method makes
network calls to query for them. As a result, it can negatively impact performance when used
on a number of features. This hit to performance is why edit operations such as add, update,
and delete do not proactively check for relationship constraint violations.

Additional information
Getting related tables for a layer or table on the map returns only those tables on the map. Similarly related queries require both origin and
destination table/layer to be present on the map. For tables not on the map, you can query them using regular query operations but cannot
use related queries. You can also view what relationships the tables participate in.
All the tables participating in a relationship must be present in the data source. ArcGIS Runtime supports related tables in the following
data sources:
ArcGIS feature service
ArcGIS map service
Geodatabase downloaded from a feature service
Geodatabase in a mobile map package
Two participating tables can have one of the following cardinalities: one-to-one, one-to-many, or many-to-many.
When defining relationships, one table must be origin and the other destination. A table can participate in more than one relationship. A
table can play a destination role in one relationship and origin in another, resulting in nested relationships.
Simple and composite workflow-based relationships are supported:
In a simple relationship, features in the destination table are independent to features in the origin table. For example, a
transformer and an electric pole may be related but they can also exist their own. Deleting an origin feature resets the keyField
of the relationship to NULL in the destination feature.
In a composite relationship, each feature in the destination table is expected to be related to an origin feature. In other words, any
orphan destination features are considered a violation of the relationship. For example, a building and its mailbox must be related.
While the building (origin) can exist on its own, a mailbox (destination) must be related to a building. When an origin feature is
deleted, the destination feature should also be deleted. This is known as a cascade delete.

Edit geometries
You edit geometries when you want to change existing geometries or create new ones. However, Geometry objects are immutable. To
edit geometries, use geometry builders.
Geometry builders
Geometry builders (or builders for short) create or change geometry. A geometry builder contains the same things a geometry
containsvertices, segments, and partsallowing its state to be changed as needed. You can create new geometries at any point from
the builders current state. A builder is available for each type of geometry. Each builder exposes the appropriate methods for modifying a
specific type of geometry. In the case of PolylineBuilder and PolygonBuilder that share many members, both inherit from
MultipartBuilder, which in turn inherits from GeometryBuilder. Other builders inherit directly from GeometryBuilder.
Because builders represent geometries under construction, they do not use the same immutable collection types as those returned from
members of the geometry classes containing a part, part collection, or point collection. Instead, builder members use mutable collection
types.
Modify existing geometry

To modify an existing geometry, complete the following steps:
1. Create the appropriate type of builder and initialize its state by passing in the geometry to be edited to the constructor. For
example, modify a polyline by creating an PolylineBuilder and pass in the existing polyline to the builder.
2. Use the methods on the builder to change the builders state. For example, add a new part to a polyline or remove a point from a
multipoint.
3. Call toGeometry to return a new immutable geometry from the current state of the builder.
4. Repeat steps 2 and 3 as many times as necessary. By keeping a reference to the builder, you can repeatedly modify the builder
state as many times as required, for example, to update a temporary graphic to display the current state to the user.
The following code demonstrates an PolylineBuilder held as a member variable in a custom geometry editor class. The
addPointToEnd method adds another vertex to the end of the polyline and can be called when a user taps at the required location. Each
time an update is made, the drawLatestGeometry method can be used to update an GraphicsOverlay with the new state of the
geometry created so far.
class roadGeometryEditor {
PolylineBuilder polylineBuilder = null;
Graphic temporaryGraphic = null;
// Builder held as member variable
public roadGeometryEditor(Feature roadFeature) {
// Set initial state of the builder based on an existing geometry
polylineBuilder = new PolylineBuilder((Polyline) roadFeature.getGeometry());
// Set up a temporary graphic to draw the geometry
SimpleLineSymbol roadSymbol = new SimpleLineSymbol(SimpleLineSymbol.Style.SOLID, 0xFFFF0000, 1f);
temporaryGraphic = new Graphic(polylineBuilder.toGeometry(), roadSymbol);
mapView.getGraphicsOverlays().get(0).getGraphics().add(temporaryGraphic);
}
public void addPointToEnd(Point newEndPoint) {
// Change the geometry
polylineBuilder.getParts().get(0).addPoint(newEndPoint);
}
public Polyline getCurrentGeometry() {
// Get latest state of the geometry
return polylineBuilder.toGeometry();
}
public void drawLatestGeometry(GraphicsOverlay editorOverlay) {
// Update the user's view of the geometry
temporaryGraphic.setGeometry(getCurrentGeometry());
}
}
You don't have to initialize a builder with an existing geometryyou can also use builders to create entirely new geometries.

When creating geometries, use isValidSketch to determine when a builder contains enough information to convert the builders state
successfully to a geometry.
Tip: When editing geometries using locations from the screen, and the map is a wraparound map,
you may need to normalize the geometry before you save it to a geodatabase or use it in tasks
or other operations.
Spatial reference management
When working with geometries and builders, the following principles apply with regard to their SpatialReference:
The spatial reference of a builder is always set during builder instantiation and cannot be changed. It can be set to null.
You don't need to set the spatial reference of points or segments passed into methods on geometries, collections, or builders. If
the spatial reference is not set, the input coordinates will be assumed to be in the same spatial reference as the geometry,
collection, or builder.
It is an error to add a point or segment having a different spatial reference than that of the geometry, collection, or builder you're
adding it to, and an exception will be thrown indicating a mismatch. This includes the case where the spatial reference of the
geometry, collection, or builder is null and that of the added point or segment is not null.
A Point or Segment returned from a geometrys member will have the same spatial reference as the geometry it came from.
When creating a new Polygon using the constructor, the API first sets the spatial reference parameter for the new Polygon, then
the points are added. If there is a mismatch between the spatial reference of the new Polygon and the points being added, this is
an error and the constructor will throw an exception.
Tip: If required for your workflow, use the projectProject method on GeometryEngine to
project points to a different spatial reference.
Multipoint geometries
Use MultipointBuilder to modify an existing Multipoint. Get and modify the mutable point collection from the builder's
getPoints method, working directly with this collection to add, remove, or insert points. Call toGeometry to instantiate a new
immutable instance of Multipoint from the current state of the builder.
MultipointBuilder builder = new MultipointBuilder((SpatialReference) null);
PointCollection points = builder.getPoints();
points.add(userAddedPoint1);
points.add(userAddedPoint2);
//...
Multipoint multipoint = builder.toGeometry();
Multipart geometries
Polygons and polylines can have multiple parts. You can use a multipart polygon to define a group of islands, or a multipart polyline to
represent a non-continuous linear feature. Due to the geometric complexity of polygons and polylines, PolylineBuilder and
PolygonBuilder are used more frequently than other builders such as PointBuilder. Using the methods on these collections, you
can build polygons and polylines by adding points. As with multipoint geometries, use the PointCollection to modify multipart
geometries. Or, you can edit the segments in multipart geometries.
// Create a builder, set the Spatial Reference
PolylineBuilder polylineBuilder = new PolylineBuilder(SpatialReferences.getWgs84());
Part firstPart = new Part(SpatialReferences.getWgs84());
firstPart.add(new LineSegment(0, 0, 0, 7)); // A LineSegment (0,0) -> (0,7)
firstPart.add(new LineSegment(new Point(0,7), new Point(3,6))); // A LineSegment (0,7) -> (3, 6)
polylineBuilder.addPart(firstPart);
Polyline polyline = polylineBuilder.toGeometry(); // Convert the current state of the builder to a Polyline

You can also edit using a mix of point-based and segment-based methods.
Here is an example of mixing pont-based and segment-based methods.
Part firstPart = new Part(SpatialReferences.getWgs84());
polygonBuilder.getParts().add(firstPart);
firstPart.addPoint(0, 0); // Add an initial point
firstPart.addPoint(0, 7); // Adjusts the Part so that it has one LineSegment (0,0) -> (0,7)
firstPart.add(new LineSegment(0, 7, 5, 0)); // Adds a new LineSegment (0,7) -> (5,0))
Editing parts
Use the PartCollection methods to add, remove, or insert Parts to a MultipartBuilder. A point-based helper method
addPart(Iterable<Point>) is available for the common task of adding an existing set of Points to a PartCollection as a new
Part.
PartCollection partCollection = new PartCollection(SpatialReferences.getWgs84());
Part part = new Part(SpatialReferences.getWgs84());
part.addPoint(new Point(78.75000000000003, 66.86936993741895));
part.addPoint( new Point(56.25000000000001, 67.22037237346096));
partCollection.add(part);
polygonBuilder.getParts().addAll(partCollection);
Editing parts using points

The Part is a collection of segments. Working with the point-based method results in defining an ordered series of vertices and, as a
consequence, creating straight LineSegments within the builder between those vertices.
The following principles apply when editing parts using points:
Use addPoint(int, Point) to insert a vertex at a specific index into a part. This will increase the number of segments in the
part by one. Connections between segments are preservedadjacent segments touch at their starting and ending vertices.
polygonBuilder.getParts().get(0).addPoint(0, new Point(56.7, 66.51326044311182));
Use removePoint(int) to remove the vertex at a specific index from a part. The number of segments decreases by one, and
connections between segments are preserved.
polygonBuilder.getParts().get(0).removePoint(0);
You can add a new vertex to the end of a MultipartBuilder using the addPoint method. This adds a vertex to the end of
the last part in the builder. If there are no parts in the builder, this method will create a new part first, then add the new vertex.
You do not need to close a part belonging to a polygon.
Caution: When working with point-based methods that take an index parameter, keep in mind that this is
the index of the specific vertex, which is a different index than that used when working with
segments. This is because where a segments ending vertex is at the same location as the
starting vertex of the next segment, it is represented by a single Point in point-based methods.
Editing parts using segments

When you work with the segments in a part, you specify each segments starting and ending vertex. This differs from editing with points,
where sequential vertices define a series of adjacent segments. Specifying starting and ending vertices for adjacent segments can
result in gaps, where the end vertex of one segment does not have exactly the same location as the start vertex of the next adjacent

segment. Gaps are not automatically corrected in the builder until you access the builders call toGeometry member to instantiate a
new polyline or polygon. At that time, if any adjacent segments in the part do not touch, a short connecting segment will be added
automatically to the new geometry to ensure the part forms a continuous edge in the new geometry. To avoid automatically adding
segments, re-use the location of the end vertex of the previous segment as the start vertex of the subsequent segment, and use insert,
remove, and add methods with care.
Similar to geometries, all segments are immutable and are created by using constructors or static factory methods. Unlike geometries,
there are no builders for segments. Segments are fully defined when created, setting all properties at once.
The following principles apply when editing parts using segments:
Use add(int, Segment) to insert a segment into a part at a specific index. This increases the number of segments in the
part by one. Be careful: this will result in a gap at either end of the new segment if the start and end vertices do not share a
location with the preceding and following adjacent segments, respectively.
LineSegment lineSegment = new LineSegment(new Point(78.75000000000003, 66.86936993741895), new Point(56.25000000000001, 67.22037237346096));
polygonBuilder.getParts().get(0).add(lineSegment);
Use remove(int) to remove a segment from a part. If you remove anything other than the first or last segment in the part, this
will result in a gap between the remaining segments. The number of segments decreases by one, and connections between
segments are preserved.
polygonBuilder.getParts().get(0).remove(0);
Because segments are immutable, existing segments in a part cannot be changed. However, you can replace the existing
segment at a specified index with a new segment by calling set(int, Segment).
LineSegment lineSegment = new LineSegment(new Point(78.75000000000003, 66.86936993741895), new Point(56.25000000000001, 67.22037237346096));
polygonBuilder.getParts().get(0).set(0, lineSegment);
You do not need to close a part belonging to a polygon.
Caution: When working with segment-based methods that take an index parameter, keep in mind that
this is the index of the segment within the part and is a different index than that used when
working with point-based helper methods. If a segment's ending vertex is at the same location
as the starting vertex of the next segment, this location is represented by a single Point in
point-based methods. However, if there is a gap, separate Points are returned for the two
locations that define the gap.
Topological simplicity in features and graphics

To be saved as a feature in a geodatabase, a geometry must be simplifiedthat is, be topologically consistent. The rules vary for different
types of geometry but include requirements such as polygons not having overlapping parts. Pass a geometry to the GeometryEngine
object's simplify method to return a simplified copy that can be saved in a geodatabase.
Note that in some cases, simplification can change the contents of the geometry, including resulting in an empty geometry. Topological
simplicity is different than geometry generalization. For more information, see ITopologicalOperator.Simplify in the ArcObjects help.
The requirements for a geometry that will be used in a graphic are less rigorous than those used in a featurethere is no need to simplify
geometries to display them in graphics.
Builders and isValidSketch

In some workflows, both graphics and features are used. In interactive editing scenarios, for example, a user sketches a geometry on
the map. A graphic is used initially to display the state of the sketch during sketching. When the user decides that the sketch is
complete, the geometry can be saved to a geodatabase feature. You can use isValidSketch on a geometry builder to determine
when the builder contains enough state to be converted successfully to a geometry. This is a useful tool to enable or disable saving the
sketch by the user. To be considered a valid sketch, a polygon builder must contain at least one part with three or more vertices in it,
and a polyline builder must contain at least one part with at least two vertices. A multipoint builder must contain at least one point, and
for a point or envelope builder, the x and y coordinates must not be NaN. If these conditions are satisfied, these cases should result in a
geometry that could be visible if drawn.
Although isValidSketch may be a good first check when building a geometry, it should not be relied upon to indicate if the eventual
geometry will be valid or empty after simplification. Before allowing a user to save a geometry, consider taking a further verification step
of calling simplify. This approach can also be used for other situations that require geometries to be simple, for example,
measurement or topological operations.

When importing or exporting geometries, for example, to JSON, if a multipart geometry has insufficient points, additional points can be
added to ensure each segment has two endpoints to preserve the stability of other clients that may expect this.
Z-values and m-values

All types of geometry can have z-values. When building geometries, a simple rule determines whether or not the geometry stores z-
values. If you call a method that has a z-value parameter, or add a point or segment that has z-values to a builder, the resulting geometry
will store z-valueshasZ will return true.
Geometries can also have m-values, used in linear referencing workflows. Using m-values is generally less common than using z-values.
Therefore, instead of using constructors, the Point and Envelope classes present static factory methods that allow the creation of
geometries with m-values.
Pay special attention to z- and m-values in editing workflows. When syncing edits, sync errors may occur if the z- or m-awareness of the
geometry does not match that of the service. Find out more in the ArcGIS REST API help topic Error handling with sync.
Tip: When saving geometries in geodatabase features, check that hasZ and hasM match the
attribute awareness of the feature table being edited.

Sync offline edits

Your users can edit offline using a services pattern and later sync their edits back to a feature service when connected. Syncing offline
edits requires that you've created a geodatabase using a sync-enabled feature service from ArcGIS Online or ArcGIS Enterprise, as
described in Create an offline map. After users have made edits and are ready to sync their local copy of the data with the service, use
GeodatabaseSyncTask to sync with the feature service. Syncing can be performed even if no edits have been made locally, to pull
changes from the feature service into the local copy of the data.
Note: A Basic license is required for editing.
To synchronize edits, do the following:

1. Create a GeodatabaseSyncTask, passing in the URL of the feature service to be edited.
2. Set up a callback to report on the progress while the synchronization happens by calling
GeodatabaseSyncTask.addJobChangedListener().
3. Set up a callback to report when the process finishes or fails by calling GeodatabaseSyncTask.addJobDoneListener().
4. Set up the parameters for the synchronization task, using either the method on the sync task, or the
SyncGeodatabaseParameters constructor.
5. Call the syncGeodatabaseAsync method on GeodatabaseSyncTask to get a Job. Pass in the synchronization parameters,
and the local geodatabase that contains the edits.
6. Call start on the job to begin the sync operation.
Note: The sync operation overwrites previously synced edits to the same features on the service.
Errors that arise during a sync operation are returned in the callback when the job is done. For descriptions of errors that can arise when
syncing offline edits, see Error handling with sync.
For services backed by non-versioned data, sync operations are performed per-layer, and are always bi-directionalthat is, local edits are
uploaded to the service, and then new edits are downloaded from the service. For services backed by versioned data, sync operations are
per-geodatabase, and you can change the synchronization parameters to determine in which direction edits are synchronizeddownload
only, upload only, or bi-directional. Use Geodatabase.getSyncModel() to find out if a geodatabase can be synchronized per-layer or
per-geodatabase. Use SyncGeodatabaseParameters.setSyncDirection() to set the synchronization direction for a sync
operation. When using bi-directional sync, note that the 'last in wins'that is, uploaded edits will overwrite changes present on the server.
Register a geodatabase in a pre-planned workflow

In a services pattern workflow sometimes known as a pre-planned workflow, you generate the geodatabase once and load copies of it
onto each user's device. If you've generated the geodatabase on the user's device with the generateGeodatabaseAsync method on
the GeodatabaseSyncTask class, you don't need to register a geodatabase.
In the pre-planned workflow, you use the registerSyncEnabledGeodatabaseAsync() method to register each geodatabase copy
(on each device) with the feature service you used to generate the original geodatabase. Registering in this way ensures each device
receives the correct updates during sync operations.
Caution: Registering a geodatabase with a feature service is not supported with a versioned feature
service.
Once you call unregister on a geodatabase, you cannot re-register the same geodatabase.
If the original geodatabase is ever unregistered, no additional clients can use that copy to
register.
For a list of benefits of this workflow, see create an offline layer.
Example code
The following example shows you how to sync your offline edits back to a feature service.
To generate and download a geodatabase, use GeodatabaseSyncTask and GenerateGeodatabaseParameters. If you already have
a geodatabase downloaded, go to the following code section.

private void createGeodatabaseSyncTask() {
// Create a GeodatabaseSyncTask and add a done loading listener

geodatabaseSyncTask = new GeodatabaseSyncTask(FEATURE_SERVICE_URL);
geodatabaseSyncTask.addDoneLoadingListener(new Runnable() {
@Override public void run() {
// Check if it failed to load. If its not in the failed state, inside a done loading listener the only other
// valid state is loaded
if (geodatabaseSyncTask.getLoadStatus() == LoadStatus.FAILED_TO_LOAD) {
dealWithException(geodatabaseSyncTask.getLoadError());
} else {
// Now the sync task is loaded, use it to create GenerateGeodatabaseParameters, or sync changes
generateGeodatabaseParameters();
}
}
});
// Load the sync task

geodatabaseSyncTask.loadAsync();
}
private void generateGeodatabaseParameters() {
// Create GenerateGeodatabaseParameters from the GeodatabaseSyncTask using current map extent

Envelope generateExtent = mapView.getVisibleArea().getExtent();
final ListenableFuture<GenerateGeodatabaseParameters> generateParamsFuture =
geodatabaseSyncTask.createDefaultGenerateGeodatabaseParametersAsync(generateExtent);
generateParamsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
generateParams = generateParamsFuture.get();
// Change GenerateGeodatabaseParameters as required - e.g. removes all layers except first from the sync
for (int i = generateParams.getLayerOptions().size() -1; i >= 1; i--) {
generateParams.getLayerOptions().remove(i);
}
// Now the parameters are prepared, use them with the sync task to generate a geodatabase
generateGeodatabase();
}
}
});
}
private void generateGeodatabase() {

// Download a copy of the geodatabase to the specified path, using prepared parameters
generateJob = geodatabaseSyncTask.generateGeodatabaseAsync(generateParams, GEODATABASE_PATH);
// Add listener to check and report on the current download status

generateJob.addJobChangedListener(new Runnable() {
@Override
public void run() {
// Deal with any errors found while generating the geodatabase
if (generateJob.getError() != null) {
dealWithException(generateJob.getError());
} else {
// While job is in progress, review job messages or update progress in logs or user interface...
updateUiWithJobProgress(generateJob);
}
}
});
// Add listener to deal with the completed job
generateJob.addJobDoneListener(new Runnable() {
@Override
public void run() {
// Check the job state is complete, deal with any errors
if ((generateJob.getStatus() != Job.Status.SUCCEEDED) || (generateJob.getError() != null)) {
dealWithException(generateJob.getError());
} else {
// Get the completed Geodatabase from the job
if (generateJob.getResult() instanceof Geodatabase) {
Geodatabase syncResultGdb = (Geodatabase) generateJob.getResult();
geodatabase = syncResultGdb;
// Use the geodatabase, for example, load it and create FeatureLayers based on the tables it contains
loadGeodatabase();
}
}
}
});
// Start the Job to generate the geodatabase

generateJob.start();
}
Once a local geodatabase has been edited, for example by using FeatureTable.addFeatureAsync, edits can be synced back to the
service. Create a SyncGeodatabaseParameters object, and call the GeodatabaseSyncTask.syncGeodatabaseAsync method,
passing in the parameters and the local geodatabase.

private void createSyncParameters() {
// Create SyncGeodatabaseParameters based on default parameters from the sync tasks

final ListenableFuture<SyncGeodatabaseParameters> syncParamsFuture = geodatabaseSyncTask
.createDefaultSyncGeodatabaseParametersAsync(geodatabase);
syncParamsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try
{
// Retrieve the SyncGeodatabaseParameters from the future
syncParams = syncParamsFuture.get();
// Continue on to sync the database using the parameters
syncGeodatabase();
}
}
});
}
private void syncGeodatabase() {

// Start the sync operation on the geodatabase
syncJob = geodatabaseSyncTask.syncGeodatabaseAsync(syncParams, geodatabase);
// Add listener to check and report on the current sync status

syncJob.addJobChangedListener(new Runnable() {
@Override
public void run() {
// Deal with any errors found while syncing the geodatabase

if (syncJob.getError() != null) {
dealWithException(syncJob.getError());
} else {
// While job is in progress, review job messages or update progress in logs or user interface...
updateUiWithJobProgress(syncJob);
}
}
});
// Add listener to deal with the completed job

syncJob.addJobDoneListener(new Runnable() {
@Override
public void run() {
// Check the job state is complete, deal with any errors
if ((syncJob.getStatus() != Job.Status.SUCCEEDED) || (syncJob.getError() != null)) {
dealWithException(syncJob.getError());
} else {
// Get the SyncLayerResults returned from the sync
List<SyncLayerResult> syncResults = (List<SyncLayerResult>) syncJob.getResult();
if (syncResults != null) {
// Check sync results, for example update the UI to inform the user
dealWithSyncResults(syncResults);
}
}
}
});
// Start the Job to sync the geodatabase
syncJob.start();
}

Find a route
With ArcGIS Runtime SDK, you can:
Calculate point-to-point and multipoint routes
Optimize the results to find the shortest or the fastest route
Reorder stops to find the best sequence
Avoid restricted areas and maneuvers
Specify time windows of arrival and departure for each stop
A route task is a network analysis task that is executed asynchronously. It returns results with details about a route that visits two or more
stops (locations) within a transportation network. This operation is sometimes referred to as solving a route.
Transportation networks are created from features (lines and points) that represent roads, bridges, tunnels, bike paths, train tracks and
other elements in the network. The geometric intersections of features help to define connectivity between the network elements they
represent. The connectivity of the transportation network is analyzed to find a route.
Note: To learn more, see the topic What is a network dataset.

This topic's first sections lead through the process to find a route using an online service. See the section Routing with local data to see
how using local data is different from using a service. Whether you use a route service or local data, the overall process is the same.
Choosing a routing data source

You can use a transportation network exposed as an online ArcGIS route service (an ArcGIS Network Analysis service). To use an online
service, you must have a network connection to the service from your device.
This topic's first sections lead through the process to find a route using an online service. See the section Routing with local data to see
how using local data is different from using a service. Whether you use a route service or local data, the overall process is the same.
Network Analyst services are hosted in Esri's cloud platform, ArcGIS Online, or can be published on your own ArcGIS servers. These
services provide a REST API for clients such as mobile and Web applications. For more information about publishing a service, see
Tutorial: Publishing a network analysis service.
How do route services differ? The most important criteria for choosing a service (or a transportation network for that matter) is the area
that it covers. You cannot find a route using a service that does not encompass all the stops and barriers that your user will specify. In
addition, route services offer differing levels of capability and specialization.
You can build a transportation network from your own data, or use a dataset provided by someone else, such as Esri's World Street Map
data. Then, you can publish a route service on your own portal or on ArcGIS Online. Or, you could use a route service created by
someone else that suits your needs. For example, the Esri World Route Service is capable of finding routes almost anywhere because it
references road data that covers much of the world. Since the ArcGIS Online road data also includes traffic data for many areas, you can
find the best routes and account for dynamic traffic conditions. For instance, you can find the best route from home to work with a
departure time of 7:00 a.m. and compare that route with one you generate for 8:00 a.m.
Like other services, some route services require credentials for access. You provide these credentials when you create the route task
object.
Creating and loading the route task

The route task is an object that refers to the transportation network, accepts route task parameters, is executed to find a route, and reports
results.
Create an instance of the route task object, setting its source to the route service you selected in the previous step
final String routetTaskSandiego =
"http://sampleserver6.arcgisonline.com/arcgis/rest/services/NetworkAnalysis/SanDiego/NAServer/Route";
// create route task from San Diego service
RouteTask routeTask = new RouteTask(routetTaskSandiego);
Then, load the route task.

// load route task
routeTask.loadAsync();
routeTask.addDoneLoadingListener(() -> {
if (routeTask.getLoadError() == null && routeTask.getLoadStatus() == LoadStatus.LOADED) {
// route task has loaded successfully
}
});
Specifying route task parameters

Route task parameters specify how a route should be found. There are many parameters that let you customize how the route is
determined. Parameters include stops and barriers. (More about those later.) Other parameters include travel mode, whether stops map
be reordered to find an optimized route, the length units to be used in the turn-by-turn directions, and so forth.
The only way to specify parameters is to call the method on the route task that retrieves the default routing parameters defined for the
service, and then change the defaults as needed before executing the route task. The service's default parameters support the most
common use case for that service. Different services can have different defaults.
Once the route task has been loaded retrieve its default parameters. Specify that the directions and the route are returned.
Remember to set the output spatial reference so that it can be displayed correctly in the map view.
try {
// get default route parameters
routeParameters = routeTask.createDefaultParametersAsync().get();
// set flags to return stops and directions
routeParameters.setReturnStops(true);
routeParameters.setReturnDirections(true);
}

Your app might allow users to choose some parameters directly, such as whether the stops should be followed in the order specified or in
optimum order. Your app would get these choices from the user and set the corresponding route task parameters.
Specifying stops and barriers

A simple route could be from a start point to an end point. In the parlance of routing, both of these points are referred to as stops. A route
can have from two to many stops. Ultimately, a stop is a point location along a transportation network.
How you get these stops is your design decision. Here are some options, and you'll probably come up with other ideas, too.
Get the current location of your device and use it as a starting point.
Let users choose stops by clicking near roads on a map.
Access an address from an address book, geocode the address, and use the result as a stop.
Barriers are places that your route must avoid because they are impassable, or places that add cost to the route if traversed. The best
route usually has the least cost.
Unlike stops which are always points, barriers can be points, polylines, or polygons. Like stops, you can define barriers in various ways.
Your app could allow users to draw barrier graphics. Another option is to use graphics from a feature table. For example, you may have a
feature table with areas affected by a forest fire, and you want your route to avoid those areas.
You do not have to specify any barriers to find a route.
Regardless of how you define your route's stops and barriers, all must share a spatial reference. That spatial reference doesn't have to
match the spatial reference of the route service or transportation network.
Specify the stops and barriers
// set stop locations
SpatialReference ESPG_3857 = SpatialReference.create(102100);
Point stop1Loc = new Point(-1.3018598562659847E7, 3863191.8817135547, ESPG_3857);
Point stop2Loc = new Point(-1.3036911787723785E7, 3839935.706521739, ESPG_3857);
// add route stops
routeParameters.setStops(Arrays.asList(new Stop(stop1Loc), new Stop(stop2Loc)));
// create barriers
PointBarrier pointBarrier = new PointBarrier(new Point(-1.302759917994629E7, 3853256.753745117, ESPG_3857));
// add barriers to routeParameters
routeParameters.setPointBarriers(Arrays.asList(pointBarrier));
Executing the route task

Execute the route task while providing the route task parameters.
try {
RouteResult result = routeTask.solveRouteAsync(routeParameters).get();
} catch (Exception ex) {
ex.printStackTrace();
}
Processing results
The route task signals when the task is complete and results are available. The most familiar part of the results may be the linear graphic
that traces the path of the route. Technically, it is a polyline that follows connected edges in the transportation network from stop to stop in
a specific order. The route task can return the stops and barriers with the results. This makes it easier for your app to access all the
associated graphics when displaying results. The route task also returns turn-by-turn directions that describe the route. If your app does
not need one or more of these result elements, each can be turned off by setting route task parameters.
It is up to your app to present results in a useful way. Most commonly, the route, the stops, and sometimes the barriers are displayed on a
graphics overlay on the map. The directions may be displayed in a list form or through a directions browser implemented by the app.

Routing with local data

You can find a route using a transportation network stored on your device, meaning that your device does not need a connection to a
communication network to find a route. You have a couple of options for provisioning your device with a local transportation network:
mobile geodatabases and mobile map packages. Either may be deployed with your app on the device.
If you'd like a ready-to-use and regularly updated network dataset (and locator) for your area of interest, you can license StreetMap
Premium data (in mobile map package format). For details, see Add StreetMap Premium data.
Mobile geodatabase
When a transportation network is in a mobile geodatabase, you can access that network by specifying the location of the geodatabase
and the name of the network.
Note: To learn more, see Creating ArcGIS Runtime content.
File directory = new File(geodatabasePath);

RouteTask routeTask = new RouteTask(context, directory.getAbsolutePath(), "Routing_ND");
Mobile map package

A mobile map package can contain multiple maps, and each map can have multiple transportation networks. Here is the general
workflow to access one of these networks:
Load the mobile map package from local storage
Get the map that contains the desired transportation network from the mobile map package
Get the desired transportation network from the map
Note: To learn more, see create a mobile map package with ArcGIS Pro.

Geoprocessing
Geoprocessing provides a large suite of tools for performing GIS tasks that range from basic buffer and polygon overlays to complex
regression analysis and image classification. You can automate all kinds of GIS workflows using Geoprocessing, from converting a large
amount of data from one format to another to using a sequence of operations to model and analyze complex spatial relationships.
Examples include:
Calculating optimum paths through a transportation network
Predicting the path of wildfire
Analyzing and finding patterns in crime locations
Predicting which areas are prone to landslides
Predicting flooding effects of a storm
There are many reasons why geoprocessing services are good options for these tasks. They can centralize logic to the service. They can
help to reduce the workload on the client. Also, geoprocessing services can access tools that arent available or efficient to run in the
client.
Geoprocessing is based on a framework of data transformation. A typical geoprocessing tool performs an operation on an ArcGIS dataset
(such as a feature class, raster, or table) and produces a new dataset as a result. Each geoprocessing tool performs a focused operation
on geographic data, perhaps as a small part of the overall analytical process.
Geoprocessing allows you to combine a sequence of tools into what is called a model. In a model, the output of one tool is fed into
another, which allows you to automate your workflows. Geoprocessing tools and models can be shared with others by creating web
services. ArcGIS Runtime uses geoprocessing tools through web services.
A geoprocessing tool is a command or function that performs an operation on GIS data. There are three types of tools, as shown in the
table below.
Tool type Description

Built-in tool Built-in tools are created by Esri and provided with ArcGIS
Model tool Model tools are user-created tools authored using ModelBuilder
Script tool Script tools run a geoprocessing Python script file
Geoprocessing tools can be system tools built by Esri and included in ArcGIS products, or custom tools built as script or model tools by
you and other users. You can use both custom and system geoprocessing tools in the same ways. Learn more about using geoprocessing
in ArcGIS Desktop by taking a quick tour.
Use geoprocessing in ArcGIS Runtime

A geoprocessing web service is published from ArcGIS Desktop to ArcGIS Online or ArcGIS Enterprise. This web service and its tasks
can be consumed as REST endpoints by web-based clients such as ArcGIS Desktop, Explorer for ArcGIS, custom web apps, and ArcGIS
Runtime SDK apps.
Learn more about creating and publishing geoprocessing web services.
What is a geoprocessing task?

A geoprocessing task is a REST child resource of a geoprocessing service. A geoprocessing service can host one or more tasks. A task
has a set of parameters that define how a client can interact with the task and what kind of input must be passed to it to execute the task.

The server executes the task and returns output values to the client. Output values could include a map service to show the results. This
allows for the display of complex data and raster data.
The following figure shows the hierarchy of geoprocessing REST resources. Notice that geoprocessing service properties (shown in
orange) are inherited by every geoprocessing task. These include the execution type, the maximum number of records to return, and the
map service used to return results.
The format for a geoprocessing task URL is http://<gpservice-url>/<taskName>. The endpoint for a task called BufferPoints
hosted on myserver, for example, would be the following.
http://myserver/ArcGIS/rest/services/BufferPoints/GPServer/BufferPoints
Tasks defined in HTML task pages

The ArcGIS Server service directory contains a set of service pagesweb pages of information about each service it provides. You can
use the service pages of a geoprocessing service to explore its tasks and their parameters, and learn how to code against themsimply
open the REST URL in a browser.
What are task parameters?

Task parameters are the inputs and outputs of a geoprocessing task and vary from task to task based on its individual requirements.
Each parameter has a set of properties that describe it, such as name, data type, whether it is required or optional, and so on.

When tasks complete, results are returned in a variety of ways. Its important to understand how a particular geoprocessing task returns
results in order to handle them properly. To learn about parameter types, see geoprocessing task parameters.
A geoprocessing task may output a map service result. This prevents the client app from having to symbolize and draw a large number
of features or to try to handle a data format that cannot be added directly to the map via the API. When maps from map services are
rendered, symbology is applied to the features.
Execution type
The work required of a geoprocessing task can be straightforward and may take a few seconds to execute on the server, or it can
support advanced functionalityprocessing large datasetsand may take longer to execute. Therefore, the REST API provides two
execution types, which are options for running the geoprocessing task on the server.
Synchronous: Synchronous tasks are suitable for fast running tasks. In synchronous tasks, the client sends a request to run
the task and waits for the results of the task to be returned as a response.
Asynchronous: Asynchronous tasks are suitable for long running jobs. In asynchronous tasks, the server returns a job ID
which the client uses to poll for task status. When the status is completed, the results are created as child resources of the job
which the client can access using its job ID.
In ArcGIS Runtime both execution types are accessed asynchronously and the call to the correct REST endpoint is defined by the
execution type set on the geoprocessing parameters. Even though the geoprocessing tasks are executed in different manner at the
service level, they are accessed through one single API. To learn how you can use geoprocessing in your app, see Run a
geoprocessing task.

Run a geoprocessing task

A geoprocessing service contains one or more geoprocessing tasks. A geoprocessing task is a geoprocessing tool running on a service
and its execution and outputs are managed by the service. You can run these tools from an ArcGIS Runtime app using classes in the
esri.arcgisruntime.tasks.geoprocessing package.
Steps to run a geoprocessing task at a high level:
1. Create a GeoprocessingTask using full URL to the target geoprocessing task endpoint.
2. Create GeoprocessingParameters providing corresponding GeoprocessingExecutionType.
3. Create GeoprocessingParameter(s) as required, and add them to GeoprocessingParameters.getInputs() where key
is the name of the parameter and value is created parameter.
4. Set environment variables on GeoprocessingParameters if needed.
5. Create GeoprocessingJob by calling the job creation method on the geoprocessing task, using the parameters created
previously.
6. Listen for job changed status and message changes on the GeoprocessingJob.
7. Run the geoprocessing job and if it completes successfully, get the GeoprocessingResult.
8. Handle returned values accordingly. Output parameters are accessed as a dictionary on GeoprocessingResult where key is
the name of the output parameter and the value is returned parameter. If the geoprocessing service is configured to use a result
map service then the result may also contain a map image layer that has been created for you.
Creating a geoprocessing task

GeoprocessingTask is the main component when running geoprocessing tasks which is used to run a single geoprocessing task. The
target is defined by providing URL to the target REST endpoint.
The format for a geoprocessing task URL is http://<gpservice-url>/<taskName>. The endpoint for a task called 'BufferPoints'
hosted on 'myserver', for example, would be something like:
https://myserver/ArcGIS/rest/services/BufferPoints/GPServer/BufferPoints
GeoprocessingTask geoprocessingTask = new GeoprocessingTask(
"http://myserver/ArcGIS/rest/services/BufferPoints/GPServer/BufferPoints");
Creating input parameters

GeoprocessingParameters contains input parameters and environment variables. Required input parameters are defined by the
geoprocessing task. Environment variables are common geoprocessing variables that guide how the service works.
When GeoprocessingParameters is created, it needs to know the execution type of the task. This defines which REST endpoint the
GeoprocessingJob is using when the task is executed. This value needs to match the one defined in the used service.
GeoprocessingParameters.getInputs() is a dictionary that contains all the parameters that are sent to the service. The key of the
item is the name of the parameter and the value contains the GeoprocessingParameter. When parameters are provided to the
geoprocessing task their parameter name and type needs to match the one defined in a task. At a minimum all parameters that are set as
required on the task must be provided to run the task successfully.
You can also provide a set of optional environment variables. These control general settings for the service, such as whether the Z and M
values are returned in the result, or which spatial reference to use for the results. For example, if you are visualizing the results of the
analysis on the map, requesting the results in the same spatial reference as the map view uses removes the need for the client to
reproject the results before adding them to the map view.
// create a GeoprocessingParameters with execution type, for example, ASYNCHRONOUS_SUBMIT
GeoprocessingParameters geoprocessingParameters = new GeoprocessingParameters(GeoprocessingParameters.ExecutionType.ASYNCHRONOUS_SUBMIT);
// provide input parameters required for the geoprocessing task
// this example shows an input parameter called "Query"
// the data type of "Query" is GPString in the REST spec, identified by GeoprocessingString in the Java API
String inputParameterName = "Query";
GeoprocessingString inputParameterValue = new GeoprocessingString("(\"DATE\" > date '1998-12-31 23:59:59')");
geoprocessingParameters.getInputs().put(inputParameterName, inputParameterValue);

Task execution types

When working with geoprocessing services, you must be aware of the execution type that the service was published with. This execution
type can be found on the service's Rest page. There are multiple execution types that define how geoprocessing tasks run on a server:
Execute (defined as esriExecutionTypeSynchronous in task page)
Synchronous execution is designed for fast-running tasks and they are run synchronously on the server. The client sends a
request asynchronously to the service and waits for the response. This means these types of services use less resources on the
server. When targeting a geoprocessing service that is exposed using this type, GeoprocessingParameters needs to be
created using GeoprocessingParameters.ExecutionType.SYNCHRONOUS_EXECUTE.
Submit (defined as esriExecutionTypeAsynchronous in task page)
Asynchronous services are best suited for long running jobs and are run using asynchronous model on the server. For
asynchronous tasks, the server returns a job ID that the client uses to poll for the task status. When the job is completed, the
results are fetched separately from the job result endpoints. When targeting a geoprocessing service that is exposed using this
type, GeoprocessingParameters needs to be created using
GeoprocessingParameters.ExecutionType.ASYNCHRONOUS_SUBMIT.
If a geoprocessing tool is published from ArcGIS Desktop with a map server result to visually represent each geodataset output parameter
as a layer then the geoprocessing server (GPServer) will have an accompanying dynamic map server of the same name for presenting
the results. This map service's symbology is based on the symbology of the output layer that resulted from running the geoprocessing tool
in ArcGIS Desktop during the publishing process. See Defining output symbology for geoprocessing tasks for additional information on
setting the symbology for a result map service.
GeoprocessingJob, which does the communication between the client and the service, knows which REST endpoint to use based on
the execution type that was given as a parameter for GeoprocessingParameters and it has to match the execution type on the
service. If the value isn't correct then an exception is thrown when the task is run.
Parameters
Geoprocessing tasks usually have input and output parameters. These parameters are defined when the geoprocessing task is authored
and can be seen in geoprocessing task page in the services directory. Each parameter of a task has a set of descriptive properties that
help you understand the parameter and provide appropriate value for the successful execution of the task.
When parameters are provided to the geoprocessing task their parameter name and type needs to match the one defined in a task. At a
minimum all parameters that are set as required on the task must be provided to run the task successfully
The significance of each property is described below
Parameter direction
Every parameter has a direction which is defined in the parameter information. This information helps you identify whether the
parameter is an input or output parameter.
When the task is executed, the client needs to provide values for the input parameters only. Output parameters are returned from the
task when the job has been run successfully.
Output parameters are always returned from a geoprocessing task in a dictionary.
Parameter data types

The data type of the parameter specifies the type of value that the client must provide for the parameter. The value of a parameter can
be as simple as a string, long, double, Boolean or date. Or, it can be a set of features or records or a raster file. For example, if the task
is expecting to have a raster input parameter, you need to provide a geoprocessing raster parameter in a
GeoprocessingParameters.getInputs() collection to execute the tool successfully.
Here is a list of ArcGIS Runtime geoprocessing parameter types and which types they correspond to the service.

Required and optional parameters

Parameters can be defined as: required, required with default value, optional, or derived. When the parameter is required but doesn't
have default value defined, the parameter must be provided when the geoprocessing task is executed. If the default value is defined,
then you can override that value by providing a new parameter in a GeoprocessingParameters.getInputs() Map. Optional
parameters can be provided in the same manner. Derived means that the you do not enter a value for the parameter. Derived types are
always output parameters.
ArcGIS Runtime Corresponding REST Note

parameter types types
GeoprocessingString GPString A string. If ChoiceList is defined in a parameter then the value must match one of the
items in the list
GeoprocessingDouble GPDouble A decimal value approximately between -2.2E308 to 1.7E308
GeoprocessingLong GPLong An integer value between 2,147,483,648 to 2,147,483,647
GeoprocessingBoolean GPBoolean True or false
GeoprocessingDate GPDate A date value
GeoprocessingLinearUnit GPLinearUnit A value that has a distance value and its unit of measurement such as kilometers or
meters
GeoprocessingDataFile GPDataFile References a file such as .txt, .pdf, .csv, and so on. Supported data types are
controlled by the used service. Can reference a file that is uploaded to the service
using Uploads capability
GeoprocessingRaster GPRasterData References a single raster file such as .tif or .jpg, and so on.
Can reference a raster that is uploaded to the service using Uploads capability.
GeoprocessingRaster GPRasterDataLayer Super set of GPRasterData that supports showing values on result map server.
GeoprocessingFeatures GPRecordSet A set of Features that represents rows and columns. Doesn't have a geometry or
spatial reference.
Can reference a file that has the features serialized.
GeoprocessingFeatures GPFeatureRecordSetLayer A set of Features that have a geometry, spatial reference and attributes.
Can reference a file that has the features serialized.
GeoprocessingMultiValue GPMultiValue An array of geoprocessing parameters of the same data type
Running the task and handling the results

The targeted geoprocessing task is run using GeoprocessingJob which is responsible handling the communication between the client
and the service. GeoprocessingJob is created using GeoprocessingTask and GeoprocessingParameters, and it can be started
by calling start. GeoprocessingJob also provides a Future task which runs the job and returns the results when the task is
completed successfully. If any errors occurs while the job is running, an exception is thrown. The error can be also retrieved directly from
the GeoprocessingJob.
// access output features after task is done
void process(GeoprocessingResult geoprocessingResult) {
final GeoprocessingFeatures geoprocessginFeatures =
(GeoprocessingFeatures) geoprocessingResult.getOutputs().get("Output_Features");
if (geoprocessginFeatures.canFetchOutputFeatures()) {
ListenableFuture<Void> fetchOutputFeaturesFuture = geoprocessginFeatures.fetchOutputFeaturesAsync();
fetchOutputFeaturesFuture.addDoneListener(() -> {
FeatureSet features = geoprocessginFeatures.getFeatures();
// process features. for example, add features to a graphics overlay
});
}
}
Results as a map image layer

The result map server is a dynamic map service that accompanies a geoprocessing service to visualize the geoprocessing results. If
this is enabled in the geoprocessing task, then theGeoprocessingResult.getMapImageLayer might be populated for you. The
visualization of the layer is determined by the symbology on the geoprocessing service.
This functionality is available on the geoprocessing services that has execution type of submit with result map server functionality
enabled.
// access output ArcGISMapImageLayer after task is done
ArcGISMapImageLayer mapImageLayer = geoprocessingResult.getMapImageLayer();
map.getOperationalLayers().add(mapImageLayer);
}

In case where GeoprocessingResult.getMapImageLayer is populated in the results and the geoprocessing result outputs contain
GeoprocessingFeatures parameters, features aren't automatically downloaded to the client to avoid unnecessary traffic between the
service and the client. If you need to download the features, you can get the features explicitly from the results.
// access output features after task is done
final GeoprocessingFeatures geoprocessginFeatures =
(GeoprocessingFeatures) geoprocessingResult.getOutputs().get("Output_Features");
if (geoprocessginFeatures.canFetchOutputFeatures()) {
ListenableFuture<Void> fetchOutputFeaturesFuture = geoprocessginFeatures.fetchOutputFeaturesAsync();
fetchOutputFeaturesFuture.addDoneListener(() -> {
FeatureSet features = geoprocessginFeatures.getFeatures();
// process features. for example, add features to a graphics overlay
});
}
}
Downloading geoprocessing data files and rasters

If GeoprocessingDataFiles or GeoprocessingRasters are used as output parameters, they have a URL specified to the location
of the output file. This file can be downloaded to the client device easily by using a Future task.
// access raster or data file after task is done
final GeoprocessingRaster geoprocessingRaster =
(GeoprocessingRaster) geoprocessingResult.getOutputs().get("Hotspot_Raster");
ListenableFuture<Void> fetchRasterFuture = geoprocessingRaster.fetchFileAsync("<fileNameWithPath>");
fetchRasterFuture.addDoneListener(() -> {
// file now available at <fileNameWithPath>
});
}

Access the ArcGIS platform

The ArcGIS platform provides a full range of GIS capabilities. There are various ways to add powerful functionality and intelligence to your
ArcGIS Runtime app by connecting to platform capabilities.
ArcGIS Online
ArcGIS Online is a cloud-based, collaborative content management system for maps, apps, data, and other geographic content. You can
access ArcGIS Online through mobile devices, a website (www.ArcGIS.com), and desktop map viewers. With ArcGIS Online you can do
the following:
Create web maps.
Web enable your data.
Share your maps, data, and applications.
Find relevant and useful basemaps, data, and configurable GIS resources.
Manage content and users in your organization.
Tip: With your free ArcGIS for Developers account, you have access to ArcGIS Online for
development and testing. Sign in at developers.arcgis.com or www.ArcGIS.com. You may want
to upgrade to a paid ArcGIS Developer Subscription.
Using ArcGIS Runtime SDK, you can work with content in a portal, for example you can access and edit existing content and create new
content items, search for users and groups, and share and unshare items.
Learn more about developing with ArcGIS Online in ArcGIS Online Help.
ArcGIS for organizations

To access all the capabilities of ArcGIS Online, your organization can purchase a subscription. With this subscription, you can store and
process geographic data, solve complex routing problems, perform spatial analysis, create reports, and enrich your own data with
demographic and geographic attributes. You also gain access to various productivity apps. A subscription can help you make geospatial
information more pervasive both within your organization and throughout the general public.
Tip: Your free ArcGIS for Developers account includes some subscription-only services for
development and testing. Sign in at developers.arcgis.com or www.ArcGIS.com. If you
upgrade your free account to a paid plan, you can still sign in using both of these sites.
Learn more about ArcGIS for organizations on esri.com.
Portals, users, roles, groups, and sharing

ArcGIS Online is an information portal and is represented in the API by the Portal class. This class is loadable.
When you sign in to ArcGIS Online with an organization account, you see a specialized view that your organization administrator has
configured for you, giving you access to maps, content, and other services specific to your organization. You can also access all your
own content and services.
A registered user of a portal is represented in the API by the PortalUser class. When you have signed in to a portal, you can get
authentication information relating to the authenticated user from the portal class. Several options are available for signing in to a portal,
such as OAuth 2.0, network credentials, tokens, and public keys (PKI). Two authentication patterns are availablenamed user and app
login. For an overview of the ways to access secure services, see ArcGIS Security and Authentication.
Portals and named users have an essential role to play in some app licensing scenarios. For more information about licensing, see
License your app.
Groups are a way to collaborate with other users who share a common interest. A user can create groups, join groups, and share items
with those groups. Groups have titles, descriptions, thumbnails, and unique IDs to help users identify them. The sharing model within
ArcGIS Online is based on groups. Groups are represented in the API by the PortalGroup class.
A free, public account is another way to access ArcGIS Online. These accounts are not associated with an organization and offer a
limited set of functionality. A public account allows you to use and create maps and share your maps and apps with everyone. Public
accounts are for noncommercial use only.

Connect to public content and services on ArcGIS Online

To connect to ArcGIS Online and access public content anonymously, you can begin by creating a portal, without authenticating with the
portal.
final Portal portal = new Portal("http://www.arcgis.com");
portal.addDoneLoadingListener(() -> {
PortalInfo portalInformation = portal.getPortalInfo();
String portalName = portalInformation.getPortalName(); // Returns 'ArcGIS Online'
}
});
portal.loadAsync();
From here, you can access public content; for example, you can display a web map, or download the data stored in a portal item. You
can also search for content such as web maps, map services, map features, groups, and users.
Some organizations share content publicly and allow anonymous access to that content; connect to publicly accessible content from
such organizations by specifying the organization URL. For example:
Portal portal = new Portal("http://anorganization.maps.arcgis.com");
Connect to secured content and services on ArcGIS Online

Apps that target organization users who are known to the ArcGIS platform (named users) should use the
DefaultAuthenticationChallegeHandler, which is the simplest way to handle all authentication challenges that ArcGIS
supports. To authenticate a user to a portal using this approach, you must set an instance of
DefaultAuthenticationChallegeHandler into the AuthenticationManager, then create a portal object, indicating that
authentication is required, and then asynchronously load the portal.
DefaultAuthenticationChallengeHandler handler = new DefaultAuthenticationChallengeHandler(activityContext);
// Create a Portal object, indicate authentication is required
final Portal portal = new Portal("http://www.arcgis.com", true);
portal.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
PortalUser user = portal.getUser();
String userDisplayName = user.getFullName(); // Returns display name of authenticated user
}
}
});
portal.loadAsync();
Authenticated credentials are then cached by the Authentication Manager.

The portal object now has access to all the secure content for which the user has access rights and can be used to find out more
information about the user, such as the user's full name (instead of the account user name). Additionally, information about the
organization such as the name, banner image, description, and so on, can be found as shown above. Apps often make use of this
information when a user connects to a specific portal, to show the user organization branding and context.
Typically, the portal object with the authenticated user is cached and used throughout the app session, to provide the app with a view of
a portal that is centered around a single user. When the app is restarted, the credential must be reinstated, or the user must repeat the
authentication process.
To access secure content, an app needs to provide a way to sign in to the platform, a process often known as authentication. The
recommended approach for authenticating a user known to the platform is to use a user login and OAuth. Apps that target users who
are unknown to the ArcGIS platform can authenticate with the platform on behalf of the user by using an app login. OAuth authentication
is one of the types of authentication challenge that is handled automatically by the
DefaultAuthenticationChallegeHandlerwhen the challenge for authentication is issued, the user is shown a web form,
allowing them to login using their own credentials.
Portal for ArcGIS

Portal for ArcGIS (a component of ArcGIS Enterprise) provides you with the same core capabilities as ArcGIS Online, but it can be
installed and hosted on your own premises, behind your firewall, for controlled distribution of content.
Learn more about ArcGIS Online on esri.com.

Connect to Portal for ArcGIS

Connecting to an instance of Portal for ArcGIS is done in a very similar way to connecting to ArcGIS Online and is represented in the
API by the same class, Portal. Use the URL to the Portal for ArcGIS website, along with an appropriate credential or authentication
valid on that portal, or no credential or authentication if accessing public content anonymously.
DefaultAuthenticationChallengeHandler handler = new DefaultAuthenticationChallengeHandler(this);
final Portal portal = new Portal("https://geoportal.mycompany.com", true);
ArcGIS Server
ArcGIS Server (a component of ArcGIS Enterprise) is a complete and integrated server-based GIS, allowing you to publish many different
types of GIS services for use by a variety of clients including ArcGIS Runtime apps. Some services provide similar functionality to that
available from ArcGIS Onlinefor example, you can create map layers based on map, feature, or WMS services, and perform geocoding,
routing, or geoprocessing functions by using services hosted by ArcGIS Server.
Discover content and services on ArcGIS Server

Use the ArcGIS Services Directory to browse the available services on an ArcGIS Server site. Open the REST Services home page in a
browser, for example, http://sampleserver6.arcgisonline.com/arcgis/rest/services.
Contact your ArcGIS Server system administrator if you're uncertain about the server URL or ArcGIS instance.
Connect to ArcGIS Server

Connecting to ArcGIS Server is a little different from connecting to portalsin the place of connecting to the portal itself, you pass the
URL of the service you want to use to a class designed to work with that service type.
For example, you can create a map layer by passing in the URL to a dynamic map service:
final String serviceFeatureURL =
"http://sampleserver5.arcgisonline.com/arcgis/rest/services/Elevation/WorldElevations/MapServer";
// create new ArcGISMap image Layer from service url
final ArcGISMapImageLayer imageLayer = new ArcGISMapImageLayer(serviceFeatureURL);
If the service is secured, valid credentials or authentication will be required.

ArcGIS Server services are listed below, along with the classes that make use of them.
Service type API classes

Feature service FeatureLayer, ArcGISFeatureTable
Map serviceDynamic ArcGISMapImageLayer
Map serviceTiled ArcGISTiledLayer
Map serviceIdentify endpoint GeoView.identifyLayerAsync and
GeoView.identifyLayersAsync methods
Map serviceExport tiles endpoint ExportTileCacheTask
Feature serviceCreate replica, synchronize replica, unregister GeodatabaseSyncTask
replica, and apply edits endpoints
GeocodeServer LocatorTask
NAServer RouteTask
ArcGIS Server services and related API classes
Services that do not have a native API class, for example, the Legend endpoint on a MapServer, can be accessed via REST. If a
credential is required, generate a token using the GenerateToken service on the ArcGIS Server site, and append this to the URL.
Learn more about ArcGIS for Server on esri.com.
Authentication Manager
Your app may need to access secured resources that are restricted to authorized users. For example, your organization may host private
data layers or feature services that are only accessible by verified users. You may also need to take advantage of premium ArcGIS Online
services, such as routing, that require secured user access. The ArcGIS platform provides many ways to secure access to your

organization's content and services. The ArcGIS Runtime SDK provides full support for access to secured ArcGIS Server, ArcGIS Online,
or Portal for ArcGIS resources using the following authorization methods:
ArcGIS Tokens: proprietary token-based authentication mechanism.
OAuth 2.0: secure delegated access to server resources.
Network credential: HTTP secured service / Integrated Windows Authentication (IWA).
Certificate: Public Key Infrastructure (PKI).
Implementing these security methods in your app (potentially for a variety of platforms) can be a lot of work. To simplify authentication,
ArcGIS Runtime provides classes to automate the process: Authentication Manager (AuthenticationManager) and Authentication
Challenge (AuthenticationChallenge).
The Authentication Manager manages access by the app to secured resources. This singleton creates an Authentication Challenge
whenever an authentication or security issue is encountered anywhere in the API. The types of Authentication Challenge include the
following:
Username / password: Challenges needing username / password authentication.
OAuth: Challenges needing an OAuth authorization code.
Client Certificate: Challenges needing a client certificate to be provided.
Secure Sockets Layer (SSL) Handshake - Challenges needing a response to certain SslError errors, usually an untrusted host
due to a self-signed certificate.
Your app responds to an Authentication Challenge by providing the requested authentication information, which may be a certificate,
credentials, or username and password. Challenges are dealt with by being forwarded to the AuthenticationChallengeHandler that
is set onto the Authentication Manager. The DefaultAuthenticationChallegeHandler provides a default implementation of this
interface; alternatively you can create your own challenge handler, if required, by implementing this interface.
After your app provides the authentication information, the Authentication Manager caches that information. The Authentication Manager
contains an instance of a CredentialCache which maintains a cache of credentials, in memory, that have been previously used to
satisfy authentication challenges. This allows a credential to be reused where appropriate, and prevents unnecessary or duplicate
challenges from being issued while accessing secure resources from the same security realm. Caching happens automatically if credential
caching is enabled on the Authentication Manager. When the app wants to sign out, clear the credential cache within the Authentication
Manager.

Access portal content

Portals such as ArcGIS Online and Portal for ArcGIS can store many types of data. Perhaps the type most commonly used by apps is a
web mapa JSON description of the data in a map, along with other display and behavioral properties. Other types include tile packages,
feature collections, and services. Some types, such as globe documents and map templates, may only be relevant to desktop systems.
Although you can access these types of data using the API, you may not be able to use them on a mobile device. Some types of data can
be taken offline.
PortalItem represents an individual item stored on a portal. Each item includes the following:
Metadata, such as a unique identifier (ID), title, summary, description, thumbnail image, and tags
Binary or text-based datafor example, the JSON that defines a web map or a feature collection, or a URL pointing to a map
service, or the binary data of a tile package or shapefile
Apps use portal items in different ways. They may show a user a range of items from a portal by combining the title, thumbnail image, and
other metadata. This approach is often used to allow users to browse web maps, basemaps, or map services, and identify the item to work
with. If a user selects an item, the app may then download the data stored in the portal item, for example, by opening and displaying a
web map in a map, or downloading a tile package. Apps sometimes access items directly by ID if a specific item should always be used.
Your app can also add new portal items and alter existing items by adding comments and ratings, updating item information, sharing,
unsharing, and deleting them, as long as the authenticated user has access permissions to do so.
You access the content of a portal item differently depending on its type. Below you can find examples of accessing different types of
portal items. For more information on connecting to a portal, see Access the ArcGIS platform.
Display a web map by ID

A very common task is to display a web map from a portal. Web maps are stored as portal items and can be opened by using the ID of the
item, along with the URL of the portal. If the map is not public (for example, if it is shared only with a specific group), you also need to pass
in valid credentials with permission to view the map. See Access the ArcGIS platform for more information on accessing secured items.
The code below sets a map into a map view by creating a portal item from the ID of a known web map portal item. This assumes that the
portal item is publicly shared, as no credentials are used.
// create a new Portal object
Portal portal = new Portal("http://www.arcgis.com");
// create a PortalItem based on a pre-defined portal id

PortalItem portalItem = new PortalItem(portal, "01f052c8995e4b9e889d73c3e210ebe3");
// create a map from a PortalItem

ArcGISMap map = new ArcGISMap(portalItem);
// set the map to be displayed in a MapView
mMapView.setMap(map);
There are different ways to display a map from a web map.
Open a map
You can create a map from a web map portal item without needing to display it immediately. From this, you could find out more about
the contents of the map before displaying it if requiredfor example, getting the basemap, operational layers, bookmarks, and initial
extent. To do this, load the map before setting it into a map viewsee Loadable pattern for more information.

Note: Remember that you must also specify credentials for a valid user with access to the item, if
the item is not publicly shared.
Find information about any portal item by ID

You can use the ID of any item stored in a portal to access it, and also to find its fieldsproperties such as its title, description, thumbnail
image, owner, and any ratings or comments added by portal users. You can also find out the type of data it contains.
The code below creates a PortalItem object representing a web map, and then finds the title and the date it was last modified.
portalItem = new PortalItem(portal, "Portal_Item_ID");
//load the PortalItem asynchronously, and wait until complete
portalItem.loadAsync();
portalItem.addDoneLoadingListener(() -> {
//check loading was successful
if (portalItem.getLoadStatus() == LoadStatus.LOADED) {
//get information about the portal item
Date modified = portalItem.getModified().getTime();
String itemDetails = String.format("%s was last modified on %tA, %te of %tB", portalItem.getTitle(),
modified, modified, modified);
}
});
Note: The thumbnail of a portal item, along with the ratings and data, is not returned from the portal
when you initially load the item, in order to reduce the network traffic and memory
requirements. See the section below on how to access these properties.
Fetch thumbnails of items
When you create a portal item object, not all information associated with it is immediately returned. This allows you to work with the item
using a minimum amount of memory and delay fetching the larger pieces of data unless, or until, you really need them. Information you
need to fetch, if required, includes thumbnail images, ratings and comments, item data, group memberships, and user folder contents.
The code below shows how to fetch the thumbnail image from a portal item and convert it to a Bitmap.
// check item has a thumbnail
if (portalItem.getThumbnailFileName() == null) {
return;
}
// fetch the thumbnail
final ListenableFuture<byte[]> thumbnailFuture = portalItem.fetchThumbnailAsync();
thumbnailFuture.addDoneListener(new Runnable() {
@Override
public void run() {
// get the thumbnail image data
byte[] itemThumbnailData;
try {
itemThumbnailData = thumbnailFuture.get();
if ((itemThumbnailData != null) && (itemThumbnailData.length > 0)) {
// create a Bitmap to use as required
Bitmap itemThumbnail = BitmapFactory.decodeByteArray(itemThumbnailData, 0, itemThumbnailData.length);
// for example, set the Bitmap onto an ImageView if on UI Thread
imageView.setImageBitmap(itemThumbnail);
displayThumbnail(imageView);
}
}
}
});
You can convert this to a BitmapDrawable if required. Ensure that the code dealing with Views is performed on the UI threadrefer to
the API reference for ListenableFuture for information about the threads that the listener will be called on.
The same applies to the thumbnails of other classes, like users, groups, and organizations. Use fetchThumbnailAsync on
PortalItem, PortalGroup, and PortalUser. Additionally, PortalInfo provides fetchOrganizationThumbnailAsync and
fetchPortalThumbnailAsync.
Access item data

Portal items that represent files, such as tile packages, images, documents, PDF files, and so on, can be opened, downloaded, and then
stored or opened in your app or in another app. As in the previous example, you will need to specifically fetch the data of a portal item
after you create it. Use the fetchDataAsync method to do this.
Fetch a user's content

Many apps present a list of maps or other items that belong to the current user. Users can create folders within their portal accounts to
help organize their work. Apps should respect the user's view of their content and present the list of folders to the user, allowing the user
to choose which folder to look at in detail.

It's easy to get all the portal items owned by the authenticated user (that represent the content and services items created by that user).
PortalUser represents information about a user, and from this you can retrieve all of the items and folders (represented by
PortalFolder) owned by the user.
The code below iterates all of the items belonging to the authenticated user of the portal that are in the default (or root) user folder, using
the PortalUserContent returned from PortalUser.fetchContentAsync. Also, each folder and its contents are iterated, using
getFolders and fetchContentInFolderAsync.
final PortalUser user = mPortal.getUser();
// fetch the content in the users root folder
final ListenableFuture<PortalUserContent> contentFuture = user.fetchContentAsync();
contentFuture.addDoneListener(() -> {
try {
StringBuilder userInfo = new StringBuilder();
//iterate items in root folder...
final PortalUserContent portalUserContent = contentFuture.get();
for (PortalItem item : portalUserContent.getItems()) {
userInfo.append(String.format("Item: %s\n", item.getTitle()));
}
//iterate user's folders

for (PortalFolder folder : portalUserContent.getFolders()) {
userInfo.append(String.format("Folder: %s\n", folder.getTitle()));
//fetch the items in each folder
final ListenableFuture<List<PortalItem>> folderFuture = user.fetchContentInFolderAsync(folder.getFolderId());
folderFuture.addDoneListener(() -> {
try {
//iterate items in each folder
List<PortalItem> folderContent = folderFuture.get();
for (PortalItem folderItem : folderContent) {
userInfo.append(String.format("-Item: %s\n", folderItem.getTitle()));
}
}
});
}
}
});
More typically, you may write an Adapter class to show PortalFolders and PortalItems in a ListView to a user (perhaps showing
the title, thumbnail, and summary), and add the values from getItems and getFolders to those adapters.
Note: As seen in the code above, user content is another example of information that you must
explicitly fetch, like portal item thumbnails and content.
To get items shared with the current user, or items owned by a different user, you need to search for content.
List the groups a user belongs to

Groups can be configured in different wayssome groups are open to all users; some are only accessible by invitation; and for others,
any user can request to join. The groups to which the authenticated user belongs can be accessed, and for any group, the identities of the
members can be found.
The PortalGroup class represents a group. You can get a list of the groups a user belongs to by calling the
PortalUser.getGroups() method. Use fetchGroupMembershipAsync to retrieve the users in each groupafter that, you can get
the members from the getUsers method.
PortalUser user = portal.getUser();
for (PortalGroup group : user.getGroups()) {
//fetch the membership of each group.
final ListenableFuture<PortalGroupUsers> portalGroupUsersResult = group.fetchGroupUsersAsync();
portalGroupUsersResult.addDoneListener(() -> {
try {
//iterate the users in the membership
final PortalGroupUsers portalGroupUsers = portalGroupUsersResult.get();
List<String> groupUsers = portalGroupUsers.getUsers();
for (String userName : groupUsers) {
//do something with the usernames
}
}
});
}
From the group, you can find out if membership is by invitation only by examining the isInvitationOnly property, and if the user can
share items with the group using the isViewOnly property.

Search for content

Portals can contain a huge amount of information. To help your users find the information they want to work with, you can add searching to
your app. Searching can allow users to find information in different ways, for example, by searching for the groups that include a keyword,
or finding all portal items that are web maps having specific tags.
Portal administrators can configure a number of settings to highlight specific content to users, such as the set of available basemaps,the
content featured in the portal homepage and gallery, and the featured groups for the organization. Learn how to easily find featured
basemaps, content, and groups.
Searching is done from the Portal class. Publicly accessible items and groups can be accessed without any authentication, but to find
items that are secured, a user with access to the item must be authenticated with the portal. See Access the ArcGIS Platform for more
information about authenticating with a portal.
Search by defining query parameters

The API provides a flexible, generic search, along with some convenience methods to help you perform common portal searches.
Find portal items by keyword

To search for portal items using a keyword, construct a query that includes the keyword you want to search for. By default, the query will
return portal items that include the keyword in any of the common fields of a portal item, including the title, tags, description, and type.
The results of the query can be iterated.
Create a PortalQueryParameters object and pass the keyword you want to search for into the constructor as the query parameter.
Then pass the PortalQueryParameters to the Portal.findItemsAsync method. The resulting PortalQueryResultSet from
the future should contain all of the portal items that contain the keyword in any of the searched fields.
final PortalQueryParameters queryParams = new PortalQueryParameters("san francisco");
final ListenableFuture<PortalQueryResultSet<PortalItem>> findItemsFuture = portal.findItemsAsync(queryParams);
findItemsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
PortalQueryResultSet<PortalItem> queryResultSet = findItemsFuture.get();
// Process the query results...

showMessage(String.format("Total results found=%d", queryResultSet.getTotalResults()));
List<PortalItem> results = queryResultSet.getResults();
for (PortalItem item : results) {
// Process the results as required...
String resultInfo = String.format("Item Name:%s (ID:%s)", item.getTitle(), item.getItemId());
}
}
}
});
Note: Remember, only the items that are accessible to the authenticated user of the portal will be
included in the search results. When a user is not authenticated, only publicly shared items
are found.
By default, the result set contains only the first 10 results but provides a convenient way to fetch subsequent sets of results if required.
To learn more about working with large result sets, see Display many search results.
For a full list of the default fields used for searching, and complete information on constructing portal query strings, see the ArcGIS
Online Search reference.
Order the search results

If there are more than a few results, you may want to help your user narrow down the results to find items of most interest. Your app can
show the most recently updated results to the user first, sorting search results by the date they were last modified, in descending order.
queryParams.setSortField("modified");
queryParams.setSortOrder(PortalQueryParameters.SortOrder.DESCENDING);
Results can be sorted in either ascending or descending order, by portal item fields such as the title, date of creation or date last
modified, type, and owner. For a full list of sort fields, see ArcGIS Online Search.

Find items by type

You can restrict the results of a search to be a specific type or types of content; for example, you can search to find only web maps.
The setQuery method has a number of overloadsthe code below uses the overload allowing you to specify the PortalItem.Type
that results must match, along with a group ID (in this case, null indicates you want to search regardless of any groups) and the search
query. The PortalItem.Type enum provides a full list of content types that may be stored as items in a portal. Retrieve the results of
the query as shown previously for searching by keyword
final PortalQueryParameters queryParams = new PortalQueryParameters();
queryParams.setQuery(PortalItem.Type.WEBMAP, null, "san francisco");
If you want to find results of more than one type of portal item, you can do this by defining your query string.
Find items in your organization

By default, a search returns results from within an organization, and also public results from outside the organization. It may be useful to
restrict results to only those within the organization of the authenticated user, as shown below.
queryParams.setCanSearchPublic(true);
Portal administrators can turn off the ability for their users to search for items outside the organization when using the website. This
setting is independent of the query API, but you can get and use the portal-level setting as shown below to allow the portal
administrators setting to determine the search behavior in your app as well as in the website.
PortalInfo info = portal.getPortalInfo();
PortalQueryParameters queryParams = new PortalQueryParameters("san francisco");
queryParams.setCanSearchPublic(info.isCanSearchPublic());
Find groups by keyword

You can find groups by using a keyword in a similar way as it is used when finding portal items. For groups, the default fields searched
include title, description, and tags (as for portal items), but also include owner.
Create a PortalQueryParameters object and pass the keyword you want to search for into the constructor as the query parameter.
Then pass the PortalQueryParameters to the Portal.findGroupsAsync method. The resulting PortalQueryResultSet
should contain all of the groups that contain the keyword in any of the searched fields. In this case, the query should find all of the
groups containing "esri_demographics", including those owned by the user named "esri_demographics".
PortalQueryParameters groupQuery = new PortalQueryParameters("esri_demographics");
final ListenableFuture<PortalQueryResultSet<PortalGroup>> findGroupsFuture = portal.findGroupsAsync(groupQuery);
findGroupsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
PortalQueryResultSet<PortalGroup> groupResults = findGroupsFuture.get();
Find items in a known group

After a search for groups, you might want to list all of the items shared with those groups. Alternatively, you might want to list the items
in a group returned from the authenticated users list of groups. If a search result set contains at least one group, to find all the items in
that group, issue a second search using the group ID as part of the second query.
The code below continues from the example shown in find groups by keyword by creating a PortalQueryParameters using the
group ID from the PortalGroup from the initial search to set the group ID in the setQueryForItemsInGroup method. The
Portal.findItemsAsync method is called to search for the items within that group.
if (groupResults.getResults().size() > 0) {
for (PortalGroup group : groupResults.getResults()) {
// Create a PortalQueryParams for each found PortalGroup and search for contents of that group
PortalQueryParameters groupContentQuery = new PortalQueryParameters();
groupContentQuery.setQueryForItemsInGroup(group.getGroupId());
final ListenableFuture<PortalQueryResultSet<PortalItem>> findItemsFuture = portal.findItemsAsync(groupContentQuery);
@Override
public void run() {
try {
PortalQueryResultSet<PortalItem> groupContentResults = findItemsFuture.get();
// Display the featured content results...
processResults(groupContentResults);
}
}
});
}
}

Find items by ID
If you already know the ID of a portal item, you can search for it by using that ID. You might find this technique useful if your app is
closed while displaying a specific itemyou can save the ID and fetch the item again to ensure the item is still accessible and all the
properties are up-to-date, and use this information to restore the state of the app. If the search returns no results, then the item may no
longer be available; for example, the owner may have changed the access permissions, and your app can react accordingly.
You can perform a search by specifying the ID in the query string.
PortalQueryParameters itemIdQuery = new PortalQueryParameters("");
itemIdQuery.setQueryForItemWithId("1966ef409a344d089b001df85332608f");
final ListenableFuture<PortalQueryResultSet<PortalItem>> findItemsFuture = portal.findItemsAsync(itemIdQuery);
@Override
public void run() {
try {
PortalQueryResultSet<PortalItem> queryResultSet = findItemsFuture.get();
if (!queryResultSet.getResults().isEmpty()) {
PortalItem theItem = queryResultSet.getResults().get(0);
// Only expecting a single result as IDs must be unique
showMessage(String.format("Found item, title=%s", theItem.getTitle()));
}
}
}
});
You can also directly retrieve a PortalItem by ID using the overloaded constructor, passing in a Portal and the ID of the required
item.
final PortalItem portalItem = new PortalItem(portal, "1966ef409a344d089b001df85332608f");
portalItem.addDoneLoadingListener(new Runnable() {
@Override
public void run() {
showMessage(String.format("Loaded PortalItem by ID, title=%s", portalItem.getTitle()));
}
});
portalItem.loadAsync();
Define a query
If you need to search for items using more complex criteria, you can build a query to satisfy that criteria making use of multiple
predicates, Boolean operators, ranges, and wildcards. You could, for example, build a query that finds items that are web maps, owned
by the user "esri", with either of the tags "atlantic" or "pacific".
PortalQueryParameters searchStringParams = new PortalQueryParameters("type:\"web map\" AND owner:esri AND tags:(pacific OR atlantic)");
Adding specific criteria can be especially useful when you are localizing your app, as you can limit results to a specific culture.
PortalQueryParameters cultureQueryParams = new PortalQueryParameters("culture:fr-FR AND type:\"map service\"");
Tip: You can also search using ranges of dates that items were created and last modified, using
the created and modified fields of a portal item. However, be aware that portal searches use
UNIX epoch dates (defined as the number of seconds that have elapsed since midnight
January 1, 1970), as noted in the ArcGIS Online Search reference.
Search for featured basemaps, content, and groups

Portal administrators can configure a number of settings to highlight specific content to users. Configurable settings include the set of
available basemaps, content featured in the portal homepage and gallery, and featured groups for the organization.
Get Home page and Gallery featured content

Administrators can configure two groups that contain featured content to show in different situations. The portal gallery can be populated
either with the contents of a group, or with the top 100 most-viewed items. The homepage of the organization can also display featured
content from a chosen group, and the maximum number of items displayed can be separately configured. Depending on the type of
content that is featured, you may want your app to display the same featured items as shown in the website. For example, if the
featured items are web maps, app users may want to browse a list of these maps, and then open them.
The simplest way to search for the PortalItems featured as homepage content is to use the
Portal.fetchHomePageFeaturedContentAsync method. Note this returns all the potential featured items, and is not limited by the
number of items the portal administrator may have configured to be shown (which can be found from
PortalInfo.getHomePageFeaturedContentCount).

final ListenableFuture<List<PortalItem>> featuredContentFuture = portal.fetchHomePageFeaturedContentAsync();

featuredContentFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
final List<PortalItem> featuredContentItems = featuredContentFuture.get();
// Display the featured content results - can use PortalInfo.getHomePageFeaturedContentCount to find how many
// featured items are shown on the home page of the portal
processResults(featuredContentItems);
}
}
});
Similarly, the fetchFeaturedItemsAsync method returns the set of featured items shown in the gallery.
final ListenableFuture<List<PortalItem>> featuredItemsFuture = portal.fetchFeaturedItemsAsync();
featuredItemsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
final List<PortalItem> featuredItems = featuredItemsFuture.get();
// Display the featured items results...
processResults(featuredItems);
}
}
});
Alternatively you can find the group or groups configured to contain featured content or items by using
PortalInfo.getHomePageFeaturedContentGroupQuery or PortalInfo.getFeaturedItemsGroupQuery and using this
value to set the query string for a PortalQueryParameters. You can then use the query to find the group or groups, and in turn
query for the PortalItems contained. One advantage of this approach is that query results are returned in batches, suitable for
paging.
PortalInfo info = portal.getPortalInfo();
PortalQueryParameters featuredContentGroupQuery = new PortalQueryParameters(info.getHomePageFeaturedContentGroupQuery());
final ListenableFuture<PortalQueryResultSet<PortalGroup>> findGroupsFuture = portal.findGroupsAsync(featuredContentGroupQuery);

findGroupsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
PortalQueryResultSet<PortalGroup> featuredContentGroupResults = findGroupsFuture.get();
if (!featuredContentGroupResults.getResults().isEmpty()) {
// Get the featured group or groups and use as required, for example issue another query...
PortalQueryParameters groupContentQuery = new PortalQueryParameters();
groupContentQuery.setQueryForItemsInGroup(featuredContentGroupResults.getResults().get(0).getGroupId());
final ListenableFuture<PortalQueryResultSet<PortalItem>> findItemsFuture = portal.findItemsAsync(groupContentQuery);
@Override
public void run() {
try {
PortalQueryResultSet<PortalItem> groupContentResults = findItemsFuture.get();
// Display the featured content results...
processResults(groupContentResults.getResults());
if (groupContentResults.getTotalResults() > groupContentResults.getResults().size());
// results are present in more than one batch... deal with paging results
}
}
});
}
}
}
});
Get a list of configured basemaps

Many apps allow a user to change the basemap used to provide context for other data shown in a map. Portal administrators can
configure the list of basemaps they want to be available to a user of a portal by sharing web maps into a specific group.
final ListenableFuture<List<Basemap>> basemapsFuture = portal.fetchBasemapsAsync();
basemapsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
final List<Basemap> basemaps = basemapsFuture.get();
// Display the available basemaps. If required, access the Basemap.Item to get information about the
// PortalItem that references each Basemap item.
processBasemaps(basemaps);

}
}
});

For each web map in the result set, you can show the thumbnail and title of the item in a gallery or list. You can easily display a web
map from the selected item by using its ID.
Additionally, you can use another predefined query (PortalInfo.getBasemapGalleryGroupQuery) to find out the basemaps
group for a portal if required, and from there you can list the items in that group.
Get featured groups

A list of featured groups can be configured to appear on the Groups and My Organization pages of the website. You can find out these
groups, and in turn can get the contents as you would for any other group.
final ListenableFuture<List<PortalGroup>> featuredGroupsFuture = portal.fetchFeaturedGroupsAsync();
featuredGroupsFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
final List<PortalGroup> featuredGroups = featuredGroupsFuture.get();
// Display the available groups...
processGroups(featuredGroups);
}
}
});
Again, predefined query strings are available for the set of groups. Unlike the other predefined queries mentioned above, there are
multiple queries used to find all of the groups. You can get a list of queries from the portal, each of which should return a single featured
group.
Display many search results

Searches may return just a few results, or many thousands of results. To reduce network traffic and memory , search results are returned
in batches (by default, only the first 10 are returned), along with a count of the total results found on the portal.
Often, the required item is in the first set of results, but your app can let the user decide if they need to see more items, for example, by
scrolling past the end of a list, switching to the next page of results, or by tapping a button. You can easily issue another query to find the
next set of results, as the result set from your first query constructs the correct subsequent query for you.
The code below creates a PortalQueryParameters, sets the initial query, and calls the Portal.findItemsAsync method. After
iterating through the initial results, PortalQueryResultSet.getNextQueryParameters is used to get the correct query to find the
next set of results (you can check the getQuery method to find out how this works). If this object is not null, then a second call can be
made to retrieve another page of results; this pattern can then be repeated until getNextQueryParameters returns null, indicating there
are no more results to fetch.
queryParams = new PortalQueryParameters("global rainfall");
@Override
public void run() {
try {
// Process the query results...
resultSet = findItemsFuture.get();
processResults(resultSet);
// Check if there are more results beyond this first set.
PortalQueryParameters nextPageQuery = resultSet.getNextQueryParameters();
if (nextPageQuery != null) {
// Present a UI to page through results by using nextPageQuery...
}
}
}
});
If you want to retrieve results in larger batches, use PortalQueryParameters.setLimit to change the batch size.

Add items to a portal

Portals, such as ArcGIS Online and Portal for ArcGIS, can store many types of items. Most types are directly related to the ArcGIS
platform, including ArcGIS documents (.mxd, .3dd, .mapx), datasets and packages (.lyr, .kml, .tpk), service urls, and so on. You can also
store things like Microsoft Office documents (.docx, .pptx, .xlsx), comma-separated values (.csv), portable document format (.pdf), and a
variety of image formats (.jpg, .png, .tif). Perhaps the most familiar type of portal item is a web map a JSON description of the data in a
map, along with other display and behavioral properties. Web maps are particularly useful in your ArcGIS Runtime SDK apps, as they
provide a way for you to display a consistent set of data and symbology to your users. Portal items also offer the ability to make and save
changes to these items, if needed.
The PortalItem class represents an individual item stored in a portal. Each item includes the following:
Metadatasuch as a unique identifier (ID), title, summary, description, thumbnail image, and tags
Binary or text-based datafor example, the JSON that defines a web map or a feature collection, or a URL pointing to a map
service, or the binary data of a tile package or shapefile
Sharing settingsthe access level and groups to whom the item is accessible
This topic will describe creating new portal items in general, setting common properties, and adding them to a portal. For information
specific to working with web map portal items, see the Display a map and Save a map topics. For information about setting the right
access level for your items, see Share a portal item.
Create a new portal item

A new portal item must be created in the context of a particular portal, such as your ArcGIS Online organization. The user connecting to
the portal must also have permissions to create new items. See the Access the ArcGIS Platform topic for information about connecting to
a portal as an authenticated user. Once you've connected to your portal, you can create a new portal item by specifying the portal on
which it will be hosted, the type of data it will store, and a name (title) to display for the item. The item content be specified when initially
adding the item to the portal. A new portal item can be added to the root folder, or to any available subfolder for the currently authenticated
user.
Note: Currently, you can only create new portal items that store web maps or feature collections with
this ArcGIS Runtime SDK.
The following example creates a new portal item called "Forest Features" that stores a feature collection. It sets properties to provide a
summary (short description), a description, and a set of tags to improve searchability, and provides the json that defines the feature
collection. The code then adds the new item to the root folder of the user's portal.
// define relevant tags to help users find this new portal item
List<String> tags = new ArrayList<>();
tags.add("TES");
tags.add("Wakim National Forest");
tags.add("Endangered species");
// create a new portal item, setting the properties that describe the item to portal users. 'portal' is a
// Portal instance that is authenticated as a user with permission to create new portal items
newPortalItem = new PortalItem(portal, PortalItem.Type.FEATURE_COLLECTION, "Forest Features",
"The status of threatened, endangered, and sensitive species within the Wakim National Forest.",
"Wakim National Forest engangered species features",
tags
);
// create the content that this portal item will store; here, the json of an existing FeatureCollectionLayer
// is used to create the content.
FeatureCollection collection = featureCollectionLayer.getFeatureCollection();
PortalItemContentParameters content = PortalItemContentParameters.createJsonContent(collection.toJson());
// add the new item to the portal, with its content. Passing 'null' as the folder parameter saves the item
// to the users root folder
final ListenableFuture<String> addPortalItemFuture = authenticatedUser.addPortalItemAsync(newPortalItem,
content, null);
addPortalItemFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try
{
String newItemId = addPortalItemFuture.get();
showMessage(String.format("New item with ID '%s' was created", newItemId));
}
}
});

When adding a new item to a portal, you can specify a subfolder in which to store the item. The available subfolders are those that belong
to the currently connected portal user. The following example gets a list of the available subfolders in which a new portal item can be
stored.
// fetch the content in the authenticated user's root folder
final ListenableFuture<PortalUserContent> contentFuture = authenticatedUser.fetchContentAsync();
contentFuture.addDoneListener(new Runnable() {
@Override
public void run() {
// iterate user's folders
PortalUserContent portalUserContent = null;
try {
portalUserContent = contentFuture.get();
for (PortalFolder folder : portalUserContent.getFolders()) {
showMessage(String.format("Folder: %s\n", folder.getTitle()));
}
}
}
});
Update a portal item

A portal item can have content that is based on simple text or on binary data. The content for a portal item may be read from a local file as
text (for a CSV item, for example), as binary data (for an image file, for example), or simply set with a URL (for GIS services). You assign
content to a portal item when initially adding it to the portal (PortalUser.addPortalItemAsync) you can update a portal item's
content later using PortalItem.updateDataAsync, as shown in the following example.
// update the portal item content by passing in the new json string
final ListenableFuture<Void> updateDataFuture = portalItemToUpdate.updateDataAsync(newJson);
updateDataFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try
{
updateDataFuture.get();
showMessage(String.format("Item with ID '%s' was updated", portalItemToUpdate.getItemId()));
}
}
});
A portal item's thumbnail image can be set, and it is then updated on the portal, as shown in the following example.
// update the portal item thumbnail
portalItemToUpdate.setThumbnailData(itemThumbnailData);
final ListenableFuture<Void> updatePropertiesFuture = portalItemToUpdate.updateItemPropertiesAsync();
updatePropertiesFuture.addDoneListener(new Runnable() {
@Override
public void run() {
showMessage("Thumbnail was updated");
}
});

For best results, a thumbnail image should be 200 pixels wide by 133 pixels high (other sizes will be adjusted to fit). Acceptable thumbnail
image formats are: PNG, GIF and JPEG. The maximum file size is 1Mb
Set sharing
When a user creates a new portal item (using ArcGIS Online or an ArcGIS Runtime API) its accessibility is private by default, meaning
only the owner of the item (and the organization's administrators) are able to view it. If you choose to, you can share your portal item with:
The creator of the item and portal administrators
Your entire organization
Specified portal groups
Everyone
Note: To control sharing for an item, you must be able to connect to the portal as an authenticated
user with the appropriate permissions (the item owner or a portal administrator).
You may also choose to share your item among combinations of the above, such as your entire organization and some specified groups,
for example. See the Share a portal item topic for more information.

Share a portal item

When one of your users creates a portal item and adds it to a portal, using ArcGIS Online or this ArcGIS Runtime API, the item is private
by default. Only the owner of the item (and the organization's administrators) are able to view it. This level of sharing is indicated by the
portal item's access property.
if (portalItem.getAccess() == PortalItem.Access.PRIVATE) {
The access property indicates the item's highest level of sharing. So if the portal item has an access value of:
PrivateThe item is not be shared with anybody. Only the owner and administrator can view the item.
PublicThe item can be viewed by everybody.
OrganizationThe item can be viewed by every member of the organization that the item is created in.
SharedThe item can only be viewed by members of a group that the item is shared with.
You can allow users to change this level of sharing so that the portal item is available to the right users.
Share with everyone or a portal's organization

If you want your portal item to be accessible to everyone, you need to make it public. Any user who has access to the portal website can
then find and use the portal item. To make a portal item public, call the shareWithAsync method and pass true as the everyone
argument.
//Share publicly, with everyone
final ListenableFuture<Void> shareFuture = portalItem.shareWithAsync(true, false);
shareFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
shareFuture.get();
showMessage("Shared item with everyone");
}
}
});
To ensure only members of the user's portal have access to an item, you can share it with just the user's portal organization. To do this,
pass true for the organization parameter of the shareWithAsync method.
//Share with just the user's organization
final ListenableFuture<Void> shareFuture = portalItem.shareWithAsync(false, true);
shareFuture.addDoneListener(new Runnable() {
@Override
public void run() {
try {
shareFuture.get();
showMessage("Shared item with the organization");
}
}
});
Share with a portal group

If a user is a member of a group, they can share items that they own with that group. Sharing items with specific groups restricts access to
a smaller, more focused set of people. For details on portal groups, seeWhat is a group?. The following sections describe how to:
Find the groups that the portal item belongs to
Find the groups the user is a member of
Share a portal item with a group
Unshared a portal item from a group
Find a portal item's groups

You can determine which groups a portal item is currently shared with by calling the fetchGroupsAsync method on the portal item.
This asynchronous method returns three types of groups. In this example:
adminGroups contains the groups which the current user is an administrator of.
memberGroups contains the groups in which the user is a member.
otherGroups contains the public groups or groups that are shared to the user's organization but that the user is not a member
of.

This code displays the title of the groups that the item is shared with.
// Get a list of all the groups the item is shared with
final ListenableFuture<PortalItemGroups> itemGroupsFuture = portalItem.fetchGroupsAsync();
itemGroupsFuture.addDoneListener(() -> {
try {
PortalItemGroups portalItemGroups = itemGroupsFuture.get();
// Build a message with the groups that this portal item belongs to
StringBuilder messageBuilder = new StringBuilder(String.format("'%s' is a member of the following groups:\n", portalItem.getTitle()));
List<PortalGroup> adminGroups = portalItemGroups.getAdmins();
for (PortalGroup adminGroup : adminGroups) {
messageBuilder.append(adminGroup.getTitle()).append("\n");
}
List<PortalGroup> memberGroups = portalItemGroups.getMembers();
for (PortalGroup memberGroup : memberGroups) {
messageBuilder.append(memberGroup.getTitle()).append("\n");
}
List<PortalGroup> otherGroups = portalItemGroups.getOthers();
for (PortalGroup otherGroup : otherGroups) {
messageBuilder.append(otherGroup.getTitle()).append("\n");
}
System.out.println(messageBuilder.toString());

// ... deal with exception
}
});
Share a portal item with specific groups

To share a portal item with specific groups, first determine which groups it should be shared with. For example, you can determine which
groups the current user is a member of by iterating through the groups returned from PortalUser.getGroups() as follows:
// Get all the users groups
List<PortalGroup> usersGroups = authenticatedUser.getGroups();
// Decide which groups to share with
final ArrayList<PortalGroup> shareWithGroups = new ArrayList<>();
for (PortalGroup group : usersGroups) {
// Only choose groups that are not view-only
if (!group.isViewOnly()) {
shareWithGroups.add(group);
}
}
Note that some groups are view-only; that is, members can view the items already in the group, but cannot share other items with that
group. To learn more about users and groups, see Access content and Access the ArcGIS Platform.
Then to share the portal item with those groups, pass a list of these groups to the shareWithGroupsAsync method as follows:
final ListenableFuture<List<PortalGroup>> shareFuture = portalItemToShare.shareWithGroupsAsync(shareWithGroups);
shareFuture.addDoneListener(() -> {
try {
// Get a list of any portal groups which the item failed to be shared into.
List<PortalGroup> failedGroups = shareFuture.get();
if ((failedGroups != null) && (failedGroups.size() > 0)) {
System.out.println("Sharing failed for " + failedGroups.size() + " of the groups:");
} else {
System.out.println(String.format("Item shared into %d groups", shareWithGroups.size()));
}
}
});
If there is a problem sharing the portal item with some groups, the failures will be indicated in the values returned from the
shareWithGroupsAsync method.
Unshare a portal item from specific groups

To stop sharing a portal item with specific groups pass a list of these groups to the unshareGroupsAsync method as follows:
// Unshare the item from the specified list of groups
final ListenableFuture<List<PortalGroup>> unshareFuture = portalItemToShare.unshareGroupsAsync(unshareGroups);
unshareFuture.addDoneListener(() -> {
try {
// Get a list of any portal groups which the item unshare failed, for example groups it wasnt already shared with
List<PortalGroup> failedGroups = unshareFuture.get();
if ((failedGroups != null) && (failedGroups.size() > 0)) {
System.out.println("Unsharing failed for " + failedGroups.size() + " of the groups:");
} else {
System.out.println(String.format("Item unshared from %d groups", unshareGroups.size()));
}
}
});
Stop sharing
To stop sharing the item, call the unshareAsync method. Calling this method:

Makes the item private and accessible to only the item owner (and the organization's administrator)
Removes all groups from the item's groups list
// Make the portalitem private
final ListenableFuture<Void> unshareFuture = portalItemToShare.unshareAsync();
unshareFuture.addDoneListener(() -> {
try {
unshareFuture.get();
System.out.println("Stopped sharing portal item");
}
});

License your app

Before you deploy your ArcGIS Runtime app into production, you're required to license it with one of the four ArcGIS Runtime license
levels: Lite (free), Basic, Standard, and Advanced.
Note that other costs may be incurred when deploying your app, such as credits used by ArcGIS Online services in your app. For
example, if you use ArcGIS Online in your app and use more than 50 credits per month or your app generates revenue, you must
purchase a deployment plan. For details on deployment plans, see Terms of Use FAQ.
Note: No license is required to develop ArcGIS Runtime apps; there's no need to authorize your
development machine. As a member of the ArcGIS Developer Program, you have a free
ArcGIS Developer Subscription (Essentials Plan). With this plan you can download and install
any ArcGIS Runtime SDK and immediately have access to all the functionality of the APIs for
development purposes. You can become a member of the developer program for free.
Develop and test

You can download and install an ArcGIS Runtime SDK using an ArcGIS for Developer account. You then have access to all of the
functionality in the API for development and testing purposes. In this mode the app will adopt the following behavior:
Any map will be watermarked with the words Licensed For Developer Use Only (as pictured here).
Licensing your app for deployment will remove the watermark and console output and provide the appropriate capabilities to your app
users.
Licensing options
Before you can use your app in production, you are required to license the ArcGIS Runtime app. Esri provides four ArcGIS Runtime
license levels: Lite, Basic, Standard, and Advanced. Each additional level opens up more capabilities for your app users.
Two options are available to set the license level in your app:
Named user
A Named User refers to an ArcGIS organizational account that is a member of an organization in ArcGIS Online or ArcGIS Enterprise.
The ability to license a Runtime app is just one feature of a Named User. You need to include code in your Runtime app to enable a
user to sign in (log in) to a portal and return license details associated with their Named User account.
Use Named Users if your target audience has access to ArcGIS Online or ArcGIS Enterprise and use devices that will be online at least
once every 30 days (timeout for a Named User license for ArcGIS Runtime). One notable benefit of this model is the license for ArcGIS
Runtime travels with the Named User, not the app, so one Named User can license many ArcGIS Runtime apps.
License key
A license key is a text string that contains license details. License keys can be acquired through your ArcGIS for Developer account or
purchased in ArcGIS Runtime deployment packs. License keys are usually compiled into your Runtime app. Each installation of your
app available to a single user counts as a deployment.
Use a license key if your target audience does not have access to named user accounts with an ArcGIS Online organization or on-
premises Portal for ArcGIS, needs to use an application that will remain offline indefinitely, or needs to guarantee an application will
function if offline more than 30 days. Customers are required to track the number of ArcGIS Runtime deployments at the Basic,
Standard, and Advanced level. Each installation of your app available to a single user counts as a deployment.

Licensing capabilities
The following table shows the functionality associated with each license level, the available licensing option, and how to acquire a license:
License Capabilities License Key Named User

level
Lite Viewing maps, layers, and packages Available for free. Sign in to your ArcGIS for Developers Sign in as a level 1 or 2
from the ArcGIS platform account, go to Licensing Your ArcGIS Runtime app and Named User in an
copy the License Key from here. organization in ArcGIS
Routing
Online or Portal for ArcGIS.
Place finding
Edit features in public feature
services. These services are
available on the Internet and are not
secured.
Generate a mobile geodatabase
with features from a sync-enabled
feature service
Download updates from a feature
service to a mobile geodatabase
Basic All capabilities of Lite Deployment packs available for purchase. Sign in as a level 2 Named
Edit features in mobile Contact the Esri office that serves you or if you are in the User in an organization in
geodatabases, and features in United States call Esri at 1-800-447-9778. ArcGIS Online or Portal for
feature services, that are only ArcGIS.
accessible on a local network or are
secured
Synchronize edits to feature
geometry, attributes, and
attachments from a mobile
geodatabase to a feature service
Add, update, or delete content on
portals
Use of ArcGIS Online analysis
services
Standard All capabilities of Basic Deployment packs available for purchase. Not available yet.
Access to additional data Contact the Esri office that serves you or if you are in the
United States call Esri at 1-800-447-9778.
Local raster layers
Local raster elevation sources
ArcGIS Runtime raster
functions (for local rasters and
rasters from image services)
Advanced All capabilities of Standard Deployment packs available for purchase. Not available yet.
Contact the Esri office that serves you or if you are in the
United States call Esri at 1-800-447-9778.
Note: Beginning with the release of Portal for ArcGIS 10.5, members in an organization in ArcGIS
Online or on-premises Portal for ArcGIS can be assigned one of two membership levels. Level
1 can be used to license Runtime at the Lite level and Level 2 can be used to license Runtime
at the Lite and Basic level. For Portals prior to version 10.5, all Named Users are equivalent to
Level 2 and can be used to license Runtime at the Basic level.
License your app by following the instructions in the section below, License your app. After this is done, the watermark and debug
messages will no longer display and your app will be ready for distribution and use in production.
Extension licenses
ArcGIS Runtime offers extensions that provide access to additional capabilities, analysis tools, and/or data.
Extension Capabilities License Key Named

license User

Streetmap Works with all license levels Licenses Not

Premium available for available
for Use offline with mobile map packages purchase by the yet.
ArcGIS High-quality cartography maps user of your
Runtime app.
Offline Geocoding
StreetMap
Offline Routing Premium for
StreetMap Premium can be downloaded for these regions: ArcGIS Runtime
extension
North America licenses are
provided on an
Latin America
annual-term
Europe basis. The
Asia Pacific StreetMap
Premium
Middle East and Africa dataset cannot
Japan be used after
the license has
Each regional mobile map package is licensed with an extension license key. You can use any combination of these packages expired.
with their associated license keys. Contact the Esri
Note: StreetMap Premium for ArcGIS Runtime licenses are purchased and provided by the office that
customer. You must provide a mechanism for your app to access this license key. The serves you or if
StreetMap Premium data cannot be used after the license has expired. Upon expiration you are in the
the app user must purchase another license to continue using the data. You must provide United States
the correct messages in your app to notify the user that their license has expired or is due call Esri at
to expire. 1-800-447-9778.
License your app

Follow these steps to license your app with a License key or a Named User:
License your app with a license key

Using a license key involves adding code to set the license level at compile time so that the license key is built into the application.
1. Read the end user license agreement.

2. Find a location in your code that runs before any ArcGIS Runtime functionality is used.
3. Call the setLicense method on the ArcGISRuntimeEnvironment singleton object to license the app with a License key.
// license with a license key
ArcGISRuntimeEnvironment.setLicense("runtimelite,1000,rud#########,day-month-year,####################");
Your app is now licensed for deployment.
Note: If you don't license the app, then the map views will be watermarked with the words
Licensed For Developer Use Only.
License your app with a Named User account

Use of a Named User involves adding code to enable sign-in to using an ArcGIS organizational account. At runtime, a user must sign in
successfully to return their license information which will be used by the app to set the license level. Follow these steps to license your
app using the Named User's account:

3. Allow the app user to authenticate with an ArcGIS organizational account. Upon loading the Portal obtain the LicenseInfo
and use this to license the app. As part of the process, save the license information in preparation for your app being used in
an offline environment for up to 30 days.
// connect to ArcGIS Online or an ArcGIS portal as a named user
// The code below shows the use of token based security but
// for ArcGIS Online you may consider using Oauth authentication.
UserCredential credential = new UserCredential("user", "password");
// replace the URL with either the ArcGIS Online URL or your portal URL
Portal portal = new Portal("https://your-org.arcgis.com/");
portal.setCredential(credential);
// load portal and listen to done loading event

portal.loadAsync();
// get license info from the portal
LicenseInfo licenseInfo = portal.getPortalInfo().getLicenseInfo();
// Apply the license at Standard level
ArcGISRuntimeEnvironment.setLicense(licenseInfo);
});

4. If you saved the license information on local storage, your app can be started and licensed in an offline environment using the
saved license information. Retrieve the license from storage and license your app.
// connect to ArcGIS Online or an ArcGIS portal as a named user
// The code below shows the use of token based security but
// for ArcGIS Online you may consider using Oauth authentication.
UserCredential credential = new UserCredential("user", "password");
// replace the URL with either the ArcGIS Online URL or your portal URL
Portal portal = new Portal("https://your-org.arcgis.com/");
portal.setCredential(credential);
// load portal and listen to done loading event

portal.loadAsync();
// get license info from the portal
LicenseInfo licenseInfo = portal.getPortalInfo().getLicenseInfo();
// Apply the license at Standard level
ArcGISRuntimeEnvironment.setLicense(licenseInfo);
});
Note: If you fail to license the app then the map views will be watermarked with the words
Licensed For Developer Use Only.
Extension level licenses

3. Call the setLicense method on the ArcGISRuntimeEnvironment singleton object to license the app with a main license key
and any extension licenses.
// license with a license and a list of extensions
ArcGISRuntimeEnvironment.setLicense("runtimeadvanced,1000,rud#########,day-month-year,####################",
Arrays.asList("runtimeanalysis,1000,rud#########,day-month-year,####################", "another license extension code"));
Your app is now licensed to use the extensions.
Attribute Esri in your app

Esri requires that when you use an ArcGIS Online basemap, Esri data services, or Esri API technology in your app you must also include
Esri attribution. There are specific requirements for attribution you may be required to address in your app depending on how your app is
built and the data it uses. This is outlined in detail here in theAttribution in your app topic.

Deploy your app

ArcGIS Runtime SDK for Android enables you to build mapping applications for Android platform phones and tablet devices. Follow the
steps below to ensure you've licensed the capabilities your app uses and that you understand associated costs.
1. License your app.
2. If your app uses content or services from ArcGIS Online, get an ArcGIS Online developer subscription. See Plans for your options
and FAQ for details.
If your app is licensed at the Standard level and you would like to deploy it via an app store or marketplace, let us know by emailing
runtimelic@esri.com.

Release notes for 100.1.0

Version 100.1 of ArcGIS Runtime SDK for Android, also known as Update 1, is the first update to version 100.0.
This topic describes what's new and changed in this release and provides a list of known issues. For the previous version's release notes,
see Release notes for 100.0.
Documentation updates since the release

Clarified statement on this page about support for Arcade expressions.
Clarified statement on this page about support for heat maps.
What's new
3D
3D has been brought to the ArcGIS Runtime for native app development. Build 3D scenes with raster, tiled, and vector data sets
including 3D specific symbology for great better than flat visualizations. For more information, see the Display a scene topic.
Raster support on mobile devices commercially available

In the previous release, apps that used local raster data on mobile phones and tablets could only be deployed as BETA; Raster was
commercially supported only on desktop platforms. At 100.1, local raster capabilities are fully supported on mobile phones and tablets.
Take a map offline

Web maps or specific areas of a web map from a portal can be downloaded and used in disconnected scenarios. The new
OfflineMapTask provides a high-level API to download the map definition and its related data. When the map is taken offline, it is
stored as a mobile map. If the map contains sync-enabled feature layers, those can be edited offline and the changes synced when
network connectivity is later available. For details, see Offline.
Client-side labeling control

A new LabelDefinition class is introduced that defines how labeling is applied to feature data for a given scale range. You can
specify the following:
Which features are covered by the definition (by applying the label definition's where-clause)
What text should be displayed, based on the individual feature's attributes and the label definition label-expression formula.
Arcade expressions are supported in label definitions and visual variables but not in unique value renderers or class breaks
renderers.
How the text should appear, using the definition's text symbol
Where the text should appear with respect to its feature, using the definition's label placement
How to move or avoid other labels or features that would overlap each label
At this release, you can only construct a LabelDefinition instance from JSON but there is no explicit API for specifying labeling
settings.
Support for additional layer types

This release adds support for the following data layer types.
OGC WMTS
Image Service
Dynamic sublayers of an ArcGIS Map Service
OpenStreetMap
Bing

Extensible tile layers

This release provides APIs to display custom tiles. The WebTiledLayer is an extensible layer that requests map tiles from a web
service based on a URI template. It provides a simple way to integrate non-ArcGIS Services as a layer in a map. Also, custom tiled
layers can be created by sub-classing ImageTiledLayer and its subclass, ServiceImageTiledLayer. These two abstract classes
expose protected abstract methods to either fetch tile images or return the URL of the tile images. By extending these two classes and
implementing the abstract methods, you can create custom tiled layers and add them to a map.
Related tables
This release provides APIs for supporting related tables. With this, apps can handle workflows that involve reading, editing, and
querying related data in both spatial and non-spatial tables. These related table workflows are supported in both online and offline
maps. For details, see Relate features and Search for related features.
Display heat maps

A new HeatmapRenderer class uses the points in a layer to calculate and display the relative density of points on a map. The density
is displayed as a heat map by smoothly varying sets of colors ranging from cool (low density of points) to hot (high density of points). At
this release, this class is constructed only from JSON when it's defined in a web map and no explicit API is provided for working with it.
Sketch editor
A 2D SketchEditor class enables sketching geometries on a map. It can be used to create new geometries and edit existing ones..
This type of sketching is typically done through user interaction; programmatic sketching is also supported. The SketchEditor class
also support undo/redo of edits, custom styling of the editor, and a system of notifications for the developer to handle during the
sketching process.
Editing of public feature services available at the Lite license level

The ability to perform edits in a connected environment on a public feature services from ArcGIS Online or Enterprise at the Lite license
level has been introduced this release. At version 100.0, all editing capabilities began at the Basic level. The editing of private feature
services or editing in an offline environment remains at the Basic, Standard, and Advanced licensing levels.
Service area and closest facility analysis

Closest facility and service area tasks are now available for performing more network analysis in your ArcGIS Runtime applications.
A service area is a region that encompasses all streets that can be accessed within a given distance or travel time from one or more
facilities. For example, a three-minute, drive-time polygon around a grocery store can determine which residents are able to reach the
store within three minutes and are thus more likely to shop there.
The closest facility task generates routes between facilities and incidents. Routes may include a route shape and driving directions. The
task may generate routes from facilities to incidents or from incidents to facilities and can find a user specified number of routes, for
example finding the three closest fire stations for an address.
Coordinate formatting
The CoordinateFormatter class can be used to convert between points and formatted coordinates notation strings such as decimal
degrees; degrees, minutes, and seconds; U.S. National Grid (USNG); and Military Grid Reference System (MGRS).
Follow a graphic in 3D
Camera controllers allow you to change the default camera behavior in a scene view. Two "orbit" camera controllers were added to lock
the focus of a camera to a fixed point target or a possibly moving graphic.
Support for StreetMap Premium packages

StreetMap Premium for ArcGIS Runtime is a new data product, licensed as an extension to ArcGIS Runtime, that provides enriched
street data, which powers a high-quality cartographic map and high-quality search, geocoding, and route analysis. Streetmap Premium
for ArcGIS Runtime maps are consistent across all regions of the world and can be taken offline for disconnected use; they can
simultaneously fulfill the need for an address locator, street network dataset, and basemap in your app.

StreetMap Premium for ArcGIS Runtime delivers HERE data as a mobile map package (an .mmpk file) for your app to access locally.
This MMPK format allows the data to be accessed offline and therefore doesn't consume data from your user's data plan. This is the
same high-quality data used by ArcGIS Online services, including the World Geocoding Service, Routing Service, and Street Map
Service.
For more information, see Add StreetMap Premium data.
GeoView Attribution
MapView and SceneView have been enhanced to automatically display attribution for map and scene layers respectively. The
attribution is dynamic and updates as layers are added/removed, toggled on/off, or change visibility as they go in and out of scale range.
Other new items

Return type of MapView.getOnTouchListener() refactored from MapView.OnTouchListener() to
View.OnTouchListener().
API additions
The following list shows the new classes which have been added to the API:
3D
ArcGISScene
ArcGISScene.BasemapChangedEvent
ArcGISScene.BasemapChangedListener
ArcGISSceneLayer
ArcGISTiledElevationSource
AtmosphereEffect
DefaultSceneViewOnTouchListener
DistanceCompositeSceneSymbol
ElevationSource
LightingMode
LocationToScreenResult
LocationToScreenResult.SceneLocationVisibility
MarkerSceneSymbol
ModelSceneSymbol
RasterElevationSource
SceneSymbol
SceneView
SimpleMarkerSceneSymbol
Surface
Layers
ArcGISMapServiceSublayerInfo
ArcGISMapServiceSublayerInfo.ServiceType
BingMapsLayer
BingMapsLayer.Style
ImageServiceRaster
ImageTiledLayer.NoDataTileBehavior
MapSublayerSource
OpenStreetMapLayer

RasterSublayerSource
ServiceImageTiledLayer
SublayerSource
WebTiledLayer
Web Map Tile Service
WmtsLayer
WmtsLayerInfo
WmtsService
WmtsServiceInfo
WmtsTileMatrixSet
WmtsTileMatrixSet.TileMatrix
Network Analysis
ClosestFacilityParameters
ClosestFacilityResult
ClosestFacilityRoute
ClosestFacilityTask
ClosestFacilityTaskInfo
Facility
Incident
ServiceAreaFacility
ServiceAreaOverlapGeometry
ServiceAreaParameters
ServiceAreaPolygon
ServiceAreaPolygonCutoffGeometry
ServiceAreaPolygonDetail
ServiceAreaPolyline
ServiceAreaResult
ServiceAreaTask
ServiceAreaTaskInfo
StartTimeUsage
TravelDirection
Offline Map
GenerateOfflineMapJob
GenerateOfflineMapParameters
GenerateOfflineMapResult
OfflineCapability
OfflineMapCapabilities
OfflineMapItemInfo
OfflineMapSyncJob
OfflineMapSyncLayerResult
OfflineMapSyncParameters
OfflineMapSyncResult\
OfflineMapSyncTask

OfflineMapTask
Related Tables
RelatedFeatureQueryResult
RelatedQueryParameters
RelationshipCardinality
RelationshipConstraintViolation
RelationshipInfo
RelationshipRole
TableJoinSublayerSource
TableQuerySublayerSource
TableSublayerSource
Sketch Layer
SketchCreationMode
SketchEditor
SketchGeometryChangedEvent
SketchGeometryChangedListener
SketchStyle
General
AnimationCurve
ArcGISImageServiceInfo
AttributionTextChangedEvent
AttributionTextChangedListener
CameraController
CameraDistanceChangedEvent
CameraDistanceChangedListener
CameraHeadingOffsetChangedEvent
CameraHeadingOffsetChangedListener
CameraPitchOffsetChangedEvent
CameraPitchOffsetChangedListener
CoordinateFormatter
CoordinateFormatter.GarsConversionMode
CoordinateFormatter.LatitudeLongitudeFormat
CoordinateFormatter.MgrsConversionMode
CoordinateFormatter.UtmConversionMode
ExtendOptions
GeoprocessingParameterInfo
GeoprocessingTaskInfo
GlobeCameraController
HeatmapRenderer
OrbitGeoElementCameraController
OrbitLocationCameraController
PictureFillSymbol
PixelType

PopupRelatedFeaturesDefinition
PopupRelatedFeaturesSortOrder
RenderingRule
RenderingRuleInfo
API deprecations
The following list shows the deprecations in the API and where relevant the replacement API.
com.esri.arcgisruntime.concurrent package
Job.setUri(String) - no equivalent available, this method is for internal use only.
com.esri.arcgisruntime.mapping.popup package
PopupDefinition.setShowRelatedRecords(boolean) - replaced by
PopupRelatedFeaturesDefinition.setShowRelatedFeatures(boolean)
PopupDefinition.isShowRelatedRecords() - replaced by PopupRelatedFeaturesDefinition.isShowRelatedFeatures()
PopupManager.getRelatedRecords() - use existing method
ArcGISFeatureTable.queryRelatedFeaturesAsync(ArcGISFeature)
PopupManager.isShowRelatedRecords(ArcGISMap) - use existing method
PopupRelatedFeaturesDefinition#isShowRelatedFeatures()
com.esri.arcgisruntime.symbology package
PictureMarkerSymbol(BitmapDrawable) - replaced by PictureMarkerSymbol.createAsync(BitmapDrawable)
PictureMarkerSymbol.getImage() - use PictureMarkerSymbol.getImage(Resources) instead
com.esri.arcgisruntime.tasks.networkanalysis package
RouteTask(String) - replaced by RouteTask(Context, String)
RouteParameters.getPointBarriers() - replaced by RouteParameters.setPointBarriers(Iterable)
RouteParameters.getPolygonBarriers() - replaced by RouteParameters.setPolygonBarriers(Iterable)
RouteParameters.getPolylineBarriers() - replaced by RouteParameters.setPolylineBarriers(Iterable)
RouteParameters.getStops() - replaced by RouteParameters.setStops(Iterable)
Issues fixed from earlier Runtime versions

NIM100285 Documentation Enhancement Request: additional information and code snippets for the ClassBreak class in the
ArcGIS Android API
NIM102854 Some graphics are missing when calling MapView.getDrawingMapCache()
BUG-000083273 A file geodatabase is corrupted in HTC One
BUG-000089913 The GeometryEngine.Intersect Method returns an empty polyline instead of the required output created through
the operation. The method GeometryEngine.intersections is now available that allows for dimensionality.
BUG-000093433 Adding a z-value point to a z-value enabled feature service results in a table exception, which the shape must
not have a Z value
ENH-000103980 No method or classes exist that allow initializing credential objects with a token or setting a token for a secure
resource in the Android Runtime 100.x SDK
Known issues
Maps, layers, and general
MapViewlocationToScreen gives incorrect coordinates in wrap around mode.
Map view grid lines that lie close to the 180th meridian or poles may not always display correctly.
AutoPanMode and InitialZoomScale are ignored if set before starting location display.
PKI secured service throws SocketException instead of returning 403.
Querying FeatureTable does not complete if the table failed to load.
Cloning an unloaded map prevents it from rendering in a map view. Load the map before cloning it.

Text in vector tiled layers may not display at certain scales.

Vector tiled layers created from a URL don't have attribution.
Crash may occur on Android when zooming and panning with vector tiled layers.
Once a vector tile layer is cloned, there is no way to handle requests for it.
Related tables: When an origin feature is deleted, the key field of the related feature is not set to null for hosted services that
have a non-unique primary key.
Web maps saved from an ArcGIS Runtime app containing Bing Maps layers may not be compatible with older versions of the
Web Viewer.
ArcGIS Online currently does not support requesting features from feature services in a different spatial reference using the
latest WKID value stored in a map.
SpatialReference.equals() may return false when comparing Web Mercator spatial references.
When exporting a tile package from a service that is hosted in ArcGIS Online (tiles.arcgis.com) with a geometry that is not in the
same spatial reference as the service, the tile package will be corrupted and will not display correctly.
ArcGISSceneLayer does not support legends.
GeoView.getLayerViewState fails for a layer that has not finished rendering.
Using SketchEditor, you cannot digitize a polyline across the dateline.
Memory is not freed when graphics symbolized with picture marker symbols are cleared from a graphics overlay.
A Bing Maps layer created with a Portal needs to load the Portal first.
Definition expressions using time fields on spatial service feature tables will result in no features being displayed.
Cannot change definition expression after setting invalid definition expression on feature layer in a SceneView.
Feature layers with indexes on GlobalID fields may cause an app to crash.
Loading feature layers that have fill symbols with an outline with of less than 0 will return an exception.
Diagonal fill symbols render in opposite directions between JavaScript and Runtime.
Moving map view to a screen with a different DPI zooms the map in and out (5-10%).
Moving map view to a screen with a different DPI changes the size of the map content.
Symbol sizes for graphics in static mode differ in size between 2D and 3D views.
Vector tile symbols don't always scale consistently with DPI.
Map view doesn't zoom to geometry if the supplied geometry's envelope has zero height or width.
Setting minimum scale on a graphics overlay in a scene view is not accurate.
Calling the clone method on a loaded feature layer throws bad_weak_ptr exception.
Gradient fills used in mobile map package are not displayed correctly in apps.
Invalid base layer, reference layer, or operational layer will not raise LayerViewStateChangedEvent under certain scenarios.
In some cases, a feature layer can have a load status of Loaded but getRenderer still returns null.
Service feature table contents do not re-populate after clearing cache.
Service feature table can fail to load from a service with "Invalid JSON" error when the real problem is the JSON from the
service contains an unsupported image format.
There's an inconsistency in handling null values in JsonSerializable UnknownJson.
Popup title does not use name when the title is defined with a coded value domain field.
Popup.GeoElement.Attributes uses label/alias values instead of field names as keys for the attribute dictionary when used with
ArcGIS map services.
Field name in popup definition for Arcade expression does not include the title for the expression field.
Popup getSymbol returns null for features from a map service.
A geodatabase is taken out of scope even if its feature tables are in scope. This is because the geodatabase holds on to strong
references to its tables, but the tables do not have a strong reference back to the geodatabase (as this would lead to a circular
reference). This is by design. It's recommended to keep the geodatabase as a global variable.

Editing overrides for a feature layer in a web map are not honored.
Synchronizing large geodatabases with many features and no local edits may take longer than expected.
Offline features disappear intermittently during map interaction when syncing large geodatabase.
When registering a mobile geodatabase with a new user (different from user who created the mobile geodatabase), local edits
still apply the user who created the geodatabase when editor tracking is enabled.
When using local street address locators, suggestion results without a house number can't be used to retrieve results.
Locator performance may be poor for larger local locator datasets.
Saving map with ForceSave false and feature collection layers by reference throws exception. Workaround: ForceSave the map
and while loading the saved map set the visibility of FeatureLayer referenced by FeatureCollectionTable to true.
Functions are not supported in where clauses for labeling.
GeoprocessingJob.ToJson throws exception when it contains input parameter type of GeoprocessingFeatures with null features.
GeoprocessingJob.FromJson does not populate GeoprocessingFeatures.URL.
Raster
Adding rasters to MosaicDatasetRaster with some invalid parameters can fail without notifying the user.
Some 3D renderers on some platforms may not work correctly on MosaicRasterDataset.
In some cases, the default rendering applied to raster data may appear different from how it appears in ArcGIS Online.
The LoadStatusChanged event doesn't fire when using a MosaicDatasetRaster instance to create a mosaic dataset and
binding it to a RasterLayer for rendering.
When adding rasters to a mosaic dataset that is already being used for a raster layer, the new content will not show up in that
existing layer.
Raster layers report LayerViewState.Error ("Layer does not have SpatialReference") while loading. The layer will then
transition to LayerViewState.Active after self-correcting and loading the layer.
RasterLayer doesn't free a used raster before the application is shut down.
Image services
When an ImageServiceRaster is created with a URL, getPath should return null but instead it returns the URL.
Setting a color map raster function as rendering rule on an image service has no effect.
Visual artifacts can appear on a map when the default rendering rule of an image service has dynamic range adjustment (DRA)
enabled.
Setting a rendering rule on ImageServiceRaster after loading has no effect.
App may crash when exporting tile cache from image service that does not support it.
Symbols, renderers and graphics

TextSymbol doesn't honor the screen alignment property for feature layers.
Kerning does not work with simple Latin scripts, causing a performance problem with military symbol text.
PictureFillSymbol width, height, and image properties are not working correctly on scene view.
When kerning is enabled on a statically-rendered TextSymbol, it will appear misaligned and may render beyond the extent of
its background.
In a scene view, changing TextSymbol font weight or style does not affect the symbol as expected. The glyph spacing
changes, but the glyphs themselves remain the same.
In a scene view, changing TextSymbol halo color or size has no effect when symbolizing elements displayed in dynamic mode.
In a graphics overlay displayed using dynamic mode in a scene view, applying a font decoration to TextSymbol has no effect.
Crash when drawingInfo uses field alias name instead of field name when using advanced symbology.
Feature layers from federated 10.3 and 10.3.1 ArcGIS Servers cannot use the default advanced symbology setting.

When a specific offset value is applied to both dynamic and static picture marker symbols, the displacement is different on both
the graphics.
In static rendering mode, setting Y offset on TextSymbol causes the symbol to render twice, once at the old and once at the
new location.
When invoking toJson on LabelDefinition, certain text symbols may get serialized as "{}", losing their properties.
Symbols should be loaded before being used in a renderer sent to a service.
Random tile flickering may occur when adding polygons to a graphic overlay with horizontal fill symbol and transparent color, in
static rendering mode.
TextSymbol for a polygon graphic spanning the dateline and rendered in Static mode is displayed in the wrong location
when zooming out.
TextSymbol HaloColor and HaloSize properties have no effect when used with graphics in dynamic mode in a SceneView.
Military polyline and polygon symbols that render correctly in 2D do not render correctly in a graphics overlay in dynamic mode
in 3D.
Some military line symbols do not display in the correct location.
Symbol rotation type (arithmetic/geographic) is ignored by graphics.
Creating a swatch returns a null image for scene symbols.
Extruded graphics in a scene view may disappear while navigating the map.
Selection halo thickness for various types of graphics are not consistently sized.
Selection color does not display for a selected polygon with a transparent outline in a dynamic graphics overlay in a SceneView.
Graphics overlays drawn in static mode do not render correctly. Use graphics overlays in dynamic mode.
A service feature table will not render when unique value renderer contains classification values with commas.
Portal
New TypeKeywords and Tags objects are created when a PortalItem is loaded, rather than repopulating the existing objects.
Feature collections
A feature collection in a web map that doesn't have a spatial reference for its extent will not draw.
FeatureCollection.toJSON loses popup info properties.
Creating FeatureCollectionTable from FeatureQueryResult can throw an exception.
When creating a feature collection from an array of graphics, the graphics' symbols are not honored. Instead, the default symbol
is used.
Very large feature collections may cause an app to run out of memory and crash.
Web maps
Web maps with dynamic layers produced by ArcGIS Runtime do not draw correctly in ArcGIS Pro. Any overridden properties
(renderer, labeling, opacity, sublayer visibility, and so on) will revert to service-specified defaults.
Labeling behavior and display in a web map may not match between JavaScript and Runtime.
3D
Files added to an existing raster elevation source at runtime are not applied to the scene view.
Elevation of vertices of a 3D polyline drawn high above the surface, viewed in relative mode, can dip when the tile beneath it is
out of view and therefore unloaded.
SceneView.screenToLocationAsync can return inaccurate Z values.
The rotation property of a viewpoint is not applied when it is used to set a viewpoint for another view.
The color of a ModelMarkerSymbol can't be changed.
Models in a SceneView may render black on Android simulators.

Z-aware feature layers do not render correctly in scene view.

When using a scene layer package with a terrain, it can be seen through terrain.
Scene layer may not display due to limited device memory.
Alpha property incorrectly applied during image export of a SceneView.
Labels for feature layers do not display on scene view.
An application might fail when using military symbology layers in a graphics overlay with a scene. This does not happen with
military feature layers.
Setting minimum scale on a graphics overlay in a scene view may not always be accurate.
Set viewpoint with NAN scale value causes globe in SceneView to render black.
Edges of polyline may appear behind globe in SceneView.
A selection highlight doesn't work when two graphics overlap.
screenToLocationAsync sometimes gives unexpected elevations when zoomed out.
In a scene view, changing the identify tolerance for graphics overlay behaves as though a zero tolerance is set.
Graphics overlay selection halo does not appear around selected symbols that are fully transparent.
The thickness of the selection halo varies between different symbol types.
For both compact and exploded caches in Web Mercator, an error occurs reading the cache configuration.
Rendering graphics in static mode near the poles or at varying distances from a camera may display unexpected results.
Camera from CurrentViewpoint on SceneView always returns null.
Multiple touch points for scene interactions, except for zoom, have not been implemented yet.
Layer refresh interval does not work in 3D scenes.
When rotating down on a scene view, the rotation stops when the clicked point is at 0,0.
For a Scene (3D), WGS 1984 is the only supported spatial reference.
App can crash when no symbol is set on a extrusion renderer.
Portions of building models may become transparent when panning the 3D scene.
Models in a SceneView may render black on iPhone 5 devices.
Identify operation can return empty results for ArcGISSceneLayer.
Graphics that not visible can be identified in a SceneView.
Unable to identify a partially-transparent symbol for a graphic in a dynamic graphics overlay in a SceneView.
Visibility of a graphic in a SceneView is determined by geometry, not display location.
Scene layer transparent pixels are not rendering correctly on Android platforms.
Transparent simple marker graphics on a 3D scene view do not correctly display all symbols that are directly behind them.
A 3D scene may exhibit significant flickering while adding a new feature.
Selected features may flicker in a scene view.
Scene layer packages are sometimes visible through the terrain.
3D vertical extrusion is applied to a graphic's symbol when it should only be applied to the renderer's symbol.
Rendering of dynamic graphics in a SceneView is fragmented in iOS simulator.
A crash can occur when destroying SceneView on Android if pause/resume are not called.
Miscellaneous
When a self signed certificate is trusted it is always cached and is not cleared.
Multiple Authentication Challenges may be fired for concurrent requests.
MapView.setViewpointGeometryAsync(Geometry, int padding) ignores padding and doesn't zoom to geometry for horizontal
lines.

A cached portal credential may not be used to access a second portal.

Authentication challenge issued when accessing a certificate secured portal under some workflows.
The map extent saved to a portal may not be accurate under some circumstances.
Basemap created by Basemap.copy() doesn't display.
Map save methods need to load map implicitly if not yet loaded.
UnsupportedOperationException thrown when calling ArcGISMapServiceInfo.getDocumentInfo().getTextAntiAliasingMode().
Upper case characters in OAuth Redirect URIs will not work.
TextSymbol does not honor SCREEN alignment property for feature layers.
Sync fails with ArcGIS Server 10.3 feature services that have realm applied.
SceneView crashes on some older devices (e.g. Asus Transformer Pad TF300T, Nexus 7 2012 version, Galaxy Note 10.1)
Default challenge handler prompts again after un-checking Remember and clicking BLOCK in the Untrusted Host dialog.
Sketch Editor fails to start sketching (NullPointer) if map changed with same SR since SR changed listener was not fired. Make
sure the map is done loading before calling start on the sketch editor.
Portal user is not set after logging into a PKI portal.
PKI portal with both client and server certificate fails to load, throws ArrayStoreException. The workaround is to use client
certificate only in the keystore.
Camera.zoomToward with factors of 0 or less cause Camera failure.
After connecting to a portal, you may get challenged again when accessing a federated service.
In a SceneView the selected graphic always renderers on top.
Popup title does not use name when defined with a coded value domain field.
When creating a feature collection from an array of graphics, the graphics' symbols are not honored.
Capabilities overridden in web map are not honored.
Applying a label definition to an ArcGISMapImageSublayer doesn't work.
Using MapView.identifyLayersAsync(...).get() hangs. It works if using a done listener instead.
Some PopupAttachment file name extensions will get changed after upload.
LocationDisplay symbol may change between navigation and default location symbols while mode remains Navigation Mode if
velocity of location update is 0.
MapView.getLocationDisplay() may block thread for several seconds.
NavigationChangedEvent fires multiple times when panning + flick, and will return false for isNavigating even if the map is still
moving.
exportImageAsync() fails to create a valid image on some devices (e.g. Nexus 7)
PopupManager.isShowAttachments returns incorrect value for features from a map service.
PopupManager.getFormattedValue() returns null/empty for identify popups from map services 10.4 or earlier.
Vector tiled layer using static basemap constructors not loading on some older devices (e.g. Nexus S and ASUS TF300T) due to
ssl issue.
GL context creation is problematic on some devices (e.g. Nexus 7 (2012) and ASUS fonepad 7).
Related topics
Release Notes 10.2.8




The 100.0.0 version of ArcGIS Runtime SDK for Android is the next generation of ArcGIS Runtime.
This major release introduces new and purposefully redesigned APIs from previous releases. This topic describes what's new, what's
changed, and known limitations in this release.
The 100.0 release is the first release in the Quartz family. The Quartz code name reflects the next generation of ArcGIS Runtime, built
from the ground up using a new architecture. This has enabled new capabilities and performance optimizations and provides API and
functional consistency across all of the Runtime SDKs. The entire API was re-imagined to incorporate these new capabilities and best-of-
breed ideas from all of the ArcGIS Runtime SDKs.
Below are details of what's new and changed in this release.
What's new
This release of the ArcGIS Runtime puts the map at the heart of the API to allow developers to quickly leverage the ArcGIS platforms Web
GIS capabilities. The following additions highlight the benefits of the new ArcGIS Runtime release.
Maps
The Map object has been split out from the view that displays it, to represent a model component from a Model-View-Controller
architecture. This important object at the heart of the ArcGIS Runtime has an API that follows the ArcGIS Web GIS information model. It
contains operational layers, basemaps, bookmarks, popups and other ArcGIS specific data to enable these to be leveraged in your
apps. It also includes convenient APIs to instantiate it from URLs, portal items or default basemaps so you can get great maps working
quickly.
Note: Version 2.0 of web maps and higher are supported (web maps from Portal for ArcGIS 10.3
and above); pre-2.0 versions are no longer supported.
Views
GeoViews (MapView and SceneView) are solely responsible for display and interaction, separating concerns from the model objects
and allowing the APIs to be simplified and harmonized between the 2D and 3D worlds. The Views contain Graphic Overlays, as well as
operations to easily identify features and graphics without having to write any layer type specific code.
Go offline
To make things easy for you, the APIs for common operations such as editing, searching, geocoding or routing are the same whether
you are online or offline.
Mobile map packages Offline maps with great symbology, place search and directions can be packaged with ArcGIS Pro,
side loaded onto your device and used in the Runtime through Mobile Map Packages. A mobile map package is a set of items
bundled together for transport, often for use in offline workflows. The items are one or more maps, their associated layers and
data, and optionally networks and locators. A mobile map package also includes metadata about the package.
Offline services You can also take your connected ArcGIS based feature and tiled layers offline line on demand with
dedicated Tasks and associated Jobs. The GeodatabaseSyncTask works with ArcGIS feature services to take features offline in
a mobile geodatabase (.geodatabase file) and allow them to be edited and synced. The ExportTileCacheTask extracts tiles from
a tiled ArcGIS map service as a tile package (.tpk file) and allows them to be viewed offline.
For more information, see the "Create an offline map" topic in this guide.
Vector tiled layers

You can use vector tiled layers in your ArcGIS Runtime app. These layers are similar to raster-based tiled layers but they are faster,
smaller, and look better on high resolution devices. They also differ in the way cartography is delivered. Instead of raster pixels, vector
tiled layers deliver cartography using vectors so cartography is rendered at runtime leveraging all the available pixels on the device. The
file format is binary and conforms to the Mapbox vector tile specification. Vector tiled layers don't contain any feature data and they don't
support identify or search operations. For details, see the API reference for ArcGISVectorTiledLayer or see the "Tiled layers"
section in the "Layers" topic in this guide.

Graphics as overlays
Graphics have always been used to display temporary application data on top of a map. To formalize this usage, graphics are now
added to GeoViews (MapView or SceneView) as overlays. This ensures that graphics are always displayed on top, even when map
layers are reordered. This also makes it convenient to switch out maps while still keeping the graphics in place. For more information,
see the "Add graphics overlays to your app" topic in this guide. It is now also possible to identify graphics overlays in a map view via a
single convenient method.
Raster (in beta)

This capability is Beta for deploying on mobile platforms.
You can now add raster data on desktop devices from many popular raster file formats such as DTED (Digital Terrain Elevation Data),
GeoTIFF, RPF (Raster Product Format), NITF (National Imagery Transmission Format), HRE (High Resolution Elevation), Erdas
Imagine, etc.
World files are no longer required to display GeoTiff and NITF formats.
Change the visualization of raster data by computing hillshades, applying colormaps, or stretching the statistical distribution of pixel
values.
New layer names

Other changes have been made to layer names: Use ArcGIS map image layers for adding ArcGIS Server map services. Use ArcGIS
tiled layers for adding ArcGIS Server tiled map services and tile packages. Use a Feature layer with associated Feature Tables for
adding layers or tables from ArcGIS feature services and geodatabases (including non-spatial tables). See the "Layers" topic in this
guide for information on the supported layer types.
Web map pop-ups

Web map pop-ups allow you to customize how the data in your layers are presented to users. A new full popup API has been added to
allow you to tap into the their configuration and build great user experiences for your users which include feature editing. Those layers
which allow popup definitions implement the new PopupSource interface. The map view also provides coarse-grained methods to
identify pop-ups taking into consideration different types of layers, their visibility, scale range, and pop-up configuration, and so on, and
returns a list of pop-ups for features at a given location.
Note: Version 2.0 of web maps and higher are supported (web maps from Portal for ArcGIS 10.3
and above); pre-2.0 versions are no longer supported.
Portal integration
The mapping API seamlessly integrates with the portal API, allowing you to access portal content and use them as maps. You can also
edit existing maps or author completely new maps and save them back to the portal, which can then be used elsewhere in the ArcGIS
system. For details see the "Access portal content" topic in this guide.
Loadable pattern
Resources, such as maps, layers, tasks etc, that load metadata asynchronously to initialize their state adopt the loadable pattern. This
pattern makes the behavior of loading state more consistent and uniform, and also makes its asynchronous nature more explicit.
Loadable resources do not automatically load their state. They load lazily, when asked either by the developer, or by other objects that
depend on it. The status of a loadable resource can be easily monitored to determine if it is loading, loaded successfully, or failed to
load, and you can retry loading it if it failed to load. For more information, refer to the loadable pattern topic in this guide.
Loadable features
Features retrieved from ArcGISFeatureTable have been optimized to contain only a minimum set of attributes which are required to
render them on a map. To get the full list of attributes, the feature has to be explicitly loaded. This optimization reduces latency and
bandwidth consumption while displaying features, but still allows you get the feature's complete data if you want to edit or display
feature details. When editing features, they must be loaded first.

Centralized handling of authentication

All security and authentication related aspects are managed by a newAuthenticationManager class which helps to unify and
centralize how authentication is performed regardless of the security mechanism being used or the operation being performed. The
authentication manager issues an authentication challenge whenever security related events are encountered. Developers can monitor
these challenges and respond with credentials to get access to secured resources, or allow the authentication manager to prompt the
end user for credentials. For more information, refer to the API reference documentation for AuthenticationManager
Geometries and geometry builders

The fundamental geometry objects remain the same - point, multipoint, polyline, and polygon but they are immutable and cannot be
modified once they are created. The constructors on geometry objects allow them to be created easily in one shot if their coordinates
are known, but you can also use geometry builders to progressively construct new geometries, either from scratch or by using an
existing geometry as the starting point and then manipulating its coordinates. For more information see the "Edit geometries" topic in
this guide.
Error handling
It's now easier to determine where errors occur in the stack so you can provide better error messages to your users. A new
standardized error domain property is available, which indicates if the error occurred client-side within the ArcGIS Runtime or server-
side from an ArcGIS Server service or web service. A consistent error code property can be used to further diagnose what the error was
and what error message should be displayed to the user. A listing of error code descriptions is provided in the "Platform error codes"
topic in this guide.
New async pattern

A brand new consistent asynchronous pattern has been developed, extending the familiar Future java pattern with an interface called
ListenableFuture. This new API allows you to add as many listeners as required to know when the method is complete.
Other new items

A new location display implementation which allows custom data sources.
A new way of configuring network requests using the request configuration class.
New interface for objects which can be serialized to and from json called JsonSerializable
The introduction of listenable lists which allow you to be notified when items change.
Issues fixed from earlier Runtime versions

ENH-000098709 When loading the map in Android, allow the android runtime the ability to resume the loading automatically when
network connection is lost
BUG-000097470 Having two transparent map service layers in a map view only allows one of them to be shown at a time on
Android 6.0 devices
BUG-000097661 Callouts are flickering in the Android SDK when they are moved to a new location
ENH-000087304 Symbology from MapService and FeatureService should have same sizes rendered on Mapview.
ENH-000094002 NAVIGATION AutoPanMode should keep activated when speed is 0.
BUG-000093433 Adding a z-value point to a z-value enabled feature service results in a table exception, which the shape must
not have a Z value.
ENH-000088172 Have the ability to perform the cut operation in an offline mode.
ENH-000081456 The Symbols with ArcGIS Runtime SDK for Android for ArcGISDynamicMapServices are displayed larger than
those displayed in ArcMap and applications build using Web APIs.
NIM082528: image rendered has different size than ImageView if initialized using the same drawable.
NIM103325 Add 'forStorage' parameter to 'find' and 'reverseGeocode' methods in the Locator class of ArcGIS Runtime SDK for
Android.

NIM103285: mapExtentChanged method needed in ArcGIS Runtime for Androidthe 100.0 release of the Runtime includes the
ability to add a listener to the map view that will be called when the visible area changes
(MapView.addVisibleAreaChangedListener).
NIM093425: Support disablePan on MapViewin the 100.0 release of the Runtime you can set the MapOnTouchListener on
the map view, allowing complete control over the gestures that perform interactive navigation.
Known issues
Maps
Deadlocks may occur if a map is destructed while it has outgoing requests.
In some cases, wrap-around does not stay enabled.
Map zooms in and out (5-10%) when dragged between monitors with different DPI
Some specialized layers are not supported in this release: KML, WMS, WMTS, OpenStreetMap, Bing, CSV by reference and
GeoRSS.
Maps do not open consistently at exactly the same initial extent.
Map view grid lines close to the date line and poles may not display.
MapView doesn't zoom to geometry if the supplied geometry's envelope has zero height or width.
Cloning/copying an unloaded map does not render in a map view.
Quickly opening a mobilemap and then destroying the mapview may cause a crash
Web maps
A web map won't open when a feature layer's type ID is not an integer.
Pop-up title does not use name when its defined with a coded value domain field.
There's an inconsistency in handling null values in JsonSerializable UnknownJson.
Map does not display any features for FeatureLayer with date-based definition expression using the timestamp keyword.
Layers
Vector tiled layers (ArcGISVectorTiledLayer)
DrawStatus does not complete when zoomed out to lowest level of detail (LOD) and no labels are displayed
Vector tile symbols don't scale consistently with DPI
Vector tiled layers created from a URL don't have attribution
Crash may occur on Android when zooming and panning with vector tiled layers.
A vector tiled layer may crash if you interact with it before it has begun drawing.
ArcGISTiledLayer fails to load with cached image service as portal item
If the URL property under basemap doesn't exist in a layer type unsupported by ArcGIS Runtime, the layer will not get
serialized.
Overrides to definition expressions on sublayers in a map image layer from a portal item are not respected.
Symbols, renderers and graphics

Points are not drawn on a graphics overlay if they're on the dateline.
If min/max scale is changed on graphics overlay before the map is loaded, min/max scale on the map view is locked.
The LocationDisplay symbol may sometimes behave strangely in navigation mode.
ClassBreaksRenderer with one class break and no minimum value symbolizes features incorrectly
Popup.Symbol returns null for features from a map service.
For GraphicsOverlay, the selection doesn't show for fully transparent symbols.
When creating a feature collection from an array of graphics, the graphics symbols are not honored.
For graphics overlays in dynamic mode, a renderer's rotation is used even if the graphic's symbol is overridden.

Symbol rotation type (arithmetic/geographic) is ignored by graphics.

Extrusion is applied to symbol in graphics when it should only be applied on symbol in renderer
Feature layers from federated 10.3 and 10.3.1 ArcGIS Servers cannot use the default advanced symbology setting.
Features with uncompressed BMP symbols may not display.
Static graphic overlays render fill symbols with an outline even if it is set to Null. Use a transparent outline instead.
Feature layers
Large amounts of local feature data delays tiles
When syncing a large geodatabase, offline features disappear intermittently during map interaction
Synchronizing large geodatabases with many features and no local edits may take longer than expected.
ArcGIS Online doesn't support requesting features from feature services in a different spatial reference using the latest WKID
value stored in a map
TextSymbol doesn't honor the screen alignment property.
Creating a feature with an invalid field name throws an incorrect error (an ownership-based access error)
Sometimes, when changing zoom levels, there's a drawing delay for symbols for features in a FeatureLayer.
Raster data
Raster renderer produces different results between MapView and SceneView
RasterLayer doesn't free a used raster before the application is shut down.
Geoprocessing
To return m and z values from the Submit geoprocessing tasks, you must include the returnZ=true and return=true
parameters to the call that fetches the output value of the GeoprocessingFeature.
Miscellaneous
Suggestion results from local street address locators cannot be used to retrieve results if they don't contain a house number
Geodatabase objects may be taken out of scope too soon, so accessing tables once the geodatabase is loaded may fail. It's
recommended to keep the geodatabase as a global variable.
Locator performance may be poor for larger local locator datasets.
Calling pause on a job that is downloading a file does not pause the job.
Creating a FeatureCollectionTable from a FeatureQueryResult throws an exception.
ReturnGeometry set to false is not honored when QueryParameter is passed to PopulateFromServiceAsync
Arcade expressions using date formatting string will get different results compared to the Javascript webclient.
MapView.setViewpointGeometryAsync(Geometry, int padding) ignores padding and doesn't zoom to geometry for horizontal lines.
A cached portal credential may not be used to access a second portal.
Authentication challenge issued when accessing a certificate secured portal under some workflows.
The map extent saved to a portal may not be accurate under some circumstances.
ServiceFeatureTable leaves behind temporary files when application is closed.
Basemap created by Basemap.copy() doesn't display.
UnsupportedOperationException thrown when calling ArcGISMapServiceInfo.getDocumentInfo().getTextAntiAliasingMode().
Upper case characters are not supported in Redirect URIs.

TextSymbol does not honor SCREEN alignment property for feature layers.
Sync fails with ArcGIS Server 10.3 feature services that have realm applied.
LocationDisplay symbol may change between navigation and default location symbols while mode remains Navigation Mode if
velocity of location update is 0.
PictureMarkerSymbol offset may be incorrect on some devices
MapView.getLocationDisplay() may block thread for several seconds.
NavigationChangedEvent fires multiple times when panning + flick, and will return false for isNavigating even if the map is still
moving.
exportImageAsync() fails to create a valid image on some devices (e.g. Nexus 7)
PopupManager.isShowAttachments returns incorrect value for features from a map service.
PopupManager.getFormattedValue() returns null/empty for identify popups from map services 10.4 or earlier.
Domain and date fields won't be substituted in PopupManager.getCustomHtmlDescription.
Vector tiled layer using static basemap constructors not loading on some older devices (e.g. Nexus S and ASUS TF300T) due to
ssl issue.
GL context creation is problematic on some devices (e.g. Nexus 7 (2012) and ASUS fonepad 7).
API changes since Beta 3

LocationDisplay get/set symbol methods now use Symbol, use a Marker or Composite symbol where necessary.
ArcGISRuntimeEnvironment has a new licensing API.
Field UNKNOWN of type AntiAliasingMode has been removed.
ArcGISFeatureLayerInfo is no longer Loadable or a RemoteResource, obtain this class from a service feature table.
ArcGISFeatureServiceInfo is no longer Loadable or a RemoteResource, obtain this class from a task or geodatabase.
ArcGISMapServiceInfo is no longer Loadable or a RemoteResource, obtain this class from a map image laye.r
Field UNKNOWN of type TextAntiAliasingMode has been removed.
VectorTileSourceInfo is no longer Loadable or a RemoteResource, obtain this from a vector tiled layer.
com.esri.arcgisruntime.datasource renamed to com.esri.arcgisruntime.data.
Class from com.esri.arcgisruntime.datasource.arcgis added to com.esri.arcgisruntime.data.
AngularUnitId field UNKNOWN has been renamed to OTHER.
AreaUnitId field UNKNOWN has been renamed to OTHER.
GeodesicDistanceResult renamed to GeodeticDistanceResult.
GeometryEngine.distanceGeodesic and GeometryEngine.moveGeodesic renamed to use Geodetic.
Field UNKNOWN of type GeodeticCurveType has been removed.
Field UNKNOWN of type GeometryBuilderType has been removed.
LinearUnitId Field UNKNOWN has been renamed to OTHER.
ImageTiledLayer.RenderMode has been removed, not needed with new symbol size and scale logic of map view.
VisibilityChangedEvent and VisibilityChangedListener removed from ArcGISSublayer.
BackgroundGrid moved to com.esri.arcgisruntime.mapping.view package.
Field UNKNOWN of type Basemap.Type has been removed.
TimeExtent has been removed, time not supported in this release.
Bookmark.get/setTimeExtent removed.
GeoView.get/setTimeExtent removed.
LayerTimeInfo.getTimeExtent removed.
ServiceTimeInfo.getTimeExtent.
Field UNKNOWN of type Viewpoint.Type has been removed.

MobileBasemapLayer moved to com.esri.arcgisruntime.layers package.

MobileMapPackage moved to com.esri.arcgisruntime.mapping package.
GeometryBuilderRequiredEvent and GeometryBuilderRequiredListener removed.
AdjustForWrapAround has been removed.
MapView.locationToScreen no longer takes the AdjustForWrapAround parameter.
IdentifyPopupResult removed, IdentifyLayerResult now contains popups.
GeoView identify methods changed to include new returnPopupsOnly only parameter.
IdentifyLayerResult getIdentifiedElements renamed getElements.
ImageLayerGeoElement removed, instances of Feature now returned from map image layer identify operations.
Field UNKNOWN of type LayerViewStatus has been removed.
NavigationCompletedEvent removed, use NavigationChangedEvent.
NavigationCompletedListener removed, use NavigationChangedListener.
PortalAccess and PortalGroupMembership removed, use PortalInfo.Access, PortalUser.Access, PortalItem.Access and
PortalGroup.Access.
PortalItemContentParams renamed to PortalItemContentParameters.
PortalItemType renamed to PortalItem.Type.
PortalMode renamed Portal.Mode.
PortalQueryParams renamed PortalQueryParameters.
PortalQueryParams.SortOrder renamed to PortalQueryParameters.SortOrder.
PortalUserRole renamed to PortalUser.Role.
CimSymbol, CimLineSymbol, CimPointSymbol, CimPolygonSymbol removed, Symbol instance now returned for advanced
symbols (default symbols).
Field UNKNOWN of type ClassBreaksRenderer.NormalizationType has been removed.
Field UNKNOWN of type MarkerSymbol.AngleAlignment has been removed.
Field UNKNOWN of type RotationType has been removed.
Field UNKNOWN of type TextSymbol.FontDecoration has been removed.
Field UNKNOWN of type TextSymbol.FontStyle has been removed.
Field UNKNOWN of type TextSymbol.FontWeight has been removed.
Field UNKNOWN of type TextSymbol.HorizontalAlignment has been removed.
Field UNKNOWN of type TextSymbol.VerticalAlignment has been removed.
com.esri.arcgisruntime.tasks.route renamed com.esri.arcgisruntime.tasks.networkanalysis.
ExportTileCacheSizeEstimate renamed ExportTileCacheSizeResult.
ArcGISFeature.addAttachmentAsync and updateAttachmentAsync now use a byte[] rather than File
ArcGISMap.save and saveAs methods have a new property called forceSaveToSupportedVersion for opting in to saving maps
which may lose unknown json and layers which cannot be saved.
CodedValueDomain.getCodedValues now returns CodedValue rather than Map<Object, String>.
Envelope.getDepth removed.
EnvelopeBuilder.getDepth removed.
ExportTileCacheTask is now loadable, constructor only takes a URL and some methods now async.
FeatureLayer get/setSelectionWidth now uses double not in.
GeodatabaseSyncTask is now loadable, constructor only takes a URL and some methods are async.
GeodatabaseSyncTask.createDefaultGenerateGeodatabaseParametersAsync now takes an extent.
Geometry.isSimple removed, use GeometryEngine.isSimple instead.

GeoView.is/setLogoVisible renamed to is/setAttributionTextVisible.

ImageTiledLayer.isResampling removed, no replacement, see known issues.
Item class properties now use a calendar rather than int. Also spatial reference now returns a string and getId is renamed to
getItemId.
Job.getJobId renamed getServerJobId.
Layer class removed addVisibilityChangedListener, getAttributionText renamed getAttribution, getId now returns a string.
LayerTimeInfo.getTimeExtent removed.
LocatorInfo.isSupportsPointAddress renamed isSupportsAddress.
various MapView setViewpoint methods have been renamed as overloads.
MapView getUnitsPerPixel renamed to getUnitsPerDensityIndependentPixel.
Job.Message.getType removed.
PictureMarkerSymbol.getBitmapDrawable removed, use getImage.
Popup class no longer takes a context. Various methods removed, use PopupManager.
PopupAttachment.setAttachment removed, use PopupAttachmentManager.
PopupDefinition getMedias renamed getMedia, is/setAllowUpdateGeometry renamed to is/setAllowEditGeometry.
PopupManager getEditingGeometryBuilder removed, isAllowUpdateGeometry renamed to isAllowEditGeometry,
isShowEditInfoSummary renamed to isShowEditSummary.
PortalFolder getCreated now returns a calendar, getId renamed getFolderId, getUserName renamed getUsername.
PortalGroup fetchGroupMembershipAsync renamed to fetchGroupUsersAsync, getCreated and getModified now return a
calendar, getId renamed getGroupId, getPhoneNumber renamed getPhone, getSortOrder and getSortField now return enums (not
strings).
PortalInfo getCreated and getModified now return a calendar, getDefaultExtent now returns an envelope.
PortlalItem getAvgRating renamed getAverageRating, get/setLicenseInfo renamed get/setAccessAndUseConstraintsHtml,
getNumComments renamed getCommentCount, getNumRatings renamed getRatingsCount, getNumViews renamed
getViewCount, getOwnerFolderId renamed getOwner, getSize now returns a long, unshareWithGroupsAsync renamed
unshareAsync.
PortalItemComment getCreated now returns a calendar, getId renamed getCommentId.
PortalItemContentParams renamed PortalItemContentParameters.
PortalItemGroups getAdminGroups renamed getAdmins, getMemberGroups renamed getMembers, getOtherGroups renamed
getOthers.
PortalUser getCreated and getModified now return a calendar, getDescription renamed getUserDescription, getUserName
renamed getUsername.
PortalUserContent getUserName renamed getUsername.
QueryFeatureOptions class renamed ServiceFeatureTable QueryFeatureFields.
TextSymbol size is now a float (not int)
TileInfo constructor has reordered parameters
Related topics
Release notes


This topic describes the changes in version 10.2.4 of the ArcGIS Runtime SDK for Android.
If you are using Eclipse or ADT as your development environment you can use the Upgrade ArcGIS projects tool, provided with the SDK,
to update your ArcGIS projects to the latest installed version.
Minimum Android API level support

At this release, we have updated the minimum supported Android platform version to Android platform version 4.0.1 (API level 14).
Direct local support for vector and raster formats

Local shapefiles, KML files, and geopackages are now supported for map display. Feature layers can now display data from a
ShapefileFeatureTable, itself created from the path to a shapefile (.shp) on the local machine. Feature data from a GeoPackage, an
Open Geospatial Consortium data format, can also be displayed in a feature layer, after first creating a GeopackageFeatureTable. The
KMLLayer class in com.esri.android.map.ogc.kml supports the ability to work with local and remote (via a URL) KML files.
You can also now display local raster data files. Refer to the com.esri.core.raster package, and the RasterLayer class in the
com.esri.android.map package for more information. Supported formats are:
ASRP/USRP
CIB1,5,10
DTED0, 1, 2
GeoPackage
GeoTIFF
HFA
HRE
IMG
JPEG
JPEG2000
NITF
PNG
RPF
SRTM1, 2
Note: Rasters stored in Geodatabases are not supported

Spatial analysis functions (BETA)
New local spatial analysis functions are available in beta in this release, using fast GPU-based processing. Available functions are:
Line of sight
Viewshed
Refer to the new com.esri.core.analysis package for more information.
Note: Spatial analysis is not currently usable on x86 devices.

Geodatabase feature service table
At this release we have continued to improved the API support for applications that can work both online and offline using a single API,
using the GeodatabaseFeatureServiceTable.
The GeodatabaseFeatureServiceTable class now supports:
Editor tracking functionality
Creating a GeodatabaseFeatureServiceTable from a nonspatial table (as opposed to a spatial layer) from a service
Performing related table queries
The GeodatabaseFeatureServiceTable currently does not support time-aware data.

For more information, see the Layer types topic.
WMTS support
WMTS services are now supported, by using the new WMTSLayer class.
Web map enhancements

Support for web maps with image service layers, and WMTS services.
Offline API quality improvements

A number of quality improvements have been made to APIs involving offline data.
Map behavior and performance improvements

A new zoom gesture on the MapView is available, double-tap-and-drag. By default, this gesture is used for single-pointer zooming. A
double-tap gesture followed by an upwards vertical drag gesture zooms the map in; double-tap followed by downwards vertical drag
gesture zooms out. Note that the pointer must not be released after the second tap of the double-tap; the pointer should remain on the
surface from the second tap, while performing the zoom in and/or out. This gesture can be overriddensee the API additions section
below for information about the API additions for this gesture. The speed of the zoom effect is determined by the distance the pointer has
moved from the original tap event. Only vertical movement is considered; horizontal movement is ignored.
A number of performance improvements have been made to various areas of the API, including increasing the speed of map animations
to be consistent with other APIs and improving the performance of some specific cases of panning the map interactively.
See also the new setBufferEnabled method described in the API Additions section.
Callout enhancements
By default the size of the callout window will stretch to accommodate the content that is to appear inside it, potentially becoming
almost as large as the entire MapView. The maximum width and height are now customizable using either absolute pixels or
density-independent pixels.
The maximum width/height of the callout window is now passed down to the content views inside the callout, to help these views
size themselves correctly, improving the display of more complex callout content.
Improved behavior of animated show/hide and floating anchor.
API breaking changes

AttachmentManager.retrieveAttachmentInfos behavioral change: The attachmentListener now calls back on worker thread while
previously called back on UI thread.
API additions
Added MapOnTouchListener.onLongPressUp event. This simplifies the magnifier workflow so that users only need to override this
event in order to get notified when the magnifier is released.
Added onDoubleTapDrag and onDoubleTapDragUp events to the MapOnTouchListener; .
Added UserCredentials.clearCachedCredentials(String url) method. This is useful because the Apache HttpClient will cache
credentials for HTTP based security types (basic, digest, ntlm, iwa), there were some issues where someone would sign out and
then go to sign in as someone else, but they were already authenticated with the cached credentials. This method provides a way
to clear any cached credentials for a given URL.
Added a new MapView constructor to support offline basemaps. This is to allow basemap switching for a Webmap (online or
offline) and use a TPK as the basemap.
Added new MapView.switchBasemap method.
Added async methods createPopupInfo, fetchPopupInfo, and fetchLayerServiceInfo to ArcGISTiledMapServiceLayer and
ArcGISDynamicMapServiceLayer. Also added simple getter for getLayerServiceInfo to the ArcGISDynamicMapServiceLayer.
Added get/setDefinitionExpression methods on a FeatureLayer to filter out features to be displayed.
Callout class: added new methods to get/set the maximum width/height of callouts and callout offsets using density-independent
pixels. Also added setPassTouchEventsToMapView and isPassTouchEventsToMapView methods to control how events are
propogated to child views. The CalloutStyle class also gains new methods to get/set maximum width/height and corner curve size
using density-independent pixels.

Added methods getTimeExtent, getTimeInfo, getTimeInterval and isTimeAware to ArcGISImageServiceLayer to support time-
aware scenarios.
New setBufferEnabled method onTiledLayer allows the ability to turn off buffering extra band of tiles being fetched outside the
MapView (in case of multiple tiled services). This results in faster rendering.
Added the new package com.esri.android.map.ogc.kml containing the KMLLayer class, for working with both remote and local
KML files.
API deprecations
The MapGestureDetector class and OnGestureListener interface have been deprecated since they are intended for internal use
only; use the MapOnTouchListener or other listeners in the com.esri.android.map.event package instead.
Deprecated the synchronous createPopupInfo and getPopupInfo in ArcGISTiledMapServiceLayer and
ArcGISDynamicMapServiceLayer; use the alternative methods with callback parameters instead.
Deprecated the fetchLayerInfo method on the ArcGISPopupInfo class; refer to the new alternative methods on the
ArcGISTiledMapServiceLayer and ArcGISDynamicMapServiceLayer classes instead.
Deprecated CalloutPopupWindow in favor of Callout (which has been enhanced as described in the section above).
Deprecated the get and set methods for title text attributes in CalloutStyle (for example, get/setTitleTextColor), as callout titles
were removed in a previous release.
Deprecated the KMLLayer class in the com.esri.android.map.ogc package; this is superseded by the new KMLLayer class in the
com.esri.android.map.ogc.kml package.
New and updated in the SDK

The SDK includes a number of new samples (GeoJSONEarthquakeMap, ClassBreaksRenderer, UniqueValueRenderer, and
DynamicLayerRenderer).
All samples have been updated to use minimum SDK version number 15, and many of the samples have also been updated to use a new
fragment-based architecture, more modern user interface elements, and to demonstrate current best practices and address bugs.
Updated guide documentation on APIs for working with portals (ArcGIS Online and ArcGIS for Portal) has been added. See Access the
ArcGIS Platform, Access content, and Search for content.
There are also new guide documentation topics giving guidance on understanding and using spatial references.
Issues fixed
NIM102062: Local tiled layers are not completely rendered in full extent on a Panasonic ToughPad FZ-A1 device.
NIM104756: Basemap does not always load after performing geocoding or routing.
NIM102514: The OnDragPointerUp event listener does not get fired consistently.
NIM104263: When editing a hosted feature service in a web map an "Update failed" error occurs when using cellular service and
leaving the Collector for ArcGIS application idling in between edits.
NIM102260: Collector for ArcGIS (Android) incorrectly rounds off the values in double field.
Known limitations
When using a FeatureServiceTable, you can edit related records, but relationships between records cannot be edited, created, or
deleted.
It is not possible to use Ownership Based Access Control (OBAC) functionality with a disconnected geodatabase created from an
ArcGIS Server version earlier than 10.3. Workaround: Use ArcGIS for Server 10.3.
Geopackage vector feature tables that have a geometry type defined as Geometry or Geometry Collection cannot be read,
displayed, or edited.
Each individual raster file used in a raster layer is limited in size to 4GB; this is a current limitation of the Android platform.
Callouts that contain WebViews as content, and that are displayed using Callout.animatedShow() or Callout.animatedHide(), may
display content poorlycontent may appear fuzzy, and callout may flash at end of hide animation. Workaround is to use non-
animated alternatives, Callout.hide() and Callout.show(), if affected.
FeatureServiceTable does not support time-awareness.

Advanced Symbology doesn't support MIL-2525C and APP 6B dictionaries installed on same device. Workaround this issue by
setting the path of one of the resources explicitly, using the MessageProcessor constructor that allows you to set the symbol
dictionary path.
New feature services created from ArcMap from feature classes that have names containing SQL keywords like "desc" and "asc"
may cause initialization to fail if used in a GeodatabaseFeatureServiceTable. Workaround is to change feature class names to
non-reserved words.
CalloutPopupWindow may display incorrectly if style with corner curve value of 0 is used.
When not using a full screen view for the OAuthView, enterprise logins may not work properly if the organization has several
redirect pages.
Drawable.createFromStream() throws NetworkOnMainThreadException while constructing PictureMarkerSymbol from a URL.
OutOfMemoryError exception thrown while trying to upload a large attachment(~60 MB) to server during sync.
Geodatabases need to be synced and edited from the same thread, otherwise edits will not be visible.
Services with a casing mismatch between the field names used in the 'editFieldsInfo' and 'fields' JSON attributes (defined in the
service REST endpoint) may not honor editor tracking.
Rendering fails for layers with class breaks renderer when the class breaks field is SHAPE.AREA or SHAPE.LEN.
Failure to load webmaps with basemaps that have popups defined.
WebMap which contains ArcGIS Server .NET 10.1 secured services never loads, and WebMapLayer which should be skipped is
not skipped.
When a Popup has multiple media and one image has invalid URL and a valid URL is linked to this image , tapping on this image
in full screen mode won't open the linked page.
If there are more than one reference layer in a basemap they don't all get shown.
Popup Pie chart can't be created if one of the values is negative.
Selection mode 'subtract' does not work correctly when using ArcGISFeatureLayer in snapshot mode.
The onWebMapLayerAdd event won't be triggered when a feature collection is added to a webmap.
Unique value renderer does not support field2.
Chinese characters won't work in text symbol.
Related topics
Release notes


This topic describes the changes in version 10.2.5 of the ArcGIS Runtime SDK for Android.
Android Studio support

Android Studio from Google is now the official supported Integrated Development Environment (IDE) for creating Android apps. At this
release, we support ArcGIS Runtime SDK for Android development with Android Studio.
An Android Archive (AAR) is available from the Bintray Maven central repository, or the ArcGIS Runtime SDK for Android download from
developers.arcgis.com; you can reference this AAR as a dependency in your Gradle build script.
Samples are now available for Android Studio, from the samples repository on GitHub.com, or from the SDK download.
Tutorials for creating apps with the new Android Studio are available in the Guide. If you are unfamiliar with Android Studio, you may want
to start with Add a map to your app.
Caution: Note that it is not currently possible to use the AAR with x86 devices or emulatorsan
UnsatisfiedLinkError will be thrown. You can workaround this issue by referencing local copies of
the .so and .jar libraries directly from your Android Studio project, instead of building against the
AAR which includes these dependencies for you. To find out more about adding a dependency to
the ArcGIS Runtime SDK for Android, refer to Install and set up.
Eclipse
The Eclipse plugin is deprecated. From version 10.2.5, Esri no longer provides tools for the Eclipse IDE in the form of a plugin, however,
it is possible to continue to develop existing apps using Eclipse by referencing the required .jar and .so files directly from your project.
A number of other smaller bug fixes and improvements have also been added.
API additions
Added GeometryEngine.normalizeCentralMeridian method. This allows geometries created in wrap-around maps to be normalized
within the spatial reference bounds.
New parameterless constructor, and new methods fetchDrawable, getUrl and setUrl on PictureMarkerSymbol for setting
PictureMarkerSymbols using URLs of bitmaps. These methods should be used when setting PictureMarkerSymbol bitmaps from a
URL instead of a local resource.
New classes LayerRelationship.Cardinality and LayerRelationship.Role, and new methods getCardinality, getRole, getKeyField
and isComposite on LayerRelationship class. These classes are used in layers with related records. For more information, see the
API reference.
API deprecations
PictureMarkerSymbol(String) constructor is deprecated in favor of a combination of the new parameterless constructor and setUrl
and fetchDrawable methods. See theAPI reference documentation for PictureMarkerSymbol for more information.
Issues fixed
BUG-000082775: MapOptions.Center does not work when device language setting is German.
OutOfMemoryError exception thrown while trying to upload a large attachment(~60 MB) to server during sync.
Known limitations
x86 native *.so files bundled in AAR do not work on android stock x86 emulator. They do work on device. If you need to test on
x86 emulator then you need to should not use the AAR bundle and instead add all the libs manually.
For Android 5.0 devices, if SwitchBaseMap is called twice in succession, the first call will be cancelled, but the
onSwitchBaseMapCompleted callback will not be called back for the cancelled call.
In some cases when zooming in on a map with a RasterLayer, the data from the previous zoom level may remain in the display.
A RasterLayer instantiated from FileRasterSource cannot be reprojected automatically. Workaround: Call the
FileRasterSource.project method before passing the FileRasterSource to the RasterLayer constructor.

If a geodatabase file has been replaced with different data, an existing Geodatabase instance may still have a reference to the
replicaIId of the previous deleted geodatabase file.
When wrap-around is enabled for a map, loading a web map that has an extent with coordinates outside the bounds of the spatial
reference can result in the wrap-around failing.
When uploading attachments to a secure service, 403 errors received from the service may be treated as unauthorized access
exceptions.
deleted.
dictionary path.
non-reserved words.
redirect pages.
Failure to load webmaps with basemaps that have popups defined.
not skipped.
NIM103321 Chinese and Korean characters may not display correctly in a text symbol if using a default font.
Related topics
Release notes


10.2.6-2
There is no new functionality as this minor release is a bug fix release
10.2.6-1
There is no new functionality as this minor release fixes one significant bug offered below:
1. x86 libs bundled in AAR file now work with emulators and x86 devices running lollipop, Android API 5.x.
10.2.6
API additions
Implemented java.io.Serializable interface on the SyncGeodatabaseParameters class, to allow geodatabase synchronization
parameters to be serialized to local storage when required, for example if an app is terminated or paused while synchronizing.
Added GeodatabaseStatusInfo.fromJson(JsonParser, String) overload. You can pass in a string representing the JobId to set on
the resulting GeodatabaseStatusInfo object.
Issues fixed
ENH-000085213 - When no location updates are available (for example, when using device GPS only, and no GPS signal is
available), GPS indicator in map will now use a grey symbol to indicate using last known location (previously may have remained
as a blue icon).
ENH-000084892 - LocationDisplayManager can no longer be successfully started if all location settings are disabled on the
device; in this case, warnings are logged in Android LogCat (previously, GPS indicator may have displayed a symbol at 0,0
lat,long if GPS sensor was off, and there was no indication that making use of the LocationDisplayManager correctly was not
possible).
BUG-000084156 - If network connections are interrupted prior to executing synchronizeReplica when synchronizing disconnected
edits, a synchronizeReplica call that was interrupted during the synchronize process can now successfully be re-attempted using
the same sync parameters (previously the edits could no longer be synchronized and subsequent attempts were unsuccessful).
BUG-000086242 - A new token is generated to access hosted services through an HTTP secured portal when using credentials
that have been serialized and deserialized (previously a new token may not have been correctly generated in this case).
The ArcGIS Runtime SDK for Android library module hosted in the Bintray maven repository contains fixes for the following issues
(these issues were not in the local download of the SDK at version 10.2.5).
BUG-000087617 - Synchronizing edits to feature service that is hosted in ArcGIS Server 10.2.2 fails with an error in
uploading item part XXX when using ArcGIS runtime SDK for Android 10.2.5 available through an Esri maven repository
hosted with Bintray.
BUG-000084930 - The issue of creating an ArcGISDynamicMapServiceLayer with a map service URL on Android API
level 21 crashing the application has been fixed.
BUG-000086307 - The problem displaying a service with a spatial reference of 102441 or 102443 in a ArcGIS Runtime
SDK for Android application targeting Android 5.0 Lollipop operating system has been fixed.
BUG-000087382 - The issue that MapOptions.Center does not work when the device language setting is Finnish has been
fixed.
Culture is now correctly set for Portal queries using the getBasemapGalleryGroupQuery, resulting in correctly localized responses.
LocationDisplayManager performance has been enhanced to store symbols as Json allowing for a smaller memory footprint
(previously, symbols were stored as drawables).
The GeodatabaseStatusInfo.getJobId method now correctly returns the synchronization job ID.
When editing a layer with feature templates in a popup, changing a field that changes the feature template will display a dialog
prompting the user to either cancel the change, reapply the default template values for all fields, or to keep the current edits
(previously the default values would overwrite any other edits previously made to the feature attributes).
A drawing issue specific to using the Android emulator on systems with Intel graphics cards has been addressed; this no longer
causes a crash.

Known limitations
x86 native *.so files bundled in AAR do not work on android stock x86 emulator. They do work on device. If you need to test on
x86 emulator then you should avoid using the AAR bundle, and instead add all the libs manually.
Note: This is fixed with v10.2.6-1, we encourage everyone to be using v10.2.6 Update 1.
For Android 5.0 devices, if SwitchBaseMap is called twice in succession, the first call will be cancelled, but the
onSwitchBaseMapCompleted callback will not be called back for the cancelled call.
In some cases when zooming in on a map with a RasterLayer, the data from the previous zoom level may remain in the display.
A RasterLayer instantiated from FileRasterSource cannot be reprojected automatically. Workaround: Call the
FileRasterSource.project method before passing the FileRasterSource to the RasterLayer constructor.
If a geodatabase file has been replaced with different data, an existing Geodatabase instance may still have a reference to the
replicaIId of the previous deleted geodatabase file.
When wrap-around is enabled for a map, loading a web map that has an extent with coordinates outside the bounds of the spatial
reference can result in the wrap-around failing.
When uploading attachments to a secure service, 403 errors received from the service may be treated as unauthorized access
exceptions.
deleted.
dictionary path.
non-reserved words.
redirect pages.
Failure to load webmaps with basemaps that have pop-ups defined.
not skipped.

NIM103321 Chinese and Korean characters may not display correctly in a text symbol if using a default font.
Related topics
Release notes


This topic describes the changes in version 10.2.7 of ArcGIS Runtime SDK for Android.
Issues addressed
BUG-000084945: Adding an offline geodatabase content to a map does not display the label of a feature class if the label is in the
Chinese language.
BUG-000089134: The Location Display Manager stops updating the phone's current location on the map if the accuracy of the
incoming coordinate is much less accurate than the previous coordinate.
BUG-000089200: The LocationDisplayManager class shows an obviously bigger GPS indicator on Motorola Droid Turbo.
ENH-000090442: The geocode.arcgis.com service has new properties that enable developers to tailor suggest results to specific
areas making suggest results more meaningful. Country code and location, geometry, and distance are now honored as suggest
parameters.
BUG-000088984/BUG-000088511: This fix for the PortalInfo print service parsing allows a web map to open from an organization
when the print service is not set as esri default on the org.
Known issues
Some services have a casing mismatch between the field names used in the EditFieldsInfo returned from
ArcGISFeatureLayer.getEditFieldsInfo() and the Fields JSON attribute, which is defined in the service's REST
endpoint. A workaround for this mismatch is to correct the casing in your app code.
Advanced symbology doesn't support military dictionaries installed on the same device. Work around this issue by setting the path
of one of the resources explicitly, using the MessageProcessor constructor that allows you to set the symbol dictionary path.
Late-breaking information
Information about excluding duplicate files from the Android Package (APK) file was omitted from the "Install and setup section." It's been
added as step 4 of that section in this guide.
Related topics
Release notes

Release notes for 10.2.8-1

This topic describes the changes in versions 10.2.8-1 and 10.2.8 of ArcGIS Runtime SDK for Android.
10.2.8-1
This release updates an API libpng dependency to address security vulnerabilities. This update allows ArcGIS Android apps that are
published to the Google Play store to be updated and any new published apps to comply with Google Play's Malicious Behavior policy.
You can read more about this vulnerability in CVE-2015-8540.
10.2.8
Issues addressed
Updated the SDK OpenSSL to version 1.0.2g to address security vulnerabilities. See this Google FAQ for more information.
Known issues
Some services have a casing mismatch between the field names used in the EditFieldsInfo returned from
ArcGISFeatureLayer.getEditFieldsInfo() and the Fields JSON attribute, which is defined in the service's REST
endpoint. A workaround for this mismatch is to correct the casing in your app code.
Advanced symbology doesn't support military dictionaries installed on the same device. Work around this issue by setting the
path of one of the resources explicitly using the MessageProcessor constructor that allows you to set the symbol dictionary
path.
Related topics
Release notes

System requirements for 100.1.0

Supported operating systems
The operating systems that the ArcGIS Runtime SDK for Android supports are the same as those listed for the Android SDK developed by
Google. Generally, development is supported on Mac OS X (Intel), Linux, and Windows-based operating systems. Refer to Google
documentation for the specific operating system versions that are supported.
Software and platform requirements

The apps you build will run on Android phones and tablets with the Android platform version 4.1.x "Jelly Bean" (API level 16) and above.
Android SDK support

The following is required for development with this SDK:
An appropriate Java Development Kit (JDK) must be installed. JDK 6 or higher is required; JDK 7 is required when targeting
Android 5.0 and higher. A Java Runtime Environment (JRE) is not enough for development. JDKs can be downloaded from the
Oracle website. More information is available on the Android Developers website in the topic Installing Android Studio.
Android SDK Tools. The downloadable component of the Android SDK which is included with Android Studio.
Integrated development environment (IDE)

Android Studio
Esri supports and recommends the use of Android Studio for development of apps that use ArcGIS Runtime SDK for Android, as this is
the IDE officially supported by Google for Android development.
Refer to the Install and set up topic for more information.
IntelliJ IDEA
IntelliJ IDEA is the IDE upon which Android Studio is based. However, IntelliJ IDEA comes bundled with an Android plugin and supports
Android Gradle based build system so you can work directly with the ArcGIS Runtime SDK for Android in IntelliJ IDEA. More information
about support for Android development in IntelliJ IDEA can be found here.
OpenGL ES 2.0
ArcGIS Runtime SDK for Android uses OpenGL ES 2.0 technology to render map images. This technology makes the product much more
versatile and usable by reducing the memory footprint, dramatically improving rendering speeds and using less power.
You need to configure graphics acceleration when using an Android emulator. Information on how to enable it can be found here.
Requirements for ArcGIS software and connected services

To connect your app to ArcGIS Server data or services, use ArcGIS 10.1 for Server or later. To use ArcGIS Server data when your app is
offline, use ArcGIS 10.2.2 for Server or later.
You can use Portal for ArcGIS version 10.2 or later with your app.
ArcGIS 10.3 for Desktop and higher is required if you're using the Create Runtime Content capability.
ArcGIS Pro 1.3 or higher is required if you're using mobile map packages and tile packages.
Web maps built with the 2.0 or higher version of the web map specification are required (from Portal for ArcGIS 10.3 and above). Note:
When you save a web map in an ArcGIS Runtime app, you are saving a web map that adheres to version 2.8 of the web map
specification. These should only be saved back to portals that support the 2.0 web map specification (Portal for ArcGIS 10.3 and above).

Essential vocabulary
Term Definition
advanced The set of conventions, rules, or encoding systems that define how to represent on a map geographic features or other items of
symbology interest (such as airplane routes) that are more complex than a simple point, line, or polygon. The advanced symbology category
includes:
Geodesics
Features symbolized with symbol dictionaries, such as features that adhere to military specifications (for example,
warfighting symbols defined in MIL-STD-2525C)
analysis A systematic examination of a problem that provides new information. ArcGIS Runtime supports many types of analyses, from
simple geometry-based analysis to advanced spatial analysis. You can also string analysis operations together to build models.
Stringing operations together for modeling or for the automation of repetitive workflows (for example, batch processing) is known
as geoprocessing.
API Application programming interface. A specification that allows developers to create applications.
ArcGIS The ArcGIS Developer Program (ADP) is a developer-focused online community that provides users with the best possible
Developer experience for discovering the development and business opportunities that ArcGIS provides. ArcGIS Developer Subscription
Program plans let developers leverage various ArcGIS capabilities by choosing a subscription plan that best aligns with their development
skills and business goals.
ArcGIS The ArcGIS Marketplace is an online marketplace for customers to discover valuable new capabilities and applications, and
Marketplace connect directly with developers to obtain new solutions.
ArcGIS Server technology (that can be hosted by you or Esri), data, apps, APIs, and other elements designed to work together to provide
platform anything from small-scale, focused GIS solutions (such as an app that lets you collect data in the field and sync it to your
database) to complex, enterprise-level solutions that model real-world scenarios and use analytical capabilities to solve complex
problems.
asynchronous Within the context of discussing how ArcGIS APIs work, 'asynchronous' is a concept by which code is executed on an available
background thread in the application's thread pool. The results of this executed code (if any) are returned upon completion. This
allows you to off-load execution of longer-running processes, freeing up the UI thread so the app remains responsive to user
interaction.
attachment A file, such as a photograph (for example, a .png file) or a document, that's associated with a feature in the geodatabase.
Authentication A pre-built component you can add to your app that displays a dialog box asking for user credentials whenever an attempt is made
Manager on a secure resource (such as a secure layer) where the credentials are missing or invalid.
base layer An element of a basemap. A basemap can contain a number of base layers that can give your map a recognizable background so
that your operational layers are displayed in context. Base layers are always at the bottom of a map.
basemap A map depicting background reference information such as landforms, roads, landmarks, and political boundaries, onto which
other thematic information is placed. For a description of basemaps and other layer types, see Layers.
cache See tile cache.
callout A container view that can be added over the map and anchored to a coordinate with a leader. The callout leader or tail indicates
the location to which it's referring and has a configurable area that can contain other GUI and View components. These can be
anything you add to the callout, including a title, an image, text, and a pop-up. A map can have one callout. Also see pop-up.
canvas a kind of ArcGIS Online basemap specifically designed to give users a neutral 'canvas' on which to better display data.
canvas layer A basemap layer that provides a neutral background with minimal colors, labels, and features. Only key information is represented
in a canvas layer to provide geographic context, allowing your thematic data to come to the foreground.
CIM symbol Cartographic Information Model symbols, which are advanced, multilayer symbols produced by ArcGIS Pro and ArcGIS Desktop.
Client ID In ArcGIS Runtime SDKs, an identifier you associate with the app you build (one Client ID per app). You get a Client ID by signing
in to developers.arcgis.com.
cloud A network of remote servers hosted on the Internet to store, manage, and process data.
composite A relationship between two tables in which each feature in the destination table is expected to be related to an origin feature. In
relationship other words, any orphan destination features are considered a violation of the relationship. For example, a building and its mailbox
must be related. While the building (origin) can exist on its own, a mailbox (destination) must be related to a building. When an
origin feature is deleted, the destination feature should also be deleted. This is known as a cascade delete. Also see simple
relationship.
composite A symbol that is a combination of two or more symbols. Each symbol can represent the same or a different aspect of a graphic or
symbol feature.
configurable A software program that you can modify, typically focused on a specific task, such as finding directions, that's hosted on ArcGIS
app Online. Typically, the source code for the app is available on GitHub for you to customize. See the configurable apps gallery on
ArcGIS Online.
connected In ArcGIS Runtime SDKs, the state of having a network connection to ArcGIS Online or ArcGIS Enterprise.
coordinate A value that denotes the location of a vertex. Coordinates can represent 2D (x,y) or 3D (x,y,z) space. The meaning of the x,y,z
coordinates is determined by a coordinate system. The vertices and coordinate system together allow your app to translate a real-
world object from its location on the earth to its location on your map. For details, see Geometries.
coordinate A reference framework consisting of a set of points, lines, and/or surfaces, and a set of rules, used to define the positions of points
system in space in two or three dimensions. For details, see Geometries. Also known as map projections. Also see projection.
cross-platform The capability supported by some ArcGIS Runtime SDKs that lets you program with an SDK on multiple platforms. For example,
development ArcGIS Runtime SDK for Java allows you to develop on Windows, Linux, and Mac.
cross-platform The capability supported by several ArcGIS Runtime SDKs that lets you write once and deploy to multiple platforms and/or
deployment devices. For example, ArcGIS Runtime SDK for Qt allows you to write once and deploy to Android, iOS, Windows, and Linux.
destination A feature in a destination table that is associated with an origin feature in an origin table. You create associations like this for a
feature variety of reasons, such as to view information in one table for features in another. For more information, see Relate features in
this ArcGIS Runtime guide or Essentials of relating tables.

destination A table that has been associated with another table, an origin table, using a key. You associate two tables for a variety of reasons,
table such as to view information in one table for features in another. For more information, see Relate features in this ArcGIS Runtime
guide or Essentials of relating tables.
device In ArcGIS Runtime, nearly any kind of computer, including desktops, laptops, mobile phones, and tablets.
dictionary A renderer that uses a style file generated in ArcGIS Pro together with a rule engine to display some types of advanced symbology
renderer on a map, such as military symbology.
direct connect A type of connection from ArcGIS directly to a geodatabase instead of accessing the geodatabase through a service.
disconnected The state of not having a network connection to ArcGIS Online or ArcGIS Enterprise.
For details on ArcGIS Runtime's offline capabilities, see Create an offline map.
distance A type of Symbol that changes based on the distance, in meters, between the SceneView's Camera and the graphic or feature that
composite the Symbol is assigned to.
scene symbol
dynamic Labels that are placed on the fly, and whose text is generated dynamically based on a labeling expression stored with the data
labels being labeled.
dynamic layer A layer, from a map published through a map service, whose appearancesuch as labeling, layer order, and symbologycan be
changed by the client.
dynamic map A map that is drawn by the server each time the user zooms or pans. This differs from a tiled service in that it does not work with a
service cache of pre-cooked tiles.
dynamic One of 2 modes for rendering a graphics overlay. In this mode, which is good in most use cases, the entire graphic representation
rendering is stored on the GPU. This mode is especially good for moving objects, as individual graphic changes can be efficiently applied
mode directly to GPU state, resulting in a seamless experience. However, the volume of graphics has a direct impact on (GPU)
resources, and the number and complexity of graphics that can be rendered in this mode is dependent on the power of the GPU
and the amount of GPU memory. The other rendering mode is called static. For a comparison, see the definition for static
rendering mode.
feature A representation of a real-world object on a map, such as a building, river, or county. A feature is persisted in a feature table in a
data store (such as a database or service) or in a map. Features in the same data store or feature layer have a common attribute
schema. Also see graphic.
feature A data structure containing one or more features having the same set of attributes.
collection
feature data A general term for the data related to one or more features.
feature layer A layer that references a set of feature data. Feature data represents geographic entities as points, lines, and polygons.
feature A service that streams features. The server bundles feature data and streams it to the requesting client. There are a number of
service modes that client APIs can use to fetch data from the server and cache features locally if and when necessary.
feature A data structure representing feature data retrieved from a feature service.
service table
feature table A database table of a single geometry type, such as point, line, or polygon, that stores features that conform to the schema of the
table.
geocode The process of transforming a description of a locationsuch as a pair of coordinates, an address, or a name of a placeto a
location on the earth's surface. The resulting locations are output as geographic features with attributes, which can be used for
mapping or spatial analysis. Also known as address matching.
geodatabase A collection of geographic datasets of various types held in a common file system folder, a Microsoft Access database, or a
multiuser relational DBMS (such as Oracle, Microsoft SQL Server, PostgreSQL, Informix, or IBM DB2). Geodatabases come in
many sizes, have varying numbers of users, and can scale from small, single-user databases built on files up to larger workgroup,
department, and enterprise geodatabases accessed by many users.
geodatabase A representation of a real-world object persisted in a geodatabase. When displayed, it's displayed in a feature layer. A feature is
feature associated with a feature table, with which it shares a common schema. Common types of feature tables and schemas are point,
line, and polygon.
GeoElement A marker interface for features and graphics that's used when you want to identify (display attribute information on) visible items on
a map view.
geometry The combination of location and shape for a real-world object or a geometric construct such as an area of interest or a buffer area
around an object. Geometry is a fundamental element for performing spatial analysis. For more information, see Geometries.
GeoPackage A single SQLite file (.gpkg) that conforms to the OGC GeoPackage specification (http://www.opengeospatial.org/standards/
geopackage), which defines GeoPackages for direct use of vector geospatial features and/or tile matrix sets.
geoprocessing A GIS operation used to manipulate data. A typical geoprocessing operation takes an input dataset, performs an operation on that
dataset, and returns the result of the operation as an output dataset. Common geoprocessing operations include geographic
feature overlay, feature selection and analysis, topology processing, raster processing, and data conversion. Geoprocessing
allows for definition, management, and analysis of information used to form decisions.
You can use geoprocessing tools to create a sequence of operations, feeding the output of one tool into another tool; automate
your work (for example overnight processing); or solve complex problems using models.
Your ArcGIS Runtime app can consume online geoprocessing services.
graphic A representation of a real-world object stored in memory. When you want to display graphics, you use a graphics overlay. Graphics
exist while the app is running and, therefore, are used often for temporary features. Graphics can have geometry and attributes.
Graphics are not associated with a feature table. For more information, see Features and graphics.
graphics An item you use in your map, typically when you have graphics that change location regularly, and you want optimal animation of
overlay the graphics when zooming in and out on the map. It differs from a layer because its graphics are temporary (held in device
memory) instead of being persisted in the map. For more information, see Features and graphics.
hillshade A representation of a raster image that portrays a hypothetical illumination of a surface by determining illumination values for each
cell in a raster. It can greatly enhance the visualization of a surface for analysis or graphical display, especially when using
transparency.
By default, shadow and light are shades of gray associated with integers from 0 to 255 (increasing from black to white).

identify To display, on a map, attribute data of a feature or graphic.

job A unit of work performed by a computing system in response to a scheduled or unscheduled request.
label Text displayed with and associated with a graphic or feature.
layer In ArcGIS, an item used to display geographic data in a map. In general, a layer's data comes from a single source, such as a map
service URL or geodatabase table. A layer uses an associated renderer to symbolize data and in some cases define properties for
the display of things like labels and pop-ups. This decoupling of the layer's data and how it's rendered gives you the flexibility to
present the same data in a variety of ways. As the name indicates, layers are stacked or "layered" in the map and drawn from
bottom to top. As a developer, you can control the order of the layer in the map as well as it's visibility. For more information on
layers and how they're used in ArcGIS Runtime, see Layers and tables.
layer definition A SQL WHERE clause that selects a subset of features from a layer.
legend A table or chart associated with a map to indicate the meaning of the map's varied symbols and layer representations.
level of detail Scale levels to include in a tiling scheme.
(LOD)
license key A string of characters you add to your application code to unlock certain capabilities on the deployment device.
loadable A characteristic of a resource, such as a layer, map, or portal item, that allows you to do such tasks as the following:
Monitor the load status of the resource
Retry to load if previous load attempts failed
A loadable resource handles concurrent and repeated requests to load in order to accommodate the common practice of sharing
the same resource instance among various parts of an app. For details, see Loadable pattern for asynchronous resources.
Local Server In ArcGIS Runtime SDKs for Java, .NET (Desktop), and Qt, a miniserver for serving local services that dont require an Internet
connection. The miniserver allows you to perform analysis and geoprocessing that's not natively supported in the Runtime core.
locator A dataset that contains information including address attributes, indexes, and queries for geocoding. An address locator contains a
snapshot of the reference data that is used for geocoding. In the process of geocoding, the reference data is no longer needed
after the locator is created. A locator can be used to find addresses or x.y locations.
map A graphical representation of spatial relationships of entities within an area. In ArcGIS Runtime, a map works together with a map
view to provide a visualization of geographic data on a screen. A map specifies how the geographic data is organized; a map view
renders the data and allows users to interact with it.
map cache See tile cache.
map image A layer whose map images are created on the fly as a user zooms and pans around a map. It differs from a tiled layer, whose map
layer images are pre-generated and are displayed as tiles in a layer in the client app. Use a map image layer for content authored in
ArcGIS Pro or ArcMap and published as an ArcGIS map service to ArcGIS Online, ArcGIS Enterprise, and Local Server.
map view A class (MapView) that represents the view tier in an MVC architecture. While a map specifies how the geographic data is
organized, a map view renders the data and allows users to interact with it.
mobile A geodatabase (.geodatabase) that uses SQLite and can be used in disconnected workflows in ArcGIS Runtime apps.
geodatabase
mobile A compressed data format that can be created from ArcGIS Pro when you share a map as a mobile map package.
basemap
layer
mobile map A set of items bundled together as a single file (an .mmpk file) for transport, often for use in offline workflows. It can be created in
package ArcGIS Pro and consumed in ArcGIS Runtime apps. The items are one or more maps, their associated layers and data, and
optionally networks and locators. It also includes metadata about the package. Maps within a mobile map package follow a
specification similar to the web map specification and can contain online and/or local layers.
non-spatial In ArcGIS Runtime, a table with no geometry information; its features cannot be drawn on a map. In some areas of the ArcGIS
table Platform, a non-spatial tables is known as a "table." You may also know this as a "non-feature table."
offline In ArcGIS Runtime, the state of having no network connection to ArcGIS Online or ArcGIS Enterprise.
on-the-fly re- Refers to taking unprojected datasets (i.e., data that are stored in latitude and longitude) and transforming their visual
projection representation to make them appear to match other datasets that are projected. For example, as data is being added to a map
with a different spatial reference, a temporary data transformation to the map's spatial reference takes place.
operational A map layer that users can interact with. Typically, an operational layer is vector-based and is editable by users. However, it can
layer also be tiled data that can be queried against. See Layers for more information.
origin feature A feature in an origin table that is associated with a destination feature in a destination table. You create associations like this for a
variety of reasons, such as to view information in one table for features in another. For more information, see Relate features in
this ArcGIS Runtime guide or Essentials of relating tables.
origin table A table that has been associated with another table, a destination table, using a key. You associate two tables for a variety of
reasons, such as to view information in one table for features in another. Origin table is also known as a source table. For more
information, see Relate features in this ArcGIS Runtime guide or Essentials of relating tables.
package A set of items, such as a map and its referenced data, that ArcGIS Desktop bundles into a single file on your local machine so that
the items can be easily transferred from user to user or provisioned onto a device. Especially useful for disconnected apps.
pop-up A visual element on the map used to view and edit attributes and attachments associated with features or graphics in a layer on a
map. While similar to attribute information that displays in an identify task, pop-ups differ because they allow you to use aliases for
the field names and to have greater control over the display. A pop-up can be presented modally, in full screen, or within any other
view.
A pop-up can display inside a callout using a callout's custom view.
portal A term used to generically refer to ArcGIS Online, Portal for ArcGIS (a component of ArcGIS Enterprise), or both. These are
websites that provide a framework to manage, share, and secure geographic assets, such as data, maps, apps, and services.
portal item A web map, layer (feature, map, and image service layers), app (web and mobile apps whose content is provided by web maps),
tool, or data file that you add to a portal.

pre-planned A synchronization preparedness process by which you generate the geodatabase once and load copies of it onto each user's
workflow device.
projection A projected coordinate system based on a map projection such as transverse Mercator, Albers equal area, or Robinson, all of
which (along with numerous other map projection models) provide various mechanisms to project maps of the earth's spherical
surface onto a two-dimensional Cartesian coordinate plane. Projected coordinate systems are sometimes referred to as map
projections. Also see coordinate system..
provision To provide data and other resources to an app by installing those resources with the app.
raster A matrix of cells (or pixels) organized into rows and columns (or a grid) where each cell contains a value representing information,
such as temperature. Rasters include digital aerial photographs, imagery from satellites, digital pictures, and scanned maps. For
general information on rasters, see What is raster data? in the ArcGIS Help.
raster layer A layer type that allows you to display raster data in your app. A raster layer can render raster data from any type of raster. You
can add it to a map as either a basemap or an operational layer. For details, see Add a raster using a raster layer in the "Add
raster data" topic.
reference A layer of information in a map that provides context to a location, such as labels for place names, transportation routes, or other
layer features of reference.
related feature A feature in one table that has been associated with a feature in a different table using a key. See Relate features for more
information.
related table A table that has a relationship to another table. The relationship, created using ArcGIS Desktop, is made possible by a key that is
common to both tables. A related table can be either a spatial table or a non-spatial table.
renderer An object that determines how features in a layer or graphics in an overlay should be drawn (rendered) on the display. The
renderer then draws them using symbols. See Symbols and renderers for more information.
rule engine A tool that assembles military symbols using data in the style file and rules from the military specification you specify.
Runtime In ArcGIS Runtime SDK for Java, Qt, and .NET (Desktop), a collection of files containing various parts of ArcGIS Runtime
components functionality, installed and used on your development machine and deployed with the apps that you create.
The full collection, which is installed to your development machine when you install an ArcGIS Runtime SDK, includes the required
Runtime core components and optional components such as those for Local Server and advanced symbology. When you prepare
an app for deployment, the Deployment Builder tool helps ensure you deploy only the parts of the collection that are required by
the app you build.
Runtime core Client files (.dll or .so) that must be deployed with all ArcGIS Runtime apps. For Java, Qt, and .NET versions, you can use
the Deployment Builder wizard to choose which Local Server capabilities you want to deploy so they can be bundled with the
Runtime core files for you.
scene view A class (SceneView) that represents the 3D view tier in an MVC architecture. While a scene specifies how the three
dimensional geographic data is organized in, a scene view renders the data three dimensionally and allows users to interact with
it.
scene A 3D representation of spatial relationships of entities within an area. In ArcGIS Runtime, a scene works together with a scene
view to provide 3D visualization of geographic data on a screen. A scene specifies how the geographic data is organized; a scene
view renders the data and allows users to interact with it.
SDK Software development kit. A collection of documentation, sample code, and sample apps to help a developer use an API to build
apps.
service A feature table created from a URL to an ArcGIS Feature service's layer or table. The service feature table has different request
feature table modes which affect how data is populated, queried and cached on the client.
shapefile A vector data storage format for storing the location, shape, and attributes of geographic features. A shapefile is stored in a set of
related files.
side-by-side A capability that lets you develop with different versions of the same SDK on the same machine.
development
side load The process of transferring data between two local devices, in particular between a computer and a mobile device such as a
(sideloading) mobile phone or tablet.
simple A relationship between two tables where features in the destination table are independent to features in the origin table. For
relationship example, a transformer and an electric pole may be related but they can also exist their own. Deleting an origin feature resets the
keyField of the relationship to NULL in the destination feature.
sketch editor Allows users to interactively sketch geometries on the view. It can sketch point, polygon, and polyline geometries from scratch,
modify existing geometries, insert and remove vertices, undo and redo changes, and so on.
spatial A coordinate-based local, regional, or global system used to precisely locate geographical entities. It defines the coordinate
reference system used to relate map coordinates to locations in the real world. Spatial references ensure that spatial data from different
layers or sources can be integrated for accurate viewing or analysis. To define a spatial reference, use either a well-known ID
(WKID), which is also known as a spatial reference ID or SRID, or a full text definition (referred to as well-known text, WKT). Also
see geographic and projected coordinate systems.
spatial table A table with geometry information; its features can be displayed on a map. You may know this as a non-feature table.
static One of 2 modes for rendering a graphics overlay. Use this mode for static graphics, complex geometries, and very large numbers
rendering of polygons. Volume of graphics has little impact on frame render time (scales well) and pushes a constant GPU payload.
mode However, rendering graphic updates is CPU/system memory intensive, which can have an impact on device battery life. The other
rendering mode is called dynamic. For a comparison, see the definition for dynamic rendering mode.
style file A .stylx file you can create in ArcGIS Pro that contains symbol primitives such as the symbol frame, the lines that make up inner
icons, and so on.
sub layer One of several layers that are part of a group layer. For example, a map service layer is a type of group layer that can contain one
or more sub image layers.
symbol A symbol defines all the non-geographic aspects of a graphic or feature's appearance, including color, size, border, and
transparency. You can use symbols to create a renderer for graphics overlays or feature layers. You can also apply a symbol
directly to individual graphics when you create them. For more information on using symbols in ArcGIS Runtime, see .Symbols and
renderers.

symbol A set of symbol primitives and a rule engine that together allow you to use military symbols in your app. The military symbols
dictionary adhere to military symbol specifications such as MIL-STD-2525C. The symbol primitives are inside a style file. To display military
symbols, you associate the layer/overlay's dictionary renderer to a symbol dictionary.
table In ArcGIS Runtime, a data source for ArcGIS data that may or may not contain geometry information. In some areas of the ArcGIS
Platform, "table" refers to a table with no geometry information. For more information on using tables in ArcGIS Runtime, see
Layers and tables.
task A class bound to online or offline data or services that provides methods to perform asynchronous operations using those data or
services. For details, see Tasks and jobs.
tile An image, often a graphics file (for example, a .jpg file), typically stored in a directory known as a cache. The image is part of a
set of tiles that, conceptually, are pieces of a bigger map. How the tiles fit into the bigger map, along with other information, is
defined in a tiling scheme. Two tile categories are as follows:
Tiles in dynamic layers are created on the fly and can be stored in a cache on the client machine or on the server machine.
Where the user pans and zooms affects which tiles are created in this scenario, so technically, the tiles may not form a
bigger, complete map when put together.
Tiles in tile cache layers are created before users view the map, often by a developer or GIS data administrator. These tiles
are known as pre-processed tiles.
Also see tile cache.
tile cache A directory that contains tiles of a map extent at specific levels. The directory can be local to a desktop app or to a client app in a
client/server configuration. Also see tile.
tiled layer A layer displayed by assembling tiles (rectangular sections) into a continuous layer. The tiles are either raster image tiles or vector
tiles; they're generated into a tile cache before they're available for use. (Compare this to a dynamic layer, which renders itself on
the fly.) Tiled layers are often used for basemaps. You may see the term "tiled layer" used to refer specifically to the raster tiled
layer type because vector tiled layers are newer than raster tile layers. Also see vector tiled layer.
tile package A tiled layer that's been bundled into a single .tpk file. The file contains a tile cache of the data and metadata about the layer,
packaged into a single, portable file. You can add a tile package to an ArcGIS Runtime app using the local tiled layer class, letting
you share tile layers with other people via regular file sharing methods (email, FTP, and so on) and through ArcGIS Online. Tile
packages are ideal in disconnected environments where access to local data is required, and are ideal for displaying basemaps.
transformation The task of moving your data between different geographic coordinate systems. You may, for example, have some data in WGS84
that was collected from a GPS reading. However, your map may be in a different spatial reference, such as British National Grid,
which is based on a different geographic coordinate system, OSGB 1936. To convert the data from WGS84 to British National
Grid, you need to apply a transformation as well as a projection. Many transformations are available, depending on the geographic
area your data comes from. In this SDK, transformations are performed using equation-based transformation methods or grid-
based transformation methods.
unique value A renderer that lets you use one or more values in a field to specify how features with that same value (or values) should be
renderer rendered.
vector tiled A layer that's similar to tiled layers (made with raster tiles) but requires less space and differs in the way cartography is delivered.
layer Instead of pixels, cartography is delivered with 2D points that define lines, polygons, and the locations of labels and marker
symbols. Cartography is rendered at runtime, so differences between levels of detail appear more continuous than with raster tiles.
The file format is binary and conforms to the Mapbox vector tile specification.
vector tile A vector tile layer that's been bundled into a single file (a .vtpk file). The file contains all the tile data files, the service definition,
package a style sheet, the fonts, and the symbol markers required to display the map. It can be downloaded from an ArcGIS Online vector
tile service.
vertex A point that stands alone or makes up part of a geometry. Vertices that make up a geometry can be connected, one to the next, in
a linear order.
viewshed The locations visible from one or more specified points or lines. Viewshed maps are useful for such applications as finding well-
exposed places for communication towers, or hidden places for parking lots. You can create viewsheds using the Standard license
level of ArcGIS Runtime SDKs.
web map An interactive display of geographic information. A web map can be described as a collection of geographic layers, behaviors and
tools. It can contain a basemap, a set of data layers (many of which include interactive pop-up windows with information about the
data), and an extent. For more detailed information, see What is a web map.


Well- Name Well-known text
known
ID
3819 GCS_HD1909 GEOGCS["GCS_HD1909",DATUM["D_Hungarian_Datum_1909",SPHEROID["Bessel_1841",6377397.155,299.1528
3821 GCS_TWD_1967 GEOGCS["GCS_TWD_1967",DATUM["D_TWD_1967",SPHEROID["GRS_1967_Truncated",6378160.0,298.25]],PRI
3824 GCS_TWD_1997 GEOGCS["GCS_TWD_1997",DATUM["D_TWD_1997",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
3889 GCS_IGRS GEOGCS["GCS_IGRS",DATUM["D_Iraqi_Geospatial_Reference_System",SPHEROID["GRS_1980",6378137.0,298
3906 GCS_MGI_1901 GEOGCS["GCS_MGI_1901",DATUM["D_MGI_1901",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIM
4001 GCS_Airy_1830 GEOGCS["GCS_Airy_1830",DATUM["D_Airy_1830",SPHEROID["Airy_1830",6377563.396,299.3249646]],PRIMEM[
4002 GCS_Airy_Modified GEOGCS["GCS_Airy_Modified",DATUM["D_Airy_Modified",SPHEROID["Airy_Modified",6377340.189,299.3249646]
4003 GCS_Australian GEOGCS["GCS_Australian",DATUM["D_Australian",SPHEROID["Australian",6378160.0,298.25]],PRIMEM["Greenwi
4004 GCS_Bessel_1841 GEOGCS["GCS_Bessel_1841",DATUM["D_Bessel_1841",SPHEROID["Bessel_1841",6377397.155,299.1528128]],P
4005 GCS_Bessel_Modified GEOGCS["GCS_Bessel_Modified",DATUM["D_Bessel_Modified",SPHEROID["Bessel_Modified",6377492.018,299.1
4006 GCS_Bessel_Namibia GEOGCS["GCS_Bessel_Namibia",DATUM["D_Bessel_Namibia",SPHEROID["Bessel_Namibia",6377483.865280418
4007 GCS_Clarke_1858 GEOGCS["GCS_Clarke_1858",DATUM["D_Clarke_1858",SPHEROID["Clarke_1858",6378293.645208759,294.2606
4008 GCS_Clarke_1866 GEOGCS["GCS_Clarke_1866",DATUM["D_Clarke_1866",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIM
4009 GCS_Clarke_1866_Michigan GEOGCS["GCS_Clarke_1866_Michigan",DATUM["D_Clarke_1866_Michigan",SPHEROID["Clarke_1866_Michigan"
4010 GCS_Clarke_1880_Benoit GEOGCS["GCS_Clarke_1880_Benoit",DATUM["D_Clarke_1880_Benoit",SPHEROID["Clarke_1880_Benoit",637830
4011 GCS_Clarke_1880_IGN GEOGCS["GCS_Clarke_1880_IGN",DATUM["D_Clarke_1880_IGN",SPHEROID["Clarke_1880_IGN",6378249.2,293
4012 GCS_Clarke_1880_RGS GEOGCS["GCS_Clarke_1880_RGS",DATUM["D_Clarke_1880_RGS",SPHEROID["Clarke_1880_RGS",6378249.14
4013 GCS_Clarke_1880_Arc GEOGCS["GCS_Clarke_1880_Arc",DATUM["D_Clarke_1880_Arc",SPHEROID["Clarke_1880_Arc",6378249.145,29
4014 GCS_Clarke_1880_SGA GEOGCS["GCS_Clarke_1880_SGA",DATUM["D_Clarke_1880_SGA",SPHEROID["Clarke_1880_SGA",6378249.2,2
4015 GCS_Everest_Adj_1937 GEOGCS["GCS_Everest_Adj_1937",DATUM["D_Everest_Adj_1937",SPHEROID["Everest_Adjustment_1937",63772
4016 GCS_Everest_def_1967 GEOGCS["GCS_Everest_def_1967",DATUM["D_Everest_Def_1967",SPHEROID["Everest_Definition_1967",637729
4018 GCS_Everest_Modified GEOGCS["GCS_Everest_Modified",DATUM["D_Everest_Modified",SPHEROID["Everest_1830_Modified",6377304.0
4019 GCS_GRS_1980 GEOGCS["GCS_GRS_1980",DATUM["D_GRS_1980",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
4020 GCS_Helmert_1906 GEOGCS["GCS_Helmert_1906",DATUM["D_Helmert_1906",SPHEROID["Helmert_1906",6378200.0,298.3]],PRIMEM
4021 GCS_Indonesian GEOGCS["GCS_Indonesian",DATUM["D_Indonesian",SPHEROID["Indonesian",6378160.0,298.247]],PRIMEM["Gre
4022 GCS_International_1924 GEOGCS["GCS_International_1924",DATUM["D_International_1924",SPHEROID["International_1924",6378388.0,2
4023 GCS_MOLDREF99 GEOGCS["GCS_MOLDREF99",DATUM["D_MOLDREF99",SPHEROID["GRS_1980",6378137.0,298.257222101]],P
4024 GCS_Krasovsky_1940 GEOGCS["GCS_Krasovsky_1940",DATUM["D_Krasovsky_1940",SPHEROID["Krasovsky_1940",6378245.0,298.3]],
4025 GCS_NWL_9D GEOGCS["GCS_NWL_9D",DATUM["D_NWL_9D",SPHEROID["NWL_9D",6378145.0,298.25]],PRIMEM["Greenwich
4027 GCS_Plessis_1817 GEOGCS["GCS_Plessis_1817",DATUM["D_Plessis_1817",SPHEROID["Plessis_1817",6376523.0,308.64]],PRIMEM
4028 GCS_Struve_1860 GEOGCS["GCS_Struve_1860",DATUM["D_Struve_1860",SPHEROID["Struve_1860",6378298.3,294.73]],PRIMEM["
4029 GCS_War_Office GEOGCS["GCS_War_Office",DATUM["D_War_Office",SPHEROID["War_Office",6378300.0,296.0]],PRIMEM["Green
4031 GCS_GEM_10C GEOGCS["GCS_GEM_10C",DATUM["D_GEM_10C",SPHEROID["GEM_10C",6378137.0,298.257223563]],PRIMEM
4032 GCS_OSU_86F GEOGCS["GCS_OSU_86F",DATUM["D_OSU_86F",SPHEROID["OSU_86F",6378136.2,298.257223563]],PRIMEM[
4033 GCS_OSU_91A GEOGCS["GCS_OSU_91A",DATUM["D_OSU_91A",SPHEROID["OSU_91A",6378136.3,298.257223563]],PRIMEM[
4034 GCS_Clarke_1880 GEOGCS["GCS_Clarke_1880",DATUM["D_Clarke_1880",SPHEROID["Clarke_1880",6378249.144808011,293.4663
4035 GCS_Sphere GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sphere",6371000.0,0.0]],PRIMEM["Greenwich",0.0],UNI
4036 GCS_GRS_1967 GEOGCS["GCS_GRS_1967",DATUM["D_GRS_1967",SPHEROID["GRS_1967",6378160.0,298.247167427]],PRIME
4042 GCS_Everest_1830 GEOGCS["GCS_Everest_1830",DATUM["D_Everest_1830",SPHEROID["Everest_1830",6377299.36,300.8017]],PR
4046 GCS_RGRDC_2005 GEOGCS["GCS_RGRDC_2005",DATUM["D_Reseau_Geodesique_de_la_RDC_2005",SPHEROID["GRS_1980",63
4047 GCS_Sphere_GRS_1980_Authalic GEOGCS["GCS_Sphere_GRS_1980_Authalic",DATUM["D_Sphere_GRS_1980_Authalic",SPHEROID["Sphere_GRS
4052 GCS_Sphere_Clarke_1866_Authalic GEOGCS["GCS_Sphere_Clarke_1866_Authalic",DATUM["D_Sphere_Clarke_1866_Authalic",SPHEROID["Sphere_C
4053 GCS_Sphere_International_1924_Authalic GEOGCS["GCS_Sphere_International_1924_Authalic",DATUM["D_Sphere_International_1924_Authalic",SPHEROID
4054 GCS_Hughes_1980 GEOGCS["GCS_Hughes_1980",DATUM["D_Hughes_1980",SPHEROID["Hughes_1980",6378273.0,298.279411123
4075 GCS_SREF98 GEOGCS["GCS_SREF98",DATUM["D_Serbian_Reference_Network_1998",SPHEROID["GRS_1980",6378137.0,29
4081 GCS_REGCAN95 GEOGCS["GCS_REGCAN95",DATUM["D_Red_Geodesica_de_Canarias_1995",SPHEROID["GRS_1980",6378137
4120 GCS_Greek GEOGCS["GCS_Greek",DATUM["D_Greek",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Gree
4121 GCS_GGRS_1987 GEOGCS["GCS_GGRS_1987",DATUM["D_GGRS_1987",SPHEROID["GRS_1980",6378137.0,298.257222101]],PR

4122 GCS_ATS_1977 GEOGCS["GCS_ATS_1977",DATUM["D_ATS_1977",SPHEROID["ATS_1977",6378135.0,298.257]],PRIMEM["Green

4123 GCS_KKJ GEOGCS["GCS_KKJ",DATUM["D_KKJ",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenwich",0
4124 GCS_RT_1990 GEOGCS["GCS_RT_1990",DATUM["D_RT_1990",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM
4126 GCS_LKS_1994 GEOGCS["GCS_LKS_1994",DATUM["D_Lithuania_1994",SPHEROID["GRS_1980",6378137.0,298.257222101]],PR
4127 GCS_Tete GEOGCS["GCS_Tete",DATUM["D_Tete",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIMEM["Greenwich
4128 GCS_Madzansua GEOGCS["GCS_Madzansua",DATUM["D_Madzansua",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIME
4129 GCS_Observatario GEOGCS["GCS_Observatario",DATUM["D_Observatario",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRI
4130 GCS_Moznet GEOGCS["GCS_Moznet",DATUM["D_Moznet",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Gre
4131 GCS_Indian_1960 GEOGCS["GCS_Indian_1960",DATUM["D_Indian_1960",SPHEROID["Everest_Adjustment_1937",6377276.345,300
4132 GCS_FD_1958 GEOGCS["GCS_FD_1958",DATUM["D_FD_1958",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM
4133 GCS_Estonia_1992 GEOGCS["GCS_Estonia_1992",DATUM["D_Estonia_1992",SPHEROID["GRS_1980",6378137.0,298.257222101]],P
4134 GCS_PDO_1993 GEOGCS["GCS_PDO_1993",DATUM["D_PDO_1993",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRI
4135 GCS_Old_Hawaiian GEOGCS["GCS_Old_Hawaiian",DATUM["D_Old_Hawaiian",SPHEROID["Clarke_1866",6378206.4,294.9786982]],P
4136 GCS_St_Lawrence_Island GEOGCS["GCS_St_Lawrence_Island",DATUM["D_St_Lawrence_Island",SPHEROID["Clarke_1866",6378206.4,294
4137 GCS_St_Paul_Island GEOGCS["GCS_St_Paul_Island",DATUM["D_St_Paul_Island",SPHEROID["Clarke_1866",6378206.4,294.9786982]]
4138 GCS_St_George_Island GEOGCS["GCS_St_George_Island",DATUM["D_St_George_Island",SPHEROID["Clarke_1866",6378206.4,294.978
4139 GCS_Puerto_Rico GEOGCS["GCS_Puerto_Rico",DATUM["D_Puerto_Rico",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIM
4140 GCS_North_American_1983_CSRS GEOGCS["GCS_North_American_1983_CSRS",DATUM["D_North_American_1983_CSRS",SPHEROID["GRS_198
4141 GCS_Israel GEOGCS["GCS_Israel",DATUM["D_Israel",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenw
4142 GCS_Locodjo_1965 GEOGCS["GCS_Locodjo_1965",DATUM["D_Locodjo_1965",SPHEROID["Clarke_1880_RGS",6378249.145,293.465
4143 GCS_Abidjan_1987 GEOGCS["GCS_Abidjan_1987",DATUM["D_Abidjan_1987",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]
4144 GCS_Kalianpur_1937 GEOGCS["GCS_Kalianpur_1937",DATUM["D_Kalianpur_1937",SPHEROID["Everest_Adjustment_1937",6377276.3
4145 GCS_Kalianpur_1962 GEOGCS["GCS_Kalianpur_1962",DATUM["D_Kalianpur_1962",SPHEROID["Everest_Definition_1962",6377301.243
4146 GCS_Kalianpur_1975 GEOGCS["GCS_Kalianpur_1975",DATUM["D_Kalianpur_1975",SPHEROID["Everest_Definition_1975",6377299.151
4147 GCS_Hanoi_1972 GEOGCS["GCS_Hanoi_1972",DATUM["D_Hanoi_1972",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIMEM
4148 GCS_Hartebeesthoek_1994 GEOGCS["GCS_Hartebeesthoek_1994",DATUM["D_Hartebeesthoek_1994",SPHEROID["WGS_1984",6378137.0,2
4149 GCS_CH1903 GEOGCS["GCS_CH1903",DATUM["D_CH1903",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["
4150 GCS_CH1903+ GEOGCS["GCS_CH1903+",DATUM["D_CH1903+",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM
4151 GCS_Swiss_TRF_1995 GEOGCS["GCS_Swiss_TRF_1995",DATUM["D_Swiss_TRF_1995",SPHEROID["GRS_1980",6378137.0,298.25722
4152 GCS_North_American_1983_HARN GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_198
4153 GCS_Rassadiran GEOGCS["GCS_Rassadiran",DATUM["D_Rassadiran",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4154 GCS_European_1950_ED77 GEOGCS["GCS_European_1950_ED77",DATUM["D_European_1950_ED77",SPHEROID["International_1924",6378
4155 GCS_Dabola_1981 GEOGCS["GCS_Dabola_1981",DATUM["D_Dabola_1981",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212
4156 GCS_S_JTSK GEOGCS["GCS_S_JTSK",DATUM["D_S_JTSK",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["
4157 GCS_Mount_Dillon GEOGCS["GCS_Mount_Dillon",DATUM["D_Mount_Dillon",SPHEROID["Clarke_1858",6378293.645208759,294.260
4158 GCS_Naparima_1955 GEOGCS["GCS_Naparima_1955",DATUM["D_Naparima_1955",SPHEROID["International_1924",6378388.0,297.0]]
4159 GCS_European_Libyan_Datum_1979 GEOGCS["GCS_European_Libyan_Datum_1979",DATUM["D_European_Libyan_1979",SPHEROID["International_1
4160 GCS_Chos_Malal_1914 GEOGCS["GCS_Chos_Malal_1914",DATUM["D_Chos_Malal_1914",SPHEROID["International_1924",6378388.0,29
4161 GCS_Pampa_del_Castillo GEOGCS["GCS_Pampa_del_Castillo",DATUM["D_Pampa_del_Castillo",SPHEROID["International_1924",6378388.0
4162 GCS_Korean_Datum_1985 GEOGCS["GCS_Korean_Datum_1985",DATUM["D_Korean_Datum_1985",SPHEROID["Bessel_1841",6377397.155
4163 GCS_Yemen_NGN_1996 GEOGCS["GCS_Yemen_NGN_1996",DATUM["D_Yemen_NGN_1996",SPHEROID["WGS_1984",6378137.0,298.25
4164 GCS_South_Yemen GEOGCS["GCS_South_Yemen",DATUM["D_South_Yemen",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIM
4165 GCS_Bissau GEOGCS["GCS_Bissau",DATUM["D_Bissau",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenw
4166 GCS_Korean_Datum_1995 GEOGCS["GCS_Korean_Datum_1995",DATUM["D_Korean_Datum_1995",SPHEROID["WGS_1984",6378137.0,298
4167 GCS_NZGD_2000 GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRI
4168 GCS_Accra GEOGCS["GCS_Accra",DATUM["D_Accra",SPHEROID["War_Office",6378300.0,296.0]],PRIMEM["Greenwich",0.0],U
4169 GCS_American_Samoa_1962 GEOGCS["GCS_American_Samoa_1962",DATUM["D_American_Samoa_1962",SPHEROID["Clarke_1866",637820
4170 GCS_SIRGAS GEOGCS["GCS_SIRGAS",DATUM["D_SIRGAS",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["G
4171 GCS_RGF_1993 GEOGCS["GCS_RGF_1993",DATUM["D_RGF_1993",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
4172 GCS_POSGAR GEOGCS["GCS_POSGAR",DATUM["D_POSGAR",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM[
4173 GCS_IRENET95 GEOGCS["GCS_IRENET95",DATUM["D_IRENET95",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
4174 GCS_Sierra_Leone_1924 GEOGCS["GCS_Sierra_Leone_1924",DATUM["D_Sierra_Leone_1924",SPHEROID["War_Office",6378300.0,296.0]]
4175 GCS_Sierra_Leone_1968 GEOGCS["GCS_Sierra_Leone_1968",DATUM["D_Sierra_Leone_1968",SPHEROID["Clarke_1880_RGS",6378249.1
4176 GCS_Australian_Antarctic_1998 GEOGCS["GCS_Australian_Antarctic_1998",DATUM["D_Australian_Antarctic_1998",SPHEROID["GRS_1980",6378

4178 GCS_Pulkovo_1942_Adj_1983 GEOGCS["GCS_Pulkovo_1942_Adj_1983",DATUM["D_Pulkovo_1942_Adj_1983",SPHEROID["Krasovsky_1940",63

4179 GCS_Pulkovo_1942_Adj_1958 GEOGCS["GCS_Pulkovo_1942_Adj_1958",DATUM["D_Pulkovo_1942_Adj_1958",SPHEROID["Krasovsky_1940",63
4180 GCS_Estonia_1997 GEOGCS["GCS_Estonia_1997",DATUM["D_Estonia_1997",SPHEROID["GRS_1980",6378137.0,298.257222101]],P
4181 GCS_Luxembourg_1930 GEOGCS["GCS_Luxembourg_1930",DATUM["D_Luxembourg_1930",SPHEROID["International_1924",6378388.0,2
4182 GCS_Azores_Occidental_1939 GEOGCS["GCS_Azores_Occidental_1939",DATUM["D_Azores_Occidental_Islands_1939",SPHEROID["Internationa
4183 GCS_Azores_Central_1948 GEOGCS["GCS_Azores_Central_1948",DATUM["D_Azores_Central_Islands_1948",SPHEROID["International_1924
4184 GCS_Azores_Oriental_1940 GEOGCS["GCS_Azores_Oriental_1940",DATUM["D_Azores_Oriental_Islands_1940",SPHEROID["International_192
4185 GCS_Madeira_1936 GEOGCS["GCS_Madeira_1936",DATUM["D_Madeira_1936",SPHEROID["International_1924",6378388.0,297.0]],PR
4188 GCS_OSNI_1952 GEOGCS["GCS_OSNI_1952",DATUM["D_OSNI_1952",SPHEROID["Airy_1830",6377563.396,299.3249646]],PRIME
4189 GCS_REGVEN GEOGCS["GCS_REGVEN",DATUM["D_REGVEN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM[
4190 GCS_POSGAR_1998 GEOGCS["GCS_POSGAR_1998",DATUM["D_POSGAR_1998",SPHEROID["GRS_1980",6378137.0,298.25722210
4191 GCS_Albanian_1987 GEOGCS["GCS_Albanian_1987",DATUM["D_Albanian_1987",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PR
4192 GCS_Douala_1948 GEOGCS["GCS_Douala_1948",DATUM["D_Douala_1948",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4193 GCS_Manoca_1962 GEOGCS["GCS_Manoca_1962",DATUM["D_Manoca_1962",SPHEROID["Clarke_1880_IGN",6378249.2,293.46602
4194 GCS_Qornoq_1927 GEOGCS["GCS_Qornoq_1927",DATUM["D_Qornoq_1927",SPHEROID["International_1924",6378388.0,297.0]],PRI
4195 GCS_Scoresbysund_1952 GEOGCS["GCS_Scoresbysund_1952",DATUM["D_Scoresbysund_1952",SPHEROID["International_1924",6378388
4196 GCS_Ammassalik_1958 GEOGCS["GCS_Ammassalik_1958",DATUM["D_Ammassalik_1958",SPHEROID["International_1924",6378388.0,29
4197 GCS_Garoua GEOGCS["GCS_Garoua",DATUM["D_Garoua",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["G
4198 GCS_Kousseri GEOGCS["GCS_Kousseri",DATUM["D_Kousseri",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM
4199 GCS_Egypt_1930 GEOGCS["GCS_Egypt_1930",DATUM["D_Egypt_1930",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4200 GCS_Pulkovo_1995 GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulkovo_1995",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIM
4201 GCS_Adindan GEOGCS["GCS_Adindan",DATUM["D_Adindan",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM[
4202 GCS_Australian_1966 GEOGCS["GCS_Australian_1966",DATUM["D_Australian_1966",SPHEROID["Australian",6378160.0,298.25]],PRIME
4203 GCS_Australian_1984 GEOGCS["GCS_Australian_1984",DATUM["D_Australian_1984",SPHEROID["Australian",6378160.0,298.25]],PRIME
4204 GCS_Ain_el_Abd_1970 GEOGCS["GCS_Ain_el_Abd_1970",DATUM["D_Ain_el_Abd_1970",SPHEROID["International_1924",6378388.0,297
4205 GCS_Afgooye GEOGCS["GCS_Afgooye",DATUM["D_Afgooye",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIMEM["Green
4206 GCS_Agadez GEOGCS["GCS_Agadez",DATUM["D_Agadez",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]],P
4207 GCS_Lisbon GEOGCS["GCS_Lisbon",DATUM["D_Lisbon",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenw
4208 GCS_Aratu GEOGCS["GCS_Aratu",DATUM["D_Aratu",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenwich
4209 GCS_Arc_1950 GEOGCS["GCS_Arc_1950",DATUM["D_Arc_1950",SPHEROID["Clarke_1880_Arc",6378249.145,293.466307656]],P
4210 GCS_Arc_1960 GEOGCS["GCS_Arc_1960",DATUM["D_Arc_1960",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIME
4211 GCS_Batavia GEOGCS["GCS_Batavia",DATUM["D_Batavia",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["G
4212 GCS_Barbados_1938 GEOGCS["GCS_Barbados_1938",DATUM["D_Barbados_1938",SPHEROID["Clarke_1880_RGS",6378249.145,293.
4213 GCS_Beduaram GEOGCS["GCS_Beduaram",DATUM["D_Beduaram",SPHEROID["Clarke_1880_IGN",6378249.2,293.466021293626
4214 GCS_Beijing_1954 GEOGCS["GCS_Beijing_1954",DATUM["D_Beijing_1954",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIME
4215 GCS_Belge_1950 GEOGCS["GCS_Belge_1950",DATUM["D_Belge_1950",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4216 GCS_Bermuda_1957 GEOGCS["GCS_Bermuda_1957",DATUM["D_Bermuda_1957",SPHEROID["Clarke_1866",6378206.4,294.9786982]
4218 GCS_Bogota GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenw
4219 GCS_Bukit_Rimpah GEOGCS["GCS_Bukit_Rimpah",DATUM["D_Bukit_Rimpah",SPHEROID["Bessel_1841",6377397.155,299.1528128]
4220 GCS_Camacupa GEOGCS["GCS_Camacupa",DATUM["D_Camacupa",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIM
4221 GCS_Campo_Inchauspe GEOGCS["GCS_Campo_Inchauspe",DATUM["D_Campo_Inchauspe",SPHEROID["International_1924",6378388.0,2
4222 GCS_Cape GEOGCS["GCS_Cape",DATUM["D_Cape",SPHEROID["Clarke_1880_Arc",6378249.145,293.466307656]],PRIMEM
4223 GCS_Carthage GEOGCS["GCS_Carthage",DATUM["D_Carthage",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265
4224 GCS_Chua GEOGCS["GCS_Chua",DATUM["D_Chua",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenwich
4225 GCS_Corrego_Alegre GEOGCS["GCS_Corrego_Alegre",DATUM["D_Corrego_Alegre",SPHEROID["International_1924",6378388.0,297.0]]
4226 GCS_Cote_d_Ivoire GEOGCS["GCS_Cote_d_Ivoire",DATUM["D_Cote_d_Ivoire",SPHEROID["Clarke_1880_IGN",6378249.2,293.466021
4227 GCS_Deir_ez_Zor GEOGCS["GCS_Deir_ez_Zor",DATUM["D_Deir_ez_Zor",SPHEROID["Clarke_1880_IGN",6378249.2,293.46602129
4228 GCS_Douala GEOGCS["GCS_Douala",DATUM["D_Douala",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]],PR
4229 GCS_Egypt_1907 GEOGCS["GCS_Egypt_1907",DATUM["D_Egypt_1907",SPHEROID["Helmert_1906",6378200.0,298.3]],PRIMEM["G
4230 GCS_European_1950 GEOGCS["GCS_European_1950",DATUM["D_European_1950",SPHEROID["International_1924",6378388.0,297.0]]
4232 GCS_Fahud GEOGCS["GCS_Fahud",DATUM["D_Fahud",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["Gre
4234 GCS_Garoua GEOGCS["GCS_Garoua",DATUM["D_Garoua",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["G
4235 GCS_Guyane_Francaise GEOGCS["GCS_Guyane_Francaise",DATUM["D_Guyane_Francaise",SPHEROID["International_1924",6378388.0,2

4236 GCS_Hu_Tzu_Shan GEOGCS["GCS_Hu_Tzu_Shan",DATUM["D_Hu_Tzu_Shan",SPHEROID["International_1924",6378388.0,297.0]],PR

4237 GCS_Hungarian_1972 GEOGCS["GCS_Hungarian_1972",DATUM["D_Hungarian_1972",SPHEROID["GRS_1967",6378160.0,298.2471674
4238 GCS_Indonesian_1974 GEOGCS["GCS_Indonesian_1974",DATUM["D_Indonesian_1974",SPHEROID["Indonesian",6378160.0,298.247]],PR
4241 GCS_Jamaica_1875 GEOGCS["GCS_Jamaica_1875",DATUM["D_Jamaica_1875",SPHEROID["Clarke_1880",6378249.144808011,293.4
4242 GCS_Jamaica_1969 GEOGCS["GCS_Jamaica_1969",DATUM["D_Jamaica_1969",SPHEROID["Clarke_1866",6378206.4,294.9786982]],P
4243 GCS_Kalianpur_1880 GEOGCS["GCS_Kalianpur_1880",DATUM["D_Kalianpur_1880",SPHEROID["Everest_1830",6377299.36,300.8017]]
4244 GCS_Kandawala GEOGCS["GCS_Kandawala",DATUM["D_Kandawala",SPHEROID["Everest_Adjustment_1937",6377276.345,300.80
4245 GCS_Kertau GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID["Everest_1830_Modified",6377304.063,300.8017]],PRIME
4246 GCS_Kuwait_Oil_Company GEOGCS["GCS_Kuwait_Oil_Company",DATUM["D_Kuwait_Oil_Company",SPHEROID["Clarke_1880_RGS",63782
4247 GCS_La_Canoa GEOGCS["GCS_La_Canoa",DATUM["D_La_Canoa",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["
4248 GCS_Provisional_S_American_1956 GEOGCS["GCS_Provisional_S_American_1956",DATUM["D_Provisional_S_American_1956",SPHEROID["Internatio
4249 GCS_Lake GEOGCS["GCS_Lake",DATUM["D_Lake",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenwich"
4250 GCS_Leigon GEOGCS["GCS_Leigon",DATUM["D_Leigon",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["Gr
4251 GCS_Liberia_1964 GEOGCS["GCS_Liberia_1964",DATUM["D_Liberia_1964",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],
4252 GCS_Lome GEOGCS["GCS_Lome",DATUM["D_Lome",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]],PRIM
4253 GCS_Luzon_1911 GEOGCS["GCS_Luzon_1911",DATUM["D_Luzon_1911",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIM
4254 GCS_Hito_XVIII_1963 GEOGCS["GCS_Hito_XVIII_1963",DATUM["D_Hito_XVIII_1963",SPHEROID["International_1924",6378388.0,297.0]
4255 GCS_Herat_North GEOGCS["GCS_Herat_North",DATUM["D_Herat_North",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4256 GCS_Mahe_1971 GEOGCS["GCS_Mahe_1971",DATUM["D_Mahe_1971",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PR
4257 GCS_Makassar GEOGCS["GCS_Makassar",DATUM["D_Makassar",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIME
4258 GCS_ETRS_1989 GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
4259 GCS_Malongo_1987 GEOGCS["GCS_Malongo_1987",DATUM["D_Malongo_1987",SPHEROID["International_1924",6378388.0,297.0]],P
4260 GCS_Manoca GEOGCS["GCS_Manoca",DATUM["D_Manoca",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["
4261 GCS_Merchich GEOGCS["GCS_Merchich",DATUM["D_Merchich",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]
4262 GCS_Massawa GEOGCS["GCS_Massawa",DATUM["D_Massawa",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM
4263 GCS_Minna GEOGCS["GCS_Minna",DATUM["D_Minna",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["Gre
4265 GCS_Monte_Mario GEOGCS["GCS_Monte_Mario",DATUM["D_Monte_Mario",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4266 GCS_Mporaloko GEOGCS["GCS_Mporaloko",DATUM["D_Mporaloko",SPHEROID["Clarke_1880_IGN",6378249.2,293.46602129362
4267 GCS_North_American_1927 GEOGCS["GCS_North_American_1927",DATUM["D_North_American_1927",SPHEROID["Clarke_1866",6378206.4
4269 GCS_North_American_1983 GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,2
4270 GCS_Nahrwan_1967 GEOGCS["GCS_Nahrwan_1967",DATUM["D_Nahrwan_1967",SPHEROID["Clarke_1880_RGS",6378249.145,293.4
4271 GCS_Naparima_1972 GEOGCS["GCS_Naparima_1972",DATUM["D_Naparima_1972",SPHEROID["International_1924",6378388.0,297.0]]
4272 GCS_New_Zealand_1949 GEOGCS["GCS_New_Zealand_1949",DATUM["D_New_Zealand_1949",SPHEROID["International_1924",6378388.0
4273 GCS_NGO_1948 GEOGCS["GCS_NGO_1948",DATUM["D_NGO_1948",SPHEROID["Bessel_Modified",6377492.018,299.1528128]],P
4274 GCS_Datum_73 GEOGCS["GCS_Datum_73",DATUM["D_Datum_73",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["
4275 GCS_NTF GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]],PRIMEM
4276 GCS_NSWC_9Z_2 GEOGCS["GCS_NSWC_9Z_2",DATUM["D_NSWC_9Z_2",SPHEROID["NWL_9D",6378145.0,298.25]],PRIMEM["Gr
4277 GCS_OSGB_1936 GEOGCS["GCS_OSGB_1936",DATUM["D_OSGB_1936",SPHEROID["Airy_1830",6377563.396,299.3249646]],PRIM
4278 GCS_OSGB_1970_SN GEOGCS["GCS_OSGB_1970_SN",DATUM["D_OSGB_1970_SN",SPHEROID["Airy_1830",6377563.396,299.32496
4279 GCS_OS_SN_1980 GEOGCS["GCS_OS_SN_1980",DATUM["D_OS_SN_1980",SPHEROID["Airy_1830",6377563.396,299.3249646]],PR
4280 GCS_Padang_1884 GEOGCS["GCS_Padang_1884",DATUM["D_Padang_1884",SPHEROID["Bessel_1841",6377397.155,299.1528128]
4281 GCS_Palestine_1923 GEOGCS["GCS_Palestine_1923",DATUM["D_Palestine_1923",SPHEROID["Clarke_1880_Benoit",6378300.789,293
4282 GCS_Pointe_Noire GEOGCS["GCS_Pointe_Noire",DATUM["D_Pointe_Noire",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212
4283 GCS_GDA_1994 GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
4284 GCS_Pulkovo_1942 GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulkovo_1942",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIM
4285 GCS_Qatar_1974 GEOGCS["GCS_Qatar_1974",DATUM["D_Qatar",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Gre
4286 GCS_Qatar_1948 GEOGCS["GCS_Qatar_1948",DATUM["D_Qatar_1948",SPHEROID["Helmert_1906",6378200.0,298.3]],PRIMEM["G
4288 GCS_Loma_Quintana GEOGCS["GCS_Loma_Quintana",DATUM["D_Loma_Quintana",SPHEROID["International_1924",6378388.0,297.0]]
4289 GCS_Amersfoort GEOGCS["GCS_Amersfoort",DATUM["D_Amersfoort",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIM
4291 GCS_South_American_1969 GEOGCS["GCS_South_American_1969",DATUM["D_South_American_1969",SPHEROID["GRS_1967_Truncated",6
4292 GCS_Sapper_Hill_1943 GEOGCS["GCS_Sapper_Hill_1943",DATUM["D_Sapper_Hill_1943",SPHEROID["International_1924",6378388.0,297
4293 GCS_Schwarzeck GEOGCS["GCS_Schwarzeck",DATUM["D_Schwarzeck",SPHEROID["Bessel_Namibia",6377483.865280418,299.15

4294 GCS_Segora GEOGCS["GCS_Segora",DATUM["D_Segora",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["G

4295 GCS_Serindung GEOGCS["GCS_Serindung",DATUM["D_Serindung",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIME
4296 GCS_Sudan GEOGCS["GCS_Sudan",DATUM["D_Sudan",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]],PRI
4297 GCS_Tananarive_1925 GEOGCS["GCS_Tananarive_1925",DATUM["D_Tananarive_1925",SPHEROID["International_1924",6378388.0,297.
4298 GCS_Timbalai_1948 GEOGCS["GCS_Timbalai_1948",DATUM["D_Timbalai_1948",SPHEROID["Everest_Definition_1967",6377298.556,3
4299 GCS_TM65 GEOGCS["GCS_TM65",DATUM["D_TM65",SPHEROID["Airy_Modified",6377340.189,299.3249646]],PRIMEM["Gree
4300 GCS_TM75 GEOGCS["GCS_TM75",DATUM["D_TM75",SPHEROID["Airy_Modified",6377340.189,299.3249646]],PRIMEM["Gree
4301 GCS_Tokyo GEOGCS["GCS_Tokyo",DATUM["D_Tokyo",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Gree
4302 GCS_Trinidad_1903 GEOGCS["GCS_Trinidad_1903",DATUM["D_Trinidad_1903",SPHEROID["Clarke_1858",6378293.645208759,294.26
4303 GCS_Trucial_Coast_1948 GEOGCS["GCS_Trucial_Coast_1948",DATUM["D_Trucial_Coast_1948",SPHEROID["Helmert_1906",6378200.0,298
4304 GCS_Voirol_1875 GEOGCS["GCS_Voirol_1875",DATUM["D_Voirol_1875",SPHEROID["Clarke_1880_IGN",6378249.2,293.466021293
4305 GCS_Voirol_Unifie_1960 GEOGCS["GCS_Voirol_Unifie_1960",DATUM["D_Voirol_Unifie_1960",SPHEROID["Clarke_1880_RGS",6378249.14
4306 GCS_Bern_1938 GEOGCS["GCS_Bern_1938",DATUM["D_Bern_1938",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIM
4307 GCS_Nord_Sahara_1959 GEOGCS["GCS_Nord_Sahara_1959",DATUM["D_Nord_Sahara_1959",SPHEROID["Clarke_1880_RGS",6378249.1
4308 GCS_RT38 GEOGCS["GCS_RT38",DATUM["D_Stockholm_1938",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIM
4309 GCS_Yacare GEOGCS["GCS_Yacare",DATUM["D_Yacare",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenw
4310 GCS_Yoff GEOGCS["GCS_Yoff",DATUM["D_Yoff",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]],PRIMEM[
4311 GCS_Zanderij GEOGCS["GCS_Zanderij",DATUM["D_Zanderij",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Gree
4312 GCS_MGI GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Greenw
4313 GCS_Belge_1972 GEOGCS["GCS_Belge_1972",DATUM["D_Belge_1972",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4314 GCS_Deutsches_Hauptdreiecksnetz GEOGCS["GCS_Deutsches_Hauptdreiecksnetz",DATUM["D_Deutsches_Hauptdreiecksnetz",SPHEROID["Bessel_1
4315 GCS_Conakry_1905 GEOGCS["GCS_Conakry_1905",DATUM["D_Conakry_1905",SPHEROID["Clarke_1880_IGN",6378249.2,293.46602
4316 GCS_Dealul_Piscului_1933 GEOGCS["GCS_Dealul_Piscului_1933",DATUM["D_Dealul_Piscului_1933",SPHEROID["International_1924",637838
4317 GCS_Dealul_Piscului_1970 GEOGCS["GCS_Dealul_Piscului_1970",DATUM["D_Dealul_Piscului_1970",SPHEROID["Krasovsky_1940",6378245
4318 GCS_NGN GEOGCS["GCS_NGN",DATUM["D_NGN",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenw
4319 GCS_KUDAMS GEOGCS["GCS_KUDAMS",DATUM["D_Kuwait_Utility",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
4322 GCS_WGS_1972 GEOGCS["GCS_WGS_1972",DATUM["D_WGS_1972",SPHEROID["WGS_1972",6378135.0,298.26]],PRIMEM["Gre
4324 GCS_WGS_1972_BE GEOGCS["GCS_WGS_1972_BE",DATUM["D_WGS_1972_BE",SPHEROID["WGS_1972",6378135.0,298.26]],PRIM
4326 GCS_WGS_1984 GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIM
4463 GCS_RGSPM_2006 GEOGCS["GCS_RGSPM_2006",DATUM["D_Reseau_Geodesique_de_St_Pierre_et_Miquelon_2006",SPHEROID["G
4466 GCS_RGSPM_2006 GEOGCS["GCS_RGSPM_2006",DATUM["D_Reseau_Geodesique_de_St_Pierre_et_Miquelon_2006",SPHEROID["G
4469 GCS_RGM_2004 GEOGCS["GCS_RGM_2004",DATUM["D_Reseau_Geodesique_de_Mayotte_2004",SPHEROID["GRS_1980",63781
4470 GCS_RGM_2004 GEOGCS["GCS_RGM_2004",DATUM["D_Reseau_Geodesique_de_Mayotte_2004",SPHEROID["GRS_1980",63781
4475 GCS_Cadastre_1997 GEOGCS["GCS_Cadastre_1997",DATUM["D_Cadastre_1997",SPHEROID["International_1924",6378388.0,297.0]],P
4483 GCS_Mexican_Datum_of_1993 GEOGCS["GCS_Mexican_Datum_of_1993",DATUM["D_Mexican_Datum_of_1993",SPHEROID["GRS_1980",63781
4490 GCS_China_Geodetic_Coordinate_System_2000 GEOGCS["GCS_China_Geodetic_Coordinate_System_2000",DATUM["D_China_2000",SPHEROID["CGCS2000",63
4555 GCS_New_Beijing GEOGCS["GCS_New_Beijing",DATUM["D_New_Beijing",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIMEM
4558 GCS_RRAF_1991 GEOGCS["GCS_RRAF_1991",DATUM["D_RRAF_1991",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRI
4600 GCS_Anguilla_1957 GEOGCS["GCS_Anguilla_1957",DATUM["D_Anguilla_1957",SPHEROID["Clarke_1880_RGS",6378249.145,293.465
4601 GCS_Antigua_1943 GEOGCS["GCS_Antigua_1943",DATUM["D_Antigua_1943",SPHEROID["Clarke_1880_RGS",6378249.145,293.465
4602 GCS_Dominica_1945 GEOGCS["GCS_Dominica_1945",DATUM["D_Dominica_1945",SPHEROID["Clarke_1880_RGS",6378249.145,293.4
4603 GCS_Grenada_1953 GEOGCS["GCS_Grenada_1953",DATUM["D_Grenada_1953",SPHEROID["Clarke_1880_RGS",6378249.145,293.46
4604 GCS_Montserrat_1958 GEOGCS["GCS_Montserrat_1958",DATUM["D_Montserrat_1958",SPHEROID["Clarke_1880_RGS",6378249.145,29
4605 GCS_St_Kitts_1955 GEOGCS["GCS_St_Kitts_1955",DATUM["D_St_Kitts_1955",SPHEROID["Clarke_1880_RGS",6378249.145,293.465
4606 GCS_St_Lucia_1955 GEOGCS["GCS_St_Lucia_1955",DATUM["D_St_Lucia_1955",SPHEROID["Clarke_1880_RGS",6378249.145,293.46
4607 GCS_St_Vincent_1945 GEOGCS["GCS_St_Vincent_1945",DATUM["D_St_Vincent_1945",SPHEROID["Clarke_1880_RGS",6378249.145,29
4608 GCS_NAD_1927_Definition_1976 GEOGCS["GCS_NAD_1927_Definition_1976",DATUM["D_NAD_1927_Definition_1976",SPHEROID["Clarke_1866",
4609 GCS_NAD_1927_CGQ77 GEOGCS["GCS_NAD_1927_CGQ77",DATUM["D_NAD_1927_CGQ77",SPHEROID["Clarke_1866",6378206.4,294.9
4610 GCS_Xian_1980 GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980",SPHEROID["Xian_1980",6378140.0,298.257]],PRIMEM["Gree
4611 GCS_Hong_Kong_1980 GEOGCS["GCS_Hong_Kong_1980",DATUM["D_Hong_Kong_1980",SPHEROID["International_1924",6378388.0,29
4612 GCS_JGD_2000 GEOGCS["GCS_JGD_2000",DATUM["D_JGD_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
4613 GCS_Gunung_Segara GEOGCS["GCS_Gunung_Segara",DATUM["D_Gunung_Segara",SPHEROID["Bessel_1841",6377397.155,299.1528
4614 GCS_QND_1995 GEOGCS["GCS_QND_1995",DATUM["D_QND_1995",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4615 GCS_Porto_Santo_1936 GEOGCS["GCS_Porto_Santo_1936",DATUM["D_Porto_Santo_1936",SPHEROID["International_1924",6378388.0,2

4616 GCS_Selvagem_Grande_1938 GEOGCS["GCS_Selvagem_Grande_1938",DATUM["D_Selvagem_Grande_1938",SPHEROID["International_1924",

4617 GCS_North_American_1983_CSRS GEOGCS["GCS_North_American_1983_CSRS",DATUM["D_North_American_1983_CSRS",SPHEROID["GRS_198
4618 GCS_South_American_1969 GEOGCS["GCS_South_American_1969",DATUM["D_South_American_1969",SPHEROID["GRS_1967_Truncated",6
4619 GCS_SWEREF99 GEOGCS["GCS_SWEREF99",DATUM["D_SWEREF99",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
4620 GCS_Point_58 GEOGCS["GCS_Point_58",DATUM["D_Point_58",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM
4621 GCS_Fort_Marigot GEOGCS["GCS_Fort_Marigot",DATUM["D_Fort_Marigot",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4622 GCS_Sainte_Anne GEOGCS["GCS_Sainte_Anne",DATUM["D_Sainte_Anne",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4623 GCS_CSG_1967 GEOGCS["GCS_CSG_1967",DATUM["D_CSG_1967",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4624 GCS_RGFG_1995 GEOGCS["GCS_RGFG_1995",DATUM["D_RGFG_1995",SPHEROID["GRS_1980",6378137.0,298.257222101]],PR
4625 GCS_Fort_Desaix GEOGCS["GCS_Fort_Desaix",DATUM["D_Fort_Desaix",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4626 GCS_Reunion_1947 GEOGCS["GCS_Reunion_1947",DATUM["D_Reunion_1947",SPHEROID["International_1924",6378388.0,297.0]],PR
4627 GCS_RGR_1992 GEOGCS["GCS_RGR_1992",DATUM["D_RGR_1992",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
4628 GCS_Tahiti_1952 GEOGCS["GCS_Tahiti_1952",DATUM["D_Tahiti_1952",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4629 GCS_Tahaa_1954 GEOGCS["GCS_Tahaa_1954",DATUM["D_Tahaa_1954",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4630 GCS_IGN72_Nuku_Hiva GEOGCS["GCS_IGN72_Nuku_Hiva",DATUM["D_IGN72_Nuku_Hiva",SPHEROID["International_1924",6378388.0,2
4631 GCS_Kerguelen_Island_1949 GEOGCS["GCS_Kerguelen_Island_1949",DATUM["D_Kerguelen_Island_1949",SPHEROID["International_1924",63
4632 GCS_Combani_1950 GEOGCS["GCS_Combani_1950",DATUM["D_Combani_1950",SPHEROID["International_1924",6378388.0,297.0]],P
4633 GCS_IGN56_Lifou GEOGCS["GCS_IGN56_Lifou",DATUM["D_IGN56_Lifou",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4636 GCS_Petrels_1972 GEOGCS["GCS_Petrels_1972",DATUM["D_Petrels_1972",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4637 GCS_Pointe_Geologie_Perroud_1950 GEOGCS["GCS_Pointe_Geologie_Perroud_1950",DATUM["D_Pointe_Geologie_Perroud_1950",SPHEROID["Intern
4638 GCS_Saint_Pierre_et_Miquelon_1950 GEOGCS["GCS_Saint_Pierre_et_Miquelon_1950",DATUM["D_Saint_Pierre_et_Miquelon_1950",SPHEROID["Clarke
4639 GCS_MOP78 GEOGCS["GCS_MOP78",DATUM["D_MOP78",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Green
4641 GCS_IGN53_Mare GEOGCS["GCS_IGN53_Mare",DATUM["D_IGN53_Mare",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4642 GCS_ST84_Ile_des_Pins GEOGCS["GCS_ST84_Ile_des_Pins",DATUM["D_ST84_Ile_des_Pins",SPHEROID["International_1924",6378388.0,
4643 GCS_ST71_Belep GEOGCS["GCS_ST71_Belep",DATUM["D_ST71_Belep",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4644 GCS_NEA74_Noumea GEOGCS["GCS_NEA74_Noumea",DATUM["D_NEA74_Noumea",SPHEROID["International_1924",6378388.0,297.0
4645 GCS_RGNC_1991 GEOGCS["GCS_RGNC_1991",DATUM["D_RGNC_1991",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4646 GCS_Grand_Comoros GEOGCS["GCS_Grand_Comoros",DATUM["D_Grand_Comoros",SPHEROID["International_1924",6378388.0,297.0
4657 GCS_Reykjavik_1900 GEOGCS["GCS_Reykjavik_1900",DATUM["D_Reykjavik_1900",SPHEROID["Danish_1876",6377019.27,300.0]],PRI
4658 GCS_Hjorsey_1955 GEOGCS["GCS_Hjorsey_1955",DATUM["D_Hjorsey_1955",SPHEROID["International_1924",6378388.0,297.0]],PRI
4659 GCS_ISN_1993 GEOGCS["GCS_ISN_1993",DATUM["D_Islands_Network_1993",SPHEROID["GRS_1980",6378137.0,298.2572221
4660 GCS_Helle_1954 GEOGCS["GCS_Helle_1954",DATUM["D_Helle_1954",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4661 GCS_LKS_1992 GEOGCS["GCS_LKS_1992",DATUM["D_Latvia_1992",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
4662 GCS_IGN72_Grande_Terre GEOGCS["GCS_IGN72_Grande_Terre",DATUM["D_IGN72_Grande_Terre",SPHEROID["International_1924",637838
4664 GCS_Azores_Oriental_1995 GEOGCS["GCS_Azores_Oriental_1995",DATUM["D_Azores_Oriental_Islands_1995",SPHEROID["International_192
4665 GCS_Azores_Central_1995 GEOGCS["GCS_Azores_Central_1995",DATUM["D_Azores_Central_Islands_1995",SPHEROID["International_1924
4666 GCS_Lisbon_1890 GEOGCS["GCS_Lisbon_1890",DATUM["D_Lisbon_1890",SPHEROID["Bessel_1841",6377397.155,299.1528128]],P
4667 GCS_IKBD_1992 GEOGCS["GCS_IKBD_1992",DATUM["D_Iraq_Kuwait_Boundary_1992",SPHEROID["WGS_1984",6378137.0,298.2
4669 GCS_LKS_1994 GEOGCS["GCS_LKS_1994",DATUM["D_Lithuania_1994",SPHEROID["GRS_1980",6378137.0,298.257222101]],PR
4670 GCS_IGM_1995 GEOGCS["GCS_IGM_1995",DATUM["D_IGM_1995",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIME
4672 GCS_Chatham_Island_1971 GEOGCS["GCS_Chatham_Island_1971",DATUM["D_Chatham_Island_1971",SPHEROID["International_1924",6378
4673 GCS_Chatham_Islands_1979 GEOGCS["GCS_Chatham_Islands_1979",DATUM["D_Chatham_Islands_1979",SPHEROID["International_1924",63
4674 GCS_SIRGAS_2000 GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIRGAS_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]]
4675 GCS_Guam_1963 GEOGCS["GCS_Guam_1963",DATUM["D_Guam_1963",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIM
4676 GCS_Vientiane_1982 GEOGCS["GCS_Vientiane_1982",DATUM["D_Vientiane_1982",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PR
4677 GCS_Lao_1993 GEOGCS["GCS_Lao_1993",DATUM["D_Lao_1993",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIMEM["Gre
4678 GCS_Lao_1997 GEOGCS["GCS_Lao_1997",DATUM["D_Lao_National_Datum_1997",SPHEROID["Krasovsky_1940",6378245.0,298
4679 GCS_Jouik_1961 GEOGCS["GCS_Jouik_1961",DATUM["D_Jouik_1961",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PR
4680 GCS_Nouakchott_1965 GEOGCS["GCS_Nouakchott_1965",DATUM["D_Nouakchott_1965",SPHEROID["Clarke_1880_RGS",6378249.145,2
4682 GCS_Gulshan_303 GEOGCS["GCS_Gulshan_303",DATUM["D_Gulshan_303",SPHEROID["Everest_Adjustment_1937",6377276.345,30
4683 GCS_PRS_1992 GEOGCS["GCS_PRS_1992",DATUM["D_Philippine_Reference_System_1992",SPHEROID["Clarke_1866",6378206

4684 GCS_Gan_1970 GEOGCS["GCS_Gan_1970",DATUM["D_Gan_1970",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["

4686 GCS_MAGNA GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["G
4687 GCS_RGPF GEOGCS["GCS_RGPF",DATUM["D_Reseau_Geodesique_de_la_Polynesie_Francaise",SPHEROID["GRS_1980",6
4688 GCS_Fatu_Iva_1972 GEOGCS["GCS_Fatu_Iva_1972",DATUM["D_Fatu_Iva_1972",SPHEROID["International_1924",6378388.0,297.0]],P
4689 GCS_IGN63_Hiva_Oa GEOGCS["GCS_IGN63_Hiva_Oa",DATUM["D_IGN63_Hiva_Oa",SPHEROID["International_1924",6378388.0,297.0
4690 GCS_Tahiti_1979 GEOGCS["GCS_Tahiti_1979",DATUM["D_Tahiti_1979",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4691 GCS_Moorea_1987 GEOGCS["GCS_Moorea_1987",DATUM["D_Moorea_1987",SPHEROID["International_1924",6378388.0,297.0]],PRI
4692 GCS_Maupiti_1983 GEOGCS["GCS_Maupiti_1983",DATUM["D_Maupiti_1983",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4693 GCS_Nakhl-e_Ghanem GEOGCS["GCS_Nakhl-e_Ghanem",DATUM["D_Nakhl-e_Ghanem",SPHEROID["WGS_1984",6378137.0,298.25722
4695 GCS_Katanga_1955 GEOGCS["GCS_Katanga_1955",DATUM["D_Katanga_1955",SPHEROID["Clarke_1866",6378206.4,294.9786982]],P
4696 GCS_Kasai_1953 GEOGCS["GCS_Kasai_1953",DATUM["D_Kasai_1953",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PR
4697 GCS_IGC_1962_6th_Parallel_South GEOGCS["GCS_IGC_1962_6th_Parallel_South",DATUM["D_IGC_1962_Arc_of_the_6th_Parallel_South",SPHEROI
4699 GCS_Le_Pouce_1934 GEOGCS["GCS_Le_Pouce_1934",DATUM["D_Le_Pouce_1934",SPHEROID["Clarke_1880_RGS",6378249.145,293
4700 GCS_IGN_Astro_1960 GEOGCS["GCS_IGN_Astro_1960",DATUM["D_IGN_Astro_1960",SPHEROID["Clarke_1880_RGS",6378249.145,29
4701 GCS_IGCB_1955 GEOGCS["GCS_IGCB_1955",DATUM["D_Institut_Geographique_du_Congo_Belge_1955",SPHEROID["Clarke_188
4702 GCS_Mauritania_1999 GEOGCS["GCS_Mauritania_1999",DATUM["D_Mauritania_1999",SPHEROID["GRS_1980",6378137.0,298.2572221
4703 GCS_Mhast_1951 GEOGCS["GCS_Mhast_1951",DATUM["D_Mhast_1951",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],P
4704 GCS_Mhast_Onshore GEOGCS["GCS_Mhast_Onshore",DATUM["D_Mhast_Onshore",SPHEROID["International_1924",6378388.0,297.0]]
4705 GCS_Mhast_Offshore GEOGCS["GCS_Mhast_Offshore",DATUM["D_Mhast_Offshore",SPHEROID["International_1924",6378388.0,297.0]]
4706 GCS_Egypt_Gulf_of_Suez_S-650_TL GEOGCS["GCS_Egypt_Gulf_of_Suez_S-650_TL",DATUM["D_Egypt_Gulf_of_Suez_S-650_TL",SPHEROID["Helme
4707 GCS_Tern_Island_1961 GEOGCS["GCS_Tern_Island_1961",DATUM["D_Tern_Island_1961",SPHEROID["International_1924",6378388.0,297
4708 GCS_Anna_1_1965 GEOGCS["GCS_Anna_1_1965",DATUM["D_Anna_1_1965",SPHEROID["Australian",6378160.0,298.25]],PRIMEM["
4709 GCS_Beacon_E_1945 GEOGCS["GCS_Beacon_E_1945",DATUM["D_Beacon_E_1945",SPHEROID["International_1924",6378388.0,297.0
4710 GCS_DOS_71_4 GEOGCS["GCS_DOS_71_4",DATUM["D_DOS_71_4",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4711 GCS_Astro_1952 GEOGCS["GCS_Astro_1952",DATUM["D_Astro_1952",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4712 GCS_Ascension_Island_1958 GEOGCS["GCS_Ascension_Island_1958",DATUM["D_Ascension_Island_1958",SPHEROID["International_1924",63
4713 GCS_Ayabelle GEOGCS["GCS_Ayabelle",DATUM["D_Ayabelle",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM
4714 GCS_Bellevue_IGN GEOGCS["GCS_Bellevue_IGN",DATUM["D_Bellevue_IGN",SPHEROID["International_1924",6378388.0,297.0]],PRI
4715 GCS_Camp_Area GEOGCS["GCS_Camp_Area",DATUM["D_Camp_Area",SPHEROID["International_1924",6378388.0,297.0]],PRIME
4716 GCS_Canton_1966 GEOGCS["GCS_Canton_1966",DATUM["D_Canton_1966",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4717 GCS_Cape_Canaveral GEOGCS["GCS_Cape_Canaveral",DATUM["D_Cape_Canaveral",SPHEROID["Clarke_1866",6378206.4,294.97869
4718 GCS_Solomon_1968 GEOGCS["GCS_Solomon_1968",DATUM["D_Solomon_1968",SPHEROID["International_1924",6378388.0,297.0]],P
4719 GCS_Easter_Island_1967 GEOGCS["GCS_Easter_Island_1967",DATUM["D_Easter_Island_1967",SPHEROID["International_1924",6378388.0
4720 GCS_Fiji_1986 GEOGCS["GCS_Fiji_1986",DATUM["D_Fiji_1986",SPHEROID["WGS_1972",6378135.0,298.26]],PRIMEM["Greenwi
4721 GCS_Fiji_1956 GEOGCS["GCS_Fiji_1956",DATUM["D_Fiji_1956",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Gr
4722 GCS_ISTS_061_1968 GEOGCS["GCS_ISTS_061_1968",DATUM["D_ISTS_061_1968",SPHEROID["International_1924",6378388.0,297.0]
4723 GCS_Grand_Cayman_1959 GEOGCS["GCS_Grand_Cayman_1959",DATUM["D_Grand_Cayman_1959",SPHEROID["Clarke_1866",6378206.4,2
4725 GCS_Johnston_Island_1961 GEOGCS["GCS_Johnston_Island_1961",DATUM["D_Johnston_Island_1961",SPHEROID["International_1924",6378
4726 GCS_Little_Cayman_1961 GEOGCS["GCS_Little_Cayman_1961",DATUM["D_Little_Cayman_1961",SPHEROID["Clarke_1866",6378206.4,294
4727 GCS_Midway_1961 GEOGCS["GCS_Midway_1961",DATUM["D_Midway_1961",SPHEROID["International_1924",6378388.0,297.0]],PRI
4728 GCS_Pico_de_Las_Nieves GEOGCS["GCS_Pico_de_Las_Nieves",DATUM["D_Pico_de_Las_Nieves",SPHEROID["International_1924",637838
4729 GCS_Pitcairn_1967 GEOGCS["GCS_Pitcairn_1967",DATUM["D_Pitcairn_1967",SPHEROID["International_1924",6378388.0,297.0]],PRI
4730 GCS_Santo_DOS_1965 GEOGCS["GCS_Santo_DOS_1965",DATUM["D_Santo_DOS_1965",SPHEROID["International_1924",6378388.0,29
4731 GCS_Viti_Levu_1916 GEOGCS["GCS_Viti_Levu_1916",DATUM["D_Viti_Levu_1916",SPHEROID["Clarke_1880_RGS",6378249.145,293.4
4732 GCS_Wake_Eniwetok_1960 GEOGCS["GCS_Wake_Eniwetok_1960",DATUM["D_Wake_Eniwetok_1960",SPHEROID["Hough_1960",6378270.0,
4733 GCS_Wake_Island_1952 GEOGCS["GCS_Wake_Island_1952",DATUM["D_Wake_Island_1952",SPHEROID["International_1924",6378388.0,2
4734 GCS_Tristan_1968 GEOGCS["GCS_Tristan_1968",DATUM["D_Tristan_1968",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4735 GCS_Kusaie_1951 GEOGCS["GCS_Kusaie_1951",DATUM["D_Kusaie_1951",SPHEROID["International_1924",6378388.0,297.0]],PRIM
4736 GCS_Deception_Island GEOGCS["GCS_Deception_Island",DATUM["D_Deception_Island",SPHEROID["Clarke_1880_RGS",6378249.145,2
4737 GCS_Korea_2000 GEOGCS["GCS_Korea_2000",DATUM["D_Korea_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
4738 GCS_Hong_Kong_1963 GEOGCS["GCS_Hong_Kong_1963",DATUM["D_Hong_Kong_1963",SPHEROID["Clarke_1858",6378293.64520875

4739 GCS_Hong_Kong_1963_67 GEOGCS["GCS_Hong_Kong_1963_67",DATUM["D_Hong_Kong_1963_67",SPHEROID["International_1924",63783

4740 GCS_PZ_1990 GEOGCS["GCS_PZ_1990",DATUM["D_Parametrop_Zemp_1990",SPHEROID["PZ_1990",6378136.0,298.25783930
4741 GCS_FD_1954 GEOGCS["GCS_FD_1954",DATUM["D_Faroe_Datum_1954",SPHEROID["International_1924",6378388.0,297.0]],PR
4742 GCS_GDM_2000 GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
4743 GCS_Karbala_1979_Polservice GEOGCS["GCS_Karbala_1979_Polservice",DATUM["D_Karbala_1979_Polservice",SPHEROID["Clarke_1880_RGS
4744 GCS_Nahrwan_1934 GEOGCS["GCS_Nahrwan_1934",DATUM["D_Nahrwan_1934",SPHEROID["Clarke_1880_RGS",6378249.145,293.4
4745 GCS_RD/83 GEOGCS["GCS_RD/83",DATUM["D_Rauenberg_1983",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PR
4746 GCS_PD/83 GEOGCS["GCS_PD/83",DATUM["D_Potsdam_1983",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIM
4747 GCS_Greenland_1996 GEOGCS["GCS_Greenland_1996",DATUM["D_Greenland_1996",SPHEROID["GRS_1980",6378137.0,298.2572221
4748 GCS_Vanua_Levu_1915 GEOGCS["GCS_Vanua_Levu_1915",DATUM["D_Vanua_Levu_1915",SPHEROID["Clarke_1880_Intl_Ft",6378306.36
4749 GCS_RGNC_1991-93 GEOGCS["GCS_RGNC_1991-93",DATUM["D_Reseau_Geodesique_de_Nouvelle_Caledonie_1991-93",SPHEROID
4750 GCS_ST87_Ouvea GEOGCS["GCS_ST87_Ouvea",DATUM["D_ST87_Ouvea",SPHEROID["WGS_1984",6378137.0,298.257223563]],P
4751 GCS_Kertau_RSO GEOGCS["GCS_Kertau_RSO",DATUM["D_Kertau_RSO",SPHEROID["Everest_Modified_1969",6377295.664,300.8
4752 GCS_Viti_Levu_1912 GEOGCS["GCS_Viti_Levu_1912",DATUM["D_Viti_Levu_1912",SPHEROID["Clarke_1880_Intl_Ft",6378306.3696,29
4753 GCS_fk89 GEOGCS["GCS_fk89",DATUM["D_fk89",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenwich",
4754 GCS_LGD2006 GEOGCS["GCS_LGD2006",DATUM["D_Libyan_Geodetic_Datum_2006",SPHEROID["International_1924",6378388.
4755 GCS_DGN_1995 GEOGCS["GCS_DGN_1995",DATUM["D_Datum_Geodesi_Nasional_1995",SPHEROID["WGS_1984",6378137.0,29
4756 GCS_VN_2000 GEOGCS["GCS_VN_2000",DATUM["D_Vietnam_2000",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIM
4757 GCS_SVY21 GEOGCS["GCS_SVY21",DATUM["D_SVY21",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Gre
4758 GCS_JAD_2001 GEOGCS["GCS_JAD_2001",DATUM["D_Jamaica_2001",SPHEROID["WGS_1984",6378137.0,298.257223563]],PR
4759 GCS_NAD_1983_NSRS2007 GEOGCS["GCS_NAD_1983_NSRS2007",DATUM["D_NAD_1983_NSRS2007",SPHEROID["GRS_1980",6378137.0
4761 GCS_HTRS96 GEOGCS["GCS_HTRS96",DATUM["D_Croatian_Terrestrial_Reference_System",SPHEROID["GRS_1980",6378137
4762 GCS_Bermuda_2000 GEOGCS["GCS_Bermuda_2000",DATUM["D_Bermuda_2000",SPHEROID["WGS_1984",6378137.0,298.257223563
4763 GCS_Pitcairn_2006 GEOGCS["GCS_Pitcairn_2006",DATUM["D_Pitcairn_2006",SPHEROID["WGS_1984",6378137.0,298.257223563]],P
4764 GCS_RSRGD2000 GEOGCS["GCS_RSRGD2000",DATUM["D_Ross_Sea_Region_Geodetic_Datum_2000",SPHEROID["GRS_1980",6
4765 GCS_Slovenia_1996 GEOGCS["GCS_Slovenia_1996",DATUM["D_Slovenia_Geodetic_Datum_1996",SPHEROID["GRS_1980",6378137.
4801 GCS_Bern_1898_Bern GEOGCS["GCS_Bern_1898_Bern",DATUM["D_Bern_1898",SPHEROID["Bessel_1841",6377397.155,299.1528128]
4802 GCS_Bogota_Bogota GEOGCS["GCS_Bogota_Bogota",DATUM["D_Bogota",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
4803 GCS_Lisbon_Lisbon GEOGCS["GCS_Lisbon_Lisbon",DATUM["D_Lisbon",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["
4804 GCS_Makassar_Jakarta GEOGCS["GCS_Makassar_Jakarta",DATUM["D_Makassar",SPHEROID["Bessel_1841",6377397.155,299.1528128]
4805 GCS_MGI_Ferro GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["F
4806 GCS_Monte_Mario_Rome GEOGCS["GCS_Monte_Mario_Rome",DATUM["D_Monte_Mario",SPHEROID["International_1924",6378388.0,297.0
4807 GCS_NTF_Paris GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265]],P
4808 GCS_Padang_1884_Jakarta GEOGCS["GCS_Padang_1884_Jakarta",DATUM["D_Padang_1884",SPHEROID["Bessel_1841",6377397.155,299.1
4809 GCS_Belge_1950_Brussels GEOGCS["GCS_Belge_1950_Brussels",DATUM["D_Belge_1950",SPHEROID["International_1924",6378388.0,297.0
4810 GCS_Tananarive_1925_Paris GEOGCS["GCS_Tananarive_1925_Paris",DATUM["D_Tananarive_1925",SPHEROID["International_1924",6378388.
4811 GCS_Voirol_1875_Paris GEOGCS["GCS_Voirol_1875_Paris",DATUM["D_Voirol_1875",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660
4812 GCS_Voirol_Unifie_1960_Paris GEOGCS["GCS_Voirol_Unifie_1960_Paris",DATUM["D_Voirol_Unifie_1960",SPHEROID["Clarke_1880_RGS",63782
4813 GCS_Batavia_Jakarta GEOGCS["GCS_Batavia_Jakarta",DATUM["D_Batavia",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PR
4814 GCS_RT38_Stockholm GEOGCS["GCS_RT38_Stockholm",DATUM["D_Stockholm_1938",SPHEROID["Bessel_1841",6377397.155,299.152
4815 GCS_Greek_Athens GEOGCS["GCS_Greek_Athens",DATUM["D_Greek",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIME
4816 GCS_Carthage_Paris GEOGCS["GCS_Carthage_Paris",DATUM["D_Carthage",SPHEROID["Clarke_1880_IGN",6378249.2,293.46602129
4817 GCS_NGO_1948_Oslo GEOGCS["GCS_NGO_1948_Oslo",DATUM["D_NGO_1948",SPHEROID["Bessel_Modified",6377492.018,299.15281
4818 GCS_S_JTSK_Ferro GEOGCS["GCS_S_JTSK_Ferro",DATUM["D_S_JTSK",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRI
4819 GCS_Nord_Sahara_1959_Paris GEOGCS["GCS_Nord_Sahara_1959_Paris",DATUM["D_Nord_Sahara_1959",SPHEROID["Clarke_1880_RGS",6378
4820 GCS_Gunung_Segara_Jakarta GEOGCS["GCS_Gunung_Segara_Jakarta",DATUM["D_Gunung_Segara",SPHEROID["Bessel_1841",6377397.155,
4821 GCS_Voirol_1879_Paris GEOGCS["GCS_Voirol_1879_Paris",DATUM["D_Voirol_1879",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660
4823 GCS_Sao_Tome GEOGCS["GCS_Sao_Tome",DATUM["D_Sao_Tome",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM[
4824 GCS_Principe GEOGCS["GCS_Principe",DATUM["D_Principe",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Gree
4901 GCS_ATF_Paris GEOGCS["GCS_ATF_Paris",DATUM["D_ATF",SPHEROID["Plessis_1817",6376523.0,308.64]],PRIMEM["Paris_RGS
4902 GCS_Nord_de_Guerre_Paris GEOGCS["GCS_Nord_de_Guerre_Paris",DATUM["D_Nord_de_Guerre",SPHEROID["Plessis_1817",6376523.0,308
4903 GCS_Madrid_1870_Madrid GEOGCS["GCS_Madrid_1870_Madrid",DATUM["D_Madrid_1870",SPHEROID["Struve_1860",6378298.3,294.73]],P
4904 GCS_Lisbon_1890_Lisbon GEOGCS["GCS_Lisbon_1890_Lisbon",DATUM["D_Lisbon_1890",SPHEROID["Bessel_1841",6377397.155,299.152

5013 GCS_PTRA08 GEOGCS["GCS_PTRA08",DATUM["D_PTRA08",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["G

5228 GCS_S_JTSK/05 GEOGCS["GCS_S_JTSK/05",DATUM["D_S_JTSK_05",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRI
5229 GCS_S_JTSK/05_Ferro GEOGCS["GCS_S_JTSK/05_Ferro",DATUM["D_S_JTSK_05",SPHEROID["Bessel_1841",6377397.155,299.152812
5233 GCS_SLD99 GEOGCS["GCS_SLD99",DATUM["D_Sri_Lanka_Datum_1999",SPHEROID["Everest_Adjustment_1937",6377276.34
5246 GCS_GDBD2009 GEOGCS["GCS_GDBD2009",DATUM["D_GDBD2009",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
5252 GCS_TUREF GEOGCS["GCS_TUREF",DATUM["D_Turkish_National_Reference_Frame",SPHEROID["GRS_1980",6378137.0,29
5264 GCS_DRUKREF_03 GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_National_Geodetic_Datum",SPHEROID["GRS_1980",6378137
5354 GCS_MARGEN GEOGCS["GCS_MARGEN",DATUM["D_Marco_Geodesico_Nacional",SPHEROID["GRS_1980",6378137.0,298.257
5360 GCS_SIRGAS-Chile GEOGCS["GCS_SIRGAS-Chile",DATUM["D_SIRGAS-Chile",SPHEROID["GRS_1980",6378137.0,298.257222101]],
5365 GCS_CR05 GEOGCS["GCS_CR05",DATUM["D_Costa_Rica_2005",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIM
5371 GCS_MARCARIO_SOLIS GEOGCS["GCS_MARCARIO_SOLIS",DATUM["D_SGNP_MARCARIO_SOLIS",SPHEROID["GRS_1980",6378137.0
5373 GCS_Peru96 GEOGCS["GCS_Peru96",DATUM["D_Peru96",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Gre
5381 GCS_SIRGAS-ROU98 GEOGCS["GCS_SIRGAS-ROU98",DATUM["D_SIRGAS-ROU98",SPHEROID["WGS_1984",6378137.0,298.2572235
5393 GCS_SIRGAS_ES2007.8 GEOGCS["GCS_SIRGAS_ES2007.8",DATUM["D_SIRGAS_ES2007.8",SPHEROID["GRS_1980",6378137.0,298.25
5451 GCS_Ocotepeque_1935 GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Ocotepeque_1935",SPHEROID["Clarke_1866",6378206.4,294.978
5464 GCS_Sibun_Gorge_1922 GEOGCS["GCS_Sibun_Gorge_1922",DATUM["D_Sibun_Gorge_1922",SPHEROID["Clarke_1858",6378293.645208
5467 GCS_Panama-Colon_1911 GEOGCS["GCS_Panama-Colon_1911",DATUM["D_Panama-Colon-1911",SPHEROID["Clarke_1866",6378206.4,294
5489 GCS_RGAF09 GEOGCS["GCS_RGAF09",DATUM["Reseau_Geodesique_des_Antilles_Francaises_2009",SPHEROID["GRS_1980
5524 GCS_Corrego_Alegre_1961 GEOGCS["GCS_Corrego_Alegre_1961",DATUM["D_Corrego_Alegre_1961",SPHEROID["International_1924",63783
5527 GCS_SAD_1969_96 GEOGCS["GCS_SAD_1969_96",DATUM["D_South_American_Datum_1969_96",SPHEROID["GRS_1967_Truncate
5546 GCS_PNG94 GEOGCS["GCS_PNG94",DATUM["D_Papua_New_Guinea_Geodetic_Datum_1994",SPHEROID["GRS_1980",6378
5561 GCS_Ukraine_2000 GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukraine_2000",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIM
5593 GCS_FEH2010 GEOGCS["GCS_FEH2010",DATUM["D_Fehmarnbelt_Datum_2010",SPHEROID["GRS_1980",6378137.0,298.25722
5681 GCS_DB_REF GEOGCS["GCS_DB_REF",DATUM["D_Deutsche_Bahn_Reference_System",SPHEROID["Bessel_1841",6377397.1
5886 GCS_TGD2005 GEOGCS["GCS_TGD2005",DATUM["D_Tonga_Geodetic_Datum_2005",SPHEROID["GRS_1980",6378137.0,298.25
6135 GCS_CIGD11 GEOGCS["GCS_CIGD11",DATUM["D_Cayman_Islands_Geodetic_Datum_2011",SPHEROID["GRS_1980",6378137
6207 GCS_Nepal_Nagarkot GEOGCS["GCS_Nepal_Nagarkot",DATUM["D_Nepal_Nagarkot",SPHEROID["Everest_Adjustment_1937",6377276.3
6311 GCS_CGRS_1993 GEOGCS["GCS_CGRS_1993",DATUM["D_Cyprus_Geodetic_Reference_System_1993",SPHEROID["WGS_1984",
6318 GCS_NAD_1983_2011 GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1983_2011",SPHEROID["GRS_1980",6378137.0,298.257222
6322 GCS_NAD_1983_PA11 GEOGCS["GCS_NAD_1983_PA11",DATUM["D_NAD_1983_PA11",SPHEROID["GRS_1980",6378137.0,298.257222
6325 GCS_NAD_1983_MA11 GEOGCS["GCS_NAD_1983_MA11",DATUM["D_NAD_1983_MA11",SPHEROID["GRS_1980",6378137.0,298.25722
6365 GCS_Mexico_ITRF2008 GEOGCS["GCS_Mexico_ITRF2008",DATUM["D_Mexico_ITRF2008",SPHEROID["GRS_1980",6378137.0,298.2572
6668 GCS_JGD_2011 GEOGCS["GCS_JGD_2011",DATUM["D_JGD_2011",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM
6706 GCS_RDN2008 GEOGCS["GCS_RDN2008",DATUM["D_Rete_Dinamica_Nazionale_2008",SPHEROID["GRS_1980",6378137.0,298
6783 GCS_NAD_1983_CORS96 GEOGCS["GCS_NAD_1983_CORS96",DATUM["D_NAD_1983_CORS96",SPHEROID["GRS_1980",6378137.0,298
6881 GCS_Aden_1925 GEOGCS["GCS_Aden_1925",DATUM["D_Aden_1925",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PR
6882 GCS_Bekaa_Valley_1920 GEOGCS["GCS_Bekaa_Valley_1920",DATUM["D_Bekaa_Valley_1920",SPHEROID["Clarke_1880_RGS",6378249.1
6883 GCS_Bioko GEOGCS["GCS_Bioko",DATUM["D_Bioko",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenwic
6892 GCS_South_East_Island_1943 GEOGCS["GCS_South_East_Island_1943",DATUM["D_South_East_Island_1943",SPHEROID["Clarke_1880_RGS"
6894 GCS_Gambia GEOGCS["GCS_Gambia",DATUM["D_Gambia",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["
6980 IGD05 GEOGCS["IGD05",DATUM["Israel_Geodetic_Datum_2005",SPHEROID["WGS_1984",6378137.0,298.257223563]],P
6983 IG05_Intermediate_CRS GEOGCS["IG05_Intermediate_CRS",DATUM["IG05_Intermediate_Datum",SPHEROID["GRS_1980",6378137.0,298.
6987 IGD05(2012) GEOGCS["IGD05(2012)",DATUM["Israeli_Geodetic_Datum_2005(2012)",SPHEROID["WGS_1984",6378137.0,298.2
6990 IG05(2012)_Intermediate_CRS GEOGCS["IG05(2012)_Intermediate_CRS",DATUM["IG05(2012)_Intermediate_Datum",SPHEROID["GRS_1980",63
7035 RGSPM06_(lon-lat) GEOGCS["RGSPM06_(lon-lat)",DATUM["D_Reseau_Geodesique_de_St_Pierre_et_Miquelon_2006",SPHEROID["G
7037 RGR92_(lon-lat) GEOGCS["RGR92_(lon-lat)",DATUM["D_RGR_1992",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
7039 RGM04_(lon-lat) GEOGCS["RGM04_(lon-lat)",DATUM["D_Reseau_Geodesique_de_Mayotte_2004",SPHEROID["GRS_1980",637813
7041 RGFG95_(lon-lat) GEOGCS["RGFG95_(lon-lat)",DATUM["D_RGFG_1995",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
7073 GCS_RGTAAF07 GEOGCS["GCS_RGTAAF07",DATUM["D_Reseau_Geodesique_des_Terres_Australes_et_Antarctiques_Francaises
7084 RGF93_(lon-lat) GEOGCS["RGF93_(lon-lat)",DATUM["D_RGF_1993",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM
7086 RGAF09_(lon-lat) GEOGCS["RGAF09_(lon-lat)",DATUM["Reseau_Geodesique_des_Antilles_Francaises_2009",SPHEROID["GRS_19
7133 RGTAAF07_(lon-lat) GEOGCS["RGTAAF07_(lon-lat)",DATUM["D_Reseau_Geodesique_des_Terres_Australes_et_Antarctiques_Francais

7136 IGD05 GEOGCS["IGD05",DATUM["Israel_Geodetic_Datum_2005",SPHEROID["WGS_1984",6378137.0,298.257223563]],P

7139 IGD05(2012) GEOGCS["IGD05(2012)",DATUM["Israeli_Geodetic_Datum_2005(2012)",SPHEROID["WGS_1984",6378137.0,298.2
7373 ONGD14 GEOGCS["ONGD14",DATUM["Oman_National_Geodetic_Datum_2014",SPHEROID["GRS_1980",6378137.0,298.25
7798 BGS2005 GEOGCS["BGS2005",DATUM["Bulgaria_Geodetic_System_2005",SPHEROID["GRS_1980",6378137.0,298.257222
7844 GDA2020 GEOGCS["GDA2020",DATUM["GDA2020",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenw
37002 GCS_Fischer_1960 GEOGCS["GCS_Fischer_1960",DATUM["D_Fischer_1960",SPHEROID["Fischer_1960",6378166.0,298.3]],PRIMEM
37003 GCS_Fischer_1968 GEOGCS["GCS_Fischer_1968",DATUM["D_Fischer_1968",SPHEROID["Fischer_1968",6378150.0,298.3]],PRIMEM
37004 GCS_Fischer_Modified GEOGCS["GCS_Fischer_Modified",DATUM["D_Fischer_Modified",SPHEROID["Fischer_Modified",6378155.0,298.3]
37005 GCS_Hough_1960 GEOGCS["GCS_Hough_1960",DATUM["D_Hough_1960",SPHEROID["Hough_1960",6378270.0,297.0]],PRIMEM["G
37006 GCS_Everest_Modified_1969 GEOGCS["GCS_Everest_Modified_1969",DATUM["D_Everest_Modified_1969",SPHEROID["Everest_Modified_1969
37007 GCS_Walbeck GEOGCS["GCS_Walbeck",DATUM["D_Walbeck",SPHEROID["Walbeck",6376896.0,302.78]],PRIMEM["Greenwich",0
37008 GCS_Sphere_ARC_INFO GEOGCS["GCS_Sphere_ARC_INFO",DATUM["D_Sphere_ARC_INFO",SPHEROID["Sphere_ARC_INFO",6370997
37202 GCS_Everest_Bangladesh GEOGCS["GCS_Everest_Bangladesh",DATUM["D_Everest_Bangladesh",SPHEROID["Everest_Adjustment_1937",6
37203 GCS_Everest_India_Nepal GEOGCS["GCS_Everest_India_Nepal",DATUM["D_Everest_India_Nepal",SPHEROID["Everest_Definition_1962",63
37204 GCS_Hjorsey_1955 GEOGCS["GCS_Hjorsey_1955",DATUM["D_Hjorsey_1955",SPHEROID["International_1924",6378388.0,297.0]],PRI
37205 GCS_Hong_Kong_1963_67 GEOGCS["GCS_Hong_Kong_1963_67",DATUM["D_Hong_Kong_1963_67",SPHEROID["International_1924",63783
37206 GCS_Oman GEOGCS["GCS_Oman",DATUM["D_Oman",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM["Gre
37207 GCS_South_Asia_Singapore GEOGCS["GCS_South_Asia_Singapore",DATUM["D_South_Asia_Singapore",SPHEROID["Fischer_Modified",63781
37208 GCS_Ayabelle GEOGCS["GCS_Ayabelle",DATUM["D_Ayabelle",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM
37211 GCS_Point_58 GEOGCS["GCS_Point_58",DATUM["D_Point_58",SPHEROID["Clarke_1880_RGS",6378249.145,293.465]],PRIMEM
37212 GCS_Beacon_E_1945 GEOGCS["GCS_Beacon_E_1945",DATUM["D_Beacon_E_1945",SPHEROID["International_1924",6378388.0,297.0
37213 GCS_Tern_Island_1961 GEOGCS["GCS_Tern_Island_1961",DATUM["D_Tern_Island_1961",SPHEROID["International_1924",6378388.0,297
37214 GCS_Astro_1952 GEOGCS["GCS_Astro_1952",DATUM["D_Astro_1952",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
37215 GCS_Bellevue_IGN GEOGCS["GCS_Bellevue_IGN",DATUM["D_Bellevue_IGN",SPHEROID["International_1924",6378388.0,297.0]],PRI
37216 GCS_Canton_1966 GEOGCS["GCS_Canton_1966",DATUM["D_Canton_1966",SPHEROID["International_1924",6378388.0,297.0]],PRIM
37217 GCS_Chatham_Island_1971 GEOGCS["GCS_Chatham_Island_1971",DATUM["D_Chatham_Island_1971",SPHEROID["International_1924",6378
37218 GCS_DOS_1968 GEOGCS["GCS_DOS_1968",DATUM["D_DOS_1968",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
37219 GCS_Easter_Island_1967 GEOGCS["GCS_Easter_Island_1967",DATUM["D_Easter_Island_1967",SPHEROID["International_1924",6378388.0
37220 GCS_Guam_1963 GEOGCS["GCS_Guam_1963",DATUM["D_Guam_1963",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIM
37221 GCS_GUX_1 GEOGCS["GCS_GUX_1",DATUM["D_GUX_1",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Green
37222 GCS_Johnston_Island_1961 GEOGCS["GCS_Johnston_Island_1961",DATUM["D_Johnston_Island_1961",SPHEROID["International_1924",6378
37223 GCS_Carthage GEOGCS["GCS_Carthage",DATUM["D_Carthage",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212936265
37224 GCS_Midway_1961 GEOGCS["GCS_Midway_1961",DATUM["D_Midway_1961",SPHEROID["International_1924",6378388.0,297.0]],PRI
37225 GCS_Carthage_Grad GEOGCS["GCS_Carthage_Grad",DATUM["D_Carthage",SPHEROID["Clarke_1880_IGN",6378249.2,293.46602129
37226 GCS_Pitcairn_1967 GEOGCS["GCS_Pitcairn_1967",DATUM["D_Pitcairn_1967",SPHEROID["International_1924",6378388.0,297.0]],PRI
37227 GCS_Santo_DOS_1965 GEOGCS["GCS_Santo_DOS_1965",DATUM["D_Santo_DOS_1965",SPHEROID["International_1924",6378388.0,29
37228 GCS_Viti_Levu_1916 GEOGCS["GCS_Viti_Levu_1916",DATUM["D_Viti_Levu_1916",SPHEROID["Clarke_1880_RGS",6378249.145,293.4
37229 GCS_Wake_Eniwetok_1960 GEOGCS["GCS_Wake_Eniwetok_1960",DATUM["D_Wake_Eniwetok_1960",SPHEROID["Hough_1960",6378270.0,
37230 GCS_Wake_Island_1952 GEOGCS["GCS_Wake_Island_1952",DATUM["D_Wake_Island_1952",SPHEROID["International_1924",6378388.0,2
37231 GCS_Anna_1_1965 GEOGCS["GCS_Anna_1_1965",DATUM["D_Anna_1_1965",SPHEROID["Australian",6378160.0,298.25]],PRIMEM["
37232 GCS_Gan_1970 GEOGCS["GCS_Gan_1970",DATUM["D_Gan_1970",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["
37235 GCS_Reunion_1947 GEOGCS["GCS_Reunion_1947",DATUM["D_Reunion_1947",SPHEROID["International_1924",6378388.0,297.0]],PR
37237 GCS_Ascension_Island_1958 GEOGCS["GCS_Ascension_Island_1958",DATUM["D_Ascension_Island_1958",SPHEROID["International_1924",63
37238 GCS_DOS_71_4 GEOGCS["GCS_DOS_71_4",DATUM["D_DOS_71_4",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM
37239 GCS_Cape_Canaveral GEOGCS["GCS_Cape_Canaveral",DATUM["D_Cape_Canaveral",SPHEROID["Clarke_1866",6378206.4,294.97869
37240 GCS_Fort_Thomas_1955 GEOGCS["GCS_Fort_Thomas_1955",DATUM["D_Fort_Thomas_1955",SPHEROID["Clarke_1880_RGS",6378249.1
37241 GCS_Graciosa_Base_SW_1948 GEOGCS["GCS_Graciosa_Base_SW_1948",DATUM["D_Graciosa_Base_SW_1948",SPHEROID["International_192
37243 GCS_LC5_1961 GEOGCS["GCS_LC5_1961",DATUM["D_LC5_1961",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIMEM
37245 GCS_Observatorio_Meteorologico_1939 GEOGCS["GCS_Observatorio_Meteorologico_1939",DATUM["D_Observatorio_Meteorologico_1939",SPHEROID["In

37246 GCS_Pico_de_Las_Nieves GEOGCS["GCS_Pico_de_Las_Nieves",DATUM["D_Pico_de_Las_Nieves",SPHEROID["International_1924",637838

37249 GCS_Sao_Braz GEOGCS["GCS_Sao_Braz",DATUM["D_Sao_Braz",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["G
37250 GCS_Selvagem_Grande_1938 GEOGCS["GCS_Selvagem_Grande_1938",DATUM["D_Selvagem_Grande_1938",SPHEROID["International_1924",
37251 GCS_Tristan_1968 GEOGCS["GCS_Tristan_1968",DATUM["D_Tristan_1968",SPHEROID["International_1924",6378388.0,297.0]],PRIM
37252 GCS_American_Samoa_1962 GEOGCS["GCS_American_Samoa_1962",DATUM["D_American_Samoa_1962",SPHEROID["Clarke_1866",637820
37253 GCS_Camp_Area GEOGCS["GCS_Camp_Area",DATUM["D_Camp_Area",SPHEROID["International_1924",6378388.0,297.0]],PRIME
37254 GCS_Deception_Island GEOGCS["GCS_Deception_Island",DATUM["D_Deception_Island",SPHEROID["Clarke_1880_RGS",6378249.145,2
37255 GCS_Gunung_Segara GEOGCS["GCS_Gunung_Segara",DATUM["D_Gunung_Segara",SPHEROID["Bessel_1841",6377397.155,299.1528
37257 GCS_S42_Hungary GEOGCS["GCS_S42_Hungary",DATUM["D_S42_Hungary",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIM
37259 GCS_Kusaie_1951 GEOGCS["GCS_Kusaie_1951",DATUM["D_Kusaie_1951",SPHEROID["International_1924",6378388.0,297.0]],PRIM
37260 GCS_Alaskan_Islands GEOGCS["GCS_Alaskan_Islands",DATUM["D_Alaskan_Islands",SPHEROID["Clarke_1866",6378206.4,294.978698
104009 GCS_Kyrg-06 GEOGCS["GCS_Kyrg-06",DATUM["D_Kyrgyz_Republic_2006",SPHEROID["GRS_1980",6378137.0,298.257222101
104010 GCS_IGS08 GEOGCS["GCS_IGS08",DATUM["IGS08",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwi
104020 GCS_JGD_2011 GEOGCS["GCS_JGD_2011",DATUM["D_JGD_2011",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM
104047 GCS_Sphere_GRS_1980_Mean_Radius GEOGCS["GCS_Sphere_GRS_1980_Mean_Radius",DATUM["D_Sphere_GRS_1980_Mean_Radius",SPHEROID["S
104050 GCS_Xrail84 GEOGCS["GCS_Xrail84",DATUM["D_Xrail84",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Gre
104100 GCS_GDBD2009 GEOGCS["GCS_GDBD2009",DATUM["D_GDBD2009",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIM
104101 GCS_Estonia_1937 GEOGCS["GCS_Estonia_1937",DATUM["D_Estonia_1937",SPHEROID["Bessel_1841",6377397.155,299.1528128]]
104102 GCS_Hermannskogel GEOGCS["GCS_Hermannskogel",DATUM["D_Hermannskogel",SPHEROID["Bessel_1841",6377397.155,299.15281
104103 GCS_Sierra_Leone_1960 GEOGCS["GCS_Sierra_Leone_1960",DATUM["D_Sierra_Leone_1960",SPHEROID["Clarke_1880_RGS",6378249.1
104104 GCS_Hong_Kong_1980 GEOGCS["GCS_Hong_Kong_1980",DATUM["D_Hong_Kong_1980",SPHEROID["International_1924",6378388.0,29
104105 GCS_Datum_Lisboa_Bessel GEOGCS["GCS_Datum_Lisboa_Bessel",DATUM["D_Datum_Lisboa_Bessel",SPHEROID["Bessel_1841",6377397.1
104106 GCS_Datum_Lisboa_Hayford GEOGCS["GCS_Datum_Lisboa_Hayford",DATUM["D_Datum_Lisboa_Hayford",SPHEROID["International_1924",63
104107 GCS_RGF_1993 GEOGCS["GCS_RGF_1993",DATUM["D_RGF_1993",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
104108 GCS_NZGD_2000 GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRI
104109 GCS_Pohnpei GEOGCS["GCS_Pohnpei",DATUM["D_Pohnpei",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIMEM["Gr
104110 GCS_REGVEN GEOGCS["GCS_REGVEN",DATUM["D_REGVEN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM[
104111 GCS_JGD_2000 GEOGCS["GCS_JGD_2000",DATUM["D_JGD_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
104112 GCS_Bab_South GEOGCS["GCS_Bab_South",DATUM["D_Bab_South",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIME
104113 GCS_Majuro GEOGCS["GCS_Majuro",DATUM["D_Majuro",SPHEROID["Clarke_1866",6378206.4,294.9786982]],PRIMEM["Green
104114 GCS_Bermuda_2000 GEOGCS["GCS_Bermuda_2000",DATUM["D_Bermuda_2000",SPHEROID["WGS_1984",6378137.0,298.257223563
104115 GCS_ITRF_1988 GEOGCS["GCS_ITRF_1988",DATUM["D_ITRF_1988",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME
104125 GCS_Chatham_Islands_1979 GEOGCS["GCS_Chatham_Islands_1979",DATUM["D_Chatham_Islands_1979",SPHEROID["International_1924",63
104126 GCS_Observatorio_Meteorologico_1965 GEOGCS["GCS_Observatorio_Meteorologico_1965",DATUM["D_Observatorio_Meteorologico_1965",SPHEROID["In
104127 GCS_Roma_1940 GEOGCS["GCS_Roma_1940",DATUM["D_Roma_1940",SPHEROID["International_1924",6378388.0,297.0]],PRIME
104128 GCS_Sphere_EMEP GEOGCS["GCS_Sphere_EMEP",DATUM["D_Sphere_EMEP",SPHEROID["Sphere_EMEP",6370000.0,0.0]],PRIMEM
104129 GCS_EUREF_FIN GEOGCS["GCS_EUREF_FIN",DATUM["D_ETRS_1989",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRI
104130 GCS_Jordan GEOGCS["GCS_Jordan",DATUM["D_Jordan",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenw
104131 GCS_D48 GEOGCS["GCS_D48",DATUM["D_D48",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Greenwi
104132 GCS_Ocotepeque_1935 GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Ocotepeque_1935",SPHEROID["Clarke_1866",6378206.4,294.978
104133 GCS_JAD_2001 GEOGCS["GCS_JAD_2001",DATUM["D_Jamaica_2001",SPHEROID["WGS_1984",6378137.0,298.257223563]],PR
104134 GCS_MONREF_1997 GEOGCS["GCS_MONREF_1997",DATUM["D_ITRF_2000",SPHEROID["GRS_1980",6378137.0,298.257222101]],P
104135 GCS_MSK_1942 GEOGCS["GCS_MSK_1942",DATUM["D_Pulkovo_1942",SPHEROID["Krasovsky_1940",6378245.0,298.3]],PRIMEM
104136 GCS_TWD_1967 GEOGCS["GCS_TWD_1967",DATUM["D_TWD_1967",SPHEROID["GRS_1967_Truncated",6378160.0,298.25]],PRI

104137 GCS_TWD_1997 GEOGCS["GCS_TWD_1997",DATUM["D_TWD_1997",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIME

104138 GCS_Old_Hawaiian_Intl_1924 GEOGCS["GCS_Old_Hawaiian_Intl_1924",DATUM["D_Old_Hawaiian_Intl_1924",SPHEROID["International_1924",6
104139 GCS_Voirol_1875_Grad GEOGCS["GCS_Voirol_1875_Grad",DATUM["D_Voirol_1875",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660
104140 GCS_Voirol_1879_Grad GEOGCS["GCS_Voirol_1879_Grad",DATUM["D_Voirol_1879",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660
104141 GCS_CGRS_1993 GEOGCS["GCS_CGRS_1993",DATUM["D_Cyprus_Geodetic_Reference_System_1993",SPHEROID["WGS_1984",
104142 GCS_PTRA08 GEOGCS["GCS_PTRA08",DATUM["D_PTRA08",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["G
104143 GCS_CR05 GEOGCS["GCS_CR05",DATUM["D_Costa_Rica_2005",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIM
104145 GCS_NAD_1983_2011 GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1983_2011",SPHEROID["GRS_1980",6378137.0,298.257222
104199 GCS_WGS_1984_Major_Auxiliary_Sphere GEOGCS["GCS_WGS_1984_Major_Auxiliary_Sphere",DATUM["D_WGS_1984_Major_Auxiliary_Sphere",SPHERO
104223 GCS_NAD_1983_CORS96 GEOGCS["GCS_NAD_1983_CORS96",DATUM["D_NAD_1983_CORS96",SPHEROID["GRS_1980",6378137.0,298
104248 GCS_MACAO_2008 GEOGCS["GCS_MACAO_2008",DATUM["D_MACAO_2008",SPHEROID["International_1924",6378388.0,297.0]],PR
104256 GCS_Nepal_Nagarkot GEOGCS["GCS_Nepal_Nagarkot",DATUM["D_Nepal_Nagarkot",SPHEROID["Everest_Adjustment_1937",6377276.3
104258 GCS_ETRF_1989 GEOGCS["GCS_ETRF_1989",DATUM["D_ETRF_1989",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRI
104259 GCS_NAD_1983_PACP00 GEOGCS["GCS_NAD_1983_PACP00",DATUM["D_NAD_1983_PACP00",SPHEROID["GRS_1980",6378137.0,298.2
104260 GCS_NAD_1983_MARP00 GEOGCS["GCS_NAD_1983_MARP00",DATUM["D_NAD_1983_MARP00",SPHEROID["GRS_1980",6378137.0,298
104261 GCS_Merchich_Degree GEOGCS["GCS_Merchich_Degree",DATUM["D_Merchich",SPHEROID["Clarke_1880_IGN",6378249.2,293.4660212
104286 GCS_NAD_1983_MA11 GEOGCS["GCS_NAD_1983_MA11",DATUM["D_NAD_1983_MA11",SPHEROID["GRS_1980",6378137.0,298.25722
104287 GCS_NAD_1983_PA11 GEOGCS["GCS_NAD_1983_PA11",DATUM["D_NAD_1983_PA11",SPHEROID["GRS_1980",6378137.0,298.257222
104305 GCS_Voirol_Unifie_1960_Degree GEOGCS["GCS_Voirol_Unifie_1960_Degree",DATUM["D_Voirol_Unifie_1960",SPHEROID["Clarke_1880_RGS",637
104700 GCS_NAD_1983_HARN_Adj_MN_Anoka GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Anoka",DATUM["D_NAD_1983_HARN_Adj_MN_Anoka",SPHEROID[
104701 GCS_NAD_1983_HARN_Adj_MN_Becker GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Becker",DATUM["D_NAD_1983_HARN_Adj_MN_Becker",SPHEROID
104702 GCS_NAD_1983_HARN_Adj_MN_Beltrami_North GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Beltrami_North",DATUM["D_NAD_1983_HARN_Adj_MN_Beltrami_N
104703 GCS_NAD_1983_HARN_Adj_MN_Beltrami_South GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Beltrami_South",DATUM["D_NAD_1983_HARN_Adj_MN_Beltrami_S
104704 GCS_NAD_1983_HARN_Adj_MN_Benton GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Benton",DATUM["D_NAD_1983_HARN_Adj_MN_Benton",SPHEROID
104705 GCS_NAD_1983_HARN_Adj_MN_Big_Stone GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Big_Stone",DATUM["D_NAD_1983_HARN_Adj_MN_Big_Stone",SPH
104706 GCS_NAD_1983_HARN_Adj_MN_Blue_Earth GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Blue_Earth",DATUM["D_NAD_1983_HARN_Adj_MN_Blue_Earth",SP
104707 GCS_NAD_1983_HARN_Adj_MN_Brown GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Brown",DATUM["D_NAD_1983_HARN_Adj_MN_Brown",SPHEROID[
104708 GCS_NAD_1983_HARN_Adj_MN_Carlton GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Carlton",DATUM["D_NAD_1983_HARN_Adj_MN_Carlton",SPHEROID
104709 GCS_NAD_1983_HARN_Adj_MN_Carver GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Carver",DATUM["D_NAD_1983_HARN_Adj_MN_Carver",SPHEROID
104710 GCS_NAD_1983_HARN_Adj_MN_Cass_North GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Cass_North",DATUM["D_NAD_1983_HARN_Adj_MN_Cass_North",S
104711 GCS_NAD_1983_HARN_Adj_MN_Cass_South GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Cass_South",DATUM["D_NAD_1983_HARN_Adj_MN_Cass_South",S
104712 GCS_NAD_1983_HARN_Adj_MN_Chippewa GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Chippewa",DATUM["D_NAD_1983_HARN_Adj_MN_Chippewa",SPHE
104713 GCS_NAD_1983_HARN_Adj_MN_Chisago GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Chisago",DATUM["D_NAD_1983_HARN_Adj_MN_Chisago",SPHERO
104714 GCS_NAD_1983_HARN_Adj_MN_Cook_North GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Cook_North",DATUM["D_NAD_1983_HARN_Adj_MN_Cook_North",S
104715 GCS_NAD_1983_HARN_Adj_MN_Cook_South GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Cook_South",DATUM["D_NAD_1983_HARN_Adj_MN_Cook_South",
104716 GCS_NAD_1983_HARN_Adj_MN_Cottonwood GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Cottonwood",DATUM["D_NAD_1983_HARN_Adj_MN_Cottonwood",S
104717 GCS_NAD_1983_HARN_Adj_MN_Crow_Wing GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Crow_Wing",DATUM["D_NAD_1983_HARN_Adj_MN_Crow_Wing",S
104718 GCS_NAD_1983_HARN_Adj_MN_Dakota GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Dakota",DATUM["D_NAD_1983_HARN_Adj_MN_Dakota",SPHEROID
104719 GCS_NAD_1983_HARN_Adj_MN_Dodge GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Dodge",DATUM["D_NAD_1983_HARN_Adj_MN_Dodge",SPHEROID
104720 GCS_NAD_1983_HARN_Adj_MN_Douglas GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Douglas",DATUM["D_NAD_1983_HARN_Adj_MN_Douglas",SPHERO
104721 GCS_NAD_1983_HARN_Adj_MN_Faribault GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Faribault",DATUM["D_NAD_1983_HARN_Adj_MN_Faribault",SPHER
104722 GCS_NAD_1983_HARN_Adj_MN_Fillmore GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Fillmore",DATUM["D_NAD_1983_HARN_Adj_MN_Fillmore",SPHERO
104723 GCS_NAD_1983_HARN_Adj_MN_Freeborn GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Freeborn",DATUM["D_NAD_1983_HARN_Adj_MN_Freeborn",SPHER
104724 GCS_NAD_1983_HARN_Adj_MN_Goodhue GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Goodhue",DATUM["D_NAD_1983_HARN_Adj_MN_Goodhue",SPHER
104725 GCS_NAD_1983_HARN_Adj_MN_Grant GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Grant",DATUM["D_NAD_1983_HARN_Adj_MN_Grant",SPHEROID["S
104726 GCS_NAD_1983_HARN_Adj_MN_Hennepin GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Hennepin",DATUM["D_NAD_1983_HARN_Adj_MN_Hennepin",SPHE
104727 GCS_NAD_1983_HARN_Adj_MN_Houston GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Houston",DATUM["D_NAD_1983_HARN_Adj_MN_Houston",SPHERO
104728 GCS_NAD_1983_HARN_Adj_MN_Isanti GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Isanti",DATUM["D_NAD_1983_HARN_Adj_MN_Isanti",SPHEROID["S
104729 GCS_NAD_1983_HARN_Adj_MN_Itasca_North GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Itasca_North",DATUM["D_NAD_1983_HARN_Adj_MN_Itasca_North"
104730 GCS_NAD_1983_HARN_Adj_MN_Itasca_South GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Itasca_South",DATUM["D_NAD_1983_HARN_Adj_MN_Itasca_South
104731 GCS_NAD_1983_HARN_Adj_MN_Jackson GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Jackson",DATUM["D_NAD_1983_HARN_Adj_MN_Jackson",SPHERO

104732 GCS_NAD_1983_HARN_Adj_MN_Kanabec GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Kanabec",DATUM["D_NAD_1983_HARN_Adj_MN_Kanabec",SPHER

104733 GCS_NAD_1983_HARN_Adj_MN_Kandiyohi GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Kandiyohi",DATUM["D_NAD_1983_HARN_Adj_MN_Kandiyohi",SPHE
104734 GCS_NAD_1983_HARN_Adj_MN_Kittson GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Kittson",DATUM["D_NAD_1983_HARN_Adj_MN_Kittson",SPHEROID
104735 GCS_NAD_1983_HARN_Adj_MN_Koochiching GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Koochiching",DATUM["D_NAD_1983_HARN_Adj_MN_Koochiching",S
104736 GCS_NAD_1983_HARN_Adj_MN_Lac_Qui_Parle GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Lac_Qui_Parle",DATUM["D_NAD_1983_HARN_Adj_MN_Lac_Qui_Pa
104737 GCS_NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_North GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_North",DATUM["D_NAD_1983_HARN_Adj_MN_
104738 GCS_NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_South GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_South",DATUM["D_NAD_1983_HARN_Adj_MN
104739 GCS_NAD_1983_HARN_Adj_MN_Le_Sueur GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Le_Sueur",DATUM["D_NAD_1983_HARN_Adj_MN_Le_Sueur",SPHE
104740 GCS_NAD_1983_HARN_Adj_MN_Lincoln GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Lincoln",DATUM["D_NAD_1983_HARN_Adj_MN_Lincoln",SPHEROID
104741 GCS_NAD_1983_HARN_Adj_MN_Lyon GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Lyon",DATUM["D_NAD_1983_HARN_Adj_MN_Lyon",SPHEROID["S_
104742 GCS_NAD_1983_HARN_Adj_MN_McLeod GEOGCS["GCS_NAD_1983_HARN_Adj_MN_McLeod",DATUM["D_NAD_1983_HARN_Adj_MN_McLeod",SPHERO
104743 GCS_NAD_1983_HARN_Adj_MN_Mahnomen GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Mahnomen",DATUM["D_NAD_1983_HARN_Adj_MN_Mahnomen",SP
104744 GCS_NAD_1983_HARN_Adj_MN_Marshall GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Marshall",DATUM["D_NAD_1983_HARN_Adj_MN_Marshall",SPHER
104745 GCS_NAD_1983_HARN_Adj_MN_Martin GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Martin",DATUM["D_NAD_1983_HARN_Adj_MN_Martin",SPHEROID[
104746 GCS_NAD_1983_HARN_Adj_MN_Meeker GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Meeker",DATUM["D_NAD_1983_HARN_Adj_MN_Meeker",SPHEROI
104747 GCS_NAD_1983_HARN_Adj_MN_Morrison GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Morrison",DATUM["D_NAD_1983_HARN_Adj_MN_Morrison",SPHER
104748 GCS_NAD_1983_HARN_Adj_MN_Mower GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Mower",DATUM["D_NAD_1983_HARN_Adj_MN_Mower",SPHEROID
104749 GCS_NAD_1983_HARN_Adj_MN_Murray GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Murray",DATUM["D_NAD_1983_HARN_Adj_MN_Murray",SPHEROID
104750 GCS_NAD_1983_HARN_Adj_MN_Nicollet GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Nicollet",DATUM["D_NAD_1983_HARN_Adj_MN_Nicollet",SPHEROI
104751 GCS_NAD_1983_HARN_Adj_MN_Nobles GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Nobles",DATUM["D_NAD_1983_HARN_Adj_MN_Nobles",SPHEROID
104752 GCS_NAD_1983_HARN_Adj_MN_Norman GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Norman",DATUM["D_NAD_1983_HARN_Adj_MN_Norman",SPHERO
104753 GCS_NAD_1983_HARN_Adj_MN_Olmsted GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Olmsted",DATUM["D_NAD_1983_HARN_Adj_MN_Olmsted",SPHERO
104754 GCS_NAD_1983_HARN_Adj_MN_Ottertail GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Ottertail",DATUM["D_NAD_1983_HARN_Adj_MN_Ottertail",SPHERO
104755 GCS_NAD_1983_HARN_Adj_MN_Pennington GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Pennington",DATUM["D_NAD_1983_HARN_Adj_MN_Pennington",SP
104756 GCS_NAD_1983_HARN_Adj_MN_Pine GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Pine",DATUM["D_NAD_1983_HARN_Adj_MN_Pine",SPHEROID["S_
104757 GCS_NAD_1983_HARN_Adj_MN_Pipestone GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Pipestone",DATUM["D_NAD_1983_HARN_Adj_MN_Pipestone",SPHE
104758 GCS_NAD_1983_HARN_Adj_MN_Polk GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Polk",DATUM["D_NAD_1983_HARN_Adj_MN_Polk",SPHEROID["S_G
104759 GCS_NAD_1983_HARN_Adj_MN_Pope GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Pope",DATUM["D_NAD_1983_HARN_Adj_MN_Pope",SPHEROID["S
104760 GCS_NAD_1983_HARN_Adj_MN_Ramsey GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Ramsey",DATUM["D_NAD_1983_HARN_Adj_MN_Ramsey",SPHERO
104761 GCS_NAD_1983_HARN_Adj_MN_Red_Lake GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Red_Lake",DATUM["D_NAD_1983_HARN_Adj_MN_Red_Lake",SPH
104762 GCS_NAD_1983_HARN_Adj_MN_Redwood GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Redwood",DATUM["D_NAD_1983_HARN_Adj_MN_Redwood",SPHE
104763 GCS_NAD_1983_HARN_Adj_MN_Renville GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Renville",DATUM["D_NAD_1983_HARN_Adj_MN_Renville",SPHERO
104764 GCS_NAD_1983_HARN_Adj_MN_Rice GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Rice",DATUM["D_NAD_1983_HARN_Adj_MN_Rice",SPHEROID["S_
104765 GCS_NAD_1983_HARN_Adj_MN_Rock GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Rock",DATUM["D_NAD_1983_HARN_Adj_MN_Rock",SPHEROID["S
104766 GCS_NAD_1983_HARN_Adj_MN_Roseau GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Roseau",DATUM["D_NAD_1983_HARN_Adj_MN_Roseau",SPHERO
104767 GCS_NAD_1983_HARN_Adj_MN_St_Louis_North GEOGCS["GCS_NAD_1983_HARN_Adj_MN_St_Louis_North",DATUM["D_NAD_1983_HARN_Adj_MN_St_Louis_N
104768 GCS_NAD_1983_HARN_Adj_MN_St_Louis_Central GEOGCS["GCS_NAD_1983_HARN_Adj_MN_St_Louis_Central",DATUM["D_NAD_1983_HARN_Adj_MN_St_Louis_
104769 GCS_NAD_1983_HARN_Adj_MN_St_Louis_South GEOGCS["GCS_NAD_1983_HARN_Adj_MN_St_Louis_South",DATUM["D_NAD_1983_HARN_Adj_MN_St_Louis_S
104770 GCS_NAD_1983_HARN_Adj_MN_Scott GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Scott",DATUM["D_NAD_1983_HARN_Adj_MN_Scott",SPHEROID["S
104771 GCS_NAD_1983_HARN_Adj_MN_Sherburne GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Sherburne",DATUM["D_NAD_1983_HARN_Adj_MN_Sherburne",SPH
104772 GCS_NAD_1983_HARN_Adj_MN_Sibley GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Sibley",DATUM["D_NAD_1983_HARN_Adj_MN_Sibley",SPHEROID["
104773 GCS_NAD_1983_HARN_Adj_MN_Stearns GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Stearns",DATUM["D_NAD_1983_HARN_Adj_MN_Stearns",SPHERO
104774 GCS_NAD_1983_HARN_Adj_MN_Steele GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Steele",DATUM["D_NAD_1983_HARN_Adj_MN_Steele",SPHEROID[
104775 GCS_NAD_1983_HARN_Adj_MN_Stevens GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Stevens",DATUM["D_NAD_1983_HARN_Adj_MN_Stevens",SPHERO
104776 GCS_NAD_1983_HARN_Adj_MN_Swift GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Swift",DATUM["D_NAD_1983_HARN_Adj_MN_Swift",SPHEROID["S_
104777 GCS_NAD_1983_HARN_Adj_MN_Todd GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Todd",DATUM["D_NAD_1983_HARN_Adj_MN_Todd",SPHEROID["S_
104778 GCS_NAD_1983_HARN_Adj_MN_Traverse GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Traverse",DATUM["D_NAD_1983_HARN_Adj_MN_Traverse",SPHER
104779 GCS_NAD_1983_HARN_Adj_MN_Wabasha GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Wabasha",DATUM["D_NAD_1983_HARN_Adj_MN_Wabasha",SPHE
104780 GCS_NAD_1983_HARN_Adj_MN_Wadena GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Wadena",DATUM["D_NAD_1983_HARN_Adj_MN_Wadena",SPHERO
104781 GCS_NAD_1983_HARN_Adj_MN_Waseca GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Waseca",DATUM["D_NAD_1983_HARN_Adj_MN_Waseca",SPHERO
104782 GCS_NAD_1983_HARN_Adj_MN_Watonwan GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Watonwan",DATUM["D_NAD_1983_HARN_Adj_MN_Watonwan",SPH
104783 GCS_NAD_1983_HARN_Adj_MN_Winona GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Winona",DATUM["D_NAD_1983_HARN_Adj_MN_Winona",SPHERO
104784 GCS_NAD_1983_HARN_Adj_MN_Wright GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Wright",DATUM["D_NAD_1983_HARN_Adj_MN_Wright",SPHEROID[
104785 GCS_NAD_1983_HARN_Adj_MN_Yellow_Medicine GEOGCS["GCS_NAD_1983_HARN_Adj_MN_Yellow_Medicine",DATUM["D_NAD_1983_HARN_Adj_MN_Yellow_M

104786 GCS_NAD_1983_HARN_Adj_MN_St_Louis GEOGCS["GCS_NAD_1983_HARN_Adj_MN_St_Louis",DATUM["D_NAD_1983_HARN_Adj_MN_St_Louis",SPHER

104900 GCS_Mercury_2000 GEOGCS["GCS_Mercury_2000",DATUM["D_Mercury_2000",SPHEROID["Mercury_2000_IAU_IAG",2439700.0,0.0]]
104901 GCS_Venus_1985 GEOGCS["GCS_Venus_1985",DATUM["D_Venus_1985",SPHEROID["Venus_1985_IAU_IAG_COSPAR",6051000.0
104902 GCS_Venus_2000 GEOGCS["GCS_Venus_2000",DATUM["D_Venus_2000",SPHEROID["Venus_2000_IAU_IAG",6051800.0,0.0]],PRIM
104903 GCS_Moon_2000 GEOGCS["GCS_Moon_2000",DATUM["D_Moon_2000",SPHEROID["Moon_2000_IAU_IAG",1737400.0,0.0]],PRIME
104904 GCS_Mars_1979 GEOGCS["GCS_Mars_1979",DATUM["D_Mars_1979",SPHEROID["Mars_1979_IAU_IAG",3393400.0,192.04301075
104905 GCS_Mars_2000 GEOGCS["GCS_Mars_2000",DATUM["D_Mars_2000",SPHEROID["Mars_2000_IAU_IAG",3396190.0,169.89444722
104906 GCS_Deimos_2000 GEOGCS["GCS_Deimos_2000",DATUM["D_Deimos_2000",SPHEROID["Deimos_2000_IAU_IAG",6200.0,0.0]],PRIM
104907 GCS_Phobos_2000 GEOGCS["GCS_Phobos_2000",DATUM["D_Phobos_2000",SPHEROID["Phobos_2000_IAU_IAG",11100.0,0.0]],PRI
104908 GCS_Jupiter_2000 GEOGCS["GCS_Jupiter_2000",DATUM["D_Jupiter_2000",SPHEROID["Jupiter_2000_IAU_IAG",71492000.0,15.414
104909 GCS_Adrastea_2000 GEOGCS["GCS_Adrastea_2000",DATUM["D_Adrastea_2000",SPHEROID["Adrastea_2000_IAU_IAG",8200.0,0.0]],
104910 GCS_Amalthea_2000 GEOGCS["GCS_Amalthea_2000",DATUM["D_Amalthea_2000",SPHEROID["Amalthea_2000_IAU_IAG",83500.0,0.0
104911 GCS_Ananke_2000 GEOGCS["GCS_Ananke_2000",DATUM["D_Ananke_2000",SPHEROID["Ananke_2000_IAU_IAG",10000.0,0.0]],PR
104912 GCS_Callisto_2000 GEOGCS["GCS_Callisto_2000",DATUM["D_Callisto_2000",SPHEROID["Callisto_2000_IAU_IAG",2409300.0,0.0]],P
104913 GCS_Carme_2000 GEOGCS["GCS_Carme_2000",DATUM["D_Carme_2000",SPHEROID["Carme_2000_IAU_IAG",15000.0,0.0]],PRIM
104914 GCS_Elara_2000 GEOGCS["GCS_Elara_2000",DATUM["D_Elara_2000",SPHEROID["Elara_2000_IAU_IAG",40000.0,0.0]],PRIMEM["
104915 GCS_Europa_2000 GEOGCS["GCS_Europa_2000",DATUM["D_Europa_2000",SPHEROID["Europa_2000_IAU_IAG",1562090.0,0.0]],P
104916 GCS_Ganymede_2000 GEOGCS["GCS_Ganymede_2000",DATUM["D_Ganymede_2000",SPHEROID["Ganymede_2000_IAU_IAG",263234
104917 GCS_Himalia_2000 GEOGCS["GCS_Himalia_2000",DATUM["D_Himalia_2000",SPHEROID["Himalia_2000_IAU_IAG",85000.0,0.0]],PRI
104918 GCS_Io_2000 GEOGCS["GCS_Io_2000",DATUM["D_Io_2000",SPHEROID["Io_2000_IAU_IAG",1821460.0,0.0]],PRIMEM["Referen
104919 GCS_Leda_2000 GEOGCS["GCS_Leda_2000",DATUM["D_Leda_2000",SPHEROID["Leda_2000_IAU_IAG",5000.0,0.0]],PRIMEM["R
104920 GCS_Lysithea_2000 GEOGCS["GCS_Lysithea_2000",DATUM["D_Lysithea_2000",SPHEROID["Lysithea_2000_IAU_IAG",12000.0,0.0]],P
104921 GCS_Metis_2000 GEOGCS["GCS_Metis_2000",DATUM["D_Metis_2000",SPHEROID["Metis_2000_IAU_IAG",30000.0,3.0]],PRIMEM["
104922 GCS_Pasiphae_2000 GEOGCS["GCS_Pasiphae_2000",DATUM["D_Pasiphae_2000",SPHEROID["Pasiphae_2000_IAU_IAG",18000.0,0.0
104923 GCS_Sinope_2000 GEOGCS["GCS_Sinope_2000",DATUM["D_Sinope_2000",SPHEROID["Sinope_2000_IAU_IAG",14000.0,0.0]],PRIM
104924 GCS_Thebe_2000 GEOGCS["GCS_Thebe_2000",DATUM["D_Thebe_2000",SPHEROID["Thebe_2000_IAU_IAG",49300.0,0.0]],PRIME
104925 GCS_Saturn_2000 GEOGCS["GCS_Saturn_2000",DATUM["D_Saturn_2000",SPHEROID["Saturn_2000_IAU_IAG",60268000.0,10.2079
104926 GCS_Atlas_2000 GEOGCS["GCS_Atlas_2000",DATUM["D_Atlas_2000",SPHEROID["Atlas_2000_IAU_IAG",16000.0,0.0]],PRIMEM["R
104927 GCS_Calypso_2000 GEOGCS["GCS_Calypso_2000",DATUM["D_Calypso_2000",SPHEROID["Calypso_2000_IAU_IAG",9500.0,0.0]],PR
104928 GCS_Dione_2000 GEOGCS["GCS_Dione_2000",DATUM["D_Dione_2000",SPHEROID["Dione_2000_IAU_IAG",560000.0,0.0]],PRIME
104929 GCS_Enceladus_2000 GEOGCS["GCS_Enceladus_2000",DATUM["D_Enceladus_2000",SPHEROID["Enceladus_2000_IAU_IAG",249400.
104930 GCS_Epimetheus_2000 GEOGCS["GCS_Epimetheus_2000",DATUM["D_Epimetheus_2000",SPHEROID["Epimetheus_2000_IAU_IAG",5950
104931 GCS_Helene_2000 GEOGCS["GCS_Helene_2000",DATUM["D_Helene_2000",SPHEROID["Helene_2000_IAU_IAG",16000.0,0.0]],PRIM
104932 GCS_Hyperion_2000 GEOGCS["GCS_Hyperion_2000",DATUM["D_Hyperion_2000",SPHEROID["Hyperion_2000_IAU_IAG",133000.0,0.0
104933 GCS_Iapetus_2000 GEOGCS["GCS_Iapetus_2000",DATUM["D_Iapetus_2000",SPHEROID["Iapetus_2000_IAU_IAG",718000.0,0.0]],PR
104934 GCS_Janus_2000 GEOGCS["GCS_Janus_2000",DATUM["D_Janus_2000",SPHEROID["Janus_2000_IAU_IAG",888000.0,0.0]],PRIME
104935 GCS_Mimas_2000 GEOGCS["GCS_Mimas_2000",DATUM["D_Mimas_2000",SPHEROID["Mimas_2000_IAU_IAG",1986300.0,0.0]],PRI
104936 GCS_Pan_2000 GEOGCS["GCS_Pan_2000",DATUM["D_Pan_2000",SPHEROID["Pan_2000_IAU_IAG",10000.0,0.0]],PRIMEM["Ref
104937 GCS_Pandora_2000 GEOGCS["GCS_Pandora_2000",DATUM["D_Pandora_2000",SPHEROID["Pandora_2000_IAU_IAG",41900.0,0.0]],P
104938 GCS_Phoebe_2000 GEOGCS["GCS_Phoebe_2000",DATUM["D_Phoebe_2000",SPHEROID["Phoebe_2000_IAU_IAG",110000.0,0.0]],P
104939 GCS_Prometheus_2000 GEOGCS["GCS_Prometheus_2000",DATUM["D_Prometheus_2000",SPHEROID["Prometheus_2000_IAU_IAG",501
104940 GCS_Rhea_2000 GEOGCS["GCS_Rhea_2000",DATUM["D_Rhea_2000",SPHEROID["Rhea_2000_IAU_IAG",764000.0,0.0]],PRIMEM
104941 GCS_Telesto_2000 GEOGCS["GCS_Telesto_2000",DATUM["D_Telesto_2000",SPHEROID["Telesto_2000_IAU_IAG",11000.0,0.0]],PRIM
104942 GCS_Tethys_2000 GEOGCS["GCS_Tethys_2000",DATUM["D_Tethys_2000",SPHEROID["Tethys_2000_IAU_IAG",529800.0,0.0]],PRIM
104943 GCS_Titan_2000 GEOGCS["GCS_Titan_2000",DATUM["D_Titan_2000",SPHEROID["Titan_2000_IAU_IAG",2575000.0,0.0]],PRIMEM
104944 GCS_Uranus_2000 GEOGCS["GCS_Uranus_2000",DATUM["D_Uranus_2000",SPHEROID["Uranus_2000_IAU_IAG",25559000.0,43.61
104945 GCS_Ariel_2000 GEOGCS["GCS_Ariel_2000",DATUM["D_Ariel_2000",SPHEROID["Ariel_2000_IAU_IAG",578900.0,0.0]],PRIMEM["R
104946 GCS_Belinda_2000 GEOGCS["GCS_Belinda_2000",DATUM["D_Belinda_2000",SPHEROID["Belinda_2000_IAU_IAG",33000.0,0.0]],PRI
104947 GCS_Bianca_2000 GEOGCS["GCS_Bianca_2000",DATUM["D_Bianca_2000",SPHEROID["Bianca_2000_IAU_IAG",21000.0,0.0]],PRIM
104948 GCS_Cordelia_2000 GEOGCS["GCS_Cordelia_2000",DATUM["D_Cordelia_2000",SPHEROID["Cordelia_2000_IAU_IAG",13000.0,0.0]],P
104949 GCS_Cressida_2000 GEOGCS["GCS_Cressida_2000",DATUM["D_Cressida_2000",SPHEROID["Cressida_2000_IAU_IAG",31000.0,0.0]]
104950 GCS_Desdemona_2000 GEOGCS["GCS_Desdemona_2000",DATUM["D_Desdemona_2000",SPHEROID["Desdemona_2000_IAU_IAG",270
104951 GCS_Juliet_2000 GEOGCS["GCS_Juliet_2000",DATUM["D_Juliet_2000",SPHEROID["Juliet_2000_IAU_IAG",42000.0,0.0]],PRIMEM["

104952 GCS_Miranda_2000 GEOGCS["GCS_Miranda_2000",DATUM["D_Miranda_2000",SPHEROID["Miranda_2000_IAU_IAG",235800.0,0.0]],P

104953 GCS_Oberon_2000 GEOGCS["GCS_Oberon_2000",DATUM["D_Oberon_2000",SPHEROID["Oberon_2000_IAU_IAG",761400.0,0.0]],PR
104954 GCS_Ophelia_2000 GEOGCS["GCS_Ophelia_2000",DATUM["D_Ophelia_2000",SPHEROID["Ophelia_2000_IAU_IAG",15000.0,0.0]],PR
104955 GCS_Portia_2000 GEOGCS["GCS_Portia_2000",DATUM["D_Portia_2000",SPHEROID["Portia_2000_IAU_IAG",54000.0,0.0]],PRIMEM
104956 GCS_Puck_2000 GEOGCS["GCS_Puck_2000",DATUM["D_Puck_2000",SPHEROID["Puck_2000_IAU_IAG",77000.0,0.0]],PRIMEM["R
104957 GCS_Rosalind_2000 GEOGCS["GCS_Rosalind_2000",DATUM["D_Rosalind_2000",SPHEROID["Rosalind_2000_IAU_IAG",27000.0,0.0]],
104958 GCS_Titania_2000 GEOGCS["GCS_Titania_2000",DATUM["D_Titania_2000",SPHEROID["Titania_2000_IAU_IAG",788900.0,0.0]],PRIM
104959 GCS_Umbriel_2000 GEOGCS["GCS_Umbriel_2000",DATUM["D_Umbriel_2000",SPHEROID["Umbriel_2000_IAU_IAG",584700.0,0.0]],P
104960 GCS_Neptune_2000 GEOGCS["GCS_Neptune_2000",DATUM["D_Neptune_2000",SPHEROID["Neptune_2000_IAU_IAG",24764000.0,58
104961 GCS_Despina_2000 GEOGCS["GCS_Despina_2000",DATUM["D_Despina_2000",SPHEROID["Despina_2000_IAU_IAG",74000.0,0.0]],P
104962 GCS_Galatea_2000 GEOGCS["GCS_Galatea_2000",DATUM["D_Galatea_2000",SPHEROID["Galatea_2000_IAU_IAG",79000.0,0.0]],PR
104963 GCS_Larissa_2000 GEOGCS["GCS_Larissa_2000",DATUM["D_Larissa_2000",SPHEROID["Larissa_2000_IAU_IAG",104000.0,6.93333
104964 GCS_Naiad_2000 GEOGCS["GCS_Naiad_2000",DATUM["D_Naiad_2000",SPHEROID["Naiad_2000_IAU_IAG",29000.0,0.0]],PRIMEM
104965 GCS_Nereid_2000 GEOGCS["GCS_Nereid_2000",DATUM["D_Nereid_2000",SPHEROID["Nereid_2000_IAU_IAG",170000.0,0.0]],PRIM
104966 GCS_Proteus_2000 GEOGCS["GCS_Proteus_2000",DATUM["D_Proteus_2000",SPHEROID["Proteus_2000_IAU_IAG",208000.0,0.0]],P
104967 GCS_Thalassa_2000 GEOGCS["GCS_Thalassa_2000",DATUM["D_Thalassa_2000",SPHEROID["Thalassa_2000_IAU_IAG",40000.0,0.0]
104968 GCS_Triton_2000 GEOGCS["GCS_Triton_2000",DATUM["D_Triton_2000",SPHEROID["Triton_2000_IAU_IAG",1352600.0,0.0]],PRIME
104969 GCS_Pluto_2000 GEOGCS["GCS_Pluto_2000",DATUM["D_Pluto_2000",SPHEROID["Pluto_2000_IAU_IAG",1195000.0,0.0]],PRIMEM
104970 GCS_Charon_2000 GEOGCS["GCS_Charon_2000",DATUM["D_Charon_2000",SPHEROID["Charon_2000_IAU_IAG",593000.0,0.0]],PR
104990 GCS_HD1909 GEOGCS["GCS_HD1909",DATUM["D_Hungarian_Datum_1909",SPHEROID["Bessel_1841",6377397.155,299.1528
104991 GCS_IGRS GEOGCS["GCS_IGRS",DATUM["D_Iraqi_Geospatial_Reference_System",SPHEROID["GRS_1980",6378137.0,298
104992 GCS_MGI_1901 GEOGCS["GCS_MGI_1901",DATUM["D_MGI_1901",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIM
Related topics
Spatial references


So many projected coordinate systems are supported now that one web page is no longer enough. So this is page one of two. For Part 2
of the projected coordinate systems list, see Projected coordinate systemsPart 2.

known
ID
(WKID)
2000 Anguilla_1957_British_West_Indies_Grid PROJCS["Anguilla_1957_British_West_Indies_Grid",GEOGCS["GCS_Anguilla_1957",DATUM["D_Ang
2001 Antigua_1943_British_West_Indies_Grid PROJCS["Antigua_1943_British_West_Indies_Grid",GEOGCS["GCS_Antigua_1943",DATUM["D_Antig
2002 Dominica_1945_British_West_Indies_Grid PROJCS["Dominica_1945_British_West_Indies_Grid",GEOGCS["GCS_Dominica_1945",DATUM["D_D
2003 Grenada_1953_British_West_Indies_Grid PROJCS["Grenada_1953_British_West_Indies_Grid",GEOGCS["GCS_Grenada_1953",DATUM["D_Gr
2004 Montserrat_1958_British_West_Indies_Grid PROJCS["Montserrat_1958_British_West_Indies_Grid",GEOGCS["GCS_Montserrat_1958",DATUM["D
2005 St_Kitts_1955_British_West_Indies_Grid PROJCS["St_Kitts_1955_British_West_Indies_Grid",GEOGCS["GCS_St_Kitts_1955",DATUM["D_St_K
2006 St_Lucia_1955_British_West_Indies_Grid PROJCS["St_Lucia_1955_British_West_Indies_Grid",GEOGCS["GCS_St_Lucia_1955",DATUM["D_St
2007 St_Vincent_1945_British_West_Indies_Grid PROJCS["St_Vincent_1945_British_West_Indies_Grid",GEOGCS["GCS_St_Vincent_1945",DATUM["D
2008 NAD_1927_CGQ77_MTM_2_SCoPQ PROJCS["NAD_1927_CGQ77_MTM_2_SCoPQ",GEOGCS["GCS_NAD_1927_CGQ77",DATUM["D_N
2016 NAD_1927_CGQ77_MTM_10_SCoPQ PROJCS["NAD_1927_CGQ77_MTM_10_SCoPQ",GEOGCS["GCS_NAD_1927_CGQ77",DATUM["D_
2017 NAD_1927_DEF_1976_MTM_8 PROJCS["NAD_1927_DEF_1976_MTM_8",GEOGCS["GCS_NAD_1927_Definition_1976",DATUM["D_
2018 NAD_1927_DEF_1976_MTM_9 PROJCS["NAD_1927_DEF_1976_MTM_9",GEOGCS["GCS_NAD_1927_Definition_1976",DATUM["D_
2019 NAD_1927_DEF_1976_MTM_10 PROJCS["NAD_1927_DEF_1976_MTM_10",GEOGCS["GCS_NAD_1927_Definition_1976",DATUM["D
2027 NAD_1927_DEF_1976_UTM_Zone_15N PROJCS["NAD_1927_DEF_1976_UTM_Zone_15N",GEOGCS["GCS_NAD_1927_Definition_1976",DA
2031 NAD_1927_CGQ77_UTM_Zone_17N PROJCS["NAD_1927_CGQ77_UTM_Zone_17N",GEOGCS["GCS_NAD_1927_CGQ77",DATUM["D_N
2036 NAD_1983_CSRS_New_Brunswick_Stereographic PROJCS["NAD_1983_CSRS_New_Brunswick_Stereographic",GEOGCS["GCS_North_American_198
2037 NAD_1983_CSRS_UTM_Zone_19N PROJCS["NAD_1983_CSRS_UTM_Zone_19N",GEOGCS["GCS_North_American_1983_CSRS",DATU
2039 Israel_TM_Grid PROJCS["Israel_TM_Grid",GEOGCS["GCS_Israel",DATUM["D_Israel",SPHEROID["GRS_1980",63781
2040 Locodjo_1965_UTM_Zone_30N PROJCS["Locodjo_1965_UTM_Zone_30N",GEOGCS["GCS_Locodjo_1965",DATUM["D_Locodjo_196
2041 Abidjan_1987_UTM_Zone_30N PROJCS["Abidjan_1987_UTM_Zone_30N",GEOGCS["GCS_Abidjan_1987",DATUM["D_Abidjan_1987
2042 Locodjo_1965_UTM_Zone_29N PROJCS["Locodjo_1965_UTM_Zone_29N",GEOGCS["GCS_Locodjo_1965",DATUM["D_Locodjo_196
2043 Abidjan_1987_UTM_Zone_29N PROJCS["Abidjan_1987_UTM_Zone_29N",GEOGCS["GCS_Abidjan_1987",DATUM["D_Abidjan_1987
2044 Hanoi_1972_GK_Zone_18 PROJCS["Hanoi_1972_GK_Zone_18",GEOGCS["GCS_Hanoi_1972",DATUM["D_Hanoi_1972",SPHER
2045 Hanoi_1972_GK_Zone_19 PROJCS["Hanoi_1972_GK_Zone_19",GEOGCS["GCS_Hanoi_1972",DATUM["D_Hanoi_1972",SPHER
2056 CH1903+_LV95 PROJCS["CH1903+_LV95",GEOGCS["GCS_CH1903+",DATUM["D_CH1903+",SPHEROID["Bessel_1

2057 Rassadiran_Nakhl_e_Taqi PROJCS["Rassadiran_Nakhl_e_Taqi",GEOGCS["GCS_Rassadiran",DATUM["D_Rassadiran",SPHERO

2058 ED_1950_ED77_UTM_Zone_38N PROJCS["ED_1950_ED77_UTM_Zone_38N",GEOGCS["GCS_European_1950_ED77",DATUM["D_Eu
2062 Madrid_1870_Madrid_Spain PROJCS["Madrid_1870_Madrid_Spain",GEOGCS["GCS_Madrid_1870_Madrid",DATUM["D_Madrid_1
2063 Dabola_1981_UTM_Zone_28N PROJCS["Dabola_1981_UTM_Zone_28N",GEOGCS["GCS_Dabola_1981",DATUM["D_Dabola_1981"
2065 S-JTSK_Ferro_Krovak PROJCS["S-JTSK_Ferro_Krovak",GEOGCS["GCS_S_JTSK_Ferro",DATUM["D_S_JTSK",SPHEROID
2066 Mount_Dillon_Tobago_Grid PROJCS["Mount_Dillon_Tobago_Grid",GEOGCS["GCS_Mount_Dillon",DATUM["D_Mount_Dillon",SPH
2067 Naparima_1955_UTM_Zone_20N PROJCS["Naparima_1955_UTM_Zone_20N",GEOGCS["GCS_Naparima_1955",DATUM["D_Naparima
2068 ELD_1979_Libya_5 PROJCS["ELD_1979_Libya_5",GEOGCS["GCS_European_Libyan_Datum_1979",DATUM["D_Europe
2073 ELD_1979_Libya_10 PROJCS["ELD_1979_Libya_10",GEOGCS["GCS_European_Libyan_Datum_1979",DATUM["D_Europ
2077 ELD_1979_UTM_Zone_32N PROJCS["ELD_1979_UTM_Zone_32N",GEOGCS["GCS_European_Libyan_Datum_1979",DATUM["D
2081 Chos_Malal_1914_Argentina_2 PROJCS["Chos_Malal_1914_Argentina_2",GEOGCS["GCS_Chos_Malal_1914",DATUM["D_Chos_Ma
2082 Pampa_del_Castillo_Argentina_2 PROJCS["Pampa_del_Castillo_Argentina_2",GEOGCS["GCS_Pampa_del_Castillo",DATUM["D_Pamp
2083 Hito_XVIII_1963_Argentina_2 PROJCS["Hito_XVIII_1963_Argentina_2",GEOGCS["GCS_Hito_XVIII_1963",DATUM["D_Hito_XVIII_1
2084 Hito_XVIII_1963_UTM_19S PROJCS["Hito_XVIII_1963_UTM_19S",GEOGCS["GCS_Hito_XVIII_1963",DATUM["D_Hito_XVIII_196
2085 NAD_1927_Cuba_Norte PROJCS["NAD_1927_Cuba_Norte",GEOGCS["GCS_North_American_1927",DATUM["D_North_Amer
2086 NAD_1927_Cuba_Sur PROJCS["NAD_1927_Cuba_Sur",GEOGCS["GCS_North_American_1927",DATUM["D_North_America
2087 ELD_1979_TM_12_NE PROJCS["ELD_1979_TM_12_NE",GEOGCS["GCS_European_Libyan_Datum_1979",DATUM["D_Euro
2088 Carthage_TM_11_NE PROJCS["Carthage_TM_11_NE",GEOGCS["GCS_Carthage",DATUM["D_Carthage",SPHEROID["Clar
2089 Yemen_NGN_1996_UTM_Zone_38N PROJCS["Yemen_NGN_1996_UTM_Zone_38N",GEOGCS["GCS_Yemen_NGN_1996",DATUM["D_Ye
2091 South_Yemen_GK_Zone_8 PROJCS["South_Yemen_GK_Zone_8",GEOGCS["GCS_South_Yemen",DATUM["D_South_Yemen",SP
2093 Hanoi_1972_GK_106_NE PROJCS["Hanoi_1972_GK_106_NE",GEOGCS["GCS_Hanoi_1972",DATUM["D_Hanoi_1972",SPHER
2094 WGS_1972_BE_TM_106_NE PROJCS["WGS_1972_BE_TM_106_NE",GEOGCS["GCS_WGS_1972_BE",DATUM["D_WGS_1972_B
2095 Bissau_UTM_Zone_28N PROJCS["Bissau_UTM_Zone_28N",GEOGCS["GCS_Bissau",DATUM["D_Bissau",SPHEROID["Interna
2096 Korean_1985_Korea_East_Belt PROJCS["Korean_1985_Korea_East_Belt",GEOGCS["GCS_Korean_Datum_1985",DATUM["D_Korea
2097 Korean_1985_Korea_Central_Belt PROJCS["Korean_1985_Korea_Central_Belt",GEOGCS["GCS_Korean_Datum_1985",DATUM["D_Kor
2098 Korean_1985_Korea_West_Belt PROJCS["Korean_1985_Korea_West_Belt",GEOGCS["GCS_Korean_Datum_1985",DATUM["D_Korea
2099 Qatar_1948_Qatar_Grid PROJCS["Qatar_1948_Qatar_Grid",GEOGCS["GCS_Qatar_1948",DATUM["D_Qatar_1948",SPHERO
2100 Greek_Grid PROJCS["Greek_Grid",GEOGCS["GCS_GGRS_1987",DATUM["D_GGRS_1987",SPHEROID["GRS_1
2101 Lake_Maracaibo_Grid_M1 PROJCS["Lake_Maracaibo_Grid_M1",GEOGCS["GCS_Lake",DATUM["D_Lake",SPHEROID["Internati
2102 Lake_Maracaibo_Grid PROJCS["Lake_Maracaibo_Grid",GEOGCS["GCS_Lake",DATUM["D_Lake",SPHEROID["International
2103 Lake_Maracaibo_Grid_M3 PROJCS["Lake_Maracaibo_Grid_M3",GEOGCS["GCS_Lake",DATUM["D_Lake",SPHEROID["Internati
2104 Lake_Maracaibo_La_Rosa_Grid PROJCS["Lake_Maracaibo_La_Rosa_Grid",GEOGCS["GCS_Lake",DATUM["D_Lake",SPHEROID["Int
2105 NZGD_2000_Mount_Eden_Circuit PROJCS["NZGD_2000_Mount_Eden_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2106 NZGD_2000_Bay_of_Plenty_Circuit PROJCS["NZGD_2000_Bay_of_Plenty_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_20
2107 NZGD_2000_Poverty_Bay_Circuit PROJCS["NZGD_2000_Poverty_Bay_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2108 NZGD_2000_Hawkes_Bay_Circuit PROJCS["NZGD_2000_Hawkes_Bay_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2109 NZGD_2000_Taranaki_Circuit PROJCS["NZGD_2000_Taranaki_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SP
2110 NZGD_2000_Tuhirangi_Circuit PROJCS["NZGD_2000_Tuhirangi_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",S

2111 NZGD_2000_Wanganui_Circuit PROJCS["NZGD_2000_Wanganui_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",S

2112 NZGD_2000_Wairarapa_Circuit PROJCS["NZGD_2000_Wairarapa_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",S
2113 NZGD_2000_Wellington_Circuit PROJCS["NZGD_2000_Wellington_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",S
2114 NZGD_2000_Collingwood_Circuit PROJCS["NZGD_2000_Collingwood_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2115 NZGD_2000_Nelson_Circuit PROJCS["NZGD_2000_Nelson_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPH
2116 NZGD_2000_Karamea_Circuit PROJCS["NZGD_2000_Karamea_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",S
2117 NZGD_2000_Buller_Circuit PROJCS["NZGD_2000_Buller_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPHE
2118 NZGD_2000_Grey_Circuit PROJCS["NZGD_2000_Grey_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPHE
2119 NZGD_2000_Amuri_Circuit PROJCS["NZGD_2000_Amuri_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPH
2120 NZGD_2000_Marlborough_Circuit PROJCS["NZGD_2000_Marlborough_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2121 NZGD_2000_Hokitika_Circuit PROJCS["NZGD_2000_Hokitika_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SP
2122 NZGD_2000_Okarito_Circuit PROJCS["NZGD_2000_Okarito_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPH
2123 NZGD_2000_Jacksons_Bay_Circuit PROJCS["NZGD_2000_Jacksons_Bay_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_20
2124 NZGD_2000_Mount_Pleasant_Circuit PROJCS["NZGD_2000_Mount_Pleasant_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2
2125 NZGD_2000_Gawler_Circuit PROJCS["NZGD_2000_Gawler_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPH
2126 NZGD_2000_Timaru_Circuit PROJCS["NZGD_2000_Timaru_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPH
2127 NZGD_2000_Lindis_Peak_Circuit PROJCS["NZGD_2000_Lindis_Peak_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2128 NZGD_2000_Mount_Nicholas_Circuit PROJCS["NZGD_2000_Mount_Nicholas_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2
2129 NZGD_2000_Mount_York_Circuit PROJCS["NZGD_2000_Mount_York_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2130 NZGD_2000_Observation_Point_Circuit PROJCS["NZGD_2000_Observation_Point_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD
2131 NZGD_2000_North_Taieri_Circuit PROJCS["NZGD_2000_North_Taieri_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000
2132 NZGD_2000_Bluff_Circuit PROJCS["NZGD_2000_Bluff_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SPHE
2133 NZGD_2000_UTM_Zone_58S PROJCS["NZGD_2000_UTM_Zone_58S",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2000",SP
2136 Accra_Ghana_Grid PROJCS["Accra_Ghana_Grid",GEOGCS["GCS_Accra",DATUM["D_Accra",SPHEROID["War_Office",6
2137 Accra_TM_1_NW PROJCS["Accra_TM_1_NW",GEOGCS["GCS_Accra",DATUM["D_Accra",SPHEROID["War_Office",63
2138 NAD_1927_CGQ77_Quebec_Lambert PROJCS["NAD_1927_CGQ77_Quebec_Lambert",GEOGCS["GCS_NAD_1927_CGQ77",DATUM["D_N
2139 NAD_1983_CSRS_MTM_2_SCoPQ PROJCS["NAD_1983_CSRS_MTM_2_SCoPQ",GEOGCS["GCS_North_American_1983_CSRS",DATU
2140 NAD_1983_CSRS_MTM_3 PROJCS["NAD_1983_CSRS_MTM_3",GEOGCS["GCS_North_American_1983_CSRS",DATUM["D_N
2147 NAD_1983_CSRS_MTM_10 PROJCS["NAD_1983_CSRS_MTM_10",GEOGCS["GCS_North_American_1983_CSRS",DATUM["D_
2154 RGF_1993_Lambert_93 PROJCS["RGF_1993_Lambert_93",GEOGCS["GCS_RGF_1993",DATUM["D_RGF_1993",SPHEROID
2155 Samoa_1962_Samoa_Lambert PROJCS["Samoa_1962_Samoa_Lambert",GEOGCS["GCS_American_Samoa_1962",DATUM["D_Am
2157 IRENET95_Irish_Transverse_Mercator PROJCS["IRENET95_Irish_Transverse_Mercator",GEOGCS["GCS_IRENET95",DATUM["D_IRENET9
2158 IRENET95_UTM_Zone_29N PROJCS["IRENET95_UTM_Zone_29N",GEOGCS["GCS_IRENET95",DATUM["D_IRENET95",SPHER
2159 Sierra_Leone_1924_New_Colony_Grid PROJCS["Sierra_Leone_1924_New_Colony_Grid",GEOGCS["GCS_Sierra_Leone_1924",DATUM["D_
2160 Sierra_Leone_1924_New_War_Office_Grid PROJCS["Sierra_Leone_1924_New_War_Office_Grid",GEOGCS["GCS_Sierra_Leone_1924",DATUM
2161 Sierra_Leone_1968_UTM_Zone_28N PROJCS["Sierra_Leone_1968_UTM_Zone_28N",GEOGCS["GCS_Sierra_Leone_1968",DATUM["D_S
2162 Sierra_Leone_1968_UTM_Zone_29N PROJCS["Sierra_Leone_1968_UTM_Zone_29N",GEOGCS["GCS_Sierra_Leone_1968",DATUM["D_S
2163 US_National_Atlas_Equal_Area PROJCS["US_National_Atlas_Equal_Area",GEOGCS["GCS_Sphere_Clarke_1866_Authalic",DATUM[
2164 Locodjo_1965_TM_5_NW PROJCS["Locodjo_1965_TM_5_NW",GEOGCS["GCS_Locodjo_1965",DATUM["D_Locodjo_1965",SP
2165 Abidjan_1987_TM_5_NW PROJCS["Abidjan_1987_TM_5_NW",GEOGCS["GCS_Abidjan_1987",DATUM["D_Abidjan_1987",SPH

2166 Pulkovo_1942_Adj_1983_3_Degree_GK_Zone_3 PROJCS["Pulkovo_1942_Adj_1983_3_Degree_GK_Zone_3",GEOGCS["GCS_Pulkovo_1942_Adj_198

2169 Luxembourg_1930_Gauss PROJCS["Luxembourg_1930_Gauss",GEOGCS["GCS_Luxembourg_1930",DATUM["D_Luxembourg_
2170 MGI_Slovenia_Grid PROJCS["MGI_Slovenia_Grid",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Bessel_1841",63
2172 Pulkovo_1942_Adj_1958_Poland_Zone_II PROJCS["Pulkovo_1942_Adj_1958_Poland_Zone_II",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DAT
2173 Pulkovo_1942_Adj_1958_Poland_Zone_III PROJCS["Pulkovo_1942_Adj_1958_Poland_Zone_III",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DAT
2174 Pulkovo_1942_Adj_1958_Poland_Zone_IV PROJCS["Pulkovo_1942_Adj_1958_Poland_Zone_IV",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DA
2175 Pulkovo_1942_Adj_1958_Poland_Zone_V PROJCS["Pulkovo_1942_Adj_1958_Poland_Zone_V",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DAT
2176 ETRS_1989_Poland_CS2000_Zone_5 PROJCS["ETRS_1989_Poland_CS2000_Zone_5",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1
2180 ETRS_1989_Poland_CS92 PROJCS["ETRS_1989_Poland_CS92",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHE
2181 ED_1950_Turkey_9 PROJCS["ED_1950_Turkey_9",GEOGCS["GCS_European_1950",DATUM["D_European_1950",SPHE
2182 ED_1950_Turkey_10 PROJCS["ED_1950_Turkey_10",GEOGCS["GCS_European_1950",DATUM["D_European_1950",SPH
2188 Azores_Occidental_1939_UTM_Zone_25N PROJCS["Azores_Occidental_1939_UTM_Zone_25N",GEOGCS["GCS_Azores_Occidental_1939",DA
2189 Azores_Central_1948_UTM_Zone_26N PROJCS["Azores_Central_1948_UTM_Zone_26N",GEOGCS["GCS_Azores_Central_1948",DATUM["D
2190 Azores_Oriental_1940_UTM_Zone_26N PROJCS["Azores_Oriental_1940_UTM_Zone_26N",GEOGCS["GCS_Azores_Oriental_1940",DATUM[
2191 Madeira_1936_UTM_Zone_28N PROJCS["Madeira_1936_UTM_Zone_28N",GEOGCS["GCS_Madeira_1936",DATUM["D_Madeira_193
2192 ED_1950_France_EuroLambert PROJCS["ED_1950_France_EuroLambert",GEOGCS["GCS_European_1950",DATUM["D_European_
2193 NZGD_2000_New_Zealand_Transverse_Mercator PROJCS["NZGD_2000_New_Zealand_Transverse_Mercator",GEOGCS["GCS_NZGD_2000",DATUM[
2195 NAD_1983_HARN_UTM_Zone_2S PROJCS["NAD_1983_HARN_UTM_Zone_2S",GEOGCS["GCS_North_American_1983_HARN",DATU
2196 ETRS_1989_Kp2000_Jutland PROJCS["ETRS_1989_Kp2000_Jutland",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SP
2197 ETRS_1989_Kp2000_Zealand PROJCS["ETRS_1989_Kp2000_Zealand",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SP
2198 ETRS_1989_Kp2000_Bornholm PROJCS["ETRS_1989_Kp2000_Bornholm",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",S
2200 ATS_1977_New_Brunswick_Stereographic PROJCS["ATS_1977_New_Brunswick_Stereographic",GEOGCS["GCS_ATS_1977",DATUM["D_ATS_
2201 REGVEN_UTM_Zone_18N PROJCS["REGVEN_UTM_Zone_18N",GEOGCS["GCS_REGVEN",DATUM["D_REGVEN",SPHEROID
2204 NAD_1927_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1927_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_North_American_1927",D
2205 NAD_1983_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_North_American_19
2206 ED_1950_3_Degree_GK_Zone_9 PROJCS["ED_1950_3_Degree_GK_Zone_9",GEOGCS["GCS_European_1950",DATUM["D_European
2207 ED_1950_3_Degree_GK_Zone_10 PROJCS["ED_1950_3_Degree_GK_Zone_10",GEOGCS["GCS_European_1950",DATUM["D_Europea
2213 ETRS_1989_TM_30_NE PROJCS["ETRS_1989_TM_30_NE",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHERO
2214 Douala_1948_AEF_West PROJCS["Douala_1948_AEF_West",GEOGCS["GCS_Douala_1948",DATUM["D_Douala_1948",SPHE
2215 Manoca_1962_UTM_Zone_32N PROJCS["Manoca_1962_UTM_Zone_32N",GEOGCS["GCS_Manoca_1962",DATUM["D_Manoca_196
2216 Qornoq_1927_UTM_Zone_22N PROJCS["Qornoq_1927_UTM_Zone_22N",GEOGCS["GCS_Qornoq_1927",DATUM["D_Qornoq_1927
2217 Qornoq_1927_UTM_Zone_23N PROJCS["Qornoq_1927_UTM_Zone_23N",GEOGCS["GCS_Qornoq_1927",DATUM["D_Qornoq_1927
2219 ATS_1977_UTM_Zone_19N PROJCS["ATS_1977_UTM_Zone_19N",GEOGCS["GCS_ATS_1977",DATUM["D_ATS_1977",SPHERO
2220 ATS_1977_UTM_Zone_20N PROJCS["ATS_1977_UTM_Zone_20N",GEOGCS["GCS_ATS_1977",DATUM["D_ATS_1977",SPHERO
2222 NAD_1983_StatePlane_Arizona_East_FIPS_0201_Feet_Intl PROJCS["NAD_1983_StatePlane_Arizona_East_FIPS_0201_Feet_Intl",GEOGCS["GCS_North_Amer
2223 NAD_1983_StatePlane_Arizona_Central_FIPS_0202_Feet_Intl PROJCS["NAD_1983_StatePlane_Arizona_Central_FIPS_0202_Feet_Intl",GEOGCS["GCS_North_Am
2224 NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet_Intl PROJCS["NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet_Intl",GEOGCS["GCS_North_Ame

2225 NAD_1983_StatePlane_California_I_FIPS_0401_Feet PROJCS["NAD_1983_StatePlane_California_I_FIPS_0401_Feet",GEOGCS["GCS_North_American_1

2226 NAD_1983_StatePlane_California_II_FIPS_0402_Feet PROJCS["NAD_1983_StatePlane_California_II_FIPS_0402_Feet",GEOGCS["GCS_North_American_
2227 NAD_1983_StatePlane_California_III_FIPS_0403_Feet PROJCS["NAD_1983_StatePlane_California_III_FIPS_0403_Feet",GEOGCS["GCS_North_American_
2228 NAD_1983_StatePlane_California_IV_FIPS_0404_Feet PROJCS["NAD_1983_StatePlane_California_IV_FIPS_0404_Feet",GEOGCS["GCS_North_American_
2229 NAD_1983_StatePlane_California_V_FIPS_0405_Feet PROJCS["NAD_1983_StatePlane_California_V_FIPS_0405_Feet",GEOGCS["GCS_North_American_
2230 NAD_1983_StatePlane_California_VI_FIPS_0406_Feet PROJCS["NAD_1983_StatePlane_California_VI_FIPS_0406_Feet",GEOGCS["GCS_North_American_
2231 NAD_1983_StatePlane_Colorado_North_FIPS_0501_Feet PROJCS["NAD_1983_StatePlane_Colorado_North_FIPS_0501_Feet",GEOGCS["GCS_North_Americ
2232 NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet PROJCS["NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet",GEOGCS["GCS_North_Amer
2233 NAD_1983_StatePlane_Colorado_South_FIPS_0503_Feet PROJCS["NAD_1983_StatePlane_Colorado_South_FIPS_0503_Feet",GEOGCS["GCS_North_Americ
2234 NAD_1983_StatePlane_Connecticut_FIPS_0600_Feet PROJCS["NAD_1983_StatePlane_Connecticut_FIPS_0600_Feet",GEOGCS["GCS_North_American_1
2235 NAD_1983_StatePlane_Delaware_FIPS_0700_Feet PROJCS["NAD_1983_StatePlane_Delaware_FIPS_0700_Feet",GEOGCS["GCS_North_American_19
2236 NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet PROJCS["NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet",GEOGCS["GCS_North_American_
2237 NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet PROJCS["NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet",GEOGCS["GCS_North_American
2238 NAD_1983_StatePlane_Florida_North_FIPS_0903_Feet PROJCS["NAD_1983_StatePlane_Florida_North_FIPS_0903_Feet",GEOGCS["GCS_North_American
2239 NAD_1983_StatePlane_Georgia_East_FIPS_1001_Feet PROJCS["NAD_1983_StatePlane_Georgia_East_FIPS_1001_Feet",GEOGCS["GCS_North_American
2240 NAD_1983_StatePlane_Georgia_West_FIPS_1002_Feet PROJCS["NAD_1983_StatePlane_Georgia_West_FIPS_1002_Feet",GEOGCS["GCS_North_American
2241 NAD_1983_StatePlane_Idaho_East_FIPS_1101_Feet PROJCS["NAD_1983_StatePlane_Idaho_East_FIPS_1101_Feet",GEOGCS["GCS_North_American_1
2242 NAD_1983_StatePlane_Idaho_Central_FIPS_1102_Feet PROJCS["NAD_1983_StatePlane_Idaho_Central_FIPS_1102_Feet",GEOGCS["GCS_North_American
2243 NAD_1983_StatePlane_Idaho_West_FIPS_1103_Feet PROJCS["NAD_1983_StatePlane_Idaho_West_FIPS_1103_Feet",GEOGCS["GCS_North_American_1
2244 NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet PROJCS["NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet",GEOGCS["GCS_North_American_
2245 NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet PROJCS["NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet",GEOGCS["GCS_North_American
2246 NAD_1983_StatePlane_Kentucky_North_FIPS_1601_Feet PROJCS["NAD_1983_StatePlane_Kentucky_North_FIPS_1601_Feet",GEOGCS["GCS_North_Americ
2247 NAD_1983_StatePlane_Kentucky_South_FIPS_1602_Feet PROJCS["NAD_1983_StatePlane_Kentucky_South_FIPS_1602_Feet",GEOGCS["GCS_North_Americ
2248 NAD_1983_StatePlane_Maryland_FIPS_1900_Feet PROJCS["NAD_1983_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_American_198
2249 NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet PROJCS["NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet",GEOGCS["GCS_Nort
2250 NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002_Feet PROJCS["NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002_Feet",GEOGCS["GCS_North_A
2251 NAD_1983_StatePlane_Michigan_North_FIPS_2111_Feet_Intl PROJCS["NAD_1983_StatePlane_Michigan_North_FIPS_2111_Feet_Intl",GEOGCS["GCS_North_Am
2252 NAD_1983_StatePlane_Michigan_Central_FIPS_2112_Feet_Intl PROJCS["NAD_1983_StatePlane_Michigan_Central_FIPS_2112_Feet_Intl",GEOGCS["GCS_North_A
2253 NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl PROJCS["NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl",GEOGCS["GCS_North_Am
2254 NAD_1983_StatePlane_Mississippi_East_FIPS_2301_Feet PROJCS["NAD_1983_StatePlane_Mississippi_East_FIPS_2301_Feet",GEOGCS["GCS_North_Americ
2255 NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet PROJCS["NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet",GEOGCS["GCS_North_Ameri
2256 NAD_1983_StatePlane_Montana_FIPS_2500_Feet_Intl PROJCS["NAD_1983_StatePlane_Montana_FIPS_2500_Feet_Intl",GEOGCS["GCS_North_American_
2257 NAD_1983_StatePlane_New_Mexico_East_FIPS_3001_Feet PROJCS["NAD_1983_StatePlane_New_Mexico_East_FIPS_3001_Feet",GEOGCS["GCS_North_Ame
2258 NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002_Feet PROJCS["NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002_Feet",GEOGCS["GCS_North_A
2259 NAD_1983_StatePlane_New_Mexico_West_FIPS_3003_Feet PROJCS["NAD_1983_StatePlane_New_Mexico_West_FIPS_3003_Feet",GEOGCS["GCS_North_Ame
2260 NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet PROJCS["NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet",GEOGCS["GCS_North_Americ
2261 NAD_1983_StatePlane_New_York_Central_FIPS_3102_Feet PROJCS["NAD_1983_StatePlane_New_York_Central_FIPS_3102_Feet",GEOGCS["GCS_North_Ame
2262 NAD_1983_StatePlane_New_York_West_FIPS_3103_Feet PROJCS["NAD_1983_StatePlane_New_York_West_FIPS_3103_Feet",GEOGCS["GCS_North_Americ
2263 NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet PROJCS["NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet",GEOGCS["GCS_North_
2264 NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet PROJCS["NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet",GEOGCS["GCS_North_America
2265 NAD_1983_StatePlane_North_Dakota_North_FIPS_3301_Feet_Intl PROJCS["NAD_1983_StatePlane_North_Dakota_North_FIPS_3301_Feet_Intl",GEOGCS["GCS_North
2266 NAD_1983_StatePlane_North_Dakota_South_FIPS_3302_Feet_Intl PROJCS["NAD_1983_StatePlane_North_Dakota_South_FIPS_3302_Feet_Intl",GEOGCS["GCS_Nort
2267 NAD_1983_StatePlane_Oklahoma_North_FIPS_3501_Feet PROJCS["NAD_1983_StatePlane_Oklahoma_North_FIPS_3501_Feet",GEOGCS["GCS_North_Ameri
2268 NAD_1983_StatePlane_Oklahoma_South_FIPS_3502_Feet PROJCS["NAD_1983_StatePlane_Oklahoma_South_FIPS_3502_Feet",GEOGCS["GCS_North_Amer
2269 NAD_1983_StatePlane_Oregon_North_FIPS_3601_Feet_Intl PROJCS["NAD_1983_StatePlane_Oregon_North_FIPS_3601_Feet_Intl",GEOGCS["GCS_North_Ame
2270 NAD_1983_StatePlane_Oregon_South_FIPS_3602_Feet_Intl PROJCS["NAD_1983_StatePlane_Oregon_South_FIPS_3602_Feet_Intl",GEOGCS["GCS_North_Ame
2271 NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet PROJCS["NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet",GEOGCS["GCS_North_Am
2272 NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702_Feet PROJCS["NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702_Feet",GEOGCS["GCS_North_Am
2273 NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet_Intl PROJCS["NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet_Intl",GEOGCS["GCS_North_Am
2274 NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet PROJCS["NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet",GEOGCS["GCS_North_American_1
2275 NAD_1983_StatePlane_Texas_North_FIPS_4201_Feet PROJCS["NAD_1983_StatePlane_Texas_North_FIPS_4201_Feet",GEOGCS["GCS_North_American_
2276 NAD_1983_StatePlane_Texas_North_Central_FIPS_4202_Feet PROJCS["NAD_1983_StatePlane_Texas_North_Central_FIPS_4202_Feet",GEOGCS["GCS_North_Am
2277 NAD_1983_StatePlane_Texas_Central_FIPS_4203_Feet PROJCS["NAD_1983_StatePlane_Texas_Central_FIPS_4203_Feet",GEOGCS["GCS_North_American
2278 NAD_1983_StatePlane_Texas_South_Central_FIPS_4204_Feet PROJCS["NAD_1983_StatePlane_Texas_South_Central_FIPS_4204_Feet",GEOGCS["GCS_North_A

2279 NAD_1983_StatePlane_Texas_South_FIPS_4205_Feet PROJCS["NAD_1983_StatePlane_Texas_South_FIPS_4205_Feet",GEOGCS["GCS_North_American_

2280 NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet_Intl PROJCS["NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet_Intl",GEOGCS["GCS_North_Americ
2281 NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet_Intl PROJCS["NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet_Intl",GEOGCS["GCS_North_Amer
2282 NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet_Intl PROJCS["NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet_Intl",GEOGCS["GCS_North_Americ
2283 NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet PROJCS["NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet",GEOGCS["GCS_North_American
2284 NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet PROJCS["NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet",GEOGCS["GCS_North_America
2285 NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet PROJCS["NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet",GEOGCS["GCS_North_Ame
2286 NAD_1983_StatePlane_Washington_South_FIPS_4602_Feet PROJCS["NAD_1983_StatePlane_Washington_South_FIPS_4602_Feet",GEOGCS["GCS_North_Ame
2287 NAD_1983_StatePlane_Wisconsin_North_FIPS_4801_Feet PROJCS["NAD_1983_StatePlane_Wisconsin_North_FIPS_4801_Feet",GEOGCS["GCS_North_Ameri
2288 NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802_Feet PROJCS["NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802_Feet",GEOGCS["GCS_North_Ame
2289 NAD_1983_StatePlane_Wisconsin_South_FIPS_4803_Feet PROJCS["NAD_1983_StatePlane_Wisconsin_South_FIPS_4803_Feet",GEOGCS["GCS_North_Amer
2290 Prince_Edward_Island_Stereographic PROJCS["Prince_Edward_Island_Stereographic",GEOGCS["GCS_ATS_1977",DATUM["D_ATS_1977
2291 NAD_1983_CSRS_Prince_Edward_Island PROJCS["NAD_1983_CSRS_Prince_Edward_Island",GEOGCS["GCS_North_American_1983_CSRS
2294 ATS_1977_MTM_4_Nova_Scotia PROJCS["ATS_1977_MTM_4_Nova_Scotia",GEOGCS["GCS_ATS_1977",DATUM["D_ATS_1977",SP
2295 ATS_1977_MTM_5_Nova_Scotia PROJCS["ATS_1977_MTM_5_Nova_Scotia",GEOGCS["GCS_ATS_1977",DATUM["D_ATS_1977",SP
2308 Batavia_TM_109_SE PROJCS["Batavia_TM_109_SE",GEOGCS["GCS_Batavia",DATUM["D_Batavia",SPHEROID["Bessel_
2309 WGS_1984_TM_116_SE PROJCS["WGS_1984_TM_116_SE",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
2310 WGS_1984_TM_132_SE PROJCS["WGS_1984_TM_132_SE",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
2311 WGS_1984_TM_6_NE PROJCS["WGS_1984_TM_6_NE",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID
2312 Garoua_UTM_Zone_33N PROJCS["Garoua_UTM_Zone_33N",GEOGCS["GCS_Garoua",DATUM["D_Garoua",SPHEROID["Clar
2313 Kousseri_UTM_Zone_33N PROJCS["Kousseri_UTM_Zone_33N",GEOGCS["GCS_Kousseri",DATUM["D_Kousseri",SPHEROID["
2314 Trinidad_1903_Trinidad_Grid_Feet_Clarke PROJCS["Trinidad_1903_Trinidad_Grid_Feet_Clarke",GEOGCS["GCS_Trinidad_1903",DATUM["D_Tr
2315 Campo_Inchauspe_UTM_19S PROJCS["Campo_Inchauspe_UTM_19S",GEOGCS["GCS_Campo_Inchauspe",DATUM["D_Campo_In
2316 Campo_Inchauspe_UTM_20S PROJCS["Campo_Inchauspe_UTM_20S",GEOGCS["GCS_Campo_Inchauspe",DATUM["D_Campo_In
2317 PSAD_1956_ICN_Regional PROJCS["PSAD_1956_ICN_Regional",GEOGCS["GCS_Provisional_S_American_1956",DATUM["D_P
2318 Ain_el_Abd_Aramco_Lambert PROJCS["Ain_el_Abd_Aramco_Lambert",GEOGCS["GCS_Ain_el_Abd_1970",DATUM["D_Ain_el_Abd
2319 ED_1950_TM27 PROJCS["ED_1950_TM27",GEOGCS["GCS_European_1950",DATUM["D_European_1950",SPHERO
2326 Hong_Kong_1980_Grid PROJCS["Hong_Kong_1980_Grid",GEOGCS["GCS_Hong_Kong_1980",DATUM["D_Hong_Kong_198
2327 Xian_1980_GK_Zone_13 PROJCS["Xian_1980_GK_Zone_13",GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980",SPHEROID
2338 Xian_1980_GK_CM_75E PROJCS["Xian_1980_GK_CM_75E",GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980",SPHEROID
2343 Xian_1980_GK_CM_105E PROJCS["Xian_1980_GK_CM_105E",GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980",SPHERO
2344 Xian_1980_GK_CM_111E PROJCS["Xian_1980_GK_CM_111E",GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980",SPHEROI


2349 Xian_1980_3_Degree_GK_Zone_25 PROJCS["Xian_1980_3_Degree_GK_Zone_25",GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980"
2370 Xian_1980_3_Degree_GK_CM_75E PROJCS["Xian_1980_3_Degree_GK_CM_75E",GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980"
2379 Xian_1980_3_Degree_GK_CM_102E PROJCS["Xian_1980_3_Degree_GK_CM_102E",GEOGCS["GCS_Xian_1980",DATUM["D_Xian_1980
2391 Finland_Zone_1 PROJCS["Finland_Zone_1",GEOGCS["GCS_KKJ",DATUM["D_KKJ",SPHEROID["International_1924",

2400 RT90_25_gon_W PROJCS["RT90_25_gon_W",GEOGCS["GCS_RT_1990",DATUM["D_RT_1990",SPHEROID["Bessel_1

2401 Beijing_1954_3_Degree_GK_Zone_25 PROJCS["Beijing_1954_3_Degree_GK_Zone_25",GEOGCS["GCS_Beijing_1954",DATUM["D_Beijing_
2422 Beijing_1954_3_Degree_GK_CM_75E PROJCS["Beijing_1954_3_Degree_GK_CM_75E",GEOGCS["GCS_Beijing_1954",DATUM["D_Beijing_
2431 Beijing_1954_3_Degree_GK_CM_102E PROJCS["Beijing_1954_3_Degree_GK_CM_102E",GEOGCS["GCS_Beijing_1954",DATUM["D_Beijing
2443 JGD_2000_Japan_Zone_1 PROJCS["JGD_2000_Japan_Zone_1",GEOGCS["GCS_JGD_2000",DATUM["D_JGD_2000",SPHERO
2452 JGD_2000_Japan_Zone_10 PROJCS["JGD_2000_Japan_Zone_10",GEOGCS["GCS_JGD_2000",DATUM["D_JGD_2000",SPHER


2462 Albanian_1987_GK_Zone_4 PROJCS["Albanian_1987_GK_Zone_4",GEOGCS["GCS_Albanian_1987",DATUM["D_Albanian_1987"
2463 Pulkovo_1995_Gauss-Kruger_CM_21E PROJCS["Pulkovo_1995_Gauss-Kruger_CM_21E",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulko
2477 Pulkovo_1995_Gauss-Kruger_CM_105E PROJCS["Pulkovo_1995_Gauss-Kruger_CM_105E",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulk
2490 Pulkovo_1995_Gauss-Kruger_CM_177W PROJCS["Pulkovo_1995_Gauss-Kruger_CM_177W",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pul


2523 Pulkovo_1942_3_Degree_GK_Zone_7 PROJCS["Pulkovo_1942_3_Degree_GK_Zone_7",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulko
2526 Pulkovo_1942_3_Degree_GK_Zone_10 PROJCS["Pulkovo_1942_3_Degree_GK_Zone_10",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulk
2550 Samboja_UTM_Zone_50S PROJCS["Samboja_UTM_Zone_50S",GEOGCS["GCS_Samboja",DATUM["D_Samboja",SPHEROID["


2582 Pulkovo_1942_3_Degree_GK_CM_21E PROJCS["Pulkovo_1942_3_Degree_GK_CM_21E",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulko
2600 LKS_1994_Lithuania_TM PROJCS["LKS_1994_Lithuania_TM",GEOGCS["GCS_LKS_1994",DATUM["D_Lithuania_1994",SPHE
2610 Pulkovo_1942_3_Degree_GK_CM_102E PROJCS["Pulkovo_1942_3_Degree_GK_CM_102E",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pul
2613 Pulkovo_1942_3_Degree_GK_CM_111E PROJCS["Pulkovo_1942_3_Degree_GK_CM_111E",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulk


2637 Pulkovo_1942_3_Degree_GK_CM_177W PROJCS["Pulkovo_1942_3_Degree_GK_CM_177W",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pu




2736 Tete_UTM_Zone_36S PROJCS["Tete_UTM_Zone_36S",GEOGCS["GCS_Tete",DATUM["D_Tete",SPHEROID["Clarke_1866"
2737 Tete_UTM_Zone_37S PROJCS["Tete_UTM_Zone_37S",GEOGCS["GCS_Tete",DATUM["D_Tete",SPHEROID["Clarke_1866"
2759 NAD_1983_HARN_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1983_HARN_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_North_Americ
2760 NAD_1983_HARN_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1983_HARN_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_North_Ameri
2761 NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_North_America
2762 NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_North_Amer
2763 NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_North_Americ
2764 NAD_1983_HARN_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1983_HARN_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_North_Amer
2765 NAD_1983_HARN_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1983_HARN_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_North_Ame
2766 NAD_1983_HARN_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1983_HARN_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_North_American
2767 NAD_1983_HARN_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1983_HARN_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_North_American
2768 NAD_1983_HARN_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1983_HARN_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_North_America
2769 NAD_1983_HARN_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1983_HARN_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_North_America
2770 NAD_1983_HARN_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1983_HARN_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_North_American
2771 NAD_1983_HARN_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1983_HARN_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_North_America
2772 NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_North_Amer
2773 NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_North_Am
2774 NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_North_Ame
2775 NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_North_American
2776 NAD_1983_HARN_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1983_HARN_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_North_American_1
2777 NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_North_America
2778 NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_North_America
2779 NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_North_America

2780 NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_North_America

2781 NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_North_Americ
2782 NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101 PROJCS["NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101",GEOGCS["GCS_North_American_1
2787 NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_North_American_
2788 NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_North_Americ
2789 NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_North_American
2790 NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_North_American
2791 NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_North_America
2792 NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_North_America
2793 NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_North_America
2794 NAD_1983_HARN_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1983_HARN_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_North_American
2795 NAD_1983_HARN_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1983_HARN_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_North_American
2796 NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_North_Americ
2797 NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_North_Americ
2798 NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_North_Amer
2799 NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_North_Ame
2800 NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_North_Ame
2801 NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_North_Ame
2802 NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_North_American
2803 NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_North_American
2804 NAD_1983_HARN_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1983_HARN_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_North_American_1
2805 NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS["GCS_No
2806 NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["GCS_North
2807 NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_North_Ameri
2808 NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_North_Ame
2809 NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_North_Amer
2810 NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_North_Ame
2811 NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS_North_Am
2812 NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_North_Am
2813 NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_North_Ame
2814 NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_North_Ame
2815 NAD_1983_HARN_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1983_HARN_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_North_Americ
2816 NAD_1983_HARN_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1983_HARN_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_North_Ame
2817 NAD_1983_HARN_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1983_HARN_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_North_Americ
2818 NAD_1983_HARN_StatePlane_Montana_FIPS_2500 PROJCS["NAD_1983_HARN_StatePlane_Montana_FIPS_2500",GEOGCS["GCS_North_American_19
2819 NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600 PROJCS["NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600",GEOGCS["GCS_North_American_1
2820 NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_North_America
2821 NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_North_Ame
2822 NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_North_Americ
2823 NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_North_Ame
2824 NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_North_American
2825 NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS_North_Am
2826 NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["GCS_North_
2827 NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS_North_Am
2828 NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_North_Amer
2829 NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS_North_Am
2830 NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_North_Ame
2831 NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GCS_Nort
2832 NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GCS_North_A
2833 NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GCS_North_

2834 NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_North_American

2835 NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_North_American
2836 NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_North_Ame
2837 NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_North_Ame
2838 NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_North_Americ
2839 NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_North_Americ
2840 NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_North_Americ
2841 NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GCS_North_
2842 NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["GCS_North_
2843 NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_North_American_
2844 NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_North_America
2845 NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["GCS_North_
2846 NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_North_Americ
2847 NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["GCS_North_
2848 NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_North_America
2849 NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_North_American
2850 NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_North_America
2851 NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_North_American
2852 NAD_1983_HARN_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1983_HARN_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_North_American_19
2853 NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_North_Americ
2854 NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_North_Americ
2855 NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS_North_Am
2856 NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS_North_Am
2857 NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GCS_North_A
2858 NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GCS_North_
2859 NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_North_Ame
2860 NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS_North_Am
2861 NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_North_Ame
2862 NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_North_Ameri
2863 NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS["GCS_Nort
2864 NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS["GCS_Nor
2865 NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_North_Amer
2866 NAD_1983_HARN_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200 PROJCS["NAD_1983_HARN_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200",GEOGCS["GCS_
2867 NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201_Feet_Intl",GEOGCS["GCS_Nort
2868 NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202_Feet_Intl",GEOGCS["GCS_N
2869 NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203_Feet_Intl",GEOGCS["GCS_Nor
2870 NAD_1983_HARN_StatePlane_California_I_FIPS_0401_Feet PROJCS["NAD_1983_HARN_StatePlane_California_I_FIPS_0401_Feet",GEOGCS["GCS_North_Ame
2871 NAD_1983_HARN_StatePlane_California_II_FIPS_0402_Feet PROJCS["NAD_1983_HARN_StatePlane_California_II_FIPS_0402_Feet",GEOGCS["GCS_North_Am
2872 NAD_1983_HARN_StatePlane_California_III_FIPS_0403_Feet PROJCS["NAD_1983_HARN_StatePlane_California_III_FIPS_0403_Feet",GEOGCS["GCS_North_Am
2873 NAD_1983_HARN_StatePlane_California_IV_FIPS_0404_Feet PROJCS["NAD_1983_HARN_StatePlane_California_IV_FIPS_0404_Feet",GEOGCS["GCS_North_Am
2874 NAD_1983_HARN_StatePlane_California_V_FIPS_0405_Feet PROJCS["NAD_1983_HARN_StatePlane_California_V_FIPS_0405_Feet",GEOGCS["GCS_North_Am
2875 NAD_1983_HARN_StatePlane_California_VI_FIPS_0406_Feet PROJCS["NAD_1983_HARN_StatePlane_California_VI_FIPS_0406_Feet",GEOGCS["GCS_North_Am
2876 NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501_Feet PROJCS["NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501_Feet",GEOGCS["GCS_North_
2877 NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502_Feet PROJCS["NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502_Feet",GEOGCS["GCS_Nort
2878 NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503_Feet PROJCS["NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503_Feet",GEOGCS["GCS_North_
2879 NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600_Feet PROJCS["NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600_Feet",GEOGCS["GCS_North_Am
2880 NAD_1983_HARN_StatePlane_Delaware_FIPS_0700_Feet PROJCS["NAD_1983_HARN_StatePlane_Delaware_FIPS_0700_Feet",GEOGCS["GCS_North_Ameri
2881 NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet PROJCS["NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet",GEOGCS["GCS_North_Am
2882 NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902_Feet PROJCS["NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902_Feet",GEOGCS["GCS_North_Am
2883 NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903_Feet PROJCS["NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903_Feet",GEOGCS["GCS_North_A
2884 NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001_Feet PROJCS["NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001_Feet",GEOGCS["GCS_North_A
2885 NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002_Feet PROJCS["NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002_Feet",GEOGCS["GCS_North_A
2886 NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101_Feet PROJCS["NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101_Feet",GEOGCS["GCS_North_Ame
2887 NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102_Feet PROJCS["NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102_Feet",GEOGCS["GCS_North_A

2888 NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103_Feet PROJCS["NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103_Feet",GEOGCS["GCS_North_Am

2891 NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601_Feet PROJCS["NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601_Feet",GEOGCS["GCS_North_
2892 NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602_Feet PROJCS["NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602_Feet",GEOGCS["GCS_North
2893 NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet PROJCS["NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_Ameri
2894 NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet PROJCS["NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet",GEOGCS["GC
2895 NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002_Feet PROJCS["NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002_Feet",GEOGCS["GCS_
2896 NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111_Feet_Intl",GEOGCS["GCS_No
2897 NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2112_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2112_Feet_Intl",GEOGCS["GCS_N
2898 NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113_Feet_Intl",GEOGCS["GCS_N
2899 NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301_Feet PROJCS["NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301_Feet",GEOGCS["GCS_North
2900 NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302_Feet PROJCS["NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302_Feet",GEOGCS["GCS_North
2901 NAD_1983_HARN_StatePlane_Montana_FIPS_2500_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Montana_FIPS_2500_Feet_Intl",GEOGCS["GCS_North_Am
2902 NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001_Feet PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001_Feet",GEOGCS["GCS_Nor
2903 NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002_Feet PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002_Feet",GEOGCS["GCS_N
2904 NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003_Feet PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003_Feet",GEOGCS["GCS_No
2905 NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101_Feet PROJCS["NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101_Feet",GEOGCS["GCS_North_
2906 NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102_Feet PROJCS["NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102_Feet",GEOGCS["GCS_Nor
2907 NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103_Feet PROJCS["NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103_Feet",GEOGCS["GCS_North
2908 NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104_Feet PROJCS["NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104_Feet",GEOGCS["GCS
2909 NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301_Feet_Intl",GEOGCS["GC
2910 NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302_Feet_Intl",GEOGCS["GC
2911 NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501_Feet PROJCS["NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501_Feet",GEOGCS["GCS_North
2912 NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502_Feet PROJCS["NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502_Feet",GEOGCS["GCS_North
2913 NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl",GEOGCS["GCS_Nor
2914 NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602_Feet_Intl",GEOGCS["GCS_Nor
2915 NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100_Feet PROJCS["NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100_Feet",GEOGCS["GCS_North_Ame
2916 NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201_Feet PROJCS["NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201_Feet",GEOGCS["GCS_North_Am
2917 NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202_Feet PROJCS["NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202_Feet",GEOGCS["GCS_N
2918 NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203_Feet PROJCS["NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203_Feet",GEOGCS["GCS_North_A
2919 NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204_Feet PROJCS["NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204_Feet",GEOGCS["GCS_N
2920 NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205_Feet PROJCS["NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205_Feet",GEOGCS["GCS_North_Am
2921 NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301_Feet_Intl",GEOGCS["GCS_North_
2922 NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302_Feet_Intl",GEOGCS["GCS_North
2923 NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303_Feet_Intl",GEOGCS["GCS_North_
2924 NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501_Feet PROJCS["NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501_Feet",GEOGCS["GCS_North_A
2925 NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502_Feet PROJCS["NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502_Feet",GEOGCS["GCS_North_A
2926 NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601_Feet PROJCS["NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601_Feet",GEOGCS["GCS_Nor
2927 NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet PROJCS["NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet",GEOGCS["GCS_Nor
2928 NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801_Feet PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801_Feet",GEOGCS["GCS_North
2929 NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802_Feet PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802_Feet",GEOGCS["GCS_Nor
2930 NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803_Feet PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803_Feet",GEOGCS["GCS_North
2931 Beduaram_TM_13_NE PROJCS["Beduaram_TM_13_NE",GEOGCS["GCS_Beduaram",DATUM["D_Beduaram",SPHEROID["C
2932 QND_1995_Qatar_National_Grid PROJCS["QND_1995_Qatar_National_Grid",GEOGCS["GCS_QND_1995",DATUM["D_QND_1995",SP
2933 Gunung_Segara_UTM_Zone_50S PROJCS["Gunung_Segara_UTM_Zone_50S",GEOGCS["GCS_Gunung_Segara",DATUM["D_Gunung
2934 Gunung_Segara_Jakarta_NEIEZ PROJCS["Gunung_Segara_Jakarta_NEIEZ",GEOGCS["GCS_Gunung_Segara_Jakarta",DATUM["D_G
2935 Pulkovo_1942_CS63_Zone_A1 PROJCS["Pulkovo_1942_CS63_Zone_A1",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulkovo_194
2939 Pulkovo_1942_CS63_Zone_K2 PROJCS["Pulkovo_1942_CS63_Zone_K2",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulkovo_194
2942 Porto_Santo_1936_UTM_Zone_28N PROJCS["Porto_Santo_1936_UTM_Zone_28N",GEOGCS["GCS_Porto_Santo_1936",DATUM["D_Por
2943 Selvagem_Grande_1938_UTM_Zone_28N PROJCS["Selvagem_Grande_1938_UTM_Zone_28N",GEOGCS["GCS_Selvagem_Grande_1938",DA

2944 NAD_1983_CSRS_MTM_2_SCoPQ PROJCS["NAD_1983_CSRS_MTM_2_SCoPQ",GEOGCS["GCS_North_American_1983_CSRS",DATU

2952 NAD_1983_CSRS_MTM_10 PROJCS["NAD_1983_CSRS_MTM_10",GEOGCS["GCS_North_American_1983_CSRS",DATUM["D_
2953 NAD_1983_CSRS_New_Brunswick_Stereographic PROJCS["NAD_1983_CSRS_New_Brunswick_Stereographic",GEOGCS["GCS_North_American_198
2964 NAD_1927_Alaska_Albers_Feet PROJCS["NAD_1927_Alaska_Albers_Feet",GEOGCS["GCS_North_American_1927",DATUM["D_Nort
2965 NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet PROJCS["NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet",GEOGCS["GCS_North_American_
2966 NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet PROJCS["NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet",GEOGCS["GCS_North_American
2967 NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301_Feet PROJCS["NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301_Feet",GEOGCS["GCS_North_Am
2968 NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302_Feet PROJCS["NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302_Feet",GEOGCS["GCS_North_A
2969 Fort_Marigot_UTM_20N PROJCS["Fort_Marigot_UTM_20N",GEOGCS["GCS_Fort_Marigot",DATUM["D_Fort_Marigot",SPHER
2970 Sainte_Anne_UTM_20N PROJCS["Sainte_Anne_UTM_20N",GEOGCS["GCS_Sainte_Anne",DATUM["D_Sainte_Anne",SPHER
2971 CSG_1967_UTM_22N PROJCS["CSG_1967_UTM_22N",GEOGCS["GCS_CSG_1967",DATUM["D_CSG_1967",SPHEROID[
2972 RGFG_1995_UTM_22N PROJCS["RGFG_1995_UTM_22N",GEOGCS["GCS_RGFG_1995",DATUM["D_RGFG_1995",SPHER
2973 Fort_Desaix_UTM_20N PROJCS["Fort_Desaix_UTM_20N",GEOGCS["GCS_Fort_Desaix",DATUM["D_Fort_Desaix",SPHERO
2975 RGR_1992_UTM_40S PROJCS["RGR_1992_UTM_40S",GEOGCS["GCS_RGR_1992",DATUM["D_RGR_1992",SPHEROID[
2976 Tahiti_1952_UTM_6S PROJCS["Tahiti_1952_UTM_6S",GEOGCS["GCS_Tahiti_1952",DATUM["D_Tahiti_1952",SPHEROID["
2977 Tahaa_1954_UTM_5S PROJCS["Tahaa_1954_UTM_5S",GEOGCS["GCS_Tahaa_1954",DATUM["D_Tahaa_1954",SPHEROI
2978 IGN72_Nuku_Hiva_UTM_7S PROJCS["IGN72_Nuku_Hiva_UTM_7S",GEOGCS["GCS_IGN72_Nuku_Hiva",DATUM["D_IGN72_Nuk
2979 Kerguelen_Island_1949_UTM_42S PROJCS["Kerguelen_Island_1949_UTM_42S",GEOGCS["GCS_Kerguelen_Island_1949",DATUM["D_
2980 Combani_1950_UTM_38S PROJCS["Combani_1950_UTM_38S",GEOGCS["GCS_Combani_1950",DATUM["D_Combani_1950",S
2981 IGN56_Lifou_UTM_58S PROJCS["IGN56_Lifou_UTM_58S",GEOGCS["GCS_IGN56_Lifou",DATUM["D_IGN56_Lifou",SPHERO
2982 IGN72_Grande_Terre_UTM_58S PROJCS["IGN72_Grande_Terre_UTM_58S",GEOGCS["GCS_IGN72_Grande_Terre",DATUM["D_IGN7
2984 RGNC_1991_Lambert_New_Caledonia PROJCS["RGNC_1991_Lambert_New_Caledonia",GEOGCS["GCS_RGNC_1991",DATUM["D_RGNC
2985 Petrels_1972_Terre_Adelie_Polar_Stereographic PROJCS["Petrels_1972_Terre_Adelie_Polar_Stereographic",GEOGCS["GCS_Petrels_1972",DATUM["
2986 Perroud_1950_Terre_Adelie_Polar_Stereographic PROJCS["Perroud_1950_Terre_Adelie_Polar_Stereographic",GEOGCS["GCS_Pointe_Geologie_Perro
2987 Saint_Pierre_et_Miquelon_1950_UTM_21N PROJCS["Saint_Pierre_et_Miquelon_1950_UTM_21N",GEOGCS["GCS_Saint_Pierre_et_Miquelon_19
2988 MOP78_UTM_1S PROJCS["MOP78_UTM_1S",GEOGCS["GCS_MOP78",DATUM["D_MOP78",SPHEROID["Internationa
2991 NAD_1983_Oregon_Statewide_Lambert PROJCS["NAD_1983_Oregon_Statewide_Lambert",GEOGCS["GCS_North_American_1983",DATUM[
2992 NAD_1983_Oregon_Statewide_Lambert_Feet_Intl PROJCS["NAD_1983_Oregon_Statewide_Lambert_Feet_Intl",GEOGCS["GCS_North_American_1983
2993 NAD_1983_HARN_Oregon_Statewide_Lambert PROJCS["NAD_1983_HARN_Oregon_Statewide_Lambert",GEOGCS["GCS_North_American_1983_H
2994 NAD_1983_HARN_Oregon_Statewide_Lambert_Feet_Intl PROJCS["NAD_1983_HARN_Oregon_Statewide_Lambert_Feet_Intl",GEOGCS["GCS_North_America
2995 IGN53_Mare_UTM_58S PROJCS["IGN53_Mare_UTM_58S",GEOGCS["GCS_IGN53_Mare",DATUM["D_IGN53_Mare",SPHER
2996 ST84_Ile_des_Pins_UTM_58S PROJCS["ST84_Ile_des_Pins_UTM_58S",GEOGCS["GCS_ST84_Ile_des_Pins",DATUM["D_ST84_Ile
2997 ST71_Belep_UTM_58S PROJCS["ST71_Belep_UTM_58S",GEOGCS["GCS_ST71_Belep",DATUM["D_ST71_Belep",SPHERO
2998 NEA74_Noumea_UTM_58S PROJCS["NEA74_Noumea_UTM_58S",GEOGCS["GCS_NEA74_Noumea",DATUM["D_NEA74_Noum
2999 Grand_Comoros_UTM_38S PROJCS["Grand_Comoros_UTM_38S",GEOGCS["GCS_Grand_Comoros",DATUM["D_Grand_Comor
3000 Gunung_Segara_NEIEZ PROJCS["Gunung_Segara_NEIEZ",GEOGCS["GCS_Gunung_Segara",DATUM["D_Gunung_Segara",
3001 Batavia_NEIEZ PROJCS["Batavia_NEIEZ",GEOGCS["GCS_Batavia",DATUM["D_Batavia",SPHEROID["Bessel_1841"
3002 Makassar_NEIEZ PROJCS["Makassar_NEIEZ",GEOGCS["GCS_Makassar",DATUM["D_Makassar",SPHEROID["Bessel_

3003 Monte_Mario_Italy_1 PROJCS["Monte_Mario_Italy_1",GEOGCS["GCS_Monte_Mario",DATUM["D_Monte_Mario",SPHEROI

3004 Monte_Mario_Italy_2 PROJCS["Monte_Mario_Italy_2",GEOGCS["GCS_Monte_Mario",DATUM["D_Monte_Mario",SPHEROI
3005 NAD_1983_BC_Environment_Albers PROJCS["NAD_1983_BC_Environment_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_
3006 SWEREF99_TM PROJCS["SWEREF99_TM",GEOGCS["GCS_SWEREF99",DATUM["D_SWEREF99",SPHEROID["GR
3007 SWEREF99_12_00 PROJCS["SWEREF99_12_00",GEOGCS["GCS_SWEREF99",DATUM["D_SWEREF99",SPHEROID["G
3019 RT90_75_gon_V PROJCS["RT90_75_gon_V",GEOGCS["GCS_RT_1990",DATUM["D_RT_1990",SPHEROID["Bessel_1
3022 RT90_0_gon PROJCS["RT90_0_gon",GEOGCS["GCS_RT_1990",DATUM["D_RT_1990",SPHEROID["Bessel_1841
3023 RT90_25_gon_O PROJCS["RT90_25_gon_O",GEOGCS["GCS_RT_1990",DATUM["D_RT_1990",SPHEROID["Bessel_1
3024 RT90_5_gon_O PROJCS["RT90_5_gon_O",GEOGCS["GCS_RT_1990",DATUM["D_RT_1990",SPHEROID["Bessel_18
3025 RT38_75_gon_V PROJCS["RT38_75_gon_V",GEOGCS["GCS_RT38",DATUM["D_Stockholm_1938",SPHEROID["Bess
3026 RT38_5_gon_V PROJCS["RT38_5_gon_V",GEOGCS["GCS_RT38",DATUM["D_Stockholm_1938",SPHEROID["Besse
3027 RT38_25_gon_V PROJCS["RT38_25_gon_V",GEOGCS["GCS_RT38",DATUM["D_Stockholm_1938",SPHEROID["Bess
3028 RT38_0_gon PROJCS["RT38_0_gon",GEOGCS["GCS_RT38",DATUM["D_Stockholm_1938",SPHEROID["Bessel_1
3029 RT38_25_gon_O PROJCS["RT38_25_gon_O",GEOGCS["GCS_RT38",DATUM["D_Stockholm_1938",SPHEROID["Bess
3030 RT38_5_gon_O PROJCS["RT38_5_gon_O",GEOGCS["GCS_RT38",DATUM["D_Stockholm_1938",SPHEROID["Besse
3031 WGS_1984_Antarctic_Polar_Stereographic PROJCS["WGS_1984_Antarctic_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D_WG
3032 WGS_1984_Australian_Antarctic_Polar_Stereographic PROJCS["WGS_1984_Australian_Antarctic_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATU
3033 WGS_1984_Australian_Antarctic_Lambert PROJCS["WGS_1984_Australian_Antarctic_Lambert",GEOGCS["GCS_WGS_1984",DATUM["D_WGS
3034 ETRS_1989_LCC PROJCS["ETRS_1989_LCC",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID["G
3035 ETRS_1989_LAEA PROJCS["ETRS_1989_LAEA",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID["G
3036 Moznet_UTM_Zone_36S PROJCS["Moznet_UTM_Zone_36S",GEOGCS["GCS_Moznet",DATUM["D_Moznet",SPHEROID["WGS
3038 ETRS_1989_ETRS-TM26 PROJCS["ETRS_1989_ETRS-TM26",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHER
3054 Hjorsey_1955_UTM_Zone_26N PROJCS["Hjorsey_1955_UTM_Zone_26N",GEOGCS["GCS_Hjorsey_1955",DATUM["D_Hjorsey_1955
3057 ISN_1993_Lambert_1993 PROJCS["ISN_1993_Lambert_1993",GEOGCS["GCS_ISN_1993",DATUM["D_Islands_Network_1993
3058 Helle_1954_Jan_Mayen_Grid PROJCS["Helle_1954_Jan_Mayen_Grid",GEOGCS["GCS_Helle_1954",DATUM["D_Helle_1954",SPHE

3059 LKS_1992_Latvia_TM PROJCS["LKS_1992_Latvia_TM",GEOGCS["GCS_LKS_1992",DATUM["D_Latvia_1992",SPHEROID[

3060 IGN72_Grande_Terre_UTM_58S PROJCS["IGN72_Grande_Terre_UTM_58S",GEOGCS["GCS_IGN72_Grande_Terre",DATUM["D_IGN7
3061 Porto_Santo_1995_UTM_Zone_28N PROJCS["Porto_Santo_1995_UTM_Zone_28N",GEOGCS["GCS_Porto_Santo_1995",DATUM["D_Por
3062 Azores_Oriental_1995_UTM_Zone_26N PROJCS["Azores_Oriental_1995_UTM_Zone_26N",GEOGCS["GCS_Azores_Oriental_1995",DATUM[
3063 Azores_Central_1995_UTM_Zone_26N PROJCS["Azores_Central_1995_UTM_Zone_26N",GEOGCS["GCS_Azores_Central_1995",DATUM["D
3064 IGM_1995_UTM_Zone_32N PROJCS["IGM_1995_UTM_Zone_32N",GEOGCS["GCS_IGM_1995",DATUM["D_IGM_1995",SPHERO
3065 IGM_1995_UTM_Zone_33N PROJCS["IGM_1995_UTM_Zone_33N",GEOGCS["GCS_IGM_1995",DATUM["D_IGM_1995",SPHERO
3066 ED_1950_Jordan_TM PROJCS["ED_1950_Jordan_TM",GEOGCS["GCS_European_1950",DATUM["D_European_1950",SPH
3067 EUREF_FIN_TM35FIN PROJCS["EUREF_FIN_TM35FIN",GEOGCS["GCS_EUREF_FIN",DATUM["D_ETRS_1989",SPHERO
3068 DHDN_Soldner_Berlin PROJCS["DHDN_Soldner_Berlin",GEOGCS["GCS_Deutsches_Hauptdreiecksnetz",DATUM["D_Deuts
3069 NAD_1927_Wisconsin_TM PROJCS["NAD_1927_Wisconsin_TM",GEOGCS["GCS_North_American_1927",DATUM["D_North_Am
3070 NAD_1983_Wisconsin_TM PROJCS["NAD_1983_Wisconsin_TM",GEOGCS["GCS_North_American_1983",DATUM["D_North_Am
3071 NAD_1983_HARN_Wisconsin_TM PROJCS["NAD_1983_HARN_Wisconsin_TM",GEOGCS["GCS_North_American_1983_HARN",DATUM
3072 NAD_1983_Maine_2000_East_Zone PROJCS["NAD_1983_Maine_2000_East_Zone",GEOGCS["GCS_North_American_1983",DATUM["D_
3073 NAD_1983_Maine_2000_Central_Zone PROJCS["NAD_1983_Maine_2000_Central_Zone",GEOGCS["GCS_North_American_1983",DATUM["
3074 NAD_1983_Maine_2000_West_Zone PROJCS["NAD_1983_Maine_2000_West_Zone",GEOGCS["GCS_North_American_1983",DATUM["D_
3075 NAD_1983_HARN_Maine_2000_East_Zone PROJCS["NAD_1983_HARN_Maine_2000_East_Zone",GEOGCS["GCS_North_American_1983_HAR
3076 NAD_1983_HARN_Maine_2000_Central_Zone PROJCS["NAD_1983_HARN_Maine_2000_Central_Zone",GEOGCS["GCS_North_American_1983_H
3077 NAD_1983_HARN_Maine_2000_West_Zone PROJCS["NAD_1983_HARN_Maine_2000_West_Zone",GEOGCS["GCS_North_American_1983_HAR
3078 NAD_1983_Michigan_GeoRef_Meters PROJCS["NAD_1983_Michigan_GeoRef_Meters",GEOGCS["GCS_North_American_1983",DATUM["D
3079 NAD_1983_HARN_Michigan_GeoRef_Meters PROJCS["NAD_1983_HARN_Michigan_GeoRef_Meters",GEOGCS["GCS_North_American_1983_HA
3080 NAD_1927_Texas_Statewide_Mapping_System PROJCS["NAD_1927_Texas_Statewide_Mapping_System",GEOGCS["GCS_North_American_1927",D
3081 NAD_1983_Texas_Statewide_Mapping_System PROJCS["NAD_1983_Texas_Statewide_Mapping_System",GEOGCS["GCS_North_American_1983",D
3082 NAD_1983_Texas_Centric_Mapping_System_Lambert PROJCS["NAD_1983_Texas_Centric_Mapping_System_Lambert",GEOGCS["GCS_North_American_1
3083 NAD_1983_Texas_Centric_Mapping_System_Albers PROJCS["NAD_1983_Texas_Centric_Mapping_System_Albers",GEOGCS["GCS_North_American_19
3084 NAD_1983_HARN_Texas_Centric_Mapping_System_Lambert PROJCS["NAD_1983_HARN_Texas_Centric_Mapping_System_Lambert",GEOGCS["GCS_North_Am
3085 NAD_1983_HARN_Texas_Centric_Mapping_System_Albers PROJCS["NAD_1983_HARN_Texas_Centric_Mapping_System_Albers",GEOGCS["GCS_North_Amer
3086 NAD_1983_Florida_GDL_Albers PROJCS["NAD_1983_Florida_GDL_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_Nor
3087 NAD_1983_HARN_Florida_GDL_Albers PROJCS["NAD_1983_HARN_Florida_GDL_Albers",GEOGCS["GCS_North_American_1983_HARN",D
3088 NAD_1983_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_North_American_1983",DA
3089 NAD_1983_StatePlane_Kentucky_FIPS_1600_Feet PROJCS["NAD_1983_StatePlane_Kentucky_FIPS_1600_Feet",GEOGCS["GCS_North_American_198
3090 NAD_1983_HARN_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_HARN_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_North_American_1
3091 NAD_1983_HARN_StatePlane_Kentucky_FIPS_1600_Feet PROJCS["NAD_1983_HARN_StatePlane_Kentucky_FIPS_1600_Feet",GEOGCS["GCS_North_Ameri
3092 Tokyo_UTM_Zone_51N PROJCS["Tokyo_UTM_Zone_51N",GEOGCS["GCS_Tokyo",DATUM["D_Tokyo",SPHEROID["Bessel_1
3097 JGD_2000_UTM_Zone_51N PROJCS["JGD_2000_UTM_Zone_51N",GEOGCS["GCS_JGD_2000",DATUM["D_JGD_2000",SPHER
3102 Samoa_1962_Samoa_Lambert PROJCS["Samoa_1962_Samoa_Lambert",GEOGCS["GCS_American_Samoa_1962",DATUM["D_Am
3106 Gulshan_303_Bangladesh_TM PROJCS["Gulshan_303_Bangladesh_TM",GEOGCS["GCS_Gulshan_303",DATUM["D_Gulshan_303",
3107 GDA_1994_South_Australia_Lambert PROJCS["GDA_1994_South_Australia_Lambert",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_199
3108 ETRS_1989_Guernsey_Grid PROJCS["ETRS_1989_Guernsey_Grid",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPH
3109 ETRS_1989_Jersey_Transverse_Mercator PROJCS["ETRS_1989_Jersey_Transverse_Mercator",GEOGCS["GCS_ETRS_1989",DATUM["D_ETR
3110 AGD_1966_VICGRID PROJCS["AGD_1966_VICGRID",GEOGCS["GCS_Australian_1966",DATUM["D_Australian_1966",SP
3111 GDA_1994_VICGRID94 PROJCS["GDA_1994_VICGRID94",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID
3112 GDA_1994_Geoscience_Australia_Lambert PROJCS["GDA_1994_Geoscience_Australia_Lambert",GEOGCS["GCS_GDA_1994",DATUM["D_GDA
3113 GDA_1994_BCSG02 PROJCS["GDA_1994_BCSG02",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["G
3114 MAGNA_Colombia_Oeste_Oeste PROJCS["MAGNA_Colombia_Oeste_Oeste",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
3115 MAGNA_Colombia_Oeste PROJCS["MAGNA_Colombia_Oeste",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["G

3116 MAGNA_Colombia_Bogota PROJCS["MAGNA_Colombia_Bogota",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["G

3117 MAGNA_Colombia_Este PROJCS["MAGNA_Colombia_Este",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["GR
3118 MAGNA_Colombia_Este_Este PROJCS["MAGNA_Colombia_Este_Este",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID
3119 Douala_1948_AEF_West PROJCS["Douala_1948_AEF_West",GEOGCS["GCS_Douala_1948",DATUM["D_Douala_1948",SPHE
3120 Pulkovo_1942_Adj_1958_Poland_Zone_I PROJCS["Pulkovo_1942_Adj_1958_Poland_Zone_I",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DAT
3121 PRS_1992_Philippines_Zone_I PROJCS["PRS_1992_Philippines_Zone_I",GEOGCS["GCS_PRS_1992",DATUM["D_Philippine_Refer
3122 PRS_1992_Philippines_Zone_II PROJCS["PRS_1992_Philippines_Zone_II",GEOGCS["GCS_PRS_1992",DATUM["D_Philippine_Refer
3123 PRS_1992_Philippines_Zone_III PROJCS["PRS_1992_Philippines_Zone_III",GEOGCS["GCS_PRS_1992",DATUM["D_Philippine_Refe
3124 PRS_1992_Philippines_Zone_IV PROJCS["PRS_1992_Philippines_Zone_IV",GEOGCS["GCS_PRS_1992",DATUM["D_Philippine_Refe
3125 PRS_1992_Philippines_Zone_V PROJCS["PRS_1992_Philippines_Zone_V",GEOGCS["GCS_PRS_1992",DATUM["D_Philippine_Refe
3126 ETRS_1989_ETRS-GK19FIN PROJCS["ETRS_1989_ETRS-GK19FIN",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPH
3141 Fiji_1956_UTM_Zone_60S PROJCS["Fiji_1956_UTM_Zone_60S",GEOGCS["GCS_Fiji_1956",DATUM["D_Fiji_1956",SPHEROID[
3142 Fiji_1956_UTM_Zone_1S PROJCS["Fiji_1956_UTM_Zone_1S",GEOGCS["GCS_Fiji_1956",DATUM["D_Fiji_1956",SPHEROID["I
3148 Indian_1960_UTM_Zone_48N PROJCS["Indian_1960_UTM_Zone_48N",GEOGCS["GCS_Indian_1960",DATUM["D_Indian_1960",SP
3149 Indian_1960_UTM_Zone_49N PROJCS["Indian_1960_UTM_Zone_49N",GEOGCS["GCS_Indian_1960",DATUM["D_Indian_1960",SP
3153 NAD_1983_CSRS_BC_Environment_Albers PROJCS["NAD_1983_CSRS_BC_Environment_Albers",GEOGCS["GCS_North_American_1983_CSR
3161 NAD_1983_Ontario_MNR_Lambert PROJCS["NAD_1983_Ontario_MNR_Lambert",GEOGCS["GCS_North_American_1983",DATUM["D_N
3162 NAD_1983_CSRS_Ontario_MNR_Lambert PROJCS["NAD_1983_CSRS_Ontario_MNR_Lambert",GEOGCS["GCS_North_American_1983_CSRS
3163 RGNC_1991_93_Lambert_New_Caledonia PROJCS["RGNC_1991_93_Lambert_New_Caledonia",GEOGCS["GCS_RGNC_1991-93",DATUM["D_
3164 ST87_Ouvea_UTM_58S PROJCS["ST87_Ouvea_UTM_58S",GEOGCS["GCS_ST87_Ouvea",DATUM["D_ST87_Ouvea",SPHE
3165 NEA74_Noumea_Lambert PROJCS["NEA74_Noumea_Lambert",GEOGCS["GCS_NEA74_Noumea",DATUM["D_NEA74_Noume
3166 NEA74_Noumea_Lambert_2 PROJCS["NEA74_Noumea_Lambert_2",GEOGCS["GCS_NEA74_Noumea",DATUM["D_NEA74_Noum
3167 Kertau_RSO_RSO_Malaya_ChSears1922trunc PROJCS["Kertau_RSO_RSO_Malaya_ChSears1922trunc",GEOGCS["GCS_Kertau_RSO",DATUM["D
3168 Kertau_RSO_RSO_Malaya PROJCS["Kertau_RSO_RSO_Malaya",GEOGCS["GCS_Kertau_RSO",DATUM["D_Kertau_RSO",SPH
3169 RGNC_1991-93_UTM_Zone_57S PROJCS["RGNC_1991-93_UTM_Zone_57S",GEOGCS["GCS_RGNC_1991-93",DATUM["D_Reseau_
3172 IGN53_Mare_UTM_Zone_59S PROJCS["IGN53_Mare_UTM_Zone_59S",GEOGCS["GCS_IGN53_Mare",DATUM["D_IGN53_Mare",S
3174 NAD_1983_Great_Lakes_Basin_Albers PROJCS["NAD_1983_Great_Lakes_Basin_Albers",GEOGCS["GCS_North_American_1983",DATUM["
3175 NAD_1983_Great_Lakes_and_St_Lawrence_Albers PROJCS["NAD_1983_Great_Lakes_and_St_Lawrence_Albers",GEOGCS["GCS_North_American_198
3176 Indian_1960_TM_106NE PROJCS["Indian_1960_TM_106NE",GEOGCS["GCS_Indian_1960",DATUM["D_Indian_1960",SPHER

3177 LGD2006_Libya_TM PROJCS["LGD2006_Libya_TM",GEOGCS["GCS_LGD2006",DATUM["D_Libyan_Geodetic_Datum_20

3178 Greenland_1996_UTM_Zone_18N PROJCS["Greenland_1996_UTM_Zone_18N",GEOGCS["GCS_Greenland_1996",DATUM["D_Greenla
3190 LGD2006_Libya_TM_Zone_5 PROJCS["LGD2006_Libya_TM_Zone_5",GEOGCS["GCS_LGD2006",DATUM["D_Libyan_Geodetic_D
3195 LGD2006_Libya_TM_Zone_10 PROJCS["LGD2006_Libya_TM_Zone_10",GEOGCS["GCS_LGD2006",DATUM["D_Libyan_Geodetic_
3199 LGD2006_UTM_Zone_32N PROJCS["LGD2006_UTM_Zone_32N",GEOGCS["GCS_LGD2006",DATUM["D_Libyan_Geodetic_Dat
3200 FD_1958_Iraq PROJCS["FD_1958_Iraq",GEOGCS["GCS_FD_1958",DATUM["D_FD_1958",SPHEROID["Clarke_188
3294 WGS_1984_USGS_Transantarctic_Mountains PROJCS["WGS_1984_USGS_Transantarctic_Mountains",GEOGCS["GCS_WGS_1984",DATUM["D_W
3295 Guam_1963_Yap_Islands PROJCS["Guam_1963_Yap_Islands",GEOGCS["GCS_Guam_1963",DATUM["D_Guam_1963",SPHER
3296 RGPF_UTM_Zone_5S PROJCS["RGPF_UTM_Zone_5S",GEOGCS["GCS_RGPF",DATUM["D_Reseau_Geodesique_de_la_P
3300 Estonian_Coordinate_System_of_1992 PROJCS["Estonian_Coordinate_System_of_1992",GEOGCS["GCS_Estonia_1992",DATUM["D_Eston
3301 Estonia_1997_Estonia_National_Grid PROJCS["Estonia_1997_Estonia_National_Grid",GEOGCS["GCS_Estonia_1997",DATUM["D_Estonia
3302 IGN63_Hiva_Oa_UTM_Zone_7S PROJCS["IGN63_Hiva_Oa_UTM_Zone_7S",GEOGCS["GCS_IGN63_Hiva_Oa",DATUM["D_IGN63_H
3303 Fatu_Iva_1972_UTM_Zone_7S PROJCS["Fatu_Iva_1972_UTM_Zone_7S",GEOGCS["GCS_Fatu_Iva_1972",DATUM["D_Fatu_Iva_19
3304 Tahiti_1979_UTM_Zone_6S PROJCS["Tahiti_1979_UTM_Zone_6S",GEOGCS["GCS_Tahiti_1979",DATUM["D_Tahiti_1979",SPHER
3305 Moorea_1987_UTM_Zone_6S PROJCS["Moorea_1987_UTM_Zone_6S",GEOGCS["GCS_Moorea_1987",DATUM["D_Moorea_1987"
3306 Maupiti_1983_UTM_Zone_5S PROJCS["Maupiti_1983_UTM_Zone_5S",GEOGCS["GCS_Maupiti_1983",DATUM["D_Maupiti_1983",S
3307 Nakhl-e_Ghanem_UTM_Zone_39N PROJCS["Nakhl-e_Ghanem_UTM_Zone_39N",GEOGCS["GCS_Nakhl-e_Ghanem",DATUM["D_Nakhl
3308 GDA_1994_NSW_Lambert PROJCS["GDA_1994_NSW_Lambert",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHERO
3309 NAD_1927_California_Teale_Albers PROJCS["NAD_1927_California_Teale_Albers",GEOGCS["GCS_North_American_1927",DATUM["D_N
3310 NAD_1983_California_Teale_Albers PROJCS["NAD_1983_California_Teale_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_N
3311 NAD_1983_HARN_California_Teale_Albers PROJCS["NAD_1983_HARN_California_Teale_Albers",GEOGCS["GCS_North_American_1983_HARN
3312 CSG_1967_UTM_Zone_21N PROJCS["CSG_1967_UTM_Zone_21N",GEOGCS["GCS_CSG_1967",DATUM["D_CSG_1967",SPHE
3313 RGFG_1995_UTM_Zone_21N PROJCS["RGFG_1995_UTM_Zone_21N",GEOGCS["GCS_RGFG_1995",DATUM["D_RGFG_1995",S
3315 Katanga_1955_Katanga_TM PROJCS["Katanga_1955_Katanga_TM",GEOGCS["GCS_Katanga_1955",DATUM["D_Katanga_1955"
3316 Kasai_1953_Congo_TM_Zone_22 PROJCS["Kasai_1953_Congo_TM_Zone_22",GEOGCS["GCS_Kasai_1953",DATUM["D_Kasai_1953"
3317 Kasai_1953_Congo_TM_Zone_24 PROJCS["Kasai_1953_Congo_TM_Zone_24",GEOGCS["GCS_Kasai_1953",DATUM["D_Kasai_1953"
3318 IGC_1962_Congo_TM_Zone_12 PROJCS["IGC_1962_Congo_TM_Zone_12",GEOGCS["GCS_IGC_1962_6th_Parallel_South",DATUM


3328 Pulkovo_1942_Adj_1958_GUGiK-80 PROJCS["Pulkovo_1942_Adj_1958_GUGiK-80",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DATUM["
3333 Pulkovo_1942_Adj_1958_GK_Zone_3 PROJCS["Pulkovo_1942_Adj_1958_GK_Zone_3",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DATUM
3336 Kerguelen_Island_1949_UTM_42S PROJCS["Kerguelen_Island_1949_UTM_42S",GEOGCS["GCS_Kerguelen_Island_1949",DATUM["D_
3337 Le_Pouce_1934_Mauritius_Grid PROJCS["Le_Pouce_1934_Mauritius_Grid",GEOGCS["GCS_Le_Pouce_1934",DATUM["D_Le_Pouce
3338 NAD_1983_Alaska_Albers PROJCS["NAD_1983_Alaska_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_North_Am
3339 IGCB_1955_Congo_TM_Zone_12 PROJCS["IGCB_1955_Congo_TM_Zone_12",GEOGCS["GCS_IGCB_1955",DATUM["D_Institut_Geog
3342 IGCB_1955_UTM_Zone_33S PROJCS["IGCB_1955_UTM_Zone_33S",GEOGCS["GCS_IGCB_1955",DATUM["D_Institut_Geograph
3343 Mauritania_1999_UTM_Zone_28N PROJCS["Mauritania_1999_UTM_Zone_28N",GEOGCS["GCS_Mauritania_1999",DATUM["D_Maurita
3346 LKS_1994_Lithuania_TM PROJCS["LKS_1994_Lithuania_TM",GEOGCS["GCS_LKS_1994",DATUM["D_Lithuania_1994",SPHE
3347 NAD_1983_Statistics_Canada_Lambert PROJCS["NAD_1983_Statistics_Canada_Lambert",GEOGCS["GCS_North_American_1983",DATUM[
3348 NAD_1983_CSRS_Statistics_Canada_Lambert PROJCS["NAD_1983_CSRS_Statistics_Canada_Lambert",GEOGCS["GCS_North_American_1983_C
3350 Pulkovo_1942_CS63_Zone_C0 PROJCS["Pulkovo_1942_CS63_Zone_C0",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulkovo_194
3353 Mhast_Onshore_UTM_Zone_32S PROJCS["Mhast_Onshore_UTM_Zone_32S",GEOGCS["GCS_Mhast_Onshore",DATUM["D_Mhast_O
3354 Mhast_Offshore_UTM_Zone_32S PROJCS["Mhast_Offshore_UTM_Zone_32S",GEOGCS["GCS_Mhast_Offshore",DATUM["D_Mhast_O
3355 Egypt_Gulf_of_Suez_S-650_TL_Red_Belt PROJCS["Egypt_Gulf_of_Suez_S-650_TL_Red_Belt",GEOGCS["GCS_Egypt_Gulf_of_Suez_S-650_T
3356 Grand_Cayman_1959_UTM_Zone_17N PROJCS["Grand_Cayman_1959_UTM_Zone_17N",GEOGCS["GCS_Grand_Cayman_1959",DATUM["
3357 Little_Cayman_1961_UTM_Zone_17N PROJCS["Little_Cayman_1961_UTM_Zone_17N",GEOGCS["GCS_Little_Cayman_1961",DATUM["D_
3358 NAD_1983_HARN_StatePlane_North_Carolina_FIPS_3200 PROJCS["NAD_1983_HARN_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_North_Ameri
3359 NAD_1983_HARN_StatePlane_North_Carolina_FIPS_3200_Feet PROJCS["NAD_1983_HARN_StatePlane_North_Carolina_FIPS_3200_Feet",GEOGCS["GCS_North_
3360 NAD_1983_HARN_StatePlane_South_Carolina_FIPS_3900 PROJCS["NAD_1983_HARN_StatePlane_South_Carolina_FIPS_3900",GEOGCS["GCS_North_Amer
3361 NAD_1983_HARN_StatePlane_South_Carolina_FIPS_3900_Feet_Intl PROJCS["NAD_1983_HARN_StatePlane_South_Carolina_FIPS_3900_Feet_Intl",GEOGCS["GCS_No
3362 NAD_1983_HARN_StatePlane_Pennsylvania_North_FIPS_3701 PROJCS["NAD_1983_HARN_StatePlane_Pennsylvania_North_FIPS_3701",GEOGCS["GCS_North_A
3363 NAD_1983_HARN_StatePlane_Pennsylvania_North_FIPS_3701_Feet PROJCS["NAD_1983_HARN_StatePlane_Pennsylvania_North_FIPS_3701_Feet",GEOGCS["GCS_No
3364 NAD_1983_HARN_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1983_HARN_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GCS_North_A
3365 NAD_1983_HARN_StatePlane_Pennsylvania_South_FIPS_3702_Feet PROJCS["NAD_1983_HARN_StatePlane_Pennsylvania_South_FIPS_3702_Feet",GEOGCS["GCS_N
3366 Hong_Kong_1963_Grid_System PROJCS["Hong_Kong_1963_Grid_System",GEOGCS["GCS_Hong_Kong_1963",DATUM["D_Hong_K
3367 IGN_Astro_1960_UTM_Zone_28N PROJCS["IGN_Astro_1960_UTM_Zone_28N",GEOGCS["GCS_IGN_Astro_1960",DATUM["D_IGN_As
3370 NAD_1927_UTM_Zone_59N PROJCS["NAD_1927_UTM_Zone_59N",GEOGCS["GCS_North_American_1927",DATUM["D_North_A
3374 FD_1954_UTM_Zone_29N PROJCS["FD_1954_UTM_Zone_29N",GEOGCS["GCS_FD_1954",DATUM["D_Faroe_Datum_1954",S
3375 GDM_2000_MRSO_Peninsular_Malaysia PROJCS["GDM_2000_MRSO_Peninsular_Malaysia",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_
3376 GDM_2000_BRSO_East_Malaysia PROJCS["GDM_2000_BRSO_East_Malaysia",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2000"

3377 GDM_2000_State_Cassini_Johor PROJCS["GDM_2000_State_Cassini_Johor",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2000",S

3378 GDM_2000_State_Cassini_Negeri_Sembilan_and_Melaka PROJCS["GDM_2000_State_Cassini_Negeri_Sembilan_and_Melaka",GEOGCS["GCS_GDM_2000",D
3379 GDM_2000_State_Cassini_Pahang PROJCS["GDM_2000_State_Cassini_Pahang",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2000
3380 GDM_2000_State_Cassini_Selangor PROJCS["GDM_2000_State_Cassini_Selangor",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_200
3381 GDM_2000_State_Cassini_Terengganu PROJCS["GDM_2000_State_Cassini_Terengganu",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2
3382 GDM_2000_State_Cassini_Pulau_Pinang_and_Seberang_Perai PROJCS["GDM_2000_State_Cassini_Pulau_Pinang_and_Seberang_Perai",GEOGCS["GCS_GDM_20
3383 GDM_2000_State_Cassini_Perlis PROJCS["GDM_2000_State_Cassini_Perlis",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2000",S
3384 GDM_2000_State_Cassini_Perak PROJCS["GDM_2000_State_Cassini_Perak",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2000",S
3385 GDM_2000_State_Cassini_Kelantan PROJCS["GDM_2000_State_Cassini_Kelantan",GEOGCS["GCS_GDM_2000",DATUM["D_GDM_2000
3386 KKJ_Finland_Zone_0 PROJCS["KKJ_Finland_Zone_0",GEOGCS["GCS_KKJ",DATUM["D_KKJ",SPHEROID["International_1
3387 KKJ_Finland_Zone_5 PROJCS["KKJ_Finland_Zone_5",GEOGCS["GCS_KKJ",DATUM["D_KKJ",SPHEROID["International_1
3388 Pulkovo_1942_Caspian_Sea_Mercator PROJCS["Pulkovo_1942_Caspian_Sea_Mercator",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulko
3391 Karbala_1979_Polservice_UTM_Zone_37N PROJCS["Karbala_1979_Polservice_UTM_Zone_37N",GEOGCS["GCS_Karbala_1979_Polservice",DA
3394 Nahrwan_1934_Iraq_Zone PROJCS["Nahrwan_1934_Iraq_Zone",GEOGCS["GCS_Nahrwan_1934",DATUM["D_Nahrwan_1934",
3395 WGS_1984_World_Mercator PROJCS["WGS_1984_World_Mercator",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHE
3396 PD/83_GK_Zone_3 PROJCS["PD/83_GK_Zone_3",GEOGCS["GCS_PD/83",DATUM["D_Potsdam_1983",SPHEROID["Bes
3397 PD/83_GK_Zone_4 PROJCS["PD/83_GK_Zone_4",GEOGCS["GCS_PD/83",DATUM["D_Potsdam_1983",SPHEROID["Bes
3398 RD/83_GK_Zone_4 PROJCS["RD/83_GK_Zone_4",GEOGCS["GCS_RD/83",DATUM["D_Rauenberg_1983",SPHEROID["B
3399 RD/83_GK_Zone_5 PROJCS["RD/83_GK_Zone_5",GEOGCS["GCS_RD/83",DATUM["D_Rauenberg_1983",SPHEROID["B
3400 NAD_1983_10TM_AEP_Forest PROJCS["NAD_1983_10TM_AEP_Forest",GEOGCS["GCS_North_American_1983",DATUM["D_North
3401 NAD_1983_10TM_AEP_Resource PROJCS["NAD_1983_10TM_AEP_Resource",GEOGCS["GCS_North_American_1983",DATUM["D_N
3402 NAD_1983_CSRS_10TM_AEP_Forest PROJCS["NAD_1983_CSRS_10TM_AEP_Forest",GEOGCS["GCS_North_American_1983_CSRS",DA
3403 NAD_1983_CSRS_10TM_AEP_Resource PROJCS["NAD_1983_CSRS_10TM_AEP_Resource",GEOGCS["GCS_North_American_1983_CSRS"
3404 NAD_1983_HARN_StatePlane_North_Carolina_FIPS_3200_Feet PROJCS["NAD_1983_HARN_StatePlane_North_Carolina_FIPS_3200_Feet",GEOGCS["GCS_North_
3405 VN_2000_UTM_Zone_48N PROJCS["VN_2000_UTM_Zone_48N",GEOGCS["GCS_VN_2000",DATUM["D_Vietnam_2000",SPHE
3406 VN_2000_UTM_Zone_49N PROJCS["VN_2000_UTM_Zone_49N",GEOGCS["GCS_VN_2000",DATUM["D_Vietnam_2000",SPHE
3407 Hong_Kong_1963_Grid_System PROJCS["Hong_Kong_1963_Grid_System",GEOGCS["GCS_Hong_Kong_1963",DATUM["D_Hong_K
3408 NSIDC_EASE_Grid_North PROJCS["NSIDC_EASE_Grid_North",GEOGCS["GCS_Sphere_International_1924_Authalic",DATUM[
3409 NSIDC_EASE_Grid_South PROJCS["NSIDC_EASE_Grid_South",GEOGCS["GCS_Sphere_International_1924_Authalic",DATUM
3410 NSIDC_EASE_Grid_Global PROJCS["NSIDC_EASE_Grid_Global",GEOGCS["GCS_Sphere_International_1924_Authalic",DATUM
3411 NSIDC_Sea_Ice_Polar_Stereographic_North PROJCS["NSIDC_Sea_Ice_Polar_Stereographic_North",GEOGCS["GCS_Hughes_1980",DATUM["D_
3412 NSIDC_Sea_Ice_Polar_Stereographic_South PROJCS["NSIDC_Sea_Ice_Polar_Stereographic_South",GEOGCS["GCS_Hughes_1980",DATUM["D_
3413 WGS_1984_NSIDC_Sea_Ice_Polar_Stereographic_North PROJCS["WGS_1984_NSIDC_Sea_Ice_Polar_Stereographic_North",GEOGCS["GCS_WGS_1984",D
3414 SVY21_Singapore_TM PROJCS["SVY21_Singapore_TM",GEOGCS["GCS_SVY21",DATUM["D_SVY21",SPHEROID["WGS_1
3415 WGS_1972_BE_South_China_Sea_Lambert PROJCS["WGS_1972_BE_South_China_Sea_Lambert",GEOGCS["GCS_WGS_1972_BE",DATUM["D
3416 ETRS_1989_Austria_Lambert PROJCS["ETRS_1989_Austria_Lambert",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SP
3417 NAD_1983_StatePlane_Iowa_North_FIPS_1401_Feet PROJCS["NAD_1983_StatePlane_Iowa_North_FIPS_1401_Feet",GEOGCS["GCS_North_American_1
3418 NAD_1983_StatePlane_Iowa_South_FIPS_1402_Feet PROJCS["NAD_1983_StatePlane_Iowa_South_FIPS_1402_Feet",GEOGCS["GCS_North_American_1
3419 NAD_1983_StatePlane_Kansas_North_FIPS_1501_Feet PROJCS["NAD_1983_StatePlane_Kansas_North_FIPS_1501_Feet",GEOGCS["GCS_North_American
3420 NAD_1983_StatePlane_Kansas_South_FIPS_1502_Feet PROJCS["NAD_1983_StatePlane_Kansas_South_FIPS_1502_Feet",GEOGCS["GCS_North_America
3421 NAD_1983_StatePlane_Nevada_East_FIPS_2701_Feet PROJCS["NAD_1983_StatePlane_Nevada_East_FIPS_2701_Feet",GEOGCS["GCS_North_American
3422 NAD_1983_StatePlane_Nevada_Central_FIPS_2702_Feet PROJCS["NAD_1983_StatePlane_Nevada_Central_FIPS_2702_Feet",GEOGCS["GCS_North_Americ
3423 NAD_1983_StatePlane_Nevada_West_FIPS_2703_Feet PROJCS["NAD_1983_StatePlane_Nevada_West_FIPS_2703_Feet",GEOGCS["GCS_North_American
3424 NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet PROJCS["NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet",GEOGCS["GCS_North_American_
3425 NAD_1983_HARN_StatePlane_Iowa_North_FIPS_1401_Feet PROJCS["NAD_1983_HARN_StatePlane_Iowa_North_FIPS_1401_Feet",GEOGCS["GCS_North_Ame
3426 NAD_1983_HARN_StatePlane_Iowa_South_FIPS_1402_Feet PROJCS["NAD_1983_HARN_StatePlane_Iowa_South_FIPS_1402_Feet",GEOGCS["GCS_North_Am
3427 NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501_Feet PROJCS["NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501_Feet",GEOGCS["GCS_North_A
3428 NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502_Feet PROJCS["NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502_Feet",GEOGCS["GCS_North_A
3429 NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701_Feet PROJCS["NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701_Feet",GEOGCS["GCS_North_Am
3430 NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702_Feet PROJCS["NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702_Feet",GEOGCS["GCS_North_

3431 NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703_Feet PROJCS["NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703_Feet",GEOGCS["GCS_North_A

3432 NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900_Feet PROJCS["NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900_Feet",GEOGCS["GCS_North_Am
3433 NAD_1983_StatePlane_Arkansas_North_FIPS_0301_Feet PROJCS["NAD_1983_StatePlane_Arkansas_North_FIPS_0301_Feet",GEOGCS["GCS_North_Americ
3434 NAD_1983_StatePlane_Arkansas_South_FIPS_0302_Feet PROJCS["NAD_1983_StatePlane_Arkansas_South_FIPS_0302_Feet",GEOGCS["GCS_North_Americ
3435 NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet PROJCS["NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet",GEOGCS["GCS_North_American_
3436 NAD_1983_StatePlane_Illinois_West_FIPS_1202_Feet PROJCS["NAD_1983_StatePlane_Illinois_West_FIPS_1202_Feet",GEOGCS["GCS_North_American_
3437 NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feet PROJCS["NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feet",GEOGCS["GCS_North_Americ
3438 NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet PROJCS["NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet",GEOGCS["GCS_North_American
3439 PDO_1993_UTM_Zone_39N PROJCS["PDO_1993_UTM_Zone_39N",GEOGCS["GCS_PDO_1993",DATUM["D_PDO_1993",SPHE
3440 PDO_1993_UTM_Zone_40N PROJCS["PDO_1993_UTM_Zone_40N",GEOGCS["GCS_PDO_1993",DATUM["D_PDO_1993",SPHE
3441 NAD_1983_HARN_StatePlane_Arkansas_North_FIPS_0301_Feet PROJCS["NAD_1983_HARN_StatePlane_Arkansas_North_FIPS_0301_Feet",GEOGCS["GCS_North_
3442 NAD_1983_HARN_StatePlane_Arkansas_South_FIPS_0302_Feet PROJCS["NAD_1983_HARN_StatePlane_Arkansas_South_FIPS_0302_Feet",GEOGCS["GCS_North
3443 NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201_Feet PROJCS["NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201_Feet",GEOGCS["GCS_North_Am
3444 NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202_Feet PROJCS["NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202_Feet",GEOGCS["GCS_North_Am
3445 NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800_Feet PROJCS["NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800_Feet",GEOGCS["GCS_North
3446 NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800_Feet PROJCS["NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800_Feet",GEOGCS["GCS_North_A
3447 Belge_Lambert_2005 PROJCS["Belge_Lambert_2005",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID
3448 JAD_2001_Jamaica_Grid PROJCS["JAD_2001_Jamaica_Grid",GEOGCS["GCS_JAD_2001",DATUM["D_Jamaica_2001",SPHER
3449 JAD_2001_UTM_Zone_17N PROJCS["JAD_2001_UTM_Zone_17N",GEOGCS["GCS_JAD_2001",DATUM["D_Jamaica_2001",SPH
3450 JAD_2001_UTM_Zone_18N PROJCS["JAD_2001_UTM_Zone_18N",GEOGCS["GCS_JAD_2001",DATUM["D_Jamaica_2001",SPH
3451 NAD_1983_StatePlane_Louisiana_North_FIPS_1701_Feet PROJCS["NAD_1983_StatePlane_Louisiana_North_FIPS_1701_Feet",GEOGCS["GCS_North_Americ
3452 NAD_1983_StatePlane_Louisiana_South_FIPS_1702_Feet PROJCS["NAD_1983_StatePlane_Louisiana_South_FIPS_1702_Feet",GEOGCS["GCS_North_Americ
3453 NAD_1983_StatePlane_Louisiana_Offshore_FIPS_1703_Feet PROJCS["NAD_1983_StatePlane_Louisiana_Offshore_FIPS_1703_Feet",GEOGCS["GCS_North_Am
3454 NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet PROJCS["NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet",GEOGCS["GCS_North_Am
3455 NAD_1983_StatePlane_South_Dakota_South_FIPS_4002_Feet PROJCS["NAD_1983_StatePlane_South_Dakota_South_FIPS_4002_Feet",GEOGCS["GCS_North_A
3456 NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701_Feet PROJCS["NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701_Feet",GEOGCS["GCS_North
3457 NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702_Feet PROJCS["NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702_Feet",GEOGCS["GCS_North
3458 NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001_Feet PROJCS["NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001_Feet",GEOGCS["GCS_N
3459 NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002_Feet PROJCS["NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002_Feet",GEOGCS["GCS_N
3460 Fiji_1986_Fiji_Map_Grid PROJCS["Fiji_1986_Fiji_Map_Grid",GEOGCS["GCS_Fiji_1986",DATUM["D_Fiji_1986",SPHEROID["W
3463 NAD_1983_Maine_2000_Central_Zone PROJCS["NAD_1983_Maine_2000_Central_Zone",GEOGCS["GCS_North_American_1983",DATUM["
3464 NAD_1983_HARN_Maine_2000_Central_Zone PROJCS["NAD_1983_HARN_Maine_2000_Central_Zone",GEOGCS["GCS_North_American_1983_H
3465 NAD_1983_NSRS2007_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1983_NSRS2007_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_NAD_19
3466 NAD_1983_NSRS2007_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1983_NSRS2007_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_NAD_19
3467 NAD_1983_NSRS2007_Alaska_Albers PROJCS["NAD_1983_NSRS2007_Alaska_Albers",GEOGCS["GCS_NAD_1983_NSRS2007",DATUM[
3468 NAD_1983_NSRS2007_StatePlane_Alaska_1_FIPS_5001 PROJCS["NAD_1983_NSRS2007_StatePlane_Alaska_1_FIPS_5001",GEOGCS["GCS_NAD_1983_N
3477 NAD_1983_NSRS2007_StatePlane_Alaska_10_FIPS_5010 PROJCS["NAD_1983_NSRS2007_StatePlane_Alaska_10_FIPS_5010",GEOGCS["GCS_NAD_1983_
3478 NAD_1983_NSRS2007_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1983_NSRS2007_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_NAD_1
3479 NAD_1983_NSRS2007_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl",GEOGCS["GCS_
3480 NAD_1983_NSRS2007_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1983_NSRS2007_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_NAD_198
3481 NAD_1983_NSRS2007_StatePlane_Arizona_East_FIPS_0201_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Arizona_East_FIPS_0201_Ft_Intl",GEOGCS["GCS_NA
3482 NAD_1983_NSRS2007_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1983_NSRS2007_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_NAD_198
3483 NAD_1983_NSRS2007_StatePlane_Arizona_West_FIPS_0203_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Arizona_West_FIPS_0203_Ft_Intl",GEOGCS["GCS_N
3484 NAD_1983_NSRS2007_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1983_NSRS2007_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_NAD_1

3485 NAD_1983_NSRS2007_StatePlane_Arkansas_North_FIPS_0301_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Arkansas_North_FIPS_0301_Ft_US",GEOGCS["GCS_

3486 NAD_1983_NSRS2007_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1983_NSRS2007_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_NAD_1
3487 NAD_1983_NSRS2007_StatePlane_Arkansas_South_FIPS_0302_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Arkansas_South_FIPS_0302_Ft_US",GEOGCS["GCS
3488 NAD_1983_NSRS2007_California_Teale_Albers PROJCS["NAD_1983_NSRS2007_California_Teale_Albers",GEOGCS["GCS_NAD_1983_NSRS2007"
3489 NAD_1983_NSRS2007_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1983_NSRS2007_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_NAD_1983_
3490 NAD_1983_NSRS2007_StatePlane_California_I_FIPS_0401_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_California_I_FIPS_0401_Ft_US",GEOGCS["GCS_NAD
3491 NAD_1983_NSRS2007_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1983_NSRS2007_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_NAD_1983
3492 NAD_1983_NSRS2007_StatePlane_California_II_FIPS_0402_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_California_II_FIPS_0402_Ft_US",GEOGCS["GCS_NA
3493 NAD_1983_NSRS2007_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1983_NSRS2007_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_NAD_1983
3494 NAD_1983_NSRS2007_StatePlane_California_III_FIPS_0403_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_California_III_FIPS_0403_Ft_US",GEOGCS["GCS_NA
3495 NAD_1983_NSRS2007_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1983_NSRS2007_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_NAD_1983
3496 NAD_1983_NSRS2007_StatePlane_California_IV_FIPS_0404_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_California_IV_FIPS_0404_Ft_US",GEOGCS["GCS_NA
3497 NAD_1983_NSRS2007_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1983_NSRS2007_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_NAD_1983
3498 NAD_1983_NSRS2007_StatePlane_California_V_FIPS_0405_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_California_V_FIPS_0405_Ft_US",GEOGCS["GCS_NA
3499 NAD_1983_NSRS2007_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1983_NSRS2007_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_NAD_1983
3500 NAD_1983_NSRS2007_StatePlane_California_VI_FIPS_0406_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_California_VI_FIPS_0406_Ft_US",GEOGCS["GCS_NA
3501 NAD_1983_NSRS2007_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1983_NSRS2007_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_NAD_
3502 NAD_1983_NSRS2007_StatePlane_Colorado_Central_FIPS_0502_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Colorado_Central_FIPS_0502_Ft_US",GEOGCS["GCS
3503 NAD_1983_NSRS2007_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1983_NSRS2007_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_NAD_1
3504 NAD_1983_NSRS2007_StatePlane_Colorado_North_FIPS_0501_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Colorado_North_FIPS_0501_Ft_US",GEOGCS["GCS_
3505 NAD_1983_NSRS2007_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1983_NSRS2007_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_NAD_1
3506 NAD_1983_NSRS2007_StatePlane_Colorado_South_FIPS_0503_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Colorado_South_FIPS_0503_Ft_US",GEOGCS["GCS_
3507 NAD_1983_NSRS2007_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1983_NSRS2007_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_NAD_1983
3508 NAD_1983_NSRS2007_StatePlane_Connecticut_FIPS_0600_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Connecticut_FIPS_0600_Ft_US",GEOGCS["GCS_NAD
3509 NAD_1983_NSRS2007_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1983_NSRS2007_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_NAD_1983_N
3510 NAD_1983_NSRS2007_StatePlane_Delaware_FIPS_0700_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Delaware_FIPS_0700_Ft_US",GEOGCS["GCS_NAD_
3511 NAD_1983_NSRS2007_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1983_NSRS2007_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_NAD_1983
3512 NAD_1983_NSRS2007_StatePlane_Florida_East_FIPS_0901_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Florida_East_FIPS_0901_Ft_US",GEOGCS["GCS_NA
3513 NAD_1983_NSRS2007_Florida_GDL_Albers PROJCS["NAD_1983_NSRS2007_Florida_GDL_Albers",GEOGCS["GCS_NAD_1983_NSRS2007",DA
3514 NAD_1983_NSRS2007_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1983_NSRS2007_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_NAD_198
3515 NAD_1983_NSRS2007_StatePlane_Florida_North_FIPS_0903_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Florida_North_FIPS_0903_Ft_US",GEOGCS["GCS_N
3516 NAD_1983_NSRS2007_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1983_NSRS2007_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_NAD_198
3517 NAD_1983_NSRS2007_StatePlane_Florida_West_FIPS_0902_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Florida_West_FIPS_0902_Ft_US",GEOGCS["GCS_NA
3518 NAD_1983_NSRS2007_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1983_NSRS2007_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_NAD_198
3519 NAD_1983_NSRS2007_StatePlane_Georgia_East_FIPS_1001_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Georgia_East_FIPS_1001_Ft_US",GEOGCS["GCS_N
3520 NAD_1983_NSRS2007_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1983_NSRS2007_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_NAD_19
3521 NAD_1983_NSRS2007_StatePlane_Georgia_West_FIPS_1002_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Georgia_West_FIPS_1002_Ft_US",GEOGCS["GCS_N
3522 NAD_1983_NSRS2007_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1983_NSRS2007_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_NAD_198
3523 NAD_1983_NSRS2007_StatePlane_Idaho_Central_FIPS_1102_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Idaho_Central_FIPS_1102_Ft_US",GEOGCS["GCS_N
3524 NAD_1983_NSRS2007_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1983_NSRS2007_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_NAD_1983_
3525 NAD_1983_NSRS2007_StatePlane_Idaho_East_FIPS_1101_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Idaho_East_FIPS_1101_Ft_US",GEOGCS["GCS_NAD
3526 NAD_1983_NSRS2007_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1983_NSRS2007_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_NAD_1983
3527 NAD_1983_NSRS2007_StatePlane_Idaho_West_FIPS_1103_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Idaho_West_FIPS_1103_Ft_US",GEOGCS["GCS_NAD
3528 NAD_1983_NSRS2007_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1983_NSRS2007_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_NAD_1983
3529 NAD_1983_NSRS2007_StatePlane_Illinois_East_FIPS_1201_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Illinois_East_FIPS_1201_Ft_US",GEOGCS["GCS_NA
3530 NAD_1983_NSRS2007_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1983_NSRS2007_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_NAD_1983
3531 NAD_1983_NSRS2007_StatePlane_Illinois_West_FIPS_1202_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Illinois_West_FIPS_1202_Ft_US",GEOGCS["GCS_NA
3532 NAD_1983_NSRS2007_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1983_NSRS2007_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_NAD_198
3533 NAD_1983_NSRS2007_StatePlane_Indiana_East_FIPS_1301_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Indiana_East_FIPS_1301_Ft_US",GEOGCS["GCS_NA
3534 NAD_1983_NSRS2007_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1983_NSRS2007_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_NAD_198
3535 NAD_1983_NSRS2007_StatePlane_Indiana_West_FIPS_1302_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Indiana_West_FIPS_1302_Ft_US",GEOGCS["GCS_N
3536 NAD_1983_NSRS2007_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1983_NSRS2007_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_NAD_1983_
3537 NAD_1983_NSRS2007_StatePlane_Iowa_North_FIPS_1401_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Iowa_North_FIPS_1401_Ft_US",GEOGCS["GCS_NAD
3538 NAD_1983_NSRS2007_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1983_NSRS2007_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_NAD_1983

3539 NAD_1983_NSRS2007_StatePlane_Iowa_South_FIPS_1402_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Iowa_South_FIPS_1402_Ft_US",GEOGCS["GCS_NAD

3540 NAD_1983_NSRS2007_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1983_NSRS2007_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_NAD_19
3541 NAD_1983_NSRS2007_StatePlane_Kansas_North_FIPS_1501_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Kansas_North_FIPS_1501_Ft_US",GEOGCS["GCS_N
3542 NAD_1983_NSRS2007_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1983_NSRS2007_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_NAD_19
3543 NAD_1983_NSRS2007_StatePlane_Kansas_South_FIPS_1502_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Kansas_South_FIPS_1502_Ft_US",GEOGCS["GCS_N
3544 NAD_1983_NSRS2007_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_NSRS2007_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_NAD_1
3545 NAD_1983_NSRS2007_StatePlane_Kentucky_North_FIPS_1601_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Kentucky_North_FIPS_1601_Ft_US",GEOGCS["GCS_
3546 NAD_1983_NSRS2007_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_NSRS2007_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_NAD_1983_N
3547 NAD_1983_NSRS2007_StatePlane_Kentucky_FIPS_1600_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Kentucky_FIPS_1600_Ft_US",GEOGCS["GCS_NAD_
3548 NAD_1983_NSRS2007_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1983_NSRS2007_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_NAD_1
3549 NAD_1983_NSRS2007_StatePlane_Kentucky_South_FIPS_1602_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Kentucky_South_FIPS_1602_Ft_US",GEOGCS["GCS
3550 NAD_1983_NSRS2007_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1983_NSRS2007_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_NAD_1
3551 NAD_1983_NSRS2007_StatePlane_Louisiana_North_FIPS_1701_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Louisiana_North_FIPS_1701_Ft_US",GEOGCS["GCS
3552 NAD_1983_NSRS2007_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1983_NSRS2007_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_NAD_
3553 NAD_1983_NSRS2007_StatePlane_Louisiana_South_FIPS_1702_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Louisiana_South_FIPS_1702_Ft_US",GEOGCS["GCS
3554 NAD_1983_NSRS2007_Maine_2000_Central_Zone PROJCS["NAD_1983_NSRS2007_Maine_2000_Central_Zone",GEOGCS["GCS_NAD_1983_NSRS20
3555 NAD_1983_NSRS2007_Maine_2000_East_Zone PROJCS["NAD_1983_NSRS2007_Maine_2000_East_Zone",GEOGCS["GCS_NAD_1983_NSRS2007
3556 NAD_1983_NSRS2007_Maine_2000_West_Zone PROJCS["NAD_1983_NSRS2007_Maine_2000_West_Zone",GEOGCS["GCS_NAD_1983_NSRS2007
3557 NAD_1983_NSRS2007_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1983_NSRS2007_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_NAD_1983
3558 NAD_1983_NSRS2007_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1983_NSRS2007_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_NAD_1983
3559 NAD_1983_NSRS2007_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1983_NSRS2007_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_NAD_1983_N
3560 NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet PROJCS["NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet",GEOGCS["GCS_North_American_1
3561 Old_Hawaiian_StatePlane_Hawaii_1_FIPS_5101 PROJCS["Old_Hawaiian_StatePlane_Hawaii_1_FIPS_5101",GEOGCS["GCS_Old_Hawaiian",DATUM
3566 NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet PROJCS["NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet",GEOGCS["GCS_North_American
3567 NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet PROJCS["NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet",GEOGCS["GCS_North_American_1
3568 NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301_Feet PROJCS["NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301_Feet",GEOGCS["GCS_North_Ame
3569 NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302_Feet PROJCS["NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302_Feet",GEOGCS["GCS_North_Am
3570 NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303_Feet PROJCS["NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303_Feet",GEOGCS["GCS_North_Am
3571 WGS_1984_North_Pole_LAEA_Bering_Sea PROJCS["WGS_1984_North_Pole_LAEA_Bering_Sea",GEOGCS["GCS_WGS_1984",DATUM["D_WG
3572 WGS_1984_North_Pole_LAEA_Alaska PROJCS["WGS_1984_North_Pole_LAEA_Alaska",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_19
3573 WGS_1984_North_Pole_LAEA_Canada PROJCS["WGS_1984_North_Pole_LAEA_Canada",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1
3574 WGS_1984_North_Pole_LAEA_Atlantic PROJCS["WGS_1984_North_Pole_LAEA_Atlantic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1
3575 WGS_1984_North_Pole_LAEA_Europe PROJCS["WGS_1984_North_Pole_LAEA_Europe",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1
3576 WGS_1984_North_Pole_LAEA_Russia PROJCS["WGS_1984_North_Pole_LAEA_Russia",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1
3577 GDA_1994_Australia_Albers PROJCS["GDA_1994_Australia_Albers",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHER
3578 NAD_1983_Yukon_Albers PROJCS["NAD_1983_Yukon_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_North_Am
3579 NAD_1983_CSRS_Yukon_Albers PROJCS["NAD_1983_CSRS_Yukon_Albers",GEOGCS["GCS_North_American_1983_CSRS",DATUM
3580 NAD_1983_Northwest_Territories_Lambert PROJCS["NAD_1983_Northwest_Territories_Lambert",GEOGCS["GCS_North_American_1983",DATU
3581 NAD_1983_CSRS_Northwest_Territories_Lambert PROJCS["NAD_1983_CSRS_Northwest_Territories_Lambert",GEOGCS["GCS_North_American_1983
3582 NAD_1983_NSRS2007_StatePlane_Maryland_FIPS_1900_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Maryland_FIPS_1900_Ft_US",GEOGCS["GCS_NAD_
3583 NAD_1983_NSRS2007_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1983_NSRS2007_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["GCS_N
3584 NAD_1983_NSRS2007_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS PROJCS["NAD_1983_NSRS2007_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS",GEOGCS["GCS
3585 NAD_1983_NSRS2007_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1983_NSRS2007_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS["GCS
3586 NAD_1983_NSRS2007_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS PROJCS["NAD_1983_NSRS2007_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS",GEOGCS["G
3587 NAD_1983_NSRS2007_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1983_NSRS2007_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_NAD_
3588 NAD_1983_NSRS2007_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl",GEOGCS["GCS
3589 NAD_1983_NSRS2007_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1983_NSRS2007_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_NAD_19
3590 NAD_1983_NSRS2007_StatePlane_Michigan_North_FIPS_2111_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Michigan_North_FIPS_2111_Ft_Intl",GEOGCS["GCS_
3591 NAD_1983_NSRS2007_Michigan_GeoRef_Meters PROJCS["NAD_1983_NSRS2007_Michigan_GeoRef_Meters",GEOGCS["GCS_NAD_1983_NSRS200
3592 NAD_1983_NSRS2007_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1983_NSRS2007_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_NAD_1

3593 NAD_1983_NSRS2007_StatePlane_Michigan_South_FIPS_2113_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Michigan_South_FIPS_2113_Ft_Intl",GEOGCS["GCS_

3594 NAD_1983_NSRS2007_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1983_NSRS2007_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS_NAD
3595 NAD_1983_NSRS2007_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1983_NSRS2007_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_NAD_
3596 NAD_1983_NSRS2007_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1983_NSRS2007_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_NAD_
3597 NAD_1983_NSRS2007_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1983_NSRS2007_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_NAD_1
3598 NAD_1983_NSRS2007_StatePlane_Mississippi_East_FIPS_2301_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Mississippi_East_FIPS_2301_Ft_US",GEOGCS["GCS
3599 NAD_1983_NSRS2007_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1983_NSRS2007_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_NAD_
3600 NAD_1983_NSRS2007_StatePlane_Mississippi_West_FIPS_2302_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Mississippi_West_FIPS_2302_Ft_US",GEOGCS["GCS
3601 NAD_1983_NSRS2007_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1983_NSRS2007_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_NAD_
3602 NAD_1983_NSRS2007_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1983_NSRS2007_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_NAD_198
3603 NAD_1983_NSRS2007_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1983_NSRS2007_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_NAD_19
3604 NAD_1983_NSRS2007_StatePlane_Montana_FIPS_2500 PROJCS["NAD_1983_NSRS2007_StatePlane_Montana_FIPS_2500",GEOGCS["GCS_NAD_1983_NS
3605 NAD_1983_NSRS2007_StatePlane_Montana_FIPS_2500_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Montana_FIPS_2500_Ft_Intl",GEOGCS["GCS_NAD_1
3606 NAD_1983_NSRS2007_StatePlane_Nebraska_FIPS_2600 PROJCS["NAD_1983_NSRS2007_StatePlane_Nebraska_FIPS_2600",GEOGCS["GCS_NAD_1983_N
3607 NAD_1983_NSRS2007_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1983_NSRS2007_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_NAD_1
3608 NAD_1983_NSRS2007_StatePlane_Nevada_Central_FIPS_2702_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Nevada_Central_FIPS_2702_Ft_US",GEOGCS["GCS_
3609 NAD_1983_NSRS2007_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1983_NSRS2007_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_NAD_198
3610 NAD_1983_NSRS2007_StatePlane_Nevada_East_FIPS_2701_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Nevada_East_FIPS_2701_Ft_US",GEOGCS["GCS_N
3611 NAD_1983_NSRS2007_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1983_NSRS2007_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_NAD_198
3612 NAD_1983_NSRS2007_StatePlane_Nevada_West_FIPS_2703_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Nevada_West_FIPS_2703_Ft_US",GEOGCS["GCS_N
3613 NAD_1983_NSRS2007_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1983_NSRS2007_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_NAD_1
3614 NAD_1983_NSRS2007_StatePlane_New_Hampshire_FIPS_2800_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_Hampshire_FIPS_2800_Ft_US",GEOGCS["GCS
3615 NAD_1983_NSRS2007_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1983_NSRS2007_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_NAD_1983
3616 NAD_1983_NSRS2007_StatePlane_New_Jersey_FIPS_2900_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_Jersey_FIPS_2900_Ft_US",GEOGCS["GCS_NA
3617 NAD_1983_NSRS2007_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1983_NSRS2007_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["GCS_N
3618 NAD_1983_NSRS2007_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US",GEOGCS["
3619 NAD_1983_NSRS2007_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1983_NSRS2007_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS_NAD
3620 NAD_1983_NSRS2007_StatePlane_New_Mexico_East_FIPS_3001_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_Mexico_East_FIPS_3001_Ft_US",GEOGCS["GC
3621 NAD_1983_NSRS2007_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1983_NSRS2007_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS_NAD
3622 NAD_1983_NSRS2007_StatePlane_New_Mexico_West_FIPS_3003_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_Mexico_West_FIPS_3003_Ft_US",GEOGCS["GC
3623 NAD_1983_NSRS2007_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS_NAD
3624 NAD_1983_NSRS2007_StatePlane_New_York_Central_FIPS_3102_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_Central_FIPS_3102_Ft_US",GEOGCS["GC
3625 NAD_1983_NSRS2007_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_NAD_1
3626 NAD_1983_NSRS2007_StatePlane_New_York_East_FIPS_3101_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_East_FIPS_3101_Ft_US",GEOGCS["GCS_
3627 NAD_1983_NSRS2007_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GCS_
3628 NAD_1983_NSRS2007_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US",GEOGCS["G
3629 NAD_1983_NSRS2007_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_NAD_1
3630 NAD_1983_NSRS2007_StatePlane_New_York_West_FIPS_3103_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_New_York_West_FIPS_3103_Ft_US",GEOGCS["GCS
3631 NAD_1983_NSRS2007_StatePlane_North_Carolina_FIPS_3200 PROJCS["NAD_1983_NSRS2007_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_NAD_19
3632 NAD_1983_NSRS2007_StatePlane_North_Carolina_FIPS_3200_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_North_Carolina_FIPS_3200_Ft_US",GEOGCS["GCS_
3633 NAD_1983_NSRS2007_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1983_NSRS2007_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GCS_NA
3634 NAD_1983_NSRS2007_StatePlane_North_Dakota_North_FIPS_3301_FtI PROJCS["NAD_1983_NSRS2007_StatePlane_North_Dakota_North_FIPS_3301_FtI",GEOGCS["GCS
3635 NAD_1983_NSRS2007_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1983_NSRS2007_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GCS_NA
3636 NAD_1983_NSRS2007_StatePlane_North_Dakota_South_FIPS_3302_FtI PROJCS["NAD_1983_NSRS2007_StatePlane_North_Dakota_South_FIPS_3302_FtI",GEOGCS["GCS
3637 NAD_1983_NSRS2007_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1983_NSRS2007_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_NAD_1983_
3638 NAD_1983_NSRS2007_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1983_NSRS2007_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_NAD_1983
3639 NAD_1983_NSRS2007_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1983_NSRS2007_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_NAD_
3640 NAD_1983_NSRS2007_StatePlane_Oklahoma_North_FIPS_3501_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Oklahoma_North_FIPS_3501_Ft_US",GEOGCS["GCS
3641 NAD_1983_NSRS2007_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1983_NSRS2007_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_NAD_
3642 NAD_1983_NSRS2007_StatePlane_Oklahoma_South_FIPS_3502_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Oklahoma_South_FIPS_3502_Ft_US",GEOGCS["GCS
3643 NAD_1983_NSRS2007_Oregon_Statewide_Lambert PROJCS["NAD_1983_NSRS2007_Oregon_Statewide_Lambert",GEOGCS["GCS_NAD_1983_NSRS2
3644 NAD_1983_NSRS2007_Oregon_Statewide_Lambert_Ft_Intl PROJCS["NAD_1983_NSRS2007_Oregon_Statewide_Lambert_Ft_Intl",GEOGCS["GCS_NAD_1983_
3645 NAD_1983_NSRS2007_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_NSRS2007_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_NAD_19
3646 NAD_1983_NSRS2007_StatePlane_Oregon_North_FIPS_3601_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Oregon_North_FIPS_3601_Ft_Intl",GEOGCS["GCS_N

3647 NAD_1983_NSRS2007_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_NSRS2007_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_NAD_19

3648 NAD_1983_NSRS2007_StatePlane_Oregon_South_FIPS_3602_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Oregon_South_FIPS_3602_Ft_Intl",GEOGCS["GCS_N
3649 NAD_1983_NSRS2007_StatePlane_Pennsylvania_North_FIPS_3701 PROJCS["NAD_1983_NSRS2007_StatePlane_Pennsylvania_North_FIPS_3701",GEOGCS["GCS_NA
3650 NAD_1983_NSRS2007_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US",GEOGCS["G
3651 NAD_1983_NSRS2007_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1983_NSRS2007_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GCS_NA
3652 NAD_1983_NSRS2007_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US",GEOGCS["G
3653 NAD_1983_NSRS2007_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1983_NSRS2007_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_NAD_198
3654 NAD_1983_NSRS2007_StatePlane_Rhode_Island_FIPS_3800_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Rhode_Island_FIPS_3800_Ft_US",GEOGCS["GCS_N
3655 NAD_1983_NSRS2007_StatePlane_South_Carolina_FIPS_3900 PROJCS["NAD_1983_NSRS2007_StatePlane_South_Carolina_FIPS_3900",GEOGCS["GCS_NAD_1
3656 NAD_1983_NSRS2007_StatePlane_South_Carolina_FIPS_3900_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_South_Carolina_FIPS_3900_Ft_Intl",GEOGCS["GCS_
3657 NAD_1983_NSRS2007_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1983_NSRS2007_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GCS_NA
3658 NAD_1983_NSRS2007_StatePlane_South_Dakota_North_FIPS_4001_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_South_Dakota_North_FIPS_4001_Ft_US",GEOGCS["G
3659 NAD_1983_NSRS2007_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1983_NSRS2007_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["GCS_N
3660 NAD_1983_NSRS2007_StatePlane_South_Dakota_South_FIPS_4002_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_South_Dakota_South_FIPS_4002_Ft_US",GEOGCS["
3661 NAD_1983_NSRS2007_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1983_NSRS2007_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_NAD_1983_
3662 NAD_1983_NSRS2007_StatePlane_Tennessee_FIPS_4100_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Tennessee_FIPS_4100_Ft_US",GEOGCS["GCS_NAD
3663 NAD_1983_NSRS2007_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_NAD_19
3664 NAD_1983_NSRS2007_StatePlane_Texas_Central_FIPS_4203_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_Central_FIPS_4203_Ft_US",GEOGCS["GCS_N
3665 NAD_1983_NSRS2007_Texas_Centric_Mapping_System_Albers PROJCS["NAD_1983_NSRS2007_Texas_Centric_Mapping_System_Albers",GEOGCS["GCS_NAD_1
3666 NAD_1983_NSRS2007_Texas_Centric_Mapping_System_Lambert PROJCS["NAD_1983_NSRS2007_Texas_Centric_Mapping_System_Lambert",GEOGCS["GCS_NAD_
3667 NAD_1983_NSRS2007_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_NAD_1983
3668 NAD_1983_NSRS2007_StatePlane_Texas_North_FIPS_4201_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_North_FIPS_4201_Ft_US",GEOGCS["GCS_NA
3669 NAD_1983_NSRS2007_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["GCS_N
3670 NAD_1983_NSRS2007_StatePlane_Texas_North_Central_FIPS_4202_FtUS PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_North_Central_FIPS_4202_FtUS",GEOGCS["G
3671 NAD_1983_NSRS2007_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_NAD_198
3672 NAD_1983_NSRS2007_StatePlane_Texas_South_FIPS_4205_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_South_FIPS_4205_Ft_US",GEOGCS["GCS_NA
3673 NAD_1983_NSRS2007_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["GCS_N
3674 NAD_1983_NSRS2007_StatePlane_Texas_South_Central_FIPS_4204_FtUS PROJCS["NAD_1983_NSRS2007_StatePlane_Texas_South_Central_FIPS_4204_FtUS",GEOGCS["G
3675 NAD_1983_NSRS2007_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_NAD_198
3676 NAD_1983_NSRS2007_StatePlane_Utah_Central_FIPS_4302_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_Central_FIPS_4302_Ft_Intl",GEOGCS["GCS_NA
3677 NAD_1983_NSRS2007_StatePlane_Utah_Central_FIPS_4302_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_Central_FIPS_4302_Ft_US",GEOGCS["GCS_NA
3678 NAD_1983_NSRS2007_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_NAD_1983_
3679 NAD_1983_NSRS2007_StatePlane_Utah_North_FIPS_4301_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_North_FIPS_4301_Ft_Intl",GEOGCS["GCS_NAD
3680 NAD_1983_NSRS2007_StatePlane_Utah_North_FIPS_4301_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_North_FIPS_4301_Ft_US",GEOGCS["GCS_NAD
3681 NAD_1983_NSRS2007_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_NAD_1983
3682 NAD_1983_NSRS2007_StatePlane_Utah_South_FIPS_4303_Ft_Intl PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_South_FIPS_4303_Ft_Intl",GEOGCS["GCS_NAD
3683 NAD_1983_NSRS2007_StatePlane_Utah_South_FIPS_4303_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Utah_South_FIPS_4303_Ft_US",GEOGCS["GCS_NAD
3684 NAD_1983_NSRS2007_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1983_NSRS2007_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_NAD_1983_NS
3685 NAD_1983_NSRS2007_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1983_NSRS2007_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_NAD_19
3686 NAD_1983_NSRS2007_StatePlane_Virginia_North_FIPS_4501_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Virginia_North_FIPS_4501_Ft_US",GEOGCS["GCS_N
3687 NAD_1983_NSRS2007_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1983_NSRS2007_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_NAD_19
3688 NAD_1983_NSRS2007_StatePlane_Virginia_South_FIPS_4502_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Virginia_South_FIPS_4502_Ft_US",GEOGCS["GCS_N
3689 NAD_1983_NSRS2007_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1983_NSRS2007_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS_NAD
3690 NAD_1983_NSRS2007_StatePlane_Washington_North_FIPS_4601_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Washington_North_FIPS_4601_Ft_US",GEOGCS["GC
3691 NAD_1983_NSRS2007_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1983_NSRS2007_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS_NAD
3692 NAD_1983_NSRS2007_StatePlane_Washington_South_FIPS_4602_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Washington_South_FIPS_4602_Ft_US",GEOGCS["GC
3693 NAD_1983_NSRS2007_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1983_NSRS2007_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GCS_NA
3694 NAD_1983_NSRS2007_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1983_NSRS2007_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GCS_NA
3695 NAD_1983_NSRS2007_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1983_NSRS2007_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS_NAD
3696 NAD_1983_NSRS2007_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US",GEOGCS["GC
3697 NAD_1983_NSRS2007_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1983_NSRS2007_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_NAD_
3698 NAD_1983_NSRS2007_StatePlane_Wisconsin_North_FIPS_4801_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Wisconsin_North_FIPS_4801_Ft_US",GEOGCS["GCS
3699 NAD_1983_NSRS2007_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1983_NSRS2007_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_NAD_
3700 NAD_1983_NSRS2007_StatePlane_Wisconsin_South_FIPS_4803_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Wisconsin_South_FIPS_4803_Ft_US",GEOGCS["GCS

3701 NAD_1983_NSRS2007_Wisconsin_TM PROJCS["NAD_1983_NSRS2007_Wisconsin_TM",GEOGCS["GCS_NAD_1983_NSRS2007",DATUM

3702 NAD_1983_NSRS2007_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_NAD_19
3703 NAD_1983_NSRS2007_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS["GCS_
3704 NAD_1983_NSRS2007_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS["GCS
3705 NAD_1983_NSRS2007_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_NAD_1
3706 NAD_1983_NSRS2007_UTM_Zone_59N PROJCS["NAD_1983_NSRS2007_UTM_Zone_59N",GEOGCS["GCS_NAD_1983_NSRS2007",DATU
3708 NAD_1983_NSRS2007_UTM_Zone_1N PROJCS["NAD_1983_NSRS2007_UTM_Zone_1N",GEOGCS["GCS_NAD_1983_NSRS2007",DATUM
3727 Reunion_1947_TM_Reunion PROJCS["Reunion_1947_TM_Reunion",GEOGCS["GCS_Reunion_1947",DATUM["D_Reunion_1947"
3728 NAD_1983_NSRS2007_StatePlane_Ohio_North_FIPS_3401_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Ohio_North_FIPS_3401_Ft_US",GEOGCS["GCS_NAD
3729 NAD_1983_NSRS2007_StatePlane_Ohio_South_FIPS_3402_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Ohio_South_FIPS_3402_Ft_US",GEOGCS["GCS_NAD
3730 NAD_1983_NSRS2007_StatePlane_Wyoming_East_FIPS_4901_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_East_FIPS_4901_Ft_US",GEOGCS["GCS_
3731 NAD_1983_NSRS2007_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US",GEOGCS["G
3732 NAD_1983_NSRS2007_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US",GEOGCS["
3733 NAD_1983_NSRS2007_StatePlane_Wyoming_West_FIPS_4904_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Wyoming_West_FIPS_4904_Ft_US",GEOGCS["GCS_
3734 NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet PROJCS["NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet",GEOGCS["GCS_North_American_1
3735 NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet PROJCS["NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet",GEOGCS["GCS_North_American_1
3736 NAD_1983_StatePlane_Wyoming_East_FIPS_4901_Feet PROJCS["NAD_1983_StatePlane_Wyoming_East_FIPS_4901_Feet",GEOGCS["GCS_North_America
3737 NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902_Feet PROJCS["NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902_Feet",GEOGCS["GCS_North_
3738 NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903_Feet PROJCS["NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903_Feet",GEOGCS["GCS_North
3739 NAD_1983_StatePlane_Wyoming_West_FIPS_4904_Feet PROJCS["NAD_1983_StatePlane_Wyoming_West_FIPS_4904_Feet",GEOGCS["GCS_North_America
3740 NAD_1983_HARN_UTM_Zone_10N PROJCS["NAD_1983_HARN_UTM_Zone_10N",GEOGCS["GCS_North_American_1983_HARN",DAT
3750 NAD_1983_HARN_UTM_Zone_4N PROJCS["NAD_1983_HARN_UTM_Zone_4N",GEOGCS["GCS_North_American_1983_HARN",DATU
3751 NAD_1983_HARN_UTM_Zone_5N PROJCS["NAD_1983_HARN_UTM_Zone_5N",GEOGCS["GCS_North_American_1983_HARN",DATU
3753 NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401_Feet PROJCS["NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401_Feet",GEOGCS["GCS_North_Ame
3754 NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402_Feet PROJCS["NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402_Feet",GEOGCS["GCS_North_Am
3755 NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901_Feet PROJCS["NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901_Feet",GEOGCS["GCS_North_

3756 NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902_Feet PROJCS["NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902_Feet",GEOGCS["GCS

3757 NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903_Feet PROJCS["NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903_Feet",GEOGCS["GCS
3758 NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904_Feet PROJCS["NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904_Feet",GEOGCS["GCS_North_
3759 NAD_1983_StatePlane_Hawaii_3_FIPS_5103_Feet PROJCS["NAD_1983_StatePlane_Hawaii_3_FIPS_5103_Feet",GEOGCS["GCS_North_American_198
3760 NAD_1983_HARN_StatePlane_Hawaii_3_FIPS_5103_Feet PROJCS["NAD_1983_HARN_StatePlane_Hawaii_3_FIPS_5103_Feet",GEOGCS["GCS_North_Ameri
3762 WGS_1984_South_Georgia_Lambert PROJCS["WGS_1984_South_Georgia_Lambert",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_198
3763 ETRS_1989_Portugal_TM06 PROJCS["ETRS_1989_Portugal_TM06",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPH
3764 NZGD_2000_Chatham_Island_Circuit PROJCS["NZGD_2000_Chatham_Island_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2
3765 HTRS96_Croatia_TM PROJCS["HTRS96_Croatia_TM",GEOGCS["GCS_HTRS96",DATUM["D_Croatian_Terrestrial_Referen
3766 HTRS96_Croatia_LCC PROJCS["HTRS96_Croatia_LCC",GEOGCS["GCS_HTRS96",DATUM["D_Croatian_Terrestrial_Refere
3767 HTRS96_UTM_Zone_33N PROJCS["HTRS96_UTM_Zone_33N",GEOGCS["GCS_HTRS96",DATUM["D_Croatian_Terrestrial_Re
3768 HTRS96_UTM_Zone_34N PROJCS["HTRS96_UTM_Zone_34N",GEOGCS["GCS_HTRS96",DATUM["D_Croatian_Terrestrial_Re
3769 Bermuda_1957_UTM_Zone_20N PROJCS["Bermuda_1957_UTM_Zone_20N",GEOGCS["GCS_Bermuda_1957",DATUM["D_Bermuda_
3770 Bermuda_2000_National_Grid PROJCS["Bermuda_2000_National_Grid",GEOGCS["GCS_Bermuda_2000",DATUM["D_Bermuda_20
3771 NAD_1927_3TM_111 PROJCS["NAD_1927_3TM_111",GEOGCS["GCS_North_American_1927",DATUM["D_North_America
3779 NAD_1983_CSRS_3TM_111 PROJCS["NAD_1983_CSRS_3TM_111",GEOGCS["GCS_North_American_1983_CSRS",DATUM["D_
3783 Pitcairn_2006_Pitcairn_TM_2006 PROJCS["Pitcairn_2006_Pitcairn_TM_2006",GEOGCS["GCS_Pitcairn_2006",DATUM["D_Pitcairn_200
3784 Pitcairn_1967_UTM_Zone_9S PROJCS["Pitcairn_1967_UTM_Zone_9S",GEOGCS["GCS_Pitcairn_1967",DATUM["D_Pitcairn_1967",
3788 NZGD_2000_Auckland_Islands_TM_2000 PROJCS["NZGD_2000_Auckland_Islands_TM_2000",GEOGCS["GCS_NZGD_2000",DATUM["D_NZG
3789 NZGD_2000_Campbell_Island_TM_2000 PROJCS["NZGD_2000_Campbell_Island_TM_2000",GEOGCS["GCS_NZGD_2000",DATUM["D_NZG
3790 NZGD_2000_Antipodes_Islands_TM_2000 PROJCS["NZGD_2000_Antipodes_Islands_TM_2000",GEOGCS["GCS_NZGD_2000",DATUM["D_NZ
3791 NZGD_2000_Raoul_Island_TM_2000 PROJCS["NZGD_2000_Raoul_Island_TM_2000",GEOGCS["GCS_NZGD_2000",DATUM["D_NZGD_2
3793 NZGD_2000_Chatham_Islands_TM_2000 PROJCS["NZGD_2000_Chatham_Islands_TM_2000",GEOGCS["GCS_NZGD_2000",DATUM["D_NZG
3794 Slovenia_1996_Slovene_National_Grid PROJCS["Slovenia_1996_Slovene_National_Grid",GEOGCS["GCS_Slovenia_1996",DATUM["D_Slove
3797 NAD_1927_MTQ_Lambert PROJCS["NAD_1927_MTQ_Lambert",GEOGCS["GCS_North_American_1927",DATUM["D_North_Am
3798 NAD_1983_MTQ_Lambert PROJCS["NAD_1983_MTQ_Lambert",GEOGCS["GCS_North_American_1983",DATUM["D_North_Am
3799 NAD_1983_CSRS_MTQ_Lambert PROJCS["NAD_1983_CSRS_MTQ_Lambert",GEOGCS["GCS_North_American_1983_CSRS",DATUM
3812 Belge_Lambert_2008 PROJCS["Belge_Lambert_2008",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID
3814 NAD_1983_Mississippi_TM PROJCS["NAD_1983_Mississippi_TM",GEOGCS["GCS_North_American_1983",DATUM["D_North_Am
3815 NAD_1983_HARN_Mississippi_TM PROJCS["NAD_1983_HARN_Mississippi_TM",GEOGCS["GCS_North_American_1983_HARN",DATU
3816 NAD_1983_NSRS2007_Mississippi_TM PROJCS["NAD_1983_NSRS2007_Mississippi_TM",GEOGCS["GCS_NAD_1983_NSRS2007",DATUM
3825 TWD_1997_TM_Penghu PROJCS["TWD_1997_TM_Penghu",GEOGCS["GCS_TWD_1997",DATUM["D_TWD_1997",SPHEROI
3826 TWD_1997_TM_Taiwan PROJCS["TWD_1997_TM_Taiwan",GEOGCS["GCS_TWD_1997",DATUM["D_TWD_1997",SPHEROID
3827 TWD_1967_TM_Penghu PROJCS["TWD_1967_TM_Penghu",GEOGCS["GCS_TWD_1967",DATUM["D_TWD_1967",SPHEROI
3828 TWD_1967_TM_Taiwan PROJCS["TWD_1967_TM_Taiwan",GEOGCS["GCS_TWD_1967",DATUM["D_TWD_1967",SPHEROID
3829 Hu_Tzu_Shan_UTM_Zone_51N PROJCS["Hu_Tzu_Shan_UTM_Zone_51N",GEOGCS["GCS_Hu_Tzu_Shan",DATUM["D_Hu_Tzu_Sha
3832 WGS_1984_PDC_Mercator PROJCS["WGS_1984_PDC_Mercator",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHER


3844 Pulkovo_1942_Adj_58_Stereo_70 PROJCS["Pulkovo_1942_Adj_58_Stereo_70",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DATUM["D_
3845 SWEREF99_RT90_7.5_gon_V_emulation PROJCS["SWEREF99_RT90_7.5_gon_V_emulation",GEOGCS["GCS_SWEREF99",DATUM["D_SWE
3846 SWEREF99_RT90_5_gon_V_emulation PROJCS["SWEREF99_RT90_5_gon_V_emulation",GEOGCS["GCS_SWEREF99",DATUM["D_SWER
3847 SWEREF99_RT90_2.5_gon_V_emulation PROJCS["SWEREF99_RT90_2.5_gon_V_emulation",GEOGCS["GCS_SWEREF99",DATUM["D_SWE
3848 SWEREF99_RT90_0_gon_emulation PROJCS["SWEREF99_RT90_0_gon_emulation",GEOGCS["GCS_SWEREF99",DATUM["D_SWEREF
3849 SWEREF99_RT90_2.5_gon_O_emulation PROJCS["SWEREF99_RT90_2.5_gon_O_emulation",GEOGCS["GCS_SWEREF99",DATUM["D_SWE
3850 SWEREF99_RT90_5_gon_O_emulation PROJCS["SWEREF99_RT90_5_gon_O_emulation",GEOGCS["GCS_SWEREF99",DATUM["D_SWER
3851 NZGD_2000_NZ_Continental_Shelf_2000 PROJCS["NZGD_2000_NZ_Continental_Shelf_2000",GEOGCS["GCS_NZGD_2000",DATUM["D_NZG
3852 RSRGD2000_DGLC2000 PROJCS["RSRGD2000_DGLC2000",GEOGCS["GCS_RSRGD2000",DATUM["D_Ross_Sea_Region_
3854 SWEREF99_County_ST74 PROJCS["SWEREF99_County_ST74",GEOGCS["GCS_SWEREF99",DATUM["D_SWEREF99",SPHE
3857 WGS_1984_Web_Mercator_Auxiliary_Sphere PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATUM["D_W
3873 ETRS_1989_GK19FIN PROJCS["ETRS_1989_GK19FIN",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROI
3890 IGRS_UTM_Zone_37N PROJCS["IGRS_UTM_Zone_37N",GEOGCS["GCS_IGRS",DATUM["D_Iraqi_Geospatial_Reference_S
3893 ED_1950_Iraq_National_Grid PROJCS["ED_1950_Iraq_National_Grid",GEOGCS["GCS_European_1950",DATUM["D_European_19
3907 MGI_1901_Balkans_5 PROJCS["MGI_1901_Balkans_5",GEOGCS["GCS_MGI_1901",DATUM["D_MGI_1901",SPHEROID["B
3911 MGI_1901_Slovenia_Grid PROJCS["MGI_1901_Slovenia_Grid",GEOGCS["GCS_MGI_1901",DATUM["D_MGI_1901",SPHEROID
3912 MGI_1901_Slovene_National_Grid PROJCS["MGI_1901_Slovene_National_Grid",GEOGCS["GCS_MGI_1901",DATUM["D_MGI_1901",S
3920 Puerto_Rico_UTM_Zone_20N PROJCS["Puerto_Rico_UTM_Zone_20N",GEOGCS["GCS_Puerto_Rico",DATUM["D_Puerto_Rico",SP
3942 RGF_1993_CC42 PROJCS["RGF_1993_CC42",GEOGCS["GCS_RGF_1993",DATUM["D_RGF_1993",SPHEROID["GRS
3968 NAD_1983_Virginia_Lambert PROJCS["NAD_1983_Virginia_Lambert",GEOGCS["GCS_North_American_1983",DATUM["D_North_A
3969 NAD_1983_HARN_Virginia_Lambert PROJCS["NAD_1983_HARN_Virginia_Lambert",GEOGCS["GCS_North_American_1983_HARN",DAT
3970 NAD_1983_NSRS2007_Virginia_Lambert PROJCS["NAD_1983_NSRS2007_Virginia_Lambert",GEOGCS["GCS_NAD_1983_NSRS2007",DATU
3973 WGS_1984_EASE_Grid_North PROJCS["WGS_1984_EASE_Grid_North",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
3974 WGS_1984_EASE_Grid_South PROJCS["WGS_1984_EASE_Grid_South",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
3975 WGS_1984_EASE_Grid_Global PROJCS["WGS_1984_EASE_Grid_Global",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
3976 WGS_1984_NSIDC_Sea_Ice_Polar_Stereographic_South PROJCS["WGS_1984_NSIDC_Sea_Ice_Polar_Stereographic_South",GEOGCS["GCS_WGS_1984",D

3978 NAD_1983_Canada_Atlas_Lambert PROJCS["NAD_1983_Canada_Atlas_Lambert",GEOGCS["GCS_North_American_1983",DATUM["D_N

3979 NAD_1983_CSRS_Canada_Atlas_Lambert PROJCS["NAD_1983_CSRS_Canada_Atlas_Lambert",GEOGCS["GCS_North_American_1983_CSRS
3986 Katanga_1955_Katanga_Gauss_Zone_A PROJCS["Katanga_1955_Katanga_Gauss_Zone_A",GEOGCS["GCS_Katanga_1955",DATUM["D_Kat
3987 Katanga_1955_Katanga_Gauss_Zone_B PROJCS["Katanga_1955_Katanga_Gauss_Zone_B",GEOGCS["GCS_Katanga_1955",DATUM["D_Kat
3988 Katanga_1955_Katanga_Gauss_Zone_C PROJCS["Katanga_1955_Katanga_Gauss_Zone_C",GEOGCS["GCS_Katanga_1955",DATUM["D_Ka
3989 Katanga_1955_Katanga_Gauss_Zone_D PROJCS["Katanga_1955_Katanga_Gauss_Zone_D",GEOGCS["GCS_Katanga_1955",DATUM["D_Ka
3991 Puerto_Rico_StatePlane_Puerto_Rico_FIPS_5201 PROJCS["Puerto_Rico_StatePlane_Puerto_Rico_FIPS_5201",GEOGCS["GCS_Puerto_Rico",DATUM
3992 Puerto_Rico_StatePlane_Virgin_Islands_St_Croix_FIPS_5202 PROJCS["Puerto_Rico_StatePlane_Virgin_Islands_St_Croix_FIPS_5202",GEOGCS["GCS_Puerto_Ri
3994 WGS_1984_Mercator_41 PROJCS["WGS_1984_Mercator_41",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
3995 WGS_1984_Arctic_Polar_Stereographic PROJCS["WGS_1984_Arctic_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1
3996 WGS_1984_IBCAO_Polar_Stereographic PROJCS["WGS_1984_IBCAO_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_
3997 WGS_1984_Dubai_Local_TM PROJCS["WGS_1984_Dubai_Local_TM",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPH
4026 MOLDREF99_Moldova_TM PROJCS["MOLDREF99_Moldova_TM",GEOGCS["GCS_MOLDREF99",DATUM["D_MOLDREF99",SP
4037 WGS_1984_TMzn35N PROJCS["WGS_1984_TMzn35N",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID
4038 WGS_1984_TMzn36N PROJCS["WGS_1984_TMzn36N",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID
4048 RGRDC_2005_Congo_TM_Zone_12 PROJCS["RGRDC_2005_Congo_TM_Zone_12",GEOGCS["GCS_RGRDC_2005",DATUM["D_Reseau
4061 RGRDC_2005_UTM_Zone_33S PROJCS["RGRDC_2005_UTM_Zone_33S",GEOGCS["GCS_RGRDC_2005",DATUM["D_Reseau_Ge
4071 Chua_UTM_Zone_23S PROJCS["Chua_UTM_Zone_23S",GEOGCS["GCS_Chua",DATUM["D_Chua",SPHEROID["Internation
4082 REGCAN95_UTM_Zone_27N PROJCS["REGCAN95_UTM_Zone_27N",GEOGCS["GCS_REGCAN95",DATUM["D_Red_Geodesica_
4083 REGCAN95_UTM_Zone_28N PROJCS["REGCAN95_UTM_Zone_28N",GEOGCS["GCS_REGCAN95",DATUM["D_Red_Geodesica_
4087 WGS_1984_World_Equidistant_Cylindrical PROJCS["WGS_1984_World_Equidistant_Cylindrical",GEOGCS["GCS_WGS_1984",DATUM["D_WGS
4088 World_Equidistant_Cylindrical_(Sphere) PROJCS["World_Equidistant_Cylindrical_(Sphere)",GEOGCS["GCS_Sphere_GRS_1980_Authalic",DA
4093 ETRS_1989_DKTM1 PROJCS["ETRS_1989_DKTM1",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID
4217 NAD_1983_BLM_Zone_59N PROJCS["NAD_1983_BLM_Zone_59N",GEOGCS["GCS_North_American_1983",DATUM["D_North_A
4390 Kertau_1968_Johor_Grid PROJCS["Kertau_1968_Johor_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID["Evere
4391 Kertau_1968_Sembilan_and_Melaka_Grid PROJCS["Kertau_1968_Sembilan_and_Melaka_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",S
4392 Kertau_1968_Pahang_Grid PROJCS["Kertau_1968_Pahang_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID["Eve
4393 Kertau_1968_Selangor_Grid PROJCS["Kertau_1968_Selangor_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID["Ev
4394 Kertau_1968_Terengganu_Grid PROJCS["Kertau_1968_Terengganu_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID["
4395 Kertau_1968_Pinang_Grid PROJCS["Kertau_1968_Pinang_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID["Ever
4396 Kertau_1968_Kedah_and_Perlis_Grid PROJCS["Kertau_1968_Kedah_and_Perlis_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHE
4397 Kertau_1968_Perak_Revised_Grid PROJCS["Kertau_1968_Perak_Revised_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHERO
4398 Kertau_1968_Kelantan_Grid PROJCS["Kertau_1968_Kelantan_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID["Ev
4401 NAD_1927_BLM_Zone_1N PROJCS["NAD_1927_BLM_Zone_1N",GEOGCS["GCS_North_American_1927",DATUM["D_North_Am


4414 NAD_1983_HARN_Guam_Map_Grid PROJCS["NAD_1983_HARN_Guam_Map_Grid",GEOGCS["GCS_North_American_1983_HARN",DAT
4415 Katanga_1955_Katanga_Lambert PROJCS["Katanga_1955_Katanga_Lambert",GEOGCS["GCS_Katanga_1955",DATUM["D_Katanga_1
4437 NAD_1983_NSRS2007_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200 PROJCS["NAD_1983_NSRS2007_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200",GEOGCS["GCS
4455 NAD_1927_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1927_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GCS_North_America
4456 NAD_1927_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1927_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GCS_North_Amer
4457 NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet PROJCS["NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet",GEOGCS["GCS_North_Am
4462 WGS_1984_Australian_Centre_for_Remote_Sensing_Lambert PROJCS["WGS_1984_Australian_Centre_for_Remote_Sensing_Lambert",GEOGCS["GCS_WGS_198
4467 RGSPM_2006_UTM_Zone_21N PROJCS["RGSPM_2006_UTM_Zone_21N",GEOGCS["GCS_RGSPM_2006",DATUM["D_Reseau_Ge
4471 RGM_2004_UTM_Zone_38S PROJCS["RGM_2004_UTM_Zone_38S",GEOGCS["GCS_RGM_2004",DATUM["D_Reseau_Geodesiq
4474 Cadastre_1997_UTM_Zone_38S PROJCS["Cadastre_1997_UTM_Zone_38S",GEOGCS["GCS_Cadastre_1997",DATUM["D_Cadastre_
4484 Mexican_Datum_1993_UTM_Zone_11N PROJCS["Mexican_Datum_1993_UTM_Zone_11N",GEOGCS["GCS_Mexican_Datum_of_1993",DATU
4491 CGCS2000_GK_Zone_13 PROJCS["CGCS2000_GK_Zone_13",GEOGCS["GCS_China_Geodetic_Coordinate_System_2000",D

4502 CGCS2000_GK_CM_75E PROJCS["CGCS2000_GK_CM_75E",GEOGCS["GCS_China_Geodetic_Coordinate_System_2000",D

4513 CGCS2000_3_Degree_GK_Zone_25 PROJCS["CGCS2000_3_Degree_GK_Zone_25",GEOGCS["GCS_China_Geodetic_Coordinate_Syste
4534 CGCS2000_3_Degree_GK_CM_75E PROJCS["CGCS2000_3_Degree_GK_CM_75E",GEOGCS["GCS_China_Geodetic_Coordinate_Syste
4543 CGCS2000_3_Degree_GK_CM_102E PROJCS["CGCS2000_3_Degree_GK_CM_102E",GEOGCS["GCS_China_Geodetic_Coordinate_Syst
4559 RRAF_1991_UTM_20N PROJCS["RRAF_1991_UTM_20N",GEOGCS["GCS_RRAF_1991",DATUM["D_RRAF_1991",SPHERO

4568 New_Beijing_Gauss_Kruger_Zone_13 PROJCS["New_Beijing_Gauss_Kruger_Zone_13",GEOGCS["GCS_New_Beijing",DATUM["D_New_Be

4579 New_Beijing_Gauss_Kruger_CM_75E PROJCS["New_Beijing_Gauss_Kruger_CM_75E",GEOGCS["GCS_New_Beijing",DATUM["D_New_Be
4584 New_Beijing_Gauss_Kruger_CM_105E PROJCS["New_Beijing_Gauss_Kruger_CM_105E",GEOGCS["GCS_New_Beijing",DATUM["D_New_B
4647 ETRS_1989_UTM_Zone_N32 PROJCS["ETRS_1989_UTM_Zone_N32",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SP
4652 New_Beijing_3_Degree_Gauss_Kruger_Zone_25 PROJCS["New_Beijing_3_Degree_Gauss_Kruger_Zone_25",GEOGCS["GCS_New_Beijing",DATUM["
4782 New_Beijing_3_Degree_Gauss_Kruger_CM_75E PROJCS["New_Beijing_3_Degree_Gauss_Kruger_CM_75E",GEOGCS["GCS_New_Beijing",DATUM["
4791 New_Beijing_3_Degree_Gauss_Kruger_CM_102E PROJCS["New_Beijing_3_Degree_Gauss_Kruger_CM_102E",GEOGCS["GCS_New_Beijing",DATUM


4794 New_Beijing_3_Degree_Gauss_Kruger_CM_111E PROJCS["New_Beijing_3_Degree_Gauss_Kruger_CM_111E",GEOGCS["GCS_New_Beijing",DATUM[
4826 WGS_1984_Cape_Verde_Grid PROJCS["WGS_1984_Cape_Verde_Grid",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPH
4839 ETRS_1989_LCC_Germany_N-E PROJCS["ETRS_1989_LCC_Germany_N-E",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989"
5014 PTRA08_UTM_Zone_25N PROJCS["PTRA08_UTM_Zone_25N",GEOGCS["GCS_PTRA08",DATUM["D_PTRA08",SPHEROID["G
5018 Lisbon_Portuguese_Grid_New PROJCS["Lisbon_Portuguese_Grid_New",GEOGCS["GCS_Lisbon",DATUM["D_Lisbon",SPHEROID["I
5048 ETRS_1989_TM35FIN_NE PROJCS["ETRS_1989_TM35FIN_NE",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHE
5069 NAD_1927_Contiguous_USA_Albers PROJCS["NAD_1927_Contiguous_USA_Albers",GEOGCS["GCS_North_American_1927",DATUM["D_
5070 NAD_1983_Contiguous_USA_Albers PROJCS["NAD_1983_Contiguous_USA_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_
5071 NAD_1983_HARN_Contiguous_USA_Albers PROJCS["NAD_1983_HARN_Contiguous_USA_Albers",GEOGCS["GCS_North_American_1983_HAR
5072 NAD_1983_NSRS2007_Contiguous_USA_Albers PROJCS["NAD_1983_NSRS2007_Contiguous_USA_Albers",GEOGCS["GCS_NAD_1983_NSRS2007
5105 ETRS_1989_NTM_Zone_5 PROJCS["ETRS_1989_NTM_Zone_5",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHE
5110 ETRS_1989_NTM_Zone_10 PROJCS["ETRS_1989_NTM_Zone_10",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPH
5167 Korean_1985_Korea_East_Sea_Belt PROJCS["Korean_1985_Korea_East_Sea_Belt",GEOGCS["GCS_Korean_Datum_1985",DATUM["D_K
5168 Korean_1985_Korea_Central_Belt_Jeju PROJCS["Korean_1985_Korea_Central_Belt_Jeju",GEOGCS["GCS_Korean_Datum_1985",DATUM["D
5173 Korean_1985_Modified_Korea_West_Belt PROJCS["Korean_1985_Modified_Korea_West_Belt",GEOGCS["GCS_Korean_Datum_1985",DATUM
5174 Korean_1985_Modified_Korea_Central_Belt PROJCS["Korean_1985_Modified_Korea_Central_Belt",GEOGCS["GCS_Korean_Datum_1985",DATU
5175 Korean_1985_Modified_Korea_Central_Belt_Jeju PROJCS["Korean_1985_Modified_Korea_Central_Belt_Jeju",GEOGCS["GCS_Korean_Datum_1985",
5176 Korean_1985_Modified_Korea_East_Belt PROJCS["Korean_1985_Modified_Korea_East_Belt",GEOGCS["GCS_Korean_Datum_1985",DATUM[
5177 Korean_1985_Modified_Korea_East_Sea_Belt PROJCS["Korean_1985_Modified_Korea_East_Sea_Belt",GEOGCS["GCS_Korean_Datum_1985",DA

5178 Korean_1985_Korea_Unified_Coordinate_System PROJCS["Korean_1985_Korea_Unified_Coordinate_System",GEOGCS["GCS_Korean_Datum_1985",

5179 Korea_2000_Korea_Unified_Coordinate_System PROJCS["Korea_2000_Korea_Unified_Coordinate_System",GEOGCS["GCS_Korea_2000",DATUM["D
5180 Korea_2000_Korea_West_Belt PROJCS["Korea_2000_Korea_West_Belt",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_2000",SP
5181 Korea_2000_Korea_Central_Belt PROJCS["Korea_2000_Korea_Central_Belt",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_2000",
5182 Korea_2000_Korea_Central_Belt_Jeju PROJCS["Korea_2000_Korea_Central_Belt_Jeju",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_2
5183 Korea_2000_Korea_East_Belt PROJCS["Korea_2000_Korea_East_Belt",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_2000",SP
5184 Korea_2000_Korea_East_Sea_Belt PROJCS["Korea_2000_Korea_East_Sea_Belt",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_200
5185 Korea_2000_Korea_West_Belt_2010 PROJCS["Korea_2000_Korea_West_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_20
5186 Korea_2000_Korea_Central_Belt_2010 PROJCS["Korea_2000_Korea_Central_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_
5187 Korea_2000_Korea_East_Belt_2010 PROJCS["Korea_2000_Korea_East_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM["D_Korea_20
5188 Korea_2000_Korea_East_Sea_Belt_2010 PROJCS["Korea_2000_Korea_East_Sea_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM["D_Kore
5221 S-JTSK_Ferro_Krovak_East_North PROJCS["S-JTSK_Ferro_Krovak_East_North",GEOGCS["GCS_S_JTSK_Ferro",DATUM["D_S_JTSK"
5223 WGS_1984_UTM_Gabon_TM PROJCS["WGS_1984_UTM_Gabon_TM",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPH
5234 Kandawala_Sri_Lanka_Grid PROJCS["Kandawala_Sri_Lanka_Grid",GEOGCS["GCS_Kandawala",DATUM["D_Kandawala",SPHER
5235 SLD99_Sri_Lanka_Grid_1999 PROJCS["SLD99_Sri_Lanka_Grid_1999",GEOGCS["GCS_SLD99",DATUM["D_Sri_Lanka_Datum_19
5243 ETRS_1989_LCC_Germany_E-N PROJCS["ETRS_1989_LCC_Germany_E-N",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989"
5247 GDBD2009_GEORSO PROJCS["GDBD2009_GEORSO",GEOGCS["GCS_GDBD2009",DATUM["D_GDBD2009",SPHEROID
5253 TUREF_TM27 PROJCS["TUREF_TM27",GEOGCS["GCS_TUREF",DATUM["D_Turkish_National_Reference_Frame"
5266 DRUKREF_03_Bhutan_National_Grid PROJCS["DRUKREF_03_Bhutan_National_Grid",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan
5269 TUREF_3_Degree_GK_Zone_9 PROJCS["TUREF_3_Degree_GK_Zone_9",GEOGCS["GCS_TUREF",DATUM["D_Turkish_National_R
5270 TUREF_3_Degree_GK_Zone_10 PROJCS["TUREF_3_Degree_GK_Zone_10",GEOGCS["GCS_TUREF",DATUM["D_Turkish_National_
5292 DRUKREF_03_Bumthang_TM PROJCS["DRUKREF_03_Bumthang_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Natio
5293 DRUKREF_03_Chhukha_TM PROJCS["DRUKREF_03_Chhukha_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nation
5294 DRUKREF_03_Dagana_TM PROJCS["DRUKREF_03_Dagana_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nationa
5295 DRUKREF_03_Gasa_TM PROJCS["DRUKREF_03_Gasa_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_National_G
5296 DRUKREF_03_Ha_TM PROJCS["DRUKREF_03_Ha_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_National_Ge
5297 DRUKREF_03_Lhuentse_TM PROJCS["DRUKREF_03_Lhuentse_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nation
5298 DRUKREF_03_Mongar_TM PROJCS["DRUKREF_03_Mongar_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nationa
5299 DRUKREF_03_Paro_TM PROJCS["DRUKREF_03_Paro_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_National_G
5300 DRUKREF_03_Pemagatshel_TM PROJCS["DRUKREF_03_Pemagatshel_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Na
5301 DRUKREF_03_Punakha_TM PROJCS["DRUKREF_03_Punakha_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nation
5302 DRUKREF_03_Samdrup_Jongkhar_TM PROJCS["DRUKREF_03_Samdrup_Jongkhar_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhut
5303 DRUKREF_03_Samtse_TM PROJCS["DRUKREF_03_Samtse_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nationa
5304 DRUKREF_03_Sarpang_TM PROJCS["DRUKREF_03_Sarpang_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nationa
5305 DRUKREF_03_Thimphu_TM PROJCS["DRUKREF_03_Thimphu_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nationa
5306 DRUKREF_03_Trashigang_TM PROJCS["DRUKREF_03_Trashigang_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Natio
5307 DRUKREF_03_Trongsa_TM PROJCS["DRUKREF_03_Trongsa_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nationa
5308 DRUKREF_03_Tsirang_TM PROJCS["DRUKREF_03_Tsirang_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_National
5309 DRUKREF_03_Wangdue_Phodrang_TM PROJCS["DRUKREF_03_Wangdue_Phodrang_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhu
5310 DRUKREF_03_Yangtse_TM PROJCS["DRUKREF_03_Yangtse_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Nationa
5311 DRUKREF_03_Zhemgang_TM PROJCS["DRUKREF_03_Zhemgang_TM",GEOGCS["GCS_DRUKREF_03",DATUM["D_Bhutan_Natio
5316 ETRS_1989_FAROE_TM PROJCS["ETRS_1989_FAROE_TM",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHER
5320 NAD_1983_Teranet_Ontario_Lambert PROJCS["NAD_1983_Teranet_Ontario_Lambert",GEOGCS["GCS_North_American_1983",DATUM["D

5321 NAD_1983_CSRS_Teranet_Ontario_Lambert PROJCS["NAD_1983_CSRS_Teranet_Ontario_Lambert",GEOGCS["GCS_North_American_1983_CS

5325 ISN_2004_Lambert_2004 PROJCS["ISN_2004_Lambert_2004",GEOGCS["GCS_ISN_2004",DATUM["D_Islands_Network_2004
5329 Gunung_Segara_Jakarta_NEIEZ PROJCS["Gunung_Segara_Jakarta_NEIEZ",GEOGCS["GCS_Gunung_Segara_Jakarta",DATUM["D_G
5330 Batavia_Jakarta_NEIEZ PROJCS["Batavia_Jakarta_NEIEZ",GEOGCS["GCS_Batavia_Jakarta",DATUM["D_Batavia",SPHEROI
5331 Makassar_Jakarta_NEIEZ PROJCS["Makassar_Jakarta_NEIEZ",GEOGCS["GCS_Makassar_Jakarta",DATUM["D_Makassar",SP
5337 Aratu_UTM_Zone_25S PROJCS["Aratu_UTM_Zone_25S",GEOGCS["GCS_Aratu",DATUM["D_Aratu",SPHEROID["Internation
5343 POSGAR_2007_Argentina_Zone_1 PROJCS["POSGAR_2007_Argentina_Zone_1",GEOGCS["GCS_POSGAR_2007",DATUM["D_POSGA
5355 MARGEN_UTM_Zone_20S PROJCS["MARGEN_UTM_Zone_20S",GEOGCS["GCS_MARGEN",DATUM["D_Marco_Geodesico_Na
5361 SIRGAS-Chile_UTM_Zone_19S PROJCS["SIRGAS-Chile_UTM_Zone_19S",GEOGCS["GCS_SIRGAS-Chile",DATUM["D_SIRGAS-Chi
5362 SIRGAS-Chile_UTM_Zone_18S PROJCS["SIRGAS-Chile_UTM_Zone_18S",GEOGCS["GCS_SIRGAS-Chile",DATUM["D_SIRGAS-Chi
5367 CRTM05 PROJCS["CRTM05",GEOGCS["GCS_CR05",DATUM["D_Costa_Rica_2005",SPHEROID["WGS_1984
5382 SIRGAS-ROU98_UTM_Zone_21S PROJCS["SIRGAS-ROU98_UTM_Zone_21S",GEOGCS["GCS_SIRGAS-ROU98",DATUM["D_SIRGAS
5383 SIRGAS-ROU98_UTM_Zone_22S PROJCS["SIRGAS-ROU98_UTM_Zone_22S",GEOGCS["GCS_SIRGAS-ROU98",DATUM["D_SIRGAS
5387 Peru96_UTM_Zone_18S PROJCS["Peru96_UTM_Zone_18S",GEOGCS["GCS_Peru96",DATUM["D_Peru96",SPHEROID["GRS
5396 SIRGAS_2000_UTM_Zone_26S PROJCS["SIRGAS_2000_UTM_Zone_26S",GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIRGAS_20
5456 Ocotepeque_1935_Costa_Rica_Norte PROJCS["Ocotepeque_1935_Costa_Rica_Norte",GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Oc
5457 Ocotepeque_1935_Costa_Rica_Sur PROJCS["Ocotepeque_1935_Costa_Rica_Sur",GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Oco
5459 Ocotepeque_1935_Guatemala_Sur PROJCS["Ocotepeque_1935_Guatemala_Sur",GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Ocot
5460 Ocotepeque_1935_El_Salvador_Lambert PROJCS["Ocotepeque_1935_El_Salvador_Lambert",GEOGCS["GCS_Ocotepeque_1935",DATUM["D
5461 Ocotepeque_1935_Nicaragua_Norte PROJCS["Ocotepeque_1935_Nicaragua_Norte",GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Oco
5462 Ocotepeque_1935_Nicaragua_Sur PROJCS["Ocotepeque_1935_Nicaragua_Sur",GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Ocote
5463 SAD_1969_UTM_Zone_17N PROJCS["SAD_1969_UTM_Zone_17N",GEOGCS["GCS_South_American_1969",DATUM["D_South_
5469 Panama-Colon_1911_Panama_Lambert PROJCS["Panama-Colon_1911_Panama_Lambert",GEOGCS["GCS_Panama-Colon_1911",DATUM["D
5472 Panama-Colon_1911_Panama_Polyconic PROJCS["Panama-Colon_1911_Panama_Polyconic",GEOGCS["GCS_Panama-Colon_1911",DATUM[
5479 RSRGD2000_MSLC2000 PROJCS["RSRGD2000_MSLC2000",GEOGCS["GCS_RSRGD2000",DATUM["D_Ross_Sea_Region_
5480 RSRGD2000_BCLC2000 PROJCS["RSRGD2000_BCLC2000",GEOGCS["GCS_RSRGD2000",DATUM["D_Ross_Sea_Region_G
5481 RSRGD2000_PCLC2000 PROJCS["RSRGD2000_PCLC2000",GEOGCS["GCS_RSRGD2000",DATUM["D_Ross_Sea_Region_G
5482 RSRGD2000_RSPS2000 PROJCS["RSRGD2000_RSPS2000",GEOGCS["GCS_RSRGD2000",DATUM["D_Ross_Sea_Region_
5490 RGAF09_UTM_Zone_20N PROJCS["RGAF09_UTM_Zone_20N",GEOGCS["GCS_RGAF09",DATUM["Reseau_Geodesique_des_
5513 S-JTSK_Krovak PROJCS["S-JTSK_Krovak",GEOGCS["GCS_S_JTSK",DATUM["D_S_JTSK",SPHEROID["Bessel_184
5514 S-JTSK_Krovak_East_North PROJCS["S-JTSK_Krovak_East_North",GEOGCS["GCS_S_JTSK",DATUM["D_S_JTSK",SPHEROID[
5518 Chatham_Island_1971_Map_Grid PROJCS["Chatham_Island_1971_Map_Grid",GEOGCS["GCS_Chatham_Island_1971",DATUM["D_Ch
5519 Chatham_Islands_1979_Map_Grid PROJCS["Chatham_Islands_1979_Map_Grid",GEOGCS["GCS_Chatham_Islands_1979",DATUM["D_
5520 DHDN_3_Degree_Gauss_Zone_1 PROJCS["DHDN_3_Degree_Gauss_Zone_1",GEOGCS["GCS_Deutsches_Hauptdreiecksnetz",DATUM
5523 WGS_1984_UTM_Gabon_TM_2011 PROJCS["WGS_1984_UTM_Gabon_TM_2011",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984
5530 SAD_1969_96_Brazil_Polyconic PROJCS["SAD_1969_96_Brazil_Polyconic",GEOGCS["GCS_SAD_1969_96",DATUM["D_South_Ame
5531 SAD_1969_96_UTM_Zone_21S PROJCS["SAD_1969_96_UTM_Zone_21S",GEOGCS["GCS_SAD_1969_96",DATUM["D_South_Ame
5536 Corrego_Alegre_1961_UTM_Zone_21S PROJCS["Corrego_Alegre_1961_UTM_Zone_21S",GEOGCS["GCS_Corrego_Alegre_1961",DATUM["


5550 PNG94_PNGMG94_Zone_54 PROJCS["PNG94_PNGMG94_Zone_54",GEOGCS["GCS_PNG94",DATUM["D_Papua_New_Guinea_
5559 Ocotepeque_1935_Guatemala_Norte PROJCS["Ocotepeque_1935_Guatemala_Norte",GEOGCS["GCS_Ocotepeque_1935",DATUM["D_Oc
5562 Ukraine_2000_GK_Zone_4 PROJCS["Ukraine_2000_GK_Zone_4",GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukraine_2000",SP
5566 Ukraine_2000_GK_CM_21E PROJCS["Ukraine_2000_GK_CM_21E",GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukraine_2000",S
5570 Ukraine_2000_3_Degree_GK_Zone_7 PROJCS["Ukraine_2000_3_Degree_GK_Zone_7",GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukrain
5573 Ukraine_2000_3_Degree_GK_Zone_10 PROJCS["Ukraine_2000_3_Degree_GK_Zone_10",GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukrai
5577 Ukraine_2000_3_Degree_GK_CM_21E PROJCS["Ukraine_2000_3_Degree_GK_CM_21E",GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukrai
5588 NAD_1927_New_Brunswick_Stereographic PROJCS["NAD_1927_New_Brunswick_Stereographic",GEOGCS["GCS_North_American_1927",DATU
5589 Sibun_Gorge_1922_Colony_Grid PROJCS["Sibun_Gorge_1922_Colony_Grid",GEOGCS["GCS_Sibun_Gorge_1922",DATUM["D_Sibun_
5596 FEH2010_Fehmarnbelt_TM PROJCS["FEH2010_Fehmarnbelt_TM",GEOGCS["GCS_FEH2010",DATUM["D_Fehmarnbelt_Datum_
5623 NAD_1927_StatePlane_Michigan_East_Old_FIPS_2101 PROJCS["NAD_1927_StatePlane_Michigan_East_Old_FIPS_2101",GEOGCS["GCS_North_American
5624 NAD_1927_StatePlane_Michigan_Central_Old_FIPS_2102 PROJCS["NAD_1927_StatePlane_Michigan_Central_Old_FIPS_2102",GEOGCS["GCS_North_Americ
5625 NAD_1927_StatePlane_Michigan_West_Old_FIPS_2103 PROJCS["NAD_1927_StatePlane_Michigan_West_Old_FIPS_2103",GEOGCS["GCS_North_American
5627 ED_1950_TM_6_NE PROJCS["ED_1950_TM_6_NE",GEOGCS["GCS_European_1950",DATUM["D_European_1950",SPH
5631 Pulkovo_1942_Adj_1958_GK_Zone_2_E-N PROJCS["Pulkovo_1942_Adj_1958_GK_Zone_2_E-N",GEOGCS["GCS_Pulkovo_1942_Adj_1958",DA
5632 PTRA08_LCC_Europe PROJCS["PTRA08_LCC_Europe",GEOGCS["GCS_PTRA08",DATUM["D_PTRA08",SPHEROID["GRS
5633 PTRA08_LAEA_Europe PROJCS["PTRA08_LAEA_Europe",GEOGCS["GCS_PTRA08",DATUM["D_PTRA08",SPHEROID["GR
5634 REGCAN95_LCC_Europe PROJCS["REGCAN95_LCC_Europe",GEOGCS["GCS_REGCAN95",DATUM["D_Red_Geodesica_de_
5635 REGCAN95_LAEA_Europe PROJCS["REGCAN95_LAEA_Europe",GEOGCS["GCS_REGCAN95",DATUM["D_Red_Geodesica_de
5636 TUREF_LAEA_Europe PROJCS["TUREF_LAEA_Europe",GEOGCS["GCS_TUREF",DATUM["D_Turkish_National_Reference
5637 TUREF_LCC_Europe PROJCS["TUREF_LCC_Europe",GEOGCS["GCS_TUREF",DATUM["D_Turkish_National_Reference_
5638 ISN_2004_LAEA_Europe PROJCS["ISN_2004_LAEA_Europe",GEOGCS["GCS_ISN_2004",DATUM["D_Islands_Network_2004"
5639 ISN_2004_LCC_Europe PROJCS["ISN_2004_LCC_Europe",GEOGCS["GCS_ISN_2004",DATUM["D_Islands_Network_2004",S
5641 SIRGAS_2000_Brazil_Mercator PROJCS["SIRGAS_2000_Brazil_Mercator",GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIRGAS_20
5643 ED_1950_Southern_Permian_Basin_Lambert PROJCS["ED_1950_Southern_Permian_Basin_Lambert",GEOGCS["GCS_European_1950",DATUM["
5644 RGR_1992_UTM_39S PROJCS["RGR_1992_UTM_39S",GEOGCS["GCS_RGR_1992",DATUM["D_RGR_1992",SPHEROID[
5646 NAD_1983_StatePlane_Vermont_FIPS_4400_Feet PROJCS["NAD_1983_StatePlane_Vermont_FIPS_4400_Feet",GEOGCS["GCS_North_American_198
5649 ETRS_1989_UTM_Zone_31N_zE-N PROJCS["ETRS_1989_UTM_Zone_31N_zE-N",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_198
5650 ETRS_1989_UTM_Zone_33N_zE-N PROJCS["ETRS_1989_UTM_Zone_33N_zE-N",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_198
5651 ETRS_1989_UTM_Zone_31N_N-zE PROJCS["ETRS_1989_UTM_Zone_31N_N-zE",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_198
5654 NAD_1983_HARN_StatePlane_Vermont_FIPS_4400_Ft_US PROJCS["NAD_1983_HARN_StatePlane_Vermont_FIPS_4400_Ft_US",GEOGCS["GCS_North_Amer

5655 NAD_1983_NSRS2007_StatePlane_Vermont_FIPS_4400_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Vermont_FIPS_4400_Ft_US",GEOGCS["GCS_NAD_1

5659 Monte_Mario_TM_Emilia-Romagna PROJCS["Monte_Mario_TM_Emilia-Romagna",GEOGCS["GCS_Monte_Mario",DATUM["D_Monte_Ma
5666 PD/83_3_Degree_GK_Zone_3_E-N PROJCS["PD/83_3_Degree_GK_Zone_3_E-N",GEOGCS["GCS_PD/83",DATUM["D_Potsdam_1983",
5667 PD/83_3_Degree_GK_Zone_4_E-N PROJCS["PD/83_3_Degree_GK_Zone_4_E-N",GEOGCS["GCS_PD/83",DATUM["D_Potsdam_1983",
5668 RD/83_3_Degree_GK_Zone_4_E-N PROJCS["RD/83_3_Degree_GK_Zone_4_E-N",GEOGCS["GCS_RD/83",DATUM["D_Rauenberg_1983
5669 RD/83_3_Degree_GK_Zone_5_E-N PROJCS["RD/83_3_Degree_GK_Zone_5_E-N",GEOGCS["GCS_RD/83",DATUM["D_Rauenberg_1983
5670 Pulkovo_1942_Adj_1958_3_Degree_GK_Zone_3_E-N PROJCS["Pulkovo_1942_Adj_1958_3_Degree_GK_Zone_3_E-N",GEOGCS["GCS_Pulkovo_1942_Ad
5676 DHDN_3_Degree_GK_Zone_2_E-N PROJCS["DHDN_3_Degree_GK_Zone_2_E-N",GEOGCS["GCS_Deutsches_Hauptdreiecksnetz",DAT
5682 DB_REF_3-Degree_GK_Zone_2_(E-N) PROJCS["DB_REF_3-Degree_GK_Zone_2_(E-N)",GEOGCS["GCS_DB_REF",DATUM["D_Deutsche_
5825 AGD_1966_ACT_Standard_Grid PROJCS["AGD_1966_ACT_Standard_Grid",GEOGCS["GCS_Australian_1966",DATUM["D_Australian
5842 WGS_1984_TM_12_SE PROJCS["WGS_1984_TM_12_SE",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROI
5879 Cadastre_1997_UTM_Zone_38S PROJCS["Cadastre_1997_UTM_Zone_38S",GEOGCS["GCS_Cadastre_1997",DATUM["D_Cadastre_
5880 SIRGAS_2000_Brazil_Polyconic PROJCS["SIRGAS_2000_Brazil_Polyconic",GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIRGAS_20
5887 TGD2005_Tonga_Map_Grid PROJCS["TGD2005_Tonga_Map_Grid",GEOGCS["GCS_TGD2005",DATUM["D_Tonga_Geodetic_Dat
5890 JAXA_Snow_Depth_Polar_Stereographic_North PROJCS["JAXA_Snow_Depth_Polar_Stereographic_North",GEOGCS["GCS_Hughes_1980",DATUM["
5921 WGS_1984_EPSG_Arctic_Regional_zone_A1 PROJCS["WGS_1984_EPSG_Arctic_Regional_zone_A1",GEOGCS["GCS_WGS_1984",DATUM["D_W
5926 WGS_1984_EPSG_Arctic_Regional_zone_B1 PROJCS["WGS_1984_EPSG_Arctic_Regional_zone_B1",GEOGCS["GCS_WGS_1984",DATUM["D_W
5931 WGS_1984_EPSG_Arctic_Regional_zone_C1 PROJCS["WGS_1984_EPSG_Arctic_Regional_zone_C1",GEOGCS["GCS_WGS_1984",DATUM["D_W

5936 WGS_1984_EPSG_Alaska_Polar_Stereographic PROJCS["WGS_1984_EPSG_Alaska_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D

5937 WGS_1984_EPSG_Canada_Polar_Stereographic PROJCS["WGS_1984_EPSG_Canada_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["
5938 WGS_1984_EPSG_Greenland_Polar_Stereographic PROJCS["WGS_1984_EPSG_Greenland_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM
5939 WGS_1984_EPSG_Norway_Polar_Stereographic PROJCS["WGS_1984_EPSG_Norway_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D
5940 WGS_1984_EPSG_Russia_Polar_Stereographic PROJCS["WGS_1984_EPSG_Russia_Polar_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D
6050 GR96_EPSG_Arctic_zone_1-25 PROJCS["GR96_EPSG_Arctic_zone_1-25",GEOGCS["GCS_Greenland_1996",DATUM["D_Greenland
6069 ETRS_1989_EPSG_Arctic_zone_2-22 PROJCS["ETRS_1989_EPSG_Arctic_zone_2-22",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1
6075 WGS_1984_EPSG_Arctic_zone_2-24 PROJCS["WGS_1984_EPSG_Arctic_zone_2-24",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_198
6094 NAD_1983_NSRS2007_EPSG_Arctic_zone_5-29 PROJCS["NAD_1983_NSRS2007_EPSG_Arctic_zone_5-29",GEOGCS["GCS_NAD_1983_NSRS2007
6098 NAD_1983_CSRS_EPSG_Arctic_zone_1-23 PROJCS["NAD_1983_CSRS_EPSG_Arctic_zone_1-23",GEOGCS["GCS_North_American_1983_CSR


6128 Grand_Cayman_National_Grid_1959 PROJCS["Grand_Cayman_National_Grid_1959",GEOGCS["GCS_Grand_Cayman_1959",DATUM["D_
6129 Sister_Islands_National_Grid_1961 PROJCS["Sister_Islands_National_Grid_1961",GEOGCS["GCS_Little_Cayman_1961",DATUM["D_Litt
6141 Cayman_Islands_National_Grid_2011 PROJCS["Cayman_Islands_National_Grid_2011",GEOGCS["GCS_CIGD11",DATUM["D_Cayman_Isla
6204 Macedonian_State_Coordinate_System PROJCS["Macedonian_State_Coordinate_System",GEOGCS["GCS_MGI_1901",DATUM["D_MGI_190
6210 SIRGAS_2000_UTM_Zone_23N PROJCS["SIRGAS_2000_UTM_Zone_23N",GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIRGAS_20
6211 SIRGAS_2000_UTM_Zone_24N PROJCS["SIRGAS_2000_UTM_Zone_24N",GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIRGAS_20
6244 MAGNA_Arauca_2007 PROJCS["MAGNA_Arauca_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["GRS
6245 MAGNA_Armenia_Quindio_2006 PROJCS["MAGNA_Armenia_Quindio_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6246 MAGNA_Barranquilla_Atlantico_1997 PROJCS["MAGNA_Barranquilla_Atlantico_1997",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPH
6247 MAGNA_Bogota_DC_2005 PROJCS["MAGNA_Bogota_DC_2005",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["G
6248 MAGNA_Bucaramanga_Santander_2008 PROJCS["MAGNA_Bucaramanga_Santander_2008",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA"
6249 MAGNA_Cali_Valle_del_Cauca_2009 PROJCS["MAGNA_Cali_Valle_del_Cauca_2009",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPH
6250 MAGNA_Cartagena_Bolivar_2005 PROJCS["MAGNA_Cartagena_Bolivar_2005",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6251 MAGNA_Cucuta_Norte_de_Santander_2011 PROJCS["MAGNA_Cucuta_Norte_de_Santander_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGN
6252 MAGNA_Florencia_Caqueta_2007 PROJCS["MAGNA_Florencia_Caqueta_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHE
6253 MAGNA_Ibague_Tolima_2007 PROJCS["MAGNA_Ibague_Tolima_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID
6254 MAGNA_Inirida_Guainia_2008 PROJCS["MAGNA_Inirida_Guainia_2008",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROI
6255 MAGNA_Leticia_Amazonas_1994 PROJCS["MAGNA_Leticia_Amazonas_1994",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6256 MAGNA_Manizales_Caldas_2011 PROJCS["MAGNA_Manizales_Caldas_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6257 MAGNA_Medellin_Antioquia_2010 PROJCS["MAGNA_Medellin_Antioquia_2010",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHE
6258 MAGNA_Mitu_Vaupes_2011 PROJCS["MAGNA_Mitu_Vaupes_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID[
6259 MAGNA_Mocoa_Putumayo_2011 PROJCS["MAGNA_Mocoa_Putumayo_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6260 MAGNA_Monteria_Cordoba_2006 PROJCS["MAGNA_Monteria_Cordoba_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6261 MAGNA_Neiva_Huila_2006 PROJCS["MAGNA_Neiva_Huila_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["
6262 MAGNA_Pasto_Narino_2008 PROJCS["MAGNA_Pasto_Narino_2008",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID
6263 MAGNA_Pereira_Risaralda_2007 PROJCS["MAGNA_Pereira_Risaralda_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6264 MAGNA_Popayan_Cauca_2006 PROJCS["MAGNA_Popayan_Cauca_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHERO

6265 MAGNA_Puerto_Carreno_Vichada_2011 PROJCS["MAGNA_Puerto_Carreno_Vichada_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",

6266 MAGNA_Quibdo_Choco_2011 PROJCS["MAGNA_Quibdo_Choco_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID
6267 MAGNA_Riohacha_La_Guajira_2006 PROJCS["MAGNA_Riohacha_La_Guajira_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPH
6268 MAGNA_San_Andres_2007 PROJCS["MAGNA_San_Andres_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["
6269 MAGNA_San_Jose_del_Guaviare_2011 PROJCS["MAGNA_San_Jose_del_Guaviare_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",S
6270 MAGNA_Santa_Marta_Magdalena_2007 PROJCS["MAGNA_Santa_Marta_Magdalena_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",
6271 MAGNA_Sucre_2006 PROJCS["MAGNA_Sucre_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID["GRS_
6272 MAGNA_Tunja_Boyaca_1997 PROJCS["MAGNA_Tunja_Boyaca_1997",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID
6273 MAGNA_Valledupar_Cesar_2011 PROJCS["MAGNA_Valledupar_Cesar_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6274 MAGNA_Villavicencio_Meta_2011 PROJCS["MAGNA_Villavicencio_Meta_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
6275 MAGNA_Yopal_Casanare_2006 PROJCS["MAGNA_Yopal_Casanare_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHERO
6307 NAD_1983_CORS96_SPCS_Puerto_Rico_and_Virgin_Islands PROJCS["NAD_1983_CORS96_SPCS_Puerto_Rico_and_Virgin_Islands",GEOGCS["GCS_NAD_198
6312 CGRS_1993_Cyprus_Local_Transverse_Mercator PROJCS["CGRS_1993_Cyprus_Local_Transverse_Mercator",GEOGCS["GCS_CGRS_1993",DATUM
6316 Macedonia_State_Coordinate_System_zone_7 PROJCS["Macedonia_State_Coordinate_System_zone_7",GEOGCS["GCS_MGI_1901",DATUM["D_M
6328 NAD_1983_2011_UTM_Zone_59N PROJCS["NAD_1983_2011_UTM_Zone_59N",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1
6350 NAD_1983_2011_Contiguous_USA_Albers PROJCS["NAD_1983_2011_Contiguous_USA_Albers",GEOGCS["GCS_NAD_1983_2011",DATUM["D
6351 NAD_1983_2011_EPSG_Arctic_zone_5-29 PROJCS["NAD_1983_2011_EPSG_Arctic_zone_5-29",GEOGCS["GCS_NAD_1983_2011",DATUM["D
6355 NAD_1983_2011_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1983_2011_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_NAD_1983_20
6356 NAD_1983_2011_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1983_2011_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_NAD_1983_20
6362 Mexico_ITRF92_LCC PROJCS["Mexico_ITRF92_LCC",GEOGCS["GCS_Mexican_Datum_of_1993",DATUM["D_Mexican_Da
6366 Mexico_ITRF2008_UTM_Zone_11N PROJCS["Mexico_ITRF2008_UTM_Zone_11N",GEOGCS["GCS_Mexico_ITRF2008",DATUM["D_Mex
6372 Mexico_ITRF2008_LCC PROJCS["Mexico_ITRF2008_LCC",GEOGCS["GCS_Mexico_ITRF2008",DATUM["D_Mexico_ITRF200
6381 Ukraine_2000_TM_Zone_7 PROJCS["Ukraine_2000_TM_Zone_7",GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukraine_2000",SP
6384 Ukraine_2000_TM_Zone_10 PROJCS["Ukraine_2000_TM_Zone_10",GEOGCS["GCS_Ukraine_2000",DATUM["D_Ukraine_2000",S


6391 Cayman_Islands_National_Grid_2011 PROJCS["Cayman_Islands_National_Grid_2011",GEOGCS["GCS_CIGD11",DATUM["D_Cayman_Isla
6393 NAD_1983_2011_Alaska_Albers PROJCS["NAD_1983_2011_Alaska_Albers",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_198
6394 NAD_1983_2011_StatePlane_Alaska_1_FIPS_5001 PROJCS["NAD_1983_2011_StatePlane_Alaska_1_FIPS_5001",GEOGCS["GCS_NAD_1983_2011",D
6404 NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_NAD_1983_2
6405 NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl",GEOGCS["GCS_NAD_
6406 NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_NAD_1983_201
6407 NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201_Ft_Intl",GEOGCS["GCS_NAD_19
6408 NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_NAD_1983_201
6409 NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203_Ft_Intl",GEOGCS["GCS_NAD_19
6410 NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_NAD_1983_2
6411 NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301_Ft_US",GEOGCS["GCS_NAD_
6412 NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_NAD_1983_2
6413 NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302_Ft_US",GEOGCS["GCS_NAD_
6414 NAD_1983_2011_California_Teale_Albers PROJCS["NAD_1983_2011_California_Teale_Albers",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
6415 NAD_1983_2011_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1983_2011_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_NAD_1983_2011"
6416 NAD_1983_2011_StatePlane_California_I_FIPS_0401_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_I_FIPS_0401_Ft_US",GEOGCS["GCS_NAD_1983
6417 NAD_1983_2011_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1983_2011_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_NAD_1983_2011
6418 NAD_1983_2011_StatePlane_California_II_FIPS_0402_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_II_FIPS_0402_Ft_US",GEOGCS["GCS_NAD_198
6419 NAD_1983_2011_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1983_2011_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_NAD_1983_2011
6420 NAD_1983_2011_StatePlane_California_III_FIPS_0403_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_III_FIPS_0403_Ft_US",GEOGCS["GCS_NAD_198
6421 NAD_1983_2011_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1983_2011_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_NAD_1983_2011
6422 NAD_1983_2011_StatePlane_California_IV_FIPS_0404_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_IV_FIPS_0404_Ft_US",GEOGCS["GCS_NAD_198
6423 NAD_1983_2011_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1983_2011_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_NAD_1983_2011
6424 NAD_1983_2011_StatePlane_California_V_FIPS_0405_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_V_FIPS_0405_Ft_US",GEOGCS["GCS_NAD_198
6425 NAD_1983_2011_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1983_2011_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_NAD_1983_2011
6426 NAD_1983_2011_StatePlane_California_VI_FIPS_0406_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_VI_FIPS_0406_Ft_US",GEOGCS["GCS_NAD_198
6427 NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_NAD_1983_
6428 NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502_Ft_US",GEOGCS["GCS_NAD
6429 NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_NAD_1983_2
6430 NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501_Ft_US",GEOGCS["GCS_NAD_
6431 NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_NAD_1983_2
6432 NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503_Ft_US PROJCS["NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503_Ft_US",GEOGCS["GCS_NAD_
6433 NAD_1983_2011_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1983_2011_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_NAD_1983_2011"
6434 NAD_1983_2011_StatePlane_Connecticut_FIPS_0600_Ft_US PROJCS["NAD_1983_2011_StatePlane_Connecticut_FIPS_0600_Ft_US",GEOGCS["GCS_NAD_198
6435 NAD_1983_2011_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1983_2011_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_NAD_1983_2011",D
6436 NAD_1983_2011_StatePlane_Delaware_FIPS_0700_Ft_US PROJCS["NAD_1983_2011_StatePlane_Delaware_FIPS_0700_Ft_US",GEOGCS["GCS_NAD_1983_
6437 NAD_1983_2011_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1983_2011_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_NAD_1983_2011
6438 NAD_1983_2011_StatePlane_Florida_East_FIPS_0901_Ft_US PROJCS["NAD_1983_2011_StatePlane_Florida_East_FIPS_0901_Ft_US",GEOGCS["GCS_NAD_198
6439 NAD_1983_2011_Florida_GDL_Albers PROJCS["NAD_1983_2011_Florida_GDL_Albers",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
6440 NAD_1983_2011_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1983_2011_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_NAD_1983_201
6441 NAD_1983_2011_StatePlane_Florida_North_FIPS_0903_Ft_US PROJCS["NAD_1983_2011_StatePlane_Florida_North_FIPS_0903_Ft_US",GEOGCS["GCS_NAD_19
6442 NAD_1983_2011_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1983_2011_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_NAD_1983_2011

6443 NAD_1983_2011_StatePlane_Florida_West_FIPS_0902_Ft_US PROJCS["NAD_1983_2011_StatePlane_Florida_West_FIPS_0902_Ft_US",GEOGCS["GCS_NAD_19

6444 NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_NAD_1983_201
6445 NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001_Ft_US PROJCS["NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001_Ft_US",GEOGCS["GCS_NAD_19
6446 NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_NAD_1983_201
6447 NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002_Ft_US PROJCS["NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002_Ft_US",GEOGCS["GCS_NAD_1
6448 NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_NAD_1983_201
6449 NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102_Ft_US PROJCS["NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102_Ft_US",GEOGCS["GCS_NAD_19
6450 NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_NAD_1983_2011"
6451 NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101_Ft_US PROJCS["NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101_Ft_US",GEOGCS["GCS_NAD_1983
6452 NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_NAD_1983_2011"
6453 NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103_Ft_US PROJCS["NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103_Ft_US",GEOGCS["GCS_NAD_198
6454 NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_NAD_1983_2011
6455 NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201_Ft_US PROJCS["NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201_Ft_US",GEOGCS["GCS_NAD_198
6456 NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_NAD_1983_2011
6457 NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202_Ft_US PROJCS["NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202_Ft_US",GEOGCS["GCS_NAD_198
6458 NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_NAD_1983_2011
6459 NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301_Ft_US",GEOGCS["GCS_NAD_19
6460 NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_NAD_1983_201
6461 NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302_Ft_US",GEOGCS["GCS_NAD_19
6462 NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_NAD_1983_2011"
6463 NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401_Ft_US PROJCS["NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401_Ft_US",GEOGCS["GCS_NAD_1983
6464 NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_NAD_1983_2011"
6465 NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402_Ft_US PROJCS["NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402_Ft_US",GEOGCS["GCS_NAD_198
6466 NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_NAD_1983_201
6467 NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501_Ft_US",GEOGCS["GCS_NAD_19
6468 NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_NAD_1983_20
6469 NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502_Ft_US",GEOGCS["GCS_NAD_1
6470 NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_NAD_1983_2
6471 NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601_Ft_US",GEOGCS["GCS_NAD_
6472 NAD_1983_2011_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_2011_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_NAD_1983_2011",D
6473 NAD_1983_2011_StatePlane_Kentucky_FIPS_1600_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kentucky_FIPS_1600_Ft_US",GEOGCS["GCS_NAD_1983_2
6474 NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_NAD_1983_2
6475 NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602_Ft_US",GEOGCS["GCS_NAD_
6476 NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_NAD_1983_2
6477 NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701_Ft_US PROJCS["NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701_Ft_US",GEOGCS["GCS_NAD_
6478 NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_NAD_1983_2
6479 NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702_Ft_US PROJCS["NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702_Ft_US",GEOGCS["GCS_NAD_
6480 NAD_1983_2011_Maine_2000_Central_Zone PROJCS["NAD_1983_2011_Maine_2000_Central_Zone",GEOGCS["GCS_NAD_1983_2011",DATUM[
6481 NAD_1983_2011_Maine_2000_East_Zone PROJCS["NAD_1983_2011_Maine_2000_East_Zone",GEOGCS["GCS_NAD_1983_2011",DATUM["D
6482 NAD_1983_2011_Maine_2000_West_Zone PROJCS["NAD_1983_2011_Maine_2000_West_Zone",GEOGCS["GCS_NAD_1983_2011",DATUM["D
6483 NAD_1983_2011_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1983_2011_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_NAD_1983_2011"
6484 NAD_1983_2011_StatePlane_Maine_East_FIPS_1801_Ft_US PROJCS["NAD_1983_2011_StatePlane_Maine_East_FIPS_1801_Ft_US",GEOGCS["GCS_NAD_198
6485 NAD_1983_2011_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1983_2011_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_NAD_1983_2011
6486 NAD_1983_2011_StatePlane_Maine_West_FIPS_1802_Ft_US PROJCS["NAD_1983_2011_StatePlane_Maine_West_FIPS_1802_Ft_US",GEOGCS["GCS_NAD_198
6487 NAD_1983_2011_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1983_2011_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_NAD_1983_2011",D
6488 NAD_1983_2011_StatePlane_Maryland_FIPS_1900_Ft_US PROJCS["NAD_1983_2011_StatePlane_Maryland_FIPS_1900_Ft_US",GEOGCS["GCS_NAD_1983_2
6489 NAD_1983_2011_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["GCS_NAD_1
6490 NAD_1983_2011_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS",GEOGCS["GCS_NAD
6491 NAD_1983_2011_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS["GCS_NAD
6492 NAD_1983_2011_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS",GEOGCS["GCS_NA
6493 NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_NAD_1983_
6494 NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl",GEOGCS["GCS_NAD
6495 NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_NAD_1983_20
6496 NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111_Ft_Intl",GEOGCS["GCS_NAD_1

6497 NAD_1983_2011_Michigan_GeoRef_Meters PROJCS["NAD_1983_2011_Michigan_GeoRef_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM["

6498 NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_NAD_1983_2
6499 NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113_Ft_Intl",GEOGCS["GCS_NAD_
6500 NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS_NAD_1983
6501 NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202_Ft_US PROJCS["NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202_Ft_US",GEOGCS["GCS_NA
6502 NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_NAD_1983_
6503 NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201_Ft_US PROJCS["NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201_Ft_US",GEOGCS["GCS_NAD
6504 NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_NAD_1983_
6505 NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203_Ft_US PROJCS["NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203_Ft_US",GEOGCS["GCS_NAD
6506 NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_NAD_1983_2
6507 NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301_Ft_US",GEOGCS["GCS_NAD_
6508 NAD_1983_2011_Mississippi_TM PROJCS["NAD_1983_2011_Mississippi_TM",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_19
6509 NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_NAD_1983_
6510 NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302_Ft_US",GEOGCS["GCS_NAD
6511 NAD_1983_2011_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1983_2011_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_NAD_1983_
6512 NAD_1983_2011_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1983_2011_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_NAD_1983_201
6513 NAD_1983_2011_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1983_2011_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_NAD_1983_20
6514 NAD_1983_2011_StatePlane_Montana_FIPS_2500 PROJCS["NAD_1983_2011_StatePlane_Montana_FIPS_2500",GEOGCS["GCS_NAD_1983_2011",DA
6515 NAD_1983_2011_StatePlane_Montana_FIPS_2500_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Montana_FIPS_2500_Ft_Intl",GEOGCS["GCS_NAD_1983_2
6516 NAD_1983_2011_StatePlane_Nebraska_FIPS_2600 PROJCS["NAD_1983_2011_StatePlane_Nebraska_FIPS_2600",GEOGCS["GCS_NAD_1983_2011",D
6518 NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_NAD_1983_2
6519 NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702_Ft_US",GEOGCS["GCS_NAD_
6520 NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_NAD_1983_201
6521 NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701_Ft_US",GEOGCS["GCS_NAD_19
6522 NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_NAD_1983_201
6523 NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703_Ft_US",GEOGCS["GCS_NAD_19
6524 NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_NAD_1983_2
6525 NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800_Ft_US",GEOGCS["GCS_NAD_
6526 NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_NAD_1983_2011
6527 NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900_Ft_US",GEOGCS["GCS_NAD_198
6528 NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["GCS_NAD_19
6529 NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US",GEOGCS["GCS_N
6530 NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS_NAD_1983
6531 NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001_Ft_US",GEOGCS["GCS_NA
6532 NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS_NAD_1983
6533 NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003_Ft_US",GEOGCS["GCS_NA
6534 NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS_NAD_1983
6535 NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102_Ft_US",GEOGCS["GCS_NA
6536 NAD_1983_2011_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1983_2011_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_NAD_1983_2
6537 NAD_1983_2011_StatePlane_New_York_East_FIPS_3101_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_East_FIPS_3101_Ft_US",GEOGCS["GCS_NAD_
6538 NAD_1983_2011_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1983_2011_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GCS_NAD_
6539 NAD_1983_2011_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US",GEOGCS["GCS_N
6540 NAD_1983_2011_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1983_2011_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_NAD_1983_2
6541 NAD_1983_2011_StatePlane_New_York_West_FIPS_3103_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_West_FIPS_3103_Ft_US",GEOGCS["GCS_NAD_
6542 NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200 PROJCS["NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_NAD_1983_20
6543 NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200_Ft_US PROJCS["NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200_Ft_US",GEOGCS["GCS_NAD_1
6544 NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GCS_NAD_198
6545 NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301_FtI PROJCS["NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301_FtI",GEOGCS["GCS_NAD
6546 NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GCS_NAD_19
6547 NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302_FtI PROJCS["NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302_FtI",GEOGCS["GCS_NAD
6548 NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_NAD_1983_2011"
6549 NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401_Ft_US PROJCS["NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401_Ft_US",GEOGCS["GCS_NAD_1983
6550 NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_NAD_1983_2011"
6551 NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402_Ft_US PROJCS["NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402_Ft_US",GEOGCS["GCS_NAD_198

6552 NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_NAD_1983_

6553 NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501_Ft_US",GEOGCS["GCS_NAD
6554 NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_NAD_1983_
6555 NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502_Ft_US",GEOGCS["GCS_NAD
6556 NAD_1983_2011_Oregon_Statewide_Lambert PROJCS["NAD_1983_2011_Oregon_Statewide_Lambert",GEOGCS["GCS_NAD_1983_2011",DATUM
6557 NAD_1983_2011_Oregon_Statewide_Lambert_Ft_Intl PROJCS["NAD_1983_2011_Oregon_Statewide_Lambert_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",
6558 NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_NAD_1983_201
6559 NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601_Ft_Intl",GEOGCS["GCS_NAD_19
6560 NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_NAD_1983_20
6561 NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602_Ft_Intl",GEOGCS["GCS_NAD_1
6562 NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701 PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701",GEOGCS["GCS_NAD_198
6563 NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US",GEOGCS["GCS_N
6564 NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GCS_NAD_198
6565 NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US",GEOGCS["GCS_N
6566 NAD_1983_2011_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200 PROJCS["NAD_1983_2011_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200",GEOGCS["GCS_NAD_
6567 NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_NAD_1983_201
6568 NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800_Ft_US PROJCS["NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800_Ft_US",GEOGCS["GCS_NAD_19
6569 NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900 PROJCS["NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900",GEOGCS["GCS_NAD_1983_20
6570 NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900_Ft_Intl",GEOGCS["GCS_NAD_1
6571 NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GCS_NAD_19
6572 NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001_Ft_US PROJCS["NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001_Ft_US",GEOGCS["GCS_N
6573 NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["GCS_NAD_19
6574 NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002_Ft_US PROJCS["NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002_Ft_US",GEOGCS["GCS_N
6575 NAD_1983_2011_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1983_2011_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_NAD_1983_2011",
6576 NAD_1983_2011_StatePlane_Tennessee_FIPS_4100_Ft_US PROJCS["NAD_1983_2011_StatePlane_Tennessee_FIPS_4100_Ft_US",GEOGCS["GCS_NAD_1983
6577 NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_NAD_1983_20
6578 NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203_Ft_US PROJCS["NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203_Ft_US",GEOGCS["GCS_NAD_1
6579 NAD_1983_2011_Texas_Centric_Mapping_System_Albers PROJCS["NAD_1983_2011_Texas_Centric_Mapping_System_Albers",GEOGCS["GCS_NAD_1983_2
6580 NAD_1983_2011_Texas_Centric_Mapping_System_Lambert PROJCS["NAD_1983_2011_Texas_Centric_Mapping_System_Lambert",GEOGCS["GCS_NAD_1983_
6581 NAD_1983_2011_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1983_2011_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_NAD_1983_2011
6582 NAD_1983_2011_StatePlane_Texas_North_FIPS_4201_Ft_US PROJCS["NAD_1983_2011_StatePlane_Texas_North_FIPS_4201_Ft_US",GEOGCS["GCS_NAD_198
6583 NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["GCS_NAD_19
6584 NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202_FtUS PROJCS["NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202_FtUS",GEOGCS["GCS_N
6585 NAD_1983_2011_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1983_2011_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_NAD_1983_2011
6586 NAD_1983_2011_StatePlane_Texas_South_FIPS_4205_Ft_US PROJCS["NAD_1983_2011_StatePlane_Texas_South_FIPS_4205_Ft_US",GEOGCS["GCS_NAD_19
6587 NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["GCS_NAD_19
6588 NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204_FtUS PROJCS["NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204_FtUS",GEOGCS["GCS_N
6589 NAD_1983_2011_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1983_2011_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_NAD_1983_2011",DA
6590 NAD_1983_2011_StatePlane_Vermont_FIPS_4400_Ft_US PROJCS["NAD_1983_2011_StatePlane_Vermont_FIPS_4400_Ft_US",GEOGCS["GCS_NAD_1983_2
6591 NAD_1983_2011_Virginia_Lambert PROJCS["NAD_1983_2011_Virginia_Lambert",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1
6592 NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_NAD_1983_201
6593 NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501_Ft_US",GEOGCS["GCS_NAD_19
6594 NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_NAD_1983_20
6595 NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502_Ft_US",GEOGCS["GCS_NAD_1
6596 NAD_1983_2011_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1983_2011_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS_NAD_1983
6597 NAD_1983_2011_StatePlane_Washington_North_FIPS_4601_Ft_US PROJCS["NAD_1983_2011_StatePlane_Washington_North_FIPS_4601_Ft_US",GEOGCS["GCS_NA
6598 NAD_1983_2011_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1983_2011_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS_NAD_1983
6599 NAD_1983_2011_StatePlane_Washington_South_FIPS_4602_Ft_US PROJCS["NAD_1983_2011_StatePlane_Washington_South_FIPS_4602_Ft_US",GEOGCS["GCS_NA
6600 NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GCS_NAD_198
6601 NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701_FtUS PROJCS["NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701_FtUS",GEOGCS["GCS_NA
6602 NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GCS_NAD_19
6603 NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702_FtUS PROJCS["NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702_FtUS",GEOGCS["GCS_NA
6605 NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US",GEOGCS["GCS_NA
6606 NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_NAD_1983_

6607 NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801_Ft_US",GEOGCS["GCS_NAD

6608 NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_NAD_1983_
6609 NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803_Ft_US",GEOGCS["GCS_NAD
6610 NAD_1983_2011_Wisconsin_TM PROJCS["NAD_1983_2011_Wisconsin_TM",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_19
6611 NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_NAD_1983_20
6612 NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901_Ft_US",GEOGCS["GCS_NAD_1
6613 NAD_1983_2011_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1983_2011_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS["GCS_NAD_
6614 NAD_1983_2011_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US",GEOGCS["GCS_N
6615 NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_NAD_1983_2
6616 NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904_Ft_US",GEOGCS["GCS_NAD_
6617 NAD_1983_2011_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1983_2011_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS["GCS_NAD_
6618 NAD_1983_2011_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US",GEOGCS["GCS_N
6619 NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_NAD_1983_201
6620 NAD_1983_2011_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1983_2011_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_NAD_1983_2011"
6621 NAD_1983_2011_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1983_2011_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_NAD_1983_2011"
6622 NAD_1983_CSRS_Quebec_Lambert PROJCS["NAD_1983_CSRS_Quebec_Lambert",GEOGCS["GCS_North_American_1983_CSRS",DAT
6623 NAD_1983_Quebec_Albers PROJCS["NAD_1983_Quebec_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_North_Am
6624 NAD_1983_CSRS_Quebec_Albers PROJCS["NAD_1983_CSRS_Quebec_Albers",GEOGCS["GCS_North_American_1983_CSRS",DATU
6625 NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302_Ft_US",GEOGCS["GCS_NAD_19
6626 NAD_1983_2011_StatePlane_Utah_North_FIPS_4301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Utah_North_FIPS_4301_Ft_US",GEOGCS["GCS_NAD_1983
6627 NAD_1983_2011_StatePlane_Utah_South_FIPS_4303_Ft_US PROJCS["NAD_1983_2011_StatePlane_Utah_South_FIPS_4303_Ft_US",GEOGCS["GCS_NAD_198
6628 NAD_1983_PA11_StatePlane_Hawaii_1_FIPS_5101 PROJCS["NAD_1983_PA11_StatePlane_Hawaii_1_FIPS_5101",GEOGCS["GCS_NAD_1983_PA11",D
6633 NAD_1983_PA11_StatePlane_Hawaii_3_FIPS_5103_Feet PROJCS["NAD_1983_PA11_StatePlane_Hawaii_3_FIPS_5103_Feet",GEOGCS["GCS_NAD_1983_PA
6634 NAD_1983_PA11_UTM_Zone_4N PROJCS["NAD_1983_PA11_UTM_Zone_4N",GEOGCS["GCS_NAD_1983_PA11",DATUM["D_NAD_1
6635 NAD_1983_PA11_UTM_Zone_5N PROJCS["NAD_1983_PA11_UTM_Zone_5N",GEOGCS["GCS_NAD_1983_PA11",DATUM["D_NAD_1
6636 NAD_1983_PA11_UTM_Zone_2S PROJCS["NAD_1983_PA11_UTM_Zone_2S",GEOGCS["GCS_NAD_1983_PA11",DATUM["D_NAD_19
6637 NAD_1983_MA11_Guam_Map_Grid PROJCS["NAD_1983_MA11_Guam_Map_Grid",GEOGCS["GCS_NAD_1983_MA11",DATUM["D_NAD
6646 Karbala_1979_Iraq_National_Grid PROJCS["Karbala_1979_Iraq_National_Grid",GEOGCS["GCS_Karbala_1979_Polservice",DATUM["D_


6703 WGS_1984_TM_60_SW PROJCS["WGS_1984_TM_60_SW",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
6707 RDN2008_TM32 PROJCS["RDN2008_TM32",GEOGCS["GCS_RDN2008",DATUM["D_Rete_Dinamica_Nazionale_2008
6720 WGS_1984_CIG92 PROJCS["WGS_1984_CIG92",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["W
6721 GDA_1994_CIG94 PROJCS["GDA_1994_CIG94",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["GR
6722 WGS_1984_CKIG92 PROJCS["WGS_1984_CKIG92",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["
6723 GDA_1994_CKIG94 PROJCS["GDA_1994_CKIG94",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHEROID["G
6732 GDA_1994_MGA_zone_41 PROJCS["GDA_1994_MGA_zone_41",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHER
6736 GDA_1994_MGA_Zone_46 PROJCS["GDA_1994_MGA_Zone_46",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SPHER
6784 OCRS_Baker_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Baker_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CORS96",D
6785 OCRS_Baker_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Baker_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_CORS96"
6786 OCRS_Baker_NAD_1983_2011_TM_Meters PROJCS["OCRS_Baker_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM["
6787 OCRS_Baker_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Baker_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM
6788 OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_198
6789 OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1
6790 OCRS_Bend-Klamath_Falls_NAD_1983_2011_TM_Meters PROJCS["OCRS_Bend-Klamath_Falls_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2
6791 OCRS_Bend-Klamath_Falls_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Bend-Klamath_Falls_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_
6792 OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Meters",GEOGCS["GCS_NA
6793 OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS["GCS_N
6794 OCRS_Bend-Redmond-Prineville_NAD_1983_2011_LCC_Meters PROJCS["OCRS_Bend-Redmond-Prineville_NAD_1983_2011_LCC_Meters",GEOGCS["GCS_NAD_1
6795 OCRS_Bend-Redmond-Prineville_NAD_1983_2011_LCC_Feet_Intl PROJCS["OCRS_Bend-Redmond-Prineville_NAD_1983_2011_LCC_Feet_Intl",GEOGCS["GCS_NAD
6796 OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Meters",GEOGCS["GCS_NAD_1983_COR
6797 OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS["GCS_NAD_1983_CO
6798 OCRS_Bend-Burns_NAD_1983_2011_LCC_Meters PROJCS["OCRS_Bend-Burns_NAD_1983_2011_LCC_Meters",GEOGCS["GCS_NAD_1983_2011",DA
6799 OCRS_Bend-Burns_NAD_1983_2011_LCC_Feet_Intl PROJCS["OCRS_Bend-Burns_NAD_1983_2011_LCC_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",
6800 OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD
6801 OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NA
6802 OCRS_Canyonville-Grants_Pass_NAD_1983_2011_TM_Meters PROJCS["OCRS_Canyonville-Grants_Pass_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_19
6803 OCRS_Canyonville-Grants_Pass_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Canyonville-Grants_Pass_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1
6804 OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Meters",GEOGCS["GCS_NAD_1
6805 OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS["GCS_NAD
6806 OCRS_Columbia_River_East_NAD_1983_2011_LCC_Meters PROJCS["OCRS_Columbia_River_East_NAD_1983_2011_LCC_Meters",GEOGCS["GCS_NAD_1983
6807 OCRS_Columbia_River_East_NAD_1983_2011_LCC_Feet_Intl PROJCS["OCRS_Columbia_River_East_NAD_1983_2011_LCC_Feet_Intl",GEOGCS["GCS_NAD_198
6808 OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Meters PROJCS["OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Meters",GEOGCS["GCS_NAD_1
6809 OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Feet_Intl PROJCS["OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Feet_Intl",GEOGCS["GCS_NAD_
6810 OCRS_Columbia_River_West_NAD_1983_2011_OM_Meters PROJCS["OCRS_Columbia_River_West_NAD_1983_2011_OM_Meters",GEOGCS["GCS_NAD_1983
6811 OCRS_Columbia_River_West_NAD_1983_2011_OM_Feet_Intl PROJCS["OCRS_Columbia_River_West_NAD_1983_2011_OM_Feet_Intl",GEOGCS["GCS_NAD_198
6812 OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NA
6813 OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_
6814 OCRS_Cottage_Grove-Canyonville_NAD_1983_2011_TM_Meters PROJCS["OCRS_Cottage_Grove-Canyonville_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_
6815 OCRS_Cottage_Grove-Canyonville_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Cottage_Grove-Canyonville_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD
6816 OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CO
6817 OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_C
6818 OCRS_Dufur-Madras_NAD_1983_2011_TM_Meters PROJCS["OCRS_Dufur-Madras_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",D
6819 OCRS_Dufur-Madras_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Dufur-Madras_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011"
6820 OCRS_Eugene_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Eugene_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CORS96"

6821 OCRS_Eugene_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Eugene_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_CORS9

6822 OCRS_Eugene_NAD_1983_2011_TM_Meters PROJCS["OCRS_Eugene_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM
6823 OCRS_Eugene_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Eugene_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",DATU
6824 OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_19
6825 OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_
6826 OCRS_Grants_Pass-Ashland_NAD_1983_2011_TM_Meters PROJCS["OCRS_Grants_Pass-Ashland_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_
6827 OCRS_Grants_Pass-Ashland_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Grants_Pass-Ashland_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_198
6828 OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD
6829 OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NA
6830 OCRS_Gresham-Warm_Springs_NAD_1983_2011_TM_Meters PROJCS["OCRS_Gresham-Warm_Springs_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_198
6831 OCRS_Gresham-Warm_Springs_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Gresham-Warm_Springs_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1
6832 OCRS_La_Grande_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_La_Grande_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CORS
6833 OCRS_La_Grande_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_La_Grande_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_COR
6834 OCRS_La_Grande_NAD_1983_2011_TM_Meters PROJCS["OCRS_La_Grande_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
6835 OCRS_La_Grande_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_La_Grande_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",DA
6836 OCRS_Ontario_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Ontario_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CORS96"
6837 OCRS_Ontario_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Ontario_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_CORS96
6838 OCRS_Ontario_NAD_1983_2011_TM_Meters PROJCS["OCRS_Ontario_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM
6839 OCRS_Ontario_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Ontario_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",DATU
6840 OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Meters PROJCS["OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Meters",GEOGCS["GCS_NAD_1983_CO
6841 OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Feet_Intl PROJCS["OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Feet_Intl",GEOGCS["GCS_NAD_1983_C
6842 OCRS_Oregon_Coast_NAD_1983_2011_OM_Meters PROJCS["OCRS_Oregon_Coast_NAD_1983_2011_OM_Meters",GEOGCS["GCS_NAD_1983_2011",
6843 OCRS_Oregon_Coast_NAD_1983_2011_OM_Feet_Intl PROJCS["OCRS_Oregon_Coast_NAD_1983_2011_OM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011
6844 OCRS_Pendleton_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Pendleton_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CORS9
6845 OCRS_Pendleton_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Pendleton_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_CORS
6846 OCRS_Pendleton_NAD_1983_2011_TM_Meters PROJCS["OCRS_Pendleton_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",DATU
6847 OCRS_Pendleton_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Pendleton_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",DA
6848 OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1
6849 OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_
6850 OCRS_Pendleton-La_Grande_NAD_1983_2011_TM_Meters PROJCS["OCRS_Pendleton-La_Grande_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_
6851 OCRS_Pendleton-La_Grande_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Pendleton-La_Grande_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_198
6852 OCRS_Portland_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Portland_NAD_1983_CORS96_LCC_Meters",GEOGCS["GCS_NAD_1983_CORS9
6853 OCRS_Portland_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Portland_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS["GCS_NAD_1983_CORS
6854 OCRS_Portland_NAD_1983_2011_LCC_Meters PROJCS["OCRS_Portland_NAD_1983_2011_LCC_Meters",GEOGCS["GCS_NAD_1983_2011",DATU
6855 OCRS_Portland_NAD_1983_2011_LCC_Feet_Intl PROJCS["OCRS_Portland_NAD_1983_2011_LCC_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",DAT
6856 OCRS_Salem_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Salem_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CORS96",D
6857 OCRS_Salem_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Salem_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_CORS96
6858 OCRS_Salem_NAD_1983_2011_TM_Meters PROJCS["OCRS_Salem_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM["
6859 OCRS_Salem_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Salem_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM
6860 OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CO
6861 OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_C
6862 OCRS_Santiam_Pass_NAD_1983_2011_TM_Meters PROJCS["OCRS_Santiam_Pass_NAD_1983_2011_TM_Meters",GEOGCS["GCS_NAD_1983_2011",D
6863 OCRS_Santiam_Pass_NAD_1983_2011_TM_Feet_Intl PROJCS["OCRS_Santiam_Pass_NAD_1983_2011_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_2011
6867 NAD_1983_CORS96_Oregon_Statewide_Lambert PROJCS["NAD_1983_CORS96_Oregon_Statewide_Lambert",GEOGCS["GCS_NAD_1983_CORS96"
6868 NAD_1983_CORS96_Oregon_Statewide_Lambert_Ft_Intl PROJCS["NAD_1983_CORS96_Oregon_Statewide_Lambert_Ft_Intl",GEOGCS["GCS_NAD_1983_CO
6870 ETRS_1989_Albania_2010 PROJCS["ETRS_1989_Albania_2010",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHE
6875 RDN2008_Italy_zone PROJCS["RDN2008_Italy_zone",GEOGCS["GCS_RDN2008",DATUM["D_Rete_Dinamica_Nazionale_
6876 RDN2008_Zone_12 PROJCS["RDN2008_Zone_12",GEOGCS["GCS_RDN2008",DATUM["D_Rete_Dinamica_Nazionale_2
6879 NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS_NAD_1983
6880 NAD_1983_2011_StatePlane_Nebraska_FIPS_2600_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nebraska_FIPS_2600_Ft_US",GEOGCS["GCS_NAD_1983_
6884 NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_NAD_1983
6885 NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601_Ft_Intl",GEOGCS["GCS_NAD
6886 NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_NAD_1983
6887 NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602_Ft_Intl",GEOGCS["GCS_NA

6915 South_East_Island_1943_UTM_Zone_40N PROJCS["South_East_Island_1943_UTM_Zone_40N",GEOGCS["GCS_South_East_Island_1943",DA

6922 NAD_1983_Kansas_LCC PROJCS["NAD_1983_Kansas_LCC",GEOGCS["GCS_North_American_1983",DATUM["D_North_Ame
6923 NAD_1983_Kansas_LCC_ftUS PROJCS["NAD_1983_Kansas_LCC_ftUS",GEOGCS["GCS_North_American_1983",DATUM["D_North
6924 NAD_1983_2011_Kansas_LCC PROJCS["NAD_1983_2011_Kansas_LCC",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1983
6925 NAD_1983_2011_Kansas_LCC_ftUS PROJCS["NAD_1983_2011_Kansas_LCC_ftUS",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
6931 WGS_1984_EASE-Grid_2.0_North PROJCS["WGS_1984_EASE-Grid_2.0_North",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984"
6932 WGS_1984_EASE-Grid_2.0_South PROJCS["WGS_1984_EASE-Grid_2.0_South",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984"
6933 WGS_1984_EASE-Grid_2.0_Global PROJCS["WGS_1984_EASE-Grid_2.0_Global",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984
6956 VN_2000_TM-3_zone_481 PROJCS["VN_2000_TM-3_zone_481",GEOGCS["GCS_VN_2000",DATUM["D_Vietnam_2000",SPHER
6959 VN_2000_TM-3_Da_Nang_zone PROJCS["VN_2000_TM-3_Da_Nang_zone",GEOGCS["GCS_VN_2000",DATUM["D_Vietnam_2000",S
6962 ETRS_1989_Albania_LCC_2010 PROJCS["ETRS_1989_Albania_LCC_2010",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",
6984 Israeli_Grid_05 PROJCS["Israeli_Grid_05",GEOGCS["IG05_Intermediate_CRS",DATUM["IG05_Intermediate_Datum",
6991 Israeli_Grid_05-12 PROJCS["Israeli_Grid_05-12",GEOGCS["IG05(2012)_Intermediate_CRS",DATUM["IG05(2012)_Interm
7005 Nahrwan_1934_UTM_zone_37N PROJCS["Nahrwan_1934_UTM_zone_37N",GEOGCS["GCS_Nahrwan_1934",DATUM["D_Nahrwan_1
7057 NAD_1983_(2011)_IaRCS_zone_1 PROJCS["NAD_1983_(2011)_IaRCS_zone_1",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1
7066 NAD_1983_(2011)_IaRCS_zone_10 PROJCS["NAD_1983_(2011)_IaRCS_zone_10",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_
7074 RGTAAF07_UTM_zone_37S PROJCS["RGTAAF07_UTM_zone_37S",GEOGCS["GCS_RGTAAF07",DATUM["D_Reseau_Geodesiq
7082 RGTAAF07_Terre_Adelie_Polar_Stereographic PROJCS["RGTAAF07_Terre_Adelie_Polar_Stereographic",GEOGCS["GCS_RGTAAF07",DATUM["D_R
7109 NAD_1983_2011_RMTCRS_St_Mary_Meters PROJCS["NAD_1983_2011_RMTCRS_St_Mary_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM[
7110 NAD_1983_2011_RMTCRS_Blackfeet_Meters PROJCS["NAD_1983_2011_RMTCRS_Blackfeet_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM
7111 NAD_1983_2011_RMTCRS_Milk_River_Meters PROJCS["NAD_1983_2011_RMTCRS_Milk_River_Meters",GEOGCS["GCS_NAD_1983_2011",DATU
7112 NAD_1983_2011_RMTCRS_Fort_Belknap_Meters PROJCS["NAD_1983_2011_RMTCRS_Fort_Belknap_Meters",GEOGCS["GCS_NAD_1983_2011",DA
7113 NAD_1983_2011_RMTCRS_Fort_Peck_Assiniboine_Meters PROJCS["NAD_1983_2011_RMTCRS_Fort_Peck_Assiniboine_Meters",GEOGCS["GCS_NAD_1983_
7114 NAD_1983_2011_RMTCRS_Fort_Peck_Sioux_Meters PROJCS["NAD_1983_2011_RMTCRS_Fort_Peck_Sioux_Meters",GEOGCS["GCS_NAD_1983_2011"
7115 NAD_1983_2011_RMTCRS_Crow_Meters PROJCS["NAD_1983_2011_RMTCRS_Crow_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
7116 NAD_1983_2011_RMTCRS_Bobcat_Meters PROJCS["NAD_1983_2011_RMTCRS_Bobcat_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM["D
7117 NAD_1983_2011_RMTCRS_Billings_Meters PROJCS["NAD_1983_2011_RMTCRS_Billings_Meters",GEOGCS["GCS_NAD_1983_2011",DATUM["
7118 NAD_1983_2011_RMTCRS_Wind_River_Meters PROJCS["NAD_1983_2011_RMTCRS_Wind_River_Meters",GEOGCS["GCS_NAD_1983_2011",DATU
7119 NAD_1983_2011_RMTCRS_St_Mary_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_St_Mary_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM["
7120 NAD_1983_2011_RMTCRS_Blackfeet_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Blackfeet_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM
7121 NAD_1983_2011_RMTCRS_Milk_River_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Milk_River_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM

7122 NAD_1983_2011_RMTCRS_Fort_Belknap_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Fort_Belknap_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",DAT

7123 NAD_1983_2011_RMTCRS_Fort_Peck_Assiniboine_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Fort_Peck_Assiniboine_Ft_Intl",GEOGCS["GCS_NAD_1983_2
7124 NAD_1983_2011_RMTCRS_Fort_Peck_Sioux_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Fort_Peck_Sioux_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",
7125 NAD_1983_2011_RMTCRS_Crow_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Crow_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
7126 NAD_1983_2011_RMTCRS_Bobcat_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Bobcat_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM["D
7127 NAD_1983_2011_RMTCRS_Billings_Ft_Intl PROJCS["NAD_1983_2011_RMTCRS_Billings_Ft_Intl",GEOGCS["GCS_NAD_1983_2011",DATUM["D
7128 NAD_1983_2011_RMTCRS_Wind_River_(ftUS) PROJCS["NAD_1983_2011_RMTCRS_Wind_River_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATU
7131 NAD_1983_2011_San_Francisco_CS13_Meters PROJCS["NAD_1983_2011_San_Francisco_CS13_Meters",GEOGCS["GCS_NAD_1983_2011",DATU
7132 NAD_1983_2011_San_Francisco_CS13_ftUS PROJCS["NAD_1983_2011_San_Francisco_CS13_ftUS",GEOGCS["GCS_NAD_1983_2011",DATUM
7257 NAD_1983_2011_InGCS_Adams_(m) PROJCS["NAD_1983_2011_InGCS_Adams_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7258 NAD_1983_2011_InGCS_Adams_(ftUS) PROJCS["NAD_1983_2011_InGCS_Adams_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7259 NAD_1983_2011_InGCS_Allen_(m) PROJCS["NAD_1983_2011_InGCS_Allen_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_
7260 NAD_1983_2011_InGCS_Allen_(ftUS) PROJCS["NAD_1983_2011_InGCS_Allen_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7261 NAD_1983_2011_InGCS_Bartholomew_(m) PROJCS["NAD_1983_2011_InGCS_Bartholomew_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D
7262 NAD_1983_2011_InGCS_Bartholomew_(ftUS) PROJCS["NAD_1983_2011_InGCS_Bartholomew_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM
7263 NAD_1983_2011_InGCS_Benton_(m) PROJCS["NAD_1983_2011_InGCS_Benton_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7264 NAD_1983_2011_InGCS_Benton_(ftUS) PROJCS["NAD_1983_2011_InGCS_Benton_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7265 NAD_1983_2011_InGCS_Blackford-Delaware_(m) PROJCS["NAD_1983_2011_InGCS_Blackford-Delaware_(m)",GEOGCS["GCS_NAD_1983_2011",DAT
7266 NAD_1983_2011_InGCS_Blackford-Delaware_(ftUS) PROJCS["NAD_1983_2011_InGCS_Blackford-Delaware_(ftUS)",GEOGCS["GCS_NAD_1983_2011",D
7267 NAD_1983_2011_InGCS_Boone-Hendricks_(m) PROJCS["NAD_1983_2011_InGCS_Boone-Hendricks_(m)",GEOGCS["GCS_NAD_1983_2011",DATU
7268 NAD_1983_2011_InGCS_Boone-Hendricks_(ftUS) PROJCS["NAD_1983_2011_InGCS_Boone-Hendricks_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DA
7269 NAD_1983_2011_InGCS_Brown_(m) PROJCS["NAD_1983_2011_InGCS_Brown_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7270 NAD_1983_2011_InGCS_Brown_(ftUS) PROJCS["NAD_1983_2011_InGCS_Brown_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7271 NAD_1983_2011_InGCS_Carroll_(m) PROJCS["NAD_1983_2011_InGCS_Carroll_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7272 NAD_1983_2011_InGCS_Carroll_(ftUS) PROJCS["NAD_1983_2011_InGCS_Carroll_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7273 NAD_1983_2011_InGCS_Cass_(m) PROJCS["NAD_1983_2011_InGCS_Cass_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_
7274 NAD_1983_2011_InGCS_Cass_(ftUS) PROJCS["NAD_1983_2011_InGCS_Cass_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7275 NAD_1983_2011_InGCS_Clark-Floyd-Scott_(m) PROJCS["NAD_1983_2011_InGCS_Clark-Floyd-Scott_(m)",GEOGCS["GCS_NAD_1983_2011",DATU
7276 NAD_1983_2011_InGCS_Clark-Floyd-Scott_(ftUS) PROJCS["NAD_1983_2011_InGCS_Clark-Floyd-Scott_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DA
7277 NAD_1983_2011_InGCS_Clay_(m) PROJCS["NAD_1983_2011_InGCS_Clay_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1
7278 NAD_1983_2011_InGCS_Clay_(ftUS) PROJCS["NAD_1983_2011_InGCS_Clay_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7279 NAD_1983_2011_InGCS_Clinton_(m) PROJCS["NAD_1983_2011_InGCS_Clinton_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7280 NAD_1983_2011_InGCS_Clinton_(ftUS) PROJCS["NAD_1983_2011_InGCS_Clinton_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7281 NAD_1983_2011_InGCS_Crawford-Lawrence-Orange_(m) PROJCS["NAD_1983_2011_InGCS_Crawford-Lawrence-Orange_(m)",GEOGCS["GCS_NAD_1983_2
7282 NAD_1983_2011_InGCS_Crawford-Lawrence-Orange_(ftUS) PROJCS["NAD_1983_2011_InGCS_Crawford-Lawrence-Orange_(ftUS)",GEOGCS["GCS_NAD_1983
7283 NAD_1983_2011_InGCS_Daviess-Greene_(m) PROJCS["NAD_1983_2011_InGCS_Daviess-Greene_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM
7284 NAD_1983_2011_InGCS_Daviess-Greene_(ftUS) PROJCS["NAD_1983_2011_InGCS_Daviess-Greene_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DAT
7285 NAD_1983_2011_InGCS_Dearborn-Ohio-Switzerland_(m) PROJCS["NAD_1983_2011_InGCS_Dearborn-Ohio-Switzerland_(m)",GEOGCS["GCS_NAD_1983_20
7286 NAD_1983_2011_InGCS_Dearborn-Ohio-Switzerland_(ftUS) PROJCS["NAD_1983_2011_InGCS_Dearborn-Ohio-Switzerland_(ftUS)",GEOGCS["GCS_NAD_1983_
7287 NAD_1983_2011_InGCS_Decatur-Rush_(m) PROJCS["NAD_1983_2011_InGCS_Decatur-Rush_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["
7288 NAD_1983_2011_InGCS_Decatur-Rush_(ftUS) PROJCS["NAD_1983_2011_InGCS_Decatur-Rush_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM
7289 NAD_1983_2011_InGCS_DeKalb_(m) PROJCS["NAD_1983_2011_InGCS_DeKalb_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7290 NAD_1983_2011_InGCS_DeKalb_(ftUS) PROJCS["NAD_1983_2011_InGCS_DeKalb_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7291 NAD_1983_2011_InGCS_Dubois-Martin_(m) PROJCS["NAD_1983_2011_InGCS_Dubois-Martin_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["
7292 NAD_1983_2011_InGCS_Dubois-Martin_(ftUS) PROJCS["NAD_1983_2011_InGCS_Dubois-Martin_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM
7293 NAD_1983_2011_InGCS_Elkhart-Kosciusko-Wabash_(m) PROJCS["NAD_1983_2011_InGCS_Elkhart-Kosciusko-Wabash_(m)",GEOGCS["GCS_NAD_1983_20
7294 NAD_1983_2011_InGCS_Elkhart-Kosciusko-Wabash_(ftUS) PROJCS["NAD_1983_2011_InGCS_Elkhart-Kosciusko-Wabash_(ftUS)",GEOGCS["GCS_NAD_1983_
7295 NAD_1983_2011_InGCS_Fayette-Franklin-Union_(m) PROJCS["NAD_1983_2011_InGCS_Fayette-Franklin-Union_(m)",GEOGCS["GCS_NAD_1983_2011",
7296 NAD_1983_2011_InGCS_Fayette-Franklin-Union_(ftUS) PROJCS["NAD_1983_2011_InGCS_Fayette-Franklin-Union_(ftUS)",GEOGCS["GCS_NAD_1983_201
7297 NAD_1983_2011_InGCS_Fountain-Warren_(m) PROJCS["NAD_1983_2011_InGCS_Fountain-Warren_(m)",GEOGCS["GCS_NAD_1983_2011",DATU
7298 NAD_1983_2011_InGCS_Fountain-Warren_(ftUS) PROJCS["NAD_1983_2011_InGCS_Fountain-Warren_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DAT
7299 NAD_1983_2011_InGCS_Fulton-Marshall-St_Joseph_(m) PROJCS["NAD_1983_2011_InGCS_Fulton-Marshall-St_Joseph_(m)",GEOGCS["GCS_NAD_1983_20
7300 NAD_1983_2011_InGCS_Fulton-Marshall-St_Joseph_(ftUS) PROJCS["NAD_1983_2011_InGCS_Fulton-Marshall-St_Joseph_(ftUS)",GEOGCS["GCS_NAD_1983_
7301 NAD_1983_2011_InGCS_Gibson_(m) PROJCS["NAD_1983_2011_InGCS_Gibson_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD

7302 NAD_1983_2011_InGCS_Gibson_(ftUS) PROJCS["NAD_1983_2011_InGCS_Gibson_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N

7303 NAD_1983_2011_InGCS_Grant_(m) PROJCS["NAD_1983_2011_InGCS_Grant_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_
7304 NAD_1983_2011_InGCS_Grant_(ftUS) PROJCS["NAD_1983_2011_InGCS_Grant_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7305 NAD_1983_2011_InGCS_Hamilton-Tipton_(m) PROJCS["NAD_1983_2011_InGCS_Hamilton-Tipton_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM
7306 NAD_1983_2011_InGCS_Hamilton-Tipton_(ftUS) PROJCS["NAD_1983_2011_InGCS_Hamilton-Tipton_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATU
7307 NAD_1983_2011_InGCS_Hancock-Madison_(m) PROJCS["NAD_1983_2011_InGCS_Hancock-Madison_(m)",GEOGCS["GCS_NAD_1983_2011",DATU
7308 NAD_1983_2011_InGCS_Hancock-Madison_(ftUS) PROJCS["NAD_1983_2011_InGCS_Hancock-Madison_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DA
7309 NAD_1983_2011_InGCS_Harrison-Washington_(m) PROJCS["NAD_1983_2011_InGCS_Harrison-Washington_(m)",GEOGCS["GCS_NAD_1983_2011",DA
7310 NAD_1983_2011_InGCS_Harrison-Washington_(ftUS) PROJCS["NAD_1983_2011_InGCS_Harrison-Washington_(ftUS)",GEOGCS["GCS_NAD_1983_2011"
7311 NAD_1983_2011_InGCS_Henry_(m) PROJCS["NAD_1983_2011_InGCS_Henry_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7312 NAD_1983_2011_InGCS_Henry_(ftUS) PROJCS["NAD_1983_2011_InGCS_Henry_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7313 NAD_1983_2011_InGCS_Howard-Miami_(m) PROJCS["NAD_1983_2011_InGCS_Howard-Miami_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM[
7314 NAD_1983_2011_InGCS_Howard-Miami_(ftUS) PROJCS["NAD_1983_2011_InGCS_Howard-Miami_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATU
7315 NAD_1983_2011_InGCS_Huntington-Whitley_(m) PROJCS["NAD_1983_2011_InGCS_Huntington-Whitley_(m)",GEOGCS["GCS_NAD_1983_2011",DAT
7316 NAD_1983_2011_InGCS_Huntington-Whitley_(ftUS) PROJCS["NAD_1983_2011_InGCS_Huntington-Whitley_(ftUS)",GEOGCS["GCS_NAD_1983_2011",D
7317 NAD_1983_2011_InGCS_Jackson_(m) PROJCS["NAD_1983_2011_InGCS_Jackson_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7318 NAD_1983_2011_InGCS_Jackson_(ftUS) PROJCS["NAD_1983_2011_InGCS_Jackson_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
7319 NAD_1983_2011_InGCS_Jasper-Porter_(m) PROJCS["NAD_1983_2011_InGCS_Jasper-Porter_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["
7320 NAD_1983_2011_InGCS_Jasper-Porter_(ftUS) PROJCS["NAD_1983_2011_InGCS_Jasper-Porter_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM
7321 NAD_1983_2011_InGCS_Jay_(m) PROJCS["NAD_1983_2011_InGCS_Jay_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1
7322 NAD_1983_2011_InGCS_Jay_(ftUS) PROJCS["NAD_1983_2011_InGCS_Jay_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7323 NAD_1983_2011_InGCS_Jefferson_(m) PROJCS["NAD_1983_2011_InGCS_Jefferson_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7324 NAD_1983_2011_InGCS_Jefferson_(ftUS) PROJCS["NAD_1983_2011_InGCS_Jefferson_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
7325 NAD_1983_2011_InGCS_Jennings_(m) PROJCS["NAD_1983_2011_InGCS_Jennings_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7326 NAD_1983_2011_InGCS_Jennings_(ftUS) PROJCS["NAD_1983_2011_InGCS_Jennings_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
7327 NAD_1983_2011_InGCS_Johnson-Marion_(m) PROJCS["NAD_1983_2011_InGCS_Johnson-Marion_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM
7328 NAD_1983_2011_InGCS_Johnson-Marion_(ftUS) PROJCS["NAD_1983_2011_InGCS_Johnson-Marion_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DAT
7329 NAD_1983_2011_InGCS_Knox_(m) PROJCS["NAD_1983_2011_InGCS_Knox_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_
7330 NAD_1983_2011_InGCS_Knox_(ftUS) PROJCS["NAD_1983_2011_InGCS_Knox_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7331 NAD_1983_2011_InGCS_LaGrange-Noble_(m) PROJCS["NAD_1983_2011_InGCS_LaGrange-Noble_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM
7332 NAD_1983_2011_InGCS_LaGrange-Noble_(ftUS) PROJCS["NAD_1983_2011_InGCS_LaGrange-Noble_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DAT
7333 NAD_1983_2011_InGCS_Lake-Newton_(m) PROJCS["NAD_1983_2011_InGCS_Lake-Newton_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D
7334 NAD_1983_2011_InGCS_Lake-Newton_(ftUS) PROJCS["NAD_1983_2011_InGCS_Lake-Newton_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM
7335 NAD_1983_2011_InGCS_LaPorte-Pulaski-Starke_(m) PROJCS["NAD_1983_2011_InGCS_LaPorte-Pulaski-Starke_(m)",GEOGCS["GCS_NAD_1983_2011",
7336 NAD_1983_2011_InGCS_LaPorte-Pulaski-Starke_(ftUS) PROJCS["NAD_1983_2011_InGCS_LaPorte-Pulaski-Starke_(ftUS)",GEOGCS["GCS_NAD_1983_201
7337 NAD_1983_2011_InGCS_Monroe-Morgan_(m) PROJCS["NAD_1983_2011_InGCS_Monroe-Morgan_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM
7338 NAD_1983_2011_InGCS_Monroe-Morgan_(ftUS) PROJCS["NAD_1983_2011_InGCS_Monroe-Morgan_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DAT
7339 NAD_1983_2011_InGCS_Montgomery-Putnam_(m) PROJCS["NAD_1983_2011_InGCS_Montgomery-Putnam_(m)",GEOGCS["GCS_NAD_1983_2011",DA
7340 NAD_1983_2011_InGCS_Montgomery-Putnam_(ftUS) PROJCS["NAD_1983_2011_InGCS_Montgomery-Putnam_(ftUS)",GEOGCS["GCS_NAD_1983_2011"
7341 NAD_1983_2011_InGCS_Owen_(m) PROJCS["NAD_1983_2011_InGCS_Owen_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7342 NAD_1983_2011_InGCS_Owen_(ftUS) PROJCS["NAD_1983_2011_InGCS_Owen_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7343 NAD_1983_2011_InGCS_Parke-Vermillion_(m) PROJCS["NAD_1983_2011_InGCS_Parke-Vermillion_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM
7344 NAD_1983_2011_InGCS_Parke-Vermillion_(ftUS) PROJCS["NAD_1983_2011_InGCS_Parke-Vermillion_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DAT
7345 NAD_1983_2011_InGCS_Perry_(m) PROJCS["NAD_1983_2011_InGCS_Perry_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_
7346 NAD_1983_2011_InGCS_Perry_(ftUS) PROJCS["NAD_1983_2011_InGCS_Perry_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7347 NAD_1983_2011_InGCS_Pike-Warrick_(m) PROJCS["NAD_1983_2011_InGCS_Pike-Warrick_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D
7348 NAD_1983_2011_InGCS_Pike-Warrick_(ftUS) PROJCS["NAD_1983_2011_InGCS_Pike-Warrick_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM
7349 NAD_1983_2011_InGCS_Posey_(m) PROJCS["NAD_1983_2011_InGCS_Posey_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7350 NAD_1983_2011_InGCS_Posey_(ftUS) PROJCS["NAD_1983_2011_InGCS_Posey_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7351 NAD_1983_2011_InGCS_Randolph-Wayne_(m) PROJCS["NAD_1983_2011_InGCS_Randolph-Wayne_(m)",GEOGCS["GCS_NAD_1983_2011",DATU
7352 NAD_1983_2011_InGCS_Randolph-Wayne_(ftUS) PROJCS["NAD_1983_2011_InGCS_Randolph-Wayne_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DA
7353 NAD_1983_2011_InGCS_Ripley_(m) PROJCS["NAD_1983_2011_InGCS_Ripley_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7354 NAD_1983_2011_InGCS_Ripley_(ftUS) PROJCS["NAD_1983_2011_InGCS_Ripley_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7355 NAD_1983_2011_InGCS_Shelby_(m) PROJCS["NAD_1983_2011_InGCS_Shelby_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD

7356 NAD_1983_2011_InGCS_Shelby_(ftUS) PROJCS["NAD_1983_2011_InGCS_Shelby_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N

7357 NAD_1983_2011_InGCS_Spencer_(m) PROJCS["NAD_1983_2011_InGCS_Spencer_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7358 NAD_1983_2011_InGCS_Spencer_(ftUS) PROJCS["NAD_1983_2011_InGCS_Spencer_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
7359 NAD_1983_2011_InGCS_Steuben_(m) PROJCS["NAD_1983_2011_InGCS_Steuben_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7360 NAD_1983_2011_InGCS_Steuben_(ftUS) PROJCS["NAD_1983_2011_InGCS_Steuben_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
7361 NAD_1983_2011_InGCS_Sullivan_(m) PROJCS["NAD_1983_2011_InGCS_Sullivan_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7362 NAD_1983_2011_InGCS_Sullivan_(ftUS) PROJCS["NAD_1983_2011_InGCS_Sullivan_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
7363 NAD_1983_2011_InGCS_Tippecanoe-White_(m) PROJCS["NAD_1983_2011_InGCS_Tippecanoe-White_(m)",GEOGCS["GCS_NAD_1983_2011",DATU
7364 NAD_1983_2011_InGCS_Tippecanoe-White_(ftUS) PROJCS["NAD_1983_2011_InGCS_Tippecanoe-White_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DA
7365 NAD_1983_2011_InGCS_Vanderburgh_(m) PROJCS["NAD_1983_2011_InGCS_Vanderburgh_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D
7366 NAD_1983_2011_InGCS_Vanderburgh_(ftUS) PROJCS["NAD_1983_2011_InGCS_Vanderburgh_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM
7367 NAD_1983_2011_InGCS_Vigo_(m) PROJCS["NAD_1983_2011_InGCS_Vigo_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1
7368 NAD_1983_2011_InGCS_Vigo_(ftUS) PROJCS["NAD_1983_2011_InGCS_Vigo_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD
7369 NAD_1983_2011_InGCS_Wells_(m) PROJCS["NAD_1983_2011_InGCS_Wells_(m)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_
7370 NAD_1983_2011_InGCS_Wells_(ftUS) PROJCS["NAD_1983_2011_InGCS_Wells_(ftUS)",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NA
7374 ONGD14_UTM_Zone_39N PROJCS["ONGD14_UTM_Zone_39N",GEOGCS["ONGD14",DATUM["Oman_National_Geodetic_Datu
Related topics
Spatial references


ArcGIS Runtime supports so many projected coordinate systems now that one web page is no longer enough! So this is page two of two.
For Part 1 of the projected coordinate systems list, see Projected coodinate systemsPart 1.

known
ID
(WKID)
7528 NAD_1983_2011_WISCRS_Adams_and_Juneau_Meters PROJCS["NAD_1983_2011_WISCRS_Adams_and_Juneau_Meters",GEOGCS["GCS_NAD_1
7529 NAD_1983_2011_WISCRS_Ashland_Meters PROJCS["NAD_1983_2011_WISCRS_Ashland_Meters",GEOGCS["GCS_NAD_1983_2011",D
7530 NAD_1983_2011_WISCRS_Barron_Meters PROJCS["NAD_1983_2011_WISCRS_Barron_Meters",GEOGCS["GCS_NAD_1983_2011",DA
7531 NAD_1983_2011_WISCRS_Bayfield_Meters PROJCS["NAD_1983_2011_WISCRS_Bayfield_Meters",GEOGCS["GCS_NAD_1983_2011",D
7532 NAD_1983_2011_WISCRS_Brown_Meters PROJCS["NAD_1983_2011_WISCRS_Brown_Meters",GEOGCS["GCS_NAD_1983_2011",DA
7533 NAD_1983_2011_WISCRS_Buffalo_Meters PROJCS["NAD_1983_2011_WISCRS_Buffalo_Meters",GEOGCS["GCS_NAD_1983_2011",DA
7534 NAD_1983_2011_WISCRS_Burnett_Meters PROJCS["NAD_1983_2011_WISCRS_Burnett_Meters",GEOGCS["GCS_NAD_1983_2011",D
7535 NAD_1983_2011_WISCRS_Calumet_Fond_du_Lac_Outagamie_Winnebago_Meters PROJCS["NAD_1983_2011_WISCRS_Calumet_Fond_du_Lac_Outagamie_Winnebago_Mete
7536 NAD_1983_2011_WISCRS_Chippewa_Meters PROJCS["NAD_1983_2011_WISCRS_Chippewa_Meters",GEOGCS["GCS_NAD_1983_2011"
7537 NAD_1983_2011_WISCRS_Clark_Meters PROJCS["NAD_1983_2011_WISCRS_Clark_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7538 NAD_1983_2011_WISCRS_Columbia_Meters PROJCS["NAD_1983_2011_WISCRS_Columbia_Meters",GEOGCS["GCS_NAD_1983_2011"
7539 NAD_1983_2011_WISCRS_Crawford_Meters PROJCS["NAD_1983_2011_WISCRS_Crawford_Meters",GEOGCS["GCS_NAD_1983_2011",
7540 NAD_1983_2011_WISCRS_Dane_Meters PROJCS["NAD_1983_2011_WISCRS_Dane_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7541 NAD_1983_2011_WISCRS_Dodge_and_Jefferson_Meters PROJCS["NAD_1983_2011_WISCRS_Dodge_and_Jefferson_Meters",GEOGCS["GCS_NAD_
7542 NAD_1983_2011_WISCRS_Door_Meters PROJCS["NAD_1983_2011_WISCRS_Door_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7543 NAD_1983_2011_WISCRS_Douglas_Meters PROJCS["NAD_1983_2011_WISCRS_Douglas_Meters",GEOGCS["GCS_NAD_1983_2011",D
7544 NAD_1983_2011_WISCRS_Dunn_Meters PROJCS["NAD_1983_2011_WISCRS_Dunn_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7545 NAD_1983_2011_WISCRS_EauClaire_Meters PROJCS["NAD_1983_2011_WISCRS_EauClaire_Meters",GEOGCS["GCS_NAD_1983_2011"
7546 NAD_1983_2011_WISCRS_Florence_Meters PROJCS["NAD_1983_2011_WISCRS_Florence_Meters",GEOGCS["GCS_NAD_1983_2011",
7547 NAD_1983_2011_WISCRS_Forest_Meters PROJCS["NAD_1983_2011_WISCRS_Forest_Meters",GEOGCS["GCS_NAD_1983_2011",DA
7548 NAD_1983_2011_WISCRS_Grant_Meters PROJCS["NAD_1983_2011_WISCRS_Grant_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7549 NAD_1983_2011_WISCRS_Green_and_Lafayette_Meters PROJCS["NAD_1983_2011_WISCRS_Green_and_Lafayette_Meters",GEOGCS["GCS_NAD_
7550 NAD_1983_2011_WISCRS_Green_Lake_and_Marquette_Meters PROJCS["NAD_1983_2011_WISCRS_Green_Lake_and_Marquette_Meters",GEOGCS["GCS
7551 NAD_1983_2011_WISCRS_Iowa_Meters PROJCS["NAD_1983_2011_WISCRS_Iowa_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7552 NAD_1983_2011_WISCRS_Iron_Meters PROJCS["NAD_1983_2011_WISCRS_Iron_Meters",GEOGCS["GCS_NAD_1983_2011",DATU
7553 NAD_1983_2011_WISCRS_Jackson_Meters PROJCS["NAD_1983_2011_WISCRS_Jackson_Meters",GEOGCS["GCS_NAD_1983_2011",D
7554 NAD_1983_2011_WISCRS_Kenosha_Milwaukee_Ozaukee_Racine_Meters PROJCS["NAD_1983_2011_WISCRS_Kenosha_Milwaukee_Ozaukee_Racine_Meters",GEOG
7555 NAD_1983_2011_WISCRS_Kewaunee_Manitowoc_Sheboygan_Meters PROJCS["NAD_1983_2011_WISCRS_Kewaunee_Manitowoc_Sheboygan_Meters",GEOGCS
7556 NAD_1983_2011_WISCRS_La_Crosse_Meters PROJCS["NAD_1983_2011_WISCRS_La_Crosse_Meters",GEOGCS["GCS_NAD_1983_2011
7557 NAD_1983_2011_WISCRS_Langlade_Meters PROJCS["NAD_1983_2011_WISCRS_Langlade_Meters",GEOGCS["GCS_NAD_1983_2011",
7558 NAD_1983_2011_WISCRS_Lincoln_Meters PROJCS["NAD_1983_2011_WISCRS_Lincoln_Meters",GEOGCS["GCS_NAD_1983_2011",D
7559 NAD_1983_2011_WISCRS_Marathon_Meters PROJCS["NAD_1983_2011_WISCRS_Marathon_Meters",GEOGCS["GCS_NAD_1983_2011"
7560 NAD_1983_2011_WISCRS_Marinette_Meters PROJCS["NAD_1983_2011_WISCRS_Marinette_Meters",GEOGCS["GCS_NAD_1983_2011"
7561 NAD_1983_2011_WISCRS_Menominee_Meters PROJCS["NAD_1983_2011_WISCRS_Menominee_Meters",GEOGCS["GCS_NAD_1983_201
7562 NAD_1983_2011_WISCRS_Monroe_Meters PROJCS["NAD_1983_2011_WISCRS_Monroe_Meters",GEOGCS["GCS_NAD_1983_2011",D
7563 NAD_1983_2011_WISCRS_Oconto_Meters PROJCS["NAD_1983_2011_WISCRS_Oconto_Meters",GEOGCS["GCS_NAD_1983_2011",D
7564 NAD_1983_2011_WISCRS_Oneida_Meters PROJCS["NAD_1983_2011_WISCRS_Oneida_Meters",GEOGCS["GCS_NAD_1983_2011",D
7565 NAD_1983_2011_WISCRS_Pepin_and_Pierce_Meters PROJCS["NAD_1983_2011_WISCRS_Pepin_and_Pierce_Meters",GEOGCS["GCS_NAD_198
7566 NAD_1983_2011_WISCRS_Polk_Meters PROJCS["NAD_1983_2011_WISCRS_Polk_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7567 NAD_1983_2011_WISCRS_Portage_Meters PROJCS["NAD_1983_2011_WISCRS_Portage_Meters",GEOGCS["GCS_NAD_1983_2011",D
7568 NAD_1983_2011_WISCRS_Price_Meters PROJCS["NAD_1983_2011_WISCRS_Price_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7569 NAD_1983_2011_WISCRS_Richland_Meters PROJCS["NAD_1983_2011_WISCRS_Richland_Meters",GEOGCS["GCS_NAD_1983_2011",
7570 NAD_1983_2011_WISCRS_Rock_Meters PROJCS["NAD_1983_2011_WISCRS_Rock_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7571 NAD_1983_2011_WISCRS_Rusk_Meters PROJCS["NAD_1983_2011_WISCRS_Rusk_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7572 NAD_1983_2011_WISCRS_Sauk_Meters PROJCS["NAD_1983_2011_WISCRS_Sauk_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7573 NAD_1983_2011_WISCRS_Sawyer_Meters PROJCS["NAD_1983_2011_WISCRS_Sawyer_Meters",GEOGCS["GCS_NAD_1983_2011",D
7574 NAD_1983_2011_WISCRS_Shawano_Meters PROJCS["NAD_1983_2011_WISCRS_Shawano_Meters",GEOGCS["GCS_NAD_1983_2011"

7575 NAD_1983_2011_WISCRS_St_Croix_Meters PROJCS["NAD_1983_2011_WISCRS_St_Croix_Meters",GEOGCS["GCS_NAD_1983_2011",D

7576 NAD_1983_2011_WISCRS_Taylor_Meters PROJCS["NAD_1983_2011_WISCRS_Taylor_Meters",GEOGCS["GCS_NAD_1983_2011",DA
7577 NAD_1983_2011_WISCRS_Trempealeau_Meters PROJCS["NAD_1983_2011_WISCRS_Trempealeau_Meters",GEOGCS["GCS_NAD_1983_20
7578 NAD_1983_2011_WISCRS_Vernon_Meters PROJCS["NAD_1983_2011_WISCRS_Vernon_Meters",GEOGCS["GCS_NAD_1983_2011",D
7579 NAD_1983_2011_WISCRS_Vilas_Meters PROJCS["NAD_1983_2011_WISCRS_Vilas_Meters",GEOGCS["GCS_NAD_1983_2011",DAT
7580 NAD_1983_2011_WISCRS_Walworth_Meters PROJCS["NAD_1983_2011_WISCRS_Walworth_Meters",GEOGCS["GCS_NAD_1983_2011",
7581 NAD_1983_2011_WISCRS_Washburn_Meters PROJCS["NAD_1983_2011_WISCRS_Washburn_Meters",GEOGCS["GCS_NAD_1983_2011
7582 NAD_1983_2011_WISCRS_Washington_Meters PROJCS["NAD_1983_2011_WISCRS_Washington_Meters",GEOGCS["GCS_NAD_1983_201
7583 NAD_1983_2011_WISCRS_Waukesha_Meters PROJCS["NAD_1983_2011_WISCRS_Waukesha_Meters",GEOGCS["GCS_NAD_1983_2011
7584 NAD_1983_2011_WISCRS_Waupaca_Meters PROJCS["NAD_1983_2011_WISCRS_Waupaca_Meters",GEOGCS["GCS_NAD_1983_2011"
7585 NAD_1983_2011_WISCRS_Waushara_Meters PROJCS["NAD_1983_2011_WISCRS_Waushara_Meters",GEOGCS["GCS_NAD_1983_2011
7586 NAD_1983_2011_WISCRS_Wood_Meters PROJCS["NAD_1983_2011_WISCRS_Wood_Meters",GEOGCS["GCS_NAD_1983_2011",DA
7587 NAD_1983_2011_WISCRS_Adams_and_Juneau_Feet PROJCS["NAD_1983_2011_WISCRS_Adams_and_Juneau_Feet",GEOGCS["GCS_NAD_198
7588 NAD_1983_2011_WISCRS_Ashland_Feet PROJCS["NAD_1983_2011_WISCRS_Ashland_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7589 NAD_1983_2011_WISCRS_Barron_Feet PROJCS["NAD_1983_2011_WISCRS_Barron_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7590 NAD_1983_2011_WISCRS_Bayfield_Feet PROJCS["NAD_1983_2011_WISCRS_Bayfield_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7591 NAD_1983_2011_WISCRS_Brown_Feet PROJCS["NAD_1983_2011_WISCRS_Brown_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7592 NAD_1983_2011_WISCRS_Buffalo_Feet PROJCS["NAD_1983_2011_WISCRS_Buffalo_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7593 NAD_1983_2011_WISCRS_Burnett_Feet PROJCS["NAD_1983_2011_WISCRS_Burnett_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7594 NAD_1983_2011_WISCRS_Calumet_Fond_du_Lac_Outagamie_Winnebago_Feet PROJCS["NAD_1983_2011_WISCRS_Calumet_Fond_du_Lac_Outagamie_Winnebago_Feet"
7595 NAD_1983_2011_WISCRS_Chippewa_Feet PROJCS["NAD_1983_2011_WISCRS_Chippewa_Feet",GEOGCS["GCS_NAD_1983_2011",D
7596 NAD_1983_2011_WISCRS_Clark_Feet PROJCS["NAD_1983_2011_WISCRS_Clark_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7597 NAD_1983_2011_WISCRS_Columbia_Feet PROJCS["NAD_1983_2011_WISCRS_Columbia_Feet",GEOGCS["GCS_NAD_1983_2011",D
7598 NAD_1983_2011_WISCRS_Crawford_Feet PROJCS["NAD_1983_2011_WISCRS_Crawford_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7599 NAD_1983_2011_WISCRS_Dane_Feet PROJCS["NAD_1983_2011_WISCRS_Dane_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7600 NAD_1983_2011_WISCRS_Dodge_and_Jefferson_Feet PROJCS["NAD_1983_2011_WISCRS_Dodge_and_Jefferson_Feet",GEOGCS["GCS_NAD_19
7601 NAD_1983_2011_WISCRS_Door_Feet PROJCS["NAD_1983_2011_WISCRS_Door_Feet",GEOGCS["GCS_NAD_1983_2011",DATUM
7602 NAD_1983_2011_WISCRS_Douglas_Feet PROJCS["NAD_1983_2011_WISCRS_Douglas_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7603 NAD_1983_2011_WISCRS_Dunn_Feet PROJCS["NAD_1983_2011_WISCRS_Dunn_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7604 NAD_1983_2011_WISCRS_Eau_Claire_Feet PROJCS["NAD_1983_2011_WISCRS_Eau_Claire_Feet",GEOGCS["GCS_NAD_1983_2011",
7605 NAD_1983_2011_WISCRS_Florence_Feet PROJCS["NAD_1983_2011_WISCRS_Florence_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7606 NAD_1983_2011_WISCRS_Forest_Feet PROJCS["NAD_1983_2011_WISCRS_Forest_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7607 NAD_1983_2011_WISCRS_Grant_Feet PROJCS["NAD_1983_2011_WISCRS_Grant_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7608 NAD_1983_2011_WISCRS_Green_and_Lafayette_Feet PROJCS["NAD_1983_2011_WISCRS_Green_and_Lafayette_Feet",GEOGCS["GCS_NAD_19
7609 NAD_1983_2011_WISCRS_Green_Lake_and_Marquette_Feet PROJCS["NAD_1983_2011_WISCRS_Green_Lake_and_Marquette_Feet",GEOGCS["GCS_N
7610 NAD_1983_2011_WISCRS_Iowa_Feet PROJCS["NAD_1983_2011_WISCRS_Iowa_Feet",GEOGCS["GCS_NAD_1983_2011",DATUM
7611 NAD_1983_2011_WISCRS_Iron_Feet PROJCS["NAD_1983_2011_WISCRS_Iron_Feet",GEOGCS["GCS_NAD_1983_2011",DATUM
7612 NAD_1983_2011_WISCRS_Jackson_Feet PROJCS["NAD_1983_2011_WISCRS_Jackson_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7613 NAD_1983_2011_WISCRS_Kenosha_Milwaukee_Ozaukee_Racine_Feet PROJCS["NAD_1983_2011_WISCRS_Kenosha_Milwaukee_Ozaukee_Racine_Feet",GEOGC
7614 NAD_1983_2011_WISCRS_Kewaunee_Manitowoc_Sheboygan_Feet PROJCS["NAD_1983_2011_WISCRS_Kewaunee_Manitowoc_Sheboygan_Feet",GEOGCS["G
7615 NAD_1983_2011_WISCRS_La_Crosse_Feet PROJCS["NAD_1983_2011_WISCRS_La_Crosse_Feet",GEOGCS["GCS_NAD_1983_2011",D
7616 NAD_1983_2011_WISCRS_Langlade_Feet PROJCS["NAD_1983_2011_WISCRS_Langlade_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7617 NAD_1983_2011_WISCRS_Lincoln_Feet PROJCS["NAD_1983_2011_WISCRS_Lincoln_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7618 NAD_1983_2011_WISCRS_Marathon_Feet PROJCS["NAD_1983_2011_WISCRS_Marathon_Feet",GEOGCS["GCS_NAD_1983_2011",D
7619 NAD_1983_2011_WISCRS_Marinette_Feet PROJCS["NAD_1983_2011_WISCRS_Marinette_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7620 NAD_1983_2011_WISCRS_Menominee_Feet PROJCS["NAD_1983_2011_WISCRS_Menominee_Feet",GEOGCS["GCS_NAD_1983_2011"
7621 NAD_1983_2011_WISCRS_Monroe_Feet PROJCS["NAD_1983_2011_WISCRS_Monroe_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7622 NAD_1983_2011_WISCRS_Oconto_Feet PROJCS["NAD_1983_2011_WISCRS_Oconto_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7623 NAD_1983_2011_WISCRS_Oneida_Feet PROJCS["NAD_1983_2011_WISCRS_Oneida_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7624 NAD_1983_2011_WISCRS_Pepin_and_Pierce_Feet PROJCS["NAD_1983_2011_WISCRS_Pepin_and_Pierce_Feet",GEOGCS["GCS_NAD_1983_
7625 NAD_1983_2011_WISCRS_Polk_Feet PROJCS["NAD_1983_2011_WISCRS_Polk_Feet",GEOGCS["GCS_NAD_1983_2011",DATUM
7626 NAD_1983_2011_WISCRS_Portage_Feet PROJCS["NAD_1983_2011_WISCRS_Portage_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7627 NAD_1983_2011_WISCRS_Price_Feet PROJCS["NAD_1983_2011_WISCRS_Price_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7628 NAD_1983_2011_WISCRS_Richland_Feet PROJCS["NAD_1983_2011_WISCRS_Richland_Feet",GEOGCS["GCS_NAD_1983_2011",DA

7629 NAD_1983_2011_WISCRS_Rock_Feet PROJCS["NAD_1983_2011_WISCRS_Rock_Feet",GEOGCS["GCS_NAD_1983_2011",DATU

7630 NAD_1983_2011_WISCRS_Rusk_Feet PROJCS["NAD_1983_2011_WISCRS_Rusk_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7631 NAD_1983_2011_WISCRS_Sauk_Feet PROJCS["NAD_1983_2011_WISCRS_Sauk_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7632 NAD_1983_2011_WISCRS_Sawyer_Feet PROJCS["NAD_1983_2011_WISCRS_Sawyer_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7633 NAD_1983_2011_WISCRS_Shawano_Feet PROJCS["NAD_1983_2011_WISCRS_Shawano_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7634 NAD_1983_2011_WISCRS_St_Croix_Feet PROJCS["NAD_1983_2011_WISCRS_St_Croix_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7635 NAD_1983_2011_WISCRS_Taylor_Feet PROJCS["NAD_1983_2011_WISCRS_Taylor_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7636 NAD_1983_2011_WISCRS_Trempealeau_Feet PROJCS["NAD_1983_2011_WISCRS_Trempealeau_Feet",GEOGCS["GCS_NAD_1983_2011
7637 NAD_1983_2011_WISCRS_Vernon_Feet PROJCS["NAD_1983_2011_WISCRS_Vernon_Feet",GEOGCS["GCS_NAD_1983_2011",DAT
7638 NAD_1983_2011_WISCRS_Vilas_Feet PROJCS["NAD_1983_2011_WISCRS_Vilas_Feet",GEOGCS["GCS_NAD_1983_2011",DATUM
7639 NAD_1983_2011_WISCRS_Walworth_Feet PROJCS["NAD_1983_2011_WISCRS_Walworth_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7640 NAD_1983_2011_WISCRS_Washburn_Feet PROJCS["NAD_1983_2011_WISCRS_Washburn_Feet",GEOGCS["GCS_NAD_1983_2011",D
7641 NAD_1983_2011_WISCRS_Washington_Feet PROJCS["NAD_1983_2011_WISCRS_Washington_Feet",GEOGCS["GCS_NAD_1983_2011"
7642 NAD_1983_2011_WISCRS_Waukesha_Feet PROJCS["NAD_1983_2011_WISCRS_Waukesha_Feet",GEOGCS["GCS_NAD_1983_2011",D
7643 NAD_1983_2011_WISCRS_Waupaca_Feet PROJCS["NAD_1983_2011_WISCRS_Waupaca_Feet",GEOGCS["GCS_NAD_1983_2011",DA
7644 NAD_1983_2011_WISCRS_Waushara_Feet PROJCS["NAD_1983_2011_WISCRS_Waushara_Feet",GEOGCS["GCS_NAD_1983_2011",D
7645 NAD_1983_2011_WISCRS_Wood_Feet PROJCS["NAD_1983_2011_WISCRS_Wood_Feet",GEOGCS["GCS_NAD_1983_2011",DATU
7845 GDA2020_GA_LCC PROJCS["GDA2020_GA_LCC",GEOGCS["GDA2020",DATUM["GDA2020",SPHEROID["GRS_
7846 GDA2020_MGA_Zone_46 PROJCS["GDA2020_MGA_Zone_46",GEOGCS["GDA2020",DATUM["GDA2020",SPHEROID[
20002 Pulkovo_1995_GK_Zone_2 PROJCS["Pulkovo_1995_GK_Zone_2",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulkovo_
20010 Pulkovo_1995_GK_Zone_10 PROJCS["Pulkovo_1995_GK_Zone_10",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulkovo


20062 Pulkovo_1995_GK_Zone_2N PROJCS["Pulkovo_1995_GK_Zone_2N",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulkovo
20070 Pulkovo_1995_GK_Zone_10N PROJCS["Pulkovo_1995_GK_Zone_10N",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulko
20071 Pulkovo_1995_GK_Zone_11N PROJCS["Pulkovo_1995_GK_Zone_11N",GEOGCS["GCS_Pulkovo_1995",DATUM["D_Pulkov
20135 Adindan_UTM_Zone_35N PROJCS["Adindan_UTM_Zone_35N",GEOGCS["GCS_Adindan",DATUM["D_Adindan",SPHER
20248 AGD_1966_AMG_Zone_48 PROJCS["AGD_1966_AMG_Zone_48",GEOGCS["GCS_Australian_1966",DATUM["D_Austra


20436 Ain_el_Abd_UTM_Zone_36N PROJCS["Ain_el_Abd_UTM_Zone_36N",GEOGCS["GCS_Ain_el_Abd_1970",DATUM["D_Ain
20499 Bahrain_State_Grid PROJCS["Bahrain_State_Grid",GEOGCS["GCS_Ain_el_Abd_1970",DATUM["D_Ain_el_Abd_1
20538 Afgooye_UTM_Zone_38N PROJCS["Afgooye_UTM_Zone_38N",GEOGCS["GCS_Afgooye",DATUM["D_Afgooye",SPHER
20539 Afgooye_UTM_Zone_39N PROJCS["Afgooye_UTM_Zone_39N",GEOGCS["GCS_Afgooye",DATUM["D_Afgooye",SPHER
20790 Portuguese_National_Grid PROJCS["Portuguese_National_Grid",GEOGCS["GCS_Lisbon_Lisbon",DATUM["D_Lisbon",S
20791 Lisbon_Lisbon_Portuguese_Grid PROJCS["Lisbon_Lisbon_Portuguese_Grid",GEOGCS["GCS_Lisbon_Lisbon",DATUM["D_Lisb
20822 Aratu_UTM_Zone_22S PROJCS["Aratu_UTM_Zone_22S",GEOGCS["GCS_Aratu",DATUM["D_Aratu",SPHEROID["Int
20934 Arc_1950_UTM_Zone_34S PROJCS["Arc_1950_UTM_Zone_34S",GEOGCS["GCS_Arc_1950",DATUM["D_Arc_1950",SP
21095 Arc_1960_UTM_Zone_35N PROJCS["Arc_1960_UTM_Zone_35N",GEOGCS["GCS_Arc_1960",DATUM["D_Arc_1960",SP
21148 Batavia_UTM_Zone_48S PROJCS["Batavia_UTM_Zone_48S",GEOGCS["GCS_Batavia",DATUM["D_Batavia",SPHERO
21291 Barbados_1938_British_West_Indies_Grid PROJCS["Barbados_1938_British_West_Indies_Grid",GEOGCS["GCS_Barbados_1938",DAT
21292 Barbados_1938_Barbados_Grid PROJCS["Barbados_1938_Barbados_Grid",GEOGCS["GCS_Barbados_1938",DATUM["D_Ba
21413 Beijing_1954_GK_Zone_13 PROJCS["Beijing_1954_GK_Zone_13",GEOGCS["GCS_Beijing_1954",DATUM["D_Beijing_19
21473 Beijing_1954_GK_Zone_13N PROJCS["Beijing_1954_GK_Zone_13N",GEOGCS["GCS_Beijing_1954",DATUM["D_Beijing_1


21500 Belge_Lambert_1950 PROJCS["Belge_Lambert_1950",GEOGCS["GCS_Belge_1950_Brussels",DATUM["D_Belge_
21780 Bern_1898_Bern_LV03C PROJCS["Bern_1898_Bern_LV03C",GEOGCS["GCS_Bern_1898_Bern",DATUM["D_Bern_18
21781 CH1903_LV03 PROJCS["CH1903_LV03",GEOGCS["GCS_CH1903",DATUM["D_CH1903",SPHEROID["Bess
21782 CH1903_LV03C-G PROJCS["CH1903_LV03C-G",GEOGCS["GCS_CH1903",DATUM["D_CH1903",SPHEROID["B
21817 Bogota_UTM_Zone_17N PROJCS["Bogota_UTM_Zone_17N",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROI
21818 Bogota_UTM_Zone_18N PROJCS["Bogota_UTM_Zone_18N",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROI
21891 Colombia_West_Zone PROJCS["Colombia_West_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID["
21892 Colombia_Bogota_Zone PROJCS["Colombia_Bogota_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID
21893 Colombia_East_Central_Zone PROJCS["Colombia_East_Central_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPH
21894 Colombia_East_Zone PROJCS["Colombia_East_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID["
21896 Colombia_West_Zone PROJCS["Colombia_West_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID["
21897 Colombia_Bogota_Zone PROJCS["Colombia_Bogota_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID
21898 Colombia_East_Central_Zone PROJCS["Colombia_East_Central_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPH
21899 Colombia_East_Zone PROJCS["Colombia_East_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID["
22032 Camacupa_UTM_Zone_32S PROJCS["Camacupa_UTM_Zone_32S",GEOGCS["GCS_Camacupa",DATUM["D_Camacupa
22033 Camacupa_UTM_Zone_33S PROJCS["Camacupa_UTM_Zone_33S",GEOGCS["GCS_Camacupa",DATUM["D_Camacupa
22091 Camacupa_TM_11_30_SE PROJCS["Camacupa_TM_11_30_SE",GEOGCS["GCS_Camacupa",DATUM["D_Camacupa",S
22092 Camacupa_TM_12_SE PROJCS["Camacupa_TM_12_SE",GEOGCS["GCS_Camacupa",DATUM["D_Camacupa",SPH
22171 POSGAR_1998_Argentina_Zone_1 PROJCS["POSGAR_1998_Argentina_Zone_1",GEOGCS["GCS_POSGAR_1998",DATUM["D_
22191 Argentina_Zone_1 PROJCS["Argentina_Zone_1",GEOGCS["GCS_Campo_Inchauspe",DATUM["D_Campo_Incha
22234 Cape_UTM_Zone_34S PROJCS["Cape_UTM_Zone_34S",GEOGCS["GCS_Cape",DATUM["D_Cape",SPHEROID["Cl
22332 Carthage_UTM_Zone_32N PROJCS["Carthage_UTM_Zone_32N",GEOGCS["GCS_Carthage",DATUM["D_Carthage",SPH
22391 Nord_Tunisie PROJCS["Nord_Tunisie",GEOGCS["GCS_Carthage",DATUM["D_Carthage",SPHEROID["Clar
22392 Sud_Tunisie PROJCS["Sud_Tunisie",GEOGCS["GCS_Carthage",DATUM["D_Carthage",SPHEROID["Clark
22521 Corrego_Alegre_UTM_Zone_21S PROJCS["Corrego_Alegre_UTM_Zone_21S",GEOGCS["GCS_Corrego_Alegre",DATUM["D_C


22700 Deir_ez_Zor_Levant_Zone PROJCS["Deir_ez_Zor_Levant_Zone",GEOGCS["GCS_Deir_ez_Zor",DATUM["D_Deir_ez_Zo
22770 Deir_ez_Zor_Syria_Lambert PROJCS["Deir_ez_Zor_Syria_Lambert",GEOGCS["GCS_Deir_ez_Zor",DATUM["D_Deir_ez_Z
22780 Deir_ez_Zor_Levant_Stereographic PROJCS["Deir_ez_Zor_Levant_Stereographic",GEOGCS["GCS_Deir_ez_Zor",DATUM["D_De
22832 Douala_UTM_Zone_32N PROJCS["Douala_UTM_Zone_32N",GEOGCS["GCS_Douala",DATUM["D_Douala",SPHEROI
22991 Egypt_Blue_Belt PROJCS["Egypt_Blue_Belt",GEOGCS["GCS_Egypt_1907",DATUM["D_Egypt_1907",SPHERO
22992 Egypt_Red_Belt PROJCS["Egypt_Red_Belt",GEOGCS["GCS_Egypt_1907",DATUM["D_Egypt_1907",SPHERO
22993 Egypt_Purple_Belt PROJCS["Egypt_Purple_Belt",GEOGCS["GCS_Egypt_1907",DATUM["D_Egypt_1907",SPHER
22994 Egypt_Extended_Purple_Belt PROJCS["Egypt_Extended_Purple_Belt",GEOGCS["GCS_Egypt_1907",DATUM["D_Egypt_19
23028 ED_1950_UTM_Zone_28N PROJCS["ED_1950_UTM_Zone_28N",GEOGCS["GCS_European_1950",DATUM["D_Europe
23090 ED_1950_TM_0_N PROJCS["ED_1950_TM_0_N",GEOGCS["GCS_European_1950",DATUM["D_European_1950
23095 ED_1950_TM_5_NE PROJCS["ED_1950_TM_5_NE",GEOGCS["GCS_European_1950",DATUM["D_European_195
23239 Fahud_UTM_Zone_39N PROJCS["Fahud_UTM_Zone_39N",GEOGCS["GCS_Fahud",DATUM["D_Fahud",SPHEROID[
23240 Fahud_UTM_Zone_40N PROJCS["Fahud_UTM_Zone_40N",GEOGCS["GCS_Fahud",DATUM["D_Fahud",SPHEROID[
23433 Garoua_UTM_Zone_33N PROJCS["Garoua_UTM_Zone_33N",GEOGCS["GCS_Garoua",DATUM["D_Garoua",SPHERO
23700 Hungarian_1972_Egyseges_Orszagos_Vetuleti PROJCS["Hungarian_1972_Egyseges_Orszagos_Vetuleti",GEOGCS["GCS_Hungarian_1972"
23830 DGN_1995_Indonesia_TM-3_Zone_46.2 PROJCS["DGN_1995_Indonesia_TM-3_Zone_46.2",GEOGCS["GCS_DGN_1995",DATUM["D
23846 Indonesian_1974_UTM_Zone_46N PROJCS["Indonesian_1974_UTM_Zone_46N",GEOGCS["GCS_Indonesian_1974",DATUM["D
23866 DGN_1995_UTM_Zone_46N PROJCS["DGN_1995_UTM_Zone_46N",GEOGCS["GCS_DGN_1995",DATUM["D_Datum_Ge


23877 DGN_1995_UTM_Zone_47S PROJCS["DGN_1995_UTM_Zone_47S",GEOGCS["GCS_DGN_1995",DATUM["D_Datum_Ge
23886 Indonesian_1974_UTM_Zone_46S PROJCS["Indonesian_1974_UTM_Zone_46S",GEOGCS["GCS_Indonesian_1974",DATUM["D
23946 Indian_1954_UTM_Zone_46N PROJCS["Indian_1954_UTM_Zone_46N",GEOGCS["GCS_Indian_1954",DATUM["D_Indian_1
24100 Jamaica_1875_Old_Grid PROJCS["Jamaica_1875_Old_Grid",GEOGCS["GCS_Jamaica_1875",DATUM["D_Jamaica_1
24200 Jamaica_Grid PROJCS["Jamaica_Grid",GEOGCS["GCS_Jamaica_1969",DATUM["D_Jamaica_1969",SPHE
24305 Kalianpur_1937_UTM_Zone_45N PROJCS["Kalianpur_1937_UTM_Zone_45N",GEOGCS["GCS_Kalianpur_1937",DATUM["D_K
24370 Kalianpur_1880_India_Zone_0 PROJCS["Kalianpur_1880_India_Zone_0",GEOGCS["GCS_Kalianpur_1880",DATUM["D_Kalia
24371 Kalianpur_1880_India_Zone_I PROJCS["Kalianpur_1880_India_Zone_I",GEOGCS["GCS_Kalianpur_1880",DATUM["D_Kalia
24372 Kalianpur_1880_India_Zone_IIa PROJCS["Kalianpur_1880_India_Zone_IIa",GEOGCS["GCS_Kalianpur_1880",DATUM["D_Ka
24373 Kalianpur_1880_India_Zone_III PROJCS["Kalianpur_1880_India_Zone_III",GEOGCS["GCS_Kalianpur_1880",DATUM["D_Kal
24374 Kalianpur_1880_India_Zone_IV PROJCS["Kalianpur_1880_India_Zone_IV",GEOGCS["GCS_Kalianpur_1880",DATUM["D_Kal
24375 Kalianpur_1937_India_Zone_IIb PROJCS["Kalianpur_1937_India_Zone_IIb",GEOGCS["GCS_Kalianpur_1937",DATUM["D_Ka
24381 Kalianpur_1975_India_Zone_III PROJCS["Kalianpur_1975_India_Zone_III",GEOGCS["GCS_Kalianpur_1975",DATUM["D_Kal
24383 Kalianpur_1975_India_Zone_IV PROJCS["Kalianpur_1975_India_Zone_IV",GEOGCS["GCS_Kalianpur_1975",DATUM["D_Kal

24500 Kertau_Singapore_Grid PROJCS["Kertau_Singapore_Grid",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID[

24547 Kertau_UTM_Zone_47N PROJCS["Kertau_UTM_Zone_47N",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID
24548 Kertau_UTM_Zone_48N PROJCS["Kertau_UTM_Zone_48N",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHEROID
24571 Kertau_RSO_Malaya_Chains PROJCS["Kertau_RSO_Malaya_Chains",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHER
24600 KOC_Lambert PROJCS["KOC_Lambert",GEOGCS["GCS_Kuwait_Oil_Company",DATUM["D_Kuwait_Oil_Co
24718 La_Canoa_UTM_Zone_18N PROJCS["La_Canoa_UTM_Zone_18N",GEOGCS["GCS_La_Canoa",DATUM["D_La_Canoa",
24817 PSAD_1956_UTM_Zone_17N PROJCS["PSAD_1956_UTM_Zone_17N",GEOGCS["GCS_Provisional_S_American_1956",D
24877 PSAD_1956_UTM_Zone_17S PROJCS["PSAD_1956_UTM_Zone_17S",GEOGCS["GCS_Provisional_S_American_1956",DA
24891 Peru_West_Zone PROJCS["Peru_West_Zone",GEOGCS["GCS_Provisional_S_American_1956",DATUM["D_Pr
24892 Peru_Central_Zone PROJCS["Peru_Central_Zone",GEOGCS["GCS_Provisional_S_American_1956",DATUM["D_
24893 Peru_East_Zone PROJCS["Peru_East_Zone",GEOGCS["GCS_Provisional_S_American_1956",DATUM["D_Pro
25000 Ghana_Metre_Grid PROJCS["Ghana_Metre_Grid",GEOGCS["GCS_Leigon",DATUM["D_Leigon",SPHEROID["Cla
25231 Lome_UTM_Zone_31N PROJCS["Lome_UTM_Zone_31N",GEOGCS["GCS_Lome",DATUM["D_Lome",SPHEROID["C
25391 Philippines_Zone_I PROJCS["Philippines_Zone_I",GEOGCS["GCS_Luzon_1911",DATUM["D_Luzon_1911",SPHE
25392 Philippines_Zone_II PROJCS["Philippines_Zone_II",GEOGCS["GCS_Luzon_1911",DATUM["D_Luzon_1911",SPHE
25393 Philippines_Zone_III PROJCS["Philippines_Zone_III",GEOGCS["GCS_Luzon_1911",DATUM["D_Luzon_1911",SPH
25394 Philippines_Zone_IV PROJCS["Philippines_Zone_IV",GEOGCS["GCS_Luzon_1911",DATUM["D_Luzon_1911",SPH
25395 Philippines_Zone_V PROJCS["Philippines_Zone_V",GEOGCS["GCS_Luzon_1911",DATUM["D_Luzon_1911",SPH
25828 ETRS_1989_UTM_Zone_28N PROJCS["ETRS_1989_UTM_Zone_28N",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1
25884 ETRS_1989_TM_Baltic_1993 PROJCS["ETRS_1989_TM_Baltic_1993",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1
25932 Malongo_1987_UTM_Zone_32S PROJCS["Malongo_1987_UTM_Zone_32S",GEOGCS["GCS_Malongo_1987",DATUM["D_Ma
26191 Nord_Maroc PROJCS["Nord_Maroc",GEOGCS["GCS_Merchich",DATUM["D_Merchich",SPHEROID["Clark
26192 Sud_Maroc PROJCS["Sud_Maroc",GEOGCS["GCS_Merchich",DATUM["D_Merchich",SPHEROID["Clarke
26193 Sahara PROJCS["Sahara",GEOGCS["GCS_Merchich",DATUM["D_Merchich",SPHEROID["Clarke_188
26194 Merchich_Sahara_Nord PROJCS["Merchich_Sahara_Nord",GEOGCS["GCS_Merchich",DATUM["D_Merchich",SPHER
26195 Merchich_Sahara_Sud PROJCS["Merchich_Sahara_Sud",GEOGCS["GCS_Merchich",DATUM["D_Merchich",SPHERO
26237 Massawa_UTM_Zone_37N PROJCS["Massawa_UTM_Zone_37N",GEOGCS["GCS_Massawa",DATUM["D_Massawa",SP
26331 Minna_UTM_Zone_31N PROJCS["Minna_UTM_Zone_31N",GEOGCS["GCS_Minna",DATUM["D_Minna",SPHEROID["
26332 Minna_UTM_Zone_32N PROJCS["Minna_UTM_Zone_32N",GEOGCS["GCS_Minna",DATUM["D_Minna",SPHEROID["
26391 Nigeria_West_Belt PROJCS["Nigeria_West_Belt",GEOGCS["GCS_Minna",DATUM["D_Minna",SPHEROID["Clark
26392 Nigeria_Mid_Belt PROJCS["Nigeria_Mid_Belt",GEOGCS["GCS_Minna",DATUM["D_Minna",SPHEROID["Clarke
26393 Nigeria_East_Belt PROJCS["Nigeria_East_Belt",GEOGCS["GCS_Minna",DATUM["D_Minna",SPHEROID["Clarke

26591 Monte_Mario_Rome_Italy_1 PROJCS["Monte_Mario_Rome_Italy_1",GEOGCS["GCS_Monte_Mario_Rome",DATUM["D_M

26592 Monte_Mario_Rome_Italy_2 PROJCS["Monte_Mario_Rome_Italy_2",GEOGCS["GCS_Monte_Mario_Rome",DATUM["D_M
26632 Mporaloko_UTM_Zone_32N PROJCS["Mporaloko_UTM_Zone_32N",GEOGCS["GCS_Mporaloko",DATUM["D_Mporaloko",
26692 Mporaloko_UTM_Zone_32S PROJCS["Mporaloko_UTM_Zone_32S",GEOGCS["GCS_Mporaloko",DATUM["D_Mporaloko",
26701 NAD_1927_UTM_Zone_1N PROJCS["NAD_1927_UTM_Zone_1N",GEOGCS["GCS_North_American_1927",DATUM["D_N
26710 NAD_1927_UTM_Zone_10N PROJCS["NAD_1927_UTM_Zone_10N",GEOGCS["GCS_North_American_1927",DATUM["D_
26729 NAD_1927_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1927_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_North_Ameri
26730 NAD_1927_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1927_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_North_Amer
26731 NAD_1927_StatePlane_Alaska_1_FIPS_5001 PROJCS["NAD_1927_StatePlane_Alaska_1_FIPS_5001",GEOGCS["GCS_North_American_1
26740 NAD_1927_StatePlane_Alaska_10_FIPS_5010 PROJCS["NAD_1927_StatePlane_Alaska_10_FIPS_5010",GEOGCS["GCS_North_American_
26741 NAD_1927_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1927_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_North_American
26742 NAD_1927_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1927_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_North_America
26743 NAD_1927_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1927_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_North_America
26744 NAD_1927_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1927_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_North_America
26745 NAD_1927_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1927_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_North_America
26746 NAD_1927_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1927_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_North_America
26747 NAD_1927_StatePlane_California_VII_FIPS_0407 PROJCS["NAD_1927_StatePlane_California_VII_FIPS_0407",GEOGCS["GCS_North_Americ
26748 NAD_1927_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1927_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_North_Americ
26749 NAD_1927_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1927_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_North_Ame
26750 NAD_1927_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1927_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_North_Americ
26751 NAD_1927_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1927_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_North_Ame
26752 NAD_1927_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1927_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_North_Ame
26753 NAD_1927_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1927_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_North_Ame
26754 NAD_1927_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1927_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_North_Am
26755 NAD_1927_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1927_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_North_Ame
26756 NAD_1927_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1927_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_North_American

26757 NAD_1927_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1927_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_North_American_

26758 NAD_1927_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1927_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_North_America
26759 NAD_1927_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1927_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_North_Americ
26760 NAD_1927_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1927_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_North_Americ
26766 NAD_1927_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1927_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_North_Americ
26767 NAD_1927_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1927_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_North_Ameri
26768 NAD_1927_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1927_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_North_American
26769 NAD_1927_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1927_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_North_Americ
26770 NAD_1927_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1927_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_North_American
26771 NAD_1927_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1927_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_North_America
26772 NAD_1927_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1927_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_North_America
26773 NAD_1927_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1927_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_North_America
26774 NAD_1927_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1927_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_North_Americ
26775 NAD_1927_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1927_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_North_American
26776 NAD_1927_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1927_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_North_American
26777 NAD_1927_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1927_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_North_Americ
26778 NAD_1927_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1927_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_North_Ameri
26779 NAD_1927_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1927_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_North_Ame
26780 NAD_1927_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1927_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_North_Ame
26781 NAD_1927_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1927_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_North_Ame
26782 NAD_1927_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1927_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_North_Ame
26783 NAD_1927_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1927_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_North_American
26784 NAD_1927_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1927_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_North_America
26785 NAD_1927_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1927_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_North_American_1
26786 NAD_1927_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1927_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS["GCS_N
26787 NAD_1927_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1927_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["GCS_North
26788 NAD_1927_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1927_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_North_Amer
26789 NAD_1927_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1927_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_North_Am
26790 NAD_1927_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1927_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_North_Ame
26791 NAD_1927_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1927_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_North_Am
26792 NAD_1927_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1927_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS_North_A
26793 NAD_1927_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1927_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_North_Am
26794 NAD_1927_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1927_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_North_Ame
26795 NAD_1927_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1927_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_North_Am
26796 NAD_1927_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1927_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_North_Americ
26797 NAD_1927_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1927_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_North_Am
26798 NAD_1927_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1927_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_North_Ameri
26799 NAD_1927_StatePlane_California_VII_FIPS_0407 PROJCS["NAD_1927_StatePlane_California_VII_FIPS_0407",GEOGCS["GCS_North_Americ
26847 NAD_1983_StatePlane_Maine_East_FIPS_1801_Feet PROJCS["NAD_1983_StatePlane_Maine_East_FIPS_1801_Feet",GEOGCS["GCS_North_Am
26848 NAD_1983_StatePlane_Maine_West_FIPS_1802_Feet PROJCS["NAD_1983_StatePlane_Maine_West_FIPS_1802_Feet",GEOGCS["GCS_North_Am
26849 NAD_1983_StatePlane_Minnesota_North_FIPS_2201_Feet PROJCS["NAD_1983_StatePlane_Minnesota_North_FIPS_2201_Feet",GEOGCS["GCS_Nort
26850 NAD_1983_StatePlane_Minnesota_Central_FIPS_2202_Feet PROJCS["NAD_1983_StatePlane_Minnesota_Central_FIPS_2202_Feet",GEOGCS["GCS_No
26851 NAD_1983_StatePlane_Minnesota_South_FIPS_2203_Feet PROJCS["NAD_1983_StatePlane_Minnesota_South_FIPS_2203_Feet",GEOGCS["GCS_Nort
26852 NAD_1983_StatePlane_Nebraska_FIPS_2600_Feet PROJCS["NAD_1983_StatePlane_Nebraska_FIPS_2600_Feet",GEOGCS["GCS_North_Amer
26853 NAD_1983_StatePlane_West_Virginia_North_FIPS_4701_Feet PROJCS["NAD_1983_StatePlane_West_Virginia_North_FIPS_4701_Feet",GEOGCS["GCS_N
26854 NAD_1983_StatePlane_West_Virginia_South_FIPS_4702_Feet PROJCS["NAD_1983_StatePlane_West_Virginia_South_FIPS_4702_Feet",GEOGCS["GCS_N
26855 NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801_Feet PROJCS["NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801_Feet",GEOGCS["GCS_No
26856 NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802_Feet PROJCS["NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802_Feet",GEOGCS["GCS_N
26857 NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201_Feet PROJCS["NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201_Feet",GEOGCS["GC
26858 NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202_Feet PROJCS["NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202_Feet",GEOGCS["G
26859 NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203_Feet PROJCS["NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203_Feet",GEOGCS["GC
26860 NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600_Feet PROJCS["NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600_Feet",GEOGCS["GCS_Nort
26861 NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701_Feet PROJCS["NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701_Feet",GEOGCS[
26862 NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702_Feet PROJCS["NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702_Feet",GEOGCS[

26863 NAD_1983_NSRS2007_StatePlane_Maine_East_FIPS_1801_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Maine_East_FIPS_1801_Ft_US",GEOGCS["G

26864 NAD_1983_NSRS2007_StatePlane_Maine_West_FIPS_1802_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Maine_West_FIPS_1802_Ft_US",GEOGCS["G
26865 NAD_1983_NSRS2007_StatePlane_Minnesota_North_FIPS_2201_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Minnesota_North_FIPS_2201_Ft_US",GEOGC
26866 NAD_1983_NSRS2007_StatePlane_Minnesota_Central_FIPS_2202_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Minnesota_Central_FIPS_2202_Ft_US",GEOG
26867 NAD_1983_NSRS2007_StatePlane_Minnesota_South_FIPS_2203_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Minnesota_South_FIPS_2203_Ft_US",GEOGC
26868 NAD_1983_NSRS2007_StatePlane_Nebraska_FIPS_2600_Ft_US PROJCS["NAD_1983_NSRS2007_StatePlane_Nebraska_FIPS_2600_Ft_US",GEOGCS["GC
26869 NAD_1983_NSRS2007_StatePlane_West_Virginia_North_FIPS_4701_FtUS PROJCS["NAD_1983_NSRS2007_StatePlane_West_Virginia_North_FIPS_4701_FtUS",GEO
26870 NAD_1983_NSRS2007_StatePlane_West_Virginia_South_FIPS_4702_FtUS PROJCS["NAD_1983_NSRS2007_StatePlane_West_Virginia_South_FIPS_4702_FtUS",GEO
26891 NAD_1983_CSRS_MTM_11 PROJCS["NAD_1983_CSRS_MTM_11",GEOGCS["GCS_North_American_1983_CSRS",DAT
26898 NAD_1983_CSRS_MTM_1 PROJCS["NAD_1983_CSRS_MTM_1",GEOGCS["GCS_North_American_1983_CSRS",DATU
26899 NAD_1983_CSRS_MTM_2 PROJCS["NAD_1983_CSRS_MTM_2",GEOGCS["GCS_North_American_1983_CSRS",DATU
26929 NAD_1983_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1983_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_North_Ameri
26930 NAD_1983_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1983_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_North_Amer
26940 NAD_1983_StatePlane_Alaska_10_FIPS_5010 PROJCS["NAD_1983_StatePlane_Alaska_10_FIPS_5010",GEOGCS["GCS_North_American_
26941 NAD_1983_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1983_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_North_American
26942 NAD_1983_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1983_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_North_America

26943 NAD_1983_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1983_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_North_America

26944 NAD_1983_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1983_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_North_America
26945 NAD_1983_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1983_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_North_America
26946 NAD_1983_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1983_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_North_America
26948 NAD_1983_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1983_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_North_Americ
26949 NAD_1983_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1983_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_North_Ame
26950 NAD_1983_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1983_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_North_Americ
26951 NAD_1983_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1983_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_North_Ame
26952 NAD_1983_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1983_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_North_Ame
26953 NAD_1983_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1983_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_North_Ame
26954 NAD_1983_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1983_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_North_Am
26955 NAD_1983_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1983_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_North_Ame
26956 NAD_1983_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1983_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_North_American
26957 NAD_1983_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1983_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_North_American_
26958 NAD_1983_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1983_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_North_America
26959 NAD_1983_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1983_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_North_Americ
26960 NAD_1983_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1983_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_North_Americ
26961 NAD_1983_StatePlane_Hawaii_1_FIPS_5101 PROJCS["NAD_1983_StatePlane_Hawaii_1_FIPS_5101",GEOGCS["GCS_North_American_1
26966 NAD_1983_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1983_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_North_Americ
26967 NAD_1983_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1983_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_North_Ameri
26968 NAD_1983_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1983_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_North_American
26969 NAD_1983_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1983_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_North_Americ
26970 NAD_1983_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1983_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_North_American
26971 NAD_1983_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1983_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_North_America
26972 NAD_1983_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1983_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_North_America
26973 NAD_1983_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1983_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_North_America
26974 NAD_1983_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1983_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_North_Americ
26975 NAD_1983_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1983_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_North_American
26976 NAD_1983_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1983_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_North_American
26977 NAD_1983_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1983_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_North_Americ
26978 NAD_1983_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1983_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_North_Ameri
26979 NAD_1983_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_North_Ame
26980 NAD_1983_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1983_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_North_Ame
26981 NAD_1983_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1983_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_North_Ame
26982 NAD_1983_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1983_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_North_Ame
26983 NAD_1983_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1983_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_North_American
26984 NAD_1983_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1983_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_North_America
26985 NAD_1983_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1983_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_North_American_1
26986 NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS["GCS_N
26987 NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["GCS_North
26988 NAD_1983_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1983_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_North_Amer
26989 NAD_1983_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1983_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_North_Am
26990 NAD_1983_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1983_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_North_Ame
26991 NAD_1983_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1983_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_North_Am
26992 NAD_1983_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1983_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS_North_A
26993 NAD_1983_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1983_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_North_Am
26994 NAD_1983_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1983_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_North_Ame
26995 NAD_1983_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1983_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_North_Am
26996 NAD_1983_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1983_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_North_Americ
26997 NAD_1983_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1983_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_North_Am

26998 NAD_1983_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1983_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_North_Ameri

27037 Nahrwan_1967_UTM_Zone_37N PROJCS["Nahrwan_1967_UTM_Zone_37N",GEOGCS["GCS_Nahrwan_1967",DATUM["D_Na
27120 Naparima_1972_UTM_Zone_20N PROJCS["Naparima_1972_UTM_Zone_20N",GEOGCS["GCS_Naparima_1972",DATUM["D_N
27200 GD_1949_New_Zealand_Map_Grid PROJCS["GD_1949_New_Zealand_Map_Grid",GEOGCS["GCS_New_Zealand_1949",DATUM
27205 NZGD_1949_Mount_Eden_Circuit PROJCS["NZGD_1949_Mount_Eden_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM[
27206 NZGD_1949_Bay_of_Plenty_Circuit PROJCS["NZGD_1949_Bay_of_Plenty_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM
27207 NZGD_1949_Poverty_Bay_Circuit PROJCS["NZGD_1949_Poverty_Bay_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM[
27208 NZGD_1949_Hawkes_Bay_Circuit PROJCS["NZGD_1949_Hawkes_Bay_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM
27209 NZGD_1949_Taranaki_Circuit PROJCS["NZGD_1949_Taranaki_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_N
27210 NZGD_1949_Tuhirangi_Circuit PROJCS["NZGD_1949_Tuhirangi_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_
27211 NZGD_1949_Wanganui_Circuit PROJCS["NZGD_1949_Wanganui_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D
27212 NZGD_1949_Wairarapa_Circuit PROJCS["NZGD_1949_Wairarapa_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D
27213 NZGD_1949_Wellington_Circuit PROJCS["NZGD_1949_Wellington_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D
27214 NZGD_1949_Collingwood_Circuit PROJCS["NZGD_1949_Collingwood_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["
27215 NZGD_1949_Nelson_Circuit PROJCS["NZGD_1949_Nelson_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_Ne
27216 NZGD_1949_Karamea_Circuit PROJCS["NZGD_1949_Karamea_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_
27217 NZGD_1949_Buller_Circuit PROJCS["NZGD_1949_Buller_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_New
27218 NZGD_1949_Grey_Circuit PROJCS["NZGD_1949_Grey_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_New
27219 NZGD_1949_Amuri_Circuit PROJCS["NZGD_1949_Amuri_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_Ne
27220 NZGD_1949_Marlborough_Circuit PROJCS["NZGD_1949_Marlborough_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM[
27221 NZGD_1949_Hokitika_Circuit PROJCS["NZGD_1949_Hokitika_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_N
27222 NZGD_1949_Okarito_Circuit PROJCS["NZGD_1949_Okarito_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_N
27223 NZGD_1949_Jacksons_Bay_Circuit PROJCS["NZGD_1949_Jacksons_Bay_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM
27224 NZGD_1949_Mount_Pleasant_Circuit PROJCS["NZGD_1949_Mount_Pleasant_Circuit",GEOGCS["GCS_New_Zealand_1949",DATU
27225 NZGD_1949_Gawler_Circuit PROJCS["NZGD_1949_Gawler_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_N
27226 NZGD_1949_Timaru_Circuit PROJCS["NZGD_1949_Timaru_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_Ne
27227 NZGD_1949_Lindis_Peak_Circuit PROJCS["NZGD_1949_Lindis_Peak_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["
27228 NZGD_1949_Mount_Nicholas_Circuit PROJCS["NZGD_1949_Mount_Nicholas_Circuit",GEOGCS["GCS_New_Zealand_1949",DATU
27229 NZGD_1949_Mount_York_Circuit PROJCS["NZGD_1949_Mount_York_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["
27230 NZGD_1949_Observation_Point_Circuit PROJCS["NZGD_1949_Observation_Point_Circuit",GEOGCS["GCS_New_Zealand_1949",DA
27231 NZGD_1949_North_Taieri_Circuit PROJCS["NZGD_1949_North_Taieri_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["
27232 NZGD_1949_Bluff_Circuit PROJCS["NZGD_1949_Bluff_Circuit",GEOGCS["GCS_New_Zealand_1949",DATUM["D_New
27258 NZGD_1949_UTM_Zone_58S PROJCS["NZGD_1949_UTM_Zone_58S",GEOGCS["GCS_New_Zealand_1949",DATUM["D_
27291 New_Zealand_North_Island PROJCS["New_Zealand_North_Island",GEOGCS["GCS_New_Zealand_1949",DATUM["D_Ne
27292 New_Zealand_South_Island PROJCS["New_Zealand_South_Island",GEOGCS["GCS_New_Zealand_1949",DATUM["D_Ne
27391 NGO_1948_Oslo_Norway_Zone_1 PROJCS["NGO_1948_Oslo_Norway_Zone_1",GEOGCS["GCS_NGO_1948_Oslo",DATUM["D
27429 Datum_73_UTM_Zone_29N PROJCS["Datum_73_UTM_Zone_29N",GEOGCS["GCS_Datum_73",DATUM["D_Datum_73",
27492 Datum_73_Modified_Portuguese_Grid PROJCS["Datum_73_Modified_Portuguese_Grid",GEOGCS["GCS_Datum_73",DATUM["D_D
27493 Datum_73_Modified_Portuguese_Grid PROJCS["Datum_73_Modified_Portuguese_Grid",GEOGCS["GCS_Datum_73",DATUM["D_D
27500 Nord_de_Guerre PROJCS["Nord_de_Guerre",GEOGCS["GCS_ATF_Paris",DATUM["D_ATF",SPHEROID["Pless
27561 NTF_Paris_Lambert_Nord_France PROJCS["NTF_Paris_Lambert_Nord_France",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF"
27562 NTF_Paris_Lambert_Centre_France PROJCS["NTF_Paris_Lambert_Centre_France",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF

27563 NTF_Paris_Lambert_Sud_France PROJCS["NTF_Paris_Lambert_Sud_France",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",S

27564 NTF_Paris_Lambert_Corse PROJCS["NTF_Paris_Lambert_Corse",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHER
27571 NTF_Paris_Lambert_Zone_I PROJCS["NTF_Paris_Lambert_Zone_I",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHE
27572 NTF_Paris_Lambert_Zone_II PROJCS["NTF_Paris_Lambert_Zone_II",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHE
27573 NTF_Paris_Lambert_Zone_III PROJCS["NTF_Paris_Lambert_Zone_III",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPH
27574 NTF_Paris_Lambert_Zone_IV PROJCS["NTF_Paris_Lambert_Zone_IV",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPH
27581 NTF_Paris_France_I PROJCS["NTF_Paris_France_I",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHEROID["
27582 NTF_Paris_France_II PROJCS["NTF_Paris_France_II",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHEROID[
27583 NTF_Paris_France_III PROJCS["NTF_Paris_France_III",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHEROID
27584 NTF_Paris_France_IV PROJCS["NTF_Paris_France_IV",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHEROID
27591 NTF_Paris_Nord_France PROJCS["NTF_Paris_Nord_France",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHERO
27592 NTF_Paris_Centre_France PROJCS["NTF_Paris_Centre_France",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHER
27593 NTF_Paris_Sud_France PROJCS["NTF_Paris_Sud_France",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHEROI
27594 NTF_Paris_Corse PROJCS["NTF_Paris_Corse",GEOGCS["GCS_NTF_Paris",DATUM["D_NTF",SPHEROID["Cla
27700 British_National_Grid PROJCS["British_National_Grid",GEOGCS["GCS_OSGB_1936",DATUM["D_OSGB_1936",SP
28191 Palestine_1923_Palestine_Grid PROJCS["Palestine_1923_Palestine_Grid",GEOGCS["GCS_Palestine_1923",DATUM["D_Pale
28192 Palestine_1923_Palestine_Belt PROJCS["Palestine_1923_Palestine_Belt",GEOGCS["GCS_Palestine_1923",DATUM["D_Pale
28193 Palestine_1923_Israel_CS_Grid PROJCS["Palestine_1923_Israel_CS_Grid",GEOGCS["GCS_Palestine_1923",DATUM["D_Pa
28232 Pointe_Noire_UTM_Zone_32S PROJCS["Pointe_Noire_UTM_Zone_32S",GEOGCS["GCS_Pointe_Noire",DATUM["D_Pointe_
28348 GDA_1994_MGA_Zone_48 PROJCS["GDA_1994_MGA_Zone_48",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994"


28471 Pulkovo_1942_GK_Zone_11N PROJCS["Pulkovo_1942_GK_Zone_11N",GEOGCS["GCS_Pulkovo_1942",DATUM["D_Pulkov
28600 Qatar_National_Grid PROJCS["Qatar_National_Grid",GEOGCS["GCS_Qatar_1974",DATUM["D_Qatar",SPHEROID
28991 RD_Old PROJCS["RD_Old",GEOGCS["GCS_Amersfoort",DATUM["D_Amersfoort",SPHEROID["Besse
28992 RD_New PROJCS["RD_New",GEOGCS["GCS_Amersfoort",DATUM["D_Amersfoort",SPHEROID["Bess
29100 SAD_1969_Brazil_Polyconic PROJCS["SAD_1969_Brazil_Polyconic",GEOGCS["GCS_South_American_1969",DATUM["D_
29101 SAD_1969_Brazil_Polyconic PROJCS["SAD_1969_Brazil_Polyconic",GEOGCS["GCS_South_American_1969",DATUM["D_
29118 SAD_1969_UTM_Zone_18N PROJCS["SAD_1969_UTM_Zone_18N",GEOGCS["GCS_South_American_1969",DATUM["D
29177 SAD_1969_UTM_Zone_17S PROJCS["SAD_1969_UTM_Zone_17S",GEOGCS["GCS_South_American_1969",DATUM["D_


29220 Sapper_Hill_1943_UTM_Zone_20S PROJCS["Sapper_Hill_1943_UTM_Zone_20S",GEOGCS["GCS_Sapper_Hill_1943",DATUM["
29221 Sapper_Hill_1943_UTM_Zone_21S PROJCS["Sapper_Hill_1943_UTM_Zone_21S",GEOGCS["GCS_Sapper_Hill_1943",DATUM["
29333 Schwarzeck_UTM_Zone_33S PROJCS["Schwarzeck_UTM_Zone_33S",GEOGCS["GCS_Schwarzeck",DATUM["D_Schwarz
29635 Sudan_UTM_Zone_35N PROJCS["Sudan_UTM_Zone_35N",GEOGCS["GCS_Sudan",DATUM["D_Sudan",SPHEROID
29636 Sudan_UTM_Zone_36N PROJCS["Sudan_UTM_Zone_36N",GEOGCS["GCS_Sudan",DATUM["D_Sudan",SPHEROID
29701 Tananarive_1925_Paris_Laborde_Grid PROJCS["Tananarive_1925_Paris_Laborde_Grid",GEOGCS["GCS_Tananarive_1925_Paris",D
29738 Tananarive_1925_UTM_Zone_38S PROJCS["Tananarive_1925_UTM_Zone_38S",GEOGCS["GCS_Tananarive_1925",DATUM["D
29739 Tananarive_1925_UTM_Zone_39S PROJCS["Tananarive_1925_UTM_Zone_39S",GEOGCS["GCS_Tananarive_1925",DATUM["D
29849 Timbalai_1948_UTM_Zone_49N PROJCS["Timbalai_1948_UTM_Zone_49N",GEOGCS["GCS_Timbalai_1948",DATUM["D_Tim
29850 Timbalai_1948_UTM_Zone_50N PROJCS["Timbalai_1948_UTM_Zone_50N",GEOGCS["GCS_Timbalai_1948",DATUM["D_Tim
29871 Timbalai_1948_RSO_Borneo_Chains PROJCS["Timbalai_1948_RSO_Borneo_Chains",GEOGCS["GCS_Timbalai_1948",DATUM["D
29872 Timbalai_1948_RSO_Borneo_Feet PROJCS["Timbalai_1948_RSO_Borneo_Feet",GEOGCS["GCS_Timbalai_1948",DATUM["D_T
29873 Timbalai_1948_RSO_Borneo_Meters PROJCS["Timbalai_1948_RSO_Borneo_Meters",GEOGCS["GCS_Timbalai_1948",DATUM["D
29900 TM65_Irish_Grid PROJCS["TM65_Irish_Grid",GEOGCS["GCS_TM65",DATUM["D_TM65",SPHEROID["Airy_Mo
29901 OSNI_1952_Irish_National_Grid PROJCS["OSNI_1952_Irish_National_Grid",GEOGCS["GCS_OSNI_1952",DATUM["D_OSNI_
30161 Japan_Zone_1 PROJCS["Japan_Zone_1",GEOGCS["GCS_Tokyo",DATUM["D_Tokyo",SPHEROID["Bessel_1
30170 Japan_Zone_10 PROJCS["Japan_Zone_10",GEOGCS["GCS_Tokyo",DATUM["D_Tokyo",SPHEROID["Bessel_
30200 Trinidad_1903_Trinidad_Grid PROJCS["Trinidad_1903_Trinidad_Grid",GEOGCS["GCS_Trinidad_1903",DATUM["D_Trinidad

30339 TC_1948_UTM_Zone_39N PROJCS["TC_1948_UTM_Zone_39N",GEOGCS["GCS_Trucial_Coast_1948",DATUM["D_Tru

30340 TC_1948_UTM_Zone_40N PROJCS["TC_1948_UTM_Zone_40N",GEOGCS["GCS_Trucial_Coast_1948",DATUM["D_Tru
30491 Nord_Algerie_Ancienne PROJCS["Nord_Algerie_Ancienne",GEOGCS["GCS_Voirol_1875",DATUM["D_Voirol_1875",S
30492 Sud_Algerie_Ancienne PROJCS["Sud_Algerie_Ancienne",GEOGCS["GCS_Voirol_1875",DATUM["D_Voirol_1875",SP
30493 Voirol_1879_Nord_Algerie_Ancienne PROJCS["Voirol_1879_Nord_Algerie_Ancienne",GEOGCS["GCS_Voirol_1879",DATUM["D_Vo
30494 Voirol_1879_Sud_Algerie_Ancienne PROJCS["Voirol_1879_Sud_Algerie_Ancienne",GEOGCS["GCS_Voirol_1879",DATUM["D_Vo
30591 Nord_Algerie PROJCS["Nord_Algerie",GEOGCS["GCS_Voirol_Unifie_1960",DATUM["D_Voirol_Unifie_1960
30592 Sud_Algerie PROJCS["Sud_Algerie",GEOGCS["GCS_Voirol_Unifie_1960",DATUM["D_Voirol_Unifie_1960"
30729 Nord_Sahara_1959_UTM_Zone_29N PROJCS["Nord_Sahara_1959_UTM_Zone_29N",GEOGCS["GCS_Nord_Sahara_1959",DATU
30791 Nord_Sahara_1959_Voirol_Unifie_Nord PROJCS["Nord_Sahara_1959_Voirol_Unifie_Nord",GEOGCS["GCS_Nord_Sahara_1959",DAT
30792 Nord_Sahara_1959_Voirol_Unifie_Sud PROJCS["Nord_Sahara_1959_Voirol_Unifie_Sud",GEOGCS["GCS_Nord_Sahara_1959",DAT
31028 Yoff_1972_UTM_Zone_28N PROJCS["Yoff_1972_UTM_Zone_28N",GEOGCS["GCS_Yoff",DATUM["D_Yoff",SPHEROID["C
31121 Zanderij_1972_UTM_Zone_21N PROJCS["Zanderij_1972_UTM_Zone_21N",GEOGCS["GCS_Zanderij",DATUM["D_Zanderij",S
31154 Zanderij_TM_54_NW PROJCS["Zanderij_TM_54_NW",GEOGCS["GCS_Zanderij",DATUM["D_Zanderij",SPHEROID
31170 Zanderij_Suriname_Old_TM PROJCS["Zanderij_Suriname_Old_TM",GEOGCS["GCS_Zanderij",DATUM["D_Zanderij",SPH
31171 Zanderij_Suriname_TM PROJCS["Zanderij_Suriname_TM",GEOGCS["GCS_Zanderij",DATUM["D_Zanderij",SPHERO
31251 MGI_Ferro_Austria_GK_West PROJCS["MGI_Ferro_Austria_GK_West",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPH
31252 MGI_Ferro_Austria_GK_Central PROJCS["MGI_Ferro_Austria_GK_Central",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SP
31253 MGI_Ferro_Austria_GK_East PROJCS["MGI_Ferro_Austria_GK_East",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPH
31254 MGI_Austria_GK_West PROJCS["MGI_Austria_GK_West",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Bess
31255 MGI_Austria_GK_Central PROJCS["MGI_Austria_GK_Central",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Be
31256 MGI_Austria_GK_East PROJCS["MGI_Austria_GK_East",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Bess
31257 MGI_Austria_GK_M28 PROJCS["MGI_Austria_GK_M28",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Bess
31265 MGI_3_Degree_Gauss_Zone_5 PROJCS["MGI_3_Degree_Gauss_Zone_5",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHERO
31275 MGI_Balkans_5 PROJCS["MGI_Balkans_5",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Bessel_184
31281 Austria_West_Zone PROJCS["Austria_West_Zone",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID["B
31282 Austria_Central_Zone PROJCS["Austria_Central_Zone",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID[
31283 Austria_East_Zone PROJCS["Austria_East_Zone",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID["Be
31284 MGI_M28 PROJCS["MGI_M28",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Bessel_1841",637
31287 MGI_Austria_Lambert PROJCS["MGI_Austria_Lambert",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Besse
31288 MGI_Ferro_M28 PROJCS["MGI_Ferro_M28",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID["Bess
31291 Austria_West_Zone PROJCS["Austria_West_Zone",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID["B
31292 Austria_Central_Zone PROJCS["Austria_Central_Zone",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID[
31293 Austria_East_Zone PROJCS["Austria_East_Zone",GEOGCS["GCS_MGI_Ferro",DATUM["D_MGI",SPHEROID["Be
31297 MGI_Austria_Lambert PROJCS["MGI_Austria_Lambert",GEOGCS["GCS_MGI",DATUM["D_MGI",SPHEROID["Besse

31370 Belge_Lambert_1972 PROJCS["Belge_Lambert_1972",GEOGCS["GCS_Belge_1972",DATUM["D_Belge_1972",SPH

31461 DHDN_3_Degree_Gauss_Zone_1 PROJCS["DHDN_3_Degree_Gauss_Zone_1",GEOGCS["GCS_Deutsches_Hauptdreiecksnetz
31491 Germany_Zone_1 PROJCS["Germany_Zone_1",GEOGCS["GCS_Deutsches_Hauptdreiecksnetz",DATUM["D_De
31528 Conakry_1905_UTM_Zone_28N PROJCS["Conakry_1905_UTM_Zone_28N",GEOGCS["GCS_Conakry_1905",DATUM["D_Con
31529 Conakry_1905_UTM_Zone_29N PROJCS["Conakry_1905_UTM_Zone_29N",GEOGCS["GCS_Conakry_1905",DATUM["D_Con
31600 Stereo_33 PROJCS["Stereo_33",GEOGCS["GCS_Dealul_Piscului_1933",DATUM["D_Dealul_Piscului_19
31700 Stereo_70 PROJCS["Stereo_70",GEOGCS["GCS_Dealul_Piscului_1970",DATUM["D_Dealul_Piscului_19
31838 NGN_UTM_Zone_38N PROJCS["NGN_UTM_Zone_38N",GEOGCS["GCS_NGN",DATUM["D_NGN",SPHEROID["WG
31839 NGN_UTM_Zone_39N PROJCS["NGN_UTM_Zone_39N",GEOGCS["GCS_NGN",DATUM["D_NGN",SPHEROID["WG
31901 KUDAMS_KTM PROJCS["KUDAMS_KTM",GEOGCS["GCS_KUDAMS",DATUM["D_Kuwait_Utility",SPHEROID
31917 SIRGAS_UTM_Zone_17N PROJCS["SIRGAS_UTM_Zone_17N",GEOGCS["GCS_SIRGAS",DATUM["D_SIRGAS",SPHE
31965 SIRGAS_2000_UTM_Zone_11N PROJCS["SIRGAS_2000_UTM_Zone_11N",GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIR
31977 SIRGAS_2000_UTM_Zone_17S PROJCS["SIRGAS_2000_UTM_Zone_17S",GEOGCS["GCS_SIRGAS_2000",DATUM["D_SIR


31992 SIRGAS_UTM_Zone_17S PROJCS["SIRGAS_UTM_Zone_17S",GEOGCS["GCS_SIRGAS",DATUM["D_SIRGAS",SPHE
32001 NAD_1927_StatePlane_Montana_North_FIPS_2501 PROJCS["NAD_1927_StatePlane_Montana_North_FIPS_2501",GEOGCS["GCS_North_Amer
32002 NAD_1927_StatePlane_Montana_Central_FIPS_2502 PROJCS["NAD_1927_StatePlane_Montana_Central_FIPS_2502",GEOGCS["GCS_North_Am
32003 NAD_1927_StatePlane_Montana_South_FIPS_2503 PROJCS["NAD_1927_StatePlane_Montana_South_FIPS_2503",GEOGCS["GCS_North_Ame
32005 NAD_1927_StatePlane_Nebraska_North_FIPS_2601 PROJCS["NAD_1927_StatePlane_Nebraska_North_FIPS_2601",GEOGCS["GCS_North_Ame
32006 NAD_1927_StatePlane_Nebraska_South_FIPS_2602 PROJCS["NAD_1927_StatePlane_Nebraska_South_FIPS_2602",GEOGCS["GCS_North_Ame
32007 NAD_1927_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1927_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_North_Americ
32008 NAD_1927_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1927_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_North_Ame
32009 NAD_1927_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1927_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_North_Americ
32010 NAD_1927_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1927_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_North_Ame
32011 NAD_1927_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1927_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_North_America
32012 NAD_1927_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1927_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS_North_Am
32013 NAD_1927_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1927_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["GCS_North_
32014 NAD_1927_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1927_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS_North_A
32015 NAD_1927_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1927_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_North_Ame
32016 NAD_1927_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1927_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS_North_Am
32017 NAD_1927_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1927_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_North_Ame
32018 NAD_1927_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1927_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GCS_Nor
32019 NAD_1927_StatePlane_North_Carolina_FIPS_3200 PROJCS["NAD_1927_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_North_Amer
32020 NAD_1927_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1927_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GCS_North_
32021 NAD_1927_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1927_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GCS_North_
32022 NAD_1927_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1927_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_North_American
32023 NAD_1927_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1927_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_North_American
32024 NAD_1927_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1927_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_North_Am
32025 NAD_1927_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1927_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_North_Am
32026 NAD_1927_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1927_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_North_Americ
32027 NAD_1927_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1927_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_North_Ameri
32028 NAD_1927_StatePlane_Pennsylvania_North_FIPS_3701 PROJCS["NAD_1927_StatePlane_Pennsylvania_North_FIPS_3701",GEOGCS["GCS_North_A
32029 NAD_1927_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1927_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GCS_North_
32030 NAD_1927_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1927_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_North_Americ
32031 NAD_1927_StatePlane_South_Carolina_North_FIPS_3901 PROJCS["NAD_1927_StatePlane_South_Carolina_North_FIPS_3901",GEOGCS["GCS_North
32033 NAD_1927_StatePlane_South_Carolina_South_FIPS_3902 PROJCS["NAD_1927_StatePlane_South_Carolina_South_FIPS_3902",GEOGCS["GCS_North
32034 NAD_1927_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1927_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GCS_North_
32035 NAD_1927_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1927_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["GCS_North_
32036 NAD_1927_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1927_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_North_American
32037 NAD_1927_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1927_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_North_America
32038 NAD_1927_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1927_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["GCS_North_
32039 NAD_1927_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1927_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_North_Ameri
32040 NAD_1927_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1927_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["GCS_North
32041 NAD_1927_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1927_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_North_America
32042 NAD_1927_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1927_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_North_American
32043 NAD_1927_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1927_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_North_Americ
32044 NAD_1927_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1927_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_North_American
32045 NAD_1927_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1927_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_North_American_1
32046 NAD_1927_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1927_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_North_Americ

32047 NAD_1927_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1927_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_North_Ameri

32048 NAD_1927_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1927_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS_North_Am
32049 NAD_1927_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1927_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS_North_A
32050 NAD_1927_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1927_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GCS_North_
32051 NAD_1927_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1927_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GCS_North_
32052 NAD_1927_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1927_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_North_Am
32053 NAD_1927_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1927_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS_North_A
32054 NAD_1927_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1927_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_North_Am
32055 NAD_1927_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1927_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_North_Amer
32056 NAD_1927_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1927_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS["GCS_Nor
32057 NAD_1927_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1927_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS["GCS_No
32058 NAD_1927_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1927_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_North_Ame
32059 NAD_1927_StatePlane_Puerto_Rico_FIPS_5201 PROJCS["NAD_1927_StatePlane_Puerto_Rico_FIPS_5201",GEOGCS["GCS_North_America
32060 NAD_1927_StatePlane_Virgin_Islands_St_Croix_FIPS_5202 PROJCS["NAD_1927_StatePlane_Virgin_Islands_St_Croix_FIPS_5202",GEOGCS["GCS_Nor
32061 NAD_1927_Guatemala_Norte PROJCS["NAD_1927_Guatemala_Norte",GEOGCS["GCS_North_American_1927",DATUM["D
32062 NAD_1927_Guatemala_Sur PROJCS["NAD_1927_Guatemala_Sur",GEOGCS["GCS_North_American_1927",DATUM["D_
32064 NAD_1927_BLM_Zone_14N PROJCS["NAD_1927_BLM_Zone_14N",GEOGCS["GCS_North_American_1927",DATUM["D_
32081 NAD_1927_MTM_1 PROJCS["NAD_1927_MTM_1",GEOGCS["GCS_North_American_1927",DATUM["D_North_A
32098 NAD_1927_Quebec_Lambert PROJCS["NAD_1927_Quebec_Lambert",GEOGCS["GCS_North_American_1927",DATUM["D
32099 NAD_1927_StatePlane_Louisiana_Offshore_FIPS_1703 PROJCS["NAD_1927_StatePlane_Louisiana_Offshore_FIPS_1703",GEOGCS["GCS_North_A
32100 NAD_1983_StatePlane_Montana_FIPS_2500 PROJCS["NAD_1983_StatePlane_Montana_FIPS_2500",GEOGCS["GCS_North_American_1
32104 NAD_1983_StatePlane_Nebraska_FIPS_2600 PROJCS["NAD_1983_StatePlane_Nebraska_FIPS_2600",GEOGCS["GCS_North_American_
32107 NAD_1983_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1983_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_North_Americ
32108 NAD_1983_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1983_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_North_Ame
32109 NAD_1983_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1983_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_North_Americ
32110 NAD_1983_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1983_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_North_Ame
32111 NAD_1983_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1983_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_North_America
32112 NAD_1983_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1983_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS_North_Am
32113 NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["GCS_North_
32114 NAD_1983_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1983_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS_North_A
32115 NAD_1983_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1983_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_North_Ame
32116 NAD_1983_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1983_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS_North_Am
32117 NAD_1983_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1983_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_North_Ame
32118 NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GCS_Nor
32119 NAD_1983_StatePlane_North_Carolina_FIPS_3200 PROJCS["NAD_1983_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_North_Amer
32120 NAD_1983_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1983_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GCS_North_
32121 NAD_1983_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1983_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GCS_North_
32122 NAD_1983_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1983_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_North_American
32123 NAD_1983_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1983_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_North_American
32124 NAD_1983_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1983_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_North_Am
32125 NAD_1983_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1983_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_North_Am
32126 NAD_1983_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_North_Americ

32127 NAD_1983_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_North_Ameri

32128 NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701 PROJCS["NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701",GEOGCS["GCS_North_A
32129 NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GCS_North_
32130 NAD_1983_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1983_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_North_Americ
32133 NAD_1983_StatePlane_South_Carolina_FIPS_3900 PROJCS["NAD_1983_StatePlane_South_Carolina_FIPS_3900",GEOGCS["GCS_North_Amer
32134 NAD_1983_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1983_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GCS_North_
32135 NAD_1983_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1983_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["GCS_North_
32136 NAD_1983_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1983_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_North_American
32137 NAD_1983_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1983_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_North_America
32138 NAD_1983_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1983_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["GCS_North_
32139 NAD_1983_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1983_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_North_Ameri
32140 NAD_1983_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1983_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["GCS_North
32141 NAD_1983_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1983_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_North_America
32142 NAD_1983_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1983_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_North_American
32143 NAD_1983_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1983_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_North_Americ
32144 NAD_1983_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1983_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_North_American
32145 NAD_1983_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1983_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_North_American_1
32146 NAD_1983_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1983_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_North_Americ
32147 NAD_1983_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1983_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_North_Ameri
32148 NAD_1983_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1983_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS_North_Am
32149 NAD_1983_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1983_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS_North_A
32150 NAD_1983_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1983_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GCS_North_
32151 NAD_1983_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1983_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GCS_North_
32152 NAD_1983_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1983_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_North_Am
32153 NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS_North_A
32154 NAD_1983_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1983_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_North_Am
32155 NAD_1983_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1983_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_North_Amer
32156 NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS["GCS_Nor
32157 NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS["GCS_No
32158 NAD_1983_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1983_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_North_Ame
32161 NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200 PROJCS["NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200",GEOGCS["GCS_
32164 NAD_1983_BLM_Zone_14N_ftUS PROJCS["NAD_1983_BLM_Zone_14N_ftUS",GEOGCS["GCS_North_American_1983",DATU
32180 NAD_1983_MTM_2_SCoPQ PROJCS["NAD_1983_MTM_2_SCoPQ",GEOGCS["GCS_North_American_1983",DATUM["D_
32190 NAD_1983_MTM_10 PROJCS["NAD_1983_MTM_10",GEOGCS["GCS_North_American_1983",DATUM["D_North_
32198 NAD_1983_Quebec_Lambert PROJCS["NAD_1983_Quebec_Lambert",GEOGCS["GCS_North_American_1983",DATUM["D

32199 NAD_1983_StatePlane_Louisiana_Offshore_FIPS_1703 PROJCS["NAD_1983_StatePlane_Louisiana_Offshore_FIPS_1703",GEOGCS["GCS_North_A

32201 WGS_1972_UTM_Zone_1N PROJCS["WGS_1972_UTM_Zone_1N",GEOGCS["GCS_WGS_1972",DATUM["D_WGS_1972


32301 WGS_1972_UTM_Zone_1S PROJCS["WGS_1972_UTM_Zone_1S",GEOGCS["GCS_WGS_1972",DATUM["D_WGS_1972




32661 UPS_North PROJCS["UPS_North",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["W
32662 WGS_1984_Plate_Carree PROJCS["WGS_1984_Plate_Carree",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",
32664 WGS_1984_BLM_Zone_14N_ftUS PROJCS["WGS_1984_BLM_Zone_14N_ftUS",GEOGCS["GCS_WGS_1984",DATUM["D_WG


32761 UPS_South PROJCS["UPS_South",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["W
32766 WGS_1984_TM_36_SE PROJCS["WGS_1984_TM_36_SE",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
53001 Sphere_Plate_Carree PROJCS["Sphere_Plate_Carree",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["
53002 Sphere_Equidistant_Cylindrical PROJCS["Sphere_Equidistant_Cylindrical",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPH
53003 Sphere_Miller_Cylindrical PROJCS["Sphere_Miller_Cylindrical",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHERO
53004 Sphere_Mercator PROJCS["Sphere_Mercator",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53008 Sphere_Sinusoidal PROJCS["Sphere_Sinusoidal",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sp
53009 Sphere_Mollweide PROJCS["Sphere_Mollweide",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53010 Sphere_Eckert_VI PROJCS["Sphere_Eckert_VI",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53011 Sphere_Eckert_V PROJCS["Sphere_Eckert_V",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53012 Sphere_Eckert_IV PROJCS["Sphere_Eckert_IV",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53013 Sphere_Eckert_III PROJCS["Sphere_Eckert_III",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53014 Sphere_Eckert_II PROJCS["Sphere_Eckert_II",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53015 Sphere_Eckert_I PROJCS["Sphere_Eckert_I",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sphe
53016 Sphere_Gall_Stereographic PROJCS["Sphere_Gall_Stereographic",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHER
53017 Sphere_Behrmann PROJCS["Sphere_Behrmann",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sp
53018 Sphere_Winkel_I PROJCS["Sphere_Winkel_I",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sphe
53019 Sphere_Winkel_II PROJCS["Sphere_Winkel_II",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53021 Sphere_Polyconic PROJCS["Sphere_Polyconic",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53022 Sphere_Quartic_Authalic PROJCS["Sphere_Quartic_Authalic",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHERO
53023 Sphere_Loximuthal PROJCS["Sphere_Loximuthal",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sp
53024 Sphere_Bonne PROJCS["Sphere_Bonne",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sphere
53025 Sphere_Hotine PROJCS["Sphere_Hotine",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sphere

53026 Sphere_Stereographic PROJCS["Sphere_Stereographic",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID[

53027 Sphere_Equidistant_Conic PROJCS["Sphere_Equidistant_Conic",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHERO
53028 Sphere_Cassini PROJCS["Sphere_Cassini",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Spher
53029 Sphere_Van_der_Grinten_I PROJCS["Sphere_Van_der_Grinten_I",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHER
53030 Sphere_Robinson PROJCS["Sphere_Robinson",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sph
53031 Sphere_Two_Point_Equidistant PROJCS["Sphere_Two_Point_Equidistant",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPH
53032 Sphere_Azimuthal_Equidistant PROJCS["Sphere_Azimuthal_Equidistant",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPH
53034 Sphere_Cylindrical_Equal_Area PROJCS["Sphere_Cylindrical_Equal_Area",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SP
53042 Sphere_Winkel_Tripel_NGS PROJCS["Sphere_Winkel_Tripel_NGS",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHER
53043 Sphere_Aitoff PROJCS["Sphere_Aitoff",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sphere"
53044 Sphere_Hammer_Aitoff PROJCS["Sphere_Hammer_Aitoff",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID
53045 Sphere_Flat_Polar_Quartic PROJCS["Sphere_Flat_Polar_Quartic",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHER
53046 Sphere_Craster_Parabolic PROJCS["Sphere_Craster_Parabolic",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHERO
53048 Sphere_Times PROJCS["Sphere_Times",GEOGCS["GCS_Sphere",DATUM["D_Sphere",SPHEROID["Sphere
53049 Sphere_Vertical_Perspective PROJCS["Sphere_Vertical_Perspective",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_198
53074 Sphere_Wagner_IV PROJCS["Sphere_Wagner_IV",GEOGCS["GCS_Sphere_GRS_1980_Authalic",DATUM["D_Sp
53075 Sphere_Wagner_V PROJCS["Sphere_Wagner_V",GEOGCS["GCS_Sphere_GRS_1980_Mean_Radius",DATUM["
53076 Sphere_Wagner_VII PROJCS["Sphere_Wagner_VII",GEOGCS["GCS_Sphere_GRS_1980_Authalic",DATUM["D_S
53077 Sphere_Natural_Earth PROJCS["Sphere_Natural_Earth",GEOGCS["GCS_Sphere_GRS_1980_Mean_Radius",DATU
53078 Sphere_Natural_Earth_II PROJCS["Sphere_Natural_Earth_II",GEOGCS["GCS_Sphere_GRS_1980_Mean_Radius",DA
53079 Sphere_Patterson PROJCS["Sphere_Patterson",GEOGCS["GCS_Sphere_GRS_1980_Mean_Radius",DATUM["D
53080 Sphere_Compact_Miller PROJCS["Sphere_Compact_Miller",GEOGCS["GCS_Sphere_GRS_1980_Mean_Radius",DAT
54001 World_Plate_Carree PROJCS["World_Plate_Carree",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHE
54002 World_Equidistant_Cylindrical PROJCS["World_Equidistant_Cylindrical",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_19
54003 World_Miller_Cylindrical PROJCS["World_Miller_Cylindrical",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
54004 World_Mercator PROJCS["World_Mercator",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROI
54008 World_Sinusoidal PROJCS["World_Sinusoidal",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54009 World_Mollweide PROJCS["World_Mollweide",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54010 World_Eckert_VI PROJCS["World_Eckert_VI",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54011 World_Eckert_V PROJCS["World_Eckert_V",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROI
54012 World_Eckert_IV PROJCS["World_Eckert_IV",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54013 World_Eckert_III PROJCS["World_Eckert_III",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54014 World_Eckert_II PROJCS["World_Eckert_II",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROI
54015 World_Eckert_I PROJCS["World_Eckert_I",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID
54016 World_Gall_Stereographic PROJCS["World_Gall_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984"
54017 World_Behrmann PROJCS["World_Behrmann",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54018 World_Winkel_I PROJCS["World_Winkel_I",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROI
54019 World_Winkel_II PROJCS["World_Winkel_II",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54021 World_Polyconic PROJCS["World_Polyconic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54022 World_Quartic_Authalic PROJCS["World_Quartic_Authalic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
54023 World_Loximuthal PROJCS["World_Loximuthal",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHER
54024 World_Bonne PROJCS["World_Bonne",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID[
54025 World_Hotine PROJCS["World_Hotine",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID[
54026 World_Stereographic PROJCS["World_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPH
54027 World_Equidistant_Conic PROJCS["World_Equidistant_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",S
54028 World_Cassini PROJCS["World_Cassini",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID
54029 World_Van_der_Grinten_I PROJCS["World_Van_der_Grinten_I",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",
54030 World_Robinson PROJCS["World_Robinson",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54031 World_Two_Point_Equidistant PROJCS["World_Two_Point_Equidistant",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_19
54032 World_Azimuthal_Equidistant PROJCS["World_Azimuthal_Equidistant",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_198
54034 World_Cylindrical_Equal_Area PROJCS["World_Cylindrical_Equal_Area",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_19
54042 World_Winkel_Tripel_NGS PROJCS["World_Winkel_Tripel_NGS",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984"
54043 World_Aitoff PROJCS["World_Aitoff",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["W
54044 World_Hammer_Aitoff PROJCS["World_Hammer_Aitoff",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPH

54045 World_Flat_Polar_Quartic PROJCS["World_Flat_Polar_Quartic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",

54046 World_Craster_Parabolic PROJCS["World_Craster_Parabolic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",S
54048 World_Times PROJCS["World_Times",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["
54049 World_Vertical_Perspective PROJCS["World_Vertical_Perspective",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984
54050 World_Fuller PROJCS["World_Fuller",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["
54051 World_Cube PROJCS["World_Cube",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["W
54052 World_Goode_Homolosine_Land PROJCS["World_Goode_Homolosine_Land",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_
54053 World_Goode_Homolosine_Ocean PROJCS["World_Goode_Homolosine_Ocean",GEOGCS["GCS_WGS_1984",DATUM["D_WGS
54074 World_Wagner_IV PROJCS["World_Wagner_IV",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHER
54075 World_Wagner_V PROJCS["World_Wagner_V",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54076 World_Wagner_VII PROJCS["World_Wagner_VII",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHER
54077 World_Natural_Earth PROJCS["World_Natural_Earth",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHE
54078 World_Natural_Earth_II PROJCS["World_Natural_Earth_II",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
54079 World_Patterson PROJCS["World_Patterson",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
54080 World_Compact_Miller PROJCS["World_Compact_Miller",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
65061 NAD_1927_StatePlane_Guam_FIPS_5400 PROJCS["NAD_1927_StatePlane_Guam_FIPS_5400",GEOGCS["GCS_North_American_192
65062 American_Samoa_1962_StatePlane_American_Samoa_FIPS_5300 PROJCS["American_Samoa_1962_StatePlane_American_Samoa_FIPS_5300",GEOGCS["GC
65161 NAD_1983_StatePlane_Guam_FIPS_5400 PROJCS["NAD_1983_StatePlane_Guam_FIPS_5400",GEOGCS["GCS_North_American_198
65163 NAD_1983_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_North_American_1
102001 Canada_Albers_Equal_Area_Conic PROJCS["Canada_Albers_Equal_Area_Conic",GEOGCS["GCS_North_American_1983",DATU
102002 Canada_Lambert_Conformal_Conic PROJCS["Canada_Lambert_Conformal_Conic",GEOGCS["GCS_North_American_1983",DAT
102003 USA_Contiguous_Albers_Equal_Area_Conic PROJCS["USA_Contiguous_Albers_Equal_Area_Conic",GEOGCS["GCS_North_American_19
102004 USA_Contiguous_Lambert_Conformal_Conic PROJCS["USA_Contiguous_Lambert_Conformal_Conic",GEOGCS["GCS_North_American_1
102005 USA_Contiguous_Equidistant_Conic PROJCS["USA_Contiguous_Equidistant_Conic",GEOGCS["GCS_North_American_1983",DAT
102006 NAD_1983_Alaska_Albers PROJCS["NAD_1983_Alaska_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_N
102007 Hawaii_Albers_Equal_Area_Conic PROJCS["Hawaii_Albers_Equal_Area_Conic",GEOGCS["GCS_North_American_1983",DATU
102008 North_America_Albers_Equal_Area_Conic PROJCS["North_America_Albers_Equal_Area_Conic",GEOGCS["GCS_North_American_1983
102009 North_America_Lambert_Conformal_Conic PROJCS["North_America_Lambert_Conformal_Conic",GEOGCS["GCS_North_American_198
102010 North_America_Equidistant_Conic PROJCS["North_America_Equidistant_Conic",GEOGCS["GCS_North_American_1983",DATU
102011 Africa_Sinusoidal PROJCS["Africa_Sinusoidal",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHERO
102012 Asia_Lambert_Conformal_Conic PROJCS["Asia_Lambert_Conformal_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_
102013 Europe_Albers_Equal_Area_Conic PROJCS["Europe_Albers_Equal_Area_Conic",GEOGCS["GCS_European_1950",DATUM["D_
102014 Europe_Lambert_Conformal_Conic PROJCS["Europe_Lambert_Conformal_Conic",GEOGCS["GCS_European_1950",DATUM["D_
102015 South_America_Lambert_Conformal_Conic PROJCS["South_America_Lambert_Conformal_Conic",GEOGCS["GCS_South_American_196
102016 North_Pole_Azimuthal_Equidistant PROJCS["North_Pole_Azimuthal_Equidistant",GEOGCS["GCS_WGS_1984",DATUM["D_WGS
102017 North_Pole_Lambert_Azimuthal_Equal_Area PROJCS["North_Pole_Lambert_Azimuthal_Equal_Area",GEOGCS["GCS_WGS_1984",DATUM
102018 North_Pole_Stereographic PROJCS["North_Pole_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984"
102019 South_Pole_Azimuthal_Equidistant PROJCS["South_Pole_Azimuthal_Equidistant",GEOGCS["GCS_WGS_1984",DATUM["D_WG
102020 South_Pole_Lambert_Azimuthal_Equal_Area PROJCS["South_Pole_Lambert_Azimuthal_Equal_Area",GEOGCS["GCS_WGS_1984",DATU
102021 South_Pole_Stereographic PROJCS["South_Pole_Stereographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984"
102022 Africa_Albers_Equal_Area_Conic PROJCS["Africa_Albers_Equal_Area_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS
102023 Africa_Equidistant_Conic PROJCS["Africa_Equidistant_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",S
102024 Africa_Lambert_Conformal_Conic PROJCS["Africa_Lambert_Conformal_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS
102025 Asia_North_Albers_Equal_Area_Conic PROJCS["Asia_North_Albers_Equal_Area_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_
102026 Asia_North_Equidistant_Conic PROJCS["Asia_North_Equidistant_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_19
102027 Asia_North_Lambert_Conformal_Conic PROJCS["Asia_North_Lambert_Conformal_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_
102028 Asia_South_Albers_Equal_Area_Conic PROJCS["Asia_South_Albers_Equal_Area_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_
102029 Asia_South_Equidistant_Conic PROJCS["Asia_South_Equidistant_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1
102030 Asia_South_Lambert_Conformal_Conic PROJCS["Asia_South_Lambert_Conformal_Conic",GEOGCS["GCS_WGS_1984",DATUM["D_
102031 Europe_Equidistant_Conic PROJCS["Europe_Equidistant_Conic",GEOGCS["GCS_European_1950",DATUM["D_Europea
102032 South_America_Equidistant_Conic PROJCS["South_America_Equidistant_Conic",GEOGCS["GCS_South_American_1969",DATU
102033 South_America_Albers_Equal_Area_Conic PROJCS["South_America_Albers_Equal_Area_Conic",GEOGCS["GCS_South_American_196
102034 North_Pole_Gnomonic PROJCS["North_Pole_Gnomonic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP
102035 North_Pole_Orthographic PROJCS["North_Pole_Orthographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",S

102036 South_Pole_Gnomonic PROJCS["South_Pole_Gnomonic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SP

102037 South_Pole_Orthographic PROJCS["South_Pole_Orthographic",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",
102038 The_World_From_Space PROJCS["The_World_From_Space",GEOGCS["GCS_Sphere_ARC_INFO",DATUM["D_Spher
102039 USA_Contiguous_Albers_Equal_Area_Conic_USGS_version PROJCS["USA_Contiguous_Albers_Equal_Area_Conic_USGS_version",GEOGCS["GCS_Nor
102040 Korean_1985_Korea_Unified_Coordinate_System PROJCS["Korean_1985_Korea_Unified_Coordinate_System",GEOGCS["GCS_Korean_Datum
102041 COB_NAD83_2007 PROJCS["COB_NAD83_2007",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_N
102042 NAD_1983_USFS_R9_Albers PROJCS["NAD_1983_USFS_R9_Albers",GEOGCS["GCS_North_American_1983",DATUM["D
102043 NAD_1983_CORS96_UTM_Zone_20N PROJCS["NAD_1983_CORS96_UTM_Zone_20N",GEOGCS["GCS_NAD_1983_CORS96",DA
102044 NAD_1983_NSRS2007_UTM_Zone_20N PROJCS["NAD_1983_NSRS2007_UTM_Zone_20N",GEOGCS["GCS_NAD_1983_NSRS2007
102045 NAD_1983_2011_UTM_Zone_20N PROJCS["NAD_1983_2011_UTM_Zone_20N",GEOGCS["GCS_NAD_1983_2011",DATUM["D
102048 NAD_1983_2011_UTM_Zone_1N PROJCS["NAD_1983_2011_UTM_Zone_1N",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
102060 D48_Slovenia_TM PROJCS["D48_Slovenia_TM",GEOGCS["GCS_D48",DATUM["D_D48",SPHEROID["Bessel_1
102061 Everest_Modified_1969_RSO_Malaya_Meters PROJCS["Everest_Modified_1969_RSO_Malaya_Meters",GEOGCS["GCS_Everest_Modified_
102062 Kertau_RSO_Malaya_Meters PROJCS["Kertau_RSO_Malaya_Meters",GEOGCS["GCS_Kertau",DATUM["D_Kertau",SPHER
102063 Kandawala_Ceylon_Belt_Meters PROJCS["Kandawala_Ceylon_Belt_Meters",GEOGCS["GCS_Kandawala",DATUM["D_Kandaw
102064 Kandawala_Ceylon_Belt_Indian_Yards_1937 PROJCS["Kandawala_Ceylon_Belt_Indian_Yards_1937",GEOGCS["GCS_Kandawala",DATUM
102065 S-JTSK_Krovak PROJCS["S-JTSK_Krovak",GEOGCS["GCS_S_JTSK",DATUM["D_S_JTSK",SPHEROID["Bes
102066 S-JTSK_Ferro_Krovak_East_North PROJCS["S-JTSK_Ferro_Krovak_East_North",GEOGCS["GCS_S_JTSK_Ferro",DATUM["D_S
102067 S-JTSK_Krovak_East_North PROJCS["S-JTSK_Krovak_East_North",GEOGCS["GCS_S_JTSK",DATUM["D_S_JTSK",SPH
102068 EMEP_50_Kilometer_Grid PROJCS["EMEP_50_Kilometer_Grid",GEOGCS["GCS_Sphere_EMEP",DATUM["D_Sphere_E
102069 EMEP_150_Kilometer_Grid PROJCS["EMEP_150_Kilometer_Grid",GEOGCS["GCS_Sphere_EMEP",DATUM["D_Sphere_
102070 Guernsey_Grid PROJCS["Guernsey_Grid",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID
102071 AGD_1966_ACT_Grid_AGC_Zone PROJCS["AGD_1966_ACT_Grid_AGC_Zone",GEOGCS["GCS_Australian_1966",DATUM["D_
102072 AGD_1966_ISG_54_2 PROJCS["AGD_1966_ISG_54_2",GEOGCS["GCS_Australian_1966",DATUM["D_Australian_1
102080 Korea_2000_Korea_Unified_Coordinate_System PROJCS["Korea_2000_Korea_Unified_Coordinate_System",GEOGCS["GCS_Korea_2000",D
102081 Korea_2000_Korea_West_Belt_2010 PROJCS["Korea_2000_Korea_West_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM["D_K
102082 Korea_2000_Korea_Central_Belt_2010 PROJCS["Korea_2000_Korea_Central_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM["D
102083 Korea_2000_Korea_East_Belt_2010 PROJCS["Korea_2000_Korea_East_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM["D_K
102084 Korea_2000_Korea_East_Sea_Belt_2010 PROJCS["Korea_2000_Korea_East_Sea_Belt_2010",GEOGCS["GCS_Korea_2000",DATUM[
102085 Korean_1985_Modified_Korea_West_Belt PROJCS["Korean_1985_Modified_Korea_West_Belt",GEOGCS["GCS_Korean_Datum_1985"
102086 Korean_1985_Modified_Korea_Central_Belt PROJCS["Korean_1985_Modified_Korea_Central_Belt",GEOGCS["GCS_Korean_Datum_198
102087 Korean_1985_Modified_Korea_Central_Belt_Jeju PROJCS["Korean_1985_Modified_Korea_Central_Belt_Jeju",GEOGCS["GCS_Korean_Datum
102088 Korean_1985_Modified_Korea_East_Belt PROJCS["Korean_1985_Modified_Korea_East_Belt",GEOGCS["GCS_Korean_Datum_1985",
102089 Korean_1985_Modified_Korea_East_Sea_Belt PROJCS["Korean_1985_Modified_Korea_East_Sea_Belt",GEOGCS["GCS_Korean_Datum_1

102090 Bermuda_2000_National_Grid PROJCS["Bermuda_2000_National_Grid",GEOGCS["GCS_Bermuda_2000",DATUM["D_Berm

102091 Monte_Mario_Italy_1 PROJCS["Monte_Mario_Italy_1",GEOGCS["GCS_Monte_Mario",DATUM["D_Monte_Mario",SP
102092 Monte_Mario_Italy_2 PROJCS["Monte_Mario_Italy_2",GEOGCS["GCS_Monte_Mario",DATUM["D_Monte_Mario",SP
102093 Roma_1940_Gauss_Boaga_Est PROJCS["Roma_1940_Gauss_Boaga_Est",GEOGCS["GCS_Roma_1940",DATUM["D_Roma
102094 Roma_1940_Gauss_Boaga_Ovest PROJCS["Roma_1940_Gauss_Boaga_Ovest",GEOGCS["GCS_Roma_1940",DATUM["D_Rom
102095 JAD_2001_Jamaica_Grid PROJCS["JAD_2001_Jamaica_Grid",GEOGCS["GCS_JAD_2001",DATUM["D_Jamaica_2001
102096 Bab_South_Palau_Azimuthal_Equidistant PROJCS["Bab_South_Palau_Azimuthal_Equidistant",GEOGCS["GCS_Bab_South",DATUM["D
102100 WGS_1984_Web_Mercator_Auxiliary_Sphere PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATU
102101 NGO_1948_Norway_Zone_1 PROJCS["NGO_1948_Norway_Zone_1",GEOGCS["GCS_NGO_1948",DATUM["D_NGO_194
102109 ETRS_1989_Slovenia_TM PROJCS["ETRS_1989_Slovenia_TM",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989
102110 RGF_1993_Lambert_93 PROJCS["RGF_1993_Lambert_93",GEOGCS["GCS_RGF_1993",DATUM["D_RGF_1993",SP
102111 Chatham_Islands_1979_Map_Grid PROJCS["Chatham_Islands_1979_Map_Grid",GEOGCS["GCS_Chatham_Islands_1979",DAT
102112 NZGD_2000_Chatham_Island_Circuit PROJCS["NZGD_2000_Chatham_Island_Circuit",GEOGCS["GCS_NZGD_2000",DATUM["D_
102113 WGS_1984_Web_Mercator PROJCS["WGS_1984_Web_Mercator",GEOGCS["GCS_WGS_1984_Major_Auxiliary_Sphere
102114 Old_Hawaiian_UTM_Zone_4N PROJCS["Old_Hawaiian_UTM_Zone_4N",GEOGCS["GCS_Old_Hawaiian",DATUM["D_Old_H
102115 Old_Hawaiian_UTM_Zone_5N PROJCS["Old_Hawaiian_UTM_Zone_5N",GEOGCS["GCS_Old_Hawaiian",DATUM["D_Old_H
102116 American_Samoa_1962_UTM_Zone_2S PROJCS["American_Samoa_1962_UTM_Zone_2S",GEOGCS["GCS_American_Samoa_1962
102117 NAD_1927_Alaska_Albers_Meters PROJCS["NAD_1927_Alaska_Albers_Meters",GEOGCS["GCS_North_American_1927",DATU
102118 NAD_1927_Georgia_Statewide_Albers PROJCS["NAD_1927_Georgia_Statewide_Albers",GEOGCS["GCS_North_American_1927",D
102119 NAD_1927_Texas_Statewide_Mapping_System PROJCS["NAD_1927_Texas_Statewide_Mapping_System",GEOGCS["GCS_North_American
102120 NAD_1927_Michigan_GeoRef_Feet_US PROJCS["NAD_1927_Michigan_GeoRef_Feet_US",GEOGCS["GCS_North_American_1927",
102121 NAD_1983_Michigan_GeoRef_Feet_US PROJCS["NAD_1983_Michigan_GeoRef_Feet_US",GEOGCS["GCS_North_American_1983",
102122 NAD_1927_Michigan_GeoRef_Meters PROJCS["NAD_1927_Michigan_GeoRef_Meters",GEOGCS["GCS_North_American_1927",DA
102123 NAD_1983_Michigan_GeoRef_Meters PROJCS["NAD_1983_Michigan_GeoRef_Meters",GEOGCS["GCS_North_American_1983",DA
102132 NGO_1948_UTM_Zone_32N PROJCS["NGO_1948_UTM_Zone_32N",GEOGCS["GCS_NGO_1948",DATUM["D_NGO_194
102136 NGO_1948_Baerum_Kommune PROJCS["NGO_1948_Baerum_Kommune",GEOGCS["GCS_NGO_1948",DATUM["D_NGO_1
102137 NGO_1948_Bergenhalvoen PROJCS["NGO_1948_Bergenhalvoen",GEOGCS["GCS_NGO_1948",DATUM["D_NGO_1948
102138 NGO_1948_Oslo_Kommune PROJCS["NGO_1948_Oslo_Kommune",GEOGCS["GCS_NGO_1948",DATUM["D_NGO_1948
102139 EUREF_FIN_TM35FIN PROJCS["EUREF_FIN_TM35FIN",GEOGCS["GCS_EUREF_FIN",DATUM["D_ETRS_1989",S
102140 Hong_Kong_1980_Grid PROJCS["Hong_Kong_1980_Grid",GEOGCS["GCS_Hong_Kong_1980",DATUM["D_Hong_Ko
102141 Hong_Kong_1980_UTM_Zone_49N PROJCS["Hong_Kong_1980_UTM_Zone_49N",GEOGCS["GCS_Hong_Kong_1980",DATUM[
102142 Hong_Kong_1980_UTM_Zone_50N PROJCS["Hong_Kong_1980_UTM_Zone_50N",GEOGCS["GCS_Hong_Kong_1980",DATUM[
102143 QND_1995_UTM_39N PROJCS["QND_1995_UTM_39N",GEOGCS["GCS_QND_1995",DATUM["D_QND_1995",SPH

102144 Merchich_Degree_UTM_Zone_28N PROJCS["Merchich_Degree_UTM_Zone_28N",GEOGCS["GCS_Merchich_Degree",DATUM["

102145 JGD_2000_UTM_Zone_51N PROJCS["JGD_2000_UTM_Zone_51N",GEOGCS["GCS_JGD_2000",DATUM["D_JGD_2000"
102151 Tokyo_UTM_Zone_51N PROJCS["Tokyo_UTM_Zone_51N",GEOGCS["GCS_Tokyo",DATUM["D_Tokyo",SPHEROID["B
102157 ETRS_1989_Kosovo_Grid PROJCS["ETRS_1989_Kosovo_Grid",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989
102158 Jordan_JTM PROJCS["Jordan_JTM",GEOGCS["GCS_Jordan",DATUM["D_Jordan",SPHEROID["Internation
102159 Observatorio_Meteorologico_1965_Macau_Grid PROJCS["Observatorio_Meteorologico_1965_Macau_Grid",GEOGCS["GCS_Observatorio_M
102160 Datum_73_Hayford_Gauss_IGeoE PROJCS["Datum_73_Hayford_Gauss_IGeoE",GEOGCS["GCS_Datum_73",DATUM["D_Datum
102161 Datum_73_Hayford_Gauss_IPCC PROJCS["Datum_73_Hayford_Gauss_IPCC",GEOGCS["GCS_Datum_73",DATUM["D_Datum
102162 Graciosa_Base_SW_1948_UTM_Zone_26N PROJCS["Graciosa_Base_SW_1948_UTM_Zone_26N",GEOGCS["GCS_Graciosa_Base_SW
102163 Lisboa_Bessel_Bonne PROJCS["Lisboa_Bessel_Bonne",GEOGCS["GCS_Datum_Lisboa_Bessel",DATUM["D_Datum
102164 Lisboa_Hayford_Gauss_IGeoE PROJCS["Lisboa_Hayford_Gauss_IGeoE",GEOGCS["GCS_Datum_Lisboa_Hayford",DATUM
102165 Lisboa_Hayford_Gauss_IPCC PROJCS["Lisboa_Hayford_Gauss_IPCC",GEOGCS["GCS_Datum_Lisboa_Hayford",DATUM["
102166 Observatorio_Meteorologico_1939_UTM_Zone_25N PROJCS["Observatorio_Meteorologico_1939_UTM_Zone_25N",GEOGCS["GCS_Observatori
102167 Porto_Santo_1936_UTM_Zone_28N PROJCS["Porto_Santo_1936_UTM_Zone_28N",GEOGCS["GCS_Porto_Santo_1936",DATUM
102168 Sao_Braz_UTM_Zone_26N PROJCS["Sao_Braz_UTM_Zone_26N",GEOGCS["GCS_Sao_Braz",DATUM["D_Sao_Braz",S
102169 Selvagem_Grande_1938_UTM_Zone_28N PROJCS["Selvagem_Grande_1938_UTM_Zone_28N",GEOGCS["GCS_Selvagem_Grande_1
102170 AGD_1966_VICGRID PROJCS["AGD_1966_VICGRID",GEOGCS["GCS_Australian_1966",DATUM["D_Australian_1
102171 GDA_1994_VICGRID94 PROJCS["GDA_1994_VICGRID94",GEOGCS["GCS_GDA_1994",DATUM["D_GDA_1994",SP
102172 GDA_1994_South_Australia_Lambert PROJCS["GDA_1994_South_Australia_Lambert",GEOGCS["GCS_GDA_1994",DATUM["D_G
102173 ETRS_1989_UWPP_1992 PROJCS["ETRS_1989_UWPP_1992",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989
102174 ETRS_1989_UWPP_2000_PAS_5 PROJCS["ETRS_1989_UWPP_2000_PAS_5",GEOGCS["GCS_ETRS_1989",DATUM["D_ETR
102178 NAD_1927_10TM_AEP_Forest PROJCS["NAD_1927_10TM_AEP_Forest",GEOGCS["GCS_North_American_1927",DATUM["
102179 NAD_1927_10TM_AEP_Resource PROJCS["NAD_1927_10TM_AEP_Resource",GEOGCS["GCS_North_American_1927",DATU
102180 NAD_1927_3TM_111 PROJCS["NAD_1927_3TM_111",GEOGCS["GCS_North_American_1927",DATUM["D_North_
102184 NAD_1983_10TM_AEP_Forest PROJCS["NAD_1983_10TM_AEP_Forest",GEOGCS["GCS_North_American_1983",DATUM["
102185 NAD_1983_10TM_AEP_Resource PROJCS["NAD_1983_10TM_AEP_Resource",GEOGCS["GCS_North_American_1983",DATU
102190 NAD_1983_BC_Environment_Albers PROJCS["NAD_1983_BC_Environment_Albers",GEOGCS["GCS_North_American_1983",DAT
102191 Nord_Maroc_Degree PROJCS["Nord_Maroc_Degree",GEOGCS["GCS_Merchich_Degree",DATUM["D_Merchich",S
102192 Sud_Maroc_Degree PROJCS["Sud_Maroc_Degree",GEOGCS["GCS_Merchich_Degree",DATUM["D_Merchich",SP
102193 Sahara_Degree PROJCS["Sahara_Degree",GEOGCS["GCS_Merchich_Degree",DATUM["D_Merchich",SPHER
102194 UWPP_1992 PROJCS["UWPP_1992",GEOGCS["GCS_ETRF_1989",DATUM["D_ETRF_1989",SPHEROID
102195 UWPP_2000_PAS_5 PROJCS["UWPP_2000_PAS_5",GEOGCS["GCS_ETRF_1989",DATUM["D_ETRF_1989",SPH


102199 Belge_Lambert_2008 PROJCS["Belge_Lambert_2008",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SP
102200 NAD_1983_HARN_UTM_Zone_2S PROJCS["NAD_1983_HARN_UTM_Zone_2S",GEOGCS["GCS_North_American_1983_HARN
102201 NAD_1983_HARN_Guam_Map_Grid PROJCS["NAD_1983_HARN_Guam_Map_Grid",GEOGCS["GCS_North_American_1983_HA
102202 NAD_1983_HARN_UTM_Zone_4N PROJCS["NAD_1983_HARN_UTM_Zone_4N",GEOGCS["GCS_North_American_1983_HARN
102203 NAD_1983_HARN_UTM_Zone_5N PROJCS["NAD_1983_HARN_UTM_Zone_5N",GEOGCS["GCS_North_American_1983_HARN
102204 Ain_el_Abd_1970_Aramco_Lambert_2 PROJCS["Ain_el_Abd_1970_Aramco_Lambert_2",GEOGCS["GCS_Ain_el_Abd_1970",DATUM
102205 NAD_1983_HARN_UTM_Zone_11N PROJCS["NAD_1983_HARN_UTM_Zone_11N",GEOGCS["GCS_North_American_1983_HAR
102208 NAD_1983_HARN_Maine_2000_East_Zone PROJCS["NAD_1983_HARN_Maine_2000_East_Zone",GEOGCS["GCS_North_American_19
102209 NAD_1983_HARN_Maine_2000_Central_Zone PROJCS["NAD_1983_HARN_Maine_2000_Central_Zone",GEOGCS["GCS_North_American_
102210 NAD_1983_HARN_Maine_2000_West_Zone PROJCS["NAD_1983_HARN_Maine_2000_West_Zone",GEOGCS["GCS_North_American_19
102212 NAD_1983_WyLAM PROJCS["NAD_1983_WyLAM",GEOGCS["GCS_North_American_1983",DATUM["D_North_A
102214 WGS_1984_Cape_Verde_Grid PROJCS["WGS_1984_Cape_Verde_Grid",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1
102215 WGS_1984_Canada_Atlas_LCC PROJCS["WGS_1984_Canada_Atlas_LCC",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_
102216 GDA_1994_Perth_Coastal_Grid_1994 PROJCS["GDA_1994_Perth_Coastal_Grid_1994",GEOGCS["GCS_GDA_1994",DATUM["D_G
102217 NAD_1983_NSRS2007_Wisconsin_TM_US_Ft PROJCS["NAD_1983_NSRS2007_Wisconsin_TM_US_Ft",GEOGCS["GCS_NAD_1983_NSR
102218 NAD_1983_USFS_R6_Albers PROJCS["NAD_1983_USFS_R6_Albers",GEOGCS["GCS_North_American_1983",DATUM["D
102219 NAD_1983_Wisconsin_TM_US_Ft PROJCS["NAD_1983_Wisconsin_TM_US_Ft",GEOGCS["GCS_North_American_1983",DATU
102220 NAD_1983_HARN_Wisconsin_TM_US_Ft PROJCS["NAD_1983_HARN_Wisconsin_TM_US_Ft",GEOGCS["GCS_North_American_1983
102221 Ocotepeque_1935_Costa_Rica_Lambert_Norte PROJCS["Ocotepeque_1935_Costa_Rica_Lambert_Norte",GEOGCS["GCS_Ocotepeque_193
102222 Ocotepeque_1935_Costa_Rica_Lambert_Sur PROJCS["Ocotepeque_1935_Costa_Rica_Lambert_Sur",GEOGCS["GCS_Ocotepeque_1935
102223 WGS_1984_Costa_Rica_TM_90 PROJCS["WGS_1984_Costa_Rica_TM_90",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_
102224 MONREF_1997_UTM_Zone_46N PROJCS["MONREF_1997_UTM_Zone_46N",GEOGCS["GCS_MONREF_1997",DATUM["D_I
102229 NAD_1983_HARN_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1983_HARN_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_North
102230 NAD_1983_HARN_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1983_HARN_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_Nort
102231 Colombia_West_West_Zone PROJCS["Colombia_West_West_Zone",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHER
102232 Bogota_Ciudad_Bogota PROJCS["Bogota_Ciudad_Bogota",GEOGCS["GCS_Bogota",DATUM["D_Bogota",SPHEROID
102233 MAGNA_Ciudad_Bogota PROJCS["MAGNA_Ciudad_Bogota",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHER
102234 NAD_1983_CSRS_UTM_Zone_14N PROJCS["NAD_1983_CSRS_UTM_Zone_14N",GEOGCS["GCS_North_American_1983_CSR
102237 Pohnpei_Az_Eq_1971 PROJCS["Pohnpei_Az_Eq_1971",GEOGCS["GCS_Pohnpei",DATUM["D_Pohnpei",SPHEROI
102238 Saipan_Az_Eq_1969 PROJCS["Saipan_Az_Eq_1969",GEOGCS["GCS_Guam_1963",DATUM["D_Guam_1963",SPH
102239 Guam_Geodetic_Triangulation_Network_1963 PROJCS["Guam_Geodetic_Triangulation_Network_1963",GEOGCS["GCS_Guam_1963",DAT
102240 Guam_Geodetic_Network_1993 PROJCS["Guam_Geodetic_Network_1993",GEOGCS["GCS_North_American_1983_HARN",D
102241 NAD_1983_HARN_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1983_HARN_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_North_A
102242 NAD_1983_HARN_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1983_HARN_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_North_A
102243 NAD_1983_HARN_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1983_HARN_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_North_
102244 NAD_1983_HARN_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1983_HARN_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_North_
102245 NAD_1983_HARN_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1983_HARN_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_North_A
102246 NAD_1983_HARN_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1983_HARN_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_North_
102247 NAD_1983_CORS96_Alaska_Albers PROJCS["NAD_1983_CORS96_Alaska_Albers",GEOGCS["GCS_NAD_1983_CORS96",DATU
102248 NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_North_
102249 NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_Nor
102250 NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_North
102251 NAD_1983_HARN_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1983_HARN_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_Nor

102252 NAD_1983_HARN_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1983_HARN_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_No

102253 NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_Nor
102254 NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_No
102255 NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_Nor
102256 NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_North_A
102257 NAD_1983_HARN_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1983_HARN_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_North_Am
102258 NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_North_
102259 NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_North_
102260 NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_North_
102261 NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101 PROJCS["NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101",GEOGCS["GCS_North_Am
102266 NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_North_
102267 NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_North
102268 NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_North_A
102269 NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_North
102270 NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_North_A
102271 NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_North_A
102272 NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_North_
102273 NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_North_
102274 NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_North_
102275 NAD_1983_HARN_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1983_HARN_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_North_A
102276 NAD_1983_HARN_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1983_HARN_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_North_A
102277 NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_North
102278 NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_North
102279 NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_Nor
102280 NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_Nor
102281 NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_Nor
102282 NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_No
102283 NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_North_A
102284 NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_North_A
102285 NAD_1983_HARN_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1983_HARN_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_North_Am
102286 NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS["G
102287 NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["GC
102288 NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_Nort
102289 NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_No
102290 NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_Nor
102291 NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_No
102292 NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS_N
102293 NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_No
102294 NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_No
102295 NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_No
102296 NAD_1983_HARN_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1983_HARN_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_North
102297 NAD_1983_HARN_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1983_HARN_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_No
102298 NAD_1983_HARN_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1983_HARN_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_North
102299 Berghaus_Star_AAG PROJCS["Berghaus_Star_AAG",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHE
102300 NAD_1983_HARN_StatePlane_Montana_FIPS_2500 PROJCS["NAD_1983_HARN_StatePlane_Montana_FIPS_2500",GEOGCS["GCS_North_Ame
102304 NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600 PROJCS["NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600",GEOGCS["GCS_North_Am
102305 CRTM05 PROJCS["CRTM05",GEOGCS["GCS_CR05",DATUM["D_Costa_Rica_2005",SPHEROID["WG
102306 Nepal_Nagarkot_TM PROJCS["Nepal_Nagarkot_TM",GEOGCS["GCS_Nepal_Nagarkot",DATUM["D_Nepal_Nagark
102307 NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_North_
102308 NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_Nor

102309 NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_North

102310 NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_No
102311 NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_North_A
102312 NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS_N
102313 NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["GCS
102314 NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS_N
102315 NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_Nor
102316 NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS_N
102317 NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_No
102318 NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GC
102319 CGRS_1993_LTM PROJCS["CGRS_1993_LTM",GEOGCS["GCS_CGRS_1993",DATUM["D_Cyprus_Geodetic_R
102320 NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GCS
102321 NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GCS
102322 NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_North_A
102323 NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_North_A
102324 NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_No
102325 NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_No
102326 NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_North
102327 NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_North
102328 ETRS_1989_UTM_Zone_32N_7stellen PROJCS["ETRS_1989_UTM_Zone_32N_7stellen",GEOGCS["GCS_ETRS_1989",DATUM["D_
102330 NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_North
102331 PTRA08_UTM_Zone_25N PROJCS["PTRA08_UTM_Zone_25N",GEOGCS["GCS_PTRA08",DATUM["D_PTRA08",SPHE
102334 NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GCS
102335 NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["GCS
102336 NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_North_Am
102337 NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_North_
102338 NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["GCS
102339 NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_North
102340 NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["GCS
102341 NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_North_
102342 NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_North_A
102343 NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_North_
102344 NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_North_A
102345 NAD_1983_HARN_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1983_HARN_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_North_Ame
102346 NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_North
102347 NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_North
102348 NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS_N
102349 NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS_N
102350 NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GCS_
102351 NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GCS
102352 NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_No
102353 NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS_N
102354 NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_No
102355 NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_Nort
102356 NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS["GC
102357 NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS["G
102358 NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_Nor
102361 NAD_1983_HARN_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200 PROJCS["NAD_1983_HARN_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200",GEOGCS
102362 ETRS_1989_UTM_Zone_N32 PROJCS["ETRS_1989_UTM_Zone_N32",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1

102363 NAD_1983_HARN_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_HARN_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_North_Am

102366 NAD_1983_CORS96_StatePlane_Alaska_1_FIPS_5001 PROJCS["NAD_1983_CORS96_StatePlane_Alaska_1_FIPS_5001",GEOGCS["GCS_NAD_19
102376 NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_NA
102377 NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_NA
102378 NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Oregon_North_FIPS_3601_Ft_Intl",GEOGCS["G
102379 NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Oregon_South_FIPS_3602_Ft_Intl",GEOGCS["G
102380 NAD_1983_CORS96_Oregon_Statewide_Lambert PROJCS["NAD_1983_CORS96_Oregon_Statewide_Lambert",GEOGCS["GCS_NAD_1983_C
102381 NAD_1983_CORS96_Oregon_Statewide_Lambert_Ft_Intl PROJCS["NAD_1983_CORS96_Oregon_Statewide_Lambert_Ft_Intl",GEOGCS["GCS_NAD_
102389 NAD_1983_Fargo_Ground_Coordinate_System PROJCS["NAD_1983_Fargo_Ground_Coordinate_System",GEOGCS["GCS_North_American
102390 NAD_1983_HARN_Fargo_Ground_Coordinate_System PROJCS["NAD_1983_HARN_Fargo_Ground_Coordinate_System",GEOGCS["GCS_North_Am
102391 NAD_1983_2011_Fargo_Ground_Coordinate_System PROJCS["NAD_1983_2011_Fargo_Ground_Coordinate_System",GEOGCS["GCS_NAD_1983
102392 NAD_1983_2011_StatePlane_Alaska_4_FIPS_5004_Feet PROJCS["NAD_1983_2011_StatePlane_Alaska_4_FIPS_5004_Feet",GEOGCS["GCS_NAD_
102398 NAD_1983_2011_StatePlane_Alaska_10_FIPS_5010_Feet PROJCS["NAD_1983_2011_StatePlane_Alaska_10_FIPS_5010_Feet",GEOGCS["GCS_NAD
102399 NAD_1983_Albers_BLM_MT_ND_SD PROJCS["NAD_1983_Albers_BLM_MT_ND_SD",GEOGCS["GCS_North_American_1983",DA
102400 London_Survey_Grid PROJCS["London_Survey_Grid",GEOGCS["GCS_Xrail84",DATUM["D_Xrail84",SPHEROID["W
102401 NAD_1983_CORS96_UTM_Zone_1N PROJCS["NAD_1983_CORS96_UTM_Zone_1N",GEOGCS["GCS_NAD_1983_CORS96",DAT


102420 ISN_2004_Lambert_2004 PROJCS["ISN_2004_Lambert_2004",GEOGCS["GCS_ISN_2004",DATUM["D_Islands_Netwo
102421 WGS_1984_ARC_System_Zone_01 PROJCS["WGS_1984_ARC_System_Zone_01",GEOGCS["GCS_WGS_1984",DATUM["D_WG
102439 WGS_1984_Australian_Centre_for_Remote_Sensing_Lambert PROJCS["WGS_1984_Australian_Centre_for_Remote_Sensing_Lambert",GEOGCS["GCS_W
102440 LKS_1992_Latvia_TM_0 PROJCS["LKS_1992_Latvia_TM_0",GEOGCS["GCS_LKS_1992",DATUM["D_Latvia_1992",S
102441 TWD_1967_TM_Taiwan PROJCS["TWD_1967_TM_Taiwan",GEOGCS["GCS_TWD_1967",DATUM["D_TWD_1967",SP
102442 TWD_1967_TM_Penghu PROJCS["TWD_1967_TM_Penghu",GEOGCS["GCS_TWD_1967",DATUM["D_TWD_1967",S
102443 TWD_1997_TM_Taiwan PROJCS["TWD_1997_TM_Taiwan",GEOGCS["GCS_TWD_1997",DATUM["D_TWD_1997",SP
102444 TWD_1997_TM_Penghu PROJCS["TWD_1997_TM_Penghu",GEOGCS["GCS_TWD_1997",DATUM["D_TWD_1997",S
102448 Macao_2008_Macao_Grid PROJCS["Macao_2008_Macao_Grid",GEOGCS["GCS_MACAO_2008",DATUM["D_MACAO_
102449 NAD_1983_MA11_UTM_Zone_55N PROJCS["NAD_1983_MA11_UTM_Zone_55N",GEOGCS["GCS_NAD_1983_MA11",DATUM["
102450 NGO_1948_Oslo_Baerum_Kommune PROJCS["NGO_1948_Oslo_Baerum_Kommune",GEOGCS["GCS_NGO_1948_Oslo",DATUM
102451 NGO_1948_Oslo_Bergenhalvoen PROJCS["NGO_1948_Oslo_Bergenhalvoen",GEOGCS["GCS_NGO_1948_Oslo",DATUM["D_
102452 NGO_1948_Oslo_Oslo_Kommune PROJCS["NGO_1948_Oslo_Oslo_Kommune",GEOGCS["GCS_NGO_1948_Oslo",DATUM["D
102453 Luzon_1911_UTM_Zone_50N PROJCS["Luzon_1911_UTM_Zone_50N",GEOGCS["GCS_Luzon_1911",DATUM["D_Luzon_1
102456 PRS_1992_UTM_Zone_50N PROJCS["PRS_1992_UTM_Zone_50N",GEOGCS["GCS_PRS_1992",DATUM["D_Philippine_
102459 NAD_1983_Idaho-Ada_County PROJCS["NAD_1983_Idaho-Ada_County",GEOGCS["GCS_North_American_1983",DATUM["
102460 HJAIA_AirportGrid_2Mar10 PROJCS["HJAIA_AirportGrid_2Mar10",GEOGCS["GCS_North_American_1983",DATUM["D_N
102461 NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101_Feet PROJCS["NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101_Feet",GEOGCS["GCS_North
102466 NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201_Feet PROJCS["NAD_1983_HARN_StatePlane_Minnesota_North_FIPS_2201_Feet",GEOGCS["GC
102467 NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202_Feet PROJCS["NAD_1983_HARN_StatePlane_Minnesota_Central_FIPS_2202_Feet",GEOGCS["G
102468 NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203_Feet PROJCS["NAD_1983_HARN_StatePlane_Minnesota_South_FIPS_2203_Feet",GEOGCS["GC
102469 NAD_1983_HARN_Mississippi_TM PROJCS["NAD_1983_HARN_Mississippi_TM",GEOGCS["GCS_North_American_1983_HARN
102470 Cape_Lo15 PROJCS["Cape_Lo15",GEOGCS["GCS_Cape",DATUM["D_Cape",SPHEROID["Clarke_1880_


102480 Hartebeesthoek94_Lo15 PROJCS["Hartebeesthoek94_Lo15",GEOGCS["GCS_Hartebeesthoek_1994",DATUM["D_Har
102490 GDBD2009_GEORSO PROJCS["GDBD2009_GEORSO",GEOGCS["GCS_GDBD2009",DATUM["D_GDBD2009",SPH
102491 Nord_Algerie_Ancienne_Degree PROJCS["Nord_Algerie_Ancienne_Degree",GEOGCS["GCS_Voirol_1875",DATUM["D_Voirol_
102492 Sud_Algerie_Ancienne_Degree PROJCS["Sud_Algerie_Ancienne_Degree",GEOGCS["GCS_Voirol_1875",DATUM["D_Voirol_1
102493 NAD_1983_PA11_UTM_Zone_4N PROJCS["NAD_1983_PA11_UTM_Zone_4N",GEOGCS["GCS_NAD_1983_PA11",DATUM["D_
102494 NAD_1983_PA11_UTM_Zone_5N PROJCS["NAD_1983_PA11_UTM_Zone_5N",GEOGCS["GCS_NAD_1983_PA11",DATUM["D_
102495 NAD_1983_MA11_Guam_Map_Grid PROJCS["NAD_1983_MA11_Guam_Map_Grid",GEOGCS["GCS_NAD_1983_MA11",DATUM[
102496 NAD_1983_PA11_UTM_Zone_2S PROJCS["NAD_1983_PA11_UTM_Zone_2S",GEOGCS["GCS_NAD_1983_PA11",DATUM["D_
102500 OCRS_Baker_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Baker_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_C
102501 OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS["GCS_NAD_1
102502 OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_
102503 OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS
102504 OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["
102505 OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS["GC
102506 OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Feet_Intl PROJCS["OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Feet_Intl",GEOGCS["GC
102507 OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS
102508 OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_
102509 OCRS_Eugene_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Eugene_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_
102510 OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS
102511 OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["G
102512 OCRS_La_Grande_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_La_Grande_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_19
102513 OCRS_Ontario_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Ontario_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_
102514 OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Feet_Intl PROJCS["OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Feet_Intl",GEOGCS["GCS_NAD
102515 OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GC
102516 OCRS_Pendleton_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Pendleton_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_198
102517 OCRS_Portland_NAD_1983_CORS96_LCC_Feet_Intl PROJCS["OCRS_Portland_NAD_1983_CORS96_LCC_Feet_Intl",GEOGCS["GCS_NAD_198
102518 OCRS_Salem_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Salem_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD_1983_C
102519 OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Feet_Intl PROJCS["OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Feet_Intl",GEOGCS["GCS_NAD
102520 NAD_1983_PA11_StatePlane_Hawaii_1_FIPS_5101 PROJCS["NAD_1983_PA11_StatePlane_Hawaii_1_FIPS_5101",GEOGCS["GCS_NAD_1983_
102525 NAD_1983_PA11_StatePlane_Hawaii_1_FIPS_5101_Feet PROJCS["NAD_1983_PA11_StatePlane_Hawaii_1_FIPS_5101_Feet",GEOGCS["GCS_NAD_


102530 OCRS_Baker_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Baker_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CO
102531 OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Bend-Burns_NAD_1983_CORS96_LCC_Meters",GEOGCS["GCS_NAD_19
102532 OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Bend-Klamath_Falls_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_N
102533 OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Bend-Redmond-Prineville_NAD_1983_CORS96_LCC_Meters",GEOGCS["G
102534 OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Canyonville-Grants_Pass_NAD_1983_CORS96_TM_Meters",GEOGCS["GC
102535 OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Columbia_River_East_NAD_1983_CORS96_LCC_Meters",GEOGCS["GCS
102536 OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Meters PROJCS["OCRS_Columbia_River_West_NAD_1983_CORS96_OM_Meters",GEOGCS["GCS
102537 OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Cottage_Grove-Canyonville_NAD_1983_CORS96_TM_Meters",GEOGCS["
102538 OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Dufur-Madras_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_19
102539 OCRS_Eugene_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Eugene_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_C
102540 OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Grants_Pass-Ashland_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_
102541 OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Gresham-Warm_Springs_NAD_1983_CORS96_TM_Meters",GEOGCS["GC
102542 OCRS_La_Grande_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_La_Grande_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983
102543 OCRS_Ontario_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Ontario_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_C
102544 OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Meters PROJCS["OCRS_Oregon_Coast_NAD_1983_CORS96_OM_Meters",GEOGCS["GCS_NAD_1
102545 OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Pendleton-La_Grande_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_
102546 OCRS_Pendleton_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Pendleton_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983
102547 OCRS_Portland_NAD_1983_CORS96_LCC_Meters PROJCS["OCRS_Portland_NAD_1983_CORS96_LCC_Meters",GEOGCS["GCS_NAD_1983_
102548 OCRS_Salem_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Salem_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1983_CO
102549 OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Meters PROJCS["OCRS_Santiam_Pass_NAD_1983_CORS96_TM_Meters",GEOGCS["GCS_NAD_1
102550 ED_1950_Turkey_9 PROJCS["ED_1950_Turkey_9",GEOGCS["GCS_European_1950",DATUM["D_European_195
102557 Kyrg-06_TM_Zone_1 PROJCS["Kyrg-06_TM_Zone_1",GEOGCS["GCS_Kyrg-06",DATUM["D_Kyrgyz_Republic_200
102570 WGS_1984_Complex_UTM_Zone_20N PROJCS["WGS_1984_Complex_UTM_Zone_20N",GEOGCS["GCS_WGS_1984",DATUM["D_
102581 NTF_France_I_degrees PROJCS["NTF_France_I_degrees",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Cla
102582 NTF_France_II_degrees PROJCS["NTF_France_II_degrees",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Cla
102583 NTF_France_III_degrees PROJCS["NTF_France_III_degrees",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Cl
102584 NTF_France_IV_degrees PROJCS["NTF_France_IV_degrees",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Cl
102585 NTF_Lambert_Zone_I PROJCS["NTF_Lambert_Zone_I",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Clark
102586 NTF_Lambert_Zone_II PROJCS["NTF_Lambert_Zone_II",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Clark
102587 NTF_Lambert_Zone_III PROJCS["NTF_Lambert_Zone_III",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Clar
102588 NTF_Lambert_Zone_IV PROJCS["NTF_Lambert_Zone_IV",GEOGCS["GCS_NTF",DATUM["D_NTF",SPHEROID["Clar
102589 Panhandle_Energy_Albers PROJCS["Panhandle_Energy_Albers",GEOGCS["GCS_North_American_1983",DATUM["D_N

102590 Tananarive_1925_Laborde_Grid PROJCS["Tananarive_1925_Laborde_Grid",GEOGCS["GCS_Tananarive_1925",DATUM["D_T

102591 Nord_Algerie_Degree PROJCS["Nord_Algerie_Degree",GEOGCS["GCS_Voirol_Unifie_1960_Degree",DATUM["D_V
102592 Sud_Algerie_Degree PROJCS["Sud_Algerie_Degree",GEOGCS["GCS_Voirol_Unifie_1960_Degree",DATUM["D_Vo
102599 WGS_1984_California_Teale_Albers_FtUS PROJCS["WGS_1984_California_Teale_Albers_FtUS",GEOGCS["GCS_WGS_1984",DATUM[
102600 NAD_1983_California_Teale_Albers_FtUS PROJCS["NAD_1983_California_Teale_Albers_FtUS",GEOGCS["GCS_North_American_1983
102601 NAD_1983_Texas_Centric_Mapping_System_Albers PROJCS["NAD_1983_Texas_Centric_Mapping_System_Albers",GEOGCS["GCS_North_Ame
102602 NAD_1983_Texas_Centric_Mapping_System_Lambert PROJCS["NAD_1983_Texas_Centric_Mapping_System_Lambert",GEOGCS["GCS_North_Am
102603 NAD_1983_Texas_Statewide_Mapping_System PROJCS["NAD_1983_Texas_Statewide_Mapping_System",GEOGCS["GCS_North_American
102604 NAD_1983_Georgia_Statewide_Lambert PROJCS["NAD_1983_Georgia_Statewide_Lambert",GEOGCS["GCS_North_American_1983"
102605 NAD_1983_Idaho_TM PROJCS["NAD_1983_Idaho_TM",GEOGCS["GCS_North_American_1983",DATUM["D_North
102606 NAD_1983_Maine_2000_East_Zone PROJCS["NAD_1983_Maine_2000_East_Zone",GEOGCS["GCS_North_American_1983",DAT
102607 NAD_1983_Maine_2000_Central_Zone PROJCS["NAD_1983_Maine_2000_Central_Zone",GEOGCS["GCS_North_American_1983",D
102608 NAD_1983_Maine_2000_West_Zone PROJCS["NAD_1983_Maine_2000_West_Zone",GEOGCS["GCS_North_American_1983",DA
102609 NAD_1983_Mississippi_TM PROJCS["NAD_1983_Mississippi_TM",GEOGCS["GCS_North_American_1983",DATUM["D_N
102610 JGD_2011_Japan_Zone_1 PROJCS["JGD_2011_Japan_Zone_1",GEOGCS["GCS_JGD_2011",DATUM["D_JGD_2011",S
102619 JGD_2011_Japan_Zone_10 PROJCS["JGD_2011_Japan_Zone_10",GEOGCS["GCS_JGD_2011",DATUM["D_JGD_2011",
102629 NAD_1983_StatePlane_Alabama_East_FIPS_0101_Feet PROJCS["NAD_1983_StatePlane_Alabama_East_FIPS_0101_Feet",GEOGCS["GCS_North_
102630 NAD_1983_StatePlane_Alabama_West_FIPS_0102_Feet PROJCS["NAD_1983_StatePlane_Alabama_West_FIPS_0102_Feet",GEOGCS["GCS_North_
102631 NAD_1983_StatePlane_Alaska_1_FIPS_5001_Feet PROJCS["NAD_1983_StatePlane_Alaska_1_FIPS_5001_Feet",GEOGCS["GCS_North_Amer
102640 NAD_1983_StatePlane_Alaska_10_FIPS_5010_Feet PROJCS["NAD_1983_StatePlane_Alaska_10_FIPS_5010_Feet",GEOGCS["GCS_North_Ame
102641 NAD_1983_StatePlane_California_I_FIPS_0401_Feet PROJCS["NAD_1983_StatePlane_California_I_FIPS_0401_Feet",GEOGCS["GCS_North_Am
102642 NAD_1983_StatePlane_California_II_FIPS_0402_Feet PROJCS["NAD_1983_StatePlane_California_II_FIPS_0402_Feet",GEOGCS["GCS_North_Am
102643 NAD_1983_StatePlane_California_III_FIPS_0403_Feet PROJCS["NAD_1983_StatePlane_California_III_FIPS_0403_Feet",GEOGCS["GCS_North_Am

102644 NAD_1983_StatePlane_California_IV_FIPS_0404_Feet PROJCS["NAD_1983_StatePlane_California_IV_FIPS_0404_Feet",GEOGCS["GCS_North_Am

102645 NAD_1983_StatePlane_California_V_FIPS_0405_Feet PROJCS["NAD_1983_StatePlane_California_V_FIPS_0405_Feet",GEOGCS["GCS_North_Am
102646 NAD_1983_StatePlane_California_VI_FIPS_0406_Feet PROJCS["NAD_1983_StatePlane_California_VI_FIPS_0406_Feet",GEOGCS["GCS_North_Am
102647 NAD_1983_NSRS2007_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200 PROJCS["NAD_1983_NSRS2007_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200",GEOGC
102648 NAD_1983_StatePlane_Arizona_East_FIPS_0201_Feet PROJCS["NAD_1983_StatePlane_Arizona_East_FIPS_0201_Feet",GEOGCS["GCS_North_A
102649 NAD_1983_StatePlane_Arizona_Central_FIPS_0202_Feet PROJCS["NAD_1983_StatePlane_Arizona_Central_FIPS_0202_Feet",GEOGCS["GCS_North
102650 NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet PROJCS["NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet",GEOGCS["GCS_North_A
102651 NAD_1983_StatePlane_Arkansas_North_FIPS_0301_Feet PROJCS["NAD_1983_StatePlane_Arkansas_North_FIPS_0301_Feet",GEOGCS["GCS_North
102652 NAD_1983_StatePlane_Arkansas_South_FIPS_0302_Feet PROJCS["NAD_1983_StatePlane_Arkansas_South_FIPS_0302_Feet",GEOGCS["GCS_North
102653 NAD_1983_StatePlane_Colorado_North_FIPS_0501_Feet PROJCS["NAD_1983_StatePlane_Colorado_North_FIPS_0501_Feet",GEOGCS["GCS_North
102654 NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet PROJCS["NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet",GEOGCS["GCS_Nor
102655 NAD_1983_StatePlane_Colorado_South_FIPS_0503_Feet PROJCS["NAD_1983_StatePlane_Colorado_South_FIPS_0503_Feet",GEOGCS["GCS_North
102656 NAD_1983_StatePlane_Connecticut_FIPS_0600_Feet PROJCS["NAD_1983_StatePlane_Connecticut_FIPS_0600_Feet",GEOGCS["GCS_North_Am
102657 NAD_1983_StatePlane_Delaware_FIPS_0700_Feet PROJCS["NAD_1983_StatePlane_Delaware_FIPS_0700_Feet",GEOGCS["GCS_North_Amer
102658 NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet PROJCS["NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet",GEOGCS["GCS_North_Am
102659 NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet PROJCS["NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet",GEOGCS["GCS_North_A
102660 NAD_1983_StatePlane_Florida_North_FIPS_0903_Feet PROJCS["NAD_1983_StatePlane_Florida_North_FIPS_0903_Feet",GEOGCS["GCS_North_A
102661 NAD_1983_StatePlane_Hawaii_1_FIPS_5101_Feet PROJCS["NAD_1983_StatePlane_Hawaii_1_FIPS_5101_Feet",GEOGCS["GCS_North_Amer
102666 NAD_1983_StatePlane_Georgia_East_FIPS_1001_Feet PROJCS["NAD_1983_StatePlane_Georgia_East_FIPS_1001_Feet",GEOGCS["GCS_North_A
102667 NAD_1983_StatePlane_Georgia_West_FIPS_1002_Feet PROJCS["NAD_1983_StatePlane_Georgia_West_FIPS_1002_Feet",GEOGCS["GCS_North_A
102668 NAD_1983_StatePlane_Idaho_East_FIPS_1101_Feet PROJCS["NAD_1983_StatePlane_Idaho_East_FIPS_1101_Feet",GEOGCS["GCS_North_Am
102669 NAD_1983_StatePlane_Idaho_Central_FIPS_1102_Feet PROJCS["NAD_1983_StatePlane_Idaho_Central_FIPS_1102_Feet",GEOGCS["GCS_North_A
102670 NAD_1983_StatePlane_Idaho_West_FIPS_1103_Feet PROJCS["NAD_1983_StatePlane_Idaho_West_FIPS_1103_Feet",GEOGCS["GCS_North_Am
102671 NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet PROJCS["NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet",GEOGCS["GCS_North_Am
102672 NAD_1983_StatePlane_Illinois_West_FIPS_1202_Feet PROJCS["NAD_1983_StatePlane_Illinois_West_FIPS_1202_Feet",GEOGCS["GCS_North_Am
102673 NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet PROJCS["NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet",GEOGCS["GCS_North_A
102674 NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet PROJCS["NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet",GEOGCS["GCS_North_A
102675 NAD_1983_StatePlane_Iowa_North_FIPS_1401_Feet PROJCS["NAD_1983_StatePlane_Iowa_North_FIPS_1401_Feet",GEOGCS["GCS_North_Am
102676 NAD_1983_StatePlane_Iowa_South_FIPS_1402_Feet PROJCS["NAD_1983_StatePlane_Iowa_South_FIPS_1402_Feet",GEOGCS["GCS_North_Am
102677 NAD_1983_StatePlane_Kansas_North_FIPS_1501_Feet PROJCS["NAD_1983_StatePlane_Kansas_North_FIPS_1501_Feet",GEOGCS["GCS_North_A
102678 NAD_1983_StatePlane_Kansas_South_FIPS_1502_Feet PROJCS["NAD_1983_StatePlane_Kansas_South_FIPS_1502_Feet",GEOGCS["GCS_North_
102679 NAD_1983_StatePlane_Kentucky_North_FIPS_1601_Feet PROJCS["NAD_1983_StatePlane_Kentucky_North_FIPS_1601_Feet",GEOGCS["GCS_North
102680 NAD_1983_StatePlane_Kentucky_South_FIPS_1602_Feet PROJCS["NAD_1983_StatePlane_Kentucky_South_FIPS_1602_Feet",GEOGCS["GCS_North
102681 NAD_1983_StatePlane_Louisiana_North_FIPS_1701_Feet PROJCS["NAD_1983_StatePlane_Louisiana_North_FIPS_1701_Feet",GEOGCS["GCS_North
102682 NAD_1983_StatePlane_Louisiana_South_FIPS_1702_Feet PROJCS["NAD_1983_StatePlane_Louisiana_South_FIPS_1702_Feet",GEOGCS["GCS_North
102683 NAD_1983_StatePlane_Maine_East_FIPS_1801_Feet PROJCS["NAD_1983_StatePlane_Maine_East_FIPS_1801_Feet",GEOGCS["GCS_North_Am
102684 NAD_1983_StatePlane_Maine_West_FIPS_1802_Feet PROJCS["NAD_1983_StatePlane_Maine_West_FIPS_1802_Feet",GEOGCS["GCS_North_Am
102685 NAD_1983_StatePlane_Maryland_FIPS_1900_Feet PROJCS["NAD_1983_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_Amer
102686 NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet PROJCS["NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet",GEOGCS["GC
102687 NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002_Feet PROJCS["NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002_Feet",GEOGCS["GCS_
102688 NAD_1983_StatePlane_Michigan_North_FIPS_2111_Feet PROJCS["NAD_1983_StatePlane_Michigan_North_FIPS_2111_Feet",GEOGCS["GCS_North_
102689 NAD_1983_StatePlane_Michigan_Central_FIPS_2112_Feet PROJCS["NAD_1983_StatePlane_Michigan_Central_FIPS_2112_Feet",GEOGCS["GCS_Nort
102690 NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet PROJCS["NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet",GEOGCS["GCS_North
102691 NAD_1983_StatePlane_Minnesota_North_FIPS_2201_Feet PROJCS["NAD_1983_StatePlane_Minnesota_North_FIPS_2201_Feet",GEOGCS["GCS_Nort
102692 NAD_1983_StatePlane_Minnesota_Central_FIPS_2202_Feet PROJCS["NAD_1983_StatePlane_Minnesota_Central_FIPS_2202_Feet",GEOGCS["GCS_No
102693 NAD_1983_StatePlane_Minnesota_South_FIPS_2203_Feet PROJCS["NAD_1983_StatePlane_Minnesota_South_FIPS_2203_Feet",GEOGCS["GCS_Nort
102694 NAD_1983_StatePlane_Mississippi_East_FIPS_2301_Feet PROJCS["NAD_1983_StatePlane_Mississippi_East_FIPS_2301_Feet",GEOGCS["GCS_North
102695 NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet PROJCS["NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet",GEOGCS["GCS_Nort
102696 NAD_1983_StatePlane_Missouri_East_FIPS_2401_Feet PROJCS["NAD_1983_StatePlane_Missouri_East_FIPS_2401_Feet",GEOGCS["GCS_North_A
102697 NAD_1983_StatePlane_Missouri_Central_FIPS_2402_Feet PROJCS["NAD_1983_StatePlane_Missouri_Central_FIPS_2402_Feet",GEOGCS["GCS_North

102698 NAD_1983_StatePlane_Missouri_West_FIPS_2403_Feet PROJCS["NAD_1983_StatePlane_Missouri_West_FIPS_2403_Feet",GEOGCS["GCS_North_

102699 NAD_1927_StatePlane_California_V_Ventura PROJCS["NAD_1927_StatePlane_California_V_Ventura",GEOGCS["GCS_North_American_1
102700 NAD_1983_StatePlane_Montana_FIPS_2500_Feet PROJCS["NAD_1983_StatePlane_Montana_FIPS_2500_Feet",GEOGCS["GCS_North_Ameri
102701 NAD_1983_PACP00_UTM_Zone_4N PROJCS["NAD_1983_PACP00_UTM_Zone_4N",GEOGCS["GCS_NAD_1983_PACP00",DATU
102702 NAD_1983_PACP00_UTM_Zone_5N PROJCS["NAD_1983_PACP00_UTM_Zone_5N",GEOGCS["GCS_NAD_1983_PACP00",DATU
102703 NAD_1983_PACP00_UTM_Zone_2S PROJCS["NAD_1983_PACP00_UTM_Zone_2S",GEOGCS["GCS_NAD_1983_PACP00",DATU
102704 NAD_1983_StatePlane_Nebraska_FIPS_2600_Feet PROJCS["NAD_1983_StatePlane_Nebraska_FIPS_2600_Feet",GEOGCS["GCS_North_Amer
102705 NAD_1983_Nebraska_Lancaster_County_FtUS PROJCS["NAD_1983_Nebraska_Lancaster_County_FtUS",GEOGCS["GCS_North_American
102706 Palestine_1923_Palestine_Grid_TM PROJCS["Palestine_1923_Palestine_Grid_TM",GEOGCS["GCS_Palestine_1923",DATUM["D_
102707 NAD_1983_StatePlane_Nevada_East_FIPS_2701_Feet PROJCS["NAD_1983_StatePlane_Nevada_East_FIPS_2701_Feet",GEOGCS["GCS_North_A
102708 NAD_1983_StatePlane_Nevada_Central_FIPS_2702_Feet PROJCS["NAD_1983_StatePlane_Nevada_Central_FIPS_2702_Feet",GEOGCS["GCS_North
102709 NAD_1983_StatePlane_Nevada_West_FIPS_2703_Feet PROJCS["NAD_1983_StatePlane_Nevada_West_FIPS_2703_Feet",GEOGCS["GCS_North_A
102710 NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feet PROJCS["NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feet",GEOGCS["GCS_North
102711 NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet PROJCS["NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet",GEOGCS["GCS_North_Am
102712 NAD_1983_StatePlane_New_Mexico_East_FIPS_3001_Feet PROJCS["NAD_1983_StatePlane_New_Mexico_East_FIPS_3001_Feet",GEOGCS["GCS_No
102713 NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002_Feet PROJCS["NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002_Feet",GEOGCS["GCS_
102714 NAD_1983_StatePlane_New_Mexico_West_FIPS_3003_Feet PROJCS["NAD_1983_StatePlane_New_Mexico_West_FIPS_3003_Feet",GEOGCS["GCS_No
102715 NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet PROJCS["NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet",GEOGCS["GCS_North
102716 NAD_1983_StatePlane_New_York_Central_FIPS_3102_Feet PROJCS["NAD_1983_StatePlane_New_York_Central_FIPS_3102_Feet",GEOGCS["GCS_No
102717 NAD_1983_StatePlane_New_York_West_FIPS_3103_Feet PROJCS["NAD_1983_StatePlane_New_York_West_FIPS_3103_Feet",GEOGCS["GCS_North
102718 NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet PROJCS["NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet",GEOGCS["GCS
102719 NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet PROJCS["NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet",GEOGCS["GCS_North_
102720 NAD_1983_StatePlane_North_Dakota_North_FIPS_3301_Feet PROJCS["NAD_1983_StatePlane_North_Dakota_North_FIPS_3301_Feet",GEOGCS["GCS_N
102721 NAD_1983_StatePlane_North_Dakota_South_FIPS_3302_Feet PROJCS["NAD_1983_StatePlane_North_Dakota_South_FIPS_3302_Feet",GEOGCS["GCS_N
102722 NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet PROJCS["NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet",GEOGCS["GCS_North_Am
102723 NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet PROJCS["NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet",GEOGCS["GCS_North_Am
102724 NAD_1983_StatePlane_Oklahoma_North_FIPS_3501_Feet PROJCS["NAD_1983_StatePlane_Oklahoma_North_FIPS_3501_Feet",GEOGCS["GCS_Nort
102725 NAD_1983_StatePlane_Oklahoma_South_FIPS_3502_Feet PROJCS["NAD_1983_StatePlane_Oklahoma_South_FIPS_3502_Feet",GEOGCS["GCS_Nort
102726 NAD_1983_StatePlane_Oregon_North_FIPS_3601_Feet PROJCS["NAD_1983_StatePlane_Oregon_North_FIPS_3601_Feet",GEOGCS["GCS_North_A
102727 NAD_1983_StatePlane_Oregon_South_FIPS_3602_Feet PROJCS["NAD_1983_StatePlane_Oregon_South_FIPS_3602_Feet",GEOGCS["GCS_North_
102728 NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet PROJCS["NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet",GEOGCS["GCS_N
102729 NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702_Feet PROJCS["NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702_Feet",GEOGCS["GCS_N
102730 NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet PROJCS["NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet",GEOGCS["GCS_North_A
102733 NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet PROJCS["NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet",GEOGCS["GCS_North_
102734 NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet PROJCS["NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet",GEOGCS["GCS_N
102735 NAD_1983_StatePlane_South_Dakota_South_FIPS_4002_Feet PROJCS["NAD_1983_StatePlane_South_Dakota_South_FIPS_4002_Feet",GEOGCS["GCS_
102736 NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet PROJCS["NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet",GEOGCS["GCS_North_Ame
102737 NAD_1983_StatePlane_Texas_North_FIPS_4201_Feet PROJCS["NAD_1983_StatePlane_Texas_North_FIPS_4201_Feet",GEOGCS["GCS_North_Am
102738 NAD_1983_StatePlane_Texas_North_Central_FIPS_4202_Feet PROJCS["NAD_1983_StatePlane_Texas_North_Central_FIPS_4202_Feet",GEOGCS["GCS_N
102739 NAD_1983_StatePlane_Texas_Central_FIPS_4203_Feet PROJCS["NAD_1983_StatePlane_Texas_Central_FIPS_4203_Feet",GEOGCS["GCS_North_A
102740 NAD_1983_StatePlane_Texas_South_Central_FIPS_4204_Feet PROJCS["NAD_1983_StatePlane_Texas_South_Central_FIPS_4204_Feet",GEOGCS["GCS_
102741 NAD_1983_StatePlane_Texas_South_FIPS_4205_Feet PROJCS["NAD_1983_StatePlane_Texas_South_FIPS_4205_Feet",GEOGCS["GCS_North_A
102742 NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet PROJCS["NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet",GEOGCS["GCS_North_Am
102743 NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet PROJCS["NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet",GEOGCS["GCS_North_A
102744 NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet PROJCS["NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet",GEOGCS["GCS_North_Am
102745 NAD_1983_StatePlane_Vermont_FIPS_4400_Feet PROJCS["NAD_1983_StatePlane_Vermont_FIPS_4400_Feet",GEOGCS["GCS_North_Americ
102746 NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet PROJCS["NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet",GEOGCS["GCS_North_A
102747 NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet PROJCS["NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet",GEOGCS["GCS_North_
102748 NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet PROJCS["NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet",GEOGCS["GCS_No
102749 NAD_1983_StatePlane_Washington_South_FIPS_4602_Feet PROJCS["NAD_1983_StatePlane_Washington_South_FIPS_4602_Feet",GEOGCS["GCS_No
102750 NAD_1983_StatePlane_West_Virginia_North_FIPS_4701_Feet PROJCS["NAD_1983_StatePlane_West_Virginia_North_FIPS_4701_Feet",GEOGCS["GCS_N
102751 NAD_1983_StatePlane_West_Virginia_South_FIPS_4702_Feet PROJCS["NAD_1983_StatePlane_West_Virginia_South_FIPS_4702_Feet",GEOGCS["GCS_N
102752 NAD_1983_StatePlane_Wisconsin_North_FIPS_4801_Feet PROJCS["NAD_1983_StatePlane_Wisconsin_North_FIPS_4801_Feet",GEOGCS["GCS_Nort
102753 NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802_Feet PROJCS["NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802_Feet",GEOGCS["GCS_No

102754 NAD_1983_StatePlane_Wisconsin_South_FIPS_4803_Feet PROJCS["NAD_1983_StatePlane_Wisconsin_South_FIPS_4803_Feet",GEOGCS["GCS_Nort

102755 NAD_1983_StatePlane_Wyoming_East_FIPS_4901_Feet PROJCS["NAD_1983_StatePlane_Wyoming_East_FIPS_4901_Feet",GEOGCS["GCS_North_
102756 NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902_Feet PROJCS["NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902_Feet",GEOGCS["GCS
102757 NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903_Feet PROJCS["NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903_Feet",GEOGCS["GC
102758 NAD_1983_StatePlane_Wyoming_West_FIPS_4904_Feet PROJCS["NAD_1983_StatePlane_Wyoming_West_FIPS_4904_Feet",GEOGCS["GCS_North_
102761 NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200_Feet PROJCS["NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200_Feet",GEOGCS["
102762 Katanga_1955_Katanga_Lambert PROJCS["Katanga_1955_Katanga_Lambert",GEOGCS["GCS_Katanga_1955",DATUM["D_Ka
102763 NAD_1983_StatePlane_Kentucky_FIPS_1600_Feet PROJCS["NAD_1983_StatePlane_Kentucky_FIPS_1600_Feet",GEOGCS["GCS_North_Amer
102764 Pulkovo_1942_Adj_1983_3_Degree_GK_Zone_7 PROJCS["Pulkovo_1942_Adj_1983_3_Degree_GK_Zone_7",GEOGCS["GCS_Pulkovo_1942_
102765 Pulkovo_1942_Adj_1983_3_Degree_GK_Zone_8 PROJCS["Pulkovo_1942_Adj_1983_3_Degree_GK_Zone_8",GEOGCS["GCS_Pulkovo_1942_
102766 NAD_1983_StatePlane_Guam_FIPS_5400_Feet PROJCS["NAD_1983_StatePlane_Guam_FIPS_5400_Feet",GEOGCS["GCS_North_American
102767 MAGNA_Leticia_Amazonas_1994 PROJCS["MAGNA_Leticia_Amazonas_1994",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA
102768 MAGNA_Medellin_Antioquia_2010 PROJCS["MAGNA_Medellin_Antioquia_2010",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA
102769 MAGNA_Arauca_2007 PROJCS["MAGNA_Arauca_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROI
102770 MAGNA_Barranquilla_Atlantico_1997 PROJCS["MAGNA_Barranquilla_Atlantico_1997",GEOGCS["GCS_MAGNA",DATUM["D_MAG
102771 MAGNA_Bogota_DC_2005 PROJCS["MAGNA_Bogota_DC_2005",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHE
102772 MAGNA_Cartagena_Bolivar_2005 PROJCS["MAGNA_Cartagena_Bolivar_2005",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA
102773 MAGNA_Tunja_Boyaca_1997 PROJCS["MAGNA_Tunja_Boyaca_1997",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SP
102774 MAGNA_Manizales_Caldas_2011 PROJCS["MAGNA_Manizales_Caldas_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA
102775 MAGNA_Florencia_Caqueta_2007 PROJCS["MAGNA_Florencia_Caqueta_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA
102776 MAGNA_Yopal_Casanare_2006 PROJCS["MAGNA_Yopal_Casanare_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",S
102777 MAGNA_Popayan_Cauca_2006 PROJCS["MAGNA_Popayan_Cauca_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",S
102778 MAGNA_Valledupar_Cesar_2011 PROJCS["MAGNA_Valledupar_Cesar_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA"
102779 MAGNA_Quibdo_Choco_2011 PROJCS["MAGNA_Quibdo_Choco_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SP
102780 MAGNA_Monteria_Cordoba_2006 PROJCS["MAGNA_Monteria_Cordoba_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA
102781 MAGNA_Inirida_Guainia_2008 PROJCS["MAGNA_Inirida_Guainia_2008",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SP
102782 MAGNA_San_Jose_del_Guaviare_2011 PROJCS["MAGNA_San_Jose_del_Guaviare_2011",GEOGCS["GCS_MAGNA",DATUM["D_MA
102783 MAGNA_Neiva_Huila_2006 PROJCS["MAGNA_Neiva_Huila_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPH
102784 MAGNA_Riohacha_La_Guajira_2006 PROJCS["MAGNA_Riohacha_La_Guajira_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAG
102785 MAGNA_Santa_Marta_Magdalena_2007 PROJCS["MAGNA_Santa_Marta_Magdalena_2007",GEOGCS["GCS_MAGNA",DATUM["D_M
102786 MAGNA_Villavicencio_Meta_2011 PROJCS["MAGNA_Villavicencio_Meta_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA
102787 MAGNA_Pasto_Narino_2008 PROJCS["MAGNA_Pasto_Narino_2008",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPH
102788 MAGNA_Cucuta_Norte_de_Santander_2011 PROJCS["MAGNA_Cucuta_Norte_de_Santander_2011",GEOGCS["GCS_MAGNA",DATUM["D
102789 MAGNA_Mocoa_Putumayo_2011 PROJCS["MAGNA_Mocoa_Putumayo_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA"
102790 MAGNA_Armenia_Quindio_2006 PROJCS["MAGNA_Armenia_Quindio_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA"
102791 MAGNA_Pereira_Risaralda_2007 PROJCS["MAGNA_Pereira_Risaralda_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA"
102792 MAGNA_San_Andres_2007 PROJCS["MAGNA_San_Andres_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPH
102793 MAGNA_Bucaramanga_Santander_2008 PROJCS["MAGNA_Bucaramanga_Santander_2008",GEOGCS["GCS_MAGNA",DATUM["D_M
102794 MAGNA_Sucre_2006 PROJCS["MAGNA_Sucre_2006",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPHEROID
102795 MAGNA_Ibague_Tolima_2007 PROJCS["MAGNA_Ibague_Tolima_2007",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SP
102796 MAGNA_Cali_Valle_del_Cauca_2009 PROJCS["MAGNA_Cali_Valle_del_Cauca_2009",GEOGCS["GCS_MAGNA",DATUM["D_MAG
102797 MAGNA_Mitu_Vaupes_2011 PROJCS["MAGNA_Mitu_Vaupes_2011",GEOGCS["GCS_MAGNA",DATUM["D_MAGNA",SPH
102798 MAGNA_Puerto_Carreno_Vichada_2011 PROJCS["MAGNA_Puerto_Carreno_Vichada_2011",GEOGCS["GCS_MAGNA",DATUM["D_M
102962 NAD_1983_2011_California_Teale_Albers PROJCS["NAD_1983_2011_California_Teale_Albers",GEOGCS["GCS_NAD_1983_2011",DAT
102963 NAD_1983_2011_Mississippi_TM PROJCS["NAD_1983_2011_Mississippi_TM",GEOGCS["GCS_NAD_1983_2011",DATUM["D_
102965 NAD_1983_2011_Contiguous_USA_Albers PROJCS["NAD_1983_2011_Contiguous_USA_Albers",GEOGCS["GCS_NAD_1983_2011",DA
102966 NAD_1983_2011_Alaska_Albers PROJCS["NAD_1983_2011_Alaska_Albers",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N
102967 NAD_1983_2011_Florida_GDL_Albers PROJCS["NAD_1983_2011_Florida_GDL_Albers",GEOGCS["GCS_NAD_1983_2011",DATUM
102968 NAD_1983_2011_Michigan_GeoRef_Meters PROJCS["NAD_1983_2011_Michigan_GeoRef_Meters",GEOGCS["GCS_NAD_1983_2011",D
102969 NAD_1983_2011_Oregon_Statewide_Lambert PROJCS["NAD_1983_2011_Oregon_Statewide_Lambert",GEOGCS["GCS_NAD_1983_2011"
102970 NAD_1983_2011_Oregon_Statewide_Lambert_Ft_Intl PROJCS["NAD_1983_2011_Oregon_Statewide_Lambert_Ft_Intl",GEOGCS["GCS_NAD_1983
102971 NAD_1983_2011_Texas_Centric_Mapping_System_Albers PROJCS["NAD_1983_2011_Texas_Centric_Mapping_System_Albers",GEOGCS["GCS_NAD_
102972 NAD_1983_2011_Texas_Centric_Mapping_System_Lambert PROJCS["NAD_1983_2011_Texas_Centric_Mapping_System_Lambert",GEOGCS["GCS_NAD
102973 NAD_1983_2011_Wisconsin_TM PROJCS["NAD_1983_2011_Wisconsin_TM",GEOGCS["GCS_NAD_1983_2011",DATUM["D_N

102974 NAD_1983_2011_Wisconsin_TM_US_Ft PROJCS["NAD_1983_2011_Wisconsin_TM_US_Ft",GEOGCS["GCS_NAD_1983_2011",DATU

102975 NAD_1983_2011_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1983_2011_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_NAD_1
102976 NAD_1983_2011_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1983_2011_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_NAD_
102977 NAD_1983_2011_StatePlane_Alaska_1_FIPS_5001 PROJCS["NAD_1983_2011_StatePlane_Alaska_1_FIPS_5001",GEOGCS["GCS_NAD_1983_
102986 NAD_1983_2011_StatePlane_Alaska_10_FIPS_5010 PROJCS["NAD_1983_2011_StatePlane_Alaska_10_FIPS_5010",GEOGCS["GCS_NAD_1983
102987 NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_NAD_19
102988 NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_NAD
102989 NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_NAD_1
102990 NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Arizona_East_FIPS_0201_Ft_Intl",GEOGCS["GCS_
102991 NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl",GEOGCS["GC
102992 NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Arizona_West_FIPS_0203_Ft_Intl",GEOGCS["GCS_
102993 NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_NAD
102994 NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_NAD
102995 NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Arkansas_North_FIPS_0301_Ft_US",GEOGCS["GC
102996 NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Arkansas_South_FIPS_0302_Ft_US",GEOGCS["GC
102997 NAD_1983_2011_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1983_2011_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_NAD_198
102998 NAD_1983_2011_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1983_2011_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_NAD_198
102999 NAD_1983_2011_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1983_2011_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_NAD_19
103000 NAD_1983_2011_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1983_2011_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_NAD_19
103001 NAD_1983_2011_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1983_2011_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_NAD_198
103002 NAD_1983_2011_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1983_2011_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_NAD_19
103003 NAD_1983_2011_StatePlane_California_I_FIPS_0401_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_I_FIPS_0401_Ft_US",GEOGCS["GCS_NA
103004 NAD_1983_2011_StatePlane_California_II_FIPS_0402_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_II_FIPS_0402_Ft_US",GEOGCS["GCS_N
103005 NAD_1983_2011_StatePlane_California_III_FIPS_0403_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_III_FIPS_0403_Ft_US",GEOGCS["GCS_N
103006 NAD_1983_2011_StatePlane_California_IV_FIPS_0404_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_IV_FIPS_0404_Ft_US",GEOGCS["GCS_N
103007 NAD_1983_2011_StatePlane_California_V_FIPS_0405_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_V_FIPS_0405_Ft_US",GEOGCS["GCS_N
103008 NAD_1983_2011_StatePlane_California_VI_FIPS_0406_Ft_US PROJCS["NAD_1983_2011_StatePlane_California_VI_FIPS_0406_Ft_US",GEOGCS["GCS_N
103009 NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_NAD_
103010 NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_NAD
103011 NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_NAD
103012 NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Colorado_North_FIPS_0501_Ft_US",GEOGCS["GCS
103013 NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Colorado_Central_FIPS_0502_Ft_US",GEOGCS["G
103014 NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503_Ft_US PROJCS["NAD_1983_2011_StatePlane_Colorado_South_FIPS_0503_Ft_US",GEOGCS["GC
103015 NAD_1983_2011_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1983_2011_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_NAD_198
103016 NAD_1983_2011_StatePlane_Connecticut_FIPS_0600_Ft_US PROJCS["NAD_1983_2011_StatePlane_Connecticut_FIPS_0600_Ft_US",GEOGCS["GCS_N
103017 NAD_1983_2011_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1983_2011_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_NAD_1983_
103018 NAD_1983_2011_StatePlane_Delaware_FIPS_0700_Ft_US PROJCS["NAD_1983_2011_StatePlane_Delaware_FIPS_0700_Ft_US",GEOGCS["GCS_NAD
103019 NAD_1983_2011_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1983_2011_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_NAD_19
103020 NAD_1983_2011_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1983_2011_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_NAD_19
103021 NAD_1983_2011_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1983_2011_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_NAD_1
103022 NAD_1983_2011_StatePlane_Florida_East_FIPS_0901_Ft_US PROJCS["NAD_1983_2011_StatePlane_Florida_East_FIPS_0901_Ft_US",GEOGCS["GCS_N
103023 NAD_1983_2011_StatePlane_Florida_West_FIPS_0902_Ft_US PROJCS["NAD_1983_2011_StatePlane_Florida_West_FIPS_0902_Ft_US",GEOGCS["GCS_N
103024 NAD_1983_2011_StatePlane_Florida_North_FIPS_0903_Ft_US PROJCS["NAD_1983_2011_StatePlane_Florida_North_FIPS_0903_Ft_US",GEOGCS["GCS_
103025 NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_NAD_1
103026 NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_NAD_1
103027 NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001_Ft_US PROJCS["NAD_1983_2011_StatePlane_Georgia_East_FIPS_1001_Ft_US",GEOGCS["GCS_

103028 NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002_Ft_US PROJCS["NAD_1983_2011_StatePlane_Georgia_West_FIPS_1002_Ft_US",GEOGCS["GCS_

103029 NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_NAD_198
103030 NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_NAD_1
103031 NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_NAD_198
103032 NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101_Ft_US PROJCS["NAD_1983_2011_StatePlane_Idaho_East_FIPS_1101_Ft_US",GEOGCS["GCS_NA
103033 NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102_Ft_US PROJCS["NAD_1983_2011_StatePlane_Idaho_Central_FIPS_1102_Ft_US",GEOGCS["GCS_
103034 NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103_Ft_US PROJCS["NAD_1983_2011_StatePlane_Idaho_West_FIPS_1103_Ft_US",GEOGCS["GCS_N
103035 NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_NAD_198
103036 NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_NAD_19
103037 NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201_Ft_US PROJCS["NAD_1983_2011_StatePlane_Illinois_East_FIPS_1201_Ft_US",GEOGCS["GCS_N
103038 NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202_Ft_US PROJCS["NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202_Ft_US",GEOGCS["GCS_N
103039 NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_NAD_19
103040 NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_NAD_1
103041 NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Indiana_East_FIPS_1301_Ft_US",GEOGCS["GCS_N
103042 NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Indiana_West_FIPS_1302_Ft_US",GEOGCS["GCS_
103043 NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_NAD_198
103044 NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_NAD_198
103045 NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401_Ft_US PROJCS["NAD_1983_2011_StatePlane_Iowa_North_FIPS_1401_Ft_US",GEOGCS["GCS_NA
103046 NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402_Ft_US PROJCS["NAD_1983_2011_StatePlane_Iowa_South_FIPS_1402_Ft_US",GEOGCS["GCS_N
103047 NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_NAD_1
103048 NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_NAD_1
103049 NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kansas_North_FIPS_1501_Ft_US",GEOGCS["GCS_
103050 NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kansas_South_FIPS_1502_Ft_US",GEOGCS["GCS
103051 NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_NAD_
103052 NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kentucky_North_FIPS_1601_Ft_US",GEOGCS["GC
103053 NAD_1983_2011_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_2011_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_NAD_1983_
103054 NAD_1983_2011_StatePlane_Kentucky_FIPS_1600_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kentucky_FIPS_1600_Ft_US",GEOGCS["GCS_NAD
103055 NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_NAD
103056 NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602_Ft_US PROJCS["NAD_1983_2011_StatePlane_Kentucky_South_FIPS_1602_Ft_US",GEOGCS["GC
103057 NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_NAD
103058 NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_NAD
103059 NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701_Ft_US PROJCS["NAD_1983_2011_StatePlane_Louisiana_North_FIPS_1701_Ft_US",GEOGCS["GC
103060 NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702_Ft_US PROJCS["NAD_1983_2011_StatePlane_Louisiana_South_FIPS_1702_Ft_US",GEOGCS["GC
103061 NAD_1983_2011_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1983_2011_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_NAD_198
103062 NAD_1983_2011_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1983_2011_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_NAD_19
103063 NAD_1983_2011_StatePlane_Maine_East_FIPS_1801_Ft_US PROJCS["NAD_1983_2011_StatePlane_Maine_East_FIPS_1801_Ft_US",GEOGCS["GCS_N
103064 NAD_1983_2011_StatePlane_Maine_West_FIPS_1802_Ft_US PROJCS["NAD_1983_2011_StatePlane_Maine_West_FIPS_1802_Ft_US",GEOGCS["GCS_N
103065 NAD_1983_2011_Maine_2000_East_Zone PROJCS["NAD_1983_2011_Maine_2000_East_Zone",GEOGCS["GCS_NAD_1983_2011",DA
103066 NAD_1983_2011_Maine_2000_Central_Zone PROJCS["NAD_1983_2011_Maine_2000_Central_Zone",GEOGCS["GCS_NAD_1983_2011",
103067 NAD_1983_2011_Maine_2000_West_Zone PROJCS["NAD_1983_2011_Maine_2000_West_Zone",GEOGCS["GCS_NAD_1983_2011",DA
103068 NAD_1983_2011_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1983_2011_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_NAD_1983_
103069 NAD_1983_2011_StatePlane_Maryland_FIPS_1900_Ft_US PROJCS["NAD_1983_2011_StatePlane_Maryland_FIPS_1900_Ft_US",GEOGCS["GCS_NAD
103070 NAD_1983_2011_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS["G
103071 NAD_1983_2011_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["GCS
103072 NAD_1983_2011_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS",GEOGCS["
103073 NAD_1983_2011_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS PROJCS["NAD_1983_2011_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS",GEOGCS["GC
103074 NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_NAD_
103075 NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_NAD
103076 NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_NAD_
103077 NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Michigan_North_FIPS_2111_Ft_Intl",GEOGCS["GCS
103078 NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl",GEOGCS["GC
103079 NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113_Ft_Intl",GEOGCS["GCS
103080 NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_NAD
103081 NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS_NA

103082 NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_NAD

103083 NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201_Ft_US PROJCS["NAD_1983_2011_StatePlane_Minnesota_North_FIPS_2201_Ft_US",GEOGCS["GC
103084 NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202_Ft_US PROJCS["NAD_1983_2011_StatePlane_Minnesota_Central_FIPS_2202_Ft_US",GEOGCS["G
103085 NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203_Ft_US PROJCS["NAD_1983_2011_StatePlane_Minnesota_South_FIPS_2203_Ft_US",GEOGCS["GC
103086 NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_NAD
103087 NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_NAD
103088 NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Mississippi_East_FIPS_2301_Ft_US",GEOGCS["GC
103089 NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Mississippi_West_FIPS_2302_Ft_US",GEOGCS["GC
103090 NAD_1983_2011_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1983_2011_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_NAD_1
103091 NAD_1983_2011_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1983_2011_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_NAD
103092 NAD_1983_2011_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1983_2011_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_NAD_1
103093 NAD_1983_2011_StatePlane_Montana_FIPS_2500 PROJCS["NAD_1983_2011_StatePlane_Montana_FIPS_2500",GEOGCS["GCS_NAD_1983_
103094 NAD_1983_2011_StatePlane_Montana_FIPS_2500_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Montana_FIPS_2500_Ft_Intl",GEOGCS["GCS_NAD
103095 NAD_1983_2011_StatePlane_Nebraska_FIPS_2600 PROJCS["NAD_1983_2011_StatePlane_Nebraska_FIPS_2600",GEOGCS["GCS_NAD_1983_
103096 NAD_1983_2011_StatePlane_Nebraska_FIPS_2600_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nebraska_FIPS_2600_Ft_US",GEOGCS["GCS_NAD
103097 NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_NAD_19
103098 NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_NAD
103099 NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_NAD_1
103100 NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nevada_East_FIPS_2701_Ft_US",GEOGCS["GCS_
103101 NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nevada_Central_FIPS_2702_Ft_US",GEOGCS["GC
103102 NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703_Ft_US PROJCS["NAD_1983_2011_StatePlane_Nevada_West_FIPS_2703_Ft_US",GEOGCS["GCS_
103103 NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_NAD
103104 NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Hampshire_FIPS_2800_Ft_US",GEOGCS["GC
103105 NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_NAD_19
103106 NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Jersey_FIPS_2900_Ft_US",GEOGCS["GCS_N
103107 NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS_NA
103108 NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["GCS_
103109 NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS_NA
103110 NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Mexico_East_FIPS_3001_Ft_US",GEOGCS["G
103111 NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US",GEOGCS
103112 NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_Mexico_West_FIPS_3003_Ft_US",GEOGCS["G
103113 NAD_1983_2011_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1983_2011_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_NAD_
103114 NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS_NA
103115 NAD_1983_2011_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1983_2011_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_NAD
103116 NAD_1983_2011_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1983_2011_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS["GC
103117 NAD_1983_2011_StatePlane_New_York_East_FIPS_3101_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_East_FIPS_3101_Ft_US",GEOGCS["GCS
103118 NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_Central_FIPS_3102_Ft_US",GEOGCS["G
103119 NAD_1983_2011_StatePlane_New_York_West_FIPS_3103_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_West_FIPS_3103_Ft_US",GEOGCS["GC
103120 NAD_1983_2011_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US PROJCS["NAD_1983_2011_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US",GEOGCS["
103121 NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200 PROJCS["NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_NAD_
103122 NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200_Ft_US PROJCS["NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200_Ft_US",GEOGCS["GCS
103123 NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GCS_N
103124 NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GCS_
103125 NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301_FtI PROJCS["NAD_1983_2011_StatePlane_North_Dakota_North_FIPS_3301_FtI",GEOGCS["GC
103126 NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302_FtI PROJCS["NAD_1983_2011_StatePlane_North_Dakota_South_FIPS_3302_FtI",GEOGCS["GC
103127 NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_NAD_198
103128 NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_NAD_198
103129 NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401_Ft_US PROJCS["NAD_1983_2011_StatePlane_Ohio_North_FIPS_3401_Ft_US",GEOGCS["GCS_NA
103130 NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402_Ft_US PROJCS["NAD_1983_2011_StatePlane_Ohio_South_FIPS_3402_Ft_US",GEOGCS["GCS_N
103131 NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_NAD
103132 NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_NAD
103133 NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Oklahoma_North_FIPS_3501_Ft_US",GEOGCS["GC
103134 NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Oklahoma_South_FIPS_3502_Ft_US",GEOGCS["GC
103135 NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601 PROJCS["NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601",GEOGCS["GCS_NAD_1

103136 NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602 PROJCS["NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602",GEOGCS["GCS_NAD_1

103137 NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Oregon_North_FIPS_3601_Ft_Intl",GEOGCS["GCS_
103138 NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Oregon_South_FIPS_3602_Ft_Intl",GEOGCS["GCS
103139 NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701 PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701",GEOGCS["GCS_N
103140 NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US",GEOGCS["
103141 NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GCS_N
103142 NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US PROJCS["NAD_1983_2011_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US",GEOGCS[
103143 NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_NAD_1
103144 NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800_Ft_US PROJCS["NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800_Ft_US",GEOGCS["GCS_
103145 NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900 PROJCS["NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900",GEOGCS["GCS_NAD_
103146 NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900_Ft_Intl",GEOGCS["GCS
103147 NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GCS_
103148 NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["GCS_
103149 NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001_Ft_US PROJCS["NAD_1983_2011_StatePlane_South_Dakota_North_FIPS_4001_Ft_US",GEOGCS
103150 NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002_Ft_US PROJCS["NAD_1983_2011_StatePlane_South_Dakota_South_FIPS_4002_Ft_US",GEOGCS
103151 NAD_1983_2011_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1983_2011_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_NAD_1983
103152 NAD_1983_2011_StatePlane_Tennessee_FIPS_4100_Ft_US PROJCS["NAD_1983_2011_StatePlane_Tennessee_FIPS_4100_Ft_US",GEOGCS["GCS_NA
103153 NAD_1983_2011_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1983_2011_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_NAD_19
103154 NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["GCS_
103155 NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_NAD_1
103156 NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["GCS_
103157 NAD_1983_2011_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1983_2011_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_NAD_19
103158 NAD_1983_2011_StatePlane_Texas_North_FIPS_4201_Ft_US PROJCS["NAD_1983_2011_StatePlane_Texas_North_FIPS_4201_Ft_US",GEOGCS["GCS_N
103159 NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202_FtUS PROJCS["NAD_1983_2011_StatePlane_Texas_North_Central_FIPS_4202_FtUS",GEOGCS["
103160 NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203_Ft_US PROJCS["NAD_1983_2011_StatePlane_Texas_Central_FIPS_4203_Ft_US",GEOGCS["GCS_
103161 NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204_FtUS PROJCS["NAD_1983_2011_StatePlane_Texas_South_Central_FIPS_4204_FtUS",GEOGCS[
103162 NAD_1983_2011_StatePlane_Texas_South_FIPS_4205_Ft_US PROJCS["NAD_1983_2011_StatePlane_Texas_South_FIPS_4205_Ft_US",GEOGCS["GCS_N
103163 NAD_1983_2011_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1983_2011_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_NAD_198
103164 NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_NAD_19
103165 NAD_1983_2011_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1983_2011_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_NAD_198
103166 NAD_1983_2011_StatePlane_Utah_North_FIPS_4301_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Utah_North_FIPS_4301_Ft_Intl",GEOGCS["GCS_NA
103167 NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302_Ft_Intl",GEOGCS["GCS_N
103168 NAD_1983_2011_StatePlane_Utah_South_FIPS_4303_Ft_Intl PROJCS["NAD_1983_2011_StatePlane_Utah_South_FIPS_4303_Ft_Intl",GEOGCS["GCS_N
103169 NAD_1983_2011_StatePlane_Utah_North_FIPS_4301_Ft_US PROJCS["NAD_1983_2011_StatePlane_Utah_North_FIPS_4301_Ft_US",GEOGCS["GCS_NA
103170 NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302_Ft_US PROJCS["NAD_1983_2011_StatePlane_Utah_Central_FIPS_4302_Ft_US",GEOGCS["GCS_
103171 NAD_1983_2011_StatePlane_Utah_South_FIPS_4303_Ft_US PROJCS["NAD_1983_2011_StatePlane_Utah_South_FIPS_4303_Ft_US",GEOGCS["GCS_N
103172 NAD_1983_2011_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1983_2011_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_NAD_1983_2
103173 NAD_1983_2011_StatePlane_Vermont_FIPS_4400_Ft_US PROJCS["NAD_1983_2011_StatePlane_Vermont_FIPS_4400_Ft_US",GEOGCS["GCS_NAD_
103174 NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_NAD_1
103175 NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_NAD_1
103176 NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501_Ft_US PROJCS["NAD_1983_2011_StatePlane_Virginia_North_FIPS_4501_Ft_US",GEOGCS["GCS_
103177 NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502_Ft_US PROJCS["NAD_1983_2011_StatePlane_Virginia_South_FIPS_4502_Ft_US",GEOGCS["GCS
103178 NAD_1983_2011_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1983_2011_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS_NA
103179 NAD_1983_2011_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1983_2011_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS_NA
103180 NAD_1983_2011_StatePlane_Washington_North_FIPS_4601_Ft_US PROJCS["NAD_1983_2011_StatePlane_Washington_North_FIPS_4601_Ft_US",GEOGCS["G
103181 NAD_1983_2011_StatePlane_Washington_South_FIPS_4602_Ft_US PROJCS["NAD_1983_2011_StatePlane_Washington_South_FIPS_4602_Ft_US",GEOGCS["G
103182 NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GCS_N
103183 NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GCS_
103184 NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701_FtUS PROJCS["NAD_1983_2011_StatePlane_West_Virginia_North_FIPS_4701_FtUS",GEOGCS["G
103185 NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702_FtUS PROJCS["NAD_1983_2011_StatePlane_West_Virginia_South_FIPS_4702_FtUS",GEOGCS["
103186 NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_NAD
103187 NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS_NA
103188 NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_NAD
103189 NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wisconsin_North_FIPS_4801_Ft_US",GEOGCS["GC

103190 NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US",GEOGCS["G

103191 NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wisconsin_South_FIPS_4803_Ft_US",GEOGCS["GC
103192 NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_NAD_
103193 NAD_1983_2011_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1983_2011_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS["GC
103194 NAD_1983_2011_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1983_2011_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS["GC
103195 NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_NAD_
103196 NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_East_FIPS_4901_Ft_US",GEOGCS["GCS
103197 NAD_1983_2011_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US",GEOGCS[
103198 NAD_1983_2011_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US",GEOGCS
103199 NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904_Ft_US PROJCS["NAD_1983_2011_StatePlane_Wyoming_West_FIPS_4904_Ft_US",GEOGCS["GCS
103200 NAD_1983_2011_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200 PROJCS["NAD_1983_2011_StatePlane_Puerto_Rico_Virgin_Isls_FIPS_5200",GEOGCS["GC
103201 RGRDC_2005_Congo_TM_Zone_12 PROJCS["RGRDC_2005_Congo_TM_Zone_12",GEOGCS["GCS_RGRDC_2005",DATUM["D_
103210 RGRDC_2005_UTM_Zone_33S PROJCS["RGRDC_2005_UTM_Zone_33S",GEOGCS["GCS_RGRDC_2005",DATUM["D_Res
103213 Chua_UTM_Zone_23S PROJCS["Chua_UTM_Zone_23S",GEOGCS["GCS_Chua",DATUM["D_Chua",SPHEROID["Int
103214 REGCAN95_UTM_Zone_27N PROJCS["REGCAN95_UTM_Zone_27N",GEOGCS["GCS_REGCAN95",DATUM["D_Red_Ge
103215 REGCAN95_UTM_Zone_28N PROJCS["REGCAN95_UTM_Zone_28N",GEOGCS["GCS_REGCAN95",DATUM["D_Red_Ge
103216 ETRS_1989_DKTM1 PROJCS["ETRS_1989_DKTM1",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPH
103220 NAD_1983_CORS96_StatePlane_Alabama_East_FIPS_0101 PROJCS["NAD_1983_CORS96_StatePlane_Alabama_East_FIPS_0101",GEOGCS["GCS_NA
103221 NAD_1983_CORS96_StatePlane_Alabama_West_FIPS_0102 PROJCS["NAD_1983_CORS96_StatePlane_Alabama_West_FIPS_0102",GEOGCS["GCS_N
103222 NAD_1983_CORS96_StatePlane_Arizona_East_FIPS_0201 PROJCS["NAD_1983_CORS96_StatePlane_Arizona_East_FIPS_0201",GEOGCS["GCS_NAD
103223 NAD_1983_CORS96_StatePlane_Arizona_Central_FIPS_0202 PROJCS["NAD_1983_CORS96_StatePlane_Arizona_Central_FIPS_0202",GEOGCS["GCS_N
103224 NAD_1983_CORS96_StatePlane_Arizona_West_FIPS_0203 PROJCS["NAD_1983_CORS96_StatePlane_Arizona_West_FIPS_0203",GEOGCS["GCS_NA
103225 NAD_1983_CORS96_StatePlane_Arizona_East_FIPS_0201_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Arizona_East_FIPS_0201_Ft_Intl",GEOGCS["GC
103226 NAD_1983_CORS96_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Arizona_Central_FIPS_0202_Ft_Intl",GEOGCS["
103227 NAD_1983_CORS96_StatePlane_Arizona_West_FIPS_0203_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Arizona_West_FIPS_0203_Ft_Intl",GEOGCS["G
103228 NAD_1983_CORS96_StatePlane_Arkansas_North_FIPS_0301 PROJCS["NAD_1983_CORS96_StatePlane_Arkansas_North_FIPS_0301",GEOGCS["GCS_N
103229 NAD_1983_CORS96_StatePlane_Arkansas_South_FIPS_0302 PROJCS["NAD_1983_CORS96_StatePlane_Arkansas_South_FIPS_0302",GEOGCS["GCS_N
103230 NAD_1983_CORS96_StatePlane_Arkansas_North_FIPS_0301_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Arkansas_North_FIPS_0301_Ft_US",GEOGCS[
103231 NAD_1983_CORS96_StatePlane_Arkansas_South_FIPS_0302_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Arkansas_South_FIPS_0302_Ft_US",GEOGCS[
103232 NAD_1983_CORS96_StatePlane_California_I_FIPS_0401 PROJCS["NAD_1983_CORS96_StatePlane_California_I_FIPS_0401",GEOGCS["GCS_NAD_
103233 NAD_1983_CORS96_StatePlane_California_II_FIPS_0402 PROJCS["NAD_1983_CORS96_StatePlane_California_II_FIPS_0402",GEOGCS["GCS_NAD
103234 NAD_1983_CORS96_StatePlane_California_III_FIPS_0403 PROJCS["NAD_1983_CORS96_StatePlane_California_III_FIPS_0403",GEOGCS["GCS_NAD
103235 NAD_1983_CORS96_StatePlane_California_IV_FIPS_0404 PROJCS["NAD_1983_CORS96_StatePlane_California_IV_FIPS_0404",GEOGCS["GCS_NAD
103236 NAD_1983_CORS96_StatePlane_California_V_FIPS_0405 PROJCS["NAD_1983_CORS96_StatePlane_California_V_FIPS_0405",GEOGCS["GCS_NAD
103237 NAD_1983_CORS96_StatePlane_California_VI_FIPS_0406 PROJCS["NAD_1983_CORS96_StatePlane_California_VI_FIPS_0406",GEOGCS["GCS_NAD
103238 NAD_1983_CORS96_StatePlane_California_I_FIPS_0401_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_California_I_FIPS_0401_Ft_US",GEOGCS["GCS
103239 NAD_1983_CORS96_StatePlane_California_II_FIPS_0402_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_California_II_FIPS_0402_Ft_US",GEOGCS["GC
103240 NAD_1983_CORS96_StatePlane_California_III_FIPS_0403_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_California_III_FIPS_0403_Ft_US",GEOGCS["GC
103241 NAD_1983_CORS96_StatePlane_California_IV_FIPS_0404_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_California_IV_FIPS_0404_Ft_US",GEOGCS["GC
103242 NAD_1983_CORS96_StatePlane_California_V_FIPS_0405_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_California_V_FIPS_0405_Ft_US",GEOGCS["GC
103243 NAD_1983_CORS96_StatePlane_California_VI_FIPS_0406_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_California_VI_FIPS_0406_Ft_US",GEOGCS["GC

103244 NAD_1983_CORS96_StatePlane_Colorado_North_FIPS_0501 PROJCS["NAD_1983_CORS96_StatePlane_Colorado_North_FIPS_0501",GEOGCS["GCS_N

103245 NAD_1983_CORS96_StatePlane_Colorado_Central_FIPS_0502 PROJCS["NAD_1983_CORS96_StatePlane_Colorado_Central_FIPS_0502",GEOGCS["GCS_
103246 NAD_1983_CORS96_StatePlane_Colorado_South_FIPS_0503 PROJCS["NAD_1983_CORS96_StatePlane_Colorado_South_FIPS_0503",GEOGCS["GCS_N
103247 NAD_1983_CORS96_StatePlane_Colorado_North_FIPS_0501_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Colorado_North_FIPS_0501_Ft_US",GEOGCS["
103248 NAD_1983_CORS96_StatePlane_Colorado_Central_FIPS_0502_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Colorado_Central_FIPS_0502_Ft_US",GEOGCS
103249 NAD_1983_CORS96_StatePlane_Colorado_South_FIPS_0503_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Colorado_South_FIPS_0503_Ft_US",GEOGCS[
103250 NAD_1983_CORS96_StatePlane_Connecticut_FIPS_0600 PROJCS["NAD_1983_CORS96_StatePlane_Connecticut_FIPS_0600",GEOGCS["GCS_NAD_
103251 NAD_1983_CORS96_StatePlane_Connecticut_FIPS_0600_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Connecticut_FIPS_0600_Ft_US",GEOGCS["GC
103252 NAD_1983_CORS96_StatePlane_Delaware_FIPS_0700 PROJCS["NAD_1983_CORS96_StatePlane_Delaware_FIPS_0700",GEOGCS["GCS_NAD_1
103253 NAD_1983_CORS96_StatePlane_Delaware_FIPS_0700_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Delaware_FIPS_0700_Ft_US",GEOGCS["GCS_
103254 NAD_1983_CORS96_StatePlane_Florida_East_FIPS_0901 PROJCS["NAD_1983_CORS96_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_NAD
103255 NAD_1983_CORS96_StatePlane_Florida_West_FIPS_0902 PROJCS["NAD_1983_CORS96_StatePlane_Florida_West_FIPS_0902",GEOGCS["GCS_NAD
103256 NAD_1983_CORS96_StatePlane_Florida_North_FIPS_0903 PROJCS["NAD_1983_CORS96_StatePlane_Florida_North_FIPS_0903",GEOGCS["GCS_NA
103257 NAD_1983_CORS96_StatePlane_Florida_East_FIPS_0901_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Florida_East_FIPS_0901_Ft_US",GEOGCS["GC
103258 NAD_1983_CORS96_StatePlane_Florida_West_FIPS_0902_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Florida_West_FIPS_0902_Ft_US",GEOGCS["GC
103259 NAD_1983_CORS96_StatePlane_Florida_North_FIPS_0903_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Florida_North_FIPS_0903_Ft_US",GEOGCS["G
103260 NAD_1983_CORS96_StatePlane_Georgia_East_FIPS_1001 PROJCS["NAD_1983_CORS96_StatePlane_Georgia_East_FIPS_1001",GEOGCS["GCS_NA
103261 NAD_1983_CORS96_StatePlane_Georgia_West_FIPS_1002 PROJCS["NAD_1983_CORS96_StatePlane_Georgia_West_FIPS_1002",GEOGCS["GCS_NA
103262 NAD_1983_CORS96_StatePlane_Georgia_East_FIPS_1001_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Georgia_East_FIPS_1001_Ft_US",GEOGCS["G
103263 NAD_1983_CORS96_StatePlane_Georgia_West_FIPS_1002_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Georgia_West_FIPS_1002_Ft_US",GEOGCS["G
103264 NAD_1983_CORS96_StatePlane_Idaho_East_FIPS_1101 PROJCS["NAD_1983_CORS96_StatePlane_Idaho_East_FIPS_1101",GEOGCS["GCS_NAD_
103265 NAD_1983_CORS96_StatePlane_Idaho_Central_FIPS_1102 PROJCS["NAD_1983_CORS96_StatePlane_Idaho_Central_FIPS_1102",GEOGCS["GCS_NA
103266 NAD_1983_CORS96_StatePlane_Idaho_West_FIPS_1103 PROJCS["NAD_1983_CORS96_StatePlane_Idaho_West_FIPS_1103",GEOGCS["GCS_NAD_
103267 NAD_1983_CORS96_StatePlane_Idaho_East_FIPS_1101_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Idaho_East_FIPS_1101_Ft_US",GEOGCS["GCS
103268 NAD_1983_CORS96_StatePlane_Idaho_Central_FIPS_1102_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Idaho_Central_FIPS_1102_Ft_US",GEOGCS["G
103269 NAD_1983_CORS96_StatePlane_Idaho_West_FIPS_1103_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Idaho_West_FIPS_1103_Ft_US",GEOGCS["GCS
103270 NAD_1983_CORS96_StatePlane_Illinois_East_FIPS_1201 PROJCS["NAD_1983_CORS96_StatePlane_Illinois_East_FIPS_1201",GEOGCS["GCS_NAD
103271 NAD_1983_CORS96_StatePlane_Illinois_West_FIPS_1202 PROJCS["NAD_1983_CORS96_StatePlane_Illinois_West_FIPS_1202",GEOGCS["GCS_NAD
103272 NAD_1983_CORS96_StatePlane_Illinois_East_FIPS_1201_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Illinois_East_FIPS_1201_Ft_US",GEOGCS["GC
103273 NAD_1983_CORS96_StatePlane_Illinois_West_FIPS_1202_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Illinois_West_FIPS_1202_Ft_US",GEOGCS["GC
103274 NAD_1983_CORS96_StatePlane_Indiana_East_FIPS_1301 PROJCS["NAD_1983_CORS96_StatePlane_Indiana_East_FIPS_1301",GEOGCS["GCS_NAD
103275 NAD_1983_CORS96_StatePlane_Indiana_West_FIPS_1302 PROJCS["NAD_1983_CORS96_StatePlane_Indiana_West_FIPS_1302",GEOGCS["GCS_NA
103276 NAD_1983_CORS96_StatePlane_Indiana_East_FIPS_1301_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Indiana_East_FIPS_1301_Ft_US",GEOGCS["GC
103277 NAD_1983_CORS96_StatePlane_Indiana_West_FIPS_1302_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Indiana_West_FIPS_1302_Ft_US",GEOGCS["G
103278 NAD_1983_CORS96_StatePlane_Iowa_North_FIPS_1401 PROJCS["NAD_1983_CORS96_StatePlane_Iowa_North_FIPS_1401",GEOGCS["GCS_NAD_
103279 NAD_1983_CORS96_StatePlane_Iowa_South_FIPS_1402 PROJCS["NAD_1983_CORS96_StatePlane_Iowa_South_FIPS_1402",GEOGCS["GCS_NAD_
103280 NAD_1983_CORS96_StatePlane_Iowa_North_FIPS_1401_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Iowa_North_FIPS_1401_Ft_US",GEOGCS["GCS
103281 NAD_1983_CORS96_StatePlane_Iowa_South_FIPS_1402_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Iowa_South_FIPS_1402_Ft_US",GEOGCS["GC
103282 NAD_1983_CORS96_StatePlane_Kansas_North_FIPS_1501 PROJCS["NAD_1983_CORS96_StatePlane_Kansas_North_FIPS_1501",GEOGCS["GCS_NA
103283 NAD_1983_CORS96_StatePlane_Kansas_South_FIPS_1502 PROJCS["NAD_1983_CORS96_StatePlane_Kansas_South_FIPS_1502",GEOGCS["GCS_NA
103284 NAD_1983_CORS96_StatePlane_Kansas_North_FIPS_1501_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Kansas_North_FIPS_1501_Ft_US",GEOGCS["G
103285 NAD_1983_CORS96_StatePlane_Kansas_South_FIPS_1502_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Kansas_South_FIPS_1502_Ft_US",GEOGCS["G
103286 NAD_1983_CORS96_StatePlane_Kentucky_North_FIPS_1601 PROJCS["NAD_1983_CORS96_StatePlane_Kentucky_North_FIPS_1601",GEOGCS["GCS_N
103287 NAD_1983_CORS96_StatePlane_Kentucky_North_FIPS_1601_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Kentucky_North_FIPS_1601_Ft_US",GEOGCS["
103288 NAD_1983_CORS96_StatePlane_Kentucky_FIPS_1600 PROJCS["NAD_1983_CORS96_StatePlane_Kentucky_FIPS_1600",GEOGCS["GCS_NAD_19
103289 NAD_1983_CORS96_StatePlane_Kentucky_FIPS_1600_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Kentucky_FIPS_1600_Ft_US",GEOGCS["GCS_
103290 NAD_1983_CORS96_StatePlane_Kentucky_South_FIPS_1602 PROJCS["NAD_1983_CORS96_StatePlane_Kentucky_South_FIPS_1602",GEOGCS["GCS_N
103291 NAD_1983_CORS96_StatePlane_Kentucky_South_FIPS_1602_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Kentucky_South_FIPS_1602_Ft_US",GEOGCS[
103292 NAD_1983_CORS96_StatePlane_Louisiana_North_FIPS_1701 PROJCS["NAD_1983_CORS96_StatePlane_Louisiana_North_FIPS_1701",GEOGCS["GCS_N
103293 NAD_1983_CORS96_StatePlane_Louisiana_South_FIPS_1702 PROJCS["NAD_1983_CORS96_StatePlane_Louisiana_South_FIPS_1702",GEOGCS["GCS_
103294 NAD_1983_CORS96_StatePlane_Louisiana_North_FIPS_1701_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Louisiana_North_FIPS_1701_Ft_US",GEOGCS[
103295 NAD_1983_CORS96_StatePlane_Louisiana_South_FIPS_1702_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Louisiana_South_FIPS_1702_Ft_US",GEOGCS
103296 NAD_1983_CORS96_StatePlane_Maine_East_FIPS_1801 PROJCS["NAD_1983_CORS96_StatePlane_Maine_East_FIPS_1801",GEOGCS["GCS_NAD_
103297 NAD_1983_CORS96_StatePlane_Maine_West_FIPS_1802 PROJCS["NAD_1983_CORS96_StatePlane_Maine_West_FIPS_1802",GEOGCS["GCS_NAD

103298 NAD_1983_CORS96_StatePlane_Maine_East_FIPS_1801_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Maine_East_FIPS_1801_Ft_US",GEOGCS["GC

103299 NAD_1983_CORS96_StatePlane_Maine_West_FIPS_1802_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Maine_West_FIPS_1802_Ft_US",GEOGCS["GC
103300 NAD_1983_HARN_WISCRS_Adams_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Adams_County_Meters",GEOGCS["GCS_North_Ame
103301 NAD_1983_HARN_WISCRS_Ashland_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Ashland_County_Meters",GEOGCS["GCS_North_Am
103302 NAD_1983_HARN_WISCRS_Barron_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Barron_County_Meters",GEOGCS["GCS_North_Ame
103303 NAD_1983_HARN_WISCRS_Bayfield_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Bayfield_County_Meters",GEOGCS["GCS_North_Am
103304 NAD_1983_HARN_WISCRS_Brown_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Brown_County_Meters",GEOGCS["GCS_North_Ame
103305 NAD_1983_HARN_WISCRS_Buffalo_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Buffalo_County_Meters",GEOGCS["GCS_North_Ame
103306 NAD_1983_HARN_WISCRS_Burnett_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Burnett_County_Meters",GEOGCS["GCS_North_Am
103307 NAD_1983_HARN_WISCRS_Calumet_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Calumet_County_Meters",GEOGCS["GCS_North_Am
103308 NAD_1983_HARN_WISCRS_Chippewa_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Chippewa_County_Meters",GEOGCS["GCS_North_A
103309 NAD_1983_HARN_WISCRS_Clark_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Clark_County_Meters",GEOGCS["GCS_North_Amer
103310 NAD_1983_HARN_WISCRS_Columbia_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Columbia_County_Meters",GEOGCS["GCS_North_A
103311 NAD_1983_HARN_WISCRS_Crawford_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Crawford_County_Meters",GEOGCS["GCS_North_A
103312 NAD_1983_HARN_WISCRS_Dane_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Dane_County_Meters",GEOGCS["GCS_North_Amer
103313 NAD_1983_HARN_WISCRS_Dodge_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Dodge_County_Meters",GEOGCS["GCS_North_Ame
103314 NAD_1983_HARN_WISCRS_Door_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Door_County_Meters",GEOGCS["GCS_North_Ameri
103315 NAD_1983_HARN_WISCRS_Douglas_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Douglas_County_Meters",GEOGCS["GCS_North_Am
103316 NAD_1983_HARN_WISCRS_Dunn_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Dunn_County_Meters",GEOGCS["GCS_North_Amer
103317 NAD_1983_HARN_WISCRS_EauClaire_County_Meters PROJCS["NAD_1983_HARN_WISCRS_EauClaire_County_Meters",GEOGCS["GCS_North_A
103318 NAD_1983_HARN_WISCRS_Florence_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Florence_County_Meters",GEOGCS["GCS_North_Am
103319 NAD_1983_HARN_WISCRS_Fond_du_Lac_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Fond_du_Lac_County_Meters",GEOGCS["GCS_Nor
103320 NAD_1983_HARN_WISCRS_Forest_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Forest_County_Meters",GEOGCS["GCS_North_Ame
103321 NAD_1983_HARN_WISCRS_Grant_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Grant_County_Meters",GEOGCS["GCS_North_Amer
103322 NAD_1983_HARN_WISCRS_Green_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Green_County_Meters",GEOGCS["GCS_North_Ame
103323 NAD_1983_HARN_WISCRS_GreenLake_County_Meters PROJCS["NAD_1983_HARN_WISCRS_GreenLake_County_Meters",GEOGCS["GCS_North_
103324 NAD_1983_HARN_WISCRS_Iowa_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Iowa_County_Meters",GEOGCS["GCS_North_Ameri
103325 NAD_1983_HARN_WISCRS_Iron_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Iron_County_Meters",GEOGCS["GCS_North_Americ
103326 NAD_1983_HARN_WISCRS_Jackson_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Jackson_County_Meters",GEOGCS["GCS_North_Am
103327 NAD_1983_HARN_WISCRS_Jefferson_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Jefferson_County_Meters",GEOGCS["GCS_North_A
103328 NAD_1983_HARN_WISCRS_Juneau_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Juneau_County_Meters",GEOGCS["GCS_North_Am
103329 NAD_1983_HARN_WISCRS_Kenosha_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Kenosha_County_Meters",GEOGCS["GCS_North_Am
103330 NAD_1983_HARN_WISCRS_Kewaunee_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Kewaunee_County_Meters",GEOGCS["GCS_North_
103331 NAD_1983_HARN_WISCRS_LaCrosse_County_Meters PROJCS["NAD_1983_HARN_WISCRS_LaCrosse_County_Meters",GEOGCS["GCS_North_A
103332 NAD_1983_HARN_WISCRS_Lafayette_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Lafayette_County_Meters",GEOGCS["GCS_North_A
103333 NAD_1983_HARN_WISCRS_Langlade_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Langlade_County_Meters",GEOGCS["GCS_North_A
103334 NAD_1983_HARN_WISCRS_Lincoln_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Lincoln_County_Meters",GEOGCS["GCS_North_Ame
103335 NAD_1983_HARN_WISCRS_Manitowoc_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Manitowoc_County_Meters",GEOGCS["GCS_North_
103336 NAD_1983_HARN_WISCRS_Marathon_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Marathon_County_Meters",GEOGCS["GCS_North_A
103337 NAD_1983_HARN_WISCRS_Marinette_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Marinette_County_Meters",GEOGCS["GCS_North_A
103338 NAD_1983_HARN_WISCRS_Marquette_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Marquette_County_Meters",GEOGCS["GCS_North_A
103339 NAD_1983_HARN_WISCRS_Menominee_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Menominee_County_Meters",GEOGCS["GCS_North_
103340 NAD_1983_HARN_WISCRS_Milwaukee_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Milwaukee_County_Meters",GEOGCS["GCS_North_
103341 NAD_1983_HARN_WISCRS_Monroe_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Monroe_County_Meters",GEOGCS["GCS_North_Am
103342 NAD_1983_HARN_WISCRS_Oconto_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Oconto_County_Meters",GEOGCS["GCS_North_Am
103343 NAD_1983_HARN_WISCRS_Oneida_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Oneida_County_Meters",GEOGCS["GCS_North_Am
103344 NAD_1983_HARN_WISCRS_Outagamie_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Outagamie_County_Meters",GEOGCS["GCS_North_
103345 NAD_1983_HARN_WISCRS_Ozaukee_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Ozaukee_County_Meters",GEOGCS["GCS_North_Am
103346 NAD_1983_HARN_WISCRS_Pepin_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Pepin_County_Meters",GEOGCS["GCS_North_Amer
103347 NAD_1983_HARN_WISCRS_Pierce_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Pierce_County_Meters",GEOGCS["GCS_North_Ame
103348 NAD_1983_HARN_WISCRS_Polk_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Polk_County_Meters",GEOGCS["GCS_North_Americ
103349 NAD_1983_HARN_WISCRS_Portage_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Portage_County_Meters",GEOGCS["GCS_North_Am
103350 NAD_1983_HARN_WISCRS_Price_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Price_County_Meters",GEOGCS["GCS_North_Ameri
103351 NAD_1983_HARN_WISCRS_Racine_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Racine_County_Meters",GEOGCS["GCS_North_Ame

103352 NAD_1983_HARN_WISCRS_Richland_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Richland_County_Meters",GEOGCS["GCS_North_Am

103353 NAD_1983_HARN_WISCRS_Rock_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Rock_County_Meters",GEOGCS["GCS_North_Ameri
103354 NAD_1983_HARN_WISCRS_Rusk_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Rusk_County_Meters",GEOGCS["GCS_North_Ameri
103355 NAD_1983_HARN_WISCRS_Sauk_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Sauk_County_Meters",GEOGCS["GCS_North_Ameri
103356 NAD_1983_HARN_WISCRS_Sawyer_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Sawyer_County_Meters",GEOGCS["GCS_North_Am
103357 NAD_1983_HARN_WISCRS_Shawano_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Shawano_County_Meters",GEOGCS["GCS_North_A
103358 NAD_1983_HARN_WISCRS_Sheboygan_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Sheboygan_County_Meters",GEOGCS["GCS_North_
103359 NAD_1983_HARN_WISCRS_St_Croix_County_Meters PROJCS["NAD_1983_HARN_WISCRS_St_Croix_County_Meters",GEOGCS["GCS_North_Am
103360 NAD_1983_HARN_WISCRS_Taylor_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Taylor_County_Meters",GEOGCS["GCS_North_Ame
103361 NAD_1983_HARN_WISCRS_Trempealeau_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Trempealeau_County_Meters",GEOGCS["GCS_Nort
103362 NAD_1983_HARN_WISCRS_Vernon_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Vernon_County_Meters",GEOGCS["GCS_North_Ame
103363 NAD_1983_HARN_WISCRS_Vilas_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Vilas_County_Meters",GEOGCS["GCS_North_Ameri
103364 NAD_1983_HARN_WISCRS_Walworth_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Walworth_County_Meters",GEOGCS["GCS_North_A
103365 NAD_1983_HARN_WISCRS_Washburn_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Washburn_County_Meters",GEOGCS["GCS_North_A
103366 NAD_1983_HARN_WISCRS_Washington_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Washington_County_Meters",GEOGCS["GCS_North_
103367 NAD_1983_HARN_WISCRS_Waukesha_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Waukesha_County_Meters",GEOGCS["GCS_North_A
103368 NAD_1983_HARN_WISCRS_Waupaca_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Waupaca_County_Meters",GEOGCS["GCS_North_A
103369 NAD_1983_HARN_WISCRS_Waushara_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Waushara_County_Meters",GEOGCS["GCS_North_A
103370 NAD_1983_HARN_WISCRS_Winnebago_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Winnebago_County_Meters",GEOGCS["GCS_North_
103371 NAD_1983_HARN_WISCRS_Wood_County_Meters PROJCS["NAD_1983_HARN_WISCRS_Wood_County_Meters",GEOGCS["GCS_North_Amer
103372 NAD_1983_CORS96_Maine_2000_East_Zone PROJCS["NAD_1983_CORS96_Maine_2000_East_Zone",GEOGCS["GCS_NAD_1983_COR
103373 NAD_1983_CORS96_Maine_2000_Central_Zone PROJCS["NAD_1983_CORS96_Maine_2000_Central_Zone",GEOGCS["GCS_NAD_1983_CO
103374 NAD_1983_CORS96_Maine_2000_West_Zone PROJCS["NAD_1983_CORS96_Maine_2000_West_Zone",GEOGCS["GCS_NAD_1983_COR
103375 NAD_1983_CORS96_StatePlane_Maryland_FIPS_1900 PROJCS["NAD_1983_CORS96_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_NAD_19
103376 NAD_1983_CORS96_StatePlane_Maryland_FIPS_1900_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Maryland_FIPS_1900_Ft_US",GEOGCS["GCS_
103377 NAD_1983_CORS96_StatePlane_Massachusetts_Mainland_FIPS_2001 PROJCS["NAD_1983_CORS96_StatePlane_Massachusetts_Mainland_FIPS_2001",GEOGCS
103378 NAD_1983_CORS96_StatePlane_Massachusetts_Island_FIPS_2002 PROJCS["NAD_1983_CORS96_StatePlane_Massachusetts_Island_FIPS_2002",GEOGCS["G
103379 NAD_1983_CORS96_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS PROJCS["NAD_1983_CORS96_StatePlane_Massachusetts_Mnld_FIPS_2001_FtUS",GEOG
103380 NAD_1983_CORS96_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS PROJCS["NAD_1983_CORS96_StatePlane_Massachusetts_Isl_FIPS_2002_FtUS",GEOGCS
103381 NAD_1983_CORS96_StatePlane_Michigan_North_FIPS_2111 PROJCS["NAD_1983_CORS96_StatePlane_Michigan_North_FIPS_2111",GEOGCS["GCS_N
103382 NAD_1983_CORS96_StatePlane_Michigan_Central_FIPS_2112 PROJCS["NAD_1983_CORS96_StatePlane_Michigan_Central_FIPS_2112",GEOGCS["GCS_
103383 NAD_1983_CORS96_StatePlane_Michigan_South_FIPS_2113 PROJCS["NAD_1983_CORS96_StatePlane_Michigan_South_FIPS_2113",GEOGCS["GCS_N
103384 NAD_1983_CORS96_StatePlane_Michigan_North_FIPS_2111_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Michigan_North_FIPS_2111_Ft_Intl",GEOGCS["
103385 NAD_1983_CORS96_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Michigan_Central_FIPS_2112_Ft_Intl",GEOGCS
103386 NAD_1983_CORS96_StatePlane_Michigan_South_FIPS_2113_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Michigan_South_FIPS_2113_Ft_Intl",GEOGCS["
103387 NAD_1983_CORS96_StatePlane_Minnesota_North_FIPS_2201 PROJCS["NAD_1983_CORS96_StatePlane_Minnesota_North_FIPS_2201",GEOGCS["GCS_
103388 NAD_1983_CORS96_StatePlane_Minnesota_Central_FIPS_2202 PROJCS["NAD_1983_CORS96_StatePlane_Minnesota_Central_FIPS_2202",GEOGCS["GCS
103389 NAD_1983_CORS96_StatePlane_Minnesota_South_FIPS_2203 PROJCS["NAD_1983_CORS96_StatePlane_Minnesota_South_FIPS_2203",GEOGCS["GCS_
103390 NAD_1983_CORS96_StatePlane_Minnesota_North_FIPS_2201_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Minnesota_North_FIPS_2201_Ft_US",GEOGCS
103391 NAD_1983_CORS96_StatePlane_Minnesota_Central_FIPS_2202_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Minnesota_Central_FIPS_2202_Ft_US",GEOGC
103392 NAD_1983_CORS96_StatePlane_Minnesota_South_FIPS_2203_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Minnesota_South_FIPS_2203_Ft_US",GEOGCS
103393 NAD_1983_CORS96_StatePlane_Mississippi_East_FIPS_2301 PROJCS["NAD_1983_CORS96_StatePlane_Mississippi_East_FIPS_2301",GEOGCS["GCS_N
103394 NAD_1983_CORS96_StatePlane_Mississippi_West_FIPS_2302 PROJCS["NAD_1983_CORS96_StatePlane_Mississippi_West_FIPS_2302",GEOGCS["GCS_
103395 NAD_1983_CORS96_StatePlane_Mississippi_East_FIPS_2301_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Mississippi_East_FIPS_2301_Ft_US",GEOGCS[
103396 NAD_1983_CORS96_StatePlane_Mississippi_West_FIPS_2302_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Mississippi_West_FIPS_2302_Ft_US",GEOGCS
103397 NAD_1983_CORS96_StatePlane_Missouri_East_FIPS_2401 PROJCS["NAD_1983_CORS96_StatePlane_Missouri_East_FIPS_2401",GEOGCS["GCS_NA
103398 NAD_1983_CORS96_StatePlane_Missouri_Central_FIPS_2402 PROJCS["NAD_1983_CORS96_StatePlane_Missouri_Central_FIPS_2402",GEOGCS["GCS_
103399 NAD_1983_CORS96_StatePlane_Missouri_West_FIPS_2403 PROJCS["NAD_1983_CORS96_StatePlane_Missouri_West_FIPS_2403",GEOGCS["GCS_NA
103400 NAD_1983_HARN_WISCRS_Adams_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Adams_County_Feet",GEOGCS["GCS_North_Americ
103401 NAD_1983_HARN_WISCRS_Ashland_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Ashland_County_Feet",GEOGCS["GCS_North_Amer
103402 NAD_1983_HARN_WISCRS_Barron_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Barron_County_Feet",GEOGCS["GCS_North_Americ
103403 NAD_1983_HARN_WISCRS_Bayfield_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Bayfield_County_Feet",GEOGCS["GCS_North_Amer
103404 NAD_1983_HARN_WISCRS_Brown_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Brown_County_Feet",GEOGCS["GCS_North_Americ
103405 NAD_1983_HARN_WISCRS_Buffalo_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Buffalo_County_Feet",GEOGCS["GCS_North_Americ

103406 NAD_1983_HARN_WISCRS_Burnett_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Burnett_County_Feet",GEOGCS["GCS_North_Ameri

103407 NAD_1983_HARN_WISCRS_Calumet_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Calumet_County_Feet",GEOGCS["GCS_North_Ame
103408 NAD_1983_HARN_WISCRS_Chippewa_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Chippewa_County_Feet",GEOGCS["GCS_North_Am
103409 NAD_1983_HARN_WISCRS_Clark_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Clark_County_Feet",GEOGCS["GCS_North_America
103410 NAD_1983_HARN_WISCRS_Columbia_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Columbia_County_Feet",GEOGCS["GCS_North_Ame
103411 NAD_1983_HARN_WISCRS_Crawford_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Crawford_County_Feet",GEOGCS["GCS_North_Ame
103412 NAD_1983_HARN_WISCRS_Dane_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Dane_County_Feet",GEOGCS["GCS_North_America
103413 NAD_1983_HARN_WISCRS_Dodge_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Dodge_County_Feet",GEOGCS["GCS_North_Americ
103414 NAD_1983_HARN_WISCRS_Door_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Door_County_Feet",GEOGCS["GCS_North_America
103415 NAD_1983_HARN_WISCRS_Douglas_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Douglas_County_Feet",GEOGCS["GCS_North_Amer
103416 NAD_1983_HARN_WISCRS_Dunn_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Dunn_County_Feet",GEOGCS["GCS_North_America
103417 NAD_1983_HARN_WISCRS_EauClaire_County_Feet PROJCS["NAD_1983_HARN_WISCRS_EauClaire_County_Feet",GEOGCS["GCS_North_Am
103418 NAD_1983_HARN_WISCRS_Florence_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Florence_County_Feet",GEOGCS["GCS_North_Ame
103419 NAD_1983_HARN_WISCRS_Fond_du_Lac_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Fond_du_Lac_County_Feet",GEOGCS["GCS_North_
103420 NAD_1983_HARN_WISCRS_Forest_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Forest_County_Feet",GEOGCS["GCS_North_Americ
103421 NAD_1983_HARN_WISCRS_Grant_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Grant_County_Feet",GEOGCS["GCS_North_America
103422 NAD_1983_HARN_WISCRS_Green_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Green_County_Feet",GEOGCS["GCS_North_Americ
103423 NAD_1983_HARN_WISCRS_GreenLake_County_Feet PROJCS["NAD_1983_HARN_WISCRS_GreenLake_County_Feet",GEOGCS["GCS_North_Am
103424 NAD_1983_HARN_WISCRS_Iowa_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Iowa_County_Feet",GEOGCS["GCS_North_America
103425 NAD_1983_HARN_WISCRS_Iron_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Iron_County_Feet",GEOGCS["GCS_North_American
103426 NAD_1983_HARN_WISCRS_Jackson_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Jackson_County_Feet",GEOGCS["GCS_North_Amer
103427 NAD_1983_HARN_WISCRS_Jefferson_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Jefferson_County_Feet",GEOGCS["GCS_North_Ame
103428 NAD_1983_HARN_WISCRS_Juneau_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Juneau_County_Feet",GEOGCS["GCS_North_Ameri
103429 NAD_1983_HARN_WISCRS_Kenosha_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Kenosha_County_Feet",GEOGCS["GCS_North_Ame
103430 NAD_1983_HARN_WISCRS_Kewaunee_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Kewaunee_County_Feet",GEOGCS["GCS_North_Am
103431 NAD_1983_HARN_WISCRS_LaCrosse_County_Feet PROJCS["NAD_1983_HARN_WISCRS_LaCrosse_County_Feet",GEOGCS["GCS_North_Am
103432 NAD_1983_HARN_WISCRS_Lafayette_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Lafayette_County_Feet",GEOGCS["GCS_North_Ame
103433 NAD_1983_HARN_WISCRS_Langlade_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Langlade_County_Feet",GEOGCS["GCS_North_Ame
103434 NAD_1983_HARN_WISCRS_Lincoln_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Lincoln_County_Feet",GEOGCS["GCS_North_Ameri
103435 NAD_1983_HARN_WISCRS_Manitowoc_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Manitowoc_County_Feet",GEOGCS["GCS_North_Am
103436 NAD_1983_HARN_WISCRS_Marathon_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Marathon_County_Feet",GEOGCS["GCS_North_Ame
103437 NAD_1983_HARN_WISCRS_Marinette_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Marinette_County_Feet",GEOGCS["GCS_North_Ame
103438 NAD_1983_HARN_WISCRS_Marquette_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Marquette_County_Feet",GEOGCS["GCS_North_Am
103439 NAD_1983_HARN_WISCRS_Menominee_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Menominee_County_Feet",GEOGCS["GCS_North_A
103440 NAD_1983_HARN_WISCRS_Milwaukee_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Milwaukee_County_Feet",GEOGCS["GCS_North_Am
103441 NAD_1983_HARN_WISCRS_Monroe_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Monroe_County_Feet",GEOGCS["GCS_North_Amer
103442 NAD_1983_HARN_WISCRS_Oconto_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Oconto_County_Feet",GEOGCS["GCS_North_Ameri
103443 NAD_1983_HARN_WISCRS_Oneida_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Oneida_County_Feet",GEOGCS["GCS_North_Ameri
103444 NAD_1983_HARN_WISCRS_Outagamie_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Outagamie_County_Feet",GEOGCS["GCS_North_Am
103445 NAD_1983_HARN_WISCRS_Ozaukee_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Ozaukee_County_Feet",GEOGCS["GCS_North_Ame
103446 NAD_1983_HARN_WISCRS_Pepin_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Pepin_County_Feet",GEOGCS["GCS_North_America
103447 NAD_1983_HARN_WISCRS_Pierce_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Pierce_County_Feet",GEOGCS["GCS_North_Americ
103448 NAD_1983_HARN_WISCRS_Polk_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Polk_County_Feet",GEOGCS["GCS_North_American
103449 NAD_1983_HARN_WISCRS_Portage_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Portage_County_Feet",GEOGCS["GCS_North_Amer
103450 NAD_1983_HARN_WISCRS_Price_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Price_County_Feet",GEOGCS["GCS_North_America
103451 NAD_1983_HARN_WISCRS_Racine_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Racine_County_Feet",GEOGCS["GCS_North_Americ
103452 NAD_1983_HARN_WISCRS_Richland_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Richland_County_Feet",GEOGCS["GCS_North_Ame
103453 NAD_1983_HARN_WISCRS_Rock_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Rock_County_Feet",GEOGCS["GCS_North_America
103454 NAD_1983_HARN_WISCRS_Rusk_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Rusk_County_Feet",GEOGCS["GCS_North_America
103455 NAD_1983_HARN_WISCRS_Sauk_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Sauk_County_Feet",GEOGCS["GCS_North_America
103456 NAD_1983_HARN_WISCRS_Sawyer_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Sawyer_County_Feet",GEOGCS["GCS_North_Ameri
103457 NAD_1983_HARN_WISCRS_Shawano_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Shawano_County_Feet",GEOGCS["GCS_North_Ame
103458 NAD_1983_HARN_WISCRS_Sheboygan_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Sheboygan_County_Feet",GEOGCS["GCS_North_Am
103459 NAD_1983_HARN_WISCRS_St_Croix_County_Feet PROJCS["NAD_1983_HARN_WISCRS_St_Croix_County_Feet",GEOGCS["GCS_North_Ame

103460 NAD_1983_HARN_WISCRS_Taylor_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Taylor_County_Feet",GEOGCS["GCS_North_Americ

103461 NAD_1983_HARN_WISCRS_Trempealeau_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Trempealeau_County_Feet",GEOGCS["GCS_North_
103462 NAD_1983_HARN_WISCRS_Vernon_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Vernon_County_Feet",GEOGCS["GCS_North_Ameri
103463 NAD_1983_HARN_WISCRS_Vilas_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Vilas_County_Feet",GEOGCS["GCS_North_America
103464 NAD_1983_HARN_WISCRS_Walworth_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Walworth_County_Feet",GEOGCS["GCS_North_Ame
103465 NAD_1983_HARN_WISCRS_Washburn_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Washburn_County_Feet",GEOGCS["GCS_North_Am
103466 NAD_1983_HARN_WISCRS_Washington_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Washington_County_Feet",GEOGCS["GCS_North_A
103467 NAD_1983_HARN_WISCRS_Waukesha_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Waukesha_County_Feet",GEOGCS["GCS_North_Am
103468 NAD_1983_HARN_WISCRS_Waupaca_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Waupaca_County_Feet",GEOGCS["GCS_North_Ame
103469 NAD_1983_HARN_WISCRS_Waushara_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Waushara_County_Feet",GEOGCS["GCS_North_Am
103470 NAD_1983_HARN_WISCRS_Winnebago_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Winnebago_County_Feet",GEOGCS["GCS_North_Am
103471 NAD_1983_HARN_WISCRS_Wood_County_Feet PROJCS["NAD_1983_HARN_WISCRS_Wood_County_Feet",GEOGCS["GCS_North_America
103472 NAD_1983_CORS96_StatePlane_Montana_FIPS_2500 PROJCS["NAD_1983_CORS96_StatePlane_Montana_FIPS_2500",GEOGCS["GCS_NAD_19
103473 NAD_1983_CORS96_StatePlane_Montana_FIPS_2500_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Montana_FIPS_2500_Ft_Intl",GEOGCS["GCS_N
103474 NAD_1983_CORS96_StatePlane_Nebraska_FIPS_2600 PROJCS["NAD_1983_CORS96_StatePlane_Nebraska_FIPS_2600",GEOGCS["GCS_NAD_1
103475 NAD_1983_CORS96_StatePlane_Nebraska_FIPS_2600_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Nebraska_FIPS_2600_Ft_US",GEOGCS["GCS_
103476 NAD_1983_CORS96_StatePlane_Nevada_East_FIPS_2701 PROJCS["NAD_1983_CORS96_StatePlane_Nevada_East_FIPS_2701",GEOGCS["GCS_NAD
103477 NAD_1983_CORS96_StatePlane_Nevada_Central_FIPS_2702 PROJCS["NAD_1983_CORS96_StatePlane_Nevada_Central_FIPS_2702",GEOGCS["GCS_N
103478 NAD_1983_CORS96_StatePlane_Nevada_West_FIPS_2703 PROJCS["NAD_1983_CORS96_StatePlane_Nevada_West_FIPS_2703",GEOGCS["GCS_NA
103479 NAD_1983_CORS96_StatePlane_Nevada_East_FIPS_2701_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Nevada_East_FIPS_2701_Ft_US",GEOGCS["G
103480 NAD_1983_CORS96_StatePlane_Nevada_Central_FIPS_2702_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Nevada_Central_FIPS_2702_Ft_US",GEOGCS[
103481 NAD_1983_CORS96_StatePlane_Nevada_West_FIPS_2703_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Nevada_West_FIPS_2703_Ft_US",GEOGCS["G
103482 NAD_1983_CORS96_StatePlane_New_Hampshire_FIPS_2800 PROJCS["NAD_1983_CORS96_StatePlane_New_Hampshire_FIPS_2800",GEOGCS["GCS_N
103483 NAD_1983_CORS96_StatePlane_New_Hampshire_FIPS_2800_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_Hampshire_FIPS_2800_Ft_US",GEOGCS[
103484 NAD_1983_CORS96_StatePlane_New_Jersey_FIPS_2900 PROJCS["NAD_1983_CORS96_StatePlane_New_Jersey_FIPS_2900",GEOGCS["GCS_NAD
103485 NAD_1983_CORS96_StatePlane_New_Jersey_FIPS_2900_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_Jersey_FIPS_2900_Ft_US",GEOGCS["GC
103486 NAD_1983_CORS96_StatePlane_New_Mexico_East_FIPS_3001 PROJCS["NAD_1983_CORS96_StatePlane_New_Mexico_East_FIPS_3001",GEOGCS["GCS
103487 NAD_1983_CORS96_StatePlane_New_Mexico_Central_FIPS_3002 PROJCS["NAD_1983_CORS96_StatePlane_New_Mexico_Central_FIPS_3002",GEOGCS["G
103488 NAD_1983_CORS96_StatePlane_New_Mexico_West_FIPS_3003 PROJCS["NAD_1983_CORS96_StatePlane_New_Mexico_West_FIPS_3003",GEOGCS["GCS
103489 NAD_1983_CORS96_StatePlane_New_Mexico_East_FIPS_3001_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_Mexico_East_FIPS_3001_Ft_US",GEOGC
103490 NAD_1983_CORS96_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_Mexico_Central_FIPS_3002_Ft_US",GEOG
103491 NAD_1983_CORS96_StatePlane_New_Mexico_West_FIPS_3003_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_Mexico_West_FIPS_3003_Ft_US",GEOGC
103492 NAD_1983_CORS96_StatePlane_New_York_East_FIPS_3101 PROJCS["NAD_1983_CORS96_StatePlane_New_York_East_FIPS_3101",GEOGCS["GCS_N
103493 NAD_1983_CORS96_StatePlane_New_York_Central_FIPS_3102 PROJCS["NAD_1983_CORS96_StatePlane_New_York_Central_FIPS_3102",GEOGCS["GCS
103494 NAD_1983_CORS96_StatePlane_New_York_West_FIPS_3103 PROJCS["NAD_1983_CORS96_StatePlane_New_York_West_FIPS_3103",GEOGCS["GCS_N
103495 NAD_1983_CORS96_StatePlane_New_York_Long_Island_FIPS_3104 PROJCS["NAD_1983_CORS96_StatePlane_New_York_Long_Island_FIPS_3104",GEOGCS[
103496 NAD_1983_CORS96_StatePlane_New_York_East_FIPS_3101_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_York_East_FIPS_3101_Ft_US",GEOGCS["
103497 NAD_1983_CORS96_StatePlane_New_York_Central_FIPS_3102_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_York_Central_FIPS_3102_Ft_US",GEOGC
103498 NAD_1983_CORS96_StatePlane_New_York_West_FIPS_3103_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_York_West_FIPS_3103_Ft_US",GEOGCS[
103499 NAD_1983_CORS96_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_New_York_Long_Isl_FIPS_3104_Ft_US",GEOG
103500 NAD_1983_CORS96_StatePlane_North_Carolina_FIPS_3200 PROJCS["NAD_1983_CORS96_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_N
103501 NAD_1983_CORS96_StatePlane_North_Carolina_FIPS_3200_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_North_Carolina_FIPS_3200_Ft_US",GEOGCS["G
103502 NAD_1983_CORS96_StatePlane_North_Dakota_North_FIPS_3301 PROJCS["NAD_1983_CORS96_StatePlane_North_Dakota_North_FIPS_3301",GEOGCS["GC
103503 NAD_1983_CORS96_StatePlane_North_Dakota_South_FIPS_3302 PROJCS["NAD_1983_CORS96_StatePlane_North_Dakota_South_FIPS_3302",GEOGCS["GC
103504 NAD_1983_CORS96_StatePlane_North_Dakota_North_FIPS_3301_FtI PROJCS["NAD_1983_CORS96_StatePlane_North_Dakota_North_FIPS_3301_FtI",GEOGCS
103505 NAD_1983_CORS96_StatePlane_North_Dakota_South_FIPS_3302_FtI PROJCS["NAD_1983_CORS96_StatePlane_North_Dakota_South_FIPS_3302_FtI",GEOGCS
103506 NAD_1983_CORS96_StatePlane_Ohio_North_FIPS_3401 PROJCS["NAD_1983_CORS96_StatePlane_Ohio_North_FIPS_3401",GEOGCS["GCS_NAD_
103507 NAD_1983_CORS96_StatePlane_Ohio_South_FIPS_3402 PROJCS["NAD_1983_CORS96_StatePlane_Ohio_South_FIPS_3402",GEOGCS["GCS_NAD_
103508 NAD_1983_CORS96_StatePlane_Ohio_North_FIPS_3401_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Ohio_North_FIPS_3401_Ft_US",GEOGCS["GCS
103509 NAD_1983_CORS96_StatePlane_Ohio_South_FIPS_3402_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Ohio_South_FIPS_3402_Ft_US",GEOGCS["GC
103510 NAD_1983_CORS96_StatePlane_Oklahoma_North_FIPS_3501 PROJCS["NAD_1983_CORS96_StatePlane_Oklahoma_North_FIPS_3501",GEOGCS["GCS_
103511 NAD_1983_CORS96_StatePlane_Oklahoma_South_FIPS_3502 PROJCS["NAD_1983_CORS96_StatePlane_Oklahoma_South_FIPS_3502",GEOGCS["GCS_
103512 NAD_1983_CORS96_StatePlane_Oklahoma_North_FIPS_3501_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Oklahoma_North_FIPS_3501_Ft_US",GEOGCS
103513 NAD_1983_CORS96_StatePlane_Oklahoma_South_FIPS_3502_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Oklahoma_South_FIPS_3502_Ft_US",GEOGCS

103514 NAD_1983_CORS96_StatePlane_Pennsylvania_North_FIPS_3701 PROJCS["NAD_1983_CORS96_StatePlane_Pennsylvania_North_FIPS_3701",GEOGCS["GC

103515 NAD_1983_CORS96_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Pennsylvania_North_FIPS_3701_Ft_US",GEOG
103516 NAD_1983_CORS96_StatePlane_Pennsylvania_South_FIPS_3702 PROJCS["NAD_1983_CORS96_StatePlane_Pennsylvania_South_FIPS_3702",GEOGCS["GC
103517 NAD_1983_CORS96_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Pennsylvania_South_FIPS_3702_Ft_US",GEOG
103518 NAD_1983_CORS96_StatePlane_Rhode_Island_FIPS_3800 PROJCS["NAD_1983_CORS96_StatePlane_Rhode_Island_FIPS_3800",GEOGCS["GCS_NA
103519 NAD_1983_CORS96_StatePlane_Rhode_Island_FIPS_3800_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Rhode_Island_FIPS_3800_Ft_US",GEOGCS["G
103520 NAD_1983_CORS96_StatePlane_South_Carolina_FIPS_3900 PROJCS["NAD_1983_CORS96_StatePlane_South_Carolina_FIPS_3900",GEOGCS["GCS_N
103521 NAD_1983_CORS96_StatePlane_South_Carolina_FIPS_3900_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_South_Carolina_FIPS_3900_Ft_Intl",GEOGCS["
103522 NAD_1983_CORS96_StatePlane_South_Dakota_North_FIPS_4001 PROJCS["NAD_1983_CORS96_StatePlane_South_Dakota_North_FIPS_4001",GEOGCS["GC
103523 NAD_1983_CORS96_StatePlane_South_Dakota_South_FIPS_4002 PROJCS["NAD_1983_CORS96_StatePlane_South_Dakota_South_FIPS_4002",GEOGCS["G
103524 NAD_1983_CORS96_StatePlane_South_Dakota_North_FIPS_4001_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_South_Dakota_North_FIPS_4001_Ft_US",GEOG
103525 NAD_1983_CORS96_StatePlane_South_Dakota_South_FIPS_4002_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_South_Dakota_South_FIPS_4002_Ft_US",GEOG
103526 NAD_1983_CORS96_StatePlane_Tennessee_FIPS_4100 PROJCS["NAD_1983_CORS96_StatePlane_Tennessee_FIPS_4100",GEOGCS["GCS_NAD_
103527 NAD_1983_CORS96_StatePlane_Tennessee_FIPS_4100_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Tennessee_FIPS_4100_Ft_US",GEOGCS["GCS
103539 NAD_1983_CORS96_StatePlane_Texas_North_FIPS_4201 PROJCS["NAD_1983_CORS96_StatePlane_Texas_North_FIPS_4201",GEOGCS["GCS_NAD
103540 NAD_1983_CORS96_StatePlane_Texas_North_Central_FIPS_4202 PROJCS["NAD_1983_CORS96_StatePlane_Texas_North_Central_FIPS_4202",GEOGCS["G
103541 NAD_1983_CORS96_StatePlane_Texas_Central_FIPS_4203 PROJCS["NAD_1983_CORS96_StatePlane_Texas_Central_FIPS_4203",GEOGCS["GCS_NA
103542 NAD_1983_CORS96_StatePlane_Texas_South_Central_FIPS_4204 PROJCS["NAD_1983_CORS96_StatePlane_Texas_South_Central_FIPS_4204",GEOGCS["G
103543 NAD_1983_CORS96_StatePlane_Texas_South_FIPS_4205 PROJCS["NAD_1983_CORS96_StatePlane_Texas_South_FIPS_4205",GEOGCS["GCS_NAD
103544 NAD_1983_CORS96_StatePlane_Texas_North_FIPS_4201_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Texas_North_FIPS_4201_Ft_US",GEOGCS["GC
103545 NAD_1983_CORS96_StatePlane_Texas_North_Central_FIPS_4202_FtUS PROJCS["NAD_1983_CORS96_StatePlane_Texas_North_Central_FIPS_4202_FtUS",GEOG
103546 NAD_1983_CORS96_StatePlane_Texas_Central_FIPS_4203_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Texas_Central_FIPS_4203_Ft_US",GEOGCS["G
103547 NAD_1983_CORS96_StatePlane_Texas_South_Central_FIPS_4204_FtUS PROJCS["NAD_1983_CORS96_StatePlane_Texas_South_Central_FIPS_4204_FtUS",GEOG
103548 NAD_1983_CORS96_StatePlane_Texas_South_FIPS_4205_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Texas_South_FIPS_4205_Ft_US",GEOGCS["GC
103549 NAD_1983_CORS96_StatePlane_Utah_North_FIPS_4301 PROJCS["NAD_1983_CORS96_StatePlane_Utah_North_FIPS_4301",GEOGCS["GCS_NAD_
103550 NAD_1983_CORS96_StatePlane_Utah_Central_FIPS_4302 PROJCS["NAD_1983_CORS96_StatePlane_Utah_Central_FIPS_4302",GEOGCS["GCS_NAD
103551 NAD_1983_CORS96_StatePlane_Utah_South_FIPS_4303 PROJCS["NAD_1983_CORS96_StatePlane_Utah_South_FIPS_4303",GEOGCS["GCS_NAD_
103552 NAD_1983_CORS96_StatePlane_Utah_North_FIPS_4301_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Utah_North_FIPS_4301_Ft_Intl",GEOGCS["GCS
103553 NAD_1983_CORS96_StatePlane_Utah_Central_FIPS_4302_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Utah_Central_FIPS_4302_Ft_Intl",GEOGCS["GC
103554 NAD_1983_CORS96_StatePlane_Utah_South_FIPS_4303_Ft_Intl PROJCS["NAD_1983_CORS96_StatePlane_Utah_South_FIPS_4303_Ft_Intl",GEOGCS["GCS
103555 NAD_1983_CORS96_StatePlane_Utah_North_FIPS_4301_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Utah_North_FIPS_4301_Ft_US",GEOGCS["GCS
103556 NAD_1983_CORS96_StatePlane_Utah_Central_FIPS_4302_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Utah_Central_FIPS_4302_Ft_US",GEOGCS["GC
103557 NAD_1983_CORS96_StatePlane_Utah_South_FIPS_4303_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Utah_South_FIPS_4303_Ft_US",GEOGCS["GC
103558 NAD_1983_CORS96_StatePlane_Vermont_FIPS_4400 PROJCS["NAD_1983_CORS96_StatePlane_Vermont_FIPS_4400",GEOGCS["GCS_NAD_19
103559 NAD_1983_CORS96_StatePlane_Virginia_North_FIPS_4501 PROJCS["NAD_1983_CORS96_StatePlane_Virginia_North_FIPS_4501",GEOGCS["GCS_NA
103560 NAD_1983_CORS96_StatePlane_Virginia_South_FIPS_4502 PROJCS["NAD_1983_CORS96_StatePlane_Virginia_South_FIPS_4502",GEOGCS["GCS_NA
103561 NAD_1983_CORS96_StatePlane_Virginia_North_FIPS_4501_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Virginia_North_FIPS_4501_Ft_US",GEOGCS["G
103562 NAD_1983_CORS96_StatePlane_Virginia_South_FIPS_4502_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Virginia_South_FIPS_4502_Ft_US",GEOGCS["G
103563 NAD_1983_CORS96_StatePlane_Washington_North_FIPS_4601 PROJCS["NAD_1983_CORS96_StatePlane_Washington_North_FIPS_4601",GEOGCS["GCS
103564 NAD_1983_CORS96_StatePlane_Washington_South_FIPS_4602 PROJCS["NAD_1983_CORS96_StatePlane_Washington_South_FIPS_4602",GEOGCS["GCS
103565 NAD_1983_CORS96_StatePlane_Washington_North_FIPS_4601_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Washington_North_FIPS_4601_Ft_US",GEOGC
103566 NAD_1983_CORS96_StatePlane_Washington_South_FIPS_4602_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Washington_South_FIPS_4602_Ft_US",GEOGC
103567 NAD_1983_CORS96_StatePlane_West_Virginia_North_FIPS_4701 PROJCS["NAD_1983_CORS96_StatePlane_West_Virginia_North_FIPS_4701",GEOGCS["GC
103568 NAD_1983_CORS96_StatePlane_West_Virginia_South_FIPS_4702 PROJCS["NAD_1983_CORS96_StatePlane_West_Virginia_South_FIPS_4702",GEOGCS["GC
103569 NAD_1983_CORS96_StatePlane_West_Virginia_North_FIPS_4701_FtUS PROJCS["NAD_1983_CORS96_StatePlane_West_Virginia_North_FIPS_4701_FtUS",GEOGC
103570 NAD_1983_CORS96_StatePlane_West_Virginia_South_FIPS_4702_FtUS PROJCS["NAD_1983_CORS96_StatePlane_West_Virginia_South_FIPS_4702_FtUS",GEOGC
103571 NAD_1983_CORS96_StatePlane_Wisconsin_North_FIPS_4801 PROJCS["NAD_1983_CORS96_StatePlane_Wisconsin_North_FIPS_4801",GEOGCS["GCS_
103572 NAD_1983_CORS96_StatePlane_Wisconsin_Central_FIPS_4802 PROJCS["NAD_1983_CORS96_StatePlane_Wisconsin_Central_FIPS_4802",GEOGCS["GCS
103573 NAD_1983_CORS96_StatePlane_Wisconsin_South_FIPS_4803 PROJCS["NAD_1983_CORS96_StatePlane_Wisconsin_South_FIPS_4803",GEOGCS["GCS_
103574 NAD_1983_CORS96_StatePlane_Wisconsin_North_FIPS_4801_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Wisconsin_North_FIPS_4801_Ft_US",GEOGCS
103575 NAD_1983_CORS96_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Wisconsin_Central_FIPS_4802_Ft_US",GEOGC
103576 NAD_1983_CORS96_StatePlane_Wisconsin_South_FIPS_4803_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Wisconsin_South_FIPS_4803_Ft_US",GEOGCS
103577 NAD_1983_CORS96_StatePlane_Wyoming_East_FIPS_4901 PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_East_FIPS_4901",GEOGCS["GCS_N
103578 NAD_1983_CORS96_StatePlane_Wyoming_East_Central_FIPS_4902 PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_East_Central_FIPS_4902",GEOGCS[

103579 NAD_1983_CORS96_StatePlane_Wyoming_West_Central_FIPS_4903 PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_West_Central_FIPS_4903",GEOGCS[

103580 NAD_1983_CORS96_StatePlane_Wyoming_West_FIPS_4904 PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_West_FIPS_4904",GEOGCS["GCS_N
103581 NAD_1983_CORS96_StatePlane_Wyoming_East_FIPS_4901_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_East_FIPS_4901_Ft_US",GEOGCS["G
103582 NAD_1983_CORS96_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_E_Central_FIPS_4902_Ft_US",GEOG
103583 NAD_1983_CORS96_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_W_Central_FIPS_4903_Ft_US",GEOG
103585 NAD_1983_CORS96_StatePlane_Wyoming_West_FIPS_4904_Ft_US PROJCS["NAD_1983_CORS96_StatePlane_Wyoming_West_FIPS_4904_Ft_US",GEOGCS["
103600 NAD_1983_HARN_Adj_MN_Aitkin_Meters PROJCS["NAD_1983_HARN_Adj_MN_Aitkin_Meters",GEOGCS["GCS_North_American_198
103601 NAD_1983_HARN_Adj_MN_Clay_Meters PROJCS["NAD_1983_HARN_Adj_MN_Clay_Meters",GEOGCS["GCS_North_American_1983
103602 NAD_1983_HARN_Adj_MN_Clearwater_Meters PROJCS["NAD_1983_HARN_Adj_MN_Clearwater_Meters",GEOGCS["GCS_North_American
103603 NAD_1983_HARN_Adj_MN_Hubbard_Meters PROJCS["NAD_1983_HARN_Adj_MN_Hubbard_Meters",GEOGCS["GCS_North_American_1
103604 NAD_1983_HARN_Adj_MN_Lake_Meters PROJCS["NAD_1983_HARN_Adj_MN_Lake_Meters",GEOGCS["GCS_North_American_1983
103605 NAD_1983_HARN_Adj_MN_Mille_Lacs_Meters PROJCS["NAD_1983_HARN_Adj_MN_Mille_Lacs_Meters",GEOGCS["GCS_North_American
103606 NAD_1983_HARN_Adj_MN_Washington_Meters PROJCS["NAD_1983_HARN_Adj_MN_Washington_Meters",GEOGCS["GCS_North_America
103607 NAD_1983_HARN_Adj_MN_Wilkin_Meters PROJCS["NAD_1983_HARN_Adj_MN_Wilkin_Meters",GEOGCS["GCS_North_American_198
103608 NAD_1983_HARN_Adj_MN_Anoka_Meters PROJCS["NAD_1983_HARN_Adj_MN_Anoka_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103609 NAD_1983_HARN_Adj_MN_Becker_Meters PROJCS["NAD_1983_HARN_Adj_MN_Becker_Meters",GEOGCS["GCS_NAD_1983_HARN_
103610 NAD_1983_HARN_Adj_MN_Beltrami_North_Meters PROJCS["NAD_1983_HARN_Adj_MN_Beltrami_North_Meters",GEOGCS["GCS_NAD_1983_
103611 NAD_1983_HARN_Adj_MN_Beltrami_South_Meters PROJCS["NAD_1983_HARN_Adj_MN_Beltrami_South_Meters",GEOGCS["GCS_NAD_1983_
103612 NAD_1983_HARN_Adj_MN_Benton_Meters PROJCS["NAD_1983_HARN_Adj_MN_Benton_Meters",GEOGCS["GCS_NAD_1983_HARN_
103613 NAD_1983_HARN_Adj_MN_Big_Stone_Meters PROJCS["NAD_1983_HARN_Adj_MN_Big_Stone_Meters",GEOGCS["GCS_NAD_1983_HAR
103614 NAD_1983_HARN_Adj_MN_Blue_Earth_Meters PROJCS["NAD_1983_HARN_Adj_MN_Blue_Earth_Meters",GEOGCS["GCS_NAD_1983_HAR
103615 NAD_1983_HARN_Adj_MN_Brown_Meters PROJCS["NAD_1983_HARN_Adj_MN_Brown_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103616 NAD_1983_HARN_Adj_MN_Carlton_Meters PROJCS["NAD_1983_HARN_Adj_MN_Carlton_Meters",GEOGCS["GCS_NAD_1983_HARN_
103617 NAD_1983_HARN_Adj_MN_Carver_Meters PROJCS["NAD_1983_HARN_Adj_MN_Carver_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103618 NAD_1983_HARN_Adj_MN_Cass_North_Meters PROJCS["NAD_1983_HARN_Adj_MN_Cass_North_Meters",GEOGCS["GCS_NAD_1983_HA
103619 NAD_1983_HARN_Adj_MN_Cass_South_Meters PROJCS["NAD_1983_HARN_Adj_MN_Cass_South_Meters",GEOGCS["GCS_NAD_1983_HA
103620 NAD_1983_HARN_Adj_MN_Chippewa_Meters PROJCS["NAD_1983_HARN_Adj_MN_Chippewa_Meters",GEOGCS["GCS_NAD_1983_HAR
103621 NAD_1983_HARN_Adj_MN_Chisago_Meters PROJCS["NAD_1983_HARN_Adj_MN_Chisago_Meters",GEOGCS["GCS_NAD_1983_HARN
103622 NAD_1983_HARN_Adj_MN_Cook_North_Meters PROJCS["NAD_1983_HARN_Adj_MN_Cook_North_Meters",GEOGCS["GCS_NAD_1983_HA
103623 NAD_1983_HARN_Adj_MN_Cook_South_Meters PROJCS["NAD_1983_HARN_Adj_MN_Cook_South_Meters",GEOGCS["GCS_NAD_1983_HA
103624 NAD_1983_HARN_Adj_MN_Cottonwood_Meters PROJCS["NAD_1983_HARN_Adj_MN_Cottonwood_Meters",GEOGCS["GCS_NAD_1983_HA
103625 NAD_1983_HARN_Adj_MN_Crow_Wing_Meters PROJCS["NAD_1983_HARN_Adj_MN_Crow_Wing_Meters",GEOGCS["GCS_NAD_1983_HA
103626 NAD_1983_HARN_Adj_MN_Dakota_Meters PROJCS["NAD_1983_HARN_Adj_MN_Dakota_Meters",GEOGCS["GCS_NAD_1983_HARN_
103627 NAD_1983_HARN_Adj_MN_Dodge_Meters PROJCS["NAD_1983_HARN_Adj_MN_Dodge_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103628 NAD_1983_HARN_Adj_MN_Douglas_Meters PROJCS["NAD_1983_HARN_Adj_MN_Douglas_Meters",GEOGCS["GCS_NAD_1983_HARN
103629 NAD_1983_HARN_Adj_MN_Faribault_Meters PROJCS["NAD_1983_HARN_Adj_MN_Faribault_Meters",GEOGCS["GCS_NAD_1983_HARN
103630 NAD_1983_HARN_Adj_MN_Fillmore_Meters PROJCS["NAD_1983_HARN_Adj_MN_Fillmore_Meters",GEOGCS["GCS_NAD_1983_HARN_
103631 NAD_1983_HARN_Adj_MN_Freeborn_Meters PROJCS["NAD_1983_HARN_Adj_MN_Freeborn_Meters",GEOGCS["GCS_NAD_1983_HARN
103632 NAD_1983_HARN_Adj_MN_Goodhue_Meters PROJCS["NAD_1983_HARN_Adj_MN_Goodhue_Meters",GEOGCS["GCS_NAD_1983_HARN
103633 NAD_1983_HARN_Adj_MN_Grant_Meters PROJCS["NAD_1983_HARN_Adj_MN_Grant_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103634 NAD_1983_HARN_Adj_MN_Hennepin_Meters PROJCS["NAD_1983_HARN_Adj_MN_Hennepin_Meters",GEOGCS["GCS_NAD_1983_HARN
103635 NAD_1983_HARN_Adj_MN_Houston_Meters PROJCS["NAD_1983_HARN_Adj_MN_Houston_Meters",GEOGCS["GCS_NAD_1983_HARN
103636 NAD_1983_HARN_Adj_MN_Isanti_Meters PROJCS["NAD_1983_HARN_Adj_MN_Isanti_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103637 NAD_1983_HARN_Adj_MN_Itasca_North_Meters PROJCS["NAD_1983_HARN_Adj_MN_Itasca_North_Meters",GEOGCS["GCS_NAD_1983_HA
103638 NAD_1983_HARN_Adj_MN_Itasca_South_Meters PROJCS["NAD_1983_HARN_Adj_MN_Itasca_South_Meters",GEOGCS["GCS_NAD_1983_H
103639 NAD_1983_HARN_Adj_MN_Jackson_Meters PROJCS["NAD_1983_HARN_Adj_MN_Jackson_Meters",GEOGCS["GCS_NAD_1983_HARN
103640 NAD_1983_HARN_Adj_MN_Kanabec_Meters PROJCS["NAD_1983_HARN_Adj_MN_Kanabec_Meters",GEOGCS["GCS_NAD_1983_HARN
103641 NAD_1983_HARN_Adj_MN_Kandiyohi_Meters PROJCS["NAD_1983_HARN_Adj_MN_Kandiyohi_Meters",GEOGCS["GCS_NAD_1983_HAR
103642 NAD_1983_HARN_Adj_MN_Kittson_Meters PROJCS["NAD_1983_HARN_Adj_MN_Kittson_Meters",GEOGCS["GCS_NAD_1983_HARN_
103643 NAD_1983_HARN_Adj_MN_Koochiching_Meters PROJCS["NAD_1983_HARN_Adj_MN_Koochiching_Meters",GEOGCS["GCS_NAD_1983_HA
103644 NAD_1983_HARN_Adj_MN_Lac_Qui_Parle_Meters PROJCS["NAD_1983_HARN_Adj_MN_Lac_Qui_Parle_Meters",GEOGCS["GCS_NAD_1983_
103645 NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_North_Meters PROJCS["NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_North_Meters",GEOGCS["GCS_
103646 NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_South_Meters PROJCS["NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_South_Meters",GEOGCS["GCS_
103647 NAD_1983_HARN_Adj_MN_Le_Sueur_Meters PROJCS["NAD_1983_HARN_Adj_MN_Le_Sueur_Meters",GEOGCS["GCS_NAD_1983_HAR

103648 NAD_1983_HARN_Adj_MN_Lincoln_Meters PROJCS["NAD_1983_HARN_Adj_MN_Lincoln_Meters",GEOGCS["GCS_NAD_1983_HARN_

103649 NAD_1983_HARN_Adj_MN_Lyon_Meters PROJCS["NAD_1983_HARN_Adj_MN_Lyon_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103650 NAD_1983_HARN_Adj_MN_McLeod_Meters PROJCS["NAD_1983_HARN_Adj_MN_McLeod_Meters",GEOGCS["GCS_NAD_1983_HARN_
103651 NAD_1983_HARN_Adj_MN_Mahnomen_Meters PROJCS["NAD_1983_HARN_Adj_MN_Mahnomen_Meters",GEOGCS["GCS_NAD_1983_HAR
103652 NAD_1983_HARN_Adj_MN_Marshall_Meters PROJCS["NAD_1983_HARN_Adj_MN_Marshall_Meters",GEOGCS["GCS_NAD_1983_HARN
103653 NAD_1983_HARN_Adj_MN_Martin_Meters PROJCS["NAD_1983_HARN_Adj_MN_Martin_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103654 NAD_1983_HARN_Adj_MN_Meeker_Meters PROJCS["NAD_1983_HARN_Adj_MN_Meeker_Meters",GEOGCS["GCS_NAD_1983_HARN_
103655 NAD_1983_HARN_Adj_MN_Morrison_Meters PROJCS["NAD_1983_HARN_Adj_MN_Morrison_Meters",GEOGCS["GCS_NAD_1983_HARN
103656 NAD_1983_HARN_Adj_MN_Mower_Meters PROJCS["NAD_1983_HARN_Adj_MN_Mower_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103657 NAD_1983_HARN_Adj_MN_Murray_Meters PROJCS["NAD_1983_HARN_Adj_MN_Murray_Meters",GEOGCS["GCS_NAD_1983_HARN_
103658 NAD_1983_HARN_Adj_MN_Nicollet_Meters PROJCS["NAD_1983_HARN_Adj_MN_Nicollet_Meters",GEOGCS["GCS_NAD_1983_HARN_
103659 NAD_1983_HARN_Adj_MN_Nobles_Meters PROJCS["NAD_1983_HARN_Adj_MN_Nobles_Meters",GEOGCS["GCS_NAD_1983_HARN_
103660 NAD_1983_HARN_Adj_MN_Norman_Meters PROJCS["NAD_1983_HARN_Adj_MN_Norman_Meters",GEOGCS["GCS_NAD_1983_HARN_
103661 NAD_1983_HARN_Adj_MN_Olmsted_Meters PROJCS["NAD_1983_HARN_Adj_MN_Olmsted_Meters",GEOGCS["GCS_NAD_1983_HARN
103662 NAD_1983_HARN_Adj_MN_Ottertail_Meters PROJCS["NAD_1983_HARN_Adj_MN_Ottertail_Meters",GEOGCS["GCS_NAD_1983_HARN_
103663 NAD_1983_HARN_Adj_MN_Pennington_Meters PROJCS["NAD_1983_HARN_Adj_MN_Pennington_Meters",GEOGCS["GCS_NAD_1983_HA
103664 NAD_1983_HARN_Adj_MN_Pine_Meters PROJCS["NAD_1983_HARN_Adj_MN_Pine_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103665 NAD_1983_HARN_Adj_MN_Pipestone_Meters PROJCS["NAD_1983_HARN_Adj_MN_Pipestone_Meters",GEOGCS["GCS_NAD_1983_HAR
103666 NAD_1983_HARN_Adj_MN_Polk_Meters PROJCS["NAD_1983_HARN_Adj_MN_Polk_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103667 NAD_1983_HARN_Adj_MN_Pope_Meters PROJCS["NAD_1983_HARN_Adj_MN_Pope_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103668 NAD_1983_HARN_Adj_MN_Ramsey_Meters PROJCS["NAD_1983_HARN_Adj_MN_Ramsey_Meters",GEOGCS["GCS_NAD_1983_HARN
103669 NAD_1983_HARN_Adj_MN_Red_Lake_Meters PROJCS["NAD_1983_HARN_Adj_MN_Red_Lake_Meters",GEOGCS["GCS_NAD_1983_HAR
103670 NAD_1983_HARN_Adj_MN_Redwood_Meters PROJCS["NAD_1983_HARN_Adj_MN_Redwood_Meters",GEOGCS["GCS_NAD_1983_HARN
103671 NAD_1983_HARN_Adj_MN_Renville_Meters PROJCS["NAD_1983_HARN_Adj_MN_Renville_Meters",GEOGCS["GCS_NAD_1983_HARN_
103672 NAD_1983_HARN_Adj_MN_Rice_Meters PROJCS["NAD_1983_HARN_Adj_MN_Rice_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103673 NAD_1983_HARN_Adj_MN_Rock_Meters PROJCS["NAD_1983_HARN_Adj_MN_Rock_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103674 NAD_1983_HARN_Adj_MN_Roseau_Meters PROJCS["NAD_1983_HARN_Adj_MN_Roseau_Meters",GEOGCS["GCS_NAD_1983_HARN_
103675 NAD_1983_HARN_Adj_MN_St_Louis_North_Meters PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_North_Meters",GEOGCS["GCS_NAD_1983_
103676 NAD_1983_HARN_Adj_MN_St_Louis_Central_Meters PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_Central_Meters",GEOGCS["GCS_NAD_198
103677 NAD_1983_HARN_Adj_MN_St_Louis_South_Meters PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_South_Meters",GEOGCS["GCS_NAD_1983
103678 NAD_1983_HARN_Adj_MN_Scott_Meters PROJCS["NAD_1983_HARN_Adj_MN_Scott_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103679 NAD_1983_HARN_Adj_MN_Sherburne_Meters PROJCS["NAD_1983_HARN_Adj_MN_Sherburne_Meters",GEOGCS["GCS_NAD_1983_HAR
103680 NAD_1983_HARN_Adj_MN_Sibley_Meters PROJCS["NAD_1983_HARN_Adj_MN_Sibley_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103681 NAD_1983_HARN_Adj_MN_Stearns_Meters PROJCS["NAD_1983_HARN_Adj_MN_Stearns_Meters",GEOGCS["GCS_NAD_1983_HARN_
103682 NAD_1983_HARN_Adj_MN_Steele_Meters PROJCS["NAD_1983_HARN_Adj_MN_Steele_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103683 NAD_1983_HARN_Adj_MN_Stevens_Meters PROJCS["NAD_1983_HARN_Adj_MN_Stevens_Meters",GEOGCS["GCS_NAD_1983_HARN
103684 NAD_1983_HARN_Adj_MN_Swift_Meters PROJCS["NAD_1983_HARN_Adj_MN_Swift_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103685 NAD_1983_HARN_Adj_MN_Todd_Meters PROJCS["NAD_1983_HARN_Adj_MN_Todd_Meters",GEOGCS["GCS_NAD_1983_HARN_Ad
103686 NAD_1983_HARN_Adj_MN_Traverse_Meters PROJCS["NAD_1983_HARN_Adj_MN_Traverse_Meters",GEOGCS["GCS_NAD_1983_HARN
103687 NAD_1983_HARN_Adj_MN_Wabasha_Meters PROJCS["NAD_1983_HARN_Adj_MN_Wabasha_Meters",GEOGCS["GCS_NAD_1983_HARN
103688 NAD_1983_HARN_Adj_MN_Wadena_Meters PROJCS["NAD_1983_HARN_Adj_MN_Wadena_Meters",GEOGCS["GCS_NAD_1983_HARN
103689 NAD_1983_HARN_Adj_MN_Waseca_Meters PROJCS["NAD_1983_HARN_Adj_MN_Waseca_Meters",GEOGCS["GCS_NAD_1983_HARN_
103690 NAD_1983_HARN_Adj_MN_Watonwan_Meters PROJCS["NAD_1983_HARN_Adj_MN_Watonwan_Meters",GEOGCS["GCS_NAD_1983_HAR
103691 NAD_1983_HARN_Adj_MN_Winona_Meters PROJCS["NAD_1983_HARN_Adj_MN_Winona_Meters",GEOGCS["GCS_NAD_1983_HARN_
103692 NAD_1983_HARN_Adj_MN_Wright_Meters PROJCS["NAD_1983_HARN_Adj_MN_Wright_Meters",GEOGCS["GCS_NAD_1983_HARN_A
103693 NAD_1983_HARN_Adj_MN_Yellow_Medicine_Meters PROJCS["NAD_1983_HARN_Adj_MN_Yellow_Medicine_Meters",GEOGCS["GCS_NAD_1983
103694 NAD_1983_HARN_Adj_MN_St_Louis_CS96_Meters PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_CS96_Meters",GEOGCS["GCS_NAD_1983_
103695 NAD_1983_HARN_Adj_MN_St_Louis_CS96_Feet PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_CS96_Feet",GEOGCS["GCS_NAD_1983_H
103700 NAD_1983_HARN_Adj_MN_Aitkin_Feet PROJCS["NAD_1983_HARN_Adj_MN_Aitkin_Feet",GEOGCS["GCS_North_American_1983_
103701 NAD_1983_HARN_Adj_MN_Clay_Feet PROJCS["NAD_1983_HARN_Adj_MN_Clay_Feet",GEOGCS["GCS_North_American_1983_H
103702 NAD_1983_HARN_Adj_MN_Clearwater_Feet PROJCS["NAD_1983_HARN_Adj_MN_Clearwater_Feet",GEOGCS["GCS_North_American_1
103703 NAD_1983_HARN_Adj_MN_Hubbard_Feet PROJCS["NAD_1983_HARN_Adj_MN_Hubbard_Feet",GEOGCS["GCS_North_American_198
103704 NAD_1983_HARN_Adj_MN_Lake_Feet PROJCS["NAD_1983_HARN_Adj_MN_Lake_Feet",GEOGCS["GCS_North_American_1983_H
103705 NAD_1983_HARN_Adj_MN_Mille_Lacs_Feet PROJCS["NAD_1983_HARN_Adj_MN_Mille_Lacs_Feet",GEOGCS["GCS_North_American_1

103706 NAD_1983_HARN_Adj_MN_Washington_Feet PROJCS["NAD_1983_HARN_Adj_MN_Washington_Feet",GEOGCS["GCS_North_American_

103707 NAD_1983_HARN_Adj_MN_Wilkin_Feet PROJCS["NAD_1983_HARN_Adj_MN_Wilkin_Feet",GEOGCS["GCS_North_American_1983_
103708 NAD_1983_HARN_Adj_MN_Anoka_Feet PROJCS["NAD_1983_HARN_Adj_MN_Anoka_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj
103709 NAD_1983_HARN_Adj_MN_Becker_Feet PROJCS["NAD_1983_HARN_Adj_MN_Becker_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103710 NAD_1983_HARN_Adj_MN_Beltrami_North_Feet PROJCS["NAD_1983_HARN_Adj_MN_Beltrami_North_Feet",GEOGCS["GCS_NAD_1983_HA
103711 NAD_1983_HARN_Adj_MN_Beltrami_South_Feet PROJCS["NAD_1983_HARN_Adj_MN_Beltrami_South_Feet",GEOGCS["GCS_NAD_1983_H
103712 NAD_1983_HARN_Adj_MN_Benton_Feet PROJCS["NAD_1983_HARN_Adj_MN_Benton_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103713 NAD_1983_HARN_Adj_MN_Big_Stone_Feet PROJCS["NAD_1983_HARN_Adj_MN_Big_Stone_Feet",GEOGCS["GCS_NAD_1983_HARN_
103714 NAD_1983_HARN_Adj_MN_Blue_Earth_Feet PROJCS["NAD_1983_HARN_Adj_MN_Blue_Earth_Feet",GEOGCS["GCS_NAD_1983_HARN
103715 NAD_1983_HARN_Adj_MN_Brown_Feet PROJCS["NAD_1983_HARN_Adj_MN_Brown_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj
103716 NAD_1983_HARN_Adj_MN_Carlton_Feet PROJCS["NAD_1983_HARN_Adj_MN_Carlton_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103717 NAD_1983_HARN_Adj_MN_Carver_Feet PROJCS["NAD_1983_HARN_Adj_MN_Carver_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103718 NAD_1983_HARN_Adj_MN_Cass_North_Feet PROJCS["NAD_1983_HARN_Adj_MN_Cass_North_Feet",GEOGCS["GCS_NAD_1983_HARN
103719 NAD_1983_HARN_Adj_MN_Cass_South_Feet PROJCS["NAD_1983_HARN_Adj_MN_Cass_South_Feet",GEOGCS["GCS_NAD_1983_HAR
103720 NAD_1983_HARN_Adj_MN_Chippewa_Feet PROJCS["NAD_1983_HARN_Adj_MN_Chippewa_Feet",GEOGCS["GCS_NAD_1983_HARN_
103721 NAD_1983_HARN_Adj_MN_Chisago_Feet PROJCS["NAD_1983_HARN_Adj_MN_Chisago_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103722 NAD_1983_HARN_Adj_MN_Cook_North_Feet PROJCS["NAD_1983_HARN_Adj_MN_Cook_North_Feet",GEOGCS["GCS_NAD_1983_HARN
103723 NAD_1983_HARN_Adj_MN_Cook_South_Feet PROJCS["NAD_1983_HARN_Adj_MN_Cook_South_Feet",GEOGCS["GCS_NAD_1983_HAR
103724 NAD_1983_HARN_Adj_MN_Cottonwood_Feet PROJCS["NAD_1983_HARN_Adj_MN_Cottonwood_Feet",GEOGCS["GCS_NAD_1983_HARN
103725 NAD_1983_HARN_Adj_MN_Crow_Wing_Feet PROJCS["NAD_1983_HARN_Adj_MN_Crow_Wing_Feet",GEOGCS["GCS_NAD_1983_HARN
103726 NAD_1983_HARN_Adj_MN_Dakota_Feet PROJCS["NAD_1983_HARN_Adj_MN_Dakota_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103727 NAD_1983_HARN_Adj_MN_Dodge_Feet PROJCS["NAD_1983_HARN_Adj_MN_Dodge_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103728 NAD_1983_HARN_Adj_MN_Douglas_Feet PROJCS["NAD_1983_HARN_Adj_MN_Douglas_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103729 NAD_1983_HARN_Adj_MN_Faribault_Feet PROJCS["NAD_1983_HARN_Adj_MN_Faribault_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103730 NAD_1983_HARN_Adj_MN_Fillmore_Feet PROJCS["NAD_1983_HARN_Adj_MN_Fillmore_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103731 NAD_1983_HARN_Adj_MN_Freeborn_Feet PROJCS["NAD_1983_HARN_Adj_MN_Freeborn_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103732 NAD_1983_HARN_Adj_MN_Goodhue_Feet PROJCS["NAD_1983_HARN_Adj_MN_Goodhue_Feet",GEOGCS["GCS_NAD_1983_HARN_
103733 NAD_1983_HARN_Adj_MN_Grant_Feet PROJCS["NAD_1983_HARN_Adj_MN_Grant_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103734 NAD_1983_HARN_Adj_MN_Hennepin_Feet PROJCS["NAD_1983_HARN_Adj_MN_Hennepin_Feet",GEOGCS["GCS_NAD_1983_HARN_
103735 NAD_1983_HARN_Adj_MN_Houston_Feet PROJCS["NAD_1983_HARN_Adj_MN_Houston_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103736 NAD_1983_HARN_Adj_MN_Isanti_Feet PROJCS["NAD_1983_HARN_Adj_MN_Isanti_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103737 NAD_1983_HARN_Adj_MN_Itasca_North_Feet PROJCS["NAD_1983_HARN_Adj_MN_Itasca_North_Feet",GEOGCS["GCS_NAD_1983_HAR
103738 NAD_1983_HARN_Adj_MN_Itasca_South_Feet PROJCS["NAD_1983_HARN_Adj_MN_Itasca_South_Feet",GEOGCS["GCS_NAD_1983_HAR
103739 NAD_1983_HARN_Adj_MN_Jackson_Feet PROJCS["NAD_1983_HARN_Adj_MN_Jackson_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103740 NAD_1983_HARN_Adj_MN_Kanabec_Feet PROJCS["NAD_1983_HARN_Adj_MN_Kanabec_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103741 NAD_1983_HARN_Adj_MN_Kandiyohi_Feet PROJCS["NAD_1983_HARN_Adj_MN_Kandiyohi_Feet",GEOGCS["GCS_NAD_1983_HARN_
103742 NAD_1983_HARN_Adj_MN_Kittson_Feet PROJCS["NAD_1983_HARN_Adj_MN_Kittson_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103743 NAD_1983_HARN_Adj_MN_Koochiching_Feet PROJCS["NAD_1983_HARN_Adj_MN_Koochiching_Feet",GEOGCS["GCS_NAD_1983_HAR
103744 NAD_1983_HARN_Adj_MN_Lac_Qui_Parle_Feet PROJCS["NAD_1983_HARN_Adj_MN_Lac_Qui_Parle_Feet",GEOGCS["GCS_NAD_1983_HA
103745 NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_North_Feet PROJCS["NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_North_Feet",GEOGCS["GCS_NA
103746 NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_South_Feet PROJCS["NAD_1983_HARN_Adj_MN_Lake_of_the_Woods_South_Feet",GEOGCS["GCS_N
103747 NAD_1983_HARN_Adj_MN_Le_Sueur_Feet PROJCS["NAD_1983_HARN_Adj_MN_Le_Sueur_Feet",GEOGCS["GCS_NAD_1983_HARN_
103748 NAD_1983_HARN_Adj_MN_Lincoln_Feet PROJCS["NAD_1983_HARN_Adj_MN_Lincoln_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103749 NAD_1983_HARN_Adj_MN_Lyon_Feet PROJCS["NAD_1983_HARN_Adj_MN_Lyon_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103750 NAD_1983_HARN_Adj_MN_McLeod_Feet PROJCS["NAD_1983_HARN_Adj_MN_McLeod_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103751 NAD_1983_HARN_Adj_MN_Mahnomen_Feet PROJCS["NAD_1983_HARN_Adj_MN_Mahnomen_Feet",GEOGCS["GCS_NAD_1983_HARN
103752 NAD_1983_HARN_Adj_MN_Marshall_Feet PROJCS["NAD_1983_HARN_Adj_MN_Marshall_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103753 NAD_1983_HARN_Adj_MN_Martin_Feet PROJCS["NAD_1983_HARN_Adj_MN_Martin_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj
103754 NAD_1983_HARN_Adj_MN_Meeker_Feet PROJCS["NAD_1983_HARN_Adj_MN_Meeker_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103755 NAD_1983_HARN_Adj_MN_Morrison_Feet PROJCS["NAD_1983_HARN_Adj_MN_Morrison_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103756 NAD_1983_HARN_Adj_MN_Mower_Feet PROJCS["NAD_1983_HARN_Adj_MN_Mower_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103757 NAD_1983_HARN_Adj_MN_Murray_Feet PROJCS["NAD_1983_HARN_Adj_MN_Murray_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103758 NAD_1983_HARN_Adj_MN_Nicollet_Feet PROJCS["NAD_1983_HARN_Adj_MN_Nicollet_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103759 NAD_1983_HARN_Adj_MN_Nobles_Feet PROJCS["NAD_1983_HARN_Adj_MN_Nobles_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad

103760 NAD_1983_HARN_Adj_MN_Norman_Feet PROJCS["NAD_1983_HARN_Adj_MN_Norman_Feet",GEOGCS["GCS_NAD_1983_HARN_A

103761 NAD_1983_HARN_Adj_MN_Olmsted_Feet PROJCS["NAD_1983_HARN_Adj_MN_Olmsted_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103762 NAD_1983_HARN_Adj_MN_Ottertail_Feet PROJCS["NAD_1983_HARN_Adj_MN_Ottertail_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103763 NAD_1983_HARN_Adj_MN_Pennington_Feet PROJCS["NAD_1983_HARN_Adj_MN_Pennington_Feet",GEOGCS["GCS_NAD_1983_HARN
103764 NAD_1983_HARN_Adj_MN_Pine_Feet PROJCS["NAD_1983_HARN_Adj_MN_Pine_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_M
103765 NAD_1983_HARN_Adj_MN_Pipestone_Feet PROJCS["NAD_1983_HARN_Adj_MN_Pipestone_Feet",GEOGCS["GCS_NAD_1983_HARN_
103766 NAD_1983_HARN_Adj_MN_Polk_Feet PROJCS["NAD_1983_HARN_Adj_MN_Polk_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_M
103767 NAD_1983_HARN_Adj_MN_Pope_Feet PROJCS["NAD_1983_HARN_Adj_MN_Pope_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103768 NAD_1983_HARN_Adj_MN_Ramsey_Feet PROJCS["NAD_1983_HARN_Adj_MN_Ramsey_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103769 NAD_1983_HARN_Adj_MN_Red_Lake_Feet PROJCS["NAD_1983_HARN_Adj_MN_Red_Lake_Feet",GEOGCS["GCS_NAD_1983_HARN_
103770 NAD_1983_HARN_Adj_MN_Redwood_Feet PROJCS["NAD_1983_HARN_Adj_MN_Redwood_Feet",GEOGCS["GCS_NAD_1983_HARN_
103771 NAD_1983_HARN_Adj_MN_Renville_Feet PROJCS["NAD_1983_HARN_Adj_MN_Renville_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103772 NAD_1983_HARN_Adj_MN_Rice_Feet PROJCS["NAD_1983_HARN_Adj_MN_Rice_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_M
103773 NAD_1983_HARN_Adj_MN_Rock_Feet PROJCS["NAD_1983_HARN_Adj_MN_Rock_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103774 NAD_1983_HARN_Adj_MN_Roseau_Feet PROJCS["NAD_1983_HARN_Adj_MN_Roseau_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103775 NAD_1983_HARN_Adj_MN_St_Louis_North_Feet PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_North_Feet",GEOGCS["GCS_NAD_1983_H
103776 NAD_1983_HARN_Adj_MN_St_Louis_Central_Feet PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_Central_Feet",GEOGCS["GCS_NAD_1983_
103777 NAD_1983_HARN_Adj_MN_St_Louis_South_Feet PROJCS["NAD_1983_HARN_Adj_MN_St_Louis_South_Feet",GEOGCS["GCS_NAD_1983_H
103778 NAD_1983_HARN_Adj_MN_Scott_Feet PROJCS["NAD_1983_HARN_Adj_MN_Scott_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103779 NAD_1983_HARN_Adj_MN_Sherburne_Feet PROJCS["NAD_1983_HARN_Adj_MN_Sherburne_Feet",GEOGCS["GCS_NAD_1983_HARN
103780 NAD_1983_HARN_Adj_MN_Sibley_Feet PROJCS["NAD_1983_HARN_Adj_MN_Sibley_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj
103781 NAD_1983_HARN_Adj_MN_Stearns_Feet PROJCS["NAD_1983_HARN_Adj_MN_Stearns_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103782 NAD_1983_HARN_Adj_MN_Steele_Feet PROJCS["NAD_1983_HARN_Adj_MN_Steele_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj
103783 NAD_1983_HARN_Adj_MN_Stevens_Feet PROJCS["NAD_1983_HARN_Adj_MN_Stevens_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103784 NAD_1983_HARN_Adj_MN_Swift_Feet PROJCS["NAD_1983_HARN_Adj_MN_Swift_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103785 NAD_1983_HARN_Adj_MN_Todd_Feet PROJCS["NAD_1983_HARN_Adj_MN_Todd_Feet",GEOGCS["GCS_NAD_1983_HARN_Adj_
103786 NAD_1983_HARN_Adj_MN_Traverse_Feet PROJCS["NAD_1983_HARN_Adj_MN_Traverse_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103787 NAD_1983_HARN_Adj_MN_Wabasha_Feet PROJCS["NAD_1983_HARN_Adj_MN_Wabasha_Feet",GEOGCS["GCS_NAD_1983_HARN_
103788 NAD_1983_HARN_Adj_MN_Wadena_Feet PROJCS["NAD_1983_HARN_Adj_MN_Wadena_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103789 NAD_1983_HARN_Adj_MN_Waseca_Feet PROJCS["NAD_1983_HARN_Adj_MN_Waseca_Feet",GEOGCS["GCS_NAD_1983_HARN_A
103790 NAD_1983_HARN_Adj_MN_Watonwan_Feet PROJCS["NAD_1983_HARN_Adj_MN_Watonwan_Feet",GEOGCS["GCS_NAD_1983_HARN
103791 NAD_1983_HARN_Adj_MN_Winona_Feet PROJCS["NAD_1983_HARN_Adj_MN_Winona_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103792 NAD_1983_HARN_Adj_MN_Wright_Feet PROJCS["NAD_1983_HARN_Adj_MN_Wright_Feet",GEOGCS["GCS_NAD_1983_HARN_Ad
103793 NAD_1983_HARN_Adj_MN_Yellow_Medicine_Feet PROJCS["NAD_1983_HARN_Adj_MN_Yellow_Medicine_Feet",GEOGCS["GCS_NAD_1983_H
103794 Mexican_Datum_1993_UTM_Zone_11N PROJCS["Mexican_Datum_1993_UTM_Zone_11N",GEOGCS["GCS_Mexican_Datum_of_199

Platform error codes

Internal API errors are handled a few different ways depending on the type of error and the general exception handling patterns common
to the platform. Some APIs use exceptions to manage errors. Error codes are documented here for reference, but for clarity refer to the
specific API references for methods that throw exceptions or return error information. In most cases the API will defer error functionality to
the objects and services available on the native platform (for example, NSError on Cocoa, ArcGISRuntimeException in .Net, Java,
and Android). The Qt SDK, used for cross-platform development, manages error information using an Error object.
There are distinct classes of errors, depending on the service invoked. As the architecture dictates, errors may originate from the API, the
runtime core supporting the API, or the service (the servers the API connects to implementing certain services.) Check the error domain if
this is information useful to your app. In most cases you only need the error code to determine the cause of the error and possible remedy.
Error domains
The API exposes several error domains. A domain is a segregated area of the API, usually bound to a framework, internal library, or
module of functionality. The error domain helps focus the error to a specific area of functionality within the API.
ArcGISRuntime
ArcGISServer
ArcGISPopup
Handling errors
There are different coding patterns used to handle errors that are specific to each API. Refer to the specific API documentation to
understand how that API will communicate an error response. There are three patterns of error response:
Return codes: sometimes an API returns an error value or null. You test the return value and handle it according to your application
implementation requirements.
Callback, lambda, or delegate function: certain APIs allow the caller to set an asynchronous callback function that the internal API calls
upon certain defined events occurring. It is possible in these callbacks to receive an error. The API defines hows the error is represented
in the callback. It is up to your application to handle the error.
Exceptions: some APIs generate an exception you should handle. There are many ways of receiving an exception: try/catch, error block/
closure, error callback, or signal.
Error codes
Error codes are defined here as integers. In order to safeguard your code from comparing against these numbers directly we suggest
some form of abstraction, such as an errors enumeration or error class. We will do our best to never change a defined error code once the
SDK is officially released, but we reserve the right to make changes. Please consult the release notes regarding any changes to these
values.
ArcGISPopup errors
API errors are client-side exceptions that usually occur due to incorrect method parameters, object state dependencies, or network
conditions.
Error Code Description

11000 Invalid attributes or geometry on the associated GeoElement.
11001 Null value is not allowed.
11002 Value is out of range.
11003 Value exceeds maximum field length.
ArcGISRuntime errors
Internal runtime errors are thrown by the core library when things go wrong client-side. Where possible the details of the exception are
described. In many instances, the details of the exception are dependent on the context that generated the exception. In these cases,
refer to the specific API that generated the error for more information.

-1 This is the catch all for unknown errors.
0 This is a success and not an error.
1 Null pointer exception.

2 Invalid argument exception.

3 Not implemented exception.
4 Out of range exception.
5 Invalid access exception.
6 Illegal state exception.
7 Not found exception.
8 Exists exception.
9 Timeout exception.
10 Regular expression exception.
11 Property not supported exception.
12 No permission exception.
13 File exception.
14 File not found exception.
15 Invalid call exception.
16 IO exception.
17 User canceled exception.
18 Internal error exception.
19 Conversion failed exception.
20 No data.
21 Attempted to use invalid JSON.
22 Error was propagated.
23 Attempted to use invalid XML.
24 Object is already owned.
SQL errors
Internal errors related to the SQL storage engine.

1001 SQLite error exception.
1002 SQLite Internal exception.
1003 SQLite Perm exception.
1004 SQLite Abort exception.
1005 SQLite Busy exception.
1006 SQLite Locked exception.
1007 SQLite NoMem exception.
1008 SQLite Read only exception.
1009 SQLite Interrupt exception.
1010 SQLite IO Error exception.
1011 SQLite Corrupt exception.
1012 SQLite Not found exception.
1013 SQLite Full exception.
1014 SQLite Can't open exception.
1015 SQLite Protocol exception.
1016 SQLite Empty exception.
1017 SQLite Schema exception.
1018 SQLite Too big exception.
1019 SQLite Constraint exception.
1020 SQLite Mismatch exception.
1021 SQLite Misuse exception.
1022 SQLite Nolfs exception.
1023 SQLite Auth exception.
1024 SQLite Format exception.
1025 SQLite Range exception.
1026 SQLite Notadb exception.

1027 SQLite Notice exception.

1028 SQLite Warning exception.
1029 SQLite Row exception.
1030 SQLite Done exception.
Geometry errors
Internal errors related to the geometry engine.

2000 Geometry Exception.
2001 Geometry Corrupted geometry exception.
2002 Geometry Empty geometry exception.
2003 Geometry Math singularity exception.
2004 Geometry Buffer is too small exception.
2005 Geometry Invalid shape type exception.
2006 Geometry Projection out of supported range exception.
2007 Geometry Non simple geometry exception.
2008 Geometry Cannot calculate geodesic exception.
2009 Geometry Notation conversion exception.
2010 Geometry Missing grid file exception.
Geodatabase errors
Internal errors related to geodatabase queries.

3001 Geodatabase Value out of range exception.
3002 Geodatabase Data type mismatch exception.
3003 Geodatabase Bad XML exception.
3004 Geodatabase Database already exists exception.
3005 Geodatabase Database does not exist exception.
3006 Geodatabase Name longer than 128 characters exception.
3007 Geodatabase Invalid shape type exception.
3008 Geodatabase Raster not supported exception.
3009 Geodatabase Relationship class one to one exception.
3010 Geodatabase Item not found exception.
3011 Geodatabase Duplicate code exception.
3012 Geodatabase Missing code exception.
3013 Geodatabase Wrong item type exception.
3014 Geodatabase Id field not nullable exception.
3015 Geodatabase Default value not supported exception.
3016 Geodatabase Table not editable exception.
3017 Geodatabase Field not found exception.
3018 Geodatabase Field exists exception.
3019 Geodatabase Cannot alter field type exception.
3020 Geodatabase Cannot alter field width exception.
3021 Geodatabase Cannot alter field to nullable exception.
3022 Geodatabase Cannot alter field to editable exception.
3023 Geodatabase Cannot alter field to deletable exception.
3024 Geodatabase Cannot alter geometry properties exception.
3025 Geodatabase Unnamed table exception.
3026 Geodatabase Invalid type for domain exception.
3027 Geodatabase Min max reversed exception.
3028 Geodatabase Field not supported on relationship class exception.
3029 Geodatabase Relationship class key exception.
3030 Geodatabase Value is null exception.

3031 Geodatabase Multiple SQL statements exception.

3032 Geodatabase No SQL statements exception.
3033 Geodatabase Geometry field missing exception.
3034 Geodatabase Transaction started exception.
3035 Geodatabase Transaction not started exception.
3036 Geodatabase Shape requires z exception.
3037 Geodatabase shape requires m exception.
3038 Geodatabase Shape no z exception.
3039 Geodatabase Shape no m exception.
3040 Geodatabase Shape wrong type exception.
3041 Geodatabase Cannot update field type exception.
3042 Geodatabase No rows affected exception.
3043 Geodatabase Subtype invalid exception.
3044 Geodatabase Subtype must be integer exception.
3045 Geodatabase Subtypes not enabled exception.
3046 Geodatabase Subtype exists exception.
3047 Geodatabase Duplicate field not allowed exception.
3048 Geodatabase Cannot delete field exception.
3049 Geodatabase Index exists exception.
3050 Geodatabase Index not found exception.
3051 Geodatabase Cursor not on row exception.
3052 Geodatabase Internal error exception.
3053 Geodatabase Cannot write geodatabase managed fields exception.
3054 Geodatabase Item already exists exception.
3055 Geodatabase Invalid spatial index name exception.
3056 Geodatabase Requires spatial index exception.
3057 Geodatabase Reserved name exception.
3058 Geodatabase Cannot update schema if change tracking exception.
3059 Geodatabase Invalid date exception.
3060 Geodatabase Database does not have changes exception.
3061 Geodatabase Replica does not exists exception.
3062 Geodatabase Storage type not supported exception.
3063 Geodatabase Replica model error exception.
3064 Geodatabase Replica client gen error exception.
3065 Geodatabase Replica no upload to acknowledge exception.
3066 Geodatabase Last write time in the future exception.
3067 Geodatabase Invalid argument exception.
3068 Geodatabase Transportation network corrupt exception.
3069 Geodatabase Transportation network file IO exception.
3070 Geodatabase Feature has pending edits exception.
3071 Geodatabase Change tracking not enabled exception.
3072 Geodatabase Transportation network file open exception.
3073 Geodatabase Transportation network unsupported exception.
3074 Geodatabase Cannot sync copy exception.
3075 Geodatabase Access control denied exception.
3076 Geodatabase Geometry outside replica extent exception.
3077 Geodatabase Upload already in progress exception.
3078 Geodatabase Database is closed exception.
Geocode errors
Internal errors related to geocoding, address, and reverse address lookup.

4001 Geocode Unsupported file format exception.

4002 Geocode Unsupported spatial reference exception.

4003 Geocode Unsupported projection transformation exception.
4004 Geocode Geocoder creation exception.
4005 Geocode Intersections not supported exception.
4006 Geocode Uninitialized geocode task exception.
4007 Geocode Invalid locator properties exception.
4008 Geocode Required field missing exception.
4009 Geocode Cannot read address exception.
4010 Geocode Geocoding not supported exception.
Network Analyst errors

Internal errors related to Network Analyst and routing tasks.
Error Description
Code
5001 Network Analyst Invalid route settings exception.
5002 Network Analyst No solution exception.
5003 Network Analyst Task canceled exception.
5004 Network Analyst Invalid network exception.
5005 Network Analyst Directions error exception.
5006 Network Analyst Insufficient number of stops exception.
5007 Network Analyst Stop unlocated exception.
5008 Network Analyst Stop located on non traversable element exception.
5009 Network Analyst Point barrier invalid added cost attribute name exception.
5010 Network Analyst Line barrier invalid scaled cost attribute name exception.
5011 Network Analyst Polygon barrier invalid scaled cost attribute name.
5012 Network Analyst Polygon barrier invalid scaled cost attribute value.
5013 Network Analyst Polyline barrier invalid scaled cost attribute value.
5014 Network Analyst Invalid impedance attribute exception.
5015 Network Analyst Invalid restriction attribute exception.
5016 Network Analyst Invalid accumulate attribute exception.
5017 Network Analyst Invalid directions time attribute exception.
5018 Network Analyst Invalid directions distance attribute exception.
5019 Network Analyst Invalid attribute parameters attribute name exception.
5020 Network Analyst Invalid attributes parameters parameter name exception.
5021 Network Analyst Invalid attributes parameters value type exception.
5022 Network Analyst Invalid attribute parameters restriction usage value exception.
5023 Network Analyst Network has no hierarchy attribute exception.
5024 Network Analyst No path found between stops exception.
5025 Network Analyst Undefined input spatial reference exception.
5026 Network Analyst Undefined output spatial reference exception.
5027 Network Analyst Invalid directions style exception.
5028 Network Analyst Invalid directions language exception.
5029 Network Analyst Directions time and impedance attribute mismatch exception.
5030 Network Analyst Invalid directions road class attribute exception.
5031 Network Analyst Stop can not be reached.
5032 Network Analyst Stop time window starts before unix epoch exception.
5033 Network Analyst Stop time window is inverted exception.
5034 Walking mode route too large exception.
5035 Stop has null geometry exception.
5036 Point barrier has null geometry exception.
5037 Polyline barrier has null geometry exception.
5038 Polygon barrier has null geometry.
5039 Online route task does not support search_where_clause condition exception.
5040 Network Analyst Insufficient number of facilities exception.

5041 Network Analyst Facility has null geometry exception.

5042 Network Analyst Facility has invalid added cost attribute name exception.
5043 Network Analyst Facility has negative added cost attribute exception.
5044 Network Analyst Facility has invalid impedance cutoff exception.
5045 Network Analyst insufficient number of incidents exception.
5046 Network Analyst Incident has null geometry exception.
5047 Network Analyst Incident has invalid added cost attribute name exception.
5048 Network Analyst Incident has negative added cost attribute exception.
5049 Network Analyst Invalid target facility count exception.
5050 Network Analyst Incident has invalid impedance cutoff exception.
5051 Network Analyst start time is before Unix epoch exception.
5052 Network Analyst Invalid default impedance cutoff exception.
5053 Network Analyst Invalid default target facility count exception.
5054 Network Analyst Invalid polygon buffer distance exception.
5055 Network Analyst Polylines cannot be returned.
5056 Network Analyst Solving non time impedance, but time windows applied.
5057 One or more stops have unsupported type.
5058 Network Analyst Route starts or ends on a waypoint.
5059 Network Analyst Reordering stops (Traveling Salesman Problem) is not supported when the collection of stops contains waypoints or
rest breaks.
5060 Network Analyst The waypoint contains time windows.
5061 Network Analyst The waypoint contains added cost attribute.
5062 Network Analyst The stop has unknown curb approach.
5063 Network Analyst The point barrier has unknown curb approach.
5064 Network Analyst The facility has unknown curb approach.
5065 Network Analyst The incident has unknown curb approach.
JSON parsing errors

Errors that may occur when dealing with JSON.

6001 JSON parser invalid token exception.
6002 JSON parser invalid character exception.
6003 JSON parser invalid unicode exception.
6004 JSON parser invalid start of JSON exception.
6005 JSON parser invalid end of pair exception.
6006 JSON parser invalid end of element exception.
6007 JSON parser invalid escape sequence exception.
6008 JSON parser invalid end of field name exception.
6009 JSON parser invalid start of field name exception.
6010 JSON parser invalid start of comment exception.
6011 JSON parser invalid decimal digit exception.
6012 JSON parser invalid hex digit.
6013 JSON parser expecting null exception.
6014 JSON parser expecting true exception.
6015 JSON parser expecting false exception.
6016 JSON parser expecting closing quote exception.
6017 JSON parser expecting not a number exception.
6018 JSON parser expecting end of comment exception.
6019 JSON parser unexpected end of data exception.
6020 JSON object expecting start object exception.
6021 JSON object expecting start array exception.
6022 JSON object expecting value object exception.
6023 JSON object expecting value array exception.
6024 JSON object expecting value int32 exception.

6025 JSON object expecting integer type exception.

6026 JSON object expecting number type exception.
6027 JSON object expecting value string exception.
6028 JSON object expecting value bool exception.
6029 JSON object iterator not started exception.
6030 JSON object iterator is finished exception.
6031 JSON object key not found exception.
6032 JSON object index out of range exception.
6033 JSON string writer JSON is complete exception.
6034 JSON string writer invalid JSON input exception.
6035 JSON string writer expecting container exception.
6036 JSON string writer expecting key or end object exception.
6037 JSON string writer expecting value or end array exception.
6038 JSON string writer expecting value exception.
Internal errors
Errors related to the internal ArcGISRuntime domain.

7001 The spatial reference is missing.
7002 The initial viewpoint is missing.
7003 Expected a different response to the request.
7004 The Bing maps key is missing.
7005 The layer type is not supported.
7006 Cannot sync because it is not enabled.
7007 Cannot export tiles because it is not enabled.
7008 Required item property is missing.
7009 Webmap version is not supported.
7011 Spatial Reference invalid or incompatible
Licensing errors
Errors that may occur when working with licensing.

8001 Unlicensed feature exception. Unlicensed feature exception.
8002 License level fixed exception. License level fixed exception.
8003 License level is already set exception. License level is already set exception.
8004 Main license is not set exception. Main license is not set exception.
8005 Unlicensed extension exception. Unlicensed extension exception.
Local server errors

Errors that may occur when working with local server.

9001 Local server failed to start.
9002 A local server's service failed to start.
9003 A local server's service terminated unexpectedly.
9004 The local server has failed.
9005 A local server's service has failed.
Internal library errors

Internal errors related to the use of common libraries.

10001 std::ios_base::failure exception.
10002 std::bad_array_new_length exception.

10003 std::underflow_error exception.

10004 std::system_error exception.
10005 std::range_error exception.
10006 std::overflow_error exception.
10007 std::out_of_range exception.
10008 std::length_error exception.
10009 std::invalid_argument exception.
10010 std::future_error exception.
10011 std::domain_error exception.
10012 std::runtime_error exception.
10013 std::logic_error exception.
10014 std::bad_weak_ptr exception.
10015 std::bad_typeid exception.
10016 std::bad_function_call exception.
10017 std::bad_exception exception.
10018 std::bad_cast exception.
10019 std::bad_alloc exception.
10020 std::exception exception.
Feature service edit errors

Edit errors are returned by the server after you call apply edits on a service feature table. The EditError (EditError) object in the API
wraps these error codes and messages. Refer to feature service error codes for more information.
HTTP, network, and REST errors

Some APIs communicate with servers and services over the World Wide Web using HTTP, such as the low-level REST API. These
services may generate standard HTTP error codes that may have meaning related to the ArcGIS platform.
Error Error Description

Code
Bad request 400 The request sent to the server is not correct.
Unauthorized 401 Authorization to the requested resource is required.
Forbidden 403 Authorization to the requested resource is required.
Not found 404 The requested resource was not found.
Invalid token 498 The access token provided is invalid or expired.
Token required 499 A token was required to access the resource.
Service error 500 The service was not able to fulfill the request, possibly due to invalid input, or the service may not be functioning
properly.
Not 501 The requested service is not implemented.
implemented

Legal
The following legal notices are installed in the legal subfolder of the local download of ArcGIS Runtime SDK for Android.
Copyright and Trademarks
Licensing Terms of Use (End User Licensing Agreement)
Acknowledgments of third parties whose software has been used in permissible forms with ArcGIS Runtime SDKs
The SDK is distributed through Esri's maven repository hosted by Bintray and the EULA is provided under the project license in the
associated project object model file, pom.xml.
For the latest versions of Licensing Terms of Use, third-party acknowledgments, and other legal information, see http://www.esri.com/legal.

ARC GIS Android Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ARC GIS Android Guide

Uploaded by

Copyright:

Available Formats

ArcGIS Runtime SDK for

Copyright 1995-2017 Esri. All rights reserved.

Copyright 1995-2017 Esri. All rights reserved. 2

Route and get directions

Copyright 1995-2017 Esri. All rights reserved. 3

What you get

Copyright 1995-2017 Esri. All rights reserved. 4

Install the SDK

Required permissions and features

Copyright 1995-2017 Esri. All rights reserved. 5

Download, install, and set up the local SDK

Contents of the SDK download

Copyright 1995-2017 Esri. All rights reserved. 6

Migrate to 100.1 from 10.2.x

Graphics overlays and graphics

Copyright 1995-2017 Esri. All rights reserved. 7

Copyright 1995-2017 Esri. All rights reserved. 8

Copyright 1995-2017 Esri. All rights reserved. 9

Develop your first map app

Create a new project in Android Studio

1. Under Quick Start, click Start a new Android Studio project.

Copyright 1995-2017 Esri. All rights reserved. 10

Add the ArcGIS Runtime SDK for Android AAR dependency

Add a MapView to your layout

Copyright 1995-2017 Esri. All rights reserved. 11

Set a map on the MapView

Note: You'll need to import com.esri.arcgisruntime.mapping.ArcGISMap and

Copyright 1995-2017 Esri. All rights reserved. 12

Build and run the app

1. On the Android Studio toolbar, click Run.

Copyright 1995-2017 Esri. All rights reserved. 13

Copyright 1995-2017 Esri. All rights reserved. 14

Copyright 1995-2017 Esri. All rights reserved. 15

Capabilities of your offline map

Offline map patterns

Copyright 1995-2017 Esri. All rights reserved. 16

Create an offline map

Create offline layers

Create an offline map

Create offline layers

Copyright 1995-2017 Esri. All rights reserved. 17

Copyright 1995-2017 Esri. All rights reserved. 18

Layers and tables

Choosing layer types

Copyright 1995-2017 Esri. All rights reserved. 19

Common layer properties

Online tiled layers

Copyright 1995-2017 Esri. All rights reserved. 20

Offline tiled layers

Functional and performance characteristics

Mobile basemap layers

Functional and performance characteristics

Copyright 1995-2017 Esri. All rights reserved. 21

Copyright 1995-2017 Esri. All rights reserved. 22

Feature collection layers

Copyright 1995-2017 Esri. All rights reserved. 23

Map Image layers

Copyright 1995-2017 Esri. All rights reserved. 24

A scene service is used to provide one of the following types of 3D data:

Copyright 1995-2017 Esri. All rights reserved. 25

Copyright 1995-2017 Esri. All rights reserved. 26

Features and graphics

Comparison of features and graphics

How features and graphics relate to a map