Michigan/DNR Data

The State of Michigan Department of Natural Resources has divisions for Forestry, Fisheries, Wildlife, and Parks and Recreation. Much of their spatial data is made available through an ESRI ArcGIS Online Hub.

Add to this table data sources that could or have been used to verify data in Michigan from the DNR - for import processes see Import.

Table of Data Sources

Datasource Name	Equivalent OSM Keys	Data Status	Data Source Last Updated by MDNR	User Lead	Notes
Michigan DNR Project Boundary 2020	boundary=*	In Progress	2022-05-03	Skunkman56	This dataset contains boundaries of state parks, forest management units, wildlife areas, recreation areas, and other collected named property holdings as part of the comprehensive strategy for land retention, acquisition, and disposal. It appears to be frequently updated by the MDNR.
Non Motorized Trails	highway=path highway=bridleway cycleway=*	In Progress	2022-04-29	Skunkman56	This dataset contains non-motorized trails such as bicycle, horse-riding, and hiking paths. This dataset is updated weekly and appears to be the authoritative source from the Michigan DNR for mapping these features.
Michigan DNR Designated Water Trails	route=canoe	In Progress	2022-04-28	Skunkman56	This dataset contains water trails. This dataset seems to be updated weekly in conjunction with the Non-Motorized Trails data and appears to be the authoritative source from the Michigan DNR for mapping these features.
Michigan DNR Designated Bicycle Trails	route=bicycle route=mtb	In Progress	2022-04-28	Skunkman56	This dataset contains Bicycle and mountain biking routes, often in conjunction with trails with primary designation for hiking, so perhaps may better mapped as separate route relations. This dataset is updated weekly in conjunction with the Non-Motorized Trails data and appears to be the authoritative source from the Michigan DNR for mapping these features.
Michigan DNR Designated Equestrian Trails	route=horse	In Progress	2022-04-28	Skunkman56	This dataset contains horse-riding trails. This dataset seems to be updated weekly in conjunction with the Non-Motorized Trails data and appears to be the authoritative source from the Michigan DNR for mapping these features.
Michigan DNR Designated Ski Trails	route=piste	In Progress	2022-04-28	Skunkman56	This dataset contains cross-country ski trails. This dataset seems to be updated weekly in conjunction with the Non-Motorized Trails data and appears to be the authoritative source from the Michigan DNR for mapping these features.
Michigan DNR Designated ORV Routes	route=atv	In Progress	2022-04-28	Skunkman56	This dataset contains trails for off-roading use of motor vehicles that are capable of navigating smoothness=horrible and smoothness=very_horrible, usually within the category of Off-road vehicle such as atv's, Side-by-side (vehicle), and motorcycle:type=offroad, but full-size highway vehicles may also be permitted on some routes. For those routes open to all types, consider tagging for [[key:ohv|off highway vehicle] and key:4wd_only. For routes only open to narrower vehicles such as atv's and off-road motorcycles, specify the key:maxwidth restriction and do not use key:ohv.
Michigan DNR Designated Motorcycle Trails	route=motorcycle	In Progress	2022-04-28	Skunkman56	This dataset contains dirtbike trails. Consider tagging with motorcycle:type=offroad to clarify the types of motorcycles suitable for trail use. This dataset seems to be updated weekly in conjunction with the Non-Motorized Trails data and appears to be the authoritative source from the Michigan DNR for mapping these features.
Michigan DNR Designated MCCCT Trails	route=motorcycle	In Progress	2022-04-28	Skunkman56	This dataset contains off-road motor vehicle trails managed by the Michigan Cross Country Cycle Club "MCCT". This dataset is a subset of the DNR Designated ORV Routes data source with the difference being operator=*. This dataset seems to be updated weekly in conjunction with the Non-Motorized Trails data and appears to be the authoritative source from the Michigan DNR for mapping these features.
Low-slope/PAMD accessible parking area	amenity=parking	Not Started	2019-03-29	Skunkman56	This dataset contains listings of handicap-accessible parking areas, but appears to have only 4 records and not recently updated
Low-slope/PAMD accessible parking and field blinds	amenity=parking amenity=hunting_stand	Not Started	2019-03-29	Skunkman56	This dataset contains listings of handicap-accessible parking areas and hunting blinds, but appears to have only 8 records and not recently updated
Low-slope/PAMD accessible trail	highway=footway	Not Started	2019-03-29	Skunkman56	This dataset contains listings of handicap-accessible trails, but appears to have only 4 records and not recently updated

Data Sources and OSM Mapping

Data Source Name

Attribute Field	Equivalent OSM Key/Tag	Notes

Michigan State Forest Covertype

Attribute Field	Equivalent OSM Key/Tag	Notes
CovertypeCode	Forest covertype code	three-digit Michigan DNR forest type code
FCS_Key	Forest compartment-stand	eight-digit code relation to Forest management unit, compartment and stand number
FC_Key	Forest compartment	five-digit code relating to Forest management unit and compartment
FMU	Forest Management Unit	two-digit code relating to Forest management unit

Mapping of Michigan DNR Forest Types to USNVC

L4Covertype	Michigan Forest Inventory Description	MDNR CoverCode	MDNR CoverType	natural=*	Further tags
	Unspecified	0	Unspecified
110	Low Intensity Urban	X	Urban
4130	Aspen			natural=wood	leaf_type=broadleaved leaf_cycle=deciduous
6120	Lowland Cedar	C, Q	Northern White Cedar, Mixed Swamp Conifers	natural=wetland	wetland=swamp USNVC: A3720 Northern White-cedar - Red Maple - Tamarack Swamp Forest Alliance,
42110	Planted Red Pine			landuse=forest	leaf_type=needleleaved leaf_cycle=evergreen USNVC: CST007177 Pinus resinosa Forest Plantation (cultural subtype)
310	Herbaceous Openland			natural=grassland
622	Lowland Shrub			natural=wetland	wetland=marsh or wetland=bog?

User Lead

User account responsible for coordinating monitoring of deviation from source for verification, errors, etc. Possibly could be primarily done via software or script, but someone should still be a point of contact and making sure any automated alerts are being monitored. Responsibility shifts from Import (coordinating the import) to maintainer (making sure the data stays fresh and current). Anyone can claim this role, but should be responsive to messages via change-sets, OSM lists, and/or direct messages.