Data Sources for Michigan

From OpenStreetMap Wiki
Jump to navigation Jump to search

Do not copy from sources which do not have a compatible copyright license. When in doubt, it is better to gather your own data.

Add to this table data sources that could or have been used to verify data in Michigan - for new imports and import processes see Import.

Datasource Name County Name Relation ID License Data Status Status Last Verified User Lead Notes
Alcona County
Alger County
Allegan County GIS Allegan County
Alpena County
Antrim County
Arenac County
Baraga County
Barry County
Bay County
Benzie County
Berrien County
Branch County
Calhoun County
Cass County
Charlevoix County
Cheboygan County
Chippewa County
Clare County
Clinton County GIS Clinton County
Crawford County
Delta County
Dickinson County
Eaton County GIS Eaton County
Emmet County
Genesee County GIS Genesee County
Gladwin County
Gogebic County
Grand Traverse County
Gratiot County
Hillsdale County
Houghton County
Huron County GIS Huron County
Ingham Parks Ingham County
Ingham County Parcels Ingham County
Parcels Ionia County
Iosco County
Iron County
Isabella County
GIS Jackson County
Kalamazoo County
Kalkaska County
Kent County GIS Kent County
Keweenaw County
Lake County
Lapeer County
Leelanau County
Lenawee County
Livingston County GIS Livingston County
Luce County
Mackinac County
Macomb County
Manistee County
Marquette County
Mason County
Mecosta County
Menominee County
Midland County
Missaukee County
Monroe County
Montcalm County GIS Montcalm County
Montmorency County
Muskegon County
Newaygo County
Oakland County
Oceana County
Ogemaw County
Ontonagon County
Osceola County
Oscoda County
Otsego County
Ottawa County
Presque Isle County
Roscommon County
Saginaw County
St. Clair County
St. Joseph County
Sanilac County
Schoolcraft County
Shiawassee County
Tuscola County
Van Buren County
Washtenaw County 359766
Wayne County 359767
Wexford County 1907341

Table Field

Datasource Name

County Name

Relation ID


Data Status

Status Last Verified

Field value Format

YYYYMMDD example 210228

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.


Field suggestions

Fields under consideration

  • Data Type - field that can indicate what types of data this source can provide or maybe new columns for each breakdown which then would require import per data type or multiple listing of the source. Needs discussion for handling.
  • Source QA Tool or Workflow - link to page describing the datasource workflow and link(s) to open access tools supporting comparing and/or monitoring the data variance between OSM and the source data.
  • Data Update Frequency - if known the period in which data is updated and should be reviewed