Michigan/Data Sources

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 relation 1907303
Alger County relation 1898716
Allegan County GIS Allegan County relation 1907304
Alpena County relation 1907305
Antrim County relation 1907306
Arenac County relation 572624
Baraga County relation 1898717
Barry County relation 1907307
Bay County relation 571344
Benzie County relation 1907308
Berrien County relation 407519
Branch County relation 1801747
Calhoun County relation 1907309
Cass County relation 1801748
Charlevoix County relation 1907310
Cheboygan County relation 1907311
Chippewa County relation 1898718
Clare County relation 1907312
Clinton County GIS Clinton County relation 1582241
Crawford County relation 1907334
Delta County relation 1898719
Dickinson County relation 1798737
Eaton County GIS Eaton County relation 1582242
Emmet County relation 1907313
Genesee County GIS Genesee County relation 359764
Gladwin County relation 574448
Gogebic County relation 1798740
Grand Traverse County relation 1586055
Gratiot County relation 1907314
Hillsdale County GIS Hillsdale County relation 1801749
Houghton County relation 1898720
Huron County GIS Huron County relation 572689
Ingham Parks Ingham County relation 901500
Ingham County Parcels Ingham County relation 901500
Parcels Ionia County relation 1907315
Iosco County relation 611155
Iron County relation 1798741
Isabella County relation 1907316
GIS Jackson County relation 901501
Kalamazoo County relation 1907317
Kalkaska County relation 1907318
Kent County GIS Kent County relation 1907319
Keweenaw County relation 912579
Lake County relation 1907320
Lapeer County relation 359763
Leelanau County relation 1586056
Lenawee County relation 1801750
Livingston County GIS Livingston County relation 359765
Luce County relation 1898721
Mackinac County relation 1898722
Macomb County relation 359762
Manistee County relation 1907321
Marquette County relation 1798743
Mason County relation 1907322
Mecosta County relation 1907323
Menominee County relation 1798744
Midland County relation 1907324
Parcels Missaukee County relation 1907325
Monroe County GIS Monroe County relation 407497
Montcalm County GIS Montcalm County relation 1907326
Montmorency County relation 1907327
Muskegon County GIS Muskegon County relation 1907328
Newaygo County relation 1907329
Oakland County relation 359761
Oceana County relation 1907330
Ogemaw County relation 1907331
Ontonagon County relation 1798745
Osceola County relation 1907333
Oscoda County relation 1907335
Otsego County relation 1907336
Ottawa County relation 1907337
Presque Isle County relation 1907338
Roscommon County relation 1907339
Saginaw County relation 582247
St. Clair County relation 574424
St. Joseph County relation 1801751
Sanilac County relation 574462
Schoolcraft County relation 1898723
Shiawassee County relation 582246
Tuscola County relation 572130
Van Buren County relation 1907340
Washtenaw County 359766
Wayne County 359767
Wexford County 1907341

Table Field

Datasource Name

County Name

Relation ID

License

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.

Notes

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