Name: USACE SPL Compensatory Mitigation (5/2016)

Display Field: Project

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: To compile these data, compensatory mitigation maps from Army Corps permit files were digitized by manually scanning paper copies or using electronic versions. Attribute data were collected and interpreted by Regulatory Division staff by searching Department of the Army (DA) permit files, including mitigation plans and mitigation monitoring reports. Due to variances in mitigation mapping formats and changes in the regulatory program requirements over time, for some cases, some data elements were extrapolated or assumptions were made based on the best available information in the file. Regulatory staff then identified geographic control points on the digitized maps and mitigation polygons were numbered to correspond with submitted attribute metadata. In some cases, applicants provided GIS data that could be incorporated directly into this overall GIS data layer.Following compilation of the data, digitized mitigation maps were submitted to GIS professionals to map by hand (or merge, if submitted in GIS format) within ESRI ArcMap. GoogleEarth was used to geographically locate many of the sites. A geographic basemap was uploaded from ESRI and in most cases ESRI World Imagery WGS 1984 Mercator Auxillary Sphere was used with coordinate system NAD83 (http://www.arcgis.com/home/item.html?id=10df2279f9684e4a9f6a7f08febac2a9). Topography and other physical features were used to visually locate the boundaries of each polygon for accurately placing mitigation sites in geographic space.Following GIS mapping of the mitigation sites by GIS professionals, the sites were individually reviewed for mapping errors, overlapping polygons, or discrepancies, also using basemap ESRI World Imagery WGS 1984 Mercator Auxillary Sphere. In some cases DA permit files were reviewed again to obtain more information about mitigation polygons or attribute data. In addition, ArcMap tools were used to eliminate overlapping polygons, using either Erase/Replace, Integrate, Eliminate, or Manual Adjustment. See Mitigation Quality Assurance Quality Control (QAQC) Procedures.After GIS mitigation maps were completed in ArcGIS, the Operations & Maintenance Business Information Link (OMBIL) Regulatory Module version 2 (ORM2) database was queried to output a report for all the mapped projects. These additional attribute data were then joined to the mitigation map attribute data using a common field (‘DA-number’).Data range: The LAD Regulatory program began compiling mitigation map data for sites in Southern California and Arizona in 2011 for years 2009-2010 resulting in about 114 Permittee Responsible compensatory mitigation maps, resulting in a fairly complete dataset for mitigation permitted across the 2009-2010 time range. In 2012, data was compiled from years 2011-2012, resulting in a near complete dataset. In addition, paper files dating back to the 1990s to about 2006 are sorted annually and any projects appearing to have required compensatory mitigation are set aside and mapped. Therefore not all pre-2009 mitigation sites have been mapped nor do we expect to map all pre-2009 sites.Disclaimer: These mitigation data are not a comprehensive list of all Corps-approved permittee-responsible compensatory mitigation sites for the Los Angeles District. These data are not to be used for official compliance, enforcement, or legal matters. A data point or polygon may represent one or more DA files. A mitigation site may or may not have been implemented, or implemented in full, and may or may not be an active or completed mitigation site. Mitigation success criteria are evaluated based on the permit conditions and on-site inspections and not the maps or map features provided (including the shape, size, acreage, placement, or attribute data). A mitigation site may not be fully representative of the actual mitigation site nor is it a substitute for the areas provided in the DA permit and Corps-approved mitigation plans.

Service Item Id: 77210beccc9a4c48a369b5dbb0eb5689

Copyright Text: Author: U.S. Army Corps of Engineers, Los Angeles District, Regulatory Division, 915 Wilshire Blvd., Los Angeles, California 90017. Point-of-contacts: Daniel P. Swenson (Daniel.P.Swenson@usace.army.mil) 213-452-3414, Bonnie L. Rogers (Bonnie.L.Rogers@usace.army.mil) 213-452-3372. Data-mappers: Various Army Corps of Engineers staff. Software used: ESRI (Environmental Systems Resource Institute) ArcMap 9.3. and 10.1.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.3438447335864007E7
YMin: 3815332.226912057
XMax: -1.2305611108205529E7
YMax: 4210540.531650132
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Unique Value Renderer:
Field 1: Permittee_
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: Enhancement
  Label: Enhancement
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [86, 129, 196, 255]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
• Value: Establishment
  Label: Establishment
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [97, 242, 97, 255]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
• Value: Preservation
  Label: Preservation
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [250, 125, 97, 255]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
• Value: Re-establishment
  Label: Re-establishment
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [235, 98, 245, 255]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
• Value: Rehabilitation
  Label: Rehabilitation
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [116, 138, 85, 255]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: false
Supports Having Clause: false
Supports Count Distinct: false
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: false
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• FID ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Producer ( type: esriFieldTypeString, alias: Producer, length: 254 )
• Area_acres ( type: esriFieldTypeDouble, alias: Area_acres )
• Project ( type: esriFieldTypeString, alias: Project, length: 254 )
• Permittee_ ( type: esriFieldTypeString, alias: Permittee_, length: 254 )
• Long_term_ ( type: esriFieldTypeString, alias: Long_term_, length: 254 )
• Mitigation ( type: esriFieldTypeString, alias: Mitigation, length: 254 )
• Habitat_ty ( type: esriFieldTypeString, alias: Habitat_ty, length: 254 )
• Date_mappe ( type: esriFieldTypeDate, alias: Date_mappe, length: 8 )
• Last_updat ( type: esriFieldTypeDate, alias: Last_updat, length: 8 )
• Overlay ( type: esriFieldTypeString, alias: Overlay, length: 254 )
• DA_NUMBER ( type: esriFieldTypeString, alias: DA_NUMBER, length: 254 )
• da_numbe_1 ( type: esriFieldTypeString, alias: da_numbe_1, length: 254 )
• action_1 ( type: esriFieldTypeString, alias: action_1, length: 254 )
• action_typ ( type: esriFieldTypeString, alias: action_typ, length: 254 )
• pnn ( type: esriFieldTypeString, alias: pnn, length: 254 )
• proj_name ( type: esriFieldTypeString, alias: proj_name, length: 254 )
• permt_auth ( type: esriFieldTypeString, alias: permt_auth, length: 254 )
• bgn_date ( type: esriFieldTypeString, alias: bgn_date, length: 254 )
• end_date ( type: esriFieldTypeString, alias: end_date, length: 254 )
• clos_methd ( type: esriFieldTypeString, alias: clos_methd, length: 254 )
• county ( type: esriFieldTypeString, alias: county, length: 254 )
• huc ( type: esriFieldTypeString, alias: huc, length: 254 )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata