Book Image

Learning ArcGIS Runtime SDK for .NET

By : Ron Vincent
Book Image

Learning ArcGIS Runtime SDK for .NET

By: Ron Vincent

Overview of this book

ArcGIS is a geographic information system (GIS) that enables you to work with maps and geographic information. It can be used to create and utilize maps, compile geographic data, analyze mapped information, share and discover geographic information and manage geographic information in a database. This book starts by showing you where ArcGIS Runtime fits within Esri’s overall platform strategy. You'll create an initial map using the SDK, then use it to get an understanding of the MVVM model. You'll find out about the different kinds of layers and start adding layers, and you'll learn to transform maps into a 3D scene. The next chapters will help you comprehend and extract information contained in the maps using co-ordinates and layer objects. Towards the end, you will learn to set the symbology, decide whether to use 2D or 3D, see how to implement 2D or 3D, and learn to search and find objects. You'll also get to grips with many other standard features of the Application Programming Interface (API), including create applications and finally testing, licensing, and deploying them. Once completed, you will be able to meet most of the common requirements of any mapping application for desktop or mobile platforms.
Table of Contents (19 chapters)
Learning ArcGIS Runtime SDK for .NET
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
3
Maps and Layers
12
Configuring, Licensing, and Deploying
Index

Architecture of ArcGIS Runtime


As noted earlier, ArcGIS Runtime is written in C++ and compiled on each supported platform natively. Unlike ArcGIS Desktop and ArcGIS Engine, which relied heavily on COM, Runtime Core is pure C++. Therefore, it is as small and efficient as possible. The following architecture diagram shows the high-level architecture of ArcGIS Runtime. As you can see in the yellow box, there is C++ Runtime Core. This means that it makes full use of the hardware and graphics card of each OS. This aspect allows very fast performance for displaying the map content and analysis; it literally means that the API is pretty much the same across all platforms. In other words, Esri is maximizing code reuse, while at the same time, maximizing performance because it is natively compiled. Not only that, Runtime Core is actually pretty small. On Windows desktop, at the current release, it's only about 23 MB in size for the x86 build. For the x64 build, it's only about 30 MB. As such, it will fit easily on disk for any modern device. Esri has also developed this architecture so that it also minimizes battery use. Lastly, each API on top of Runtime Core has been designed to expose the full capabilities of Runtime Core.

When it comes to the rendering engine, Runtime Core uses OpenGL, OpenGL ARB shader, OpenGL ES 2.0, DirectX 9, and DirectX 11. Each rendering technology is selected to optimize the performance on each OS. Therefore, a desktop computer with a powerful graphics card can achieve maximum performance whereas a mobile device will obviously use a less powerful graphics card but it still maximizes the use of OpenGL ES, for example. Not shown in the architecture diagram is the Hardware Abstraction Layer (HAL) between the rendering engines and Runtime Core. With HAL, Esri can add even more rendering engine capabilities on top of these native rendering technologies, such as DirectX:

As a developer of ArcGIS Runtime, it's important to understand that the choices you make at the API level at the top of architecture really decide what happens at the HAL level and lower.