ArcGIS REST Services Directory Login
Home > services > Open > River_Morphology (MapServer) > River Anthropogenic Modification Index Help | API Reference
JSON

Layer: River Anthropogenic Modification Index (ID: 1)

Name: River Anthropogenic Modification Index

Display Field: restoration_approach

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: The RAMI layer is calculated for all baseline river water bodies. Anthropogenic pressures which were believed to degrade channel form were mapped across all these water bodies. This includes bank protection, culverts, river straightening, bed reinforcement, embankments, weirs and more. This mapping was initially done using remote sensing (e.g. aerial photographs and OS maps) to identify the pressures. All baseline rivers that were identified as being at less than good morphological condition, or in good but close to poor morphological condition due to these modifications were then field surveyed, so that the reliability and resolution in the data was improved. This includes > 7,000 km of river that were walked. River type was also recorded, as the type of the river impacts the degree of impact the anthropogenic pressure will have. The river types include: bedrock, cascade, step-pool, plane-riffle, plane bed, active meandering, wandering, passive meandering and peat. For example, a stretch of bank protection on a bedrock river will have less of an impact on river form and habitat than it would have on an active meandering river, which would naturally be able to move sideways across the floodplain. For every pressure and river type combination, impact ratings were created, to predict the impact that pressure was likely to have on a specific type of river. The impact ratings (see MImAS reference at this end of this section) were then used to calculate the degree of impact (or capacity used) for every 1 km stretch of the baseline river network to create the River Anthropogenic Modification Index (RAMI). Capacity used = Impact rating x pressure footprint 1 km length The pressure footprint was simply the length of that pressure within the 1km length being assessed. This was then divided by the length being assessed (in this case 1 km) to get a measure of the capacity used (i.e. how much impact is the system likely to be undergoing). The resulting number was then used to place reaches into categories based on the extent of modification (Table 1). Table 1: Capacity used score as calculated within the RAMI approach and resulting modification categories. Capacity usedRAMI category< 25%Low modification25.1 – 50%Moderate modification50.1 – 75 %High modification75.1 – 100%Significant modification> 100%*Very significant modificationN/AWetland/unknown river type** * Due to overlapping pressures, in some circumstances more than 100% capacity can be used.** Capacities were not calculated for this type of waterbody.Method to produce the RAMI layer in GISAll the information was extracted from the different GIS layers (morph pressures and river type) and converted into tables in Excel format. The different pressures were split into different parts when the pressure expanded two river types. This helps to work out accurately the MImAS capacity (i.e. apply the correct impact rating to each section of the pressure). The way to control the length and location of pressures and river types was made using river codes (from the SEPA river network) and downstream and upstream distances. The excel file used for tuis purpose is this one: The excel file contains different tabs. The tabs that have used for this project are in blue and named starting with a ‘3’. Tab “3 Water metrics”:To create an internal ID (Internal ID before extracting reaches)Column F: to find the location (reach number) of the downstream distance of every pressure. Reach number are 1, 2, 3, …… each of those correspond to e.g.: reach 1 is the first 1000m reach, reach 12 is 12,000m, etc.Column G: to find the location (reach number) of the upstream distance of every pressure. Reach number are 1, 2, 3, …… each of those correspond to e.g.: reach 1 is the first 1000m reach, reach 12 is 12,000m, etc.Column H: to identify if the pressure is contained in the same reach number.Column I: to identify if the pressure expands several reaches. Columns J and K: for the same pressure works out the lowest reach where the pressure expands. It works out the Mimas capacity in K.Columns L and M: if the pressure expands more than one reach, the reach number and the capacity used is worked out here (M). Columns N and O…. same that before.Etc… Tab “3 Water Metrics 1.1”: Insert the internal ID and Rivercode before each pair: JK, LM, NO, etc, to make it easy to create a table with all those reaches. To create a new Tab where I will paste all the columns with all the new reaches. (3 Water metrics 2)Tab 3 Water metrics 2:I copy all the Pairs: RAMI Reach and capacity used for that RAMI reach I copy all seven pairs and paste them in columns one under the other (i.e. I need a table with the same columns showing reach and capacity for the different reaches)When I copy the columns in b, I also copy the unique internal ID produced in 1. This will help to bring all the information from the tab Water Metrics, later on to Water Metrics 2.Also, I need to create two columns with the DWN and UPS distance of reaches 1000, 2000, 3000, etc. to do linear referencing later. Then I will create a dynamic table to Sum the capacity use in each Reach within each RivCod. This capacity value will be the one that will be useful to allocate the RAMI value. (Tab 3 Water metrics Pivot 3).Tab 3 Water metrics Pivot 3: The dynamic table uses data from Water Metrics 2.The table extracted from this dynamic table will be the one to export to GIS using linear referencing. I used a annex tab to help producing this tab (Tab 3 Annex to pivot 4).The final table to be used in GIS is in tab “3 Extract to GIS 6”.GIS work. I used ArcGIS Pro. Linear referencing tools making use of RivCode and downstream and upstream distances for each 1000 reaches. The shapefile was generated. RAMI_test1.zip (this version, attached below, has not metadata yet).

Service Item Id: d4639908e4e84b3e8c25e6ad4a0cc652

Copyright Text: SEPA Hydromorphology

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata