licensing. In the concurrent model, a license manager program runs on a server and allocates licenses at a user’s request. This model is often called a “floating license,” because it is assigned, and then taken back when the user is finished, allowing a fixed number of licenses to be shared across many computers. In the single-use model, the license is tied to a specific computer.
Capabilities of ArcGIS Pro
Although it is different in many ways, ArcGIS Pro will eventually have the equivalent capabilities of ArcMap and more. This updating process is ongoing, with new capabilities being added with each release. ArcGIS Pro 2.3, for which this book is tested, represented a significant milestone in which nearly all of ArcMap’s key functions were present, and additional capabilities and improvements are still being added.
ArcGIS Pro integrates the functions of ArcMap, ArcCatalog, ArcToolbox, ArcScene, and ArcGlobe within a single interface so that 3D data visualization and analysis no longer require opening a separate program. ArcGIS Pro retains the Python® and ModelBuilder™ customization modules. Certain aspects that users are accustomed to using as separate features, such as COGO or Maplex™ for ArcGIS®, are now integrated directly into the program. The familiar extensions, such as Spatial Analyst or 3D Analyst, continue to be available and work in much the same way, as additional licensed tools in ArcToolbox.
However, users should be aware that the very design of ArcGIS Pro precludes certain familiar aspects of ArcMap from working precisely the same way. In ArcGIS Pro, the design criteria specify that most actions are geoprocessing events (taking advantage of the multiprocessor computer). Tools have replaced some of the common right-click commands, either as a temporary measure until the functionality is integrated into the GUI, or as a design choice. For example, instead of opening a window to execute a selection using table attributes with the Query Builder, you must run a tool named Select Layer By Attribute.
TIPCan’t find something? Try searching for a tool.
When should I switch?
Several factors will affect the decision of when to switch to ArcGIS Pro.
Reasons for making the switch include:
•Improved performance that takes advantage of multicore architecture
•Seamless integration of two- and three-dimensional visualization, analysis, and editing
•Improved flexibility in creating dynamic labels
•Creating multiple layouts based on the same map or maps
•Tight integration with ArcGIS Online, making it easier to share maps and map services
•A more modern and intuitive GUI
•Expanded use of defaults that can make life easier for inexperienced users
•The product life cycle of ArcMap (See the Esri Support Product Life Cycles website.)
ArcMap users may dispute the “more intuitive interface” claim when encountering ArcGIS Pro for the first time. In truth, the GUI is probably more difficult to learn if you already know ArcMap and have become accustomed to certain ways of doing things. In general, new users find the ArcGIS Pro GUI easier to learn. Over time, you get used to it.
The software also implements reasonable defaults more than ArcMap, hiding complications from beginners. This feature has both benefits and pitfalls. For example, ArcGIS Pro does not automatically warn users when two different geographic coordinate systems (datums) are being used in the same map (although this warning can be turned on). This choice makes little difference unless the user is working at very large scales with precise data, and in many situations the issue can be safely ignored. However, it can cause difficulties later if inexperienced users compile data for a project without being aware that the feature classes and rasters use multiple datums.
When ArcMap retires, the software will continue to be available, and people can continue to use it, but it will no longer be updated or supported. A similar process occurred when ArcInfo® Workstation and ArcView became ArcGIS® Desktop.
Delaying the switch might be wise under some circumstances:
•The organization does not have enough computers capable of running ArcGIS Pro.
•Some critical functionality may not yet be available.
•The organization has many custom scripts or tools that must be updated and tested.
•Third-party extensions (such as HEC-RAS or MODFLOW) may not yet be supported.
•Maps and layouts must be shared with ArcMap users.
Several other considerations regarding data must also be considered:
•ArcGIS Pro does not recognize personal geodatabases or ArcInfo coverages.
•The organization and structure of maps and layouts are different.
•Data management in ArcGIS Pro has complications not seen in ArcCatalog.
•Absolute/relative paths are now fixed by default and have less flexibility.
•The Excel™ interpreter is different and seems less forgiving than the one in ArcMap.
As discussed in the next section, even though the data format is consistent (the geodatabase), the way that files are organized is quite altered and not as flexible. To switch to ArcGIS Pro, you must learn different ways of doing things. For example, it is extremely difficult to rename a project, so you are stuck with the initial name, even if you decide it is inappropriate or confusing. You no longer have a choice whether to use absolute or relative paths in a document; the choice is made by the software. This feature removes a potential trap for inexperienced users, and the defaults usually work well, but experienced users who are accustomed to controlling this option may find that they need to change how they organize datasets.
If you use many Excel files, problems may occur. The Excel interpreter has had difficulty reading files, in my experience, and usually I must resort to the comma-delimited CSV file format instead. The errors can be delayed and subtle. For example, in one project an Excel table imported just fine but generated fatal errors when it was exported to a geodatabase. A CSV version of the same table was imported and exported to the geodatabase without trouble.
Mapping differences to consider before switching:
•The default symbols follow a different cartographic style.
•Previous custom styles (such as Civic or Forestry) are not included and must be imported.
•Labels are more flexible, but the options are more numerous and take getting used to.
•Annotation editing tools are still catching up to ArcMap in functionality and reliability.
The symbol styles have been changed to favor web mapping applications and may make it difficult to see multiple layers well. Dark colors with white outlines dominate the default symbols, and although they can be changed, it adds an extra step when a feature class is added to a map. Previous custom style sets must be imported from the ArcMap symbol folder, although if a map document is imported, the symbols will be included. In general, the map document import function works well, although a few settings may not be preserved and will need to be reset, such as the data frame clip setting.
Annotation
