linkage-mapper3.0
weixin_6108851714.14MB需要积分:1资源文件列表:
linkage_mapper_3_0_0.zip 大约有179个文件 
linkage_mapper_3_0_0/- linkage_mapper_3_0_0/demo/
- linkage_mapper_3_0_0/demo/data/
linkage_mapper_3_0_0/demo/data/cc_climate.tfw 96B - linkage_mapper_3_0_0/demo/data/cc_climate.tif 1.81MB
- linkage_mapper_3_0_0/demo/data/cc_climate.tif.aux.xml 1.98KB
- linkage_mapper_3_0_0/demo/data/cc_climate.tif.ovr 469.88KB
- linkage_mapper_3_0_0/demo/data/cc_climate.tif.xml 5.73KB
- linkage_mapper_3_0_0/demo/data/cc_cores.cpg 9B
- linkage_mapper_3_0_0/demo/data/cc_cores.dbf 174B
- linkage_mapper_3_0_0/demo/data/cc_cores.prj 450B
- linkage_mapper_3_0_0/demo/data/cc_cores.sbn 300B
- linkage_mapper_3_0_0/demo/data/cc_cores.sbx 132B
- linkage_mapper_3_0_0/demo/data/cc_cores.shp 325.7KB
- linkage_mapper_3_0_0/demo/data/cc_cores.shp.xml 429.96KB
- linkage_mapper_3_0_0/demo/data/cc_cores.shx 244B
- linkage_mapper_3_0_0/demo/data/cc_resistances.tfw 96B
- linkage_mapper_3_0_0/demo/data/cc_resistances.tif 1.34MB
- linkage_mapper_3_0_0/demo/data/cc_resistances.tif.aux.xml 1.92KB
- linkage_mapper_3_0_0/demo/data/cc_resistances.tif.ovr 348.6KB
- linkage_mapper_3_0_0/demo/data/cc_resistances.tif.xml 6.57KB
- linkage_mapper_3_0_0/demo/data/distances_lm_cores.txt 313B
- linkage_mapper_3_0_0/demo/data/distances_lp_cores.txt 210B
- linkage_mapper_3_0_0/demo/data/lm_cores.CPG 5B
- linkage_mapper_3_0_0/demo/data/lm_cores.dbf 102B
- linkage_mapper_3_0_0/demo/data/lm_cores.prj 494B
- linkage_mapper_3_0_0/demo/data/lm_cores.sbn 204B
- linkage_mapper_3_0_0/demo/data/lm_cores.sbx 132B
- linkage_mapper_3_0_0/demo/data/lm_cores.shp 8.11KB
- linkage_mapper_3_0_0/demo/data/lm_cores.shp.xml 1.24KB
- linkage_mapper_3_0_0/demo/data/lm_cores.shx 148B
- linkage_mapper_3_0_0/demo/data/lm_resistances.tfw 93B
- linkage_mapper_3_0_0/demo/data/lm_resistances.tif 933.98KB
- linkage_mapper_3_0_0/demo/data/lm_resistances.tif.aux.xml 1.72KB
- linkage_mapper_3_0_0/demo/data/lm_resistances.tif.ovr 284.03KB
- linkage_mapper_3_0_0/demo/data/lm_resistances.tif.xml 5.77KB
- linkage_mapper_3_0_0/demo/data/lp_climate_refugia.tfw 94B
- linkage_mapper_3_0_0/demo/data/lp_climate_refugia.tif 78.16KB
- linkage_mapper_3_0_0/demo/data/lp_climate_refugia.tif.aux.xml 1.63KB
- linkage_mapper_3_0_0/demo/data/lp_climate_refugia.tif.ovr 14.86KB
- linkage_mapper_3_0_0/demo/data/lp_climate_refugia.tif.xml 23.64KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_current.tfw 94B
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_current.tif 587.83KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_current.tif.aux.xml 1.82KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_current.tif.ovr 134.85KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_current.tif.xml 19.06KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_future.tfw 94B
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_future.tif 586.17KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_future.tif.aux.xml 1.81KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_future.tif.ovr 134.22KB
- linkage_mapper_3_0_0/demo/data/lp_climate_sig_future.tif.xml 8.11KB
- linkage_mapper_3_0_0/demo/data/lp_cores.cpg 5B
- linkage_mapper_3_0_0/demo/data/lp_cores.dbf 121B
- linkage_mapper_3_0_0/demo/data/lp_cores.prj 468B
- linkage_mapper_3_0_0/demo/data/lp_cores.sbn 196B
- linkage_mapper_3_0_0/demo/data/lp_cores.sbx 132B
- linkage_mapper_3_0_0/demo/data/lp_cores.shp 46.07KB
- linkage_mapper_3_0_0/demo/data/lp_cores.shp.xml 142.52KB
- linkage_mapper_3_0_0/demo/data/lp_cores.shx 140B
- linkage_mapper_3_0_0/demo/data/lp_resistances.tfw 94B
- linkage_mapper_3_0_0/demo/data/lp_resistances.tif 635.11KB
- linkage_mapper_3_0_0/demo/data/lp_resistances.tif.aux.xml 1.85KB
- linkage_mapper_3_0_0/demo/data/lp_resistances.tif.ovr 127.92KB
- linkage_mapper_3_0_0/demo/data/lp_resistances.tif.xml 7.47KB
- linkage_mapper_3_0_0/demo/maps/
- linkage_mapper_3_0_0/demo/maps/CC Demo Results.mxd 343KB
- linkage_mapper_3_0_0/demo/maps/CC Demo.mxd 490.5KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/.backups/
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/.backups/LM ArcGIS Pro Demo.aprx 428.97KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000001.gdbindexes 110B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000001.gdbtable 302B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000001.gdbtablx 5.03KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000001.TablesByName.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000002.gdbtable 2.01KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000002.gdbtablx 5.03KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000003.gdbindexes 42B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000003.gdbtable 525B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000003.gdbtablx 5.03KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.CatItemsByPhysicalName.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.CatItemsByType.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.FDO_UUID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.gdbindexes 310B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.gdbtable 1.67KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.gdbtablx 5.03KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.horizon 32B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000004.spx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000005.CatItemTypesByName.atx 12.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000005.CatItemTypesByParentTypeID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000005.CatItemTypesByUUID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000005.gdbindexes 296B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000005.gdbtable 2.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000005.gdbtablx 5.03KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000006.CatRelsByDestinationID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000006.CatRelsByOriginID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000006.CatRelsByType.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000006.FDO_UUID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000006.gdbindexes 318B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000006.gdbtable 190B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000006.gdbtablx 32B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.CatRelTypesByBackwardLabel.atx 12.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.CatRelTypesByDestItemTypeID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.CatRelTypesByForwardLabel.atx 12.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.CatRelTypesByName.atx 12.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.CatRelTypesByOriginItemTypeID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.CatRelTypesByUUID.atx 4.02KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.gdbindexes 602B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.gdbtable 3.54KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/a00000007.gdbtablx 5.03KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/gdb 4B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.gdb/timestamps 400B
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/Default.tbx 4KB
- linkage_mapper_3_0_0/demo/maps/LM ArcGIS Pro Demo/LM ArcGIS Pro Demo.aprx 428.94KB
- linkage_mapper_3_0_0/demo/maps/LM Demo Results.mxd 341.5KB
- linkage_mapper_3_0_0/demo/maps/LM Demo.mxd 309.5KB
- linkage_mapper_3_0_0/demo/maps/LP Demo Results.mxd 374KB
- linkage_mapper_3_0_0/demo/maps/LP Demo.mxd 335KB
- linkage_mapper_3_0_0/demo/output/
- linkage_mapper_3_0_0/demo/scripts/
- linkage_mapper_3_0_0/demo/scripts/bm_demo.py 1.29KB
- linkage_mapper_3_0_0/demo/scripts/cc_demo.py 1.84KB
- linkage_mapper_3_0_0/demo/scripts/cm_demo.py 1.04KB
- linkage_mapper_3_0_0/demo/scripts/lm_demo.py 2.37KB
- linkage_mapper_3_0_0/demo/scripts/lp_demo.py 3.23KB
- linkage_mapper_3_0_0/demo/scripts/pp_demo.py 1.43KB
- linkage_mapper_3_0_0/LICENSE.txt 31.71KB
- linkage_mapper_3_0_0/resources/
- linkage_mapper_3_0_0/resources/LM Logo.png 14.72KB
- linkage_mapper_3_0_0/resources/LM Logo.xcf 21.29KB
- linkage_mapper_3_0_0/resources/lm_build.bat 1.89KB
- linkage_mapper_3_0_0/resources/lm_run.py 732B
- linkage_mapper_3_0_0/toolbox/
- linkage_mapper_3_0_0/toolbox/Linkage Mapper.tbx 1.8MB
- linkage_mapper_3_0_0/toolbox/scripts/
- linkage_mapper_3_0_0/toolbox/scripts/barrier_master.py 2.58KB
- linkage_mapper_3_0_0/toolbox/scripts/CcDlgContent.xsl 23.27KB
- linkage_mapper_3_0_0/toolbox/scripts/cc_config.py 2.71KB
- linkage_mapper_3_0_0/toolbox/scripts/cc_grass_cwd.py 8.54KB
- linkage_mapper_3_0_0/toolbox/scripts/cc_main.py 17.64KB
- linkage_mapper_3_0_0/toolbox/scripts/cc_util.py 1012B
- linkage_mapper_3_0_0/toolbox/scripts/circuitscape_master.py 5.99KB
- linkage_mapper_3_0_0/toolbox/scripts/clip_corridors.py 3.45KB
- linkage_mapper_3_0_0/toolbox/scripts/delete_cwds.py 1.12KB
- linkage_mapper_3_0_0/toolbox/scripts/iterate_barriers.py 21.72KB
- linkage_mapper_3_0_0/toolbox/scripts/LmDlgContent.xsl 23.94KB
- linkage_mapper_3_0_0/toolbox/scripts/LmPinchDlgContent.xsl 22.71KB
- linkage_mapper_3_0_0/toolbox/scripts/lm_config.py 16.77KB
- linkage_mapper_3_0_0/toolbox/scripts/lm_master.py 6.56KB
- linkage_mapper_3_0_0/toolbox/scripts/lm_retry_decorator.py 2.32KB
- linkage_mapper_3_0_0/toolbox/scripts/lm_settings.py 696B
- linkage_mapper_3_0_0/toolbox/scripts/lm_util.py 88.12KB
- linkage_mapper_3_0_0/toolbox/scripts/lm_util_config.py 334B
- linkage_mapper_3_0_0/toolbox/scripts/lm_version.py 21B
- linkage_mapper_3_0_0/toolbox/scripts/logfile_upgrade.py 2.05KB
- linkage_mapper_3_0_0/toolbox/scripts/LpDlgContent.xsl 24.77KB
- linkage_mapper_3_0_0/toolbox/scripts/lp_main.py 30.09KB
- linkage_mapper_3_0_0/toolbox/scripts/lp_settings.py 1.29KB
- linkage_mapper_3_0_0/toolbox/scripts/raster_aggregator.py 5.08KB
- linkage_mapper_3_0_0/toolbox/scripts/s1_getAdjacencies.py 8.88KB
- linkage_mapper_3_0_0/toolbox/scripts/s2_buildNetwork.py 21.51KB
- linkage_mapper_3_0_0/toolbox/scripts/s3_calcCwds.py 33.63KB
- linkage_mapper_3_0_0/toolbox/scripts/s4_refineNetwork.py 9.26KB
- linkage_mapper_3_0_0/toolbox/scripts/s5_calcLccs.py 17.76KB
- linkage_mapper_3_0_0/toolbox/scripts/s6_barriers.py 36.03KB
- linkage_mapper_3_0_0/toolbox/scripts/s7_centrality.py 9.19KB
- linkage_mapper_3_0_0/toolbox/scripts/s8_pinchpoints.py 24.86KB
- linkage_mapper_3_0_0/toolbox/styles/
- linkage_mapper_3_0_0/toolbox/styles/Linkage Mapper.style 676KB
- linkage_mapper_3_0_0/toolbox/styles/Linkage Mapper.stylx 80KB
- linkage_mapper_3_0_0/user_guides/
- linkage_mapper_3_0_0/user_guides/Barrier Mapper User Guide.pdf 695.65KB
- linkage_mapper_3_0_0/user_guides/Centrality Mapper User Guide.pdf 363.37KB
- linkage_mapper_3_0_0/user_guides/Climate Linkage Mapper User Guide.docx.pdf 388.68KB
- linkage_mapper_3_0_0/user_guides/Developer Documentation/
- linkage_mapper_3_0_0/user_guides/Developer Documentation/Linkage Priority Developer Documentation.docx 296.63KB
- linkage_mapper_3_0_0/user_guides/Linkage Pathways Linkage Mapper User Guide.pdf 1.52MB
- linkage_mapper_3_0_0/user_guides/Linkage Priority User Guide.pdf 1.19MB
- linkage_mapper_3_0_0/user_guides/Pinchpoint Mapper User Guide.pdf 673.52KB
资源介绍:
Linkage Mapper是用于支撑区域野生动物栖息地连通性分析的GIS工具。它由几个Python脚本组成，打包为ArcGIS工具箱，可以自动绘制野生动物栖息地连接走廊。开发者为了支持2010年华盛顿野生动物栖息地连接工作，并将其公开用于其他野生动物的连接性评估。 Linkage Mapper使用核心栖息地矢量图斑和阻力栅格来绘制核心区域之间的最低成本联系。阻力栅格中每一个像元都有一个反映能量消耗、移动难度或死亡风险的值。阻力值通常由像元特性决定，如土地覆盖或房屋密度，并结合特定的物种的景观阻力。当动物离开特定的核心栖息地时，成本加权分析会累积总运动阻力图。这些脚本使用ArcGIS和Python函数来识别相邻的核心区域，并在他们之间创建成本最低的走廊地图。这些脚本能够标准化和合并走廊地图，并形成一个综合走廊地图。结果显示，每个网格单元在提供核心区域之间的连接方面的相对价值，允许用户识别哪些走廊由遇到更多或更少的特性，这些特性有助于或阻碍核心区域之间的移动。 目前的版本新开发的工具，可用于绘制走廊内的夹点（使用Circuitscape），绘制具有高度网络中心性的核心区域和走廊。
1
Linkage Mapper Toolbox:
Linkage Pathways Tool User Guide
Version 3.0—Updated July 2021
Brad McRae
1
and Darren Kavanagh
2
1
The Nature Conservancy
2
Adze Informatics
Acknowledgements
Brian Cosentino made substantial coding contributions to early versions of this toolbox. Viral
Shah contributed code from his thesis for network analyses. Jeff Jenness supported this work
with updates to the Conefor Inputs tool. Thanks to Andrew Gilmer and Theresa Nogeire for
helpful comments on this user guide. Thanks also to the Washington Habitat Connectivity
Working Group for feedback on these tools as they were being developed. John Gallo and
Randal Greene made minor changes such as terminology and screengrab updates for the v2.0
Release.
Software Requirements and Licensing
Linkage Mapper requires ArcGIS Desktop (10.3 or greater) or ArcGIS Pro, with the ArcGIS
Spatial Analyst extension. If you are using ArcGIS Desktop and do not have an Advanced
license, you will also need to install the Conefor Inputs tool (see below). Linkage Mapper is
provided free of charge and is licensed under a GNU General Public License.
Preferred Citation
McRae, B.H. and D.M. Kavanagh. 2011. Linkage Mapper Connectivity Analysis Software. The
Nature Conservancy, Seattle WA. Available at: https://circuitscape.org/linkagemapper.
2
Table of Contents
1. Introduction ............................................................................................................................. 3
1.1 Background ..................................................................................................................... 3
1.2 Before you begin– a note about connectivity modeling and software
limitations ....................................................................................................................... 3
2 Installation............................................................................................................................... 4
3 Using Linkage Pathways......................................................................................................... 5
3.1 Input data requirements................................................................................................... 5
3.2 Prepping your data and work spaces ............................................................................... 5
3.3 Running the toolbox ........................................................................................................ 7
4 What the Steps Do ................................................................................................................ 10
Step 1: Identify adjacent (neighboring) core areas ................................................................... 11
Step 2: Construct a network of core areas using adjacency and distance data ......................... 11
Step 3: Calculate cost-weighted distances and least-cost paths ................................................ 12
Step 4: Implement optional rules specifying which core area to connect ................................ 14
Step 5: Calculate least-cost corridors and mosaic them into a single map ............................... 14
5 Other features, extra hints, and troubleshooting ................................................................... 16
5.1 Saving and re-loading run settings ................................................................................ 16
5.2 Scaling your resistance values ...................................................................................... 16
5.3 Applying Linkage Pathways to large study areas, large core areas, or
large numbers of core areas .......................................................................................... 16
5.4 Manually removing or retaining links........................................................................... 16
5.5 Freeing up disk space .................................................................................................... 16
5.6 Combining Linkage Pathways and Circuitscape to prioritize
connectivity conservation ............................................................................................. 17
5.7 Common problems ........................................................................................................ 17
5.8 Recovering if ArcGIS applications crash in Step 3 ...................................................... 17
5.9 Helpful utilities and accessing additional options ........................................................ 18
5.10 Upgrading ..................................................................................................................... 18
6 Community ........................................................................................................................... 18
7 Literature Cited ..................................................................................................................... 18
8 Linkage Pathways Tutorial ................................................................................................... 19
3
1. Introduction
1.1 Background
The Linkage Pathways Tool of the Linkage Mapper Toolbox is a GIS tool designed to support
regional wildlife habitat connectivity analyses. It consists of several Python scripts, packaged as
an ArcGIS tool, that automate the mapping of wildlife habitat corridors.
Linkage Pathways uses vector maps of core habitat areas and raster maps of resistance to
movement to identify and map least-cost linkages between core areas. Each cell in a resistance
map is attributed with a value reflecting the energetic cost, difficulty, or mortality risk of moving
across that cell. Resistance values are typically determined by cell characteristics, such as land
cover or housing density, combined with species-specific landscape resistance models. As
animals move away from specific core areas, cost-weighted distance analyses produce maps of
total movement resistance accumulated.
The scripts use ArcGIS and Python functions to identify adjacent (neighboring) core areas and
create maps of least-cost corridors between them. The scripts then normalize and mosaic the
individual corridor maps to create a single composite corridor map. The result shows the relative
value of each grid cell in providing connectivity between core areas, allowing users to identify
which routes encounter more or fewer features that facilitate or impede movement between core
areas.
We developed these scripts to support the 2010 Washington Wildlife Habitat Connectivity
Working Group (WHCWG) statewide connectivity analysis, and public them public for use in
other wildlife connectivity assessments. More details on the models and algorithms implemented
by Linkage Pathways can be found in Chapter 2 and Appendix D of WHCWG (2010).
Enhanced Modules–The toolbox now includes newly developed tools to map pinch-points
within corridors (using Circuitscape) , map core areas and corridors with high network centrality
(i.e. those that are most important for keeping a network connected), map barriers (some of
which may offer restoration opportunities), the relative priority among all the linkages on a
landscape, and map corridors that follow climatic gradients to facilitate species range shifts in
response to climate change. Please see the Pinchpoint Mapper, Centrality Mapper, Barrier
Mapper, Linkage Priority, and Climate Linkage Mapper user guides included with the
Linkage Mapper download.
1.2 Before you begin– a note about connectivity modeling and software
limitations
Linkage Pathways was developed to automate some of the arduous and time-consuming steps of
connectivity modeling. However, even with tools like this one, connectivity modeling involves a
great deal of research, data compilation, GIS analyses, and careful interpretation of results.
Defining core areas, parameterizing resistance models, and other modeling decisions you will
need to make are not trivial. Before diving in, we strongly recommend that users thoroughly
familiarize themselves with the process and challenges of connectivity modeling by consulting
published resources. Good places to start include an overview of habitat and corridor modeling
on the Corridor Designer website (http://corridordesign.org/designing_corridors), WHCWG
(2010), Beier et al. (2011), and references listed within. See Sawyer et al. (2011) for a critique of
current corridor modeling practices.
4
You can see WHCWG (2010) for the kind of datasets for which Linkage Pathways was
developed and tested. You may encounter bugs or limitations applying it different datasets,
especially study areas with large numbers of grid cells, large numbers of core areas, or core areas
with highly complex shape.
2 Installation
1) Make sure you have the required GIS and Python installations
Linkage mapper requires ArcGIS Desktop (10.3 or greater) or ArcGIS Pro, with ArcGIS
Spatial Analyst. You will also need Python and NumPy (Numerical Python), which are
automatically installed by ArcGIS.
2) Install Linkage Mapper
Download Linkage Mapper from https://circuitscape.org/linkagemapper.
Open the linkagemapper.zip archive and place the contents in a folder that has no spaces or
special characters in its path (e.g. C:\LinkageMapper).
3) Install the Conefor Inputs Tool for ArcGIS (optional for users with ArcGIS Desktop
Advanced or ArcGIS Pro)
Download Conefor inputs from: http://jennessent.com/arcgis/conefor_inputs.htm. Once you’ve
downloaded the tool, follow the instructions in the Conefor Inputs user guide. From there, you’ll
need to activate the Conefor toolbar in ArcMap: View>>Toolbars>>Conefor. The toolbar should
look like this:
4) Verify your installation
There are multiple ways to access the Linkage Mapper toolbox in ArcGIS. The simplest method
is to browse to the installation directory via a catalog folder connection and double clicking the
toolbox. For other methods see the product help.
You can test the code by running the tutorial at the end of this document.
5
3 Using Linkage Pathways
3.1 Input data requirements
Inputs to Linkage Pathways include 1) a core area polygon GIS file, 2) a resistance raster GIS
file, and, depending on your ArcGIS software or license, 3) a text file specifying Euclidean
(straight-line, edge-to-edge) distances between core area polygons. The core area polygon GIS
file can be either an ESRI shapefile or ESRI geodatabase feature class. The file must have an
attribute specifying core area IDs consisting of positive integers < 9999 that identify unique core
areas. The resistance raster GIS file should include resistances represented by positive numbers
(integers or floating point) only. We recommend resistances scaled so that values of 1 represent
ideal habitat (WHCWG 2010) and increase to at least 100 for barriers (Beier et al. 2011).
Please ensure that your resistance and core area maps are in the same projection.
Linkage Pathways has not been tested with data in different coordinate systems. We
strongly suggest that map units be in meters.
The text file with Euclidean distances between cores can be generated by the Conefor Inputs tool
using the core area file as input (see next section). It can also be automatically generated by
Linkage Pathways if you have ArcGIS Desktop Advanced or ArcGIS Pro.
3.2 Prepping your data and work spaces
Before you start, you’ll need to set up your project directory and, if necessary, create a Euclidean
distances file using your core area polygon data and the Conefor Inputs Tool.
1) Create a project directory
This is where intermediate and output files will be written. This should be a shallow and short
directory (something like C:\ANBO), ideally on a local drive to speed processing. The name of
the directory will also be used as a prefix for final output files (e.g. ANBO_LCPs). There should
be no spaces or special characters anywhere in the directory path.
Note: running Linkage Pathways with input data or project directories on a shared drive
can slow things down drastically, and can cause errors with some ArcGIS routines. It’s
best to use a local drive (and shallow directory) if you can.
You should create unique project directories for each project/scenario you run, to avoid
confusing intermediate data from different analyses.
Several subdirectories will be created in your project directory, including an output directory
with final products. Data are passed between computational steps in the datapass directory. The
scripts also create vector line maps with corridor statistics (stored in the datapass directory
between steps and the link_maps geodatabase in the output directory when the program
completes), as well as raster corridor maps (stored in the corridors geodatabase). Step-by-step
versions of link maps are moved to run_history directory after completion. This directory also
has a log directory where run messages are stored.
2) If you don’t have an Advanced ArcGIS Desktop license or ArcGIS Pro, calculate
Euclidean (straight-line) distances between core areas using the Conefor Inputs Tool.
The Conefor Inputs Tool measures minimum Euclidean distances between core area polygons.
We use this tool solely to generate a text table of core area pairs and distances between them. If
you have another way to provide a table of distances in the same format (see the demo data
provided in the tutorial), you may do that instead.
2302_79748036
zhaoshanshan168
weixin_43318444
yangyin1998
weixin_52224365
2401_84464170
qq_44870829
weixin_62918638