It is common for ArcMap users to use a range of MXDs as standard card layouts. For example, those standard card layouts are stored on a shared network drive and then reused by all colleagues.
The new “Layout Gallery” introduced in the newest version of ArcGIS Pro offers a way to do this within Pro:
When you need to quickly make a layout, you don’t always want to build it from scratch. Instead, you want to quickly select an existing layout and make a few minor updates. With the new layout gallery in ArcGIS Pro 2.5, you can do just that!
This handy gallery contains various layout files (.pagx) that can be accessed from any project. Just select a layout and it’s added to your project. Then point it to your map and BAM! your layout is complete.
To be accurate, layout files have been around for multiple versions of ArcGIS Pro, but you always had to navigate to a file and import it. And, you never got to preview what the layout looked like before you added it. The gallery allows you to easily see and select layout files.
Access and Customize the Gallery
To access the gallery, go to the Layout tab on the ribbon and choose Import Layout. The gallery appears. Select any file to add it as a new layout in your project.
If you want to use a layout file not in the gallery, press the Import layout file… button at the bottom of the gallery.
By default the gallery shows 12 different layouts with different styles, elements, page sizes, and page orientations. These are nice, but I’d really prefer to have the gallery show me layouts I’ve created that fit my cartographic style or project requirements. Turns out, you can!
You can change the folder referenced by the gallery to point to any folder you have access to. The layout files in that folder (and it’s subfolders) will now be the ones in the gallery.
- Create a folder with all your layout files
- Click on the Project tab on the ribbon
- Click Options
- Go to Layout
- Update the Import Gallery Path to point your layout file folder
Now when I open the gallery, I only see the layout files in my folder and its subfolders. And, the subfolder names are used as headings to help organize my layouts. Awesome!
You may notice that the layout names in the gallery aren’t the same as the file names. The gallery displays the title and thumbnail stored in the layout file’s metadata. You need to edit the metadata directly to update the name or thumbnail in the gallery.
To do this, connect to the folder containing the layout files in the Catalog Pane, right click on the layout file and choose Edit Metadata. Then you can adjust the layout file’s title and thumbnail, which are reflected in the gallery. Make sure you edit the metadata for the layout FILE, not the layout itself.
Now you can customize your layout gallery to easily add your favorite layout files to any project. Have fun!
Thanks to Aubri Kinghorn for sharing this with us.
Prior to use Web Feature Services in ArcMap, the Data Interoperability extension must be installed. From ArcMap 10.5 is just downloading and installing the extension enough, this does not involve any additional costs. For previous versions however, a separate Data Interoperability license is needed. Once the extension is installed (and authorized if version < 10.5), you can make a connexion to a WFS service through the Catalog, by adding a new Interoperability connection. Subsequently, add the service to your map by the Add Data dialog window or by a simple drag-and-drop from the Catalog window. For a more detailed workflow, please refer to the Adding a WFS service to ArcMap documentation.
The content of a WMS server can easily be used in ArcMap, without needing to install any additional extension. To add a wms service as a layer in a map, start by establishing a connection to the server, and then simply add the service to your map. The connection can be made through the Catalog window, or after opening the Add Data dialog box. For a more detailed workflow, please refer to the Adding WMS services documentation.
ArcGIS Pro automatically starts an edit session when you modify existing data or create data. For more information, see Automatic edit sessions in the help topic Editing in ArcGIS Pro.
Many ArcMap styles have been retired and are not included as system styles in ArcGIS Pro. However, these styles can be imported from ArcMap. See Import an ArcMap style into the project. A number of these styles have already been converted to ArcGIS Pro *.stylx format and can be downloaded fromArcGIS Online at Esri Styles.
Yes. If you have an ArcGIS Desktop license for an extension product, you are licensed to use the same extension in ArcGIS Pro if it is available. See ArcGIS Pro extensions for a list of available extensions. Extension licenses in ArcGIS Pro are managed using the same license type (for example, Named User) as your ArcGIS Pro license.
You cannot export a map from ArcGIS Pro as a map document (.mxd). However, web maps shared from ArcGIS Pro can be opened in ArcMap, ArcGIS Online, or ArcGIS Enterprise.
When you import a map document (.mxd), all the data frames become maps in your ArcGIS Proproject, but only one of them opens. You can open the other maps from the Catalog pane by clicking the Project tab at the top of the pane and expanding the Maps item. Alternatively, you can open the catalog view from the View tab on the ribbon and browse to the maps in your project.
Yes, map documents (.mxd), scenes (.sxd), and globes (.3DD) can be imported into ArcGIS Pro and saved in a project. For more information, see Import a map or a map package in the help topic Add maps and scenes to a project. The same geodatabase and shapefile datasets can be used by both applications. Web layers shared from ArcGIS Pro can be opened in ArcMap. Also, ArcMap and ArcGIS Pro can run side by side on the same machine. However, ArcGIS Pro projects cannot be imported into ArcMap.
No, models that are built new, or opened and saved in ArcGIS Pro, cannot be used directly in ArcMap. However, you can save the containing toolbox as a previous version and use that toolbox in ArcMap. It’s safest to make a backup of the original toolbox before modifying any models in ArcGIS Pro. Keep in mind that many tools and new data formats are only available in ArcGIS Pro, so the model still may not work in ArcMap.
Yes, most of the time. However, if the model includes a tool that is not available in ArcGIS Pro, the model will not work. You may need to wait until that tool is available in a future release of ArcGIS Pro. Alternatively, you may be able to remove the tool and use a workaround. Additionally, if a tool in the model has changed in ArcGIS Pro, the model will not work until you update the model (make a backup of the toolbox, open the model in ArcGIS Pro, validate, and save the model). Refer to a tool’s help topic to determine what needs to change for the tool to work in ArcGIS Pro. One common issue is that the Calculate Field tool no longer supports Visual Basic (VB) expressions. Learn more about migrating ModelBuilder workflows to ArcGIS Pro.
The majority of ArcMap geoprocessing tools are available in ArcGIS Pro. However, some tools are not available. In some cases, these tools may be available in a future release. Tools that work with data formats that are not supported in ArcGIS Pro, such as coverages, will not be available in the future.
Usually, yes. ArcGIS Pro uses Python 3.x, while other applications in ArcGIS Desktop and ArcGIS Server use Python 2.x. Despite some significant differences between these versions of Python, many geoprocessing scripts can be used as-is in both ArcMap and ArcGIS Pro. You can read about Python migration for ArcGIS Pro, and use the Analyze Tools For Pro geoprocessing tool to analyze a script or toolbox for necessary updates.
No, ArcGIS Pro has a new .NET API, and the functionality and workflows are different from what exists in ArcMap. The new API was built using ArcObjects; however, ArcObjects is not exposed directly.
No, you can install ArcGIS Pro on a machine that has any version of ArcMap, or on a machine without any Esri products. However, you can only install one version of ArcGIS Pro per machine.