NCCN Elk LEWI Monitoring Data Package, 2008-2024
Department of the Interior
@usgov.doi_gov_nccn_elk_lewi_monitoring_data_package_2008_2024
Department of the Interior
@usgov.doi_gov_nccn_elk_lewi_monitoring_data_package_2008_2024
This data package contains elk monitoring data collected under the auspices of the North Coast and Cascades Network (NCCN) Inventory and Monitoring Program during 2008-2024 at Lewis and Clark National Historical Park (LEWI).
The monitoring protocol, publications, and all other associated links can be found in the project reference at: NCCN Monitoring Elk Ground (Lewis and Clark National Historical Park), https://irma.nps.gov/DataStore/Reference/Profile/2182083
Monitoring was initiated to track Roosevelt elk seasonal use and visitor viewing opportunities in and around the Fort Clatsop unit of Lewis and Clark National Historical Park (LEWI). The preservation of elk herds that frequent LEWI is central to the park’s purpose, “to preserve … the historic, cultural, scenic, and natural resources associated with the arrival of the Lewis and Clark Expedition in the lower Columbia River area, and … commemorating the culmination and the winter encampment of the Lewis and Clark Expedition in the winter of 1805-1806 …” (Public Law 108-387). Today, elk viewing opportunities in the park and surrounding Clatsop Plains region generate broad appeal with the visiting public. Elk range widely outside of park boundaries where habitat conditions are affected by urbanization, forest management, and agricultural practices, and where populations and behaviors of elk are influenced by hunting patterns, other human disturbance factors, and habitat change. Staff at LEWI have used data generated by elk monitoring to build community partnerships, to highlight regional habitat and land use planning effects on park resources, and to inform regional discussions of policies that may influence the park’s elk population.
The primary monitoring objectives of the protocol are to measure the relative use and proportion of area used by elk during winter in the Fort Clatsop Unit of the park, and the rate at which elk are sighted from roads in and around the Fort Clatsop unit of . Relative use and the proportion of area used by elk are determined from annual elk fecal pellet surveys, wherein pairs of observers visit a systematic array of permanent plots in the fall to clear them of elk fecal pellets, and return to the plots in late winter to count elk fecal pellets that have accumulated during winter. Standardized road surveys are conducted in and near the Fort Clatsop park unit three or four times monthly during alternate months, where two observers drive four routes to record numbers of elk, location, and composition of each group observed. Data from road surveys are used to provide an index of elk viewing opportunities for park visitors along the selected set of routes.
Organization: Department of the Interior
Last updated: 2025-09-14T18:49:29.829664
Tags: astoria, biology, biota, cervid, cervus-elaphus, double-observer, ecological-framework-biological-integrity-focal-species-or-communities-mammals, ecology, elk, habitats, inventory-and-monitoring, lewi, lewis-and-clark-national-historical-park, mammals, monitoring, nccn, north-coast-and-cascades-network, oregon, populations, resource-management, roosevelt-elk, species, surveys, tabular-data, terrestrial-ecosystems, trend, ungulate, vertebrates, warrenton, washington, wildlife
CREATE TABLE nccn_elklewi_driving_surveydata (
"park_code" VARCHAR,
"survey_year" BIGINT,
"month" BIGINT,
"period" VARCHAR,
"survey_date" TIMESTAMP,
"route" VARCHAR,
"survey_completed" VARCHAR,
"temp_c_start" DOUBLE,
"wind_start" DOUBLE,
"wind_desc" VARCHAR,
"sky_start" DOUBLE,
"sky_desc" VARCHAR,
"elk_seen" VARCHAR,
"obs_number" DOUBLE,
"observation_time" VARCHAR,
"coord_source" VARCHAR,
"mile_marker" DOUBLE,
"obs_utme" DOUBLE,
"obs_utmn" DOUBLE,
"azimuth" DOUBLE,
"distance_m" DOUBLE,
"final_utme" DOUBLE,
"final_utmn" DOUBLE,
"habitat" VARCHAR,
"habitat_desc" VARCHAR,
"total_elk" DOUBLE,
"branch_bulls" DOUBLE,
"spike_bulls" DOUBLE,
"total_bulls" DOUBLE,
"antlerless_adults" DOUBLE,
"calves" DOUBLE,
"unknown" DOUBLE,
"duplicate_obs" DOUBLE,
"is_excluded" BIGINT
);
CREATE TABLE nccn_elklewi_driving_surveyelkgroupobservations (
"park_code" VARCHAR,
"survey_year" BIGINT,
"month" BIGINT,
"period" VARCHAR,
"survey_date" TIMESTAMP,
"route" VARCHAR,
"survey_completed" VARCHAR,
"temp_c_start" DOUBLE,
"wind_start" DOUBLE,
"wind_desc" VARCHAR,
"sky_start" DOUBLE,
"sky_desc" VARCHAR,
"elk_seen" VARCHAR,
"observation_time" VARCHAR,
"coord_source" VARCHAR,
"mile_marker" DOUBLE,
"obs_utme" BIGINT,
"obs_utmn" BIGINT,
"azimuth" BIGINT,
"distance_m" BIGINT,
"final_utme" BIGINT,
"final_utmn" BIGINT,
"habitat" VARCHAR,
"habitat_desc" VARCHAR,
"total_elk" BIGINT,
"branch_bulls" DOUBLE,
"spike_bulls" DOUBLE,
"total_bulls" BIGINT,
"antlerless_adults" DOUBLE,
"calves" DOUBLE,
"unknown" DOUBLE,
"duplicate_obs" BIGINT,
"is_excluded" BIGINT
);
CREATE TABLE nccn_elklewi_driving_surveyroutemarkers (
"park_code" VARCHAR,
"park_name" VARCHAR,
"location_code" VARCHAR,
"location_name" VARCHAR,
"location_type" VARCHAR,
"location_status" VARCHAR,
"mile_marker" DOUBLE,
"utm_east" BIGINT,
"utm_north" BIGINT,
"utm_zone" VARCHAR,
"utm_datum" VARCHAR,
"decimal_longitude_deg" DOUBLE,
"decimal_latitude_deg" DOUBLE,
"decimal_degrees_datum" VARCHAR,
"location_established" TIMESTAMP
);
CREATE TABLE nccn_elklewi_pellet_clearingcounts (
"park_code" VARCHAR,
"location_code" BIGINT,
"pellet_year" BIGINT,
"season" VARCHAR,
"survey_year" BIGINT,
"survey_date" TIMESTAMP,
"plot_code" VARCHAR,
"plot_label" VARCHAR,
"first_observer" BIGINT,
"num_groups" BIGINT,
"num_recount" BIGINT,
"is_excluded" BIGINT
);
CREATE TABLE nccn_elklewi_pellet_surveydata (
"park_code" VARCHAR,
"location_code" BIGINT,
"pellet_year" BIGINT,
"season" VARCHAR,
"survey_year" BIGINT,
"survey_date" TIMESTAMP,
"survey_start" VARCHAR,
"survey_end" VARCHAR,
"dual_observers" VARCHAR,
"veg_type" VARCHAR,
"veg_desc" VARCHAR,
"light_level" VARCHAR,
"blowdown_severity_pct" VARCHAR,
"blowdown_midpt" DOUBLE,
"severity_desc" VARCHAR,
"plot_code" VARCHAR,
"plot_label" VARCHAR,
"survey_num" BIGINT,
"observer" VARCHAR,
"plot_veg" VARCHAR,
"veg_cover_pct" DOUBLE,
"survey_mins" DOUBLE,
"survey_secs" DOUBLE,
"num_cleared" DOUBLE,
"plot_notes" VARCHAR,
"obs_number" DOUBLE,
"pellet_class" DOUBLE,
"num_clumps" DOUBLE,
"num_pellets" DOUBLE,
"recount_code" VARCHAR,
"recount_desc" VARCHAR,
"is_excluded" BIGINT
);
CREATE TABLE nccn_elklewi_pellet_surveylocations (
"park_code" VARCHAR,
"park_name" VARCHAR,
"location_code" BIGINT,
"location_type" VARCHAR,
"location_status" VARCHAR,
"utm_east" BIGINT,
"utm_north" BIGINT,
"utm_zone" VARCHAR,
"utm_datum" VARCHAR,
"decimal_longitude_deg" DOUBLE,
"decimal_latitude_deg" DOUBLE,
"decimal_degrees_datum" VARCHAR,
"eval_status" VARCHAR,
"eval_status_desc" VARCHAR,
"evaluation_notes" VARCHAR,
"location_notes" VARCHAR,
"location_established" TIMESTAMP,
"location_discontinued" TIMESTAMP
);
CREATE TABLE nccn_elklewi_pellet_surveyspecies (
"park_code" VARCHAR,
"location_code" BIGINT,
"pellet_year" BIGINT,
"season" VARCHAR,
"survey_year" BIGINT,
"survey_date" TIMESTAMP,
"species_code" VARCHAR,
"scientific_name" VARCHAR,
"common_name" VARCHAR,
"percent_cover" DOUBLE,
"percent_browsed" DOUBLE,
"browse_severity" VARCHAR,
"obs_notes" VARCHAR,
"is_excluded" BOOLEAN
);
CREATE TABLE nccn_elklewi_pellet_surveystatus (
"park_code" VARCHAR,
"location_code" BIGINT,
"location_status" VARCHAR,
"pellet_year" BIGINT,
"fall" VARCHAR,
"winter" VARCHAR,
"location_established" TIMESTAMP,
"location_discontinued" TIMESTAMP,
"comments" VARCHAR
);
Anyone who has the link will be able to view this.