Download the Tutorial

More documents

Recommendations

Info

In addition to adding the target name and ID fields, you may want to make sure that alltargets to be used in the Marxan analysis have been properly screened by experts, andstratified if necessary. For example, stratification is needed if the user wants to assigndifferent goals to the same target class that is spread across different geography settings(e.g. political boundaries, elevations or geologic zones). These stratified targets musthave both a unique name and ID defined. At a minimum, the targets should have theconservation goals defined. Remember, you can use either the GOAL field to define thegoals in specific units (number of occurrences, length, or area) or you can use the PROPfield to set up proportions (percentages). If you use the PROP field, Marxan will calculatethe appropriate target amount based on the proportion specified using a block definitionfile. If GOAL and PROP are both set, then the PROP variable will take precedence andthe GOAL variable will be ignored in the block definition. Also note that the proportionis based on the total amount defined in the puvspr.dat file. Before moving on to the nextstep, you are also going to need your planning units (with unique IDs), the optional statuslayer (e.g. protected areas) if using a status flag for locking in areas, and a method forextracting the optional cost parameter (e.g. ERS model).Once you click on Marxan Target Prep, a dialogbox appears that asks you to select the TargetLayer to Prepare and corresponding TargetName and ID Fields. You must also specify anoutput feature class (e.g. shapefile). A newfeature class will be created so make sure yougive it a descriptive name and have it writtenout to your Marxan working directory. Whenyou are ready, click OK and the new feature class will be created containing all theadditional fields and a new dialog box will appear, listing each unique target on the leftside and the fields to be populated along the top. The user can now enter the values ofeach field using the table previously prepared. Each field has the default value alreadyassigned but these num bers can be change d accordi ng to the conservation scenario thathas been set up in the data prep table. If you h ave many targ ets that need to be assignedth e same value, you can use the “Fill Down First Row” to automate the calculation of thefields using whatever values you enter i n the first row. These values w ill be duplicatedtoall other rows.When you are finished entering in all the values, recheck the numbers and press OK.Now add the new feature class to the map view and open the attribute table in order tomake sure that the fields have been created and they have been populated with the correctTNC Protected Area Tools (PAT) Version 3.0The Nature Conservancy, August 200960
values. These values will be used in generate the input files that Marxan will use. Youmay notice that additional fields TNAME and TID were created. These are created forconsistent naming conventions when using the Marxan Input Generator, which you arenow ready to start in order to create the input files that Marxan will use.3.2.3 Marxan Input Generator (MIG)Now that the target layers have the required fields andcorresponding values assigned, you are ready to usethe Marxan Input Generator (MIG) to create the inputfiles that Marxan will use. Make sure the followingdata layers are in your map view’s table of contentsbefore proceeding with MIG (both the status and costlayers are optional for running Marxan):1. Planning Units - a polygon feature (e.g.hexagons) with unique ID assigned.2. Target Layers – these must be previously runthrough the Target Prep tool or have allrequired fields with user-defined values. Targets must also be dissolved so there isone record per unique target class (Target Prep does this for you). If they are notdissolved, you will have repeating targets listed in the spec.dat and block.dat files.3. Status Layer - this is an optional layer but needed if you plan on using a protectedarea layer or other special interest areas to “lock in” planning units. The user alsohas the option of locking in planning units by specifying a pre-assigned planningunit field value (0, 1, 2, 3) that is extracted and written to the pu.dat file.4. Cost Layer – also an optional layer but needed if you are using planning unit costvalues in your Marxan analysis. For defining cost, the user has the followingoptions to choose from: a) choosing a grid (e.g. ERS model) whose planning unitmean value will be extracted and written to the pu.dat file; b) selecting a predefinedcost field that already exists in the planning unit layer; c) using the area ofthe planning unit as cost; or d) typing in a flat cost that will be assigned to everyplanning unit.Before executing MIG, remember that all input layers must be in the same projection andhave the projection defined. You must also make sure you have an ArcGIS – ArcInfoLevel license with ArcInfo Workstation installed. “ArcMap – ArcInfo” should appear inthe title bar of your ArcGIS program. Also, check your ArcGIS Start Up menu to see ifArcInfo Workstation is listed, which indicates it has been installed. The Spatial Analystextension must also be turned on (Tools > Extensions). Once you verify theserequirements, you are now ready to launch MIG.For this exercise, we will use the planning units (tydixton_planning_units.shp), all thetarget input files (target_point_species.shp, target_line_habitats.shp, target_polygon_habitat.shp), the protected areas (tydixton_protected_areas.shp), and the sample ERSmodel grid (tydixton_ers). When the MIG dialog box appears, you will be prompted toTNC Protected Area Tools (PAT) Version 3.0The Nature Conservancy, August 200961
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: An example of what an attribute tab
Page 63 and 64: Occurrence (OCC), Minimum Clump (CL
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?