{
  "fetched_at": "2026-10-19T19:12:24Z",
  "source_url": "https://www.kaggle.com/competitions/forest-cover-type-prediction/data",
  "pages": [
    {
      "name": "data-description",
      "content": "<p>The study area includes four wilderness areas located in the Roosevelt National Forest of northern Colorado. Each observation is a 30m x 30m patch. You are asked to predict an integer classification for the forest cover type. The seven types are:</p>\r\n<p>1 - Spruce/Fir<br /> 2 - Lodgepole Pine<br /> 3 - Ponderosa Pine<br /> 4 - Cottonwood/Willow<br /> 5 - Aspen<br /> 6 - Douglas-fir<br /> 7 - Krummholz</p>\r\n<p>The training set (15120 observations) contains both features and the Cover_Type. The test set contains only the features. You must predict the Cover_Type for every row in the test set (565892 observations).</p>\r\n<h2>Data Fields</h2>\r\n<p><strong>Elevation</strong> - Elevation in meters<br /><strong>Aspect</strong> - Aspect in degrees azimuth<br /><strong>Slope</strong> - Slope in degrees<br /><strong>Horizontal_Distance_To_Hydrology</strong> - Horz Dist to nearest surface water features<br /><strong>Vertical_Distance_To_Hydrology</strong> - Vert Dist to nearest surface water features<br /><strong>Horizontal_Distance_To_Roadways</strong> - Horz Dist to nearest roadway<br /><strong>Hillshade_9am</strong> (0 to 255 index) - Hillshade index at 9am, summer solstice<br /><strong>Hillshade_Noon</strong> (0 to 255 index) - Hillshade index at noon, summer solstice<br /><strong>Hillshade_3pm</strong> (0 to 255 index) - Hillshade index at 3pm, summer solstice<br /><strong>Horizontal_Distance_To_Fire_Points</strong> - Horz Dist to nearest wildfire ignition points<br /><strong>Wilderness_Area</strong> (4 binary columns, 0 = absence or 1 = presence) - Wilderness area designation<br /><strong>Soil_Type</strong> (40 binary columns, 0 = absence or 1 = presence) - Soil Type designation<br /><strong>Cover_Type</strong> (7 types, integers 1 to 7) - Forest Cover Type designation</p>\r\n<p>The wilderness areas are:</p>\r\n<p>1 - Rawah Wilderness Area<br /> 2 - Neota Wilderness Area<br /> 3 - Comanche Peak Wilderness Area<br /> 4 - Cache la Poudre Wilderness Area</p>\r\n<p>The soil types are:</p>\r\n<p>1 Cathedral family - Rock outcrop complex, extremely stony.<br /> 2 Vanet - Ratake families complex, very stony.<br /> 3 Haploborolis - Rock outcrop complex, rubbly.<br /> 4 Ratake family - Rock outcrop complex, rubbly.<br /> 5 Vanet family - Rock outcrop complex complex, rubbly.<br /> 6 Vanet - Wetmore families - Rock outcrop complex, stony.<br /> 7 Gothic family.<br /> 8 Supervisor - Limber families complex.<br /> 9 Troutville family, very stony.<br /> 10 Bullwark - Catamount families - Rock outcrop complex, rubbly.<br /> 11 Bullwark - Catamount families - Rock land complex, rubbly.<br /> 12 Legault family - Rock land complex, stony.<br /> 13 Catamount family - Rock land - Bullwark family complex, rubbly.<br /> 14 Pachic Argiborolis - Aquolis complex.<br /> 15 unspecified in the USFS Soil and ELU Survey.<br /> 16 Cryaquolis - Cryoborolis complex.<br /> 17 Gateview family - Cryaquolis complex.<br /> 18 Rogert family, very stony.<br /> 19 Typic Cryaquolis - Borohemists complex.<br /> 20 Typic Cryaquepts - Typic Cryaquolls complex.<br /> 21 Typic Cryaquolls - Leighcan family, till substratum complex.<br /> 22 Leighcan family, till substratum, extremely bouldery.<br /> 23 Leighcan family, till substratum - Typic Cryaquolls complex.<br /> 24 Leighcan family, extremely stony.<br /> 25 Leighcan family, warm, extremely stony.<br /> 26 Granile - Catamount families complex, very stony.<br /> 27 Leighcan family, warm - Rock outcrop complex, extremely stony.<br /> 28 Leighcan family - Rock outcrop complex, extremely stony.<br /> 29 Como - Legault families complex, extremely stony.<br /> 30 Como family - Rock land - Legault family complex, extremely stony.<br /> 31 Leighcan - Catamount families complex, extremely stony.<br /> 32 Catamount family - Rock outcrop - Leighcan family complex, extremely stony.<br /> 33 Leighcan - Catamount families - Rock outcrop complex, extremely stony.<br /> 34 Cryorthents - Rock land complex, extremely stony.<br /> 35 Cryumbrepts - Rock outcrop - Cryaquepts complex.<br /> 36 Bross family - Rock land - Cryumbrepts complex, extremely stony.<br /> 37 Rock outcrop - Cryumbrepts - Cryorthents complex, extremely stony.<br /> 38 Leighcan - Moran families - Cryaquolls complex, extremely stony.<br /> 39 Moran family - Cryorthents - Leighcan family complex, extremely stony.<br /> 40 Moran family - Cryorthents - Rock land complex, extremely stony.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "<p><a href=\"https://www.kaggle.com/c/forest-cover-type-prediction/forums/t/13534/get-started-with-kaggle-scripts/72674#post72674\">Get started on this competition with Kaggle Scripts.</a> No data download or local environment needed!</p>\r\n<p><a href=\"http://en.wikipedia.org/wiki/Random_forest\">Random forests?</a> <a href=\"http://en.wikipedia.org/wiki/Cover_tree\">Cover trees?</a> Not so fast, computer nerds. We're talking about the real thing.</p>\r\n<p>In this competition you are asked to predict the forest cover type (the predominant kind of tree cover) from strictly cartographic variables (as opposed to remotely sensed data). The actual forest cover type for a given 30 x 30 meter cell was determined from US Forest Service (USFS) Region 2 Resource Information System data. Independent variables were then derived from data obtained from the US Geological Survey and USFS. The data is in raw form (not scaled) and contains binary columns of data for qualitative independent variables such as wilderness areas and soil type.</p>\r\n<p>This study area includes four wilderness areas located in the Roosevelt National Forest of northern Colorado. These areas represent forests with minimal human-caused disturbances, so that existing forest cover types are more a result of ecological processes rather than forest management practices.</p>\r\n<h2>Acknowledgements</h2>\r\n<p>Kaggle is hosting this competition for the machine learning community to use for fun and practice. This dataset was provided by Jock A. Blackard and Colorado State University. We also thank the UCI machine learning repository for <a href=\"https://archive.ics.uci.edu/ml/datasets/Covertype\">hosting the dataset</a>. If you use the problem in publication, please cite:</p>\r\n<p><em>Bache, K. &amp; Lichman, M. (2013). <a href=\"http://archive.ics.uci.edu/ml\">UCI Machine Learning Repository</a>. Irvine, CA: University of California, School of Information and Computer Science</em></p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<p>Submissions are evaluated on multi-class classification accuracy.</p>\r\n<h2>Submission File</h2>\r\n<p>Your submission file should have the observation Id and a predicted cover type (an integer between 1 and 7, inclusive). The file should contain a header and have the following format:</p>\r\n<pre>Id,Cover_Type<br />15121,1<br />15122,1<br />15123,1<br />...</pre>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "rules",
      "content": "\r\n\t<!-- Begin Base Rules -->\r\n    <h3>One account per participant</h3>\r\n    <p>You cannot sign up to Kaggle from multiple accounts and therefore you cannot submit from multiple accounts.</p>\r\n    <h3>No private sharing outside teams</h3>\r\n    <p>\r\n        Privately sharing code or data outside of teams is not permitted.\r\n        It's okay to share code if made available to all participants on the forums.\r\n    </p>\r\n    <h3>Team Mergers</h3>\r\n    <p>\r\n        Team mergers are allowed and can be performed by the team leader. In order to merge, the combined team must have a total submission count less than or equal to the maximum allowed as of the merge date. The maximum allowed is the number of submissions per day multiplied by the number of days the competition has been running.<br/>\r\n    </p>\r\n\r\n    <h3>Team Limits</h3>\r\n    <p>There is no maximum team size.</p>\r\n    <h3>Submission Limits</h3>\r\n    <p>You may submit a maximum of 5 entries per day.</p>\r\n    <p>You may select up to 2 final submissions for judging.</p>\r\n    <h3>Competition Timeline</h3>\r\n    <p>Start Date: <strong>5/16/2014 6:55 PM UTC</strong></p>\r\n    <p>Merger Deadline: <strong>None</strong></p>\r\n    <p>Entry Deadline: <strong>None</strong></p>\r\n    <p>End Date: <strong>5/11/2015 11:59 PM UTC</strong></p>\r\n\t<!-- End Base Rules -->\r\n<ul>\r\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">Due to the public nature of the data, this competition does not count towards Kaggle ranking points.</span></li>\r\n<li>We ask that you respect the spirit of the competition and do not cheat. You should not submit entries based on test-set answers or train your model on the test set. Hand labeling is also forbidden.</li>\r\n</ul>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}