Customizing ArcGIS for Desktop
In this section, we will discuss the benefits of customizing ArcGIS. When a particular
requirement or feature is not available in ArcGIS, we can actually extend the ArcGIS
functionality to do that for us. In this book, we will explain two different approaches
for deploying ArcGIS customization respectively: add-ins and extending ArcObjects.
You will need the ArcObjects SDK to start the development. There are many other
ways for customizing ArcGIS, including user interface customization using Visual
Basic for Applications (VBA), modeling and scripting using Python, and building
standalone applications using ArcGIS Engine. In this book, we will use the add-ins
and extending ArcObjects method.
ArcGIS for Desktop comes with great set of built-in tools that can help you solve
interesting mapping problems. However, there comes a time where your problem is a
complex one. This is where you might need to extend and customize the functionality
of ArcGIS to provide a suitable solution to your problem. The examples in this
book require customizations to tackle them. In this section, we discuss the different
customization approaches to set up our development environment. Another reason
to extend ArcGIS, for example, a certain functionality, might be available in ArcGIS,
but you need to perform 10 or 15 steps to achieve it, and customizing the product can
group and automate these steps so that you can default all of them in a few clicks.
The first attempted approach to providing customization for ArcGIS was through
VBA. This is similar to the macroscripts in Microsoft Word and Excel. You could
write an application and save it in the map document and later share this document,
and the person running your document could use your application. It was a
convenient approach for sharing mapping, but with many problems. The main
problem was the security. The document might contain malicious code that would
execute with user privileges and can potentially harm the user. That is why this
approach was discouraged and has been replaced with ArcGIS add-ins and the
extensions building approach. Today, you can still develop using VBA by installing
the VBA compatibility setup.
Customizing ArcGIS for Desktop requires that you either build add-ins or use the
classical Dynamic Link Library (DLL) approach and register it with ArcGIS for it to
work. Both approaches use ArcObjects as the underlying technology, however, the
final building technique is different.
These built approaches are not share-friendly, however, Esri came up with a
beautiful solution and platform for sharing, and that is ArcGIS Online. That
discussion though should be an entirely different book
In this section, we will discuss the benefits of customizing ArcGIS. When a particular
requirement or feature is not available in ArcGIS, we can actually extend the ArcGIS
functionality to do that for us. In this book, we will explain two different approaches
for deploying ArcGIS customization respectively: add-ins and extending ArcObjects.
You will need the ArcObjects SDK to start the development. There are many other
ways for customizing ArcGIS, including user interface customization using Visual
Basic for Applications (VBA), modeling and scripting using Python, and building
standalone applications using ArcGIS Engine. In this book, we will use the add-ins
and extending ArcObjects method.
ArcGIS for Desktop comes with great set of built-in tools that can help you solve
interesting mapping problems. However, there comes a time where your problem is a
complex one. This is where you might need to extend and customize the functionality
of ArcGIS to provide a suitable solution to your problem. The examples in this
book require customizations to tackle them. In this section, we discuss the different
customization approaches to set up our development environment. Another reason
to extend ArcGIS, for example, a certain functionality, might be available in ArcGIS,
but you need to perform 10 or 15 steps to achieve it, and customizing the product can
group and automate these steps so that you can default all of them in a few clicks.
The first attempted approach to providing customization for ArcGIS was through
VBA. This is similar to the macroscripts in Microsoft Word and Excel. You could
write an application and save it in the map document and later share this document,
and the person running your document could use your application. It was a
convenient approach for sharing mapping, but with many problems. The main
problem was the security. The document might contain malicious code that would
execute with user privileges and can potentially harm the user. That is why this
approach was discouraged and has been replaced with ArcGIS add-ins and the
extensions building approach. Today, you can still develop using VBA by installing
the VBA compatibility setup.
Customizing ArcGIS for Desktop requires that you either build add-ins or use the
classical Dynamic Link Library (DLL) approach and register it with ArcGIS for it to
work. Both approaches use ArcObjects as the underlying technology, however, the
final building technique is different.
These built approaches are not share-friendly, however, Esri came up with a
beautiful solution and platform for sharing, and that is ArcGIS Online. That
discussion though should be an entirely different book
ليست هناك تعليقات:
إرسال تعليق