Download the Tutorial

More documents

Recommendations

Info

enter in several fields and choose between many options that tell the program where toextract the values that it will use to create the input text files for Marxan.Each of the items in the Marxan Input Generator menu will now be explained:Planning Unit:Planning ID Field:Target Inputs:Create Bound File:Specify the planning unit feature class (polygon).Specify the field that contains the unique ID for eachplanning unit.Choose all the target layers (points, lines, or polygons) thatwill be used to create the Marxan input files. Click on thelayer to select it and click again to unselect. All layers inthe current map view will appear here. You cannot uselayers with the same name.Click this box is you would like to create a boundary file(bound.dat). You will need this file if you are going tospecify a boundary length modifier (BLM) parameter inyour Marxan runs.Create Block Definition File: Click this box if you would like to create a BlockDefinition file (block.dat). If choosing this option, you needto have the following fields assigned in your target files:Type (TYPE), Species Penalty Factor (SPF), TargetTNC Protected Area Tools (PAT) Version 3.0The Nature Conservancy, August 200962
Occurrence (OCC), Minimum Clump (CLUMP),Separation Number (SEPNUM), Separation Distance(SEPDIS), and Proportion (PROP).Area/Length Conversions:Status OptionsThe default units are specified in hectares (area) andkilometers (length). If using the area of the planning unit ascost, the cost will be reported in hectares. You should onlychange the default numbers if you are using units other thanhectares (10000 sq m) for polygons and kilometers (1000m) for length (e.g. feet). The user should also make surethat the specified goal units are the same as thecalculated units.Status is optional but needed if you plan on using aprotected area layer or other special interest areas to “lockin” planning units. Click the “Use Layer” option forspecifying a protected area polygon feature class (or specialinterest areas). Click the “Use PU Field” is you havealready assigned a status field value (0, 1, 2, 3) in yourplanning unit file.If you are using a layer to calculate the status values,choose the layer (e.g. tydixton_protected_areas.shp) in thedrop-down menu. If you are using the PU field option,choose the correct field in the drop-down menu.Status Value: If you are using a layer to calculate thestatus value, choose the status value you want assigned inthe drop-down menu. For locking in planning units, thedefault and most common status value used is 2. The statusvalues are:0 The planning unit is not guaranteed to be in theinitial or ‘seed’ reserve (or portfolio).1 The planning unit will be included in the ‘seed’reserve or the initial reserve.2 The planning unit is fixed (or locked) in the reserve.3 The planning unit is fixed outside (or locked out) ofthe reserve.Status Overlap Threshold: Use this field to indicate theoverlap threshold you would like to use for the intersectionof the status layer with your planning unit layer. Thisthreshold is used to indicate whether or not a planning unitwill be chosen and assigned the specified status value. Thedefault is set to 50%, meaning if the status layer overlaps aplanning unit by at least 50%, it will be flagged with theTNC Protected Area Tools (PAT) Version 3.0The Nature Conservancy, August 200963
Page 1 and 2:
Protected Area Tools (PAT)TMfor Arc
Page 3 and 4:
AcknowledgementsThe idea for the de
Page 5 and 6:
Mandatory Requirements Needed to Ru
Page 7 and 8:
Installing the Protected Area Tools
Page 9 and 10:
The majority of the work that goes
Page 11 and 12: data to spatially represent the spe
Page 13 and 14: 2003, Araújo et al. 2002). In some
Page 15 and 16: 1.1 Setting up the ERS TableSuccess
Page 17 and 18: 1.1.1 Overlay FunctionAnother item
Page 19 and 20: features have been added to the map
Page 21 and 22: the output will automatically defau
Page 23 and 24: Once you click OK in the previous m
Page 25 and 26: unit or feature (i.e. polygon) must
Page 27 and 28: higher elevations and ridges moving
Page 29 and 30: 1.3.4.2 Marine ERS ModelsDeveloping
Page 31 and 32: MODULE 2. Relative Biodiversity Ind
Page 33 and 34: Normalized relative biodiversity in
Page 35 and 36: EXERCISE 2. Calculating the Relativ
Page 37 and 38: the targets (polygons with lots of
Page 39 and 40: Once this step is performed, you ca
Page 41 and 42: This selection routine will choose
Page 43 and 44: 3.0 The MARXAN AlgorithmOne of the
Page 45 and 46: 6. All input features must have the
Page 47 and 48: grid of squares or lattice of hexag
Page 49 and 50: • To make "area" and "length" com
Page 51 and 52: Sug gested steps for preparing inpu
Page 53 and 54: 2. Planning Unit File (pu.dat)This
Page 55 and 56: ‘id2’ are set but no value for
Page 57 and 58: conservation target files are alrea
Page 59 and 60: An example of what an attribute tab
Page 61: values. These values will be used i
Page 65 and 66: 3.2.4 Combining Marxan Input FilesI
Page 67 and 68: 2. Click onto the Run Options tab p
Page 69 and 70: This is the folder where the output
Page 71 and 72: 3.4 Joining and Displaying Marxan O
Page 73 and 74: Figure 12. Results of joining the t
Page 75: McPherson, M, S. Schill, G. Raber,
show all

Download the Tutorial

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?