Layers:

Layer: Active (0)

Name: Active

Display Field: PERMIT

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: This feature class shows the general point location of Land Quality Division (LQD) mine permits. The point locations of regular permits (PTs), small mining permits (SPs), limited mining operations (LMOs), and research and development licennse locations are displayed. Currently, the feature class is being updated approximately quarterly as the personnel are able to update for the thier district. The data are being used in the LQD active mine permit web map (http://159.238.120.99/lqd_permit_public/index.html).

Service Item Id: 5b97a056d1054e7c90004a8f46201f3e

Copyright Text: This feature class was created by Chad Kopplin the WDEQ GIS Manager and is maintained by Matt Dillon, Monte Buchanan, David Schellinger, and Matt Kunze.

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8249.890053120675
YMin: 4539114.133398897
XMax: 579026.0497805829
YMax: 4999610.76478719
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: PERMIT_STA
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: Active
  Label: Active
  Description: N/A
  Symbol:
  
Transparency: 0
Labeling Info:
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: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• OBJECTID_1 ( type: esriFieldTypeOID, alias: OBJECTID_1 )
• OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 )
• TERM_DATE ( type: esriFieldTypeDate, alias: TERM_DATE, length: 8 )
• FORF_DATE ( type: esriFieldTypeDate, alias: FORF_DATE, length: 8 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: County (1)

Name: County

Display Field: DISTRICT

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: This feature class shows the general point location of gravel pit permits held by County governments in Wyoming. The feature class is updated periodically as personnel are able to update for the thier district. The data are being used in the LQD active mine permit web map (http://159.238.120.99/lqd_permit_public/index.html).

Service Item Id: 5b97a056d1054e7c90004a8f46201f3e

Copyright Text:

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -7094.6301635595155
YMin: 4541106.366408049
XMax: 575852.0043566113
YMax: 4999518.18192072
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: PIT_STATUS
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: Active
  Label: Active
  Description: N/A
  Symbol:
  
• Value: Inactive
  Label: Inactive
  Description: N/A
  Symbol:
  
• Value: Reclaimed
  Label: Reclaimed
  Description: N/A
  Symbol:
  
Transparency: 0
Labeling Info:
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: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• DISTURBED_ ( type: esriFieldTypeDouble, alias: DISTURBED_ )
• OBJECTID_1 ( type: esriFieldTypeOID, alias: OBJECTID_1 )
• OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
• DISTRICT ( type: esriFieldTypeString, alias: DISTRICT, length: 8 , Coded Values: [1: District 1: Cheyenne] , [2: District 2: Lander] , [3: District 3: Sheridan] )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• COUNTY ( type: esriFieldTypeString, alias: COUNTY, length: 20 , Coded Values: [ALBANY: Albany] , [JOHNSON: Johnson] , [BIG HORN: Big Horn] , ...20 more... )
• MINE ( type: esriFieldTypeString, alias: MINE, length: 50 )
• MINERAL ( type: esriFieldTypeString, alias: MINERAL, length: 20 , Coded Values: [AG: Agate] , [BA: Ballast] , [BE: Bentonite] , ...37 more... )
• APPROVAL_D ( type: esriFieldTypeDate, alias: APPROVAL_D, length: 8 )
• COMMENTS ( type: esriFieldTypeString, alias: COMMENTS, length: 150 )
• 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... )
• COMPANY ( type: esriFieldTypeString, alias: COMPANY, length: 50 )
• PERMIT_TYP ( type: esriFieldTypeString, alias: PERMIT_TYP, length: 20 )
• PERMIT_STA ( type: esriFieldTypeString, alias: PERMIT_STA, length: 20 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PIT_STATUS ( type: esriFieldTypeString, alias: PIT_STATUS, length: 50 )
• 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 )

Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE (2)

Sub Layers:
• BOUNDARY OUTLINE
• Coal Permit
• Bentonite Permit
• Uranium Permit
• Trona Permit
• Regular Permit - Other Minerals
• Small Mine Permit
• Research and Development License
Name: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Display Field:

Type: Group Layer

Geometry Type: null

Description:

Service Item Id: 5b97a056d1054e7c90004a8f46201f3e

Copyright Text:

Default Visibility: true

MaxRecordCount: 0

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: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
N/A
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


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Type ID Field: null

Fields: None

Layer: BOUNDARY OUTLINE (3)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: BOUNDARY OUTLINE

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. Coal permit boundaries for all LQD Districts are current as of July 22, 2020. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of July 22, 2020. Non-coal permit boundaries for LQD District 2 are current as of May 8, 2020. 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. Coal permit boundaries for all LQD Districts are current as of July 22, 2020. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of July 22, 2020. Non-coal permit boundaries for LQD District 2 are current as of May 8, 2020. 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: Coal Permit (4)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: Coal Permit

Display Field: PERMIT_STA

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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 are 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: MINERAL
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
Style: esriSFSSolid
Color: [130, 130, 130, 102]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 102]
Width: 1
Default Label: Coal Permit

Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: Bentonite Permit (5)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: Bentonite Permit

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. Coal permit boundaries for all LQD Districts are current as of July 22, 2020. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of July 22, 2020. Non-coal permit boundaries for LQD District 2 are current as of May 8, 2020. 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. Coal permit boundaries for all LQD Districts are current as of July 22, 2020. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of July 22, 2020. Non-coal permit boundaries for LQD District 2 are current as of May 8, 2020. 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 255, 197, 255]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 0]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: Uranium Permit (6)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: Uranium Permit

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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 are 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: MINERAL
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
Style: esriSFSSolid
Color: [255, 255, 0, 102]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 102]
Width: 1
Default Label: Uranium Permit

Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: Trona Permit (7)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: Trona Permit

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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 are 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: MINERAL
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
Style: esriSFSSolid
Color: [255, 85, 0, 102]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 102]
Width: 1
Default Label: Trona Permit

Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: Regular Permit - Other Minerals (8)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: Regular Permit - Other Minerals

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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 are 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: PERMIT_TYP
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
Style: esriSFSSolid
Color: [0, 197, 255, 102]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 102]
Width: 1
Default Label: Regular Permit - Other Minerals

Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: Small Mine Permit (9)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: Small Mine Permit

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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 are 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: PERMIT_TYP
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
Style: esriSFSSolid
Color: [76, 230, 0, 102]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 102]
Width: 1
Default Label: Small Mine Permit

Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )

Layer: Research and Development License (10)

Parent Layer: COAL AND NON-COAL BOUNDARIES -MINUS BENTONITE

Name: Research and Development License

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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 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. Coal permit boundaries for all LQD Districts are current as of September 10, 2019. Non-coal permit boundaries for LQD Districts 1 and 3 are current as of September 10, 2019. Non-coal permit boundaries for LQD District 2 are 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: 5b97a056d1054e7c90004a8f46201f3e

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

Default Visibility: true

MaxRecordCount: 1000

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

Supports Datum Transformation: true

Extent:
XMin: -8432.447719020594
YMin: 4539100.129649114
XMax: 579408.0420913557
YMax: 5000797.091245532
Spatial Reference: 26913  (26913)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: PERMIT_TYP
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
Style: esriSFSSolid
Color: [230, 0, 169, 102]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 102]
Width: 1
Default Label: Research and Development License

Transparency: 0
Labeling Info:
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:
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LONG ( type: esriFieldTypeDouble, alias: LONG )
• APPROVED_A ( type: esriFieldTypeDouble, alias: APPROVED_A )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• SHAPE_STAr ( type: esriFieldTypeDouble, alias: SHAPE_STAr )
• SHAPE_STLe ( type: esriFieldTypeDouble, alias: SHAPE_STLe )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PERMIT ( type: esriFieldTypeString, alias: PERMIT, length: 10 )
• 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... )
• 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 )
• 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 ( type: esriFieldTypeGeometry, alias: Shape )
• 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 )