gmu

Frequently-asked questions:

What does this data set describe?
Title:
gmu

Abstract:
24k version of Idaho Fish & Game's (IDFG) Game Management Units (GMUs). This file was produced by IDFG from the GMU legal descriptions available in the back of the published regulations. The following layers were used in this order to define new boundaries: 1. State Outline, IDFG's state.shp, a modified version of the Inside Idaho coverage with streams_measured (100k) used for improved hydrography boundaries. NOTE: This boundary file used to clip the 24K GMUs is NOT 24k but 100k in resolution, at time of publishing no official 24k state boundary was available. 2. County Boundaries from DRG's or where coincident with streams from streams, divides from IDWR Prelim Divides or digitized from DRGs 3. Roads a. ITD Roads, itd.shp b. National Forest Roads: Boise, Salmon/Challis, Clearwater, Nez Perce c. BLM Roads d. Ada County Roads e. USGS DLG Roads (using GDT and TIGER to determine road names) f. GDT Roads - new construction not represented in other files only g. Digitized from DOQ where not available in any layer (< 5 cases) 4. Hydrography based on National Hydrography Dataset or digitized from DRGs Note: In all cases where islands are included/excluded from a Unit the appropriate shoreline was used to represent the boundary rather than stream centerline. In case of CJ Strike, the body of water representing the Snake River was used, portion of reservoir attributed to the Bruneau River was excluded. 5. Divides from IDWR Preliminary New 24k HUC file or digitized from DRGs 6. Utility Lines and Fences digitized from DRGs/DOQs 7. Physical Features such as peaks, passes, rocks and the like from GNIS/DRGs 8. National Wildlife Refuge Boundaries from the IDFG Conservation Data Center (CDC)

  1. How should this data set be cited?

    Idaho Department of Fish and Game, 8/8/2007, gmu: Idaho Department of Fish and Game, Boise, ID, USA.

    Online links:
  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -117.530976
    East: -110.656206
    North: 49.039239
    South: 41.945913

  3. What does it look like?


  4. Does the data set describe conditions during a particular time period?

    Beginning date: 19910701
    Ending date: 20080630
    Currentness reference:
    Data Valid

  5. What is the general form of this data set?

    Geospatial data presentation form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • G-polygon(100)
      • Label point(101)
      • GT-polygon composed of chains(100)
      • Point(4)
      • Composite object(30)

    2. What coordinate system is used to represent geographic features?

      The map projection used is Transverse Mercator.

      Projection parameters:
      Transverse Mercator
      Scale factor at central meridian: 0.999600
      Longitude of central meridian: -114.000000
      Latitude of projection origin: 42.000000
      False easting: 2500000.000000
      False northing: 1200000.000000

      Planar coordinates are encoded using coordinate pair.
      Abscissae (x-coordinates) are specified to the nearest 0.002048.
      Ordinates (y-coordinates) are specified to the nearest 0.002048.
      Planar coordinates are specified in meters.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

  7. How does the data set describe geographic features?

    gmu
    FID
    Internal feature number.

    (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry.

    (Source: ESRI)

    Coordinates defining the features.

    OBJECTID


    NAME


    ID


    SHAPE_area
    Area of feature in internal units squared.

    (Source: ESRI)

    Positive real numbers that are automatically generated.

    SHAPE_len


    gmu.pat
    FID
    Internal feature number.

    (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry.

    (Source: ESRI)

    Coordinates defining the features.

    AREA
    Area of feature in internal units squared.

    (Source: ESRI)

    Positive real numbers that are automatically generated.

    PERIMETER
    Perimeter of feature in internal units.

    (Source: ESRI)

    Positive real numbers that are automatically generated.

    GMU#
    Internal feature number.

    (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    GMU-ID
    User-defined feature number.

    (Source: ESRI)

    UNITID
    Game Management Unit Identifier


    UNIT
    GMU Name eg. 8A, 9, 10


    ZONEID
    Elk Zone Identifier


    AREAID
    Elk Zone Name, eg. Bannock, McCall, Lemhi


    RANK
    Management Area Identifier


    ACRES
    Management Area Rank


    HECTARES
    Acres of GMU


    ZONE_NAME
    Hectares of GMU


    REGIONID
    Not the Official Region boundary, Region used in reporting some harvest and population statistics only. Region 4,5 & 6 differ in official version. Units 69 and adjacent Units are in multiple Units.


    gmu.patelkzones
    FID
    Internal feature number.

    (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry.

    (Source: ESRI)

    Coordinates defining the features.

    AREA
    Area of feature in internal units squared.

    (Source: ESRI)

    Positive real numbers that are automatically generated.

    PERIMETER
    Perimeter of feature in internal units.

    (Source: ESRI)

    Positive real numbers that are automatically generated.

    ELKZONES#
    Internal feature number.

    (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    ELKZONES-ID
    User-defined feature number.

    (Source: ESRI)

    ZONEID


Back to Top

Who produced the data set?
  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

    • Idaho Department of Fish and Game

  2. Who also contributed to the data set?

    See Abstract for a list of data sets used in making this layer.

  3. To whom should users address questions about the data?

    Brent Thomas
    Idaho Department of Fish and Game, Department of Wildlife
    GIS Analyst, Sr.
    600 South Walnut, P.O. Box 25
    Boise, ID 83707-0025
    USA

    (208) 334-3700 (voice)
    (208) 334-2148 (FAX)
    idfginfo@idfg.idaho.gov
    Hours of Service: 8 am - 5 pm M-F
Back to Top

Why was the data set created?
To represent the boundaries of Game Management Units used in managing and hunting Big Game.

Back to Top

How was the data set created?
  1. Where did the data come from?

  2. What changes have been made?

    (source 1 of 7)
    Dataset copied.

    Data sources used in this process:
    • d:\projects\biggame\shapes\gmua2

    (source 2 of 7)
    Dataset copied.

    Data sources used in this process:
    • d:\projects\biggame\shapes\gmu24k

    (source 3 of 7)
    Dataset copied.

    (source 4 of 7)
    Metadata imported.

    Data sources used in this process:
    • U:\Shapes\gmu.shp.xml

    (source 5 of 7)
    Dataset copied.

    (source 6 of 7)
    Metadata imported.

    Data sources used in this process:
    • U:\Shapes\gmu.shp.xml

    (source 7 of 7)
    Metadata imported.

    Data sources used in this process:
    • K:\IFWIS\SDE_Layers\Game Management Units.lyr.xml

Back to Top

How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

  5. How consistent are the relationships among the observations, including topology?

Back to Top

How can someone get a copy of the data set?
Are there legal restrictions on access or use of the data?

Access constraints: This file is freely available in the public domain.
Use constraints:
Refer to the boundaries published in the current IDFG Big Game or Moose, Sheep and Goat Guides for the official GMU boundaries before hunting. This file is a best representation only.

Distributor 1 of 1

  1. Who distributes the data set?

    Brent Thomas
    Idaho Fish and Game
    GIS Analyst
    600 South Walnut, P.O. Box 25
    Boise, ID 83707-0025
    USA

    (208) 334-3700 (voice)
    idfginfo@idfg.state.id.us
    Hours of Service: 8am - 5pm M-F

  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

Back to Top

Who wrote the metadata?
Dates:
Last modified: 20070807

Metadata author:
Brent Thomas
Idaho Department of Fish and Game
GIS Analyst
600 S Walnut
PO Box 25
Boise, Idaho 83707
USA

(208) 334-3700 (voice)
(208) 334-2148 (FAX)
idfginfo@idfg.state.id.us
Hours of Service: 8 am - 5 pm M-F

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata(FGDC-STD-001-1998)

Metadata extensions used:
  • http://www.esri.com/metadata/esriprof80.html

    • Back to Top