5. Running the tool

The operation of the Data Searches tool is explained in this section. While the interface is similar between the ArcGIS Pro, ArcMap and MapInfo implementations of the tool, there are some differences. This user guide is specific to the ArcGIS Pro version of the tool.

As discussed in the Setting up the tool section, the Data Searches tool is operated from a GIS project file within which the data required to run the tool is already loaded in the active map window. Therefore, before running the tool, ensure the following conditions are met:

  • A GIS project has been created which contains both the search sites layer(s) and the data layers (containing the sites and species that will be queried) in a map window.

  • The search sites layer(s) have a column that contains the unique reference for each search, and this reference has the correct format.

  • The tool XML configuration file ‘DataSearches.xml’ has been set up and is named correctly.

  • One or more user XML profiles have been set up and are in the same folder as the tool XML file.

  • The Data Searches tool has been installed and set up.

See also

Please refer to the Setting up the tool section for further information about any of these requirements.

5.1. Opening the tool

To open the Data Searches tool in ArcGIS Pro, open the Tools menu bar and click on the Data Searches tool button (Fig. 5.1).

../_images/LaunchSearchesTool.png

Fig. 5.1 Launching the Data Searches tool in ArcGIS Pro

Note

Once the tool has been opened the window pane will remain open unless it is manually closed. As with other dockable windows in ArcGIS Pro, the window can docked anywhere in the ArcGIS Pro application and can be pinned or hidden when not in use.

5.2. Initial set-up

In order to function, the tool needs to know the location of the XML configuration files. The first time the tool is run, or whenever the configuration file is moved, the user must specify the folder containing the XML files.

Click on the ‘Open folder’ button (Fig. 5.2).

../_images/OpenXMLFolderButton.png

Fig. 5.2 Click on the Open Folder button

Then navigate to the folder containing the XML files and click OK. If the tool XML file is present and its structure is correct, the list of user profiles will appear in the drop-down list (Fig. 5.3).

../_images/SelectConfigFolder.png

Fig. 5.3 Locating the configuration file folder

Note

The location of the configuration folder will be stored for future use.

5.3. Loading a profile

If more than one user XML profile is found, and the tool configuration file is configured to allow the user to choose the XML profile, then the Profile tab will appear to allow the user to choose an XML profile (Fig. 5.4).

../_images/SelectXMLProfile.png

Fig. 5.4 Example list of XML profiles to select

Select a profile and click ‘Load’ to start the tool using that profile. If there are any structural issues with the selected XML profile, the tool will display a message with the error it has encountered, and not load any further (Fig. 5.5).

../_images/LaunchWarning.png

Fig. 5.5 Example warning message displayed for any XML structural issues

Provided that the selected XML profile is otherwise correct, the Search tab will display (Fig. 5.6).

../_images/DisplayForm.png

Fig. 5.6 The form displaying all of the available search fields and options

Note

If there is only one user XML profile, or if the tool configuration file is configured to not allow the user to choose the XML profile, then the default XML profile will lead automatically (if found).

If any of the map layers specified in the XML profile are not present in the active map window then a warning message will appear (Fig. 5.7).

../_images/MissingLayersWarning.png

Fig. 5.7 Example warning message that one of the layers is missing

A warning message will also appear on the form (Fig. 5.8).

../_images/MissingLayersWarning2.png

Fig. 5.8 Example warning message that one of the layers is missing

Note

Layers missing from the active map will not appear in the ‘Layers to Search’ list and hence will not be available for selection.

5.6. Search results

When the search is finished, any exported data tables, saved GIS layers, the search feature GIS layer, the buffer GIS layer, and the log file are all saved in the ‘GISFolder’ specified in the XML document. Any saved GIS layers resulting from the search are also added to the map interface (if requested).

Note

Only results for those layers for which features were found within the search radius are saved and added to the map. Empty files will not be generated.

Search results are added to the active map as follows:

  • If ‘Yes’ is selected in the ‘Add Layers to Map’ search option, each saved GIS layer (where ‘Yes’ is selected in the ‘KeepLayer’ attribute in the configuration) is added to a new group layer. The name of the group layer follows the ‘GroupLayerName’ format specified in the XML profile, with any special characters replaced with the ‘RepChar’ value (e.g. ‘LERC/24/001’ becomes ‘001’ if the ‘GroupLayerName’ value is %subref%).

  • If either ‘Yes - with labels’ or ‘Yes - without labels’ are selected in the ‘Add Layers to Map’ search option and, if a layer file name is specified in the ‘LayerFileName’ attribute in the configuration for a saved layer, symbology is applied to that layer using the specified layer file.

  • If ‘Yes - with labels’ is selected in the ‘Add Layers to Map’ search option and, if a column name is specified in the ‘LabelColumn’ attribute in the configuration for a saved layer, labels are applied to that layer (as specified in the configuration using the ‘LabelClause’ attribute).

  • A buffer GIS layer, created during the search, will be added to the new group layer and symbology will be applied using the appropriate layer file (as specified in the configuration using the ‘BufferLayerName’ general attribute).

  • Unless the buffer radius specified is zero, the map will zoom to the extent of the buffer layer that was created during the search.

An example of how the results will appear in ArcGIS Pro is shown in Fig. 5.20.

../_images/Results.png

Fig. 5.20 Example results from search process