EPA Facility Registry Service (FRS): ER_RMP
This web feature service contains location and facility identification information from EPA's Facility Registry System (FRS) for the subset of facilities that link to the Risk Management Plan (RMP) database. RMP stores the risk management plans reported by companies that handle, manufacture, use, or store certain flammable or toxic substances, as required under section 112(r) of the Clean Air Act (CAA). FRS identifies and geospatially locates facilities, sites or places subject to environmental regulations or of environmental interest. Using vigorous verification and data management procedures, FRS integrates facility data from EPA's national program systems, other federal agencies, and State and tribal master facility records and provides EPA with a centrally managed, single source of comprehensive and authoritative information on facilities. This data set contains the subset of FRS integrated facilities that link to RMP facilities once the RMP data has been integrated into the FRS database. Additional information on FRS is available at the EPA website https://www.epa.gov/enviro/facility-registry-service-frs. These data are considered sensitive and are restricted to internal use only. The download file and map service are accessible only on the EPA intranet. EPA Category: Mission Sensitive, NARA Category: Critical Infrastructure.
EPA Facility Registry Service (FRS): ER_TRI
This web feature service contains location and facility identification information from EPA's Facility Registry System (FRS) for the subset of facilities that link to the Toxic Release Inventory (TRI) System. TRI is a publicly available EPA database reported annually by certain covered industry groups, as well as federal facilities. It contains information about more than 650 toxic chemicals that are being used, manufactured, treated, transported, or released into the environment, and includes information about waste management and pollution prevention activities. FRS identifies and geospatially locates facilities, sites or places subject to environmental regulations or of environmental interest. Using vigorous verification and data management procedures, FRS integrates facility data from EPA's national program systems, other federal agencies, and State and tribal master facility records and provides EPA with a centrally managed, single source of comprehensive and authoritative information on facilities. This data set contains the subset of FRS integrated facilities that link to TRI facilities once the TRI data has been integrated into the FRS database. Additional information on FRS is available at the EPA website https://www.epa.gov/enviro/facility-registry-service-frs. These data are considered sensitive and are restricted to internal use only. The download file and map service are accessible only on the EPA intranet. EPA Category: Mission Sensitive, NARA Category: Critical Infrastructure.
EPA Facility Registry Service (FRS): ER_CHEMICALS
To improve public health and the environment, the United States Environmental Protection Agency (USEPA) collects information about facilities, sites, or places subject to environmental regulation or of environmental interest. These data are considered sensitive and are restricted to internal use only. The download file and map service are accessible only on the EPA intranet. EPA Category: Mission Sensitive, NARA Category: Critical Infrastructure.
EPA Facility Registry Service (FRS): ER_RCRATSD
EPA Facility Registry Service (FRS): ER_CERCLIS
This web feature service contains location and facility identification information from EPA's Facility Registry System (FRS) for the subset of facilities that link to the Comprehensive Environmental Response, Compensation, and Liability Information System (CERCLIS) non-NPL sites. Superfund is a program administered by the EPA to locate, investigate, and clean up the worst hazardous waste sites throughout the United States. Before Superfund, Americans were less aware of how dumping chemical wastes might affect public health and the environment. Hazardous wastes were often left in the open, where they seeped into the ground, flowed into rivers and lakes, and contaminated soil and groundwater. Consequently, where these practices were intensive or continuous, there were uncontrolled or abandoned hazardous waste sites. These sites include abandoned warehouses, manufacturing facilities, processing plants, and landfills. Citizen concern about the extent of this problem prompted Congress in 1980 to establish the Superfund Program to eliminate the health and environmental threats posed by hazardous waste sites. EPA administers the Superfund program in cooperation with individual states and tribal governmentsFRS integrates facility data from EPA's national program systems, other federal agencies, and State and tribal master facility records and provides EPA with a centrally managed, single source of comprehensive and authoritative information on facilities. This data set contains the subset of FRS integrated facilities that link to CERCLIS non-NPL facilities once the CERCLIS data has been integrated into the FRS database. Additional information on FRS is available at the EPA website https://www.epa.gov/enviro/facility-registry-service-frs. These data are considered sensitive and are restricted to internal use only. The download file and map service are accessible only on the EPA intranet. EPA Category: Mission Sensitive, NARA Category: Critical Infrastructure.
EPA Facility Registry Service (FRS): ER_FRP
This dataset contains location and facility identification information from EPA's Facility Registry System (FRS) for the subset of facilities that link to Facility Response Plan (FRP) in the Oil database. These facilities are subject to the requirements to prevent and respond to oil spills. FRP facilities are referred to as substantial harm facilities due to the quantities of oil stored and facility characteristics. FRS identifies and geospatially locates facilities, sites or places subject to environmental regulations or of environmental interest. Using vigorous verification and data management procedures, FRS integrates facility data from EPA's national program systems, other federal agencies, and State and tribal master facility records and provides EPA with a centrally managed, single source of comprehensive and authoritative information on facilities. This data set contains the subset of FRS integrated facilities that link to Oil FRP facilities once the Oil data has been integrated into the FRS database. Additional information on FRS is available at the EPA website https://www.epa.gov/enviro/facility-registry-service-frs. These data are considered sensitive and are restricted to internal use only. The download file and map service are accessible only on the EPA intranet. EPA Category: Mission Sensitive, NARA Category: Critical Infrastructure.
EPA Facility Registry Service (FRS): ER_CONTACTS
EPA Facility Registry Service (FRS): ER_NAICS
EPA Facility Registry Service (FRS): ER_SIC
EPA Facility Registry Service (FRS): ER_STATE_ID
EPA Facility Registry Service (FRS): ER_TSCA
This web feature service contains location and facility identification information from EPA's Facility Registry System (FRS) for the subset of facilities that link to the Toxic Substances Control Act (TSCA) System. The TSCA database supports the Toxic Substances Control Act (TSCA) of 1976, which provides EPA with authority to require reporting, record-keeping and testing requirements, and restrictions relating to chemical substances and/or mixtures. Certain substances are generally excluded from TSCA, including, among others, food, drugs, cosmetics and pesticides. TSCA addresses the production, importation, use, and disposal of specific chemicals including polychlorinated biphenyls (PCBs), asbestos, radon and lead-based paint.FRS identifies and geospatially locates facilities, sites or places subject to environmental regulations or of environmental interest. Using vigorous verification and data management procedures, FRS integrates facility data from EPA's national program systems, other federal agencies, and State and tribal master facility records and provides EPA with a centrally managed, single source of comprehensive and authoritative information on facilities. This data set contains the subset of FRS integrated facilities that link to TSCA facilities once the TSCA data has been integrated into the FRS database. Additional information on FRS is available at the EPA website https://www.epa.gov/enviro/facility-registry-service-frs. These data are considered sensitive and are restricted to internal use only. The download file and map service are accessible only on the EPA intranet. EPA Category: Mission Sensitive, NARA Category: Critical Infrastructure.
Individual informal consumer complaint data detailing complaints filed with the Consumer Help Center beginning October 31, 2014. This data represents information selected by the consumer. The FCC does not verify the facts alleged in these complaints.
This is the landing page for 49 CFR Part 225 Railroad Accident, incident, Casualty and Operational data.
The U.S. Department of Transportation has convened an interagency working group, led by the Bureau of Transportation Statistics, to develop timely information on supply chain activity. The working group includes relevant DOT modes and the U.S. Departments of Agriculture, Energy, Commerce and Labor. BTS freight information covers the following four areas: 1. Port Data - Inside the Gate 2. Port Data - Outside the Gate 3. Freight Movement 4. Transportation Labor and Capacity Tightness Visuals of the data can be found at: https://www.bts.gov/freight-indicators#container-capacity Note: In May 2025, Canadian Pacific Kansas City (CPKC) started reporting data to reflect the April 14, 2023, merger of Canadian Pacific (CP) and Kansas City Southern (KCS). New charts representing CKPC data were added and new data for CKPC will be updated weekly from May 10, 2025. The charts for CP and KCS will not be updated in the future.
Crossing Inventory Source Data (Form 71) - Current
A highway-rail crossing is a location where a public highway, road, street, or private roadway, including associated sidewalks and pathways, crosses one or more railroad tracks. All such crossings are reported by railroads and state Department of Transportations to the FRA on Form FRA F 6180.71 U.S. DOT Crossing Inventory Form. Each location has an assigned U.S. DOT Grade Crossing Identification Number, or crossing ID. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/DownloadCrossingInventoryData.aspx). To download data that contains data in a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Crossing-Inventory-Data-Current/m2f8-22s6. The data dictionary can be found here: https://data.transportation.gov/api/views/8uv2-y4is/files/9ad38db9-c214-4e51-8e0a-31eeaca0d77d?download=true&filename=GCIS_Data_Dictionary_External_Use_v3-2-0-152_Rel_06-21-2022.pdf For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
*This is a "daily difference" dataset. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.* This dataset contains information on a carrier’s/broker’s/freight forwarder’s previous insurance policy(ies). This dataset contains the DOT number and docket number of the entity. Additionally, it contains the cancellation method (cancelled, replaced, name change, transferred), the type of policy, the policy number, and the effective and cancellation dates of the policy.
Trespasser & Suicide Reports - Landing Page
Crossing Inventory Data (Form 71) - Historical
A highway-rail crossing is a location where a public highway, road, street, or private roadway, including associated sidewalks and pathways, crosses one or more railroad tracks. All such crossings are reported by railroads and state Department of Transportations to the FRA on Form FRA F 6180.71 U.S. DOT Crossing Inventory Form. Each location has an assigned U.S. DOT Grade Crossing Identification Number, or crossing ID. This dataset is in a user-friendly human-readable format. It contains the historical crossing inventory. To download the current inventory data, go here: https://data.transportation.gov/Railroads/Crossing-Inventory-Data-Form-71-Current/m2f8-22s6. The data dictionary can be found here: https://data.transportation.gov/api/views/m2f8-22s6/files/55a89796-f127-402c-82e3-09d5af892b42?download=true&filename=Form71_Data_Dictionary.xlsx. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
This is the landing page to download Form 55 Injury/Illness Summary [Operational Data].
Accident Type (including Highway-Rail Crossings) (3.08)
This is the page for Accident Type (including Highway-Rail Crossings) (3.08).
Injury/Illness Summary - Operational Source Data (Form 55)
All railroads are required to submit their operational data for train miles, employee hours worked, yard switching miles, the number of passengers transported, and passenger miles monthly on Form FRA F 6180.55 Injury/Illness Summary [Operational Data]. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/on_the_fly_download.aspx). To download data that contains data is a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Injury-Illness-Summary-Operational-Data/m8i6-zdsy. The data dictionary can be found here: https://data.transportation.gov/api/views/unww-uhxd/files/fa3f4232-2794-45ed-8062-afae43a860fd?download=true&filename=rrsfile_EFFECTIVE_060111%20(1).pdf. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
The FRA Milepost is a spatial file that originates of multiple sources and contains point locations of mileposts along the FRA's rail network. The mileposts was developed from varies sources and should only be used as a reference file. The railroad lines and their mileposts are privately owned and are subjected of changed based on the rail owner. If used for identifying specific locations, please contact the railroad to verify the mileposts numbers and their locations.
This is the landing page for data for Form 6180.55a Injury/Illness Continuation Sheet.
*This is a "daily difference" dataset. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.* Information on insurance forms that were rejected by FMCSA. The dataset contains information on the insurance policy associated with the form, along with the date that the form was rejected and the reason for rejection (e.g., “Policy is already cancelled”). The dataset contains the DOT number and docket number of the carrier/broker/freight forwarder associated with the policy.
FRA develop a spatial point layer of the rail bridges over road and water. The bridges are a snapshot and is not an offical or complete inventory of all bridges. Railroads change ownership, railroads are abandoned, bridges are replaced, etc. therefore it cannot be relied upon as being accurate.
*This is a "daily difference" dataset. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.* Records showing the history of each authority granted to a carrier/broker/freight forwarder, along with the dates of the original authority action (e.g., “granted”) and the final authority action (e.g., “revoked”). The dataset contains the DOT number and docket number of the entity that holds or held the authority. As there can be multiple authorities for a single entity, there may be multiple records for an entity.
Crossing Inventory Warning Device Equipment Summary (8.10)
This report contains data for the highway-rail crossing inventory, broken out by the highest level of warning device present at the crossing. There are four views of data: by (1) state, (2) county, (3) city, and (4) railroad. The data is grouped by the type of warning devices present: four quad (full barrier) gates, all other gates, flashing lights, highway signals/bells, special active warning devices, stop signs, crossbucks, other signs or signals, or no signs or signals.
This a list of active and inactive railroads, companies, and other organizations related to railroad operations. Organization Type ID = 1 designates a railroad; 4 designates a non-railroad organization (e.g. company, shipper, public entity, etc.). If a code has a blank EndDate, this means the organization is active; a populated EndDate field means the organization is no longer active.
Injury/Illness Summary - Casualty Data (Form 55a)
Casualties are reportable fatalities, injuries, or illnesses arising from the operation of a railroad. Casualties may be classified as either fatal or nonfatal. All casualty incidents are reported to the FRA on Form FRA F 6180.55a Injury/Illness Continuation Sheet. This dataset is in a user-friendly human-readable format. To download the source dataset that contains raw data values, go here: https://data.transportation.gov/dataset/Form55a-Source-Table/kuvg-3uwp. The data dictionary can be found here: https://datahub.transportation.gov/api/views/rash-pd2d/files/26b34409-e658-4681-a55e-d9c03079c33c?download=true&filename=Form55a_Data_Dictionary.xlsx. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
This is the page for Casualty (Form 55a) PDF Generator report
*This is a "daily difference" dataset. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.* Information on carrier/broker/freight forwarder authorities that have been revoked by FMCSA. The dataset includes the DOT number and docket number of the entity, the type of authority revoked, and the reason.
This is the data download page for FRA Form 6180.54 Rail Equipment Accident/Incident data.
This is the landing page for the Form 6180.55a Injury/Illness Continuation Sheet [Casualty] data.
Injury/Illness Summary - Operational Data (Form 55)
All railroads are required to submit their operational data for train miles, employee hours worked, yard switching miles, the number of passengers transported, and passenger miles monthly on Form FRA F 6180.55 Injury/Illness Summary [Operational Data]. This dataset is in a user-friendly human-readable format. To download the source dataset that contains raw data values, go here: https://data.transportation.gov/dataset/Form-55-Source-Table/unww-uhxd. The data dictionary can be found here: https://datahub.transportation.gov/api/views/m8i6-zdsy/files/9271e9d5-ff71-4b06-a050-2ba1765bca36?download=true&filename=Form55_Data_Dictionary.xlsx. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
Crossing Inventory Data (Form 71) - Current
A highway-rail crossing is a location where a public highway, road, street, or private roadway, including associated sidewalks and pathways, crosses one or more railroad tracks. All such crossings are reported by railroads and state Department of Transportations to the FRA on Form FRA F 6180.71 U.S. DOT Crossing Inventory Form. Each location has an assigned U.S. DOT Grade Crossing Identification Number, or crossing ID. This dataset is in a user-friendly human-readable format. It contains the current crossing inventory - one record for each crossing. To download historical data, go here: https://data.transportation.gov/Railroads/Crossing-Inventory-Data-Historical/vhwz-raag. To download the source dataset that contains raw data values, go here: https://data.transportation.gov/dataset/Crossing-Inventory-Source-Data-Form-71-Current/xp92-5xme. The data dictionary can be found here: https://data.transportation.gov/api/views/m2f8-22s6/files/55a89796-f127-402c-82e3-09d5af892b42?download=true&filename=Form71_Data_Dictionary.xlsx. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
This is the landing page for operational data reported to the FRA on Form 6180.55 Injury/Illness Summary.
Highway-Rail Grade Crossing Accident/Incident Source Data (Form 57)
All impacts between railroad on-track equipment and highway users at a highway-rail grade crossing are reported by railroads to the FRA on Form FRA F 6180.57 Highway-Rail Grade Crossing Accident/Incident Report. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/on_the_fly_download.aspx). To download data that contains data in a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Highway-Rail-Grade-Crossing-Accident-Data/7wn6-i5b9. The data dictionary can be found here: https://datahub.transportation.gov/api/views/icqf-xf4w/files/531a212f-6b94-4403-9876-a6933a1469aa?download=true&filename=gxirfile_EFFECTIVE_060111%20(24).pdf. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
Records for each BOC3 agent hired by a carrier/broker/freight forwarder. Each entity must hire a BOC3 agent to represent them in legal matters to obtain operating authority. In some cases, entities may act as their own BOC3 agent. The records in the dataset contain the BOC3 agent’s name and address. The dataset also contains the DOT number and docket number of the represented entity. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.
*This is a "daily difference" dataset. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.* Records for each BOC3 agent hired by a carrier/broker/freight forwarder. Each entity must hire a BOC3 agent to represent them in legal matters to obtain operating authority. In some cases, entities may act as their own BOC3 agent. The records in the dataset contain the BOC3 agent’s name and address. The dataset also contains the DOT number and docket number of the represented entity.
State, County and City FIPS Reference Table
State, County and City FIPS (Federal Information Processing Standards) codes are a set of numeric designations given to state, cities and counties by the U.S. federal government. All geographic data submitted to the FRA must have a FIPS code.
This is the Rail Safety Overview Report (1.12), which contains summary level train accidents, highway-rail incidents, casualty and operational data.
Highway-Rail Grade Crossing Accident Prediction System (GXAPS)
*This is a "daily difference" dataset. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.* Information on the implementation dates of an active or pending insurance policy (posted date, effective date and cancel effective date). In addition to these dates, the record contains the insurance company name, the BI&PD underlying limit and maximum limit amounts, and the DOT number and docket number of the carrier/broker/freight forwarder that holds the policy.
Rail Equipment Accident/Incident Data (Form 54) Subset – Unique Train Accidents (Not at Grade Crossings)
October 2025 - Dataset View and OData/API Connection Change Notice - Please Read: https://data.transportation.gov/stories/s/6kdh-gsgx Rail equipment accidents/incidents, collisions, derailments, fires, explosions, acts of God, or other events involving the operation of railroad on-track equipment (standing or moving) and causing reportable damages greater than the reporting threshold for the year in which the accident/incident occurred, must be reported by railroads to the FRA on Form FRA 6180.54 - Rail Equipment Accident/Incident. Please note that this dataset displays unique train accidents. When an accident involves multiple railroads, each railroad must report its data. As a result, there can be multiple records for one accident. This dataset has been modified to pull and display one record for each accident. Highway-rail crossing incidents have also been removed from this dataset because they are not considered train accidents. To see the full dataset with all reports with all data for all accidents, please visit https://data.transportation.gov/Railroads/Rail-Equipment-Accident-Incident-Data/85tf-25kj. The data dictionary can be found here: https://datahub.transportation.gov/api/views/byy5-w977/files/ac84a1c8-56d4-4a21-85c2-3a33080ab720?download=true&filename=Form54_Data_Dictionary.xlsx. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
Transportation Services Index and Seasonally-Adjusted Transportation Data
About Transportation Services Index The Transportation Services Index (TSI), created by the U.S. Department of Transportation (DOT), Bureau of Transportation Statistics (BTS), measures the movement of freight and passengers. The index, which is seasonally adjusted, combines available data on freight traffic, as well as passenger travel, that have been weighted to yield a monthly measure of transportation services output. For charts and discussion on the relationship of the TSI to the economy, see our Transportation as an Economic Indicator: Transportation Services Index page (https://data.bts.gov/stories/s/TET-indicator-1/9czv-tjte) For release schedule see: https://www.bts.gov/newsroom/transportation-services-index-release-schedule About seasonally-adjusted data Statisticians use the process of seasonal-adjustment to uncover trends in data. Monthly data, for instance, are influenced by the number of days and the number of weekends in a month as well as by the timing of holidays and seasonal activity. These influences make it difficult to see underlying changes in the data. Statisticians use seasonal adjustment to control for these influences. Controlling of seasonal influences allows measurement of real monthly changes; short and long term patterns of growth or decline; and turning points. Data for one month can be compared to data for any other month in the series and the data series can be ranked to find high and low points. Any observed differences are “real” differences; that is, they are differences brought about by changes in the data and not brought about by a change in the number of days or weekends in the month, the occurrence or non-occurrence of a holiday, or seasonal activity.
This is the summary of operational data for train miles, number of employee hours worked, yard switching miles, passenger miles, number of passengers transported and the number of reports submitted.
Railroad Equipment Accident/Incident Source Data (Form 54)
Rail equipment accidents/incidents, collisions, derailments, fires, explosions, acts of God, or other events involving the operation of railroad on-track equipment (standing or moving) and causing reportable damages greater than the reporting threshold for the year in which the accident/incident occurred, must be reported by railroads to the FRA on Form FRA 6180.54 - Rail Equipment Accident/Incident. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/on_the_fly_download.aspx). To download data that contains data in a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Rail-Equipment-Accident-Incident-Data/85tf-25kj. The data dictionary can be found here: https://datahub.transportation.gov/api/views/aqxq-n5hy/files/ea00a728-94b0-43e7-8c11-8481f13170a7?download=true&filename=accfile_EFFECTIVE_060111%20(8).pdf. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
This is the landing page for crossing incident data from Form 6180.57 Highway-Rail Incidents, with crossing inventory data from Form 6180.71 USDOT Crossing Inventory.
Crossing Inventory Source Data (Form 71) - Historical
A highway-rail crossing is a location where a public highway, road, street, or private roadway, including associated sidewalks and pathways, crosses one or more railroad tracks. All such crossings are reported by railroads and state Department of Transportations to the FRA on Form FRA F 6180.71 U.S. DOT Crossing Inventory Form. Each location has an assigned U.S. DOT Grade Crossing Identification Number, or crossing ID. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/DownloadCrossingInventoryData.aspx). To download data that contains data in a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Crossing-Inventory-Data-Form-71-Historical/vhwz-raag/about_data. The data dictionary can be found here: https://data.transportation.gov/api/views/8uv2-y4is/files/9ad38db9-c214-4e51-8e0a-31eeaca0d77d?download=true&filename=GCIS_Data_Dictionary_External_Use_v3-2-0-152_Rel_06-21-2022.pdf For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
Rail Equipment Accident/Incident Data (Form 54)
Rail equipment accidents/incidents, collisions, derailments, fires, explosions, acts of God, or other events involving the operation of railroad on-track equipment (standing or moving) and causing reportable damages greater than the reporting threshold for the year in which the accident/incident occurred, must be reported by railroads to the FRA on Form FRA 6180.54 - Rail Equipment Accident/Incident. This dataset is in a user-friendly human-readable format. To download the source dataset that contains raw data values, go here: https://data.transportation.gov/dataset/Form-54-Source-Table/aqxq-n5hy. The data dictionary can be found here: https://data.transportation.gov/api/views/85tf-25kj/files/729e3c9c-7dff-429d-9ac0-8f35a0762aa2?download=true&filename=Form54_Data_Dictionary.xlsx For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
Highway-Rail Grade Crossing Incident Data (Form 57)
All impacts between railroad on-track equipment and highway users at a highway-rail grade crossing are reported by railroads to the FRA on Form FRA F 6180.57 Highway-Rail Grade Crossing Accident/Incident Report. This dataset is in a user-friendly human-readable format. To download the source dataset that contains raw data values, go here: https://data.transportation.gov/dataset/Form57-Source-Table/icqf-xf4w. The data dictionary can be found here: https://data.transportation.gov/api/views/7wn6-i5b9/files/009f2989-72b7-486c-8a3b-539df5e3d9c8?download=true&filename=Form57_Data_Dictionary.xlsx. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
Highway-Rail Grade Crossing Incident (Form 71) Reason for Update Field Reference Table
*This is a "daily difference" dataset. See dataset attachment "FMCSA Dataset Description and Data Definitions - Select Datasets" for more information.* Records for carriers/brokers/freight forwarders with active, inactive, or pending authorities (common or contract). It includes the DOT number and MC/FF/MX number for the carrier/broker/freight forwarder, along with company census data, e.g., types of authority, address, types of insurance on file, and amounts of insurance on file.
Grade Crossing Inventory System - Highway-Rail Grade Crossing Inventory (Form 71) Field Reference Table
This a reference table for the Grade Crossing Inventory System, which is the application used to submit data for the Highway-Rail Grade Crossing Inventory (Form 71). The data dictionary for GCIS is attached as well. The LookupType column contains the name of the field/column in the source GCIS/Form 71 dataset. The LookupValue column contains the submitted value and the LookupText field is the human-readable text description of that value (e.g. for LookupType=TypeXing; LookupValue=3 and LookupText=Public, which designates that a crossing is public). This reference table can be used for the Crossing Inventory Source Data Form 71 – Current: https://datahub.transportation.gov/dataset/Crossing-Inventory-Source-Data-Form-71-Current/xp92-5xme.
About the Data: The dataset includes recall information related to specific NHTSA campaigns. Users can filter based on characteristics like manufacturer and component. The dataset can also be filtered by recall type: tires, vehicles, car seats, and equipment. The earliest campaign data is from 1966. The dataset displays the completion rate from the latest Recall Quarterly Report or Annual Report data from Year 2015 Quarter 1 (2015-1) onward. Data Reporting Requirement: Manufacturers who determine that a product or piece of original equipment either contains a safety defect or is not in compliance with Federal safety standards are required to notify NHTSA within 5 business days. NHTSA requires that manufacturers file a Defect and Noncompliance Report in compliance with Federal Regulation 49 (the National Traffic and Motor Safety Act) Part 573, which identifies the requirements for safety recalls. This information is stored in the NHTSA database referenced above. Notes: The default visualization depicted here represents only the top 12 manufacturers for the current calendar year. Please use the Filters for specific data requests. For a complete historical perspective, please visit: https://www.nhtsa.gov/sites/nhtsa.gov/files/2023-03/2022-Recalls-Annual-Report_030223-tag.pdf.
Train Accident/Incident (Form 54) PDF Generator
This is the Train Accident/Incident (Form 54) PDF Generator report.
Using OData Connections with Excel and Access
Train Accident (not at Highway-Rail Crossings) Summary (2.03)
This is the page for Train Accident (not at Highway-Rail Crossings) Summary (2.03).
General Purpose Data and Statistics. GradeDEC.Net is a web-based tool for the investment analysis of highway-rail grade crossing improvements. It provides state departments of transportation, local governments, metropolitan planning agencies, inspectors, and railroad companies with the online ability to conduct benefit-cost analysis of highway-rail grade crossing infrastructure investments. GradeDEC.Net allows users to divert highway traffic to and from closed or separated grade crossings to adjacent crossings, and calculate a full set of benefits including changes in accident risk associated with changes in traditional grade crossing technology. Users can also evaluate supplemental safety measures listed in the Notice of Proposed Rulemaking covering the use of locomotive horns at highway-rail grade crossing. Users are also able to save an analysis on-site for later revision and update and submit reports directly to the FRA.
Work Schedules and Sleep Patterns of Railroad Employees
The Federal Railroad Administration (FRA) sponsored a study of the work schedules and sleep patterns of railroad employees. The purpose of the study was to understand work-schedule related fatigue that affects various categories of railroad employees by documenting a group's work/rest schedules and sleep patterns to ascertain their impact on the level of fatigue/alertness.Employees surveyed include: signalmen, maintenance of way (MOW) workers, dispatchers, and train & engine service workers (in both freight and passenger train service)
Federal Railroad Administration GIS Web Mapping Application
The GIS Web Mapping Application is design to have the look and feel as Google Earth. The primary functionality is to provide the user information about FRA's rail lines, rail crossings, freight stations, and mileposting.
The entire National Highway-Rail Crossing Inventory is available in three separate downloadble files. There is a file of all current Public-at-Grade crossings. There is a file of all current Private and grade-separated crossings. There is also a file which contains about 10 years of archival records for all types of crossings.
This file contains reported cases of impacts between on-track equipment and any user of a public or private highway-rail intersection. National files from 1975 through the current year are available for download. In addition, individual files by State are available for the years 1991 through the current year.
"This file contains reported cases of collisions, derailments, fires, explosions, acts of God, or other events involving the operation of railroad on-track equipment and involving damages exceeding the reporting threshold for the year reported. National files from 1975 through the current year are available for download. In addition, individual files by State are available for the years 1991 through the current year.
This text file contains the date, CUSIP numbers, ticker symbols, issuer name, price, and total number of fails-to-deliver (i.e., the balance level outstanding) recorded in the National Securities Clearing Corporation's ("NSCC") Continuous Net Settlement (CNS) system aggregated over all NSCC members.
Agency office locations located that service tribes at the reservation level. The twelve regional offices located in the heart of Indian Country. The Bureau of Indian Affairs Central Office oversees all the the regional offices and is also included in this file. Delivery of program services to the federally recognized tribes and individual Indians and Alaska Natives, whether directly or through contracts, grants or compacts, is administered by the 12 regional offices and 83 agencies that report to the BIA Deputy Director-Field Operations, located in Washington, D.C. Each regional office is headed by a Regional Director who is responsible for all Bureau activities within a defined geographical area except education, law enforcement and functions of an administrative nature. The typical Regional Office includes a Deputy Regional Director for Trust Services and Deputy Regional Director for Indian Services. The twelve regional offices are located in the heart of Indian Country with the agencies located at the reservation level. These regional offices services the needs of specific tribes. The Bureau of Indian Affairs Central Office oversees all the the regional offices and is also included in this file.
Bureau of Indian Affairs Branch of Geospatial Support
TEAMER: Numerical Modeling of WECs to Support OES Task 10
This submission contains the files for reproducing the waves only and sphere test article simulations for the experimental setup (three different wave conditions) associated with the Teamer Request for Technical Support 9 (RFTS 9) fluid dynamics simulations to support the Ocean Energy Systems Energy Technology Collaboration Program (OES) Task 10 Wave Energy Converters Modeling Verification and Validation effort. The README.pdf file contains details on the test domain, test cases, guidance for installing the required software, representative results, and additional details on the contents of the OES10_RFTS9_Archive.gz beyond those noted below. All this information and the contents of the OES10_RFTS9_Archive.gz file is also available via GitHub (see resource link below) under the 'distortingMesh/paddleWaveMaker' directory. The following directories are available in the OES10_RFTS9_Archive.gz file: - The 'data' directory contains the experimental validation data, the paddle input signal data, and representative output data from the OpenFOAM simulations. - The 'images' directory contains images of representative results for the three test cases and were generated using the python .py files located in the main directory. - The 'openFoamCaseFiles' directory contains cleaned OpenFOAM case files for the three test conditions. Refer to additional README files contained within the OES10_RFTS9_Archive.gz file for additional details. This project is part of the TEAMER RFTS 9 (request for technical support) program: Numerical Modeling of WECs to support OES task 10.
Tribal Colleges and Universities (TCUs) are chartered by their respective tribal governments, including the ten tribes within the largest reservations in the United States. The 33 accredited TCUs operate more than 90 campuses and sites in 15 states—covering most of Indian Country—and serve students from well more than 250 federally recognized Indian tribes. TCUs vary in enrollment (size), focus (liberal arts, sciences, workforce development/training), location (woodlands, desert, frozen tundra, rural, urban), and student population (predominantly American Indian). However, tribal identity is the core of every TCU, and they all share the mission of tribal self-determination and service to their respective communities. These academically rigorous institutions engage in partnerships with organizations including U.S. Department of the Interior, U.S. Department of Agriculture, U.S. Department of Housing and Urban Development, the National Science Foundation, National Aeronautics and Space Administration, and universities nationwide to support research and education programs that focus on issues such as climate change, sustainable agriculture, water quality, wildlife population dynamics, and diabetes prevention. Many support distance learning involving state-of-the-art learning environments.
It is important to note that the Tribal Leadership Directory is not an official listing of federally recognized tribes. It should be used in conjunction with the Federal Register Notice of Indian Entities Recognized and Eligible to Receive Services from the United States Bureau of Indian Affairs (81 Fed. Reg. 26826), which is the official listing of all federally recognized tribes in the United States, pursuant to the Federally Recognized Indian Tribe List Act of 1994 (Pub. L. 103-454, 108 Stat. 4791-4792). Since tribal elections and other changes in tribal leadership occur throughout the year, the Directory’s information is the most currently available at the time of its most recent weekly update. Because the BIA cannot track all tribal leadership changes in real time, it does not guarantee the accuracy of the Directory’s tribal contact information. To access the most recent Federal Register Notice, visit: https://www.federalregister.gov/documents/2024/01/08/2024-00109/indian-entities-recognized-by-and-eligible-to-receive-services-from-the-united-states-bureau-of
This dataset contains the tribal leadership locations as well as contact information for all 227 Alaska Native Villages. For a full list of Tribes in Alaska please visit: https://www.bia.gov/regional-offices/alaska/tribes-served. Within Alaska are a dynamic and diverse mix of Tribes, Tribal organizations and natural features. The passage of the Alaska Native Claims Settlement Act (ANCSA) in 1971 added an additional layer of land ownership across Alaska. Additionally, in 1998 the federal government officially recognized over 200 Indian tribes in Alaska (entirely separate entities from Alaska Native corporations), which opened the doors for a government-to-government relationships between those tribes and the federal government.
<pre style='background-color:rgb(255, 255, 255); color:rgb(76, 76, 76); font-family:"Segoe UI", Arial, sans-serif; font-size:13.3333px; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; letter-spacing:normal; margin:0px; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; width:1598.84px; word-spacing:0px;'>The BLM may purchase or acquire land and interests in land (including access easements, conservation easements, mineral rights and water rights) if funding is available, acquisition is supported in a land use plan, and there are no title defects, hazardous materials or other local issues. Acquiring land through purchase can enhance recreation opportunities, preserve open space, strengthen resource protection, and provide an alternative for transferring ownership to the BLM when a land exchange or other options are not available. Lands may also be acquired through donation. Such offers generally may be accepted as a gift to the United States if the lands are contiguous to, and “block-up” with, existing public lands. Donation may allow the donor an income tax deduction based on the appraised value of the donation.This dataset contains current and historic land acquisition cases with the dispositions of 'Authorized', Interim' or 'Status Record' The data are derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores "0", "1", "2", "3" should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores "4", "4.1", "5", "6", "7" and "8" were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3: Mapped to Section. Score of "8.1", "8.2", "8.3", "9" and "10" are mapped to the Section for various reasons (refer to log information in data quality field). Group 4: Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5: No NLSDB Geometry, Only Attributes. Scores "11", "12", "20", "21" and "22" do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 :Mapped to County. Scores of "25" map to the County. Group 7: Improved Geometry. Scores of "100" are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.
BLM CO Visual Resource Management Polygons
The objective of Visual Resource Management (VRM) is to manage public lands in a manner which will protect the quality of the scenic (visual) values of these lands. VRM is a system for minimizing the visual impacts of surface-disturbing activities and maintaining scenic values for the future. Each program involved in resource development work is responsible for protecting visual values. This includes ensuring that (1) personnel in each program who are involved in activities which affect visual values are properly trained in visual management techniques; (2) visual values are adequately considered in all management activities; and (3) adequate guidance and funding is available to accomplish these purposes
Range Improvements are man-made or man-caused features on the landscape designed and implemented for the purpose of improving the available forage, managing the season of use or use patterns and enhancing the overall rangeland health of areas available for domestic livestock use. Range improvements may occur on private, state, and public lands under the jurisdiction of the Bureau of Land Management (BLM) and/or other federal or state agencies. On public lands managed by the Bureau of Land Management (BLM), permittees or lessees (henceforth, “operators”) may be required to install range improvements to meet the terms and conditions of their permits or leases. Often the BLM, operators, and other interested parties work together and jointly contribute to construction.Range improvements are authorized physical modifications or treatment which are designed to improve production of forage; change vegetation composition; control patterns of use; provide water; stabilize soil and water conditions; restore, protect, and improve the conditions of the rangeland ecosystems to benefit livestock, wild horses and burros, and fish and wildlife. They include, but are not limited to, structures, treatment projects and use of mechanical devices or modifications achieved through mechanical means. Range Improvements. There are two kinds of range improvements: nonstructural and structural. Seeding or prescribed burns are examples of nonstructural range improvements. Fences or facilities such as wells or water pipelines are examples of structural improvements. Many structural improvements are considered permanent, as they are not easily removed from the land. This data standard will only relate to structural range improvements features as GIS and attribute data related to almost all non-structural range improvements is stored in other national data standard datasets (e.g. NISIMS, VTRT, NFPORS). Range improvement data is also available in the Range Improvement System (RIPS), a BLM database used for tracking the establishment and maintenance of range improvments. RIPS is the database of record and contains the data to be used for budgetary and workload planning. This data set shall be comprised of a spatial display of the data in RIPS. The record unique identifier within the RIPS database (RIPS number) will be added to GIS features in this data standard to link between spatial depictions of range improvements features to their corresponding RIPS records. Wherever possible RIPS data shall be used to populate this data set.
BLM OR Harvest Land Treatments Polygon Hub
HARV_POLY: This dataset represents completed harvest land treatments on BLM managed lands in the states of Oregon and Washington. Harvest treatments are the cutting and removal or trees or biomass.
This dataset contains notice level operations for locatable mineral cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Locatable minerals include all minerals locatable under the 1872 General Mining Law. This data set contains cases for locatable minerals under notice level operations with the case disposition of 'Authorized' or 'Pending'. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.
The 2021 Sage-grouse Habitat Planning Map update incorporates wildfire data and other edits relevant to the 2021 field and fire season as per typical processes used during the past decade. Additional areas of non-habitat, such as paved highways, municipal boundaries, water bodies etc., were also removed. However, the map extent for sage-grouse key habitat and potential restoration areas should be considered provisional, contingent on the final outcome of additional analyses currently underway in association with the national Greater Sage-grouse Conservation Strategy. This data set contains simple, landscape-scale greater sage-grouse habitat types for Idaho and constitutes a current approximation of sage-grouse habitat in the state. The data can be used for general conservation and restoration planning purposes, but additional data or field verification are needed for applications at finer scales. The habitat types include: (1) key sage-grouse habitat areas and (2) four habitat restoration types: (a) R1 - perennial native and non-native grasslands with high restoration potential; (b) R2 - annual grass dominated areas (either shrubland or grassland) with low restoration potential; (c) R3 - conifer encroachment areas with high restoration potential and (d) RB - areas that have recently burned and the type of habitat that is coming back and its restoration potential has not yet been determined. Beginning in 2015, the NA class was included to track areas that were previously identified as habitat but were removed due to vegetation type or terrain (eg. stands of existing timber on North-facing slopes). A new data set will be developed annually to update the planning map and chart landscape-level changes in sage-grouse habitat over time. Edits may also document refinements discovered through inventory, monitoring and modeling. This data covers all of Idaho and a small area in Nevada that is managed by Idaho BLM. Intended scale of use is 1:100,000. This dataset is not synonymous with BLM's Sage-grouse Habitat Management Areas (Priority, Important and General) as those incorporate additional habitat and sage-grouse population data or models.
Bureau of Land Management, id_so_information
The 2024 Sage-grouse Habitat Planning Map update incorporates wildfire data and other edits relevant to the 2024 field and fire season as per typical processes used during the past decade. Additional areas of non-habitat, such as paved highways, municipal boundaries, water bodies etc., were also removed. However, the map extent for sage-grouse key habitat and potential restoration areas should be considered provisional, contingent on the final outcome of additional analyses currently underway in association with the national Greater Sage-grouse Conservation Strategy. This data set contains simple, landscape-scale greater sage-grouse habitat types for Idaho and constitutes a current approximation of sage-grouse habitat in the state. The data can be used for general conservation and restoration planning purposes, but additional data or field verification are needed for applications at finer scales. The habitat types include: (1) key sage-grouse habitat areas and (2) four habitat restoration types: (a) R1 - perennial native and non-native grasslands with high restoration potential; (b) R2 - annual grass dominated areas (either shrubland or grassland) with low restoration potential; (c) R3 - conifer encroachment areas with high restoration potential and (d) RB - areas that have recently burned and the type of habitat that is coming back and its restoration potential has not yet been determined. Beginning in 2015, the NA class was included to track areas that were previously identified as habitat but were removed due to vegetation type or terrain (eg. stands of existing timber on North-facing slopes). A new data set will be developed annually to update the planning map and chart landscape-level changes in sage-grouse habitat over time. Edits may also document refinements discovered through inventory, monitoring and modeling. This data covers all of Idaho and a small area in Nevada that is managed by Idaho BLM. Intended scale of use is 1:100,000. This dataset is not synonymous with BLM's Sage-grouse Habitat Management Areas (Priority, Important and General) as those incorporate additional habitat and sage-grouse population data or models.
LSE_CLM_POLY: This dataset is a spatial representation of Leases and Claims (LSE_CLM). It is a portion of the total encumbrance data category that includes information about entities, rights, and restrictions relating to the use of Federal minerals. This dataset contains Leases and Claims within Oregon and Washington BLM-administered lands (surface and subsurface) and over mineral estate in areas of split estate (i.e., areas where the BLM administers Federal mineral estate, but the surface is not owned by the BLM).
Illustrate BLM Colorado Recreation point locations and boundaries. The point dataset represents the point features that show the physical locations of BLM Colorado Recreation Sites. The polygon dataset represents the spatial extent and boundaries of the BLM Colorado Recreation Sites.
BLM OR Mechanical Treatments Polygon Hub
MECH_POLY: This dataset represents completed mechanical treatments on BLM managed lands in the states of Oregon and Washington. Mechanical treatments are 1.) machine and manual methods of area treatment; 2.) pulling, piling, chopping, grinding, or mowing treatments to consolidate, reduce or clear live or dead vegetation (might be grass, brush, small trees, stump removal), as well as "Cut-Leave" of trees, and soil preparation such as plowing or ripping.
BLM's Visual Resource Management system provides a way to identify and evaluate scenic values to determine the appropriate levels of management. It also provides a way to analyze potential visual impacts and apply visual design techniques to ensure that surface-disturbing activities are in harmony with their surroundings. This is a two stage process: Inventory, Visual Resource Inventory (VRI) and Analysis, Visual Resource Contrast Rating.
The 2020 Sage-grouse Habitat Planning Map update incorporates wildfire data and other edits relevant to the 2020 field and fire season as per typical processes used during the past decade. Additional areas of non-habitat, such as paved highways, municipal boundaries, water bodies etc., were also removed. However, the map extent for sage-grouse key habitat and potential restoration areas should be considered provisional, contingent on the final outcome of additional analyses currently underway in association with the national Greater Sage-grouse Conservation Strategy. This data set contains simple, landscape-scale greater sage-grouse habitat types for Idaho and constitutes a current approximation of sage-grouse habitat in the state. The data can be used for general conservation and restoration planning purposes, but additional data or field verification are needed for applications at finer scales. The habitat types include: (1) key sage-grouse habitat areas and (2) four habitat restoration types: (a) R1 - perennial native and non-native grasslands with high restoration potential; (b) R2 - annual grass dominated areas (either shrubland or grassland) with low restoration potential; (c) R3 - conifer encroachment areas with high restoration potential and (d) RB - areas that have recently burned and the type of habitat that is coming back and its restoration potential has not yet been determined. Beginning in 2015, the NA class was included to track areas that were previously identified as habitat but were removed due to vegetation type or terrain (eg. stands of existing timber on North-facing slopes). A new data set will be developed annually to update the planning map and chart landscape-level changes in sage-grouse habitat over time. Edits may also document refinements discovered through inventory, monitoring and modeling. This data covers all of Idaho and a small area in Nevada that is managed by Idaho BLM. Intended scale of use is 1:100,000. This dataset is not synonymous with BLM's Sage-grouse Habitat Management Areas (Priority, Important and General) as those incorporate additional habitat and sage-grouse population data or models.
BLM CO Visual Resource Inventory Classes Polygon
BLM CO VRI Sensitivity Level Rating Unit Polygons
GRA_ALLOTMENT: This is the feature dataset for the Livestock grazing allotments and associated attributes describing some basic characteristics of the allotments for allotments on BLM lands in Oregon and Washington.
BLM CO VRI Visual Distance Zone Polygons
BLM CO VRI Scenic Quality Rating Unit Polygons
The 2023 Sage-grouse Habitat Planning Map update incorporates wildfire data and other edits relevant to the 2023 field and fire season as per typical processes used during the past decade. Additional areas of non-habitat, such as paved highways, municipal boundaries, water bodies etc., were also removed. However, the map extent for sage-grouse key habitat and potential restoration areas should be considered provisional, contingent on the final outcome of additional analyses currently underway in association with the national Greater Sage-grouse Conservation Strategy. This data set contains simple, landscape-scale greater sage-grouse habitat types for Idaho and constitutes a current approximation of sage-grouse habitat in the state. The data can be used for general conservation and restoration planning purposes, but additional data or field verification are needed for applications at finer scales. The habitat types include: (1) key sage-grouse habitat areas and (2) four habitat restoration types: (a) R1 - perennial native and non-native grasslands with high restoration potential; (b) R2 - annual grass dominated areas (either shrubland or grassland) with low restoration potential; (c) R3 - conifer encroachment areas with high restoration potential and (d) RB - areas that have recently burned and the type of habitat that is coming back and its restoration potential has not yet been determined. Beginning in 2015, the NA class was included to track areas that were previously identified as habitat but were removed due to vegetation type or terrain (eg. stands of existing timber on North-facing slopes). A new data set will be developed annually to update the planning map and chart landscape-level changes in sage-grouse habitat over time. Edits may also document refinements discovered through inventory, monitoring and modeling. This data covers all of Idaho and a small area in Nevada that is managed by Idaho BLM. Intended scale of use is 1:100,000. This dataset is not synonymous with BLM's Sage-grouse Habitat Management Areas (Priority, Important and General) as those incorporate additional habitat and sage-grouse population data or models.
CHEM_POLY: This dataset represents completed chemical land treatments on BLM managed lands in the states of Oregon and Washington. Chemical treatments are applications of herbicide or pesticide, to control or kill pests and invasive plants, or fertilizer to enhance plant growth.
Archive contains all of the files outlined in the main description. Directories include: 'data', 'images', and 'openFoamCaseFiles', in addition to .py files for generating associated plots.
Zipped File Geodatabase (Accessible on the EPA Intranet only)
ArcGIS Server Map Services (Accessible on the EPA Intranet only)
The README.pdf file contains details on the test domain, test cases, guidance for installing the required software, representative results, and additional details on the contents of the OES10_RFTS9_Archive.gz.
Project GitHub repository, refer to the 'distortingMesh/paddleWaveMaker' directory for additional information on this project.