Name: LQD STATEWIDE BOUNDARIES_PT_SP_RD

Display Field: PERMIT

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The dataset was created by the Land Quality Division (LQD) of the Wyoming Department of Environmental Quality (WDEQ). The dataset contains boundaries for all regular mining permits, small mining permits, and research and development licenses regulated by the WDEQ/LQD in Wyoming. All LQD Districts and minerals are represented. The boundaries are current as of June 6, 2018. These data are for display purposes only and do not represent survey grade information. Users are referred to individual mine permits for more detailed information. The WDEQ/LQD makes no warranties as to the validity, and assumes no liability associated with the use or misuse of this information. Most of the permit boundaries were created by the WDEQ/LQD using information in the mine permits, as discussed below. Some permit boundaries for certain uranium and bentonite mines were provided directly from the permittees. The "DATA" field provides a brief description of how the boundary was created or if the boundary was provided directly by a mine operator. The "COMMENTS" field provides further details on how the boundary was created. In some cases the WDEQ/LQD made minor edits to the boundary supplied by the operator, and this is also noted in the "DATA" or "COMMENTS" field.When not supplied by the mine operator, the WDEQ/LQD created the boundaries by two primary methods. First, the legal description information in Appendix C of each permit was used to create the boundary in conjunction with the July 2016 Geographic Coordinate Database (GCDB) (aka Public Land Survey System (PLSS)) data from the Wyoming BLM (https://www.blm.gov/wy/st/en/resources/public_room/cadastral/gcdb.html). In some cases Coordinate Geography (COGO) tool in ArcGIS was used to create boundaries for irregular feature shapes such as roads and other boundary curves. A second method used to create the boundary was by scanning and georeferencing a current map from the mine permit.It should be noted that some users may notice that the permit boundaries do not match exactly with section lines depicted on different versions of the PLSS, such as USGS Digital Raster Graphics (DRG) topographic maps or older versions of the GCDB. The GCDB data used for this project was presumed to be the most up to date and accurate PLSS data available. However, it should be noted that the BLM cautions that the GCDB dataset has no legal significance and cannot be used as a substitute for a legal boundary survey. Further information on GCDB is available from the BLM at: https://www.blm.gov/wy/st/en/resources/public_room/cadastral/gcdb.html. The accuracy of the permit boundaries was checked in several ways. First, the boundaries were visually compared against maps in the permit. Second, the boundaries were checked against the legal description information in Appendix C of the adjudication file for each permit. Finally, the calculated GIS acres for each permit were compared against the approved permit acres for each permit. In some cases where a large discrepancy exists between the calculated and approved acres, this is noted in the COMMENTS field. It is noted that some permit boundaries for bentonite permits showed large discrepancies between calculated and approved acres; these boundaries may be updated in the future as more information and edits are made.Users should note that mine permit boundaries in Wyoming can frequently change. The permit boundaries in this shapefile are considered current as of June 6, 2018. The most up to date information on permit boundaries and acreages can be obtained by checking Appendix C in the adjudication file of each mine permit.

Service Item Id: 35a5e2871bf0494a8e599d096a96bbca

Copyright Text: Wyoming Department of Environmental Quality, Land Quality Division

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 1000000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.23613810769E7
YMin: 5012797.513099998
XMax: -1.15834352575E7
YMax: 5621587.190700002
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 255]
Width: 3
Label: MINE PERMIT BOUNDARY
Description: N/A
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: [PERMIT]
Use Coded Values: true
Symbol:
Color: [0, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: center
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 12
Font Family: Arial
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 250000.0
Max. Scale: 0.0

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• SHP_DATE ( type: esriFieldTypeDate, alias: SHP_DATE, length: 8 )
• DATA ( type: esriFieldTypeString, alias: DATA, length: 5 , Coded Values: [GPS: Data collected via GPS and considered valid] , [OP: Data provided by the operator or company and considered valid] , [DG: Digitized from aerial phtography and considered provisional] , ...4 more... )
• COMMENTS ( type: esriFieldTypeString, alias: COMMENTS, length: 150 )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• COMPANY ( type: esriFieldTypeString, alias: COMPANY, length: 50 )
• MINE ( type: esriFieldTypeString, alias: MINE, length: 50 )
• MINERAL ( type: esriFieldTypeString, alias: MINERAL, length: 20 , Coded Values: [AG: Agate] , [BA: Ballast] , [BE: Bentonite] , ...37 more... )
• COUNTY ( type: esriFieldTypeString, alias: COUNTY, length: 20 , Coded Values: [ALBANY: Albany] , [JOHNSON: Johnson] , [BIG HORN: Big Horn] , ...20 more... )
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• DIST ( type: esriFieldTypeString, alias: DIST, length: 8 , Coded Values: [1: District 1: Cheyenne] , [2: District 2: Lander] , [3: District 3: Sheridan] )
• APPROVAL_D ( type: esriFieldTypeDate, alias: APPROVAL_D, length: 8 )
• PERMIT_TYP ( type: esriFieldTypeString, alias: PERMIT_TYP, length: 50 )
• PERMIT_STA ( type: esriFieldTypeString, alias: PERMIT_STA, length: 20 )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• TERM_DATE ( type: esriFieldTypeDate, alias: TERM_DATE, length: 8 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )

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

  Iteminfo   Thumbnail   Metadata